Duncan

Hi Mark, WAsP is a 32-bit program, and would not work differently. The core of WAsP is written in FORTRAN, and this language apparently has some fundamental constraints which make it very hard for compilers to make use of 64-bit addressing. (I have no idea why.) Most of us WAsP developers have 64-bit Windows on 64-bit hardware. There are really very few programs which can take proper advantage of 64-bits. The main advantage for us is that we can install and use lots of RAM. This lets us host multiple Virtual Machines, and have many programs open simultaneously. So this capability might affect how you use can use WAsP in your work, rather than how a single instance of WAsP itself will perform. Duncan

Hi. Note that you don't need a licence to run WAsP: only if you want to do some calculations. So you can open WAsP workspace and view and export the data without a current licence. One export option allows you to get a Surfer GRD of the all-sector power density. (Is that what you mean by a raster of the wind resource grid?).

Do you have the latest WASP version (10.1.100)?

Hi Hans Peter, I'm imagining a project with one or more wind farms, and under each wind farm there are groups of turbine sites and different groups can have different wind atlases with different met stations. Is that what you're doing? For each met station, you want to create an equivalent turbine site and do a siting calculation. First of all, did you know that you can get direct access to the met station's own back prediction? Metstation.BackPrediction.PredictedWeibullRose will give you a rose of AKF. For the climate, you don't need to insert a turbine site. But maybe you want the AEP result. For that, you would definitely need a turbine site so that you can use the associated WTG. In any case, you need a way to find these met stations in the project hierarchy. There are a couple of ways to get them. Depending on what else is going on in the hierarchy, the easiest might be to use the 'AllMembers' property of the workspace. This will give you a flat collection of all the members in the entire workspace. You can then filter this collection to select all the met stations, and iterate over those. To get a reference to the workspace from any hierarchy member, just do this: Set WorkspaceMember = SomeMember.AsIHierarchyMember.Project.AsIHierarchyMember.Parent Each HM can find its project, and you can rely on the workspace being the parent of every project. Now this reference you have is a generic IHierarchyMember type. To use IWorkspace-specific methods, you need to type cast it like this: Set Workspace = TypeCaster.CastMemberToWorkspace(WorkspaceMember) Then get a reference to the met. station class like this: Set MsClass = ReportingAssistant.AllClasses.ByID(ehmcMetStation) Use this met. station class to filter the workspace members collection, thus: MetStations = Foo.AllMembers.FilterByClass(MsClass) Now your variable MetStations is an iterator (type IHierarchyMemberGroupIterator) which you can loop over to work with each one in turn. You can insert a new turbine site and move it around the hierarchy to do the calculations you need. But it's probably easier to create and destroy a new turbine site for each met station you want to work with. But you need to put it in the right place. It can't be a child of the met station, or even of the met. station's parent wind atlas. So you need to go up two levels in the hierarchy and insert it there. You could do it like this: If Not Metstation.AssociatedWindAtlas Is Nothing Then Set AtlasParent = Metstation.AssociatedWindAtlas.AsIHierarchyMember.Parent Set TempSite = AtlasParent.Insertions.New.ByClassID(ehmcTurbineSite).Execute End Sub Does any of this help? Is it relevant to what you're trying to do? Do you want a complete code example? Duncan.

Generally, each period should be a year. We don't recommend anything else, as far as I know. The all-sector U50max is calculated from the sectorwise values, and should usually be greater than any of the sectors (not the maximum value from all sectors). I see that the help file does not explain why this should be. I will try to find a reference if you want. I don't quite understand your third point. What do you mean here by wind 'type'? Duncan

Hi Hans Peter, Sorry if the WAsP hierarchy interfaces are confusing. They were designed to be rather generic and support new types of hierarchy member in future. In retrospect I see that we could also have implemented other, simpler, interfaces on the same underlying model, which might have made scripting simpler. We'll consider that for the next generation of code. Meanwhile, here's a suggestion about what you want to achieve. Set Site = Project.AsIHierarchyMember.Insertions.New.ByClassID(ehmcTurbineSite).Execute If Not Atlas.MetStation Is Nothing Then Set MetStation = Atlas.MetStation If MetStation.AsIWaspSite.IsLocatedInMap Then Site.AsIWaspSite.Move MetStation.AsIWaspSite.Location.x, MetStation.AsIWaspSite.Location.y Site.HubHeightAgl = MetStation.AnemometerHeightAgl Site.AsICalculatingHierarchyMember.DoAllPossibleCalculations MsgBox Site.PredictedWindClimate.EmergentProbabilityDistribution.MeanSpeed End If End Sub Site.AsIHierarchyMember.Remove Workspace.AllMembers.FilterByClass I hope that this works, or gives you a clue. If the enum member ehmcTurbineSite doesn't work, then replace it with integer value 7. I assume that you have only one atlas in the project. If you have different atlases associated with different turbine sites or farms, then it's more complicated to find them all. Let me know if that's what you need and I can post some sample code. Duncan.

There is a paper which may give more detail... Kristensen, L., Rathmann, O. and Hansen, S. O.: 1999, Extreme winds in Denmark, Technical Report Risø-R-1068(EN) , Risø National Laboratory. ... but I don't have an electronic copy of that. Perhaps someone else can help?

Hello, In WAsP Engineering, we don't do any power calculations so it doesn't use a representation of the turbine type. Duncan.

Hi Manohar, Jose, This error is actually due to a software configuration problem. We are making a fix which should be ready next week. We can send it out to anyone who is affected, and this fix will eventually be included in an update to the software. If you're not seeing this error message, then you're not affected. Please email me duncan(at)wasptechnical.dk or Niko niko(at)wasptechnical.dk for further assistance.

Remember that if you download a CHM file from the web, you sometimes need to 'Unblock' it before you can use it properly. Right-click the file and view the file properties to make this change.

Hi Hans Peter, We should have another beta (#4) ready later this week. I'll send you a link as soon as it's available. Duncan.

Have you checked the help file? If you search for RIX you'll find a section called "Limitations of the flow model". An explanation of the delta-rix approach is given in http://www.wasp.dk/Support/DownloadFiles/Influence%20of%20topographical%20input%20data.pdf

WAsP Map Editor can certainly do this. Have you checked the help file? Search for 'digitize'.

Hi, we don't have a fixed date, but we are already running much later than we hoped. If we can't make the final release before the summer vacation, we'll all be extremely disappointed. Sorry to be so vague, but it does depend on beta testing work, as you say. If anyone wants to just have a look at the new version without getting too deeply involved, we can make a standalone exe which doesn't require installation and leaves your existing WEng 2 perfectly intact. Any takers?

Can you tell us which version of WAsP you're using, please?

Hello, I have made some updates to the RveaScripting CHM file. Nothing extensive, I'm afraid. There are now lists of the interfaces available for WAsP scripting but no instructional text. Download the CHM from http://wasptechnical.dk/Services/Redirect.aspx?token=033ca13c-d59c-49aa-a502-aac5fe719297 Remember that if you download a CHM file from the web, you sometimes need to 'Unblock' it before you can use it properly. Right-click the file and view the file properties to make this change. We will also be publishing this help file as a web help resource soon. The documentation will be revised again this spring, to match the release of WAsP Engineering 3.

WAsP Engineering 3 is finally on the way. We are in the beta-testing phase now. New features include: * Create projects direct from grid maps * A new type of sectorless extreme wind climate * Obstacle effect cleaning for met. stations * Display output in Google Earth (like WAsP 10) * A new, dongle-less licencing system * Better integration of calculations for the WAT Is anyone interested in helping out with the beta testing? It would be great to get some feedback from about five or six serious WEng users. If you're interested, and would have time to do this in the next month, then please email me: duncan.heathfield@wasptechnical.dk.

This forum is not about WASP3D. It's about a wind energy modelling program called WASP (www.wasp.dk). There is no such thing as a reverse countdown in our software.

Are you sure that this is the right WAsP product? Perhaps you mean this one: http://www.wasp3d.com/WASP3D/support.php

Hi Folks, Sorry to disappoint, but I am simply trying to find time to make a dump of the API declarations to the documentation: not to do a full explanatory job on the API itself. I know it's pathetic, but it's all we can do at this stage.

Hello HPJ. Sorry I didn't reply earlier to your post. There were complicated reasons which made it easier for us to have the air density as a project level setting, rather than using the WTG table selection. I can't quite remember what they were, though. Sorry if that's inconvenient, but it made it possible to introduce the change sooner. I can give you some pointers about how that script would work. If you have a reference to the project (IWaspProject), then you can use the property AsIRveaConfigurable, which will typecast the reference to an IRveaConfigurable interface. From this, you can retrieve the Configuration (interface: IRveaConfiguration). That'll let you get the parameter. Set Parameter = Project.AsIRveaConfigurable.Configuration.ParameterByID(TheID) TheID you need for this is "ROHFORPD". Hint: you can see the IDs in the parameter dictionary in the registry at HKEY_CURRENT_USER\Software\Risoe National Laboratory\Parameters\ When you've got the parameter, you can simply set the value Parameter.Value = Wtg.SelectedPerformanceTable.AirDensity Hope that this is helpful. (I'm trying desperately to make time to finish adding the WAsP scripting interfaces to the RveaScripting documentation CHM. Hope to achieve that this month.)

Actually, there really is an online help file (for WAsP version 9, at least). http://www.wasp.dk/Support/FAQ/WebHelp/Wasp9.htm

Hi. Thanks for posting the problem and the solutions (so quickly that we did not have time to contribute!). This is exactly that the forums are supposed to be about. The guy who wrote the LIDAR script is on leave just now, but we can try to help if you have any other problems.

I guess you should send it to us to have a look, then. Could you do that? wengsupport@risoe.dk.

Posts are welcome. Let's hope others are getting some benefit from these discussions too. Module-level variables can also be seen by all the procedures: they don't need to be consts. You only lose the constancy, not the scope.