z-logo
Premium
Evaluating forecasts of the evolution of the cloudy boundary layer using diurnal composites of radar and lidar observations
Author(s) -
Barrett Andrew I.,
Hogan Robin J.,
O'Connor Ewan J.
Publication year - 2009
Publication title -
geophysical research letters
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 2.007
H-Index - 273
eISSN - 1944-8007
pISSN - 0094-8276
DOI - 10.1029/2009gl038919
Subject(s) - lidar , diurnal cycle , cloud height , diurnal temperature variation , radar , environmental science , entrainment (biomusicology) , cloud computing , meteorology , liquid water path , atmospheric sciences , boundary layer , cloud base , cloud top , cloud cover , ceilometer , climatology , geology , remote sensing , geography , physics , mechanics , computer science , precipitation , telecommunications , rhythm , acoustics , operating system
Observations of boundary‐layer cloud have been made using radar and lidar at Chilbolton, Hampshire, UK. These have been compared with output from 7 different global and regional models. Fifty‐five cloudy days have been composited to reveal the mean diurnal variation of cloud top and base heights, cloud thickness and liquid water path of the clouds. To enable like‐for‐like comparison between model and observations, the observations have been averaged on to the grid of each model. The composites show a distinct diurnal cycle in observed cloud; the cloud height exhibits a sinusoidal variation throughout the day with a maximum at around 1600 and a minimum at around 0700 UTC. This diurnal cycle is captured by six of the seven models analysed, although the models generally under‐predict both cloud top and cloud base heights throughout the day. The two worst performing models in terms of cloud boundaries also have biases of around a factor of two in liquid water path; these were the only two models that did not include an explicit formulation for cloud‐top entrainment.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here