WAsP 8.3

This document describes the releases, the bug fixes and other changes made.

Version 8.03.0037

Do I really need to install this?

Yes. This release fixes some obscure but confusing problems, as well as improving the way that the hierarchy status is communicated.

Bugs fixed

• There was a date generation error in the resource grid calculation script
• The wind farm uniform hub heights setting was failing to work reliably in some obscure cases
• There was sometimes a problem with system memory not being correctly released when a workspace was closed
• Roughness roses set to be calculating would not be self-calculating when a project/workspace is re-opened from file.
• Roughness roses opened from file might be emptied of data if moved to be a child of a new site.

New features and improvements in this release

• The Risoe Licence Manager program has been completely overhauled, and the dongle drivers should be installed more reliably. (Note, however, that the installation now takes longer to complete.)
• Hierarchy members which are in the 'root' workspace area are now shown 'greyed' to emphasise that they do not contribute to calculations.
• Results which can no longer be calculated are 'flushed' (cleared away) when the corresponding hierarchy member is calculated
• Hierarchy members with results due for flushing are now shown as 'dirty' (yellow warning icon)
• WAsP 9 workspaces can be opened in WAsP 8 for testing and comparison

Installation

This release can be installed on clean machine, using the MSI (or EXE) file, or can be used to update an existing installation of WAsP 8.x. To perform an update, run the MSI file.

Version 8.03.0020

Bugs fixed

• Source file trace reacts to summertime (daylight saving time) when opening an existing workspace.

Version 8.03.0018

Bugs fixed

• Exporting a resource grid to WRG or WWR format was inoperative in 8.3.0016.

Version 8.03.0016

Bugs fixed

• When exporting a resource grid to WRG or RSF format, if the Total Weibull-A value is between 9.994 and 10.00, then the written value will be too long and cause column concatenation.
• The dongle device drivers may not be installed correctly in some circumstances.
• The instructions in the licence manager perhaps indicate that Rikke will give out a free licence if you email her (wrong!)

Version 8.03.0015

New features

• It's possible to open and use "Weibull-only" OWCs (without histograms)
• Other non-standard *.tab file formats can now be used to open OWC's
• Resource grids can be exported to a new XML-file format
• In addition to 'locking' the remembered file paths for all types, you can now opt to use the current workspace path
• There's a new script which makes an HTML resource grid report
• The import of binary format map files is again supported
• The path for scripts folders can now be set in the options window
• The palette library can accept Surfer *.clr files for import
• When trying to save a workspace to a read-only file, the program is more helpful than before
• If a hierarchy member is going to be replaced by a move or insertion,  you can choose to move it automatically to the workspace level
• The wind farm report scripts have been updated to include sectorwise U
• Updated help file
• Updated script collections
• A new utility script calculates and exports all resource grids in a workspace
• A new site effects export script dumps an ASCII file of results as shown in the TS window
• A new report script reports the site effects for a turbine site

Bugs fixed

• An error arises when deleting a selected palette file
• Some labels in the OWC Wizard are confusing
• Resource grid results are discarded immediately when they become 'dirty', instead of remaining available for view/export
• Re-importing a wind atlas from file (because it changed on disk) can make it uncalculatable
• If one file previously-imported file is detected as having changed, all other subsequent ones are (perhaps wrongly) treated the same
• Export to file menu item is always disabled for sites, but always visible anyway
• Moving a roughness rose between hierarchy members does not change its associated site for calculations
• If the map view window is opened to a maximised state, the map is not itself maximised correctly
• The wind farm wake effect calculations may crash in case of "zero-sectors"
• If you try to export a WRG file when the results aren't ready, then an error arises
• Trying to import a version 7 object to the wrong kind of parent hierarchy member causes a nasty error.
• No units information for Azimuth resolution in BZ model in configuration editor leads to confusion
• WAsP does not recover from exernal launch to open a binary map file
• Users can edit parameter names in parameter editor window
• Resource grid does not obey 'calculate automatically when needed'
• The wrong vector map in a wind farm report for second wind farm in projects with two wind farms
• Report fails on turbine without power-curve. TS and WF reports don't work without associated WTG
• You can collapse the workspace hierarchy member in the tree
• Wasp Options panel – adaptation tab not refreshing itself correctly
• Wind Farm Power Curve may have incomplete speed range
• If a script file is deleted or renamed while the program is running, a series of errors occurs
• Text color behaving wrongly in the configuration editor window
• Toolbars cannot be moved even though they have a handlebar
• If the hierarchy member names are too long, you can't see the time left for calculations in the progress indicator
• Hierarchy expansion and collapsing should be disconnected from double-clicks in tree.
• The site calculations will cause a complete crash if the Azimuth resolution is set to between 1 and 5
• WAsP does not recover from DDE launch of binary map file
• Resource grid report should show AEP in MW/GW/TW, not full numbers
• Temporary licences don't work with dongles
• Wind Farm Power Curve table may have a too limited speed range