|
|
WAsP the Wind Atlas Analysis and Application Program |
|
|
WAsP the Wind Atlas Analysis and Application Program |
This list of known issues relates to the newest versions of the WAsP programs only. You may also check the FAQ's for more information on program specifications and limitations. For a list of known issues related to version 7.3 of WAsP click here. For a list of known issues related to version 8.4 of WAsP click here.
Description: An image captured from "Virtual Globe" may erroneously be turned.
Users affected: Users applying old versions (version 4.3 and older) of
Google Earth.
Details: An image framed and captured from "Virtual Globe" (Google Earth)
may erroneously be turned when appearing in the spatial view in WAsP 10.
Fix: Virtual Globe (Google Earth) should be kept updated
to the latest version.
If you have not allowed Windows to upgrade Internet Explorer from version 6, and have installed the Yahoo! toolbar, then you may sometimes experience problems when launching HTML reports. The window to display the reports will not display correctly. To work around this problem, make sure that you have Internet Explorer open before invoking a report.
Description: Bad interpretation of uniform roughness when specified by
a very short roughness-change line.
Users affected: All.
Details: In the rare cases where a uniform roughness length is specified by
a very short roughness change line, with the two roughness values being equal,
the roughness may be misinterpreted. The roughness may wrongly be taken to be the height-contour
elevation (in case of a combined height-contour/roughness-change line) or simply
zero if the line polyline or polygon is seen under a very small
angle from a point of interest (met. mast, tubine
site or reference site). In WAsP 8 the error may lead to the calculation of a
wrong roughness rose, in WAsP 9 it may cause the program to freeze when
attempting to evaluate site effects for a point of interest.
Workaround: When specifying an over-all uniform roughness,
add a
roughness change line running along the border of the elevation map, with
Roughness1 = Roughness2 = all-over roughness value.
Description: Non-standard air densities cannot be
treated explicitly. Issue #420
Users affected: All.
Details: No possibility to specify the air density explicitly for a single turbine or for a wind farm.
Power densities are therefore calculated for standard conditions only. The
sample wind turbine power curves are specified for standard conitions only.
Workaround: Power productions can be calculated for the actual site air
density by obtaining from the wind turbine manufacturer a power curve
which is valid and optimized for the actual average site air density, and use that instead of
a standard-density power curve.
Fixes: Wind turbine power curves containing multiple air density information will be introduced in a
future version.
Description: Low land roughness and water roughness confusion. Issue
#885.
Users affected: All.
Details: Non-zero roughness lengths below or equal to 0.0005 may be interpreted by
WAsP as water.
Workaround: Never use land rougnesses below or equal to 0.0005 m in a map. Doing so
may cause the roughness rose calculation to confuse land with water. This can be
revealed by inspecting the roughness rose looking for roughness lengths of zero.
For water areas there is no change: you should always set the roughness value to
0 (zero) in WAsP.
Fixes: This issue will be fixed in a future version.
Description: Break-down of lengthy digitization operations. Issue #423.
Users affected: All.
Details: When performing lengthy on-screen digitizations of height contours/roughness lines on top of a background bit-mapped map image, the process may sometimes lock up, leaving the map display window empty, and also sometimes affecting the functioning of the operating system. The cause seems to be limited assigned graphical memory in the
Windows operating system.
Workaround: The problem may be avoided by at suitably regular intervals saving the map digitized so far, followed by closing down and restarting the map editor, and then continuing the digitization
process.
Fixes: Will be fixed in later version of the map editor by using an alternative graphical drawing technique.
Description: Printing the displayed map image may fail for some
printer types.
Users affected: All.
Details: For some printer types (new color printer types?), the actual
image of the vector map + various editing features will not be printed only
the header text. (The reason may be that the Delphi-compiler version used to
compile the Map Editor does not fully support some new printer types.)
Workaround: Instead of printing directly from the Map Editor, export the
map image to a graphics file, and manually order that file to be printed.
Fixes: Will be fixed in a later version of the map editor by using a
newer compiler version supporting new printer types.
