27.02.2013 Views

Wind Energy

Wind Energy

Wind Energy

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

108 Karine Leroux and Olivier Eiff<br />

(a) 2.0<br />

n=H<br />

1.5<br />

1.0<br />

0.5<br />

0.0<br />

0 1 2 3 4<br />

(b)<br />

2.0<br />

s=H<br />

n=H<br />

1.5<br />

1.0<br />

0.5<br />

0.0<br />

H<br />

0 . 6H<br />

0 1 2 3 4<br />

s=H<br />

Fig. 18.3. Boundary layer representation. | −→ U |/U0 for Re ∼ 10 2 (a), and Re ∼ 10 4<br />

(b)<br />

nevertheless some differences between the two cases. The TLW train of wavelength<br />

0.8λ is shifted downstream by 0.3H in the slip case, resulting in a<br />

shifted extend of the separated downslope windstorm, in phase with the wave<br />

train.<br />

18.5 Boundary Layer and Wave Field Interaction<br />

In Figs. 18.3a and b for Re ∼ 10 2 and Re ∼ 10 4 , respectively, the norm of<br />

the velocity field | −→ U | /U0 is plotted on a (s/H, n/H) chart, on the lee<br />

side. n is the perpendicular height from surface, and s is the surface-following<br />

coordinate starting on the obstacle crest. The thickness of the high velocity<br />

region defined as | −→ U |> U0 is 40% smaller at high Re-number, but in both<br />

cases the maximum velocity is located at a distance of 0.4H above the obstacle<br />

near x = λ/3. If the obstacle were a flat plate, the boundary-layer height<br />

δ/H would be approximately proportional to 1/H for the flow parameters<br />

of the two cases. Considering Umax to delimit the boundary-layer height on<br />

the obstacles, they do not scale as standard boundary layers, implying, as<br />

expected, a strong wave-field influence. The Re-number independence suggests<br />

a one-way interaction of the wave field on the boundary-layer height.<br />

2.5<br />

2.0<br />

1.5<br />

1.0<br />

0.5<br />

0.0

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!