300m south sonic
Not sure when this happened, but suspect during either the Jun 4th or 5th lightening storms.

Sonic still working after being hit. No signs of damage to north sonic

250m south boom
For some reason the south boom at 250m is shorter than all the rest. Neither Bruce nor I can remember why this is or when it happened. 250m except for LUMEX and XPIA has not been instrumented.

Measurement from the center of the sonic path to the south leg is 3.15m

Sonics and T/RH at 300, 250, 200, and 150m have all been removed.

BAO Ceilometer and Sodar data files
Here is where you can find the raw data files for both the mono-static sodar and ceilometer located at the visitor compound:

ftp://ftp1.esrl.noaa.gov/psd3/bao/Ceilo/raw/    (Vaisala binary)

This file describes the data format:
ftp://ftp1.esrl.noaa.gov/psd3/bao/Ceilo/readme_ceilometer_BAO.txt

ftp://ftp1.esrl.noaa.gov/psd3/bao/Tower/Sodar/Raw/     (netcdf)

This file describes the data format:
ftp://ftp1.esrl.noaa.gov/psd3/bao/SODAR/Sodar_Readme.txt

We use MATLAB to read the raw files. We can get you the code if you want.

Profiling lidar

For the profiling lidars, we plan:

- global study (throughout XPIA) comparing the WCv1 lidars to each other and to the WCv2 lidar (after it was deployed 12 March)
- global study (throughout XPIA) comparing the lidars to tower sonics for mean wind speed and direction
- global study (throughout XPIA) comparing the wind fluctuations from the lidars to TKE from the tower sonics
- case study of some interesting LLJs (0-6 UTC) such as 5 March, 16-17 March (odd NEly jet), 4 Apr, 6 Apr (2-6 UTC), 6-7 Apr (22-4 UTC), 10 Apr (0-6 UTC), 12 Apr (0-12 UTC), 14 Apr (0-8 UTC, very strong),  23 Apr (0-8 UTC, very strong, sswly), 24 Apr (0-6 UTC, pulsing LLJ, NWly)

 

UTD preliminary data analysis

The UTD team proposes to work on the evaluation of the scanning lidar accuracy for different configurations and atmospheric conditions. This analysis is carried out by comparing the 200S radial velocity with the sonic data acquired by the met-tower and the profiling lidars. The sonic and profiling lidar data are projected over the 200S line-of-sight in order to produce an equivalent radial velocity.

For this analysis an "effective" range gate is evaluated, i.e. the projection of the range gate over the horizontal plane and mean wind direction. This parameter is considered to be the sensitive measurement volume of the lidar. The vertical extent of the lidar range gate is also evaluated, which is a parameter to estimate the effect of wind shear on the radial velocity.

The error analysis will be performed by considering different stability regimes, turbulence intensity, wind shear and veer.

After this error analysis for the radial velocity of single lidars, the retrieval of 3D velocity components from 3 intersecting and synchronous lidars will be carried out. For this analysis a crucial point is the definition of the effective measurement volume determined by the intersection of the 3 range gates.

For the proposed analysis the following experiments will be investigated:

• Dual/Triple Doppler Stares - Sonic + Lidar Supersite 3/21/2015-3/24/2015
• Dual/Triple Doppler Stares - Sonic + Lidar Supersite + Radar Site 3/24/2015-4/1/2015

Tower power issue solved (we hope). Thanks to some excellent weather and Bruce's sleuthing we feel we have the breaker issue solved. There was a worn wire inside one of the electrical boxes at ~125m that was shorting out. Tower vibrations and temperature swings over 40 years. It's amazing there aren't more problems"  (knock on galvanized steel").

BAO Tower Update 2015-05-27
200 and 300m T/RH not working. Starting Sat May 23 1900 UTC
Probably will not be replaced.
Lost NCAR and some standard BAO tower data over weekend. Back up  Tuse May 26.