DQR ID | Subject | Data Streams Affected | Data Quality Metric |
---|---|---|---|
D000111.4 | Reprocess:SGP BLC reprocessing status | sgpblcC1.a1, sgpblcprofC1.a1 | Suspect |
D000204.6 | SGP/BLC - Retraction of D000111.4 BLC offset | sgpblcC1.a1, sgpblcprofC1.a1 | Suspect |
D020227.8 | SGP/MPL/C1 - Data missing due to hardware failures | sgpmplcbh1scottC1.c1, sgpmplC1.a1, sgpmplnor1campC1.c1 | Missing |
D020927.1 | SGP/ARSCL/C1 - ARSCL Cloud Bases and Low-level reflectivities | sgparsclcbh1clothC1.c1, sgparsclbnd1clothC1.c1, sgparscl1clothC1.c1 | Suspect |
D031119.1 | SGP/RL/C1 - Alternatively processed data available | sgp10rlprofbe1turnC1.c0, sgp10rlprofbe1turnC1.c1 | Does not affect quality |
D040424.1 | SGP/MPL/C1 - Signal degrading | sgpmplC1.a1, sgpmplnor1campC1.c1 | Suspect |
D040426.4 | SGP/MPL/C1 - Detector Failure | sgpmplC1.a1, sgpmplnor1campC1.c1 | Incorrect |
D040525.18 | SGP/RL/C1 - Metadata errors | sgp10rlprofdep1turnC1.c1, sgp10rlprofbe1turnC1.c1 | Does not affect quality |
D040525.22 | SGP/BLC/C1 - Metadata errors | sgpblcC1.a1 | Does not affect quality |
D040525.23 | SGP/BLC/C1 - Metadata errors | sgpblcprofC1.a1 | Does not affect quality |
D040525.28 | SGP/MPL/C1 - Metadata errors | sgpmplC1.a1, sgpmplnor1campC1.c1 | Does not affect quality |
D040525.29 | SGP/MPL/C1 - Metadata errors | sgpmplcbh1scottC1.c1 | Does not affect quality |
D040706.4 | SGP/MPL/C1 - Reduced detection sensitivity | sgpmplnor1campC1.c1, sgpmplC1.a1 | Suspect |
D041109.1 | SGP/RL/C1 - Decreased sensitivity | sgp10rlprofbe1turnC1.c0, sgp10rlprofdep1turnC1.c1, sgp10rlprofbe1turnC1.c1 | Suspect |
D050222.2 | SGP/MMCR/C1 - Power supply failure | sgparsclbnd1clothC1.c1, sgparscl1clothC1.c1 | Incorrect |
D050421.14 | SGP/MPL/C1 - Sensor Calibration | sgpmplC1.a1 | Incorrect |
D050914.3 | SGP/MPL/C1 - Instrument offline | sgpmplnor1campC1.c1, sgpmplC1.a1 | Missing |
D060327.2 | SGP/MPL/C1 - Intermittent Double Pulse from MPL laser | sgpmplC1.a1 | Does not affect quality |
D071203.3 | SGP/MPL/C1 - Scope temperature incorrect | sgpmplpolavgC1.s1, sgpmplpolavgC1.c1, sgpmplpolC1.b1 | Incorrect |
D080829.3 | SGP/RL/C1 - Degraded sensitivity in WFOV channels | sgprlprofmerge1turnC1.c0 | Suspect |
D080909.1 | SGP/RL/C1 - No liquid water data in RLPROFmerge | sgprlprofmerge1turnC1.c0 | Missing |
D090122.2 | SGP/RL/C1 - Invalid mode 0 data | sgprlprofmerge1turnC1.c0 | Incorrect |
D100519.1 | SGP/ARSCL/C1 - Ceilometer not used during processing | sgparsclcbh1clothC1.c1, sgparsclbnd1clothC1.c1, sgparscl1clothC1.c1 | Suspect |
D110409.1 | SGP/RL/C1 - Incorrect time array | sgp10rlprofbe1turnC1.c0, sgp10rlprofdep1turnC1.c1, sgprlprofmerge1turnC1.c0, sgp10rlprofbe1turnC1.c1 | Incorrect |
D110720.1 | SGP/RL/C1 - Malfunction in WFOV data acquisition | sgp10rlprofbe1turnC1.c0, sgprlprofmerge1turnC1.c0 | Incorrect |
D111004.1 | SGP/RL/C1 - Frequent intermittent drop-outs in the WFOV photon counting signals | sgprlprofmerge1turnC1.c0 | Incorrect |
D111004.3 | SGP/RL/C1 - Bad shot count data | sgprlprofmerge1turnC1.c0, sgp10rlprofdep1turnC1.c1 | Incorrect |
D120228.1 | SGP/MPLCMASK/C1 - Cloud layer metadata misleading | sgp30smplcmask1zwangC1.c1 | Does not affect quality |
D140221.8 | SGP/RL/C1 - Reprocessing Notice (RID 1026) | sgprlprofmerge1turnC1.c0 | Does not affect quality |
D140326.7 | SGP/RLPROF/C1 - Reduced signal due to partially closed laser shutter | sgp10rlprofbe1turnC1.c0, sgp10rlprofdep1turnC1.c1, sgp10rlprofbe1turnC1.c1, sgprlprofmerge1turnC1.c0 | Suspect |
D140416.3 | SGP/RLPROF/C1 - Reduced SNR due to partial laser blockage | sgprlprofmerge1turnC1.c0, sgp10rlprofdep1turnC1.c1 | Suspect |
D140611.16 | SGP/MPLCMASK/C1 - Reprocessing Notice (RID 1136) | sgp30smplcmask1zwangC1.c1 | Does not affect quality |
D140619.4 | SGP/RLPROF/C1 - Invalid data due to hatch closure | sgprlprofmerge1turnC1.c0 | Incorrect |
D160212.3 | SGP - Data System Upgrades: Data Missing | sgpceilC1.b1 | Missing |
D970408.3 | Continuing signal degradation | sgpmplcbh1scottC1.c1, sgpmplC1.a1 | Suspect |
D980331.1 | Instrument misalignment report | sgpmplnor1campC1.c1 | Suspect |
D980402.1 | Laser Output Energy Monitor at Zero | sgpmplnor1campC1.c1 | Suspect |
D980402.2 | Laser Output Energy Monitor at Zero | sgpmplnor1campC1.c1 | Suspect |
D990224.1 | SGP/MPL - Missing data due to blown detector | sgpmplnor1campC1.c1, sgpmplcbh1scottC1.c1, sgpmplC1.a1 | Missing |
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
04/01/1994 | 0000 | 06/30/1999 | 2359 | Suspect |
Subject: | Reprocess:SGP BLC reprocessing status |
DataStreams: | sgpblcC1.a1, sgpblcprofC1.a1 |
Description: | The BLC data was the subject of a reprocessing effort last summer in support of the ARSCL effort. As a result three distinct windows of data with varying levels of processing have been created. 1) 940401-961031 - not reprocessed. This data has a 110m offset in the reported cloud base height (see P980831.1). No sgpblcprofC1.a1 data available. Reprocessing required. 2) 961101-990630 - reprocessed. The 110m offset was corrected in this data and the blcprof data were created. This data still contains the defunct field 'operational_state' which was determined to be useless and was removed in later data. This data will be reprocessed at a later date to remove the operational_state field to create a continuity with the current data. 3) 990701-present - reprocessed/processed without 'operational_state' field. Offset has been corrected or no longer exists. The format of this data is the target for the previous two data windows. |
Measurements: | sgpblcprofC1.a1:
sgpblcC1.a1:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
04/01/1994 | 0000 | 02/03/2000 | 2359 | Suspect |
Subject: | SGP/BLC - Retraction of D000111.4 BLC offset |
DataStreams: | sgpblcC1.a1, sgpblcprofC1.a1 |
Description: | D000111.4 reported on the reprocessing status of the SGP BLC data and indicated which time periods had been reprocessed to remove a 110m offset. First error: the offset was actually 122m, not 110m. Second error: an error in the reprocessing algorithm resulted in the offset not being removed. This DQR retracts D000111.4. All BLC data processed to date still have a 122m offset. That is the cloud base height reported in the data stream is 122m too high. Data processed after 20000204 with version 7.0 of the algorithm (recorded in the header of the data file) do not contain the offset. The data processed through 20000204 will be reprocessed when resources are available. |
Measurements: | sgpblcprofC1.a1:
sgpblcC1.a1:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
08/10/2001 | 0000 | 10/29/2001 | 2033 | Missing |
Subject: | SGP/MPL/C1 - Data missing due to hardware failures |
DataStreams: | sgpmplcbh1scottC1.c1, sgpmplC1.a1, sgpmplnor1campC1.c1 |
Description: | The MPL instrument was out of service during the time range specified due to hardware failures. Data during this period are missing and unrecoverable. |
Measurements: | sgpmplcbh1scottC1.c1:
sgpmplC1.a1:
sgpmplnor1campC1.c1:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
12/01/1996 | 0000 | 02/04/2000 | 2359 | Suspect |
Subject: | SGP/ARSCL/C1 - ARSCL Cloud Bases and Low-level reflectivities |
DataStreams: | sgparsclcbh1clothC1.c1, sgparsclbnd1clothC1.c1, sgparscl1clothC1.c1 |
Description: | Prior to February 4, 2000, the ARSCL data set incorporated data from the Beaufort Laser Ceilometer as one of its inputs. Because of the BLC's high spatial resolution, this data was often chosen by ARSCL as the "CloudBaseBestEstimate" for boundary layer clouds. It was subsequently determined that the BLC cloud base was biased, with the BLC reporting cloud base heights that are 122 meters too high. The bias error will be corrected when the entire ARSCL data set is reprocessed as part of release_4. (The release version number is included the the netCDF global comments). This reprocessing will also include a small correction the the MMCR near-field reflectivities. This correction is less than 1 dB except for hydrometers within 200 meters of the surface. Thanks to Roger Marchand for helping bracket this problem. |
Measurements: | sgparsclbnd1clothC1.c1:
sgparscl1clothC1.c1:
sgparsclcbh1clothC1.c1:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
05/15/2002 | 0000 | 06/25/2002 | 2359 | Does not affect quality |
Subject: | SGP/RL/C1 - Alternatively processed data available |
DataStreams: | sgp10rlprofbe1turnC1.c0, sgp10rlprofbe1turnC1.c1 |
Description: | Reprocessed ARM Raman Lidar water vapor data is available for the IHOP IOP period 20020515 to 20020625 at http://iop.archive.arm.gov/arm-iop/2002/sgp/ihop/turner-raman/ The data were reprocessed by Dave Turner to apply an improved near-field correction ("overlap correction") to the water vapor data collected by the Raman lidar during IHOP. These files contain only the water vapor data; users who require the aerosol and cloud fields from this instrument will need to retrieve the regular ARM data sets. |
Measurements: | sgp10rlprofbe1turnC1.c1:
sgp10rlprofbe1turnC1.c0:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
09/25/2002 | 0000 | 01/16/2003 | 2359 | Suspect |
Subject: | SGP/MPL/C1 - Signal degrading |
DataStreams: | sgpmplC1.a1, sgpmplnor1campC1.c1 |
Description: | The MPL viewport window was blown off during a storm on 2002/09/25. The MPL received a soaking of rain. Following this event, although site operations cleaned and dried the optics, the lidar performance continued to degrade over the next few months. Although initially suitable for cloud detection, by Dec 10th the lidar was providing useful results only during the day (oddly enough). By Jan 16, the detector was dead. It is not recommended to depend on night-time cloud base heights after Dec. 10 2002. It is not recommended to use any of the data after 9/25 for aerosol retrievals. |
Measurements: | sgpmplC1.a1:
sgpmplnor1campC1.c1:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
01/16/2003 | 0000 | 01/31/2003 | 2359 | Incorrect |
Subject: | SGP/MPL/C1 - Detector Failure |
DataStreams: | sgpmplC1.a1, sgpmplnor1campC1.c1 |
Description: | The detector failed following a period of data quality degradation. The MPL was replaced on 1/31/2003. |
Measurements: | sgpmplC1.a1:
sgpmplnor1campC1.c1:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
03/01/1998 | 0000 | 03/17/2003 | 2359 | Does not affect quality |
Subject: | SGP/RL/C1 - Metadata errors |
DataStreams: | sgp10rlprofdep1turnC1.c1, sgp10rlprofbe1turnC1.c1 |
Description: | The latitude, longitude and altitude of the Raman Lidar were incorrectly entered into the ARM database. The correct location of the SGP.C1 Raman Lidar is: Lat: 36.609N Lon: 97.487W Alt: 311m |
Measurements: | sgp10rlprofdep1turnC1.c1:
sgp10rlprofbe1turnC1.c1:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
08/11/1994 | 0000 | 05/23/2000 | 2359 | Does not affect quality |
Subject: | SGP/BLC/C1 - Metadata errors |
DataStreams: | sgpblcC1.a1 |
Description: | The latitude, longitude and altitude of the Belfort Laser Ceilometer were incorrectly entered into the ARM database. The correct location of the SGP.C1 BLC was: Lat: 36.606N Lon: 97.485W Alt: 316m |
Measurements: | sgpblcC1.a1:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
11/01/1996 | 0000 | 05/23/2000 | 2359 | Does not affect quality |
Subject: | SGP/BLC/C1 - Metadata errors |
DataStreams: | sgpblcprofC1.a1 |
Description: | The latitude, longitude and altitude of the Belfort Laser Ceilometer were incorrectly entered into the ARM database. The correct location of the SGP.C1 BLC was: Lat: 36.606N Lon: 97.485W Alt: 316m |
Measurements: | sgpblcprofC1.a1:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
05/01/1996 | 0000 | 01/19/2000 | 2359 | Does not affect quality |
Subject: | SGP/MPL/C1 - Metadata errors |
DataStreams: | sgpmplC1.a1, sgpmplnor1campC1.c1 |
Description: | The latitude, longitude and altitude of the Micropulse Lidar (MPL) were incorrectly entered into the ARM database. The correct location of the SGP.C1 MPL is: Lat: 36.606N Lon: 97.485W Alt: 316m |
Measurements: | sgpmplC1.a1:
sgpmplnor1campC1.c1:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
04/10/1994 | 0000 | 01/19/2000 | 2359 | Does not affect quality |
Subject: | SGP/MPL/C1 - Metadata errors |
DataStreams: | sgpmplcbh1scottC1.c1 |
Description: | The latitude, longitude and altitude of the Micropulse Lidar (MPL) were incorrectly entered into the ARM database. The correct location of the SGP.C1 MPL is: Lat: 36.606N Lon: 97.485W Alt: 316m |
Measurements: | sgpmplcbh1scottC1.c1:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
07/01/2004 | 1500 | 07/07/2004 | 0350 | Suspect |
07/23/2004 | 2200 | 09/10/2004 | 2100 | Suspect |
Subject: | SGP/MPL/C1 - Reduced detection sensitivity |
DataStreams: | sgpmplnor1campC1.c1, sgpmplC1.a1 |
Description: | During the time periods indicated, the laser power supply was low. This resulted in compromised detection sensitivity, particularly for thin clouds and/or during daylight hours. That is, some clouds may not have been identified. The low laser power would not have resulted in false positives. |
Measurements: | sgpmplC1.a1:
sgpmplnor1campC1.c1:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
01/01/2002 | 0000 | 09/17/2004 | 1745 | Suspect |
Subject: | SGP/RL/C1 - Decreased sensitivity |
DataStreams: | sgp10rlprofbe1turnC1.c0, sgp10rlprofdep1turnC1.c1, sgp10rlprofbe1turnC1.c1 |
Description: | The sensitivity of the Raman Lidar degraded significantly beginning in late 2001. Between May and September 2004, the electronics were upgraded and the telescope was refurbished resulting in sensitivity better than when the instrument system was first installed. A detailed technical report describing the effects of the signal degradation and the steps taken to correct the problem is being written. In the interim, contact Dave Turner (dave.turner@pnl.gov) for more information. |
Measurements: | sgp10rlprofdep1turnC1.c1:
sgp10rlprofbe1turnC1.c1:
sgp10rlprofbe1turnC1.c0:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
01/16/2005 | 0030 | 02/11/2005 | 2115 | Incorrect |
Subject: | SGP/MMCR/C1 - Power supply failure |
DataStreams: | sgparsclbnd1clothC1.c1, sgparscl1clothC1.c1 |
Description: | A power supply failed in the MMCR's receiver. During the period of this DQR, the radar would appear to work but the calibration is probably incoorect during good portions of this time. The power supply was replaced and normal operation resumed at 2115 on 02/11/2005. |
Measurements: | sgparsclbnd1clothC1.c1:
sgparscl1clothC1.c1:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
11/03/2004 | 0000 | 02/23/2005 | 2300 | Incorrect |
Subject: | SGP/MPL/C1 - Sensor Calibration |
DataStreams: | sgpmplC1.a1 |
Description: | The Energy Monitor records the value of the laser energy. During the time in question, the laser energy exceed the maximum value in the calibration table for the energy monitor. In other words, the value is pegged. This condition does not affect the backscatter signal. But it will prevent users from normalizing the backscatter signal to the laser output. |
Measurements: | sgpmplC1.a1:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
07/07/2004 | 0350 | 07/23/2004 | 2150 | Missing |
Subject: | SGP/MPL/C1 - Instrument offline |
DataStreams: | sgpmplnor1campC1.c1, sgpmplC1.a1 |
Description: | Instrument was taken offline due to a failure of the laser power supply. Data are missing and unrecoverable. |
Measurements: | sgpmplC1.a1:
sgpmplnor1campC1.c1:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
02/01/2005 | 0000 | 08/09/2006 | 1159 | Does not affect quality |
Subject: | SGP/MPL/C1 - Intermittent Double Pulse from MPL laser |
DataStreams: | sgpmplC1.a1 |
Description: | When Spectra Physics discontinued support for their laser diode power supply, an alternative was needed 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. |
Measurements: | sgpmplC1.a1:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
06/29/2007 | 1900 | 08/06/2007 | 1900 | Incorrect |
Subject: | SGP/MPL/C1 - Scope temperature incorrect |
DataStreams: | sgpmplpolavgC1.s1, sgpmplpolavgC1.c1, sgpmplpolC1.b1 |
Description: | The scope_temp started to jump around on 6/29 at about 19:00 GMT between 24-32C. Then ~03:00 GMT on 6/30 the temperature exceeded the MAX flag value of 40C and was fluctuating between 150-225C. Temp probe connection was found to be loose and was reseated 20070806. Ignore scope temp data and assume values are valid. |
Measurements: | sgpmplpolavgC1.s1:
sgpmplpolavgC1.c1:
sgpmplpolC1.b1:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
03/07/2008 | 0000 | 03/10/2008 | 1500 | Suspect |
04/09/2008 | 1800 | 04/10/2008 | 1500 | Suspect |
03/25/2008 | 0500 | 04/04/2008 | 1600 | Suspect |
Subject: | SGP/RL/C1 - Degraded sensitivity in WFOV channels |
DataStreams: | sgprlprofmerge1turnC1.c0 |
Description: | The sensitivity of all the wide field-of-view (WFOV) channels was abnormally low due a malfunction of the filter wheel. The filter wheel for the WFOV channels did not rotate into position properly and thus partially obscured the return light. |
Measurements: | sgprlprofmerge1turnC1.c0:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
09/06/2006 | 0000 | 03/04/2008 | 2359 | Missing |
Subject: | SGP/RL/C1 - No liquid water data in RLPROFmerge |
DataStreams: | sgprlprofmerge1turnC1.c0 |
Description: | From 20060906 to 20080304 the liquid water channel (LWC) was disabled due to the removal of its photomultiplier tube (PMT). During this period the signals recorded in the sgprlC1.a0 files for the LWC contain invalid data, and so the decision was made not have the rlprof_merge vap process the LWC data. As a result, the sgprlprofmerge1turnC1.c0.*.cdf files contain NO LWC fields (variables or attributes) during this period. Do not attempt to read any fields (variables or attributes) associated with the liquid water channel in the sgprlprofmerge1turnC1.c0.*.cdf files between the dates of 20060906 through 20080304. |
Measurements: | sgprlprofmerge1turnC1.c0:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
11/12/2008 | 0000 | 01/13/2009 | 0000 | Incorrect |
Subject: | SGP/RL/C1 - Invalid mode 0 data |
DataStreams: | sgprlprofmerge1turnC1.c0 |
Description: | On 20081112 the filter wheel for the wide field-of-view (WFOV) channel was incorrectly rotated. The net effect was that we were recording neutral density filter data when we should have been collecting data with the channels completely blocked (mode 0 data). As a result, the WFOV mode 0 data contains contributions from the pulse return and the solar background that should not be present. The mode 0 data is used in the rlprof_merge VAP to remove the electronic background level from the analog signal. After the problem was identified the filter wheel was set back to its proper rotation on 20090112. A work-around has been implemented in the rlprof_merge VAP to handle the lack of valid mode 0 during the affected period. The work-around involves computing the electronic background from pre-pulse data during nighttime periods only. With this technique we are not able to estimate the range-dependence of the electronic backgound, as we did before. However, this range dependence is typically quite weak, and so the impact on the rlprof_merge output is expected to be minimal. |
Measurements: | sgprlprofmerge1turnC1.c0:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
11/20/2009 | 0000 | 12/31/2009 | 2359 | Suspect |
Subject: | SGP/ARSCL/C1 - Ceilometer not used during processing |
DataStreams: | sgparsclcbh1clothC1.c1, sgparsclbnd1clothC1.c1, sgparscl1clothC1.c1 |
Description: | The ceilometer was not used during processing due to a ceilometer data format change that ARSCL did not handle properly. As a result, cloud boundaries in the lowest several kilometers may be less accurate than usual, as they are based solely on the micropulse lidar and millimeter cloud radar. |
Measurements: | sgparsclbnd1clothC1.c1:
sgparscl1clothC1.c1:
sgparsclcbh1clothC1.c1:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
03/27/2011 | 0100 | 03/29/2011 | 1300 | Incorrect |
Subject: | SGP/RL/C1 - Incorrect time array |
DataStreams: | sgp10rlprofbe1turnC1.c0, sgp10rlprofdep1turnC1.c1, sgprlprofmerge1turnC1.c0, sgp10rlprofbe1turnC1.c1 |
Description: | On March 27 2011 at 0100 GMT the Raman lidar's instrument computer automatically advanced it's time by one hour (transition to daylight savings time). The problem was eventually fixed on March 29 2011 at 1300 when the clock was set back one hour to the correct time. The ingest experienced problems when the clock was set back one hour. The time arrays in the following files are set one hour ahead of what they should be: 1. sgprlC1.a0.20110327.000001.cdf for profile indices equal to or greater than 355 2. all of sgprlC1.a0.20110327.120001.cdf 3. all of sgprlC1.a0.20110328.134549.cdf 4. all of sgprlC1.a0.20110329.000005.cdf 5. sgprlC1.a0.20110329.120005.cdf for profile indices less than or equal to 72 Also, the time arrays in sgprlC1.a0.20110329.120005.cdf between profile indices 73 through 641 are incorrect. In this case, the offset varies approximately linearly with profile index from 1 hour at index 73 to 0 at index 641. The ingest apparently introduced some unphysical variations in time in this part of the file. |
Measurements: | sgp10rlprofdep1turnC1.c1:
sgprlprofmerge1turnC1.c0:
sgp10rlprofbe1turnC1.c1:
sgp10rlprofbe1turnC1.c0:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
05/31/2011 | 1400 | 08/23/2011 | 2011 | Incorrect |
Subject: | SGP/RL/C1 - Malfunction in WFOV data acquisition |
DataStreams: | sgp10rlprofbe1turnC1.c0, sgprlprofmerge1turnC1.c0 |
Description: | A malfunction in the data acquisition hardware resulted in corrupted data in the wide-field-of-view (WFOV) nitrogen, water vapor and elastic channels. The problem is so serious as to yield these signals useless during the period covered by this DQR. Do not use any data products derived from the WFOV raw signals during the period covered by this DQR. This includes water vapor mixing ratio, aerosol scattering ratio, and aerosol extinction. The narrow-field-of-view (NFOV)channels are unaffected by this problem. So data products derived from only the NFOV channel should be okay. These include the 'high' channel signals from the merge VAP, depolarization and temperature. |
Measurements: | sgprlprofmerge1turnC1.c0:
sgp10rlprofbe1turnC1.c0:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
05/31/2011 | 1330 | 08/19/2011 | 1900 | Incorrect |
Subject: | SGP/RL/C1 - Frequent intermittent drop-outs in the WFOV photon counting signals |
DataStreams: | sgprlprofmerge1turnC1.c0 |
Description: | Beginning suddenly, near 1330 UTC on 31 May 2011, the liquid water and all three WFOV channels began showing intermittent and frequent drop-outs in the photon counting signals. These drop-outs were periods when the signal would momentarily fade and then come back. This problem, which was traced to a malfunction of the Licel data recorders, occurred at irregular intervals and with such frequency as to render the data from the affected channels useless. This problem persisted until repairs were made to the Licel transient recorders on 19 August 2011. Although only the WFOV channels (and liquid water channel) were affected, the aerosol and water vapor mixing ratio VAPs are computed by combining NFOV and WFOV channels. Thus, all of these higher level data products were adversely impacted by the drop-out problem. The NFOV data in the sgprlC1.a0 and sgprlprofmerge1turnC1.c0 datastreams were unaffected by the "drop-out" problem. These signals could be used to compute aerosol optical properties and water vapor mixing ratio. |
Measurements: | sgprlprofmerge1turnC1.c0:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
09/29/2011 | 0000 | 10/06/2011 | 1500 | Incorrect |
07/15/2011 | 1000 | 07/15/2011 | 1400 | Incorrect |
05/03/2012 | 1430 | 06/12/2012 | 1930 | Incorrect |
08/08/2011 | 1300 | 09/15/2011 | 0000 | Incorrect |
Subject: | SGP/RL/C1 - Bad shot count data |
DataStreams: | sgprlprofmerge1turnC1.c0, sgp10rlprofdep1turnC1.c1 |
Description: | The number of laser pulses averaged per profile, or shot count, exhibited erratic behavior during the periods in question. The values reported in the sgprlC1.a0 datastream were incorrect and varied radically from profile to profile. Shot counts are used in the Merge VAP to compute photon count rates, which are then used by all the other RL VAPs. Thus, the shot count problem renders all of the RL VAPs bad or suspect during the periods in question. It appears that the problem was caused as the signal on the line between two triggering units got noisier over time, causing the second unit to occasionally trigger on noise. The second unit triggers the Licel electronics. So the false triggering on the second unit caused false shot count readings. On 6 October 2011 the trigger level was adjusted by the on-site technician, and this solved the problem. On 3 May 2012 the DG535 pulse generator, which is used to trigger the Licel data recorders, was swapped out with a spare. After installation of the spare, the system started recording erroneous values of shot counts. The problem was fixed on 12 June 2012 when the on-site tech increased trigger level on the DG535. |
Measurements: | sgp10rlprofdep1turnC1.c1:
sgprlprofmerge1turnC1.c0:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
05/01/1996 | 0000 | 08/09/2006 | 2359 | Does not affect quality |
Subject: | SGP/MPLCMASK/C1 - Cloud layer metadata misleading |
DataStreams: | sgp30smplcmask1zwangC1.c1 |
Description: | The comment in the header for cloud_base_layer indicates that a value of -1 indicates that no cloud is detected. For the specified time range, a value of 0 indicates that no cloud is detected. Values greater than zero indicate cloudy conditions, otherwise it is clear. |
Measurements: | sgp30smplcmask1zwangC1.c1:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
05/03/2012 | 0000 | 01/28/2014 | 0000 | Does not affect quality |
Subject: | SGP/RL/C1 - Reprocessing Notice (RID 1026) |
DataStreams: | sgprlprofmerge1turnC1.c0 |
Description: | See below for details of reprocessing that was completed on 20140822. Original DQR category:3 (Yellow, Suspect ). ----------------------------------------------------------- Regions where photon counting rates exceed 20 MHz are 37.5 meters too high. Correct data by shifting down 37.5 meters. Additional information: The detection system in the RL uses Licel data recorders. These recorders provide simultaneous measurements of analog voltage and photon counts from the photo multiplier tubes. The analog signal has an inherent delay relative to the photon counting signal, which is corrected for in the rlprofmerge VAP. The delay parameter is determined through offline analysis by the instrument mentor, and then inputted into a configuration file that is used by the VAP. During the effected period, the delay parameter for the narrow-field-of-view elastic channel was incorrect. As a result, the analog signal leads the photon counting signal by 5 range bins (5X7.5m = 37.5m). Photon counting rates that are outputted by the rlprofmerge VAP use the analog signals in regions where the photon counting rates exceed 20 MHz. So the counting rate data in these regions are (incorrectly) shifted downward by 37.5 m (i.e. -37.5m). |
Measurements: | sgprlprofmerge1turnC1.c0:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
03/25/2014 | 1500 | 03/26/2014 | 1220 | Suspect |
Subject: | SGP/RLPROF/C1 - Reduced signal due to partially closed laser shutter |
DataStreams: | sgp10rlprofbe1turnC1.c0, sgp10rlprofdep1turnC1.c1, sgp10rlprofbe1turnC1.c1, sgprlprofmerge1turnC1.c0 |
Description: | The laser shutter was partially closed during the period in question. This resulted in a reduction in the sensitivity of all detection channels. |
Measurements: | sgprlprofmerge1turnC1.c0:
sgp10rlprofdep1turnC1.c1:
sgp10rlprofbe1turnC1.c1:
sgp10rlprofbe1turnC1.c0:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
03/25/2014 | 1500 | 03/26/2014 | 1215 | Suspect |
Subject: | SGP/RLPROF/C1 - Reduced SNR due to partial laser blockage |
DataStreams: | sgprlprofmerge1turnC1.c0, sgp10rlprofdep1turnC1.c1 |
Description: | The laser output was partially blocked. This resulted in reduced SNR in all detection channels. |
Measurements: | sgp10rlprofdep1turnC1.c1:
sgprlprofmerge1turnC1.c0:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
08/09/2006 | 0000 | 06/06/2014 | 2359 | Does not affect quality |
Subject: | SGP/MPLCMASK/C1 - Reprocessing Notice (RID 1136) |
DataStreams: | sgp30smplcmask1zwangC1.c1 |
Description: | See below for details of reprocessing that was completed on 20140807. Original DQR category: 4 (Red, Incorrect). ----------------------------------------------------------- Linear depolarization ratio calculation incorrect in the VAP processing code. |
Measurements: | sgp30smplcmask1zwangC1.c1:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
06/18/2014 | 1910 | 06/19/2014 | 2145 | Incorrect |
Subject: | SGP/RLPROF/C1 - Invalid data due to hatch closure |
DataStreams: | sgprlprofmerge1turnC1.c0 |
Description: | The outgoing beam was completely blocked by the hatch. As a result, the data contain no valid atmospheric signals. |
Measurements: | sgprlprofmerge1turnC1.c0:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
01/26/2016 | 1800 | 01/27/2016 | 2145 | Missing |
Subject: | SGP - Data System Upgrades: Data Missing |
DataStreams: | sgpceilC1.b1 |
Description: | The data system was undergoing upgrades. Data were lost during this period. |
Measurements: | sgpceilC1.b1:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
03/17/1997 | 0000 | 04/14/1997 | 2359 | Suspect |
Subject: | Continuing signal degradation |
DataStreams: | sgpmplcbh1scottC1.c1, sgpmplC1.a1 |
Description: | Despite recent efforts (970310-970314) by the instrument mentor, signal degradation of the MPL has continued. The degradation has continued to the point that the effective range of the MPL is nearing 10 km. The instrument mentor and PI have concluded that an overhaul of the instrument by the vendor is in order. |
Measurements: | sgpmplcbh1scottC1.c1:
sgpmplC1.a1:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
04/15/1997 | 0000 | 09/10/1997 | 0000 | Suspect |
Subject: | Instrument misalignment report |
DataStreams: | sgpmplnor1campC1.c1 |
Description: | A low-resolution (300 m) MPL system (unit number 04) was installed at the SGP site in April '97 upon the laser diode failure of the 02 unit in March. Calibration of this instrument in August found that the optics were misaligned causing a near range focusing error in the data. Calibration files produced for this data, while acceptable, do not completely correct for the problem. As a result, aerosol property retrievals using this data are not suggested. Cloud boundary heights, though appear satisfactory. This system was removed from SGP in early September |
Measurements: | sgpmplnor1campC1.c1:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
04/25/1997 | 2123 | 04/28/1997 | 1459 | Suspect |
Subject: | Laser Output Energy Monitor at Zero |
DataStreams: | sgpmplnor1campC1.c1 |
Description: | Energy monitor reading for laser output is at zero for intermittant one-minute averaged shots during this flagged data period. From the lidar equation progressing to normalized relative backscatter the laser energy is required and is a denominator. Therefore a value of zero will render the product as infinite. Shots where this has taken place are left as zeros. It is suggested that the time period 19970425 2123 - 19970428 1459 be avoided for any quantitative analysis. |
Measurements: | sgpmplnor1campC1.c1:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
09/02/1997 | 2211 | 09/03/1997 | 1359 | Suspect |
09/07/1997 | 1445 | 09/08/1997 | 1544 | Suspect |
09/10/1997 | 2142 | 09/10/1997 | 2355 | Suspect |
Subject: | Laser Output Energy Monitor at Zero |
DataStreams: | sgpmplnor1campC1.c1 |
Description: | Energy monitor reading for laser output is at zero for intermittant one-minute averaged shots during this flagged data period. From the lidar equation progressing to normalized relative backscatter the laser energy is required and is a denominator. Therefore a value of zero will render the product as infinite. Shots where this has taken place are left as zeros. It is suggested that the time periods 19970902 2211 - 19970903 1359, 19970907 1445 - 19970908 1544, and 19970910 2142 - 19970910 2355 be avoided for any quantitative analysis. |
Measurements: | sgpmplnor1campC1.c1:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
11/11/1998 | 0000 | 01/23/1999 | 2359 | Missing |
Subject: | SGP/MPL - Missing data due to blown detector |
DataStreams: | sgpmplnor1campC1.c1, sgpmplcbh1scottC1.c1, sgpmplC1.a1 |
Description: | Sometime early 11/11 the detector on the MPL-004 blew out. The Detector was replaced by Albert Mendoza. The instrument was operational on Jan. 23, 1999. Link this to P981119.2 that reported the blown detector and the corrective action taken |
Measurements: | sgpmplcbh1scottC1.c1:
sgpmplC1.a1:
sgpmplnor1campC1.c1:
|