Jump to content

All Activity

This stream auto-updates

  1. Yesterday
  2. Hello, I can not download data series from New European Wind Atlas When I try to download data (mesodownload/time series, then I make a selection and press download button), I am getting a file of HTML format ( mesoscale-ts) that takes me here: DataPoint API reference - Met Office This is the same if I go to this link, NEWA Mesoscale Time-series API - Swagger UI (neweuropeanwindatlas.eu), I complete the fields, execute and then try to download. Please can you help me with this? Thanks https://map.neweuropeanwindatlas.eu/
  3. Earlier
  4. Hi Rogier, thanks very much for your response. I am interested in learning more about how the most significant cells are chosen, in order to inform my roughness map creation process. Is this selection process described in more detail anywhere?
  5. Hi Doha, the papers you mention are indeed the right references. This paragraph in the paper 1 you mention probably explains it best: The original zooming grid is just a grid where the grid cells increase in size further away from the site: The roughness lengths in these cells are then multiplied with a exponentially weighted distance. From those transformed cell values the most significant ones are found with a simple algorithm where you just loop over all roughness changes until you have explained enough of the initial variance in all transformed roughness changes in a certain sector.
  6. Hi all, I have been investigating how large roughness maps are processed on WAsP, and have found the following two paper which describe some aspects of how the roughness rose is generated: https://wes.copernicus.org/articles/6/1379/2021/wes-6-1379-2021.html https://wes.copernicus.org/articles/3/353/2018/wes-3-353-2018.pdf I now understand that WAsP simplifies large roughness maps with many roughness changes into a roughness rose, and that each sector of this rose has a maximum of 10 roughness changes by default. I have also observed that a great amount of simplification is involved, as I have personally tested large roughness maps with more than 10 roughness changes in a given sector and seen resulting roughness roses with at most 5 changes in any sector. I have not found a detailed description of how the roughness changes used on the roughness rose are chosen or how WAsP simplifies or averages several roughness changes on the original roughness map into one roughness value on the corresponding section of the roughness rose. Does such a description exist anywhere?
  7. Thank your support ! Best regards, Trantduc
  8. We updated the wind climate models and the new model parameters are not supported by the old LIB file format. If you need a LIB file for a special purpose, you must recalculate the GWC without the new model options before you can export it to file. Follow this procedure: Right-click the GWC and select Show GWC from the popup menu. Open the Stability panel and select the old EWA profile model from the drop-down menu. Open the Geostrophic shear panel and hit the Turn off button Close the GWC and recalculate it Right-click the GWC and select the Export GWC to legacy format option from the popup menu. For WAsP calculations, we definitely recommend GWC calculations by the updated model and export to the new GWC file format. Maybe you can seek advice from the WindPro developers about the best workflow for their program. Best regards, Morten
  9. Hello WAsP Team, I am encountering an issue with data usage. Previously, I would import a .tab file, map vectors in WAsP, perform calculations, and obtain a .lib file. In Winpro, I utilized this .lib file as wind statistics in Site data. However, in the latest version of WAsP, the .lib file has been replaced by a .gwc file. Unfortunately, the wind statistics in Site Data currently only accepts .lib files. Could you please assist me in using the .gwc file appropriately so that I can use it for park calculations? Thank you for your support. Best regards, Trantduc
  10. The WAsP week 2024 is a three-days WAsP course followed by two days of workshops. You can learn about our ideas for workshop topics at WAsP Week 2024 open for registration, but we are open for your suggestions too. Do you have a topic, which you would like us to discuss in depth?
  11. Hi Pablo, The Terrain analysis (CFD) window can optimize this mosaic to cover all turbines and met stations by a minimum number of 2x2 km tiles. As you say, this will normally not result in an area of a rectangular shape. WAsP allows you to generate one or several resource grids, and they may include areas with no CFD data. To see how this work, we can open the ParqueFicticio workspace, which is part of the WAsP sample data normally stored in ..\Documents\WAsP samples\WAsP 12\Wasp, import the associated CFD data and create a resource grid, which is larger than the area covered by CFD calculations as in the first screen dump below. If we export this to a WRG file, that file will include the grid nodes without CFD data and report zero in all result columns, see second screen dump. I do not know how Windfarmer will react to a WRG file containing lots of zeros. To learn about best practice for CFD results in Windfarmer, I suggest that you consult the Windfarmer documentation or ask for their guidance. Good luck with your project!
  12. Hi Heather, The wind speedup and deflection script in WAsP Engineering provides a simple lookup table, which you can use to correct an observed time series observed at a reference point to the conditions at a turbine site and maybe another height above ground ground level. We made this script a long time ago supporting people who wanted to work with alternatives to the annual-maximum method, which in those days was the only extreme-wind estimation method in WEng. In principle, you could correct your time series by the lookup table of the WEng speedup and deflection script and use it for other purposes, but be aware that the WEng flow models focus on extreme wind conditions and does not include stability corrections. The built-in standard model of WAsP (IBZ) and WAsP-CFD are more suited for prediction of energy production. When correcting a time series by these models, you must consider possible differences in upwind flow profiles and apply the geostrophic drag law. As mentioned above by Rogier.
  13. Joan

    .lib to .tab

    Dear Ashlin, There is no tool available to do this directly. The .omwc/.tab files store an observed wind climate (usually based on measurements), while .gwc/.lib files store a generalized wind climate (typically produced by WAsP). A generalized wind climate is different from an observed wind climate, which is why a direct conversion is not possible. You can think of the generalized wind climate as the wind climate corresponding to idealized flat terrain with uniform surface roughness. If you want to calculate a wind climate for a specific height and position over real terrain, you can insert a 'reference site' in your WAsP project. You can then inspect the sector-wise Weibull distribution for this reference site, though, unfortunately, you won't be able to view a histogram similar to what is provided in a *.tab file. Best regards, Joan
  14. Ashlin

    .lib to .tab

    How do I covert a wind atlas file .lib to a wind speed and direction .tab file?
  15. Hi Heather, it is not possible yet to do what you describe but we are planning to develop it some time in the future. You can get part of the model chain by applying the speedups but the geostrophic drag law part is currently always converting to histograms (time-independent). If it is just about automating the process you could look at the pywasp or windkit (https://docs.wasp.dk/pywasp/ https://docs.wasp.dk/windkit/) where there is functions to convert from time series to histograms (https://docs.wasp.dk/windkit/io/wc_autogen/windkit.binned_wind_climate.bwc_from_timeseries.html).
  16. For example, would it be valid to use the wind speedup and deflection script to do this by computing the speed up and deflection for a range of angles and then applying it in excel to my time series of met mast observations?
  17. Thank you for your comments. To clarify: I am not trying to use multiple met masts in WAsP. I am trying to compute, for a time series of wind speeds from a single met mast, the predicted time series of equivalent wind speeds at each of my turbine locations.
  18. I am new to WAsP/WEng/WCA/WAT - I have tried to do my due diligence but apologies if I have missed something obvious: Amongst all of the tools in the WAsP bundle, is there a way to enter a time series of observed wind speeds at a particular met mast and extract the equivalent estimated wind speeds at each of the turbine locations? I am aware that I can load a time series of wind data into the WAsP climate analyser, extract a generalized climate, and then translate that climate to my turbine locations. I am also aware that I can enter a single wind speed and direction in WEng in order to obtain the predicted wind speeds at each of my turbine locations for that value. Essentially I just want to do that but for a large number of wind speeds and directions at once. Thank you for any guidance that you can provide, Heather
  19. I have reinstalled the software and the same error occurs
  20. Hi I get the above error when trying to insert a data treatment for wind direction. it doesn't not matter what number I insert I get the above error and the entire program shuts down instantly Regards
  21. yes it is resolved now, thanks The format for data should use "-" an d not "\" as is in the sample data
  22. Hello, I am making a big "mosaic" consisting of fifteen 2x2 km CFD tiles. The mosaic does not have a rectangular shape. Nevertheless, Windfarmer uses WRG files which are rectangular in shape. Should I create within Wasp fifteen 2x2 km WRGs to feed into Windfarmer? Or, Will WAsP allow me to create a single rectangular WRG although not all the area will be covered with CFD results? Additional info: All my turbines will be placed within CFD results area, which is guaranteed through appropriate windfarm boundaries set out within Windfarmer. Thanks very much!
  23. Dear Ashlin, We've encountered a similar issue before. Could you please check your TXT file using a text editor? It’s possible that the timestamp format might be inconsistent. The WAsP Climate Analyst requires a uniform date format, so you’ll need to ensure that your file uses a consistent format before importing it. Please let us know if this resolves the issue. Best regards, Joan
  24. Hello I am trying to import the sample data as a text file and I keep getting this error Exception report produced at 2024-07-31 01:54:48 Arithmetic operation resulted in an overflow. raised at: 2024-07-31 01:52:32 2024-07-31 01:52:32: Message added: Failed to read a file 2024-07-31 01:52:32: Exception raised in: ClimateAnalyst :cFileReadOperation:PerformReadOperation 2024-07-31 01:52:32: Message added: File reading operation failed while performing file read operation in class cFileReadOperationCollection in method ReadFiles. 2024-07-31 01:52:32: Exception raised in: ClimateAnalystcFileReadOperationCollection:ReadFiles 2024-07-31 01:52:32: Message added: Could not refresh the report view 2024-07-31 01:52:32: Exception raised in: ClimateAnalyst:fObservationSeriesFileImporter:ReadDataFromFiles Latest thread started in: ClimateAnalyst:cProgressMonitor:Class_Terminate Please assist
  1. Load more activity
×
×
  • Create New...