TWP/MPL/C1 - Intermittent Double Pulse from laser

When Spectra Physics discontinued support for their laser diode power supply, an 
alternative was need to extend the usefulness of the Spectra Physics laser head inside the MPLs.  
The solution was to use a Coherent laser diode. Unfortunately, the Coherent diode lasers 
do not have the exact same characteristics as the Spectra Physics diode lasers. As a 
result, the output of the Spectra Physics laser head sometimes produces a second pulse close 
in time but lower in intensity from the first main pulse. This is known as ?double pulsing?.

Not all of the Spectra Physics/Coherent combination systems produce a double pulse and the 
systems that do produce a double pulse do not always exhibit this behavior. It can be 
identified by a second peak at ~.2km. At first glance the signal in the data will resemble 
a low aerosol or cloud layer. When the double pulse is weak, the atmospheric signal will 
obscure the double pulse signal. At the ARM sites with a sunshade such as TWP and AMF, 
the double pulse can be seen when the sunshade closes during solar noon. When the sunshade 
closes, the MPL does not see atmospheric signal so the second pulse is evident. At SGP, a 
daily window cleaning is part of the routine. During this time the double pulse can be 
seen. Without a sunshade or window cleaning it is impossible to say definitively if double 
pulse is present. 

The first system to produce a double pulse was MPL s/n 008 located at TWP ? C2 Nauru in 
February 2005. The second system was MPL s/n 004 located at SGP in August 2005. The 
potential for the other systems to produce a double pulse is high. However, as of March 2006, 
the MPLs at NSA, TWP ? C1, TWP ? C3 and AMF have not recorded data with the double pulse 
artifact. 

The ARM program is in the process of replacing all the MPLs with a newer model. After the 
new MPLs are deployed the double pulse problem should not be an issue. The old systems 
will be relegated as spares. The double pulse problem will return if an old system is 
needed to replace a failed new system.

• Attenuated backscatter(detector_counts)

TWP/SMET/C1 - Upper wind sensor failure

The upper wind speed sensor was binding at low wind speeds.  Comparison to the lower wind 
sensor showed that the upper sensor flat-lines for long periods of time.  The upper 
anemometer was replaced.

• Upper sensor, wind direction standard deviation(up_dir_sd)
• Upper sensor, wind direction vector average(up_dir_vec_avg)
• Upper sensor, wind speed maximum(up_spd_max)
• Upper sensor, wind speed arithmetic average(up_spd_arith_avg)
• Upper sensor, wind speed vector average(up_spd_vec_avg)
• Upper sensor, wind speed minimum(up_spd_min)
• Upper sensor, wind speed standard deviation(up_spd_sd)

TWP/MPL/C1 - Data dropouts

Data dropouts occurred during this period. Problem ended when MPL computer was rebooted.

• Background Signal(background_signal)
• Angle of orientation with respect to true geographic north(tranceiver_azimuth_angle)
• range(range)
• Array of heights for the range gates(height)
• Detector Temperature(detector_temp)
• Dummy altitude for Zeb(alt)
• required to correct raw counts for detector deadtime prior to all other
  corrections.(deadtime_correction)
• Amount of time the actual laser pulse lags behind the sync trigger(laser_sync_offset)
• GPS raw data filename(filename)
• lon(lon)
• Attenuated backscatter(detector_counts)
• Maximum altitude retrieved from multichannel scalar card.(max_altitude)
• Voltage level which operates the thermistor(voltage_10)
• Preliminary cloud base height above ground level(cbh)
• Repetition Rate, or Trigger Frequency of the laser(pulse_rep)
• Preliminary cloud base height(preliminary_cbh)
• Voltage level which operates the energy monitor(voltage_15)
• value represents date of last configuration change as yyyymmdd(property)
• lat(lat)
• Angle of inclination with respect to horizontal(tranceiver_altitude_angle)
• Number of laser pulses summed during measurement interval(shots_sum)
• Laser Temperature(laser_temp)
• Aerosol backscatter coefficient at 355 nm(backscatter)
• Filter Temperature(filter_temp)
• time(time)
• Sum of raw backscatter counts per bin prior to ANY corrections.(total_counts)
• Distance from leading edge of first range bin to the center of each bin .(range_bins)
• Repetition rate, or Trigger Frequency of the laser(trigger_freq)
• Time offset of tweaks from base_time(time_offset)
• Voltage level which operates the A_D card and the detector(voltage_5)
• Width of range-bins calculated from range_bin_time(range_bin_width)
• Assumed zero-range bin number\(assumed_zero_range_bin)
• Number of laser shots recorded(shots_summed)
• Instrument Temperature(instrument_temp)
• effective range offset due to poor sync between laser firing and A/D trigger.(range_offset)
• base time(base_time)
• Laser output energy per pulse(energy_monitor)
• Amount of time the scalar lags behind the sync trigger(scalar_sync_offset)
• Amount of time laser pulse lags behind the scalar trigger(laser_scalar_sync_offset)
• Voltage level which operates the A/D card and the detector(voltage_05)
• Time in nanoseconds for each range bin of multichannel scalar card.(range_bin_time)

• Time offset of tweaks from base_time(time_offset)
• Height of Center of Each Range Bin(Heights)
• MPL Cloth et al. Algorithm Significance Mask(SigniMaskMplCloth)
• base time(base_time)

• base time(base_time)
• Time offset of tweaks from base_time(time_offset)
• Height of Center of Each Range Bin(Heights)
• MPL Cloth et al. Algorithm Cloud Mask(CloudMaskMplCloth)

TWP/SMET/C1 - Reprocess: Tipping bucket rain gauge added

A tipping bucket rain gauge was added to the TWP.C1 SMET suite of instruments on 20061017. 
 Effective 20060926, two new variables (count and rain amount) were added to the end of 
the twpsmet60sC1.b1 datastream.  Between 9/26 and 10/17, the data for these two variables 
are filled with zeros.  Users should not use the data during this period as the zeros 
are not representative of the rain fall at the site.  When reprocessing of this datastream 
occurs these variables will be added for the 19961009-20060926 and data from 
19961009-20061017 will be filled with -9999 (missing).

• base time(base_time)

TWP/MMCR/C1 - Reprocess: Height Error

A timing error was found in the PIRAQ MMCR's.  It resulted in recorded heights being too 
high for each radar mode by the following amounts: 
Mode 1: 24.8756 m too high
Mode 2: 25.6249 m too high
Mode 3: 33.1176 m too high
Mode 4: 33.1176 m too high
Range gate spacing was not affected.

• Array of heights for each power(heights)

• Height of Center of Each Range Bin(Heights)

• Raw data stream - documentation not supported(raw)

TWP/MMCR/C1 - Error in recorded heights

An error in MMCR configuration resulted in a timing error.  This caused erroneous height 
values (too large) to be recorded in the data files.

• Array of heights for each power(heights)

• Height of Center of Each Range Bin(Heights)

• Raw data stream - documentation not supported(raw)