Duncan

Hi Vob, Thanks. I have looked through our feature request backlog and we have planned for exactly this, but the process fell between two members of the team, and has been inactive. Now I have re-started the process. Mostly, this was done, but we got stuck on a technical detail. You should expect to see this in an 11.3 release in the next few months. Best wishes, Duncan.

Hi, Sorry that you are stuck with this problem. We're preparing a tool to help, but I don't know when it will be ready to ship. While we make the tool, we could run it on your lib file and send you back an extrapolated one. Just email us the file and we'll do something ASAP. Best wishes, Duncan.

Hello, We are almost ready to release version 3.1 of WEng. The big difference over 3.0 is that it supports Peak-Over-Threshold extreme wind climates. These OEWCs can be generated by the latest WAsP Climate Analyst (Version 3.0 is available now from the WAsP web pages (http://www.wasp.dk/Download/Software/WEng3_Installation) There is now a release candidate of WEng 3.1. If anyone here would like to give it a try, then please contact us by email and we'll send a link. Best wishes, Duncan.

Hi Vob, Yes, the wake effects are only modelled within wind farms. Each farm can have different sub-groups. So it sounds like you should move both farms into a single farm as separate Turbine Site Groups. This should be possible with a drag and drop. It's neither a bug, nor a feature. It's just the way we made it. This allows users to have multiple wind farms in the same project without modelling their interference (for example if they are far away). HTH, Duncan.

If you are getting a message like "meso-scale roughness lies outside gwc roughness" as an error, or if you can't calculate some site because "the atlas range does not include the site roughness", then you need to re-calculate your Generalised Wind Climate (GWC) with different settings. In fact, the new (WAsP 10.2) default settings are probably what you need. So, I suggest that you do this (assuming that you have the met station data to allow you to recalculate the atlas)... 1) Move (drag) the GWC and its child met. station to the workspace root 2) Insert a new GWC to the project. I will have the new default max roughness of 1.5 metres. 3) Move (drag) the child met. station back to the project under the new GWC 4) Re-calculate the atlas and then its derived predictions If you have a site where the meso-scale roughness in one sector is greater than 1.5 metres (?!), then you'll need to change the defaults before creating the new atlas. To do this, right-click on the project and choose "Edit configuration for member". Then expand "wind atlas structure", and select "standard roughness length #5", and edit that upwards. Hope this helps. For those who can't actually recalculate their old GWCs (Libs), we will try to offer you something soon. Duncan.

Hi everyone, We have made a WAsP update which fixes a couple of GUI bugs and makes a small relaxation of the constraints. Unfortunately, we cannot really remove the rule which says that you can predict for a meso roughness length greater than the maximum roughness class in the atlas. This extrapolation is just unsafe. But we have no restored the ability to extrapolate down below the lowest height in the atlas. You can download Release B of WAsP 11.2 from here: http://wasptechnical.dk/Services/Redirect.aspx?token=9c08f8b0-4516-4f5b-a37a-1e0272654378 We are working on making changes which will allow you to perform a deliberate, one-time extrapolating change to your wind atlas to add a new, higher roughness length. But we really recommend that if at all possible, you should re-calculate the atlas in this case. That's the only safe and correct thing to do. Best wishes, Duncan.

Hi everyone. So far not too many people have this problem, but we've worked out a solution and will try to update this week. WindPro users are having problems getting the wind profile calculation to work, because it starts near the ground: lower than the lowest height class. We plan to relax this constraint, but the real fix is to change the settings for the profile calculation so that it doesn't go below the minimum height. Duncan.

And if you're following the forum, you'll see that this is now an actual release. http://www.wasptechnical.dk/Forum/viewtopic.php?id=830

Hi David, Thanks for your message. You've made a good point. It could be that this change affects more cases than we expected. I actually found this problem with the WAsP 10 sample data! I will urgently check with the scientists to see what they recommend. Duncan.

Today we release WAsP 11.2. You can download it from here: http://wasptechnical.dk/Services/Redirect.aspx?token=56ce31bf-bc28-4db8-b1cd-b5998aafb540 We have made some changes to the core model to fix problems with CFD flow result treatments at unusual sites. You should probably re-calculate existing projects, but don't expect any significant differences in most cases. Good news: this doesn't affect your CFD result tiles so there's no need to recalculate those. There are more detailed release notes here: http://www.wasp.dk/Download/Software/WAsP11_Installation/WasP11_2_ReleaseA_Installer Best wishes, Duncan.

Hello, anyone working on this is welcome to test with our latest Release Candidate for WAsP 11.2, which includes this feature. Get it here: http://wasptechnical.dk/Services/Redirect.aspx?token=16e6c06f-4c0d-4aab-a272-5f76be45fa38 Email us if you need some help or advice.

Hi Vob, The code is trying to be smart. The hierarchy is only refreshed properly after the script has finished executing. Then, it looks to see how many new things have been inserted. If there are more than five, then no windows will be opened. Have you noticed that working? Anyway, I've just added the feature you requested. A script can now call ReportingAssistant.DisableGuiWindowOpening. This will simply disable the opening of new windows from insertions for the script. It's reset automatically when the script has finished. The script can't turn it back on again, so you can't choose to have some windows displayed and some hidden within a single script operation. This will be in the builds for WAsP 11.2. Hope that helps! Best wishes, Duncan.

Hello Burock82, BPal, Sorry that your posts have gone unanswered until now. Borock82, I don't really understand what you're asking about here. Do you mean that you want to extract data from the CFDRES file directly and insert it to Excel? That's what BPal is wondering about. It's true that the RES file is a ZIP archive which consists internally of a lot of different Surfer-format GRD files which are quite clearly labelled. You could easily extract these from the RES archive and display them in Surfer. However, If you extract any data from the CFDRES file yourself and use it for something, then you're on your own: that's not WAsP output. There are some non-trivial interpolations and other checks being made in the code which interprets the contents of the CFDRES file for display and downstream use in the WAsP software. This code is running inside both WindPro and WAsP. To get a site result, you should work with the GUI or scripting interfaces to extract what you need from our modelling objects. In the met. station window, you can see the turbulence intensity for each sector on the site effects tab. Does that answer your questions? Duncan.

Hi, My colleague Ray is looking into this question and will reply to you. If nothing simple can be done, we will add some methods to the script execution context to let you achieve what you need. We are very keen to help people who have invested such effort in discovering how to use the types and develop scripts. Best wishes, Duncan.

Hello, I'm sorry we didn't respond to your original post. The main scripting wizard (Ray) is on holiday just now, but I could have helped out with this question. The RSF format is depreciated, partly because it has such strict fixed column widths that don't work well with modern wind farm data. It's great to hear that you found a script to do what you need. The utility script only does one site at a time. I think we put it there really as a template example for cases just like this, so that you can create a correctly formatted RSF. Duncan.

With the release of WAsP 11, we removed roughness roses from the program. It's still possible to see the roughness rose (survey) which the model calculates if you use a reference site, but you can't provide them as inputs for calculations. The only way to tell WAsP about the roughness around a site now is to provide the data as a map. Our assumption was that almost everyone is using maps to describe roughness now. Has this change caused difficulty for anyone? Does this change prevent anyone from upgrading to WAsP 11. If so, we'd like to hear what kind of problems you see. Duncan.

Hello, I have looked at the code, and I can't see what's causing this. It's apparently to do with the report template files. Either the css or the report template. The corresponding settings are in HKEY_CURRENT_USER\Software\Risoe National Laboratory\Wasp\Version 11\User settings\File broker\Reporting And the files should be there in the program files folder. To investigate further, I need a full error report. I'd like to take this off the forums and into our formal bug tracking system. If either you, Per, or your end user or Malik the OP, could send me some more information, please do. Mail to support@wasptechnical.dk

Hello, The Error you see is something to do with 'Insert Disk Abort", which seems to indicate there is some problem with accessing the old hard drive. I suggest that you search for *.wwh files on the old drive, and copy them onto the new machine and try to open them from there. If you have a *.wwh file which you can't open, you can send it to us at wasptechnical, in case we can do anything, but I don't expect much. If you can't see any *.wwh files on your old hard drive, then they are either lost or corrupted somehow. Duncan.

Hi Jan, Sorry we didn't reply sooner. To get the speedups to Excel, you can go to the 'Site effects' tab on the turbine site window and just CTRL-C to copy them all to clipboard. They should render nicely if you paste them to Excel I will pass on your question about the reference speed for turbulence intensity to my colleagues. Duncan.

Please can you check that you have updated to the latest available build of WAsP Engineering 2? http://www.wasp.dk/Download/Software/WEng2_Installation

Is it possible for you to upgrade to WEng 3? WAsP 11 and WEng 3 work best together. I am not sure if WENg 2 can run a WAT script with WAsP 11, but I can investigate if you need. Upgrading WEng is by far the best option here, so let me know if that's possible.

Hello, it should be possible to make an Excel script to do this. Can you send an example worksheet to show exactly which data and which format you need? Duncan.

Hi Youci, These are different. The rose is formed from directional sectors and sub-sectors. So the sector could be 30 degrees for a 12 sector rose. Then there are sub-sectors within these for higher-resolution analysis. Within each sector, there are roughness areas separated by changes. That's the number of changes per sector. The maximum is 10, so no matter how many actual roughness change lines intersect with the sector, the roughness view along that sectors direction will only contain 10 'zones'. To see all this, look in the reference site window, where we let you calculate and display the roughness rose. HTH, Duncan.

Does the word report do everything you need apart from put the output into Excel? Is it this one: "Applied EWC report: 50 year winds for all sites and heights"? Duncan.

If you download a CHM file from the web or a network, it's "locked" for security reasons. You need to right-click on the file in your file system explorer and select 'Properties'. You should see a big button labelled "Unblock" or something. Click that and try again. Duncan.