Duncan

Hello, which version of WAsP are you using? There was a problem with a recent update which meant that some workspaces were not getting the projection correctly restored. I think in that case, if you set the map projection again for the vector map (by hand) then it should work. This doesn't sound like a Google Earth related problem, more like something to do with our projection transformation work. Our code generates KML and then launches Google Earth to display that. If GE is responding at all, then GE is working. If the information rendered is wrong in some way (like the wrong hemisphere), then it's our code which is having problems. Duncan.

We'll add this as a feature request. Thanks. Duncan.

WAsP doesn't tell you how many turbines to install or where to put them. That's your job. The software will tell you how much electricity will be generated in the arrangement of turbines you have specified. Duncan.

Just use the power curve you got and you'll need to assume it's standard air density. But you could / should ask them if you should use something else. The CT curve is used only when doing wake calculations. You could take one from another, similar, turbine . There is a program called Turbine Editor included in the software package, I think, and you can use this to make the file needed for WAsP if you don't have a good one from the manufacturer. Duncan.

You can change the heights used when calculating a wind atlas. If you right-click the project and select "Edit configuration for member..." then find the option "Wind atlas structure" and you'll see five standard heights. Any of these can be adjusted, but keep then in ascending order of height. You can also change the number of standard heights. Next time you calculate a wind atlas it should use these settings. Duncan.

SRTM is orographic (elevation) only. There is no roughness information from that radar survey of the world. To prepare a roughness map, you could digitise the change lines yourself in WAsP Map Editor, or you could take a land use classes map and use some kind of table to interpret those classes into roughness lengths. Programs like Global Mapper support this kind of interpretation. Obstacles are another matter completely. WAsP 11 only accepts obstacles with polar coordinates. You can use the obstacle group editor inside WAsP to add information about them. Duncan.

Hi, were the data actually measured at 10m AGL, or were they downscaled to that height from some other simulation or measurement? Duncan.

Hello Hyungjun Yang, I have replied to you directly by email. Best wishes, Duncan.

Hello, We had a case last week where another user was seeing exactly this error message. The problem here is that the error message code itself has a bug and is not displaying anything useful for you. In the other case, the underlying error was actually that the calculation ran out of memory on a very very large domain. But because of the bug, the correct error message was not displayed. We have fixed the code already and the fix will be distributed to everyone with the next release. Is it possible that your error wsa actually the same? You could try reducting the domain size. In any case, you can email your project to us at wasp support and we can investigate further. Cheers, Duncan.

Hello Utku, Could you post the file here, or at least the top four lines of the file? If that's not possible, please raise a technical support request by emailing WAsP support . Then you'll be able to send the file in confidence and we can investigate what you're seeing. Best wishes, Duncan.

Hello Clanker, Sorry you are having problems. I've never heard of this before. The line of the error message that intrigues me is this one: "Cannot open a file with that name" Are you using an operating system with a special character set? Polish? Greek? Korean? Could there be something about one of the names you chosen? I do think that your problem is unique, so you're welcome to raise this as a regular support case for direct help. Best wishes, Duncan.

Hi CA1, Sorry to hear about this. For me, it's working fine, and we haven't changed anything recently in that part of the code. Has anyone else experienced problems with 11.5? Duncan.

That sounds like an interesting task. It's possible to do it from an internal script, but could be a little bit clumsy. By 'internal script', I mean a script file which you launch from the menu inside WAsP when a workspace is already open. The alternative is to perform the calculation using the WAsP automation API, but that requires a more expensive 'developer' licence. If I was writing this script, I would probably start by making an Excel sheet with lists all the combinations of site locations (6*x,y over 12 columns, one combination per row). Then I'd create the workspace with the 6 turbine sites arbitrarily located. The script would open the Excel sheet and work through row by row: assigning the locations to the six sites and then calculating the new AEP for the farm and writing that back to the Excel sheet in the 13th column, for example. HTH, Duncan.

Hi Anna, Since you posted this, we've been in contact via the WAsP support email, and it seems to be resolved. You fixed it by un-installing and re-installing WAsP. Duncan.

Hello, There are various pages on the web discussing this problem. As I say, it's not a problem with WAsP, it's problem with the operating system which WAsP can't solve. You could try temporarily switching off your AntiVirus. If that solves the problem, you should explore the settings on your AntiVirus and see if you can get things working while maintaining security. http://www.ehow.com/how_8586163_configure-avast-script-blocking.html I don't know if this is the problem, but it's all I can suggest for now. Best wishes, Duncan.

Hi everyone, Yesterday I hacked up a quick script for a colleague. It's simple and useful, so I thought of just posting it here in case anyone finds it helpful. I'll just paste the script source in here. The script finds all the turbine sites in the project root and writes a text file of sectorwise corrections in a way which is convenient for some other progam to read and use. Best wishes, Duncan. Utility Project

Hi, this is not an installation problem with WAsP. The scripting component is part of Windows, and is not working for some reason. Have you searched for information about the message you see? Can you say which version of Windows are you using, and what kind of virus checker / safety system are you using?

Hello, On a test machine with WAsP11, I un-registered my licence and found that it was nevertheless possible to create KML files and launch them in Google Earth. Duncan.

Hi, The answer is 'yes'! You can install the software and run it and open workspaces and look at the numbers and maps and so on. All this works fine without a licence. You can use an unlicenced WAsP as a viewer program. You can even change workspace arrangements and save them out to disc, but you can't recalculate your results. Hope that helps, Duncan.

This is really an archaeological question! We don't know about the code inside rsf2grd. But indeed, the old fashioned way of getting all-sector mean U was to use a Gamma function totalling of the sector wise A and K. It will be hard to reproduce the numbers exactly from a home made implementation. We found it was even sensitive to different Fortran and C++ compilers. Can you give me some more idea about which numbers (inside WASP) you are interested to use, and what you want to do with them?

Hello Windmueller, Can you help me understand? I can't find a script which is doing this. Can you tell me the exact name of the script (file)? Duncan.

Hello, Linux is not supported by our software. But in general you should be able to get wind speed results that make sense and are consistent. What are you generating, exactly? All-sector mean wind speed from the WRG 'Total'? How are you calculating it and with what are you comparing it? Duncan..

What problem do you see? Is there an error? I suggest that you separate the calculations from the presentation. Create an intermediate variable to hold the intermediate result. Put the number into that, and then MSGBOX it to see that the calculation has worked. Then handle the writing as a separate operation.

Hello Tanvi, I think that this is a special problem, so I have created a technical support case for this and will contact you directly. Duncan.

Hello, This is a strange issue. Can I just ask which version of WAsP you're using here? Duncan.