Duncan

Avnerfurshpan, I have emailed you directly from waspsupport to ask you more about your case. I think that for the script timeout to arise, you need to have invoked a single (atomic) operation which takes a long time. The script might take a long time to run if it does many operations, and no problem will arise. The error is caused by a single operation taking a long time. I'm interested in what kind of operation you're running that takes so long to complete. Is it a big wake calculation, or a resource grid? How big are your maps? Duncan

Yes, WAsP Map Editor 11 does not have any licence protection: you can use it for free, even if you only have a WAsP 10 licence.

Yves, we have had a mix-up in getting an answer to your question about the user manuals. I have now sent it again. I have also emailed you directly to follow up this question of the WAT error you have seen. In the other thread (http://www.wasptechnical.dk/forum/viewtopic.php?id=747) we asked for some data to reproduce the problem, but apparently we have received none. Let's clarify the situation and get things working for you.

Hello JonnyGP, Have you downloaded and installed the latest map editor? http://www.wasp.dk/Download/Software/WAsP11_Installation Duncan

Hello. I'm sorry to report that this feature request got "lost in the long grass" while we worked on the CFD integration for WAsP 11. I found it assigned to a future milestone. Now it's been moved up to the next release. If you're ever "constantly running into an annoyance", please keep on telling us! We have many items on our radar, and sometimes they can be accidentally dropped like this. Apologies again. Duncan.

Hi Malik, We have contacted you directly by email about your problem. Duncan.

Hello, We have a freely-available DLL which you could use for this: it's guaranteed to give the same results as WAsP tools. I will ask my colleague Matti to contact you. As for the exact implementation of the binning method, I will ask the responsible scientist to post an explanation here. Best wishes, Duncan.

Sorry I still can't understand or reproduce what you're seeing. I guess we need to exchange screen shots. I will email you directly to continue this discussion.

In the new project dialog window, you have selected the "Use Grid Map" tab, I presume. Then you have two selections to make: the source elevation map and the source grid map. There are separate buttons and fields for each of these. For roughness, you can choose to use a single roughness length instead of a roughness grid, but if you select a roughness grid map the single roughness length option should be deselected automatically. Sorry, but I don't understand your description of the problem, unless you are trying to load a roughness map using the button intended for selecting the elevation map. If this doesn't help, maybe email me directly with a screen shot or something. Best wishes, Duncan.

I have today found and fixed this bug. It will take a couple of weeks for us to release a new installer which repairs this. If anyone needs a fix in the meantime, please email me for help (support@wasptechnical.dk).

Hello, Did you notice that there is a new release of the Map Editor program available from the WAsP Web site. Please try if this helps with your problem. http://www.wasp.dk/Download/Software/WAsP11_Installation.aspx Best wishes, Duncan.

Well, if the problem is different, the next release might not fix the bug! I will take this discussion to direct email, so that we can investigate your case in more detail. Duncan.

Hi, It appears your dongle has had some kind of physical failure and needs to be replaced. This discussion now continues by direct email. Duncan.

Can you explain the two sources of data which you are trying to combine? Are they both maps?

Hi JonnyGP I have replied directly by email. Sorry for the (long) delay in offering you help. Duncan.

Thanks Mango, I have received the data. I think the answer will be specific to your case, so let's take this off the forums and handle it by email.

Hello. If you have downloaded the help file (CHM) from the internet, Windows will block it buy default. Right-click on the file in explorer, and select Properties, and then choose 'Unblock'. HTH, Duncan.

Hi Chuaw, Sorry to hear about this problem. It's not a known issue. The dongles for all versions of WAsP are the same, and many people are using them successfully on Windows 7 -64 as far as I know. The fact that the dongle light is not coming on may indicate that there is a mechanical problem with the dongle itself. Can you try it on another computer? What happens if you just plug it in? Duncan.

Malik, you should be able to open the help file from the main Windows start button, in case the WEng menu item does not work. But your error message shows something funny. "C:\Program Files (x86)\WAsP\Bi\Weng3.chm" It should be wasp\bin. I wonder what's happening here. If you see any other funny problems, then I suggest remove and re-installing all the wasp software you have.

Hi Mango / Jer, Yes, it's hard to understand without a map of the site. Can you send me something by email? Duncan.

Hi Malik, What have you tried so far? Did you try removing and re-installing? The DLL 177 doesn't usually give any problems, so it seems that maybe the installation was not successful. Did it work before and then suddenly stop working?

Great to hear this. Thanks. I guess other people will experience this as Windows 8.1 gets rolled out more widely.

The roughness survey which WAsP calculates from the map data is a summary. I have asked my colleague Qiangbing to reply with a more detailed description of the way this is calculated. It's explained in the European Wind Atlas.

Thanks for your contribution. No-one answered and we actually removed the feature completely from WAsP 11. I don't know if anyone even noticed: certainly we had no complaints.

Hi, Sorry about this. Have you by any chance installed WAsP 11 as well? In some cases, this has given rise to a version conflict. We have a fix which I can send you. WAsP 11 and WAsP 10 should run fine side-by-side on the same machine. This is not your fault. Duncan.