Jump to content

All Activity

This stream auto-updates

  1. Last week
  2. The two most common problems with the SCM tool are The SCM server providing the long-term reference data might be down. However, I just checked and it worked OK this afternoon. If the coordinates of the reference mast or the map projection are incorrect, the SCM server might not find the data, e.g. it if the false position is in the middle of an ocean. The easiest way to check the mast location is to open a spatial view, synchronize with Google Earth (see below), and make sure that the map is displayed correctly on the virtual world. If these simple explanations does not apply, then please contact our technical support system via mail. The above error message might be enough for the programmer to understand the issue, but please also describe your actions just before the error message arrived. Screen dumps and a sample project file demonstrating the problem are also useful and sometimes even necessary. In general, it is usually better to contact the support system about specific technical problems and reserve this forum for discussions of interest to all users.
  3. Dear Team, I am trying to compare the results between EWC and SC method but i could not run SC method. i tried to change the map size, map file, and wind data as well. however, nothing works. the message is as follows but hard to interpret. // Exception report produced at 2024-06-21 17:47:47 Object variable or With block variable not set raised at: 2024-06-21 17:46:12 2024-06-21 17:46:12: Message added: Could not create a SCM data server 2024-06-21 17:46:12: Message added: Could not begin the insertion of an SCM extreme wind climate 2024-06-21 17:46:12: Exception raised in: WAsP Engineering: cProjectEditor:InsertingScmExtremeWindClimateBegin 2024-06-21 17:46:12: Message added: Could not explore (or perform one of) the operations available for a selected thing 2024-06-21 17:46:12: Exception raised in: WAsP Engineering:cOperationSet:ExploreOperations 2024-06-21 17:46:12: Message added: The 'Create generalised extreme wind climate using SC method' operation could not be performed 2024-06-21 17:46:12: Exception raised in: WAsP Engineering:cOperation:Invoke 2024-06-21 17:46:12: Message added: Could not perform the action requested 2024-06-21 17:46:12: Exception raised in: WAsP Engineering:cMainform:ProcessContextMenuToolClick Latest thread started in: WAsP Engineering:cMainform:pSlaveForm_ToolbarClicked // could you please help me out to progress? Regards, Gyeongil
  4. We have released new versions of PyWAsP and Windkit. Windkit has a number of deprecations, please pay attention if you are using these. We aren't sure how long we should keep deprecations around, please let us know if you have thoughts on this. PyWAsP has a number of breaking changes, we are closing in on a more stable API, but still expect a few more breaking changes. The highlights of Windkit include a new Long Term Correct module, an improved WindTurbines class, better integration with GeoPanandas, Improvements to downloading of raster and vector maps, and a new function to implement cross prediction. Full release notes can be found at: https://docs.wasp.dk/windkit/release_notes.html#id1 For PyWAsP the main highlight is the new climate extrapolation functions. These functions allow the prediction of either binned or weibull wind climates without creating a generalized wind climate lookup table, reducing interpolation errors. The binned wind climate to binned wind climate approach was presented at the Wind Europe Technical Workshop for Resource Assessment. In addition, new BWC resampling functions have been added, we have included support for custom root CA certificates, and have been able to improve performance for a number of functions. Full release notes are found at: https://docs.wasp.dk/pywasp/release_notes.html#id1
  5. Yes that calculation is similar except you don't need the fgtm (frequency greater than mean) variable, because the inputs for NEWA microscale are sectorwise A and k's, the fgtm is only required when you have a wind speed histogram as input. The first and third moments are calculated from the wind direction frequency weighted first and third moments and then you can use `_fit_wasp_m1_m3` to find the combined A and k from those.
  6. Earlier
  7. Thank you so much. I was specifically looking for the calculation of weib_A_combined and weib_k_combined values which is obtained from downloading the wind data from Microscale API https://wps.neweuropeanwindatlas.eu/api/microscale-atlas/v1/get-data-bbox. Do they use https://docs.wasp.dk/windkit/_modules/windkit/weibull.html#_fit_wasp_m1_m3_fgtm as well for the calculation of weib_A_combined and weib_k_combined ?
  8. Thanks very much Morten, the dummy roughness line works perfectly.
  9. I was testing my above method and need to correct myself. It seems like the map editor does not save information about the adjusted map size to file. so I guess thise merely was intended as a way to enlarge the 'canvas' while 'painting' roughness-change lines and elevation contours manually. In most cases you can use the methods inside WAsP and WAsP Engineering as described in my post above, but not for the Prepare data for WAT tool inside WAsP Engineering. The trouble is that this tool will ask you for a WAsP vector map file and then do some WAsP calculations for mean wind climates. As you can imagine, this can fail if the map does not include an offshore wind farm. A work-around method is to open the map in the map editor adjust the map size to include the wind farm create a dummy roughness line as a polygon surrounding the offshore wind farm specify water surface roughness both inside and outside that polygon. Load the map with the amended map into the Prepare data for WAT tool and its WAsP calculations should work without problems.
  10. The map editor limits the map domain as you describe, because it does not know for sure how far the water surfaces extends into the unknown. However, you can select Edit> Adjust map domain size in the main menu of the Map Editor main window (not the Map display window) and extend the map domain size manually. As an alternative, you can extend the map from inside WAsP. For this you right-click the vector map in the object hierarchy and select Change Extend of map from the popup menu. The domain editor of WAsP Engineering program generates a grid map based on your vector map. For coastal or offshore sites, we sometimes need to extend that map in the offshore direction. For this you first zoom out the displayed vector map and then you can select a grid map with more extend in the offshore direction. The zoom button in the WAsP Engineering domain editor window is the second one next to the line with the name of the vector map, see below.
  11. Hello, I downloaded elevation data from GWA map warehouse for a coastal site, using Map Editor 12.4. It seems that the program is truncating the map extension to areas of existing contour lines on the continent. The coast I am dealing with is the Pacific Ocean so I have 1000s of km without contours in that direction. This truncation effectively reduces the distance to the map border recommended for modeling with WaSP (modelling height x 100). Should I worry or try to fix this manually (eg. creating a small contour line say 10km off the coast)? Or am I skipping some step when downlading elevation data? Thanks very much!
  12. It is probably easiest to check this code for the calculation: https://docs.wasp.dk/windkit/_modules/windkit/weibull.html#_fit_wasp_m1_m3_fgtm
  13. Hello Team, I was not able to find anywhere which method is used to calculate the weibull parameters A and k. Can anyone confirm the method of weibull estimation used and whether there are any special approaches taken by WASP in the estimation?
  14. ... I saw, your second post. I am not sure what happened, but this error is probably related to the first one, and difficult to reproduce in the latter session.
  15. Hi Rainer, Thank you for reporting this. I assume that you are using the new WAT 4.7, and I also used this for testing. Your method is correct, and I don’t think you misunderstood anything. I can reproduce the first reported problem, where the map is placed outside the project tree. Furthermore, WAT gives error messages when I try to move it or delete it. This is clearly wrong and something which needs fixing. You wonder whether the error affects the results. The terrain elevation data are used for evaluation of terrain complexity and thereby the Cct factors and turbulence results. If the map is missing WAT will use the maximum Cct factor of 1.15. In my test, the misplaced map object does not affect the results at first, but when I select new turbine sites, WAT found the map object even though it was misplaced. Maybe you can use this as a temporary work-around, while waiting for an amended WAT version. To check the Cct used for the turbulence calculations you can look at Reports for selected turbine> Terrain complexity. I do not fully understand the second reported problem where you imported two sets of WAsP/WEng data and observed NaN values for effective turbulence results. Most likely the data were not imported correctly, but I you like me to check, then please send the resulting WAT project as an attachment of a mail to waspsupport@dtu.dk. You do not need to explain much, just refer to this discussion thread. Cheers, Morten
  16. update to the second point: Now it calculates the eff. TI. Don't know why, I changend nothing? Perhaps waiting one hour solved the problem 😉 The first problem is still there, the Grid Data disappears when adding site groups to WAT.
  17. Hi, I have problems with WAT: 1. when I 'prepare data for WAT' in WEng and open it directly in WAT, it opens and all is fine so far. But in the next step, when I prepare data for WAT for different sites/hubheights and save it in Excel and then import in in WAT (add more WAsP/WEng results), the Terrain Grid Data Object disappears and I just have the two sitegroups. There are Turbulence results in the result window, but I'm afraid that they don't consider the terrain height anymore? When I export the Terrain Grid Map from WEng and import it in WAT, it is shown outside the Project 'folder'. If I try to drag&drop it to the project, I get an error message (EAccess Violation occured...) 2. When I prepare both sites/heights as Excel files and try to import them in a blank WAT project, no effective Turbulence Ieff is calculated, it only shows 'NAN's in the Eff. turbulence table resp. the 'Ieff,site' column. Also there, I cannot add a terrain grid map to the project, see above. Am I missing something? How can I calculate the eff. Turb. Intensity when starting the WAT project from scratch? Best Regards, Rainer Cordsen
  18. Dear user, I am sorry but we do not support WAsP 11 or any other old software versions anymore. WAsP 11 was supported until one year after the release of WAsP 12 in December 2017. Therefore, an upgrade to the WAsP Bundle license (including WAsP 12, WAsP Engineering 4 and Windfarm Assessment Tool 4) is necessary in order to have support included with your license. You can learn more about what’s new in WAsP 12 here: https://www.wasp.dk/software/wasp/whats-new-in-wasp-12 You can order WAsP 12 here: https://www.wasp.dk/order Best regards, Katerina
  19. Mert sent us some WindPro and WAsP project files demonstrating these wake loss difference. Thanks for this, it is always easier to discuss possible problems when we have test data! My former DTU colleague Tobias Ahsbahs, now working for the WindPro developers at EMD, spotted that the Ct curve used in WAsP project was much lower that the Ct curve in the WindPro project. We all agreed that this must be the reason for the different wake loss predictions.
  20. I Been having problems with using WAsP within the resource, statgen and scaler in windPRO 4, I’m using a licenced WAsP 11.4 version, when I try to run anything related to WAsP keep saying “rvea0223 is not unlocked”. How can I fix that?
  21. Good afternoon. I write from Mexico. Please. Can somebody help me? I have a perpetual license for WAsP 11, but it stopped working properly. And they don't give me technical support. I need to install the program again. Can someone send me the link to install WAsP 11? Please.
  22. Morten

    WAsP 12 Losses

    We rewrote the homepage, so the WAT AEP link is changed to https://www.wasp.dk/software/windfarm-assessment-tool/wataep. It does not explain that much about the models, but I once made some videos about this for DTU students The latest WAT version enhanced the AEP model with an option for different uncertainties and technical losses for individual turbine groups, see Windfarm Assessment Tool version 4.7 released - WAsP
  23. Hi Mert, The implementation of the wake models in WAsP and WindPro are independent, so it is quite possible that the programmers made different choices. I made a third implementation in WAT and compared it with WAsP. The agreement was reasonable in flat terrain, but the differences were larger than expected in complex terrain. This must be because I handled speedup and deflection between the wind at the wake-shedding and wake-exposed turbine sites differently. Other reasons for model deviations could be the number of calculated wind directions within each wind sector the interpolation in the power and thrust-coefficient curves when looking up data for a speed-up corrected wind speed - especially near the cut-in wind speed possible air-density correction of the thrust-coefficient curve in WindPro? - we decided to ignore this in WAsP and WAT So you see, even though the PARK 2 model is really simple, there are undocumented details, which programmers might handle differently. Kind regards, Morten
  24. Mert

    WAsP 12 Losses

    Hello, The WATAEP link is not working. Could you please update the link? I have the same issue. Thanks and kind regards, Mert
  25. Hello all, We have one Windpro account which utilizes WAsP to calculate the energy production. Recently we have realized even tough we reach the same Gross Energy Production with using both Windpro and WAsP seperately , we are getting different wake loss values when doing the exact same wind energy assessment. All the information is exactly same for both softwares(height contours, roughness map, wind data, power curve, same Wake Model). I am suspicious regarding the wake models. In WindPro we have (N.O. Jensen (RISO/EMD) Park 2 2018 model, in WAsP it says PARK2. Do these have differences? Thanks and kind regards, Mert
  26. Hi Morten, I created a ticket using your link. Thank you so much for that. I would get support very soon from the team.
  27. Hi Morten, Thanks for your time. No, I am new here and want to fix the issue. I used the sample data from Wasp; for example, the sample of Italy used data from 1997 to 2002, which showed me the same issue. I emailed the WASP technical team about this issue, but they have not responded.
  1. Load more activity
×
×
  • Create New...