The RL operates by transmitting pulses of laser radiation and recording radiation backscattered from the atmosphere as a function of time to provide range information similar to a radar system. The return signal contains a strong elastically scattered component due to scattering from clouds, aerosols, and molecular Raman Scattering. The return also contains weaker inelastically scattered components that provide chemical-specific information.
As the beam propagates through the cloud, it is strongly attenuated and this often results in a shadowing effect above the cloud. We note that the elastic channels operate at 355 nm, which is in a so-called solar blind region of the spectrum due to absorption of solar radiation by ozone in the stratosphere. As a result, the elastic channels are essentially unaffected to solar radiation.
The nitrogen and water channels are not sensitive to aerosol backscatter, however it is affected by aerosol extinction. The signal will not exhibit a strong return for the cloud base, but the signal is strongly attenuated in the cloud and will exhibit a shadowing effect similar to the elastic return. These channels are also sensitive to solar radiation.
The RL generally runs smoothly with little to no problems. As such, the metrics should appear green for all variables for routine data. When individual variables flag as red (bad data) or grey (missing data), a problem may be ongoing.
The first 4 plots are of various counts using different methods and channels. The first one is the number of photons recorded using the water counts channel, second is the nitrogen counts channel, thirds is the high elastic channel, and fourth is the high depolarization channel. The channel that looks the most promising to monitor is the depolarization counts. You are able to observe cloud boundaries which can be compared to other instruments. You can also see an oscillation in the lower boundary layer. This can be attributed to the AC unit kicking on and off to cool the enclosure. In the example above, cloud cover is noted generally before 0400 UTC.
Shots
The shots should remain fairly constant throughout the day with hourly dips. All values should remain within the bounds, delineated on the plots by the dashed lines form top to bottom at 300 and 250, respectively.
Diagnostics
The four diagnostic plots are helpful in identifying problems with the instrument. The laser pulse energy should remain fairly constant. Any dip greater than about 50 mJ is worth mentioning in your DQA. The RH often swings during the winter months, but should appear reasonable. The temperature variables should remain fairly constant, with temps1-4 being the most flatlined. Note that small dips (such as with temp1 in blue) are acceptable. Also note that temp2 (green) is reading the exact same value as temp 3 (red). Indeed, they are flatlined as expected.
The comparison plots are helpful in identifying periods where cloud cover is expected to show up on the RL plots. Note the nice consistency between instruments with some sort of cloud cover before 0400 UTC.
List of past problems for this instrument that DO need to be mentioned in your DQA's:
Instrument out of alignment
The most frequent problem from which the RL suffers are due to a misalignment of the mirrors inside the instrument. This has been known to occur after particularly heavy thunderstorms and after strong earthquakes (because yes, that is a problem in Oklahoma!) The instrument sometimes even gets out of alignment during the middle of the day for no apparent reason. When an alignment issue is suspected, the metrics may indicate so by flagging the data in yellow. The best way to confirm an alignment issue is by looking at the data.
Alignment issues are identifiable by a clear lack of strong signal surrounded by sharp phase shifts. Some alignment problems don't start with such an abrupt shift but rather with a prolonged (e.g. maybe an hour) of data that appears to be fading out. Note both telltale signs of an alignment problem noted in the plot above. Any period of suspected misalignment should be mentioned in your DQA, with periods greater than 24 hours requiring a DQPR submittal.
Degraded Data
The data should not appear degraded with frequent periods of jumpy or missing data. The source of the degraded data above was a malfunction in the data acquisition system, ultimately owing to a problem with the power supply to one of the system racks. See DQPR 5338 or DQR D160620.1 for more information.
Bugs!
The RL experienced what looked to be a case of the mirrors out of alignment, but it turned out to be a layer of bugs and dew covering the window.