Professional Documents
Culture Documents
Publication date:
2014
Document Version
Publisher's PDF, also known as Version of record
Citation (APA):
Ott, S., & Nielsen, M. (2014). Developments of the offshore wind turbine wake model Fuga. DTU Wind Energy.
DTU Wind Energy E, No. 0046
General rights
Copyright and moral rights for the publications made accessible in the public portal are retained by the authors and/or other copyright
owners and it is a condition of accessing publications that users recognise and abide by the legal requirements associated with these rights.
Users may download and print one copy of any publication from the public portal for the purpose of private study or research.
You may not further distribute the material or use it for any profit-making activity or commercial gain
You may freely distribute the URL identifying the publication in the public portal
If you believe that this document breaches copyright please contact us providing details, and we will remove access to the work immediately
and investigate your claim.
Developments of the offshore
wind turbine wake model Fuga
Department of
E Report 2014
Wind Energy
January 2014
Abstract This is the final report of the project entitled Risø DTU Modelling Services
carried out by DTU Wind Energy (formerly known as Risø National Laboratory) as part
of the Carbon Trust’s Offshore Wind Accelerator Stage 2 under a contract with Carbon
Trust. The project is a follow–up to a Carbon Trust’s Offshore Wind Accelerator Stage 1
project called Linearized CFD Wake models. The earlier project resulted in the development,
implementation and validation of the Fuga model. Fuga is a linearized CFD model that can
predict wake effects for offshore wind farms. The main purpose of Stage 2 is to add more
features to Fuga and turn it into a useful tool for offshore wind farm developers. The new
features consist in
• Flexibility. Including the ability to cope with several types of turbines in the same
project, thus making it possible to predict inter farm interactions. The graphical user
interface has been greatly improved and a number of input/output facilities have been
added.
• Stability effects. The effect of stability has been added through a modification of the
eddy viscosity based on Monin–Obukhov theory. The numerical solver developed in
Stage 1 has been generalized in order to make it deal with the modified equations.
• Meandering. Meandering has been included in the form of a post processing of the
model results that bend and twist the wake centreline. The meandering centrelines are
calculated using a Gaussian process developed on the basis of measured spectra. An
analysis of meteorological data from Horns Rev has been made in order to quantify the
impact of non–stationarity of the wind direction. The results are generalized so as to
account for the uncertainties imposed by a ten minute mean value trend as well as by
the distance between turbines and the met mast.
The old model has been validated against a number of data sets. Some of these tests have
been repeated in order to demonstrate and validate the new model features. Production data
from Horns Rev 1 have been re–analysed using well defined selection criteria for which the
developed uncertainty models apply, and a comparison with data is made. Even if the model
predictions fall within estimated error bars, the model seems to over predict the measured
efficiencies by a few percent.
The model works best for unstable, neutral and light stable conditions whereas the results
for stable and very stable conditions are questionable. We suspect this is caused by a failure
of the numerical solver that becomes progressively more severe as the stability increases.
In no event will the Technical University of Denmark (DTU) be liable for any damage,
including any lost profits, lost savings, or other incidental or consequential damages arising
out of the use or inability to use the results presented in this report, even if DTU has been
advised of the possibility of such damage, or for any claim by any other party.
Contents
1 Introduction 5
2 Flexibility 6
4 Wake meandering 12
4.1 Data interpretation 12
4.2 Turbulent scales 16
4.3 Wake meandering modelling 19
5 Rotor averaging 23
6 Validation 25
6.1 Repeats of old tests 25
6.2 New Horns Rev 1 test 27
7 Guidelines 32
7.1 Stability input to Fuga 32
7.2 Roter averaging 32
7.3 How to make a climatology with stability 32
7.4 Fuga user interface 35
References 41
3.1 Theory
In the new model atmospheric stability is represented as a change of the eddy viscosity
profile of the approach flow. The eddy viscosity K determines the velocity profile through
the relation
dU
K(z) = u2∗ (1)
dz
Following the ’simple’ philosophy we assume that the eddy viscosity is unaffected by the
presence of a wake. Measurements in wakes show increased levels of turbulence, but the
length scale is decreased at the same time so that the effect on K seems to be limited.
The buoyancy term in the momentum equation is ignored. This eliminates the need for
a (potential) temperature equation. A temperature equation coupled with the momentum
equation via a buoyancy term would produce solutions that exhibit gravity waves. It is likely
that gravity waves can have interesting effects under very stable conditions, e.g. when the
turbines excite standing waves in the farm. This has been observed in the lee of islands with
a small mountains on them, where it causes the wind to speed up instead of slow down. It
would not have been very difficult to include such buoyancy effects, but since they are not
likely to be of much importance, except perhaps for some very rare cases, we choose to keep
things as simple as possible and neglect the coupling via buoyancy. Buoyancy is therefore
only modelled indirectly through the eddy viscosity K. In the old model the eddy viscosity,
K, was set equal to κu∗ z, which is its value in a flat, homogeneous terrain (such as an open
sea) under neutral, barotropic conditions. For non–neutral conditions we will use the eddy
viscosity dictated by Monin–Obukhov (M–O) similiarity theory, Monin and Obukhov (1954)
(see also Monin and Yaglom 1975).
M–O theory introduces the Monin–Obukhov length scale L defined as
T u3∗ T u2∗
L=− = (2)
κghwθi κgθ∗
p
where T is the absolute temperature at the surface, u∗ = −hw0 u0 i is the friction velocity,
g is the acceleration of gravity and θ is the potential temperature and θ∗ = hwθi/u∗ . L/u∗
is a corresponding time scale and θ∗ is a temperature scale. When these scales are used to
write the equations in non–dimensional form a small miracle happens: the equations are the
same no matter what L is! It should be noted that ’the equations’ are the Navier-Stokes
equations in the Boussinesq buoyancy approximation and without the Coriolis force. The
use of the eddy viscosity concept is sometimes also called the Bousinnesq approximation,
but that assumption is not necessary to derive the theory, nor do we need to postulate any
closure. We are, in other words, talking about equations that have fully realistic turbulent
solutions. In flat terrain it gets even better because the boundary conditions for the mean
fields become independent of L too. As a result the mean velocity profile must have the form
U (z) = u∗ (f (z/L) − f (z0 /L)) (3)
where f is a universal function that can be determined from measurements. It turns out
θ∗
hθ(z)i = T + (log z/z0 − ψh (z/L) + ψh (z0 /L)) (8)
κθ
There is a simple relation between temperature and potential temperature:
θ(z) = T (z) + g/Cp z (9)
where T (z) is the absolute temperature at height z and Cp is the specific heat of air at
constant pressure.
In M–O theory stability varies with height. Near the ground the profiles are dominated
by logarithm and close to neutral while the ψ functions become more an more important
as the non–dimensional height ζ ≡ z/L increases. In this respect M–O theory differs from
the once very popular Pasquill (1974) stability class system, where stability is independent
of height. For wind turbines zhub /L would be a relevant stability measure, but since the
hub height does no vary very much for offshore turbines we follow Gryning, Batchvarova,
Brummer, Jørgensen and Larsen (2007) and use 1/L to define stability classes (see table 2
in this report).
In the new mode the look–up tables have three entries: kz0 , β and ζ0 ≡ z0 /L. The old
model had only two (kz0 and β, see Ott et al. 2011). The extra dimension of the tables
make them considerably more voluminous.
M–O theory assumes equilibrium with constant fluxes that do not vary with height. For
offshore wind farms there could be a problem because non–neutral situations often corre-
sponds to situations that are created by a temperature difference between sea and land.
If the wind blows from land to sea and the land is warmer than the sea then the sea will
cool the air and create a stable layer with a capping inversion that grows very slowly with
the distance from shore (the fetch). While the stable layer cools it approaches a neutral
layer, and the assumption of equilibrium could be violated. Lange, Larsen, Højstrup and
Barthelmie (2004) argue that this seems to be the case for the Nysted wind farm. Cold air
on a warm sea will of course create an unstable layer that also decays to a neutral layer. The
stability over open sea thus tends to be neutral, although sea temperature differences over
long distances can make stability deviate from neutral and radiative cooling from clouds
can create convection. Sathe, Gryning and Peña (2011) analysed met data from Horns Rev
and found that unstable conditions are much more common for NW winds than for SW
and explains it as caused by the general N–S gradient of the sea temperature. Stability
generated in this way should be similar to stability over a land surface, whereas stability
generated by temperature differences between land and sea is probably more complex. A
further investigation of this is needed, but this falls outside the scope of the present project.
2 ψ (z /L) is usually small and the term is often neglected.
h 0
(1 + 5.0 ζ) for ζ > 0
φm (ζ) = (11)
(1 − 19.3 ζ)−0.25 for ζ < 0
(1 + 7.8 ζ) for ζ > 0
φh (ζ) = (12)
(1 − 12 ζ)−0.5 for ζ < 0
The uncertainty of these profiles is considerable, especially for strong stability where not
much is known for values of z/L larger than about 1. We are therefore in trouble when
zhub > L > 0. Very stable conditions with L less than about 100m are therefore out of
Fuga’s reach. It should be noted that the boundary layer depth generally decreases with L
and for extreme stability the boundary layer may not even reach up to the turbine rotors,
and the surface layer will be even more shallow. In such situations the shape of the wind
profile will depend on many factors such as the sea–land effects mentioned above, effects of
baroclinity, the presence of a low level jet etc. It therefore becomes more and more impossible
to maintain the assumption of a universal and predictable behaviour as stability increases.
The fluxes of momentum and heat that go into the definition of L can be measured
directly with a sonic anemometer. In case sonic anemometer data are not available L can
be estimated from wind and temperature profiles. Over a sea surface stability is driven by
the air to water temperature difference. It is therefore important to have measurements
of temperature in the water as well as in the air. In principle two air temperatures taken
at different heights could also work, but the difference is so small that it easily becomes
very inaccurate. It is therefore essential that offshore met masts include water temperature
measurements. L can be estimated from ten minutes values of air and water temperatures,
a wind speed, current and an estimate of the surface roughness. We will assume that the
current is negligible and obtain the surface roughness from Charnock’s (1955) relation:
z0 = Ac u2∗ /g + Bc ν u∗ (13)
where Ac is the Charnock constant (following Peña and Gryning (2008) we use Ac = 0.012),
ν is the molecular viscosity, and Bc = 0.12, Grachev and Fairall (1996). A second term
has been added in order to accounts for the limit of laminar flow at very low wind speeds.
Using M–O profiles we then have enough equations to determine L. In general the equations
must be solved numerically, but for near neutral conditions there are simplifications. From
observations of wind speed U taken at height zu , air temperature ta taken at height zt and
sea surface temperature ts we can form a so–called bulk Richardson number Rb :
gzref (θ(zt ) − Ts )
Rb = (14)
Ts U 2
where zref is a reference height of our choice - its only purpose is to make Rb non–dimensional.
Inserting profile functions into (48) we find the following relation
(log zu /z0 − ψm (zu /L))2
zref /L = Rb (15)
log zt /z0 − ψh (zt /L)
For near neutral conditions we have zt /L ∼ zu /L ∼ 0 so that we are allowing us to drop ψm
and ψh . Using a good guess for the surface roughness, say z0 = 0.1 mm, we then arrive at
∂u0 ∂ ∂u1 ∂K
u0 ik1 u1 + w1 = −k2 K u1 + K + ik1 w1 − ik1 p1 + f11 (17)
∂z ∂z ∂z ∂z
∂ ∂v 1 ∂K
u0 ik1 v 1 = −k2 K v 1 + K + ik2 w1 − ik2 p1 (18)
∂z ∂z ∂z
∂ ∂w1 ∂K ∂w1 ∂p1
u0 ik1 w1 = −k2 K w1 + K + − (19)
∂z ∂z ∂z ∂z ∂z
∂w1
ik1 u1 + ik2 v 1 + = 0 (20)
∂z
where k2 = k12 +k22 . The difference is that K now depends on stability as described in section
3.1. The boundary conditions are:
u(k1 , k2 , z0 ) = 0
v(k1 , k2 , z0 ) = 0
w(k1 , k2 , z0 ) = 0
u(k1 , k2 , zi ) = u0 (zi )
v(k1 , k2 , zi ) = 0
w(k1 , k2 , zi ) = 0 (21)
∂ K ∂
= (25)
∂t κu∗ ∂z
The numerical solution to the linearized equations is the Achilles heel of the model. It
was only with great difficulty we managed to solve the equations for the neutral case, and
from start there was no guarantee that it would work for all stabilities. The problem is
that the equations have particular solutions that increase or decrease extremely fast, and
finding the well behaved linear combination that solves the problem is like finding a needle
in a haystack. The problem becomes less severe when K is large. This happens on the
unstable side which is therefore quite benign. On the stable side, however, K gets smaller
and smaller as the stability increases. It was therefore expected that the numerical solution
would break down at some point, but hopefully only at very strong and rare stabilities. The
first expectation came true, but unfortunately the solutions seem to misbehave even at quite
moderate stabilities. It was not the intention to develop new numerical solution methods in
the present project, but a few ideas were tried none of which lead to an improvement. This
problem is something that needs to be looked at in the future.
4D fields
Weather
Model world
Measurements Idealized flow
Met mast Homogeneous
SCADA Stationary
The diagram illustrates the various ingredients that go into the validation of a wake
model. We have the real world with its complex fields (velocity, temperature etc.) and
complicated interactions. We don’t have full access to the real world, but have to be make
do with measurements such as met mast data and SCADA data. These are essentially point
measurements and we have to make some kind of interpretation in order to fill the gaps and
create an idealized model world which our wake model can work with. In the model world
the fields have to be statistically stationary because otherwise we cannot make a Reynolds
decomposition and therefore we cannot apply a RANS model. Horizontal homogeneity is
also a necessary assumption in our case. Once we have decided how to interpret the data
we can make model predictions which finally can compared to data. Strictly speaking, you
cannot be compare directly to the real world which remains a bit on the sideline in the
diagram. If the comparison is good there are two possibilities: either the data interpretation
and the model are both correct or they are both wrong. Two wrongs can make a right, and
this may if fact occur if the data interpretation is incorrect and the model is tuned to make a
good comparison. It is therefore necessary to discuss data interpretation. In order to do this
in a simple way we will make two different interpretations and work out the consequences
for the data comparison. We will also focus on the wind direction because wake effects are
very sensitive to this parameter. Similar considerations can be given to other parameters
such as wind speed and stability measures, but the wind direction has the largest impact.
The traditional interpretation of met data is to regard each ten minutes period as be-
longing to a statistically stationary time series with (abstract) mean values equal to the
corresponding ten minutes averages. In figure 1 this corresponds to the black, piecewise con-
stant curve. The implication is that a single mean value of the wind direction is assigned
285
q @degD
280
275
270
t @sD
600 1200 1800 2400 3000 3600 4200 4800 5400 6000
Figure 1. Green: wind direction time series. Black: mean value, traditional interpretation.
Red: mean value, alternative interpretation.
every ten minutes and used as input to the model. This of course does not make the average
wind direction equal to the ’true’ mean wind. We could shift the ten minutes periods by e
few minutes and get different mean values with the same data. We will therefore investigate
the implications of making a more realistic, alternative interpretation.
The alternative interpretation is illustrated by the red curve. Here the mean value is
changing continuously in time in a piecewise linear manner connecting the ten minutes
averages. This mean that each ten minutes period corresponds to a range of mean values
depending on the slopes of the linear pieces. Instead of feeding the model with one wind
direction for each period, we should feed the model with a range of values distributed around
the observed average value. In other words, we are still treating the model world flow as
statistically stationary, but allow more variation of the wind direction input than in the
traditional approach.
Figure 2 shows a histogram of measurements of ∆θ, the difference between consecutive
ten minutes averaged of the wind direction. The red dots show a fit to an exponential
distribution:
a1 ζ0 + b1 u∗
β= (27)
1 + a2 ζ0 + b2 u∗
The values of the fitting constants are listed in Table 1. These values are default values in
Fuga. They could be used tentatively for other locations than Horns Rev, even if site specific
values based on local measurements are to be preferred.
We need the distribution Pδθ of the variable δθ ≡ θ − θ where θ is the wind directions to
be used as model input and θ is the observed ten minutes average wind direction. In figure
1 δθ represents the difference between the red line and the black line. Each linear piece of
the red line corresponds to an interval of mean values with
−|∆θ|/2 < δθ < |∆θ|/2 (28)
Thus all the flow cases corresponding to the column around ∆θ in the histogram in figure 2
should be distributed evenly on this interval. In terms of probability this can be expressed
as
4000
3000
f HDqL
2000
1000
0
-15 -10 -5 0 5 10 15
Dq
Figure 2. Histogram of ∆θ, the difference between successive ten minutes averaged of the
wind direction. Data were from met mast M7 located to the east of Horns Rev 1. The red
dots is a fit to an exponential distribution.
P∆θ (∆θ) d∆θ for −|∆θ|/2 < δθ < |∆θ|/2
|∆θ| dPδθ (δθ) = (29)
0 otherwise
Figure 3. A slide showing wake model results averaged over a narrow wind direction bin.
Figure 4. The blue line corresponds to the assumed wind direction interval seen at distance
X from the mast.
t 1 1 t
P∆θ (∆θ) d∆θ for T − 2 |∆θ| < δθ < |∆θ| 2 + T
|∆θ| dPδθ (δθ) = (33)
0 otherwise
where t = X/U and T is the averaging time (e.g. ten minutes). Inserting (26) into (33) and
integrating yields
n o
β 2β|x| 2β|x|
2
Γ(0, 2t/T +1 ) + Γ(0, 1−2t/T ) for t < T /2
Pδθ (x) = n o (34)
β Γ(0, 2β|x| ) − Γ(0, 2β|x| )
for t > T /2
2 2t/T +1 2t/T −1
kinetic energy. The high peak at around 10−6 Hz is due to diurnal variations and is part of
a big ’mountain’ of low frequencies. Although these slow fluctuations represent almost all
the kinetic energy, they effectively just determine the mean wind speed and direction in any
given ten minutes period, and we would not normally refer to this as ’turbulence’. At slightly
higher frequencies we have the fluctuations that can make the wind direction change over
10 minutes, which were discussed and analysed in section 4.1. These variations are caused
mainly by mesoscale mechanisms such as the passage of weather systems, convection cells,
gravity waves or clouds. Near the surface this mainly affects horizontal motion are mainly
horizontal even if the flow as such is not two dimensional. Lindborg (1999) analysed long
range spatial velocity correlation data derived from airplane flights and saw two ranges. For
low wave numbers k < 2π/500km) the spectrum varies as k −3 which is due to an enstrophy
cascade that represents true 2D behaviour. For larger k in the range 2π/30km–2π/500km
the spectrum varies as k −5/3 , which could in principle be caused by a 2D energy cascade,
but Lindborg argues against this and prefers to interpret it as 3D behaviour caused e.g. by
gravity waves which can also produce such a range. When in figure 6 the local maximum
at ∼ 10−2 Hz is taken to divide ’2D’ from ’3D’ behaviour, the ’2D’ should be taken with a
grain of salt. Even if the motion is mainly horizontal the flow a mixture between 2D and 3D
behaviour. The next blob marked ’meandering’ represents motion that takes place ’on top
of’ the drifting mean wind. In figure 1 it is contained in the excursion of the green curve
from the red curves. These scales are responsible for the distortions of the wake centrelines
that are referred to as meandering. We could characterize the ’meandering’ eddies as large
enough to move a cross section of the wake as a whole, yet small enough the make the
centreline wiggly–waggly. Still smaller scales (larger frequencies) represent 3D eddies that
are comparable in size with the wake cross section but too small to contain it. This regime is
marked ’scrambling’ because it represents eddies that make a lot of mess by moving around
parts of the wake. Modelling the effects of this is, to say the least, not straight forward, and
today it can only really be done with large eddy simulations. Finally, we have the eddies
that are much smaller than the wake cross section. They only stir the wake locally and cause
momentum to spread in diffusive manner. In this way they tend to smooth out the mess
created by the slightly larger eddies, but they never really succeed in doing so. It is only the
effect of the smallest eddies that can truly be represented by an eddy viscosity.
The main features of the spectrum shown in figure 6 are common to datasets from mid
latitudes. The Australian dataset studied by Ayotte, Davy and Coppin (2001) shows similar
trends. In general the high frequency, 3D part is more site specific than the low frequency
2D part. The 3D turbulence is mainly created by surface friction and the turbulent kinetic
energy is proportional to u2∗ . The level therefore depends on the the wind speed (at 10m, say),
but also on terrain since u∗ increases with increasing roughness (for a fixed U ). Therefore
2D
3D
en 2011
there is generally more turbulence in this part of the spectrum for onshore sites than for
offshore sites. Larsén, Vincent and Larsen (2012) found that the low frequency mesoscale
part, is very similar from site to site, even from onshore to offshore sites. Moreover, the low
frequency part of the spectrum does not seem to depend on stability nor on the average wind
speed. This makes sense if we think of phenomena such gravity waves, clouds or convection
cells which can be transported around by the main wind without being dynamically coupled
to it.
Eddy viscosity can only truly represent the smallest eddies, but for a realistic RANS
model the eddy viscosity must represent a larger part of the turbulence. It could be argued
that the result of the action of ’scrambling’ eddies work a bit like viscose diffusion when a
time averaging is applied. As we go to larger scales, the eddy viscosity becomes less and less
realistic and we can ask ourselves whether we should consider the larger scales as described
by the model. If we go to the limit and include all scales, we end up with a model describing
something like one year averaged wakes. Depending on the wind rose, the wakes would
spread out from the turbines in all directions and the model would not be able to handle
shadow effects at all. We are therefore forced to exclude too large eddies from the model
world. This means that we can only predict what would happen if the large eddies were not
there. Comparison with data from the real world then becomes complicated by the fact that
large eddies do exist in the real world. It is also difficult to say exactly where we should draw
the line between ’large’ and ’small’ eddies. We could perhaps answer such questions if we
0.6
0.4
fvHu*tL
0.2
0.0
Figure 7. Dots: normalized autocorrelation function of v obtained from simulated wind fields.
Red line: fit.
This simulation technique works well, but it uses much computer resources both in terms
memory and cpu time. It is therefore usually run on a cluster. but Fuga is supposed to run
1.2
1.0
0.8
m @-D
0.6
0.4
0.2
0.0
-0.01 0.00 0.01 0.02 0.03
1•L @m D -1
Figure 8. The µ parameter as function of the inverse Monin–Obukhov length. Blue is for the
v component and green is for the w component
0.08
0.06
l @m-1 D
0.04
0.02
0.00
-0.01 0.00 0.01 0.02 0.03
1•L @m D-1
Figure 9. The λ parameter as function of the inverse Monin–Obukhov length. Blue is for the
v component and green is for the w component
Figure 10. The seven points used in the seven point method
A more accurate can be improved by using the following seven point method instead of a
one point method:
Z R Z 2π 5
1 1 X p
dr dθ F (r, θ) ≈ πR2 F (0, 0) + F ( 2/3R, jπ/3) (47)
0 0 4 8 j=0
The formula is valid if F is a polynomial in y = r cos θ and z = r sin θ with degree less
than 5.pIt is most practical to arrange the seven points in three different heights: zhub and
zhub ± 2/3R. The output from the model is restricted to certain levels that jump about
10% from level to level. An interpolation is made when evaluating U at the three desired
heights, which spoils some of the accuracy, but the method is still definitely better than the
one point method.
Thrust curves are normally calculated assuming a logarithmic profile or measured indi-
rectly by strain gauges placed on the tower. The thrust coefficient is then obtained using the
0.70
0.60
0.50
0.40
1 2 3 4 5 6 7 8 9 10
a Row number
1 270+-2.5 Fuga
270+-7.5 Fuga
270+-12.5 Fuga
0.9
270+-17.5 Fuga
270+-2.5 Data
0.8 270+-7.5 Data
Normalized prod.
270+-12.5 Data
270+-17.5 Data
0.7
0.6
0.5
0.4
1 2 3 4 5 6 7 8 9 10
Row number
b
1 270+-2.5 Fuga
270+-7.5 Fuga
270+-12.5 Fuga
0.9
270+-17.5 Fuga
270+-2.5 Data
0.8 270+-7.5 Data
Normalized prod.
270+-12.5 Data
270+-17.5 Data
0.7
0.6
0.5
0.4
1 2 3 4 5 6 7 8 9 10
Row number
c
Figure 11. Comparison of Fuga results with data from the Horns Rev I wind farm. U=10m/s,
z0 =0.1mm, a: the old model. b: new model without meandering or filter. c: new model with
meandering and filter.
Table 2. Stability classes used for the test and input used for the 9±1m/s bin.
A new test was prepared for the Horns Rev 1 data set. AMOK was used to extract stability
information from met mast M7 data together with SCADA data for turbine production. The
wind direction was measured by a wind vane (z = 60m) and the velocity was measured by
a cup anemometer (z = 70m) both on the met mast. M7 is located 6km to the east of the
farm, which is further away from the farm than both M2 and M6, but the data from M7
are more reliable. Data was binned according to wind speed (2m/s bins), wind direction (5
degree bins) and inverse Monin–Obukhov length binned in the classes defined in Gryning
et al. (2007), see Table 2. The table also contains the bin averages used for model input. Data
for U = 9 ± 1 m/s were selected for evaluation. The very stable cases were omitted. Only
wind directions where the met mast was clear of the wake from the farm were used. Wind
directions between N and NE are very rare, hence useable wind directions are limited to bins
between 45 degrees and 240 degrees. Production data were selected for each turbine and data
were rejected unless all upwind turbines were running. The average turbine production was
therefore based on different data for each turbine since down wind turbines were allowed
not be running. The production efficiency was calculated using the average production of
all the running, unobstructed turbines as reference. For some wind direction bins there were
little data or none at all. For an individual turbine the spread of the production data in a
bin is about 30% 3 . With between 10 add 100 realizations the error of the mean value is on
the order of 3–10%. The error on the production efficiency is dominated by the estimate of
the undisturbed production, which consists of an average over 8–18 turbines depending on
the wind direction. The uncertainty of this average is lower that for a single turbine, but it
is difficult to say how much lower because the productions from the individual turbines are
correlated. There are also systematic errors such as spatial and temporal changes of wind
speed and stability and coastal effects making the climate inhomogeneous. This suggests an
accuracy of the data of perhaps 5%.
The model was run for all the stability classes except class +3, where the criterion that
z/L < 1 is violated. Three different settings were used: 1) ’raw’ results without meandering
and filtering, 2) with meandering turned on and 3) with both meandering and trend and
spatial filtering. The one point method was used in all cases.
Figure 12 shows results for Class 0 (neutral). The effect of the stochastic meandering can
be seen, but it is not large. This wold perhaps change if the measured σu was used as input
(the model uses the relation σu /u∗ = 2.4). The trend and spatial de–correlation filter has
more impact, perhaps a little bit too much in this case. The overall agreement with data is
fair even if the model over–predicts the efficiency by about 3%.
Figure 13 shows results with both meandering and filtering for all stability classes (except
very stable). The general picture is again that the model over–predicts by 2–5%.
Table 3 shows the mean value of the relative production for those wind direction bins
where enough data exists to allow an estimate of the total production to be made. The
3 All percentages in this section are relative to the undisturbed reference production
Table 3. Mean farm efficiency over the sector 42.5–242.5 degrees where data exist for all
turbines.
Class -3 -2 -1 0 +1 +2
Modelled efficiency 87.2% 86.3% 85.3% 83.1% 81.3% 80.7%
Observed efficiency 83.7% 82.4% 80.8% 79.9% 79.0% 76.0%
difference 3.5% 3.9% 4.5% 3.2% 2.3% 4.7%
1. 1.
0.8 0.8
Farm Efficiency
0.6 0.6
0.4 0.4
0.2 0.2
0. 0.
0 30 60 90 120 150 180 210 240 270 300 330
q
b
0 30 60 90 120 150 180 210 240 270 300 330
1. 1.
0.8 0.8
Farm Efficiency
0.6 0.6
0.4 0.4
0.2 0.2
0. 0.
0 30 60 90 120 150 180 210 240 270 300 330
q
c
0 30 60 90 120 150 180 210 240 270 300 330
1. 1.
0.8 0.8
Farm Efficiency
0.6 0.6
0.4 0.4
0.2 0.2
0. 0.
0 30 60 90 120 150 180 210 240 270 300 330
q
d
0 30 60 90 120 150 180 210 240 270 300 330
1. 1.
0.8 0.8
Farm Efficiency
0.6 0.6
0.4 0.4
0.2 0.2
0. 0.
0 30 60 90 120 150 180 210 240 270 300 330
q
Figure 12. Red dots: observed total farm efficiency for Horns Rev 1. Neutral (C=0) and U =
9 ± 1m/s. Blue line: model predictions. a: without filters. b: meandering filter. c: meandering
and trend filter. d: meandering and trend and spatial filter
1. 1.
0.8 0.8
Farm Efficiency
0.6 0.6
0.4 0.4
0.2 0.2
0. 0.
0 30 60 90 120 150 180 210 240 270 300 330
0 30 60 90 120 150
q
180 210 240 270 300 330
Class -3
1. 1.
0.8 0.8
Farm Efficiency
0.6 0.6
0.4 0.4
0.2 0.2
0. 0.
0 30 60 90 120 150 180 210 240 270 300 330
0 30 60 90 120 150
q
180 210 240 270 300 330
Class -2
1. 1.
0.8 0.8
Farm Efficiency
0.6 0.6
0.4 0.4
0.2 0.2
0. 0.
0 30 60 90 120 150 180 210 240 270 300 330
0 30 60 90 120 150
q
180 210 240 270 300 330
Class -1
1. 1.
0.8 0.8
Farm Efficiency
0.6 0.6
0.4 0.4
0.2 0.2
0. 0.
0 30 60 90 120 150 180 210 240 270 300 330
0 30 60 90 120 150
q
180 210 240 270 300 330
Class 0
1. 1.
0.8 0.8
Farm Efficiency
0.6 0.6
0.4 0.4
0.2 0.2
0. 0.
0 30 60 90 120 150 180 210 240 270 300 330
q Class +1
0 30 60 90 120 150 180 210 240 270 300 330
1. 1.
0.8 0.8
Farm Efficiency
0.6 0.6
0.4 0.4
0.2 0.2
0. 0.
0 30 60 90 120 150 180 210 240 270 300 330
q Class +2
Figure 13. Red dots: observed total farm efficiency for Horns Rev 1 with ±2.5 wind direction
bins. Blue line: model predictions for U = 9 ± 1m/s with 4 meandering repeats per direction,
±2.5 degree rectangular filter and filter for trend and spatial de–correlation. Stability class
ranges from -3 (upper) to +2 (lower)
0.88
0.86
360o mean efficiency
0.84
0.82
0.80
0.78
0.76
Figure 14. Relative production averaged over 360 degree for the seven stability classes.
ζ0 = Ac κ θ∗ /T (48)
In other words, ζ0 is essentially a measure of θ∗ , the temperature scale of the layer. This
is an indicator of stability, but a different one from e.g. 1/L, which is sometimes used. For
model evaluations and Annual Energy Production (AEP) estimates it is important to enter
the right ζ0 . The AMOK tool can be used to convert met mast measurements to estimates
of z0 , L and ζ0 .
Monin–Obukhov theory is not reliable for extremely stable conditions where profiles es-
sentially become unpredictable, and the diabatic functions φm and φh are ill-determined for
values of ζ larger than 1. We recommend not to use trust results for cases where L is smaller
than the hub height, because the underlying theory is not valid.
The shadowing is generally more severe in stable conditions and less severe in unstable
conditions compared to neutral, and things tend to even out when the AEP is estimated,
However, even a small difference could be decisive for the choice of the location of a wind
farm. Unfortunately, the numerical solutions break down for too stable cases and yields
results that we are far too optimistic with respect to wake losses. The present solver4 is not
reliable for ζ0 & +3 10−7 . This corresponds to L ∼ 130m or zhub /L ∼ 0.5.
where P (u∗ , ζ0 , α) is the joint pdf of u∗ , ζ0 and α (the wind direction), and F (u∗ , ζ0 , α)
is a function such as the energy production. The conventional method is to divide the
approximate (u∗ , ζ0 , α) space into bins and approximate F by a function which is constant
over each bin so that
Z Z Z X X
hF (u∗ , ζ0 , α)i ≈ du∗ dζ0 dα P (u∗ , ζ0 , α) Fbin Ξbin (u∗ , ζ0 , α) = Fbin hξbin (u∗ , ζ0 , α)i
bins bins
(50)
where {ξbin } is the set of characteristic functions for the bins. The method works fine as
long as we have enough bins to give a decent representation of F . In our case we need to
make quite large bins in order to avoid that they become half empty, and the approximation
could become inaccurate. We will therefore try to improve the approximation by the use of
chapeau functions. It is best to illustrate the idea with a 1D distribution instead of a 3D.
A chapeau function ∆ is a piecewise linear function of the form
0 for x < a
x−a for a < x < b
∆(x) = b−a (51)
b−x
c−b for b < x < c
0 for c < x
We divide the x–axis into segments by a set of points {xi } and define chapeau functions ∆i
using (51) with (a, b, c) = (xi−1 , xi , xi+1 ). We can use the chapeau functions to approximate
a function F (x) by a continuous, piecewise linear function, viz.
X
F (x) ≈ F (xi ) ∆i (x) (52)
i
Since ∆i (xj ) = δij , the right hand side attains the right values for x = xi and is linear in
between. This is a slightly better than the piecewise constant approximation. For the mean
value we get
The 3D case is similar. We use chapeau functions for the variables u∗ and ζ0 , divide the
two axes at points {u∗i } and {ζ0j } and define 2D chapeau functions as the product of two
1D chapeau functions:
∆ij (u∗ , ζ0 ) ≡ ∆i (u∗ ) ∆j (ζ0 ) (54)
It is natural to use Fourier modes for the wind direction and write F as
∞
X
F (u∗ , ζ0 , α) = Ck (u∗ , ζ0 ) eikα (55)
k=−∞
where φk is a filter that cuts off the infinity sum over k and helps blurring the data. Using
this approximation for F we get
X X
hF (u∗ , ζ0 , α)i ≈ Ck (u∗i , ζ0j ) h∆ij (u∗ , ζ0 ) eikα i φk (57)
ij k
The analysis outlined above was carried out for data from the years 2005-2009. The dataset
contains about 240000 records of ten minutes averages. Wind speed at 20m, temperature at
16m, water temperature 1m below sea level, and wind direction at 68m were used to find
1/L, z0 , θ∗ , and u∗ . Figure 15 is a sanity check where the wind speed at 70m was estimated
est est
using (5) and compared to measurements. The values of the ratio U70 /U70 scatter nicely
around 1.0 with only a small bias of about 2 percent. It is typical that the scatter if largest
in the stable region with ζ = 70m/L > 0.5.
Figure 15. The windspeed extrapolated from 20m to 70m compared to the measured wind
speed at 70m. The green line is the average.
Figure 16. Turbine site selection in Fuga with a) all sites included, b) only sites in the last
wind farm included, and c) all sites included except the first wind farm and phase 2 of the
last wind farm.
The wind-farm layout is specified by a WAsP project file, which includes turbine positions
and heights, site-specific wind climates, and power curves with associated thrust-coefficient
Figure 17 shows the user interface with the atmospheric boundary layer defined in the
lower-left area. The wind speed and direction specified here applies to the selected reference
site. The case list refers to existing linearized CFD solutions, and you may either select one
of these or specify a new combination of z0 , zi and ζ0 . You can use the separate AMOK
program to derive these parameters from wind speed, air temperature and sea temperature.
Methods for directional averaging are chosen in the top-right area of the user-interface
window. Some of these have parameters, like the number of repetitions for wake meander
simulations or the spread of a Gaussian averaging filter. Options for modelling effects of shift-
ing 10-min averaged wind directions and spatial de-correlation between the wind direction
at reference site and turbine sites are always available for the wake meander method. The
simple box averaging and Gaussian averaging filters are available when calculating annual
energy production.
The fourth page, shown in Figure 18, illustrates the wake behind a single turbine. The
coloured plot at the top shows horizontal velocity fields and the chart below shows wind
speed along crosswind, downwind or vertical transect lines defined by the user. Use this
plot type to check linearized CFD solutions or compare solutions for different atmospheric
stability.
The fifth page in Figure 19 displays the combined wake of all turbines with a wind-
speed profiles along a user-defined transect line. In the shown situation, we have chosen a
wind direction aligned with a row of turbines and defined a transect line passing through
the turbine positions. For the wake aggregation the program sorts the turbines after the
projected distance along the wind direction and starts by finding the thrust of the most
upwind turbine. This thrust and the single-wake solution is then used to find the reduced
wind speed at the next turbine position. The algorithm progresses in the downwind direction
until the thrust is known at all turbines, and then it is possible to lookup the reduced velocity
at any position. Lateral turbine displacements, wake centre-line displacement due to wake
meandering, rotor averaging, variable hub heights, and variable thrust-coefficient curves are
taken into account in this calculation.
Figure 20. Wake velocity profiles under unstable (L=100m), neutral and unstable (L=-100m)
atmospheric stability.
The lower panel can also display 2D profiles of wind speed or velocity deficit. The plots
in Figure 20 are combined of three such plots for variable atmospheric stability with a wind
direction only transect line only passing a single turbine. The eddy diffusivity increases with
height and especially in the unstable case we see that the wake is mainly depleted from the
top, so the height of the maximum velocity deficit decreases with distance. The downwind
Figure 21. Normalized power production of the Horns Rev I wind farm at 9 m/s as func-
tion of direction with a) no directional averaging, b) wake meandering, trend in wind speed
and spatial de-correlation of wind direction relative to the centre of the farm, and c) wake
meandering, trend and de-correlation relative to the M7 mast 6 km east of the farm.
Figure 21 shows a polar plot of aggregated power of the Horns Rev I wind farm at a
wind speed of 9 m/s normalized with a hypothetical production without wake effects. The
directions with minimal production efficiency are the ones where the wind blows along rows
of turbines. The three plots show the importance of directional filtering and the distance to
the reference site.
All tables and plots shown in Fuga may be saved to file or copied to the Windows clipboard
via the Fuga file menu. Tables are copied in tab-delimited text format, which is easy to paste
into Excel notebooks. It is also possible to invoke the result table menu and create flexible
tables of wake-reduced wind speeds or power as a function of wind speed and direction with
optional rotor averaging, directional averaging and wake meander simulation. Results are
calculated for individual turbine sites and for wind turbine groups.
The FugaBatch program is a non-visual tool, which do the same calculations as Fuga and
exports these to file. It is useful for sensitivity studies with systematic variation of model
input. The scripting syntax is explained in the Fuga help file and a collection of sample
scripts demonstrate typical uses.
The purpose of Fuga.exe is to demonstrate the method of linearized wake computations by lookup tables (LUTs). Fuga
calls the programs preludium.exe to generate preLUTs and LUTs and trafalgar.exe to calculate single-wake pro-
files. In addition Fuga calculates the combined wake from all turbines in a wind farm and estimates the annual power
production by a method similar to WAsP, however, with wake losses calculated by the Fuga wake model.
l Setting up calculations in Fuga 2
l Result views
l Further information
New in Fuga 2.5
Bug fix:
l Parameters in the wake-meander simulation model were not applied with the correct stability dependence.
l The filtering of the wind-direction dependence of the power output is now calculated as the last step. This cor-
rects a previous method where power was calculated from a filtered wind speed. The correction affects the
'wind direction trend' and 'spatial de-correlation' filters, but not the 'simple average' or 'Gaussian average'
filters.
New features:
l Improved control over wind direction filters modelling sampling effects of power statistics. The filter is pro-
vided in two versions - one for trends in the wind direction signal during sample periods and one for trend
plus statistical de-correlation due to spatial separation between reference mast and turbine sites. The filters
are not only available for the meander-model results but also for the top-hat and Gaussian averaging filters.
l FFT-based filters are also available from the 'Files| save results| result table' dialogue.
l Import of WAsP 11 workspaces.
New in Fuga 2.4
Bug fix:
l AEP calculations sometimes went wrong for projects using turbines with multiple power curves inside the
WAsP workspace, e.g. intended for different air densities. By mistake earlier versions of Fuga always used the
first power curve regardless of the WAsP workspace choice.
l Yet another correction for projects with turbines of different heights. A previous error, corrected in Fuga 2.2,
was incorrect reference velocity at the upwind turbine . The additional error, corrected in Fuga 2.4, was that
the velocity deficit at the downwind turbine sometimes was evaluated at the height of the wrong turbine.
New features:
l Wake meander effects
l Thrust and power optionally evaluated by a rotor-averaged inflow velocity
l Rotor averaging, variable wind direction, and wake meander now also affects AEP calculations and efficiency
for direction plot. Earlier versions only used directional averaging when calculating power performance for a
selected wind case. See how to set averaging options in Fuga GUI and in FugaBatch
l Alternative win64 versions of Fuga and Fugabatch allows Windows 7 users to use more RAM memory.
New in Fuga 2.3
New features:
l Single-turbine and windfarm wake effects also for boundary layers of non-neutral atmospheric stability
l Annual Energy Productions for a specified distribution of atmospheric stabilities
l Graphical display of specified stability statistics
See how to specify non-neutral stability in Fuga GUI and in FugaBatch
New in Fuga 2.2
Bug fix:
l Corrected AEP calculation for projects with turbines of different height. This problem existed in versions 2.0-
2.1 of both main Fuga and FugaBacth - but only with AEP calculations, not calculations for specific wind
cases.
l Corrected selection of tables in wind turbine generator files (*.wtg) with multiple performance tables or equiv-
alent multi-table turbine data in workspace files (*.wwh). The first table in the file was always selected erro-
neously ignoring user preferences.
New features:
l Result table may also be calculated by FugaBatch
l Adjustable colour schemes for single-wake and windfarm wake plots
l Graphical display of turbine-specific wake losses
l Output from preludium.exe and trafalgar.exe redirected to log files
New in Fuga 2.1
Bug fix:
l Corrected spreading in Gaussian filter used for directional averaging
New features:
l Speed optimizations in GUI - mainly by avoiding repeated calculations and interrupting time-consuming plot-
ting
l Optional speed and length scales plus coastline in the windfarm view
l Optional deactivation of sites or turbine groups by right-clicking objects in the workspace hierarchy
l Screening of incorrect far-field flow results due to lack of single-wake data
l Optional coarse-resolution plotting in wind-farm view (which is faster)
l Optional redirection of FugaBatch output to log file
New in Fuga 2.0
New features:
l Support for complex projects with multiple turbine types and variable turbine heights
l Import of WAsP workspace files, also in scripts
l Aggregated results for all turbine groups including nested subgroups
l Zoom in single-wake plot
New in Fuga 1.5
Bug fix:
l Data scanning routine might attempt to access PreLUT information before available. This was probably only a
problem when manually moving content of LUTs folders and thereby changing the Windows file order.
New features:
l Support for 3D wakes, however only in projects with a single turbine type
l Display of vertical wind profiles
New in Fuga 1.4
Bug fix:
l Resolutions of AEP calculations are now identical in Fuga and FugaBatch
New features:
l FugaBatch input is slightly simplified. There is no need to specify wake *.par and *.dat files as these are now
detected automatically.
l Possible to control the resolution for the AEP integral via parameters in fuga.ini
New in Fuga 1.3
Bug fix:
l Arrows next to wind direction and speed input boxes now results in a new calculation
New features:
l New versions of the preludium and trafalgar programs with minor modification to input files. Results are now
produced at the exact hub height.
l Now possible to average the calculated power and wind speed over a range of wind directions.
l A new data export facility is included.
l FugaBatch - a non-interactive mode for scripting of Fuga calculations
New in Fuga 1.2
Bug fixes:
l Improved response to change of wind direction
l Improved data export
l Improved wake modelling by much better versions of the preludium and trafalgar programs
New features:
l Precise positioning of transects in single-wake view
l Wind profile along transect in windfarm-wake view
l Zoom and pan in windfarm-wake view
New in Fuga 1.1
New features:
l First version with a help file
l Import from WAsP windfarm file (including local wind climates)
Setting up calculations in Fuga 2
Fuga 2 needs
l Wind farm layout and site-specific wind climate from a WAsP workspace file
l A boundary layer description.
Available data are presented in drop-down list on the left-hand side of the program window. In the first session these
lists will be empty and the user must click the ‘Add new’ item at the top of each list or in the main menu. This is also
the way to introduce new wind farms and new boundary layer descriptions.
Previously, in Fuga 1, you selected the wind farm layout and turbine type independently. To allow for complex wind
farms this information is now read from the WAsP workspace file. Fugabatch is still able to read Fuga 1 styled input,
but then the calculations are limited to wind farms with one turbine type only. Read more on differences between
Fuga 2 and Fuga 1
Results in the site-list and wind-farm-wake views depend on a reference wind
Workspace data
Wind farm information is stored in WAsP workspace files. Click the ‘Add new’ item at the top of the list to add file or
select one of the previously load workspaces stored in the fuga subdirectory 'WAsP workspaces'.
A workspace can hold several wind farms, which can be organised as nested groups or adjacent independent
projects. Select a turbine group, turbine type and reference site by mouse clicks. Selected objects will be marked by
bold text.
It is possible to temporarily deactivate a turbine site or site group by right-clicking on the object in the workspace
hierarchy. The turbine group called 'Nysted Windfarm' is deactivated in the above image to the right. With only two
groups in the project, a similar selection could have been made by clicking on the 'Rødsand' turbine group.
How to prepare a WAsP workspace
Atmospheric boundary layer data
Select previously calculated wake data or choose ‘Add new’ in the case drop-down list. The names reflect the surface
roughness Z0, inversion height Zi and stability parameter Zeta0, which is surface roughness length divided by the
Monin-Obukhov parameter L.
A new dialog box will pop up if you choosed 'Add new' in the initial drop-down list. In that dialog you select a com-
bination of surface roughness Z0, inversion height Zi and stability parameter Zeta0, which defines that boundary
layer. The parameter defines LUT files, which will be calculated by l preludium.exefor all turbines in the current
project. You can further limit the range of levels, where wake deficit (DAT files) are calculated by trafalgar.exe. Sec-
tion roughness and stability parameters suggests for surface roughness and stability. Typical inversion heights for
neutral atmospheric stability over the North and are something like 400 m. Inversion heights for stable conditions
may be much lower, but bear in mind that Fuga needs a inversion heights higher than the upper tip height of the tall-
est turbine in a project.
The stability parameter Zeta is specified by selecting a value from yet another drop-down list, also included an 'Add
new' option. The values in the list corresponds to existing preLUT directories.
Selecting 'Add new' from the list of stability parameters will invoke a second pop-up menu. This includes a table show-
ing the categorization of Ameya et al. (2011) Wind Energy, Vol. 14, p.767-780. You should not select Zeta0 values
outside this range.
Reference wind
The flow field is defined by a speed and direction at the height of the selected reference site which you select by a
click on the object hierarchy. This can be a turbine site or you could add a reference mast with a different height, say
10-m in the WAsP workspace. Wind at other turbine sites will be corrected by the vertical wind profile only.
Atmospheric boundary layer statistics
single-wake, windfam-wake and other results for a specific wind are calculated for the selected case.
The annual energy production may,optionally, be calculated by a specific boundary layer case applicable at all times
or by a statistically weighted average of multiple boundary-layer cases. When the 'production' tab is activated you will
see this option.
Pressing 'define statistical variation ' will open a file prompt. The present file format is like this but may change in
future version. Having defined a statistical variation you inspect it by selecting 'ABL case Plot' in the 'Production' view.
Result views
Result lists and plots may be exported from the main menu.
Fuga display results in tabulated views on the right-hand side of the program window.
l File overview
l Turbine site list
l Production
l Single wake
l Windfarm wake
A view will be empty if necessary input is missing.
File overview
The files view provides an overview of the data structure. When the structure grows too large it is recommended to
reduce the system by deleting unused subdirectories in the LUTs directory.
It is possible to display input parameters by clicking on turbine and cases. Starting from version 2.2 it is also possible
to display log files containing redirected output whcih in earlier versions was displayed in pop-up DOS windows.
Site list view
The turbine site list displays site location, local wind speed with and without wake effects, electrical power, turbine
efficiency and turbine type. The local wind speed is based on an assumption of a logarithmic wind profile, effects of
orographic or non-uniform surface roughness are ignored in the wake modelling. The power corresponds to the local
wind speed corrected for wake effects. Turbine efficiency is defined as the ratio of actual power and the power cor-
responding to free wind speed.
Before wake calculations the turbine sites are sorted after the wind direction and upwind sites are evaluated before
downwind sites. In this way it is possible to use corrected wind speeds for looking up thrust coefficients at individual
turbine sites.
The steady uniform wind direction assumed in the model is rare in nature. Fuga can average the results over a range
of directions or use its wake meander model. Set a mark in the checkbox above the list to display current averaging
options.
By default the sub-group results include effects of all turbines. Select an individual group in the object hierarchy to
exclude wakes from other turbines.
Production view
This list shows net annual power productions, i.e. the expected production in a typical year corrected for wake
losses. Efficiencies are defined by ratios of net productions and ideal productions without wake effects. Accumulated
results are shown at the bottom of the list, both for all turbines and for sub groups. It is possible to show results for
individual sectors and to compare with the WAsP workspace results.
The Fuga AEP calculation is based on probability-weighted integrals of power productions for all wind speeds and
directions using local wind climates calculated by. Effects of orographic speed up and internal boundary layers are
included in the WAsP generated wind climates. It is just the wake corrections which ignore effects of variable terrain.
This approach is also used in similar WAsP AEP calculations.
By default the sub-group results include effects of all turbines in the set up. Select an individual group in the object
hierarchy to exclude wakes from other turbines.
The single wake window shows the wake of a single wake at the selected wind speed. Local wind speeds are shown at
the status bar at the bottom of the program window when the mouse cursor is moved over the wake display. Clicking
on the wake field will change the position of the below cross profile, which is also indicated by a dotted line in the
wake field display. A more precise positioning of the profile is done by the edit boxes left of the profile view. You can
zoom closer to the turbine position and optionally interpolate the results.
When an edit boxes is focused, the profile position may also controlled by keyboard arrow keys combined with the
shift or ctrl key.
Clicking on the radio buttons to the left will change the direction of the chosen transect profile. Use the list below to
select a level for horizontal profiles. The check boxes at the lower-left corner controls whether to normalise distances
in the X-Y plot and whether to plot the wind profile or the wake velocity deficit. Automatic plot scaling is controlled
with the plot options.
The plot scaling is automatic by default. You may also specify axes minima and maxima, this is useful when com-
paring cross profiles at different downwind positions.
Windfarm wake view
.
The wind farm wake window shows the wind field in the entire wind farm at the selected wind speed and direction.
The averaging options, displayed by a mark en the checkbox at the top, will only affect the efficiency for direction
plot.
Zoom and pan
It is possible to zoom in or out with the spin edit box above the plot. The zoom factor is calculated as 2i/5 where i is the
value in the spin edit box. Sometimes it is best to edit this number directly as it takes a while to calculate the plot and
this is done each time the zoom factor change. An alternative zoom method is to press the ctrl key while scrolling the
mouse wheel. Dragging the mouse with the ctrl and left mouse keys pressed will pan the wind-farm view.
Speed up options
Plotting the combined wind field of a big wind farm can be slow. The 'WF plot by FFT' option, i.e. acceleration by fast
Fourier transforms, will speed up the plotting of a big project but not of a small one. It should not be used it in
combination with positive zoom, as wakes from turbines outside the view becomes invisible. Use the 'Block WF plot'
option to temporarily prevent any wind-farm plotting.
Adjust the view
The size of the plot depends on the main window size. Plotting is time consuming because the flow has to be eval-
uated everywhere. Adjusting the resolution, shown in number of pixels, will speed up the process. Setting a res-
olution of zero will imply that Fuga interpolate in the single-wake results even for plotting - this makes most sense
with a high zoom factor Checkboxes are used to add speed- and length scales plus coastline to the plot. It is also pos-
sible to adjust the colour scheme. 'New defaults' are recommended for projector displays and 'X-ray' is best for B&W
printer output.
Measure a distance
The approximate distance and direction between two sites can be measured by dragging with the left mouse-key
pressed. Press shift on the keyboard while releasing the mouse key to keep the measure on the screen.
There are two ways to select a turbine site group or individual site
1. by selecting a site in the drop-down list in the 'efficiency for direc-
tion' pane
2. by clicking on the map above. Setting a checkmark at 'snap to tur-
bine position' will move the reference point to the nearby turbine site
Use the drop-down list in the top-left corner to select the height above the
surface. Click the button called 'accurate position' to gain full control of the
reference point, e.g. to select a point directly downwind a specific turbine
Efficiency plot
The chart below the main plot shows the power efficiency or local speed reduction as function of wind direction.
These values are normalized by the undisturbed wind speed and production of a turbine without wake effects. The
direction is indicated to the left of the plot when the cursor is moved over the plot.
Fuga 2
Fuga 2 is designed for complex wind farms and wind-farm clusters with mixtures of turbine types. The Pre-
ludium/Trafalgar data structure is maintained, although we sometimes apply multiple folders for a single turbine if
LUTs and wake data are needed for several hub heights and atmospheric stabilities. The complex wind farm layout is
read from the WAsP workspace file (*.wwh). With this file format it is possible to organize turbine sites into multiple
site groups nested into as many sub groups as needed. Each group, and even the individual turbine site, can have a
specific turbine generator and hub height.
Results are aggregated for each turbine group. Effects of turbines in neighbouring groups are included by default,
but you can also model a turbine group without wake effects from neighbouring groups.
Averaging options
Averaging options affects calculations in
l exported result tables
l turbine site list
l production table (new in Fuga 2.4)
l windfarm-wake 'efficiency for direction' plot (new in Fuga 2.4)
Averaging options does not affects calculations in
l single-wake results
l windfarm-wake main plot
l windfarm-wake horizontal profile
l windfarm-wake vertical profile
One reason for these limitations is that the speed-optimized wake meander model only simulates wake displacements
near downwind turbine positions. The detailed wake trajectory is unknown.
The averaging options appear at the top of the window when applicable. Rotor-averaged wind speed means that the
inflow velocity is evaluated at seven points on the rotor and a weighted average is used for evaluating thrust and
power. Without this option the inflow is evaluated at the rotor centre only. The option can be used in combination with
either directional averaging method.
Directional averaging
Fixed wind direction is the basic and fastest method. It may however overestimate the wake centre-line velocity deficit
and underestimate the width of the wake-affected region.
The simple average and Gaussian average methods apply filters on the wind direction, which reduces the wake veloc-
ity deficit and increases the width of individual wakes. The width or standard deviation of these filters is specified in
the input box appearing to the right of the filer-type option. Fuga actually implements two versions of these methods.
The first one is based on the average of repeated calculations with wind directions distributed around a mean wind
direction. The second version is based on wind directions covering the full 360° horizon, and here the filtering is
done in Fourier space after FFT transforming of the raw results. The first version is used for analysing specific wind
situations and the second one is used in context of AEP estimates, where winds from all directions are always avail-
able. Exported results from the result table dialogue can be calculated by either version.
The final method invokes meander simulation. This is based on a stochastic model and results will differ after each
simulation. To improve the uncertainty of the estimates you can repeat the simulation and use mean results. The opti-
mum number of repeats depends on the size of the windfarm, as random variations from multiple turbines tend to
cancel each other. The results for a single turbine will depend on the number of upwind turbines, so uncertainties for
individual turbines will typically vary with wind direction. The same is often true for an wind farm covering an elon-
gated area. Use the drop-down list at the top to select which simulation to display in tables and efficiency plot. The
button to the right of the repeat number selector can be used to repeat the simulations.
A checkmark at wind direction trend will activate an additional directional averaging filter, which models the effects of
variable wind direction during the sample period. The option should be set when comparing Fuga model predictions
to observed turbine performance binned after an observed wind direction. In most cases this wind direction is meas-
ured at a reference mast and not at the individual turbine sites, and in this case it will be relevant also to select the
spatial decorrelation option modelling the lack of correlation in concurrent wind directions at reference mast and
individual turbine sites. The averaging effect decreases with wind speed and increases with distance between individ-
ual turbine sites and reference site. A project met mast will be an appropriate reference site. Open the workspace in
WAsP to insert a project reference mast and select it by a click in Fuga object hierarchy. The wind direction trend and
spatial decorrelation options are implemented in Fourier space. They are unavailable in the specific-wind situation but
may be calculated from the 'result-table' data export.
How to prepare a WAsP workspace
The work flow is
1. set up a WAsP project, including groups of turbines sites, a wind atlas, and wind turbine generators
2. right-click on a project object and select the ‘do all feasible calculations’ or press F9
3. check that the WAsP calculations were successful, i.e. the wind farm icon in the WAsP object hierarchy
should not include a warning signs but look like this
4. export the workspace file
There is much more detailed information in the WAsP help file, both regarding user interface, modelling and file for-
mats. The section called 'quick start tutorial' is recommended.
Here is a list of basic operations:
Modify a turbine power- and trust-coefficient curve
There are two file formats for this. The old *.pow format is easiest to edit with an ASCII editor. The *.wtg format can
be edited with the WAsP turbine editor. The latter file format may contain several performance tables applicable for
different air density.
Specify a turbine type
You may (but do not have to) specify a turbine type for each turbine site. WAsP will look for a turbine assigned to the
turbine group if site information is missing. If this information is missing too, then WAsP will search for a turbine type
assigned to its parent group or project. The principle is to look for local information before global one.
Modify a turbine height
A turbine hub height in WAsP may differ from its default value in the power-curve file. Right-click on a site or turbine
group and specify the real-world hub height.
Add or modify turbine positions
The interactive way is to right-click on an existing site to edit its coordinates or right-click on a turbine site group to
add more sites. To edit lots of positions it is more convenient to import a site list which can be prepared by an ASCII
editor. The format is described in the WAsP help file. Tip: Export a list from an existing group and use this as a tem-
plate.
Add a reference mast
You can insert a reference mast for a turbine site group. In WAsP it is used as a reference for a windfarm power
curve. In Fuga you can use it as a reference point for specifying wind condition at a height different from the turbine
hub height(s).
Reorganize turbine site groups
You can insert new turbine site groups in a project and add nested sub groups. You can drag turbine sites from one
site group to another.
Add wind climate information
Climate information is either added
l as a wind atlas file representative for the region or
l as locally observed wind statistics.
Observed wind statistics are read from a file, which can be generated from time series with a tool called WAsP Climate
Analyst. It is also possible to write a *.tab file which has a relatively simple format, see WAsP help file. WAsP observed
wind file is assigned to a met station which specifies the met mast position and the station is assigned to a wind atlas.
Wind atlas information are cleansed for local effects.
The number of wind sectors used in both WAsP and Fuga depends on the number of sectors in the input wind cli-
mate. The default is to use 12 sectors. Go back to the WAsP Climate Analyst if you need to change this.
Prepare terrain data
This is normally done with the WAsP Map Editor. For offshore projects the roughness change at the coast line is often
much more significant than terrain elevation on nearby land.
How to prepare a WAsP windfarm file
Fuga 1 needed data in the WAsP windfarm file (*.wwf). Fuga 2 uses the more complex workspace file (*.wwh) but
you can still do Fugabatch calculations based on wind farm files for simple projects with identical turbines.
This wind farm file is prepared in the following way:
1. set up a WAsP project, including a group of turbines sites, a wind atlas, and a wind turbine generator
2. right-click on the site group and select the ‘do all feasible calculations’ option from the popup menu
3. check that the WAsP calculations were successful, i.e. the wind farm icon in the WAsP object hierarchy
should not include a warning signs but look like this
4. right-click on the site group again and select ‘export wind farm to file’ from the popup menu
The WAsP wind farm file contains turbine locations and, with successful WAsP calculations, also the local wind cli-
mates and annual power production estimates.
Fuga version 1.0 used the even simpler WAsP site location *.txt or *.wsg file format. This file type was, however,
abandoned in version 1.1, because it lacks information on wind climate and power production.
Case statistics file
The influence of variable statistics is simplified to a statistical weighting of a selection of specific cases. Each case is
specified by surface roughness z0, inversion height zi and stability parameter zeta0 and may be assigned a text iden-
tifier. The statistical frequency of occurrence for each case is given in sectors and wind-speed bins.
The sectors are defined by their dividing directions, e.g. 348-23°, 23-46°, 46-217°, 217-348° , 23-46°in the below
example. Wind-speed bins are defined by their maxima, e.g. 0-2 m/s, 2-4 m/s, 4-6 m/s, 6-8 m/s, 8-10 m/s, 10-15
m/s, 15-30 m/s in the below example.
Example
The following sample file 'casestats.txt' is included is found in the Fuga directory.
Roughness and stability parameters
The tables provides surface roughness and stability parameters for Fuga. They describe an equilibrium offshore sur-
faces layer with surface roughness estimated by Charnock's equation. The wind speed U [m/s] is defined at a ref-
erence height of 70 m. The inverse Monin-Obukhov length 1/L values [m-1 ]correspond to Sathe-Gryning-Peña class
limits and midpoints.
Table 1: Z [mm] as function of wind speed and stability.
0
very unstable near-neu- neutral near-neu- stable
unstable tral tral
unstable stable
1/L
U -0.0200 -0.0150 -0.0100 -0.0075 -0.0050 -0.0035 -0.0020 0.0000 0.0020 0.0035 0.0050 0.0125 0.0
4.0 0.01624 0.01582 0.01529 0.01496 0.01455 0.01425 0.01386 0.01303 0.01178 0.01096 0.01023 0.00750 0.00
5.0 0.02740 0.02666 0.02572 0.02514 0.02443 0.02390 0.02323 0.02177 0.01961 0.01820 0.01695 0.01231 0.00
6.0 0.04213 0.04094 0.03945 0.03853 0.03740 0.03656 0.03549 0.03320 0.02980 0.02759 0.02564 0.01847 0.01
7.0 0.06073 0.05895 0.05675 0.05538 0.05370 0.05245 0.05088 0.04749 0.04250 0.03927 0.03642 0.02605 0.01
8.0 0.08350 0.08098 0.07786 0.07593 0.07357 0.07181 0.06959 0.06484 0.05786 0.05337 0.04941 0.03510 0.02
9.0 0.11073 0.10730 0.10305 0.10043 0.09722 0.09483 0.09184 0.08542 0.07603 0.07001 0.06471 0.04569 0.03
10.0 0.14269 0.13816 0.13256 0.12909 0.12487 0.12174 0.11781 0.10939 0.09713 0.08930 0.08242 0.05787 0.04
11.0 0.17966 0.17381 0.16661 0.16216 0.15674 0.15272 0.14768 0.13692 0.12130 0.11135 0.10263 0.07168 0.05
12.0 0.22190 0.21452 0.20543 0.19983 0.19302 0.18797 0.18165 0.16817 0.14865 0.13626 0.12543 0.08718 0.06
13.0 0.26968 0.26052 0.24927 0.24234 0.23391 0.22768 0.21988 0.20328 0.17931 0.16414 0.15091 0.10440 0.07
14.0 0.32326 0.31207 0.29833 0.28988 0.27962 0.27203 0.26255 0.24240 0.21339 0.19509 0.17915 0.12338 0.09
15.0 0.38291 0.36941 0.35284 0.34267 0.33033 0.32122 0.30983 0.28569 0.25101 0.22919 0.21023 0.14417 0.10
16.0 0.44888 0.43277 0.41303 0.40092 0.38623 0.37541 0.36189 0.33327 0.29228 0.26654 0.24423 0.16681 0.12
17.0 0.52143 0.50239 0.47910 0.46482 0.44753 0.43479 0.41890 0.38530 0.33730 0.30724 0.28122 0.19133 0.13
18.0 0.60083 0.57853 0.55127 0.53459 0.51440 0.49954 0.48101 0.44191 0.38618 0.35137 0.32129 0.21777 0.15
19.0 0.68734 0.66141 0.62977 0.61042 0.58703 0.56983 0.54840 0.50324 0.43903 0.39902 0.36450 0.24617 0.17
20.0 0.78120 0.75129 0.71481 0.69253 0.66562 0.64584 0.62123 0.56943 0.49595 0.45027 0.41093 0.27655 0.20
21.0 0.88270 0.84839 0.80661 0.78111 0.75034 0.72774 0.69966 0.64061 0.55705 0.50521 0.46065 0.30895 0.22
22.0 0.99208 0.95296 0.90537 0.87636 0.84138 0.81572 0.78384 0.71691 0.62242 0.56393 0.51372 0.34341 0.24
23.0 1.10961 1.06524 1.01133 0.97849 0.93893 0.90993 0.87394 0.79848 0.69216 0.62649 0.57022 0.37996 0.27
24.0 1.23556 1.18547 1.12469 1.08770 1.04318 1.01057 0.97012 0.88543 0.76637 0.69299 0.63021 0.41862 0.30
25.0 1.37020 1.31391 1.24567 1.20419 1.15430 1.11779 1.07253 0.97790 0.84516 0.76351 0.69375 0.45942 0.32
Working with projects with three or more turbine site groups you may want to include all but one or some of these
groups. This can be done by first selecting the combined set of turbines and then temporarily deactivating sub-
groups. You do this by right-clicking on a group.
Data export
Data export to file or clipboard are found in the 'file' menu. Clicking on one of the 'Save...' menu items will invoke a
Windows save-file dialogue. The default names are shown below but it is also possible to specify other names. Most of
the results are identical to the ones shown in the user interface, but the result table has a more flexible layout. The
'Zip all' option will collect all results in a single file. The 'Copy...' options will copy results to the Windows clipboard.
Result table
The layout of exported result tables can be modified in various ways
l Result type -chose whether to export wind speeds at turbine locations, with wake effects from neighbour tur-
bines, or the corresponding power read from the WAsP power curve file.
l Turbine site - select data from a single site, from all sites, or the average or total from the entire windfarm
l Wind direction - select a range of wind directions and a increment. Choose output for each direction of just
the average
l Wind speed - select a range of wind speeds and a increment.
The results will be modelled with current averaging options.
Main menu
You can new projects and case data form the File menu. It is possible to export results and plots to file and clipboard.
The about box under the help menu provides version information for the Preludium, Trafalgar and Fuga programs.
Fuga scripting
FugaBatch is a special version of Fuga designed to run in a non-interactive mode. The calculations are controlled by a
script input file and the name of this file is specified as a parameter in the command line, e.g.
fugaBatch fugaScript.txt [/L=MyLogFile.txt]
The second parameter is optional. When included, the progress reports normally written to a DOS window are redi-
rected to the specified file.
The script input file has two sections. First the setup is specified by names of various input files. These file names are
written with double quotation marks and must be given in the order shown the below examples, since Fuga will proc-
esses each line of the script individually. The easiest way to generate the input files is by using Fuga in interactive
mode, but you can also generate them by calling WAsP, preludium and trafalgar directly. It is not possible to change
the Fuga setup within a single call, i.e. if you want to model a wind farm with two alternative turbine types in non-
interactive mode you have to call fugaBatch twice.
Setup
The first section can be written in two ways:
Fuga 1 style (Deprecated)
Command: SiteListFilename
the full path to a WAsP windfarm file (*.wwf)
Command: TurbineFilename
the full path to a WAsP turbine file (*.pow or *.wtg)
Command: CaseFilename
the full path to the casedata file (casedata.bin) in a directory with Preludium and Trafalgar output.
NB: You may need to update old scripts as Fuga 2.3 GUI changes names of existing directories, e.g. from "C:\LUTs-
T\Vestas_V80_(2_MW_offshore)[h=67.00]\Z0=0.00010000Zi=00399\casedata.bin" to "C:\LUTs-T\Vestas_V80_
(2_MW_offshore)[h=67.00]\Z0=0.00010000Zi=00399Zeta0=5.0E-7\casedata.bin"
Fuga 2 style
Command: Workspace
the full path to a WAsP workspace file (*.wwh)
Command: CASE z0 zi zLo zHi [Zeta0]
Boundary layer specifications. Here, z0 is surface roughness [m], zi is the boundary layer height [m], and zL0 and
zHi [m] define the vertical range of wake output. The zi, zLo, and zHi parameters are approximate as they will be
rounded off to the nearest level in the preludium model. The stability parameter Zeta0, which is z0 divided by Moni-
Obukhov length L, is optional. Stability will be set to neutral, Zeta0=0, if not specified.
Modified Fuga 1 style
Command: SiteListFilename
Command: TurbineFilename
Command: CASE z0 zi zLo zHi [Zeta0]
The original Fuga 1 style script normally only works with input files created by the main Fuga program. Scripts with
the CaseFilename substituted by the newer CASE command make Fugabatch generate missing information.
Instructions
The second section of the script input file contains instructions for various kinds of output. You can include as many
instructions as you like in a single script.
Annual energy production
Command: AEP Nsec [caseStatsFilename] filename
where Nsec actually now is redundant. It is only allowed for backward compatibility and it will be ignored if present.
Filename is the name of the output file. CaseStatsFilename is optional. If omitted, the calculations will be based on
boundary-layer conditions in the 'caseFilename' (Fuga 1 style) or 'case' (Fuga 2 style) instructions. When included,
the AEP calculations are based on frequencies of different atmospheric stabilities defined in the specified file . The file
format is described here.
Hub-height wind speeds at turbine positions
Command: SHELTER filename
where filename is the name of the output file This will produce a table with windspeeds at turbine positions for all tur-
bine sites, all directions and all free stream wind speeds. The calculated wind speeds include wake effects of all
upwind turbines, but not the effect of the local turbine
Reference site
Command: REFERENCESITE x-coordinate y-coordinate height
Where x-coordinate, y-coordinate and height gives the reference site position. The horizontal coordinates position are
used when DirStatFilter is set to 2 in the AVERAGINGOPTIONS command. The height is used as the reference height
for wind speeds defined in the PROD, FLOW and TRANSECT commands.
Power production and local hub-height wind speed for a given wind situation
Command: PROD windspeed windDirection filename
Where windspeed and windDirection describes the free wind and filename is the name of the output file
Hub-height wind speeds in a cartesian grid
Command: FLOW windspeed windDirection X0 Y0 dX dY Nx Ny filename
Where windspeed and windDirection describes the free wind, X0 and Y0 are the coordinates of the lower-left corner
of the grid, dX and dY are grid resolutions in X and Y direction, Nx and NY are the number of grid nodes in each direc-
tion and filename is the name of the output file. The output is the wind affected by wakes of all turbines, including the
local turbine if a grid node matches a turbine site. Thus the results are different than those produced by the SHELTER
command.
The output file is in the Surfer Ascii *.grd format described in the WAsP help file.
Wind speeds in a 2D cartesian grid intersecting a 3D wake
Command: FLOW windspeed windDirection X0 Y0 Z0 rot tilt dX dY Nx Ny filename
where windspeed and windDirection describes the free wind, X0, Y0, and Z0 are coordinates of the lower-left corner
of the grid, as in the previous version. Furthermore, dX and dY are grid resolutions and Nx and NY are the number of
grid nodes in each direction and filename is the name of the output file. An important change is, however, that the
Surfer grid coordinate system does not have to be oriented in a horizontal plane with with X toward East. The grid
orientation is specified by 1) a counter-clockwise rotation angle, e.g. to make the surfer grid X axis point NW you
enter rot=135, and 2) a tilt angle, e.g. to make the Y axis point vertical you enter tilt=90. The grid origo is centred at
the point (X0, Y0, Z0). The wind speed applies to the turbine hub height.
Hub-height wind speeds along a transect
Command: TRANSECT windspeed windDirection X1 Y1 X2 Y2 N filename
Where windspeed and windDirection describes the free wind, X1 and Y1 are coordinates of the start of the transect,
X2 and Y2 are coordinates of the end of the transect, N is the number of nodes along the transect and filename is the
name of the output file. These results are similar to those found by the FLOW command.
Wind speeds along a general 1D transect in a 3D wake
Command: TRANSECT windspeed windDirection X1 Y1 Z1 X2 Y2 Z2 N filename
As above, except that the now the transect start and end points are written with three coordinates. The wind speed
applies to the turbine hub height.
Velocity deficit
The DEFICITcommand is similar to the two versions of the TRANSECTcommand. The only difference that the velocity def-
icit is written to the file instead of the wake-corrected wind field.
Result Table
Command: RESULTTABLE ResultType TurbineSite uLo uHi Du DirLo DirHi Ddir DirAve useFFT filename
Where
l ResultType is set to 0 for wind speed or 1 for power production
l TurbineSite is a string which either is identifier of a particular turbine site or "All" for data from all sites or
"Total" for the average(speed) or aggregated(power) of for all sites in the wind farm
l uLo is the lower limit of the wind-speed range
l uHi is the upper limit of the wind-speed range
l dU is an wind-speed increment in the table
l DirLo is the first wind direction
l DirHi is the last value in a range of wind direction which is arranged anticlockwise
l Ddir is a wind-direction increment in the table
l DirAve indicates whether to output for every wind direction (if set to 0) or to output the average for all direc-
tions in the range (if set to 1)
l useFFT set to 1 means that results are calculated for all directions and the directional filters are applied in Fou-
rier space. With this option set there may be a small correction to the wind-direction increment Ddir and the
last wind direction DirHi. With useFFT set to 0 (default) the top-hat and Gaussian averaging filters will be cal-
culated as the weighted average of several calculations, and the DirStatFilter corrections defined in the AVER-
AGINGOPTIONS command are temporarily inactive.
l Filename is the name of the output file
Averaging options
Command: AVERAGINGOPTIONS RotorAve AveFilter FilterScale MeanderRepeats DirStatFilter
Where
l RotorAve is set to 1 for rotor-averaged inflow velocity or 0 for rotor centre velocity (default)
l AveFilter is set to
o 0 for a fixed direction with no directional averaging (default)
o 1 for simple top-hat averaging in a user-defied sector
o 2 for weighted averaging in a Gaussian distribution around the centre angle
o 3 for meander simulation
l FilterScale is the half width of the top-hat averaging filter or spread of the Gaussian filter. This parameter has
no effect on the meander model, but please insert a dummy value anyway
l MeanderRepeats is the number of repeated meander simulations.
l DirStatFilter models the statistical uncertainty of power statistics due to variable wind direction. It is set to
o 0 for no correction
o 1 for correction for wind-direction trend during each sample period (typically a 10-min sample period)
o 2 for correction of trend effects as above, plus statistical de-correlation due to spatial separation
between reference mast and turbine sites. NB: Remember to set the REFERENCESITE command for
this option
Averaging options affect subsequent script commands until a new set of options is specified. Averaging options will
only affect AEP, PROD, SHELTER and RESULTTABLE commands - and with further exceptions for the DirStatFilter
option. This last option relies on FFT calculus and therefore it is not active for the PROD calculations and for RESUL-
TABLE it is only active with the useFFT option set to 1. It is also inactive if AveFilter option is set to 0 (fixed direction).
If that case is of interest you could use a top-hat filter of zero width. Read about equivalent averaging options in the
GUI version.
Pause in output
Command: PAUSE [duration]
Where
l Duration is the length of the pause in seconds. With no duration specified, the script will wait for the user to
press 'Enter' on the keyboard.
This command will insert a delay in the screen output. It is intended for script testing and will be ignored if the output
is redirected to a log file.
Examples
A Fuga 1 styled script file
[Setup]
sitelistFilename ".\WAsP sitelists\Horns Rev 1.wwf"
turbineFilename ".\WAsP turbine data\Vestas V80 (2000 kW).pow"
caseFilename "..\LUTs\Vestas_V80_(2_MW_offshore)\Z0=0.00010000Zi=00400Zeta0=0.00E-0\casedata.bin"
CASE 0.0001 400 1 400
[Instructions]
AEP 12 ".\export\Horns Rev AEP.txt"
SHELTER ".\export\Horns Rev shelter factors.txt"
PROD 10 282 ".\export\Horns Rev u=10 Dir=282.txt"
PROD 11 270 ".\export\Horns Rev u=11 Dir=270.txt"
FLOW 10 265 423000 6147000 10 10 1000 600 ".\export\Horns Rev u=11 Dir=270.grd"
FLOW 7 215 429905 6147152 5 144 90 20 2 400 160 ".\export\Horns Rev vertical diagonal cross section, u=10
Dir=265.grd"
TRANSECT 10 270 423000 6147000 433000 6147000 200 ".\export\Horns Rev transect u=10 Dir=270.txt"
TRANSECT 7 215 426703 6149495 5 426703 6149495 350 346 ".\export\Horns Rev vertical transect, u=7
Dir=215.txt"
ResultTable 0 "All" 5 8 1 265 275 1 0 2 4.2 ".\export\Horns Rev results.txt"
A Fuga 2 styled script file
[Setup]
WORKSPACE ".\WAsP workspaces\hornsrev.wwh" "Horns rev combined"
CASE 0.0001 400 1 400
[Instructions]
AEP ".\export\Horns Rev AEP.txt"
SHELTER ".\export\Horns Rev shelter factors.txt"
PROD 10 282 ".\export\Horns Rev u=10 Dir=282.txt"
PROD 11 270 ".\export\Horns Rev u=11 Dir=270.txt"
FLOW 10 265 423000 6147000 10 10 1000 600 ".\export\Horns Rev u=11 Dir=270.grd"
FLOW 7 215 429905 6147152 5 144 90 20 2 400 160 ".\export\Horns Rev u=11 Dir=270.grd"
TRANSECT 10 270 423000 6147000 433000 6147000 200 ".\export\Horns Rev transect u=10 Dir=270.txt"
TRANSECT 7 215 426703 6149495 5 426703 6149495 350 346 ".\export\Horns Rev transect u=7 Dir=215(3).txt"
DEFICIT 10 270 423000 6147000 433000 6147000 200 ".\export\Horns Rev deficit u=10 Dir=270.txt"
DEFICIT 7 215 426703 6149495 5 426703 6149495 350 346 ".\export\Horns Rev deficit u=7 Dir=215(3).txt"
ResultTable 0 "All" 5 8 1 265 275 1 0 2 4.2 ".\export\Horns Rev results.txt"
A Fuga 1 styled script file with stability effects
[Setup]
sitelistFilename ".\WAsP sitelists\Horns Rev 1.wwf"
turbineFilename ".\WAsP turbine data\Vestas V80 (2000 kW).pow"
caseFilename "..\LUTs\Vestas_V80_(2_MW_offshore)\Z0=0.00010000Zi=00400Zeta0=2.00E-7\casedata.bin"
CASE 0.0001 400 1 400 2.00E-7
[Instructions]
AEP "caseStats.txt" ".\export\Horns Rev AEP.txt"
PROD 10 282 ".\export\Horns Rev u=10 Dir=282.txt"
PROD 11 270 ".\export\Horns Rev u=11 Dir=270.txt"
A Fuga 2 styled script file with stability effects
[Setup]
WORKSPACE ".\WAsP workspaces\hornsrev.wwh" "Horns rev combined"
CASE 0.0001 400 1 400 2.00E-7
[Instructions]
AEP "caseStats.txt" ".\export\Horns Rev AEP.txt"
PROD 10 282 ".\export\Horns Rev u=10 Dir=282.txt"
PROD 11 270 ".\export\Horns Rev u=11 Dir=270.txt"
A result table script
[Setup]
WORKSPACE ".\WAsP workspaces\hornsrev.wwh" "Horns rev combined"
CASE 0.0001 400 1 400
[Instructions]
ResultTable 0 "All" 5 8 1 265 275 1 0 ".\export\Nysted results.txt"
AVERAGINGOPTIONS 1 2 3.5 1 2
ResultTable 0 "Total" 5 8 1 0 359 1 0 1 ".\export\Nysted results, RotorAve, Gauss(3.5Deg), decorrelation and
FFT.txt"
Number of turbines
The wind-farm wake calculation time increases with the number of turbines. The calculation of wake effects on
individual turbines will depend on the number of upwind turbines, though not when these are far off the wind tra-
jectory hitting the downwind turbine. Thus, the overall wake calculation time scale between O(N) and O(N2), where N
is the number of turbines.
Rotor averaging
With rotor averaging, the inflow is calculated as a weighted average of the velocity of seven points on the exposed tur-
bine. This extra work slows down the calculations by a factor of approximately 4.
Meander model
The meander model is a stochastic simulation and slower than the simple methods. The wake effect on each turbine is
simulated independently. For AEP calculations we cheat a little and use the same simulated wake trajectories for all
wind speeds, tough with wind-speed dependent thrust. If you select multiple meander simulations, the simulation
time will increase proportionally. A high number of simulations is usually unnecessary for a large wind farm as var-
iable results for individual turbines tend to cancel each other. The variability for individual turbines will generally
decrease with the number of upwind turbines and also disappear for no upwind turbines are found. Thus, variability
of single-turbine meander results will depend on direction.
CPU cache
Fuga calculations tend to speed up the second time in a work session. This is probably because LUT table data are
available in the cache.
Software updates
We recommend to install software updates in a new directory, check that the new system works, and then delete the
old file structure. However, for smaller changes, we can give the following guidelines:
l Changes in preludium.exe or its input parameters in script1.txt will outdate all LUTs subdirectories, which
should be deleted.
l Changes in trafalgar.exe will outdate *.dat files at the the second level of the LUTs subdirectories, i.e. the
case level. If trafalgar.exe is changed it is probably be easiest to delete all case subdirectories and regen-
erate them.
l Changes in fuga.exe should only affect files in the fuga directory and its subdirectories.
l With new turbine information, e.g. a modified power curve, all files in the corresponding turbine directory
and its case directories should be removed.
References
l Søren Ott (2011): Linearized CFD, Risø-I-3093 (EN), 29 pp.
l Søren Ott (2011): Linearized CFD Models for Wakes, Risø-R-1772 (EN), 37 pp.
l Søren Ott and Morten Nielsen (2010): Fuga Files and Scripts
l Ameya Sathe, Sven-Erik Gryning, Alfredo Peña (2011): Comparison of the atmospheric stability and wind pro-
files at two wind farm sites over a long marine fetch in the North Sea, Wind Energy Vol. 14, Issue 6, p. 767–
780
l WAsP help file, distributed with WAsP and also available from www.wasp.dk
Bibliographic Data Sheet DTU Wind Energy E-0046
Title and author(s)
ISBN ISSN
978-87-92896-81-0
Dept. or group Date
89 3 21 28
Abstract (Max. 2000 char.)
This is the final report of the project entitled Risø DTU Modelling Services carried out by
DTU Wind Energy (formerly known as Risø National Laboratory) as part of the Carbon
Trust’s Offshore Wind Accelerator Stage 2 under a contract with Carbon Trust. The project
is a follow–up to a Carbon Trust’s Offshore Wind Accelerator Stage 1 project called Lin-
earized CFD Wake models. The earlier project resulted in the development, implementation
and validation of the Fuga model. Fuga is a linearized CFD model that can predict wake
effects for offshore wind farms. The main purpose of Stage 2 is to add more features to Fuga
and turn it into a useful tool for offshore wind farm developers. The new features consist in
• Flexibility. Including the ability to cope with several types of turbines in the same
project, thus making it possible to predict inter farm interactions. The graphical user
interface has been greatly improved and a number of input/output facilities have been
added.
• Stability effects. The effect of stability has been added through a modification of the
eddy viscosity based on Monin–Obukhov theory. The numerical solver developed in
Stage 1 has been generalized in order to make it deal with the modified equations.
• Meandering. Meandering has been included in the form of a post processing of the
model results that bend and twist the wake centreline. The meandering centrelines are
calculated using a Gaussian process developed on the basis of measured spectra. An
analysis of meteorological data from Horns Rev has been made in order to quantify the
impact of non–stationarity of the wind direction. The results are generalized so as to
account for the uncertainties imposed by a ten minute mean value trend as well as by
the distance between turbines and the met mast.
The old model has been validated against a number of data sets. Some of these tests have
been repeated in order to demonstrate and validate the new model features. Production data
from Horns Rev 1 have been re–analysed using well defined selection criteria for which the
developed uncertainty models apply, and a comparison with data is made. Even if the model
predictions fall within estimated error bars, the model seems to over predict the measured
efficiencies by a few percent.
The model works best for unstable, neutral and light stable conditions whereas the results
for stable and very stable conditions are questionable. We suspect this is caused by a failure
of the numerical solver that becomes progressively more severe as the stability increases.
Descriptors
DTU Wind Energy is a department of the Technical University of Denmark with a unique integration of research, education, innovation and
public/private sector consulting in the field of wind energy. Our activities develop new opportunities and technology for the global and Danish
exploitation of wind energy. Research focuses on key technical-scientific fields, which are central for the development, innovation and use of wind
energy and provides the basis for advanced education at the education.
We have more than 240 staff members of which approximately 60 are PhD students. Research is conducted within nine research programmes
organized into three main topics: Wind energy systems, Wind turbine technology and Basics for wind energy.
info@vindenergi.dtu.dk
www.vindenergi.dtu.dk