DQR ID | Subject | Data Streams Affected |
---|---|---|
D000514.1 | SGP/SIROS/E9 - downwelling PIR | sgpsirosE9.a1, DsgpsirosE9.00 |
D000514.2 | SGP/SIROS/E9 - occasional spikes in readings | sgpsirosE9.a1, DsgpsirosE9.00 |
D020620.56 | SGP/SIROS/E4 - wrong units for broadband irradiance | sgpsirosE4.a1 |
D020620.57 | SGP/SIROS/E7 - wrong units for broadband irradiance | sgpsirosE7.a1 |
D020620.58 | SGP/SIROS/E8 - wrong units for broadband irradiance | sgpsirosE8.a1 |
D020620.59 | SGP/SIROS/E9 - wrong units for broadband irradiance | sgpsirosE9.a1 |
D030606.5 | SGP/SIROS/E9 - Bad Calibrations for MFRSR channels | sgpsirosE9.a1, DsgpsirosE9.00 |
D940922.3 | Improper sds-mode global metadata value | sgpsirosE9.a1 |
D950328.3 | Installation of new data logger PROM | sgpsirosE9.a1 |
D960402.1 | Bad upwelling IR signal, bad upwelling SW signal | sgpsirosE4.a1 |
D960402.4 | Bad upwelling and downwelling IR signal, bad upwelling SW signal | sgpsirosE3.a1 |
D960404.4 | Unshaded PSP dirty domes | sgpsirosE8.a1, sgpsirosE11.a1 |
D960423.2 | SGP/SIROS/E4 - Wrong units for broadband irradiance | sgpsirosE4.a1 |
D960423.3 | SGP/SIROS/E7 - Wrong units for broadband irradiance | sgpsirosE7.a1 |
D960423.4 | SGP/SIROS/E8 - Wrong units for broadband irradiance | sgpsirosE8.a1 |
D960423.5 | SGP/SIROS/E9 - Wrong units for broadband irradiance | sgpsirosE9.a1 |
D960501.2 | SGP/SIROS - wrong units for broadband irradiance | sgpsirosE1.a1, sgpsirosE3.a1, sgpsirosE4.a1, sgpsirosE7.a1, sgpsirosE8.a1, sgpsirosE9.a1, sgpsirosE10.a1, sgpsirosE11.a1, sgpsirosE12.a1, sgpsirosE13.a1, sgpsirosE15.a1, sgpsirosE16.a1, sgpsirosE18.a1, sgpsirosE20.a1, sgpsirosE22.a1, sgpsirosE24.a1 |
D960510.3 | MFRSR out of alignment | sgpsirosE8.a1 |
D960602.1 | SGP/SIROS/E4 - time offset on 960529 | sgpsirosE4.a1 |
D960610.1 | missing MFRSR data site E5 | sgpsirosE5.a1 |
D960613.1 | MFRSR data missing - 960508 to 960612 site E4 | sgpsirosE4.a1 |
D960613.2 | data unrecoverable 950309 to 950515 | sgpsirosE4.a1 |
D960620.1 | E3 - MFRSR out of alignment | sgpsirosE3.a1 |
D960620.2 | E7 - MFRSR out of alignment | sgpsirosE7.a1 |
D960726.1 | bad data - MFRSR - site E9 | sgpsirosE9.a1 |
D960913.7 | time stamp error | sgpsirosE3.a1 |
D960914.1 | time stamp error | sgpsirosE7.a1 |
D960914.15 | time stamp error | sgpsirosE5.a1 |
D960914.16 | time stamp error | sgpsirosE4.a1 |
D960914.2 | time stamp error | sgpsirosE8.a1 |
D960914.3 | time stamp error | sgpsirosE9.a1 |
D970102.2 | MFRSR out of alignment | sgpsirosE7.a1 |
D970321.1 | Tower down | sgpsirosE7.a1 |
D970321.2 | solar tracker inoperative | sgpsirosE4.a1 |
D970624.1 | E9 NIP affected by precipitation | sgpsirosE9.a1 |
D970626.2 | E4 NIP affected by precipitation | sgpsirosE4.a1 |
D990124.2 | SGP/SONDE - Dry bias in sonde RH | sgpsondeB1.00, sgpsondeB1.a0, sgpsondeB1.a1, sgpsondeB4.00, sgpsondeB4.a0, sgpsondeB4.a1, sgpsondeB5.00, sgpsondeB5.a0, sgpsondeB5.a1, sgpsondeB6.00, sgpsondeC1.00, sgpsondeC1.a0, sgpsondeC1.a1, DsgpsondeB1.00, DsgpsondeB1.a0, DsgpsondeB1.a1, DsgpsondeB4.00, DsgpsondeB4.a0, DsgpsondeB4.a1, DsgpsondeB5.00, DsgpsondeB5.a0, DsgpsondeB5.a1, DsgpsondeC1.00, DsgpsondeC1.a0, DsgpsondeC1.a1, sgpsondeptuC1.00, DsgpsondeptuB1.00, DsgpsondeptuB4.00, DsgpsondeptuB5.00, DsgpsondeptuB6.00, DsgpsondeptuC1.00, sgpsondewnpnB1.a0, sgpsondewnpnB1.a1, sgpsondewnpnB4.a0, sgpsondewnpnB4.a1, sgpsondewnpnB5.a0, sgpsondewnpnB5.a1, sgpsondewnpnB6.a0, sgpsondewnpnB6.a1, sgpsondewnpnC1.a0, sgpsondewnpnC1.a1, sgpsondewnprC1.a0, sgpsondewnprC1.a1, sgpsondewrpnB1.00, sgpsondewrpnB1.a0, sgpsondewrpnB1.a1, sgpsondewrpnB4.00, sgpsondewrpnB4.a0, sgpsondewrpnB4.a1, sgpsondewrpnB5.00, sgpsondewrpnB5.a0, sgpsondewrpnB5.a1, sgpsondewrpnB6.00, sgpsondewrpnB6.a0, sgpsondewrpnB6.a1, sgpsondewrpnC1.00, sgpsondewrpnC1.a0, sgpsondewrpnC1.a1, sgpsondewrprB1.00, sgpsondewrprB1.a0, sgpsondewrprB1.a1, sgpsondewrprB4.00, sgpsondewrprB4.a0, sgpsondewrprB4.a1, sgpsondewrprB5.00, sgpsondewrprB5.a0, sgpsondewrprB5.a1, sgpsondewrprC1.00, sgpsondewrprC1.a0, sgpsondewrprC1.a1, DsgpsondeptucalcB1.c1, DsgpsondeptucalcB4.c1, DsgpsondeptucalcB5.c1, DsgpsondeptucalcC1.c1, DsgpsondenogcwrpnB1.c1, DsgpsondenogcwrpnB4.c1, DsgpsondenogcwrpnB5.c1, DsgpsondenogcwrpnC1.c1, DsgpsondenogcptucalcB1.c1, DsgpsondenogcptucalcB4.c1, DsgpsondenogcptucalcB5.c1, DsgpsondenogcptucalcC1.c1 |
Start Date | Start Time | End Date | End Time |
---|---|---|---|
01/12/1994 | 0000 | 10/19/1994 | 1400 |
Subject: | SGP/SIROS/E9 - downwelling PIR |
DataStreams: | sgpsirosE9.a1, DsgpsirosE9.00 |
Description: | The downwelling PIR data for this time period are incorrect because of a wiring problem involving a mix-up of the cable ane preamplifier for this SIROS platform. Further information is given in C941109.3 for P940907.1. |
Measurements: | sgpsirosE9.a1:
DsgpsirosE9.00:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
12/13/1993 | 0000 | 11/01/1994 | 0000 |
Subject: | SGP/SIROS/E9 - occasional spikes in readings |
DataStreams: | sgpsirosE9.a1, DsgpsirosE9.00 |
Description: | Since installation of this SIROS site to the dates specified, negative spikes occurred in the data streams indicated. These spikes were induced by electrical interference from the fence that was used to keep out cattle. The spikes were eliminated by moving the fence further away from the SIROS sensors in October 1994. An assessment by Mike Split on the effects of the spikes indicated that the spikes superimposed on the readings ranged from -10 to -100 W m^-2. As many as 40 per day could occur. As a result of these spikes, the daily average reading of irradiance could be reduced by as much as 1 W m^-2, a half-hour average could be reduced by as much as 2 W m^-2, and a 5-min average could be affected by as much as 5 W m^-2. |
Measurements: | sgpsirosE9.a1:
DsgpsirosE9.00:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
05/08/1995 | 2020 | 01/23/1996 | 2359 |
Subject: | SGP/SIROS/E4 - wrong units for broadband irradiance |
DataStreams: | sgpsirosE4.a1 |
Description: | Headers for SIROS, MFR25m and MFR10m give the units for broadband irradiance as 'watts per square meter' (W/M^2). However, the units are really 'counts'. The fields affected are SIROS: 'hemisp_broadband:units' 'diffuse_hemisp_broadband:units' 'direct_norm_broadband:units' MFR: 'mfr_up_hemisp_broadband:units' This problem has existed since the beginning of the data streams, and was corrected by Jeff Slater on 1/23/96 (see C960314.2 by Ken Yates that closed P960229.2) |
Measurements: | sgpsirosE4.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
05/18/1995 | 0020 | 01/23/1996 | 2359 |
Subject: | SGP/SIROS/E7 - wrong units for broadband irradiance |
DataStreams: | sgpsirosE7.a1 |
Description: | Headers for SIROS, MFR25m and MFR10m give the units for broadband irradiance as 'watts per square meter' (W/M^2). However, the units are really 'counts'. The fields affected are SIROS: 'hemisp_broadband:units' 'diffuse_hemisp_broadband:units' 'direct_norm_broadband:units' MFR: 'mfr_up_hemisp_broadband:units' This problem has existed since the beginning of the data streams, and was corrected by Jeff Slater on 1/23/96 (see C960314.2 by Ken Yates that closed P960229.2) |
Measurements: | sgpsirosE7.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
09/22/1995 | 0000 | 01/23/1996 | 2359 |
Subject: | SGP/SIROS/E8 - wrong units for broadband irradiance |
DataStreams: | sgpsirosE8.a1 |
Description: | Headers for SIROS, MFR25m and MFR10m give the units for broadband irradiance as 'watts per square meter' (W/M^2). However, the units are really 'counts'. The fields affected are SIROS: 'hemisp_broadband:units' 'diffuse_hemisp_broadband:units' 'direct_norm_broadband:units' MFR: 'mfr_up_hemisp_broadband:units' This problem has existed since the beginning of the data streams, and was corrected by Jeff Slater on 1/23/96 (see C960314.2 by Ken Yates that closed P960229.2) |
Measurements: | sgpsirosE8.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
01/12/1994 | 1514 | 01/23/1996 | 2359 |
Subject: | SGP/SIROS/E9 - wrong units for broadband irradiance |
DataStreams: | sgpsirosE9.a1 |
Description: | Headers for SIROS, MFR25m and MFR10m give the units for broadband irradiance as 'watts per square meter' (W/M^2). However, the units are really 'counts'. The fields affected are SIROS: 'hemisp_broadband:units' 'diffuse_hemisp_broadband:units' 'direct_norm_broadband:units' MFR: 'mfr_up_hemisp_broadband:units' This problem has existed since the beginning of the data streams, and was corrected by Jeff Slater on 1/23/96 (see C960314.2 by Ken Yates that closed P960229.2) |
Measurements: | sgpsirosE9.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
03/17/1994 | 0000 | 11/18/1994 | 2359 |
Subject: | SGP/SIROS/E9 - Bad Calibrations for MFRSR channels |
DataStreams: | sgpsirosE9.a1, DsgpsirosE9.00 |
Description: | per Nels Larson (11/09/94) "The MFRSR gains measured in the field were found to be different than the values used in the Ashton SIROS CalibInfo files used to process the data for Board 93913, which was installed 94/03/17. I have dug deeply into my notes from Jerry Berndt's visit to the field in March, and found some gains he reported for the board at that time. I also found a note on the same page stating that I should refer to the calibration sheet in his lab notebook for the proper gains. Well, I used the gains from the lab notebook and didn't check them against the gains he rattled off over the phone. The ones he gave me verbally match pretty well with the actual state of the board as found by John in October. What will need to be done is to correct the processed Ashton data stream of the MFRSR Detector Channels 3,4,6,7 (499,608,859,934 nm) for improper logger board gains effective 94/03/17. Because it is such a long period of data, I would recommend reprocessing the data with the new CalibInfo files, rather than including a set of constants to apply to the old MFRSR data values. Again, only the MFRSR Detector channels are affected by these calibration changes. The non-MFRSR Detector data, including the PIR, PSP, NIP, MFRSR temperature, and logger health data, are unaffected." |
Measurements: | sgpsirosE9.a1:
DsgpsirosE9.00:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
04/01/1994 | 0000 | 07/28/1994 | 2359 |
Subject: | Improper sds-mode global metadata value |
DataStreams: | sgpsirosE9.a1 |
Description: | DQR No: Subject: SGP/SIROS.E9 - Improper sds-mode global metadata value Date Submitted: September 20, 1994 Submitted By: PJ Caraher ___ Instrument Mentor ___ EST Member ___ Science Team Member X__ Other : DMT member Organization: Argonne National Lab Email address: caraher@athens.dis.anl.gov Telephone: (708)252-4262 Platform/Measurement: DsgpsirosE9 What level data: (raw,a0,a1,b1,c1 etc): a1 What location was the data collected at: Ashton (E9) Period of time in question Begin Date 04/01/94 Time 00:00 (GMT) End Date 07/28/94 Time 00:00 (GMT) Data should be labeled: ___ questionable X__ incorrect ___ wrong calibration ___ others _______________________________ Discussion of Problem: While reingesting the SIROS data for E9 (Ashton) I improperly ran the ingest in "testrun" mode rather than "production" mode. Thus the reingested data from April 01 through July 28 should have its sds-mode (global metadata value) as "production" rather than "testrun". Other observations/measurements impacted by this problem: Suggested Corrections of the Problem: (e.g. change calibration factor and recompute, flag data with this comment, etc.) This is a very minor problem but it should be noted so as to avoid any confusion. REQUIRED ACTIONS: This report is informational no further action required___Yes___ Experiment Center action required as follows: Site Operations action required as follows: Archive action required as follows: ------------------------------------------------------- TO BE FILLED IN UPON COMPLETION OF ACTION ABOVE: Action Taken: Experiment Center: Site Operations: Archive: EST: |
Measurements: | sgpsirosE9.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
03/09/1995 | 1512 | 03/09/1995 | 1553 |
Subject: | Installation of new data logger PROM |
DataStreams: | sgpsirosE9.a1 |
Description: | DQR No: Platform: sgpsirosE9 Subject: Installation of new data logger PROM Date Submitted: 95/03/27 Submitted By: Nels Larson _X_ Instrument Mentor ___ EST Member ___ Science Team Member ___ Other _____________________________ For questions or problems, please contact the ARM Experiment Center at 509-375-6898 or via email at dqr@arm.gov. Platform/Measurement: All data What level data: (raw,a0,a1,b1,c1 etc): All What location was the data collected at: Ashton Period of time in question Begin Date 95/03/09 Time 15:12 (GMT) End Date 95/03/09 Time 15:53 (GMT) Data should be labeled: ___ questionable ___ All data fields affected ___ incorrect ___ Only some data fields affected ___ wrong calibration ___ others Discussion of Problem: The MFRSR head for sgpmsirosE9 was changed by the mentors. The old head, 923, was removed for recalibration, and the new head, 229, was installed. No data was acquired between 95/03/09 15:12-15:53. The data logger PROM was upgraded to the lateset Version 13. Other observations/measurements impacted by this problem: Suggested Corrections of the Problem: (e.g. change calibration factor and recompute, flag data with this comment, etc.) Data Processing Notes Date |
Measurements: | sgpsirosE9.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
03/01/1996 | 0000 | 04/18/1996 | 2145 |
Subject: | Bad upwelling IR signal, bad upwelling SW signal |
DataStreams: | sgpsirosE4.a1 |
Description: | Data has been collected at site E4 since about April 1995. We have just started to examine data from this site taken from about 1 March 1996. We do not know the quality of the data before this date. After this date, the signal from the upwelling IR pyrgeometer is bad, as well as the signal from the upwelling SW pyranometer. Suggested Corrections of the Problem: Inspect and fix the offending instruments (the repairpersons at the SGP site have been notified about these instruments). |
Measurements: | sgpsirosE4.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
03/06/1996 | 0000 | 03/21/1996 | 1300 |
Subject: | Bad upwelling and downwelling IR signal, bad upwelling SW signal |
DataStreams: | sgpsirosE3.a1 |
Description: | Data has been collected at site E3 since about March 6, 1996. From this date to about March 21, 1996, the signal from both IR pyrgeometers (both upwelling and downwelling) is bad. After March 21, 1996 these instruments were repaired and the data looks reasonable. |
Measurements: | sgpsirosE3.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
03/21/1996 | 0000 | 04/02/1996 | 2359 |
Subject: | Unshaded PSP dirty domes |
DataStreams: | sgpsirosE8.a1, sgpsirosE11.a1 |
Description: | Subject: Unshaded PSP dirty domes Platform/Measurement: sgpsiros/unshaded PSP What location was the data collected at: E8, E11 Period of time in question Begin Date 03/21/96 End Date 04/02/96 Discussion of Problem: Large differences between estimates of downwelling hemispheric shortwave radiation from the unshaded PSP and the combination of the NIP and shaded PSP were observed as early as March 21, 1996 and lasted through April 2, 1996 when Site Operations cleaned the radiometer domes at E8. The differences were as high as 150 W/m^2 during the late afternoon on several days within this period. The cause of the differences seems to be dirt on the unshaded PSP dome (which was observed before the dome was cleaned) causing the estimate from the unshaded PSP to be lower than expected. The dome condition observation was obtained by email communication with Site Operatons staff and is not know to be logged elsewhere. Differences in the downwelling hemispheric shortwave estimates at E11 (though not nearly as large as at E8) showed improvement after dome cleaning activities on April 2, as well. A postscript file attachment depicts the data for E8 on April 2 and the cleaning of the dome can be identified at the time: Day of Year 93.82, or at about 1930Z. |
Measurements: | sgpsirosE11.a1:
sgpsirosE8.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
05/08/1995 | 2020 | 01/23/1996 | 2359 |
Subject: | SGP/SIROS/E4 - Wrong units for broadband irradiance |
DataStreams: | sgpsirosE4.a1 |
Description: | Headers for SIROS, MFR25m and MFR10m give the units for broadband irradiance as 'watts per square meter' (W/m^2). However, the units are really 'counts'. The fields affected are SIROS: 'hemisp_broadband:units' 'diffuse_hemisp_broadband:units' 'direct_norm_broadband:units' MFR: 'mfr_up_hemisp_broadband:units' This problem has existed since the beginning of the data streams, and was corrected by Jeff Slater on 1/23/96 (see C960314.2 by Ken Yates that closed P960229.2) |
Measurements: | sgpsirosE4.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
05/18/1995 | 0000 | 01/23/1996 | 2359 |
Subject: | SGP/SIROS/E7 - Wrong units for broadband irradiance |
DataStreams: | sgpsirosE7.a1 |
Description: | Headers for SIROS, MFR25m and MFR10m give the units for broadband irradiance as 'watts per square meter' (W/m^2). However, the units are really 'counts'. The fields affected are SIROS: 'hemisp_broadband:units' 'diffuse_hemisp_broadband:units' 'direct_norm_broadband:units' MFR: 'mfr_up_hemisp_broadband:units' This problem has existed since the beginning of the data streams, and was corrected by Jeff Slater on 1/23/96 (see C960314.2 by Ken Yates that closed P960229.2) |
Measurements: | sgpsirosE7.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
09/22/1995 | 0000 | 01/23/1996 | 2359 |
Subject: | SGP/SIROS/E8 - Wrong units for broadband irradiance |
DataStreams: | sgpsirosE8.a1 |
Description: | Headers for SIROS, MFR25m and MFR10m give the units for broadband irradiance as 'watts per square meter' (W/m^2). However, the units are really 'counts'. The fields affected are SIROS: 'hemisp_broadband:units' 'diffuse_hemisp_broadband:units' 'direct_norm_broadband:units' MFR: 'mfr_up_hemisp_broadband:units' This problem has existed since the beginning of the data streams, and was corrected by Jeff Slater on 1/23/96 (see C960314.2 by Ken Yates that closed P960229.2) |
Measurements: | sgpsirosE8.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
01/12/1994 | 1514 | 01/23/1996 | 2359 |
Subject: | SGP/SIROS/E9 - Wrong units for broadband irradiance |
DataStreams: | sgpsirosE9.a1 |
Description: | Headers for SIROS, MFR25m and MFR10m give the units for broadband irradiance as 'watts per square meter' (W/m^2). However, the units are really 'counts'. The fields affected are SIROS: 'hemisp_broadband:units' 'diffuse_hemisp_broadband:units' 'direct_norm_broadband:units' MFR: 'mfr_up_hemisp_broadband:units' This problem has existed since the beginning of the data streams, and was corrected by Jeff Slater on 1/23/96 (see C960314.2 by Ken Yates that closed P960229.2) |
Measurements: | sgpsirosE9.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
01/06/1994 | 0000 | 01/23/1996 | 2359 |
Subject: | SGP/SIROS - wrong units for broadband irradiance |
DataStreams: | sgpsirosE1.a1, sgpsirosE3.a1, sgpsirosE4.a1, sgpsirosE7.a1, sgpsirosE8.a1, sgpsirosE9.a1, sgpsirosE10.a1, sgpsirosE11.a1, sgpsirosE12.a1, sgpsirosE13.a1, sgpsirosE15.a1, sgpsirosE16.a1, sgpsirosE18.a1, sgpsirosE20.a1, sgpsirosE22.a1, sgpsirosE24.a1 |
Description: | Headers for SIROS, give the units for broadband irradiance as 'watts per square meter' (w/m^2). However, the units are really 'counts'. The fields affected are: 'hemisp_broadband:units' 'diffuse_hemisp_broadband:units' 'direct_norm_broadband:units' This problem existed since the beginning of the data streams, and was corrected on 1/23/96. |
Measurements: | sgpsirosE24.a1:
sgpsirosE13.a1:
sgpsirosE18.a1:
sgpsirosE4.a1:
sgpsirosE7.a1:
sgpsirosE16.a1:
sgpsirosE8.a1:
sgpsirosE12.a1:
sgpsirosE9.a1:
sgpsirosE15.a1:
sgpsirosE3.a1:
sgpsirosE22.a1:
sgpsirosE11.a1:
sgpsirosE10.a1:
sgpsirosE20.a1:
sgpsirosE1.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
04/18/1996 | 0000 | 08/08/1996 | 2359 |
Subject: | MFRSR out of alignment |
DataStreams: | sgpsirosE8.a1 |
Description: | DQR Date Submitted: 10 May 1996 Submitted By: Jim Barnard _X_ Instrument Mentor ___ EST Member ___ Science Team Member ___ Other _____________________________ For questions or problems, please contact the ARM Experiment Center at 509-375-6898 or via email at problems@arm.gov. Platform/Measurement: What level data: (raw,a0,a1,b1,c1 etc): raw,a0,a1 What location was the data collected at: E8 Period of time in question Begin Date about 96/04/18 End Date ongoing problem Data should be labeled: ___ questionable ___ All data fields affected _x_ incorrect _x_ Only some data fields affected ___ wrong calibration ___ others Discussion of Problem: The MFRSR at site E8 has been out of alignment from about 96/04/18 to the present time. This is an ongoing problem. The poor alignment manifests itself in a sawtooth pattern in the direct beam and diffuse components of the MFRSR data. During the time this pattern exists, the data are almost useless. For this site, the poor alignment affects the afternoon data. Other observations/measurements impacted by this problem: Suggested Corrections of the Problem: (e.g. change calibration factor and recompute, flag data with this comment, etc.): align instument at earliest possible time (Logistically, this is harder than it seems at first glance). |
Measurements: | sgpsirosE8.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
05/29/1996 | 0000 | 05/29/1996 | 2359 |
Subject: | SGP/SIROS/E4 - time offset on 960529 |
DataStreams: | sgpsirosE4.a1 |
Description: | On 960529, site E4 was brought back on line. For reasons I do not understand the time stamp was incorrect for most of this day; for example, the sun is at its zenith at about 0900 LST! This is clearly incorrect. In the afternoon and evening hours, this site goes "down" and after this down period the time problem appears to be solved. The next day's data (960530) looks correct and there appears to be no time problem. |
Measurements: | sgpsirosE4.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
05/31/1996 | 0500 | 08/08/1996 | 1613 |
Subject: | missing MFRSR data site E5 |
DataStreams: | sgpsirosE5.a1 |
Description: | Site E5 was fired up on about 96/05/31. An MFRSR was not connected due to a lack of MFRSR parts. Consequently, no MFRSR measurements are being made at this site, and the MFRSR output consists of zeros. |
Measurements: | sgpsirosE5.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
05/08/1996 | 0000 | 06/12/1996 | 1700 |
Subject: | MFRSR data missing - 960508 to 960612 site E4 |
DataStreams: | sgpsirosE4.a1 |
Description: | The MFRSR head was damaged at site E4. MFRSR data was not collected from 960508 to about 960612. The head was replaced on 960612 about 1700 GMT and data collection again started. During the time the data was NOT collected, zeros will appear for all MFRSR data fields. This DQR supercedes DQR D960608.1. |
Measurements: | sgpsirosE4.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
03/09/1995 | 0000 | 05/15/1995 | 2359 |
Subject: | data unrecoverable 950309 to 950515 |
DataStreams: | sgpsirosE4.a1 |
Description: | At site E7, from the dates 950309 to 950515, the data is unrecoverable. This problem appears to be caused by a bug in the program that is stored on the data logger board's EPROM. The data might be recoverable with great effort. Note: this site was first turned on about 950300 so there's little or no data before this time. |
Measurements: | sgpsirosE4.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
06/01/1996 | 0000 | 08/19/1996 | 1600 |
Subject: | E3 - MFRSR out of alignment |
DataStreams: | sgpsirosE3.a1 |
Description: | The MFRSR at site E3 appears to be woefully out of alignment. The alignment problems started about 96/06/01. It's not possible to exactly pin down the date that the alignment problem started because the cloudy weather that occured around 96/06/01 makes the detection of alignment problems difficult. (In fact, it wasn't until 96/06/19 that the problem could be detected unambigiously). The alignment problem at this site is so severe that both the morning and afternoon data streams are affected. The alignment problem does not affect the total, downwelling radiation stream. |
Measurements: | sgpsirosE3.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
06/19/1996 | 0000 | 12/14/1996 | 2359 |
Subject: | E7 - MFRSR out of alignment |
DataStreams: | sgpsirosE7.a1 |
Description: | The day of 96/06/19 was clear at site E7. Inspection of the data shows that this site suffers from an slight alignment problem that affects the data measured in the afternoon. The alignment problem could affect data taken before this time and go unnoticed because clear skies are usually necessary to detect all but the most severe alignment problems. The total, downwelling radiation stream is not affected by the alignment problem. |
Measurements: | sgpsirosE7.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
06/14/1996 | 0000 | 07/25/1996 | 2359 |
Subject: | bad data - MFRSR - site E9 |
DataStreams: | sgpsirosE9.a1 |
Description: | From about 960614 to 960725, the data emanating from the MFRSR at site E9 was very noisy indicating that there was a problem with the instrument. On 960725, the MFRSR head was changed and the problem appears to have been solved. The data quality could be poor prior to 960614, so beware! |
Measurements: | sgpsirosE9.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
03/06/1996 | 0000 | 07/10/1996 | 2359 |
Subject: | time stamp error |
DataStreams: | sgpsirosE3.a1 |
Description: | The internal code that runs the MFRSR data logger had a bug that occasionally caused the time stamp associated with the data to be slightly in error. This error is thought to be very small (say less than 30 seconds) and very infrequent. (Unfortunately, we cannot give firm estimates of the magnitude and frequency of the error). After 96/07/10 the problem was corrected. Those who use the data before this time should realize that the time stamp for each record of data might be slightly in error. |
Measurements: | sgpsirosE3.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
05/18/1995 | 0000 | 07/11/1996 | 2359 |
Subject: | time stamp error |
DataStreams: | sgpsirosE7.a1 |
Description: | The internal code that runs the MFRSR data logger had a bug that occasionally caused the time stamp associated with the data to be slightly in error. This error is thought to be very small (say less than 30 seconds) and very infrequent. (Unfortunately, we cannot give firm estimates of the magnitude and frequency of the error). After 96/07/11 the problem was corrected. Those who use the data before this time should realize that the time stamp for each record of data might be slightly in error. |
Measurements: | sgpsirosE7.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
06/14/1996 | 0000 | 07/11/1996 | 2359 |
Subject: | time stamp error |
DataStreams: | sgpsirosE5.a1 |
Description: | The internal code that runs the MFRSR data logger had a bug that occasionally caused the time stamp associated with the data to be slightly in error. This error is thought to be very small (say less than 30 seconds) and very infrequent. (Unfortunately, we cannot give firm estimates of the magnitude and frequency of the error). After 96/07/11 the problem was corrected. Those who use the data before this time should realize that the time stamp for each record of data might be slightly in error. |
Measurements: | sgpsirosE5.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
05/08/1995 | 0000 | 07/11/1996 | 2359 |
Subject: | time stamp error |
DataStreams: | sgpsirosE4.a1 |
Description: | The internal code that runs the MFRSR data logger had a bug that occasionally caused the time stamp associated with the data to be slightly in error. This error is thought to be very small (say less than 30 seconds) and very infrequent. (Unfortunately, we cannot give firm estimates of the magnitude and frequency of the error). After 96/07/11 the problem was corrected. Those who use the data before this time should realize that the time stamp for each record of data might be slightly in error. |
Measurements: | sgpsirosE4.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
09/22/1995 | 0000 | 07/10/1996 | 2359 |
Subject: | time stamp error |
DataStreams: | sgpsirosE8.a1 |
Description: | The internal code that runs the MFRSR data logger had a bug that occasionally caused the time stamp associated with the data to be slightly in error. This error is thought to be very small (say less than 30 seconds) and very infrequent. (Unfortunately, we cannot give firm estimates of the magnitude and frequency of the error). After 96/07/10 the problem was corrected. Those who use the data before this time should realize that the time stamp for each record of data might be slightly in error. |
Measurements: | sgpsirosE8.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
01/12/1994 | 0000 | 07/09/1996 | 2359 |
Subject: | time stamp error |
DataStreams: | sgpsirosE9.a1 |
Description: | The internal code that runs the MFRSR data logger had a bug that occasionally caused the time stamp associated with the data to be slightly in error. This error is thought to be very small (say less than 30 seconds) and very infrequent. (Unfortunately, we cannot give firm estimates of the magnitude and frequency of the error). After 96/07/09 the problem was corrected. Those who use the data before this time should realize that the time stamp for each record of data might be slightly in error. |
Measurements: | sgpsirosE9.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
06/19/1996 | 0000 | 12/24/1996 | 2359 |
Subject: | MFRSR out of alignment |
DataStreams: | sgpsirosE7.a1 |
Description: | From about 96/06/19 to about 96/12/24 1630 GMT the MFRSR has suffered from alignment problems (to varying degrees). These alignment difficulties have a very colorful history; to wit: 96/06/19 - alignment problem detected that affects data measured in the afternoon (as noted by the sawtooth pattern in the data) 96/07/21 - alignment occurs, but the alignment problem still persists 96/08/08 - another alignment occurs, but the alignment is now much worse 96/09/18 - yet another alignment occurs, and the alignment is now much better, although the instrument is still a little out of alignment 96/10/02 - yet another alignment with more improvement noted, but an alignment problem still is detectable 96/12/01 - suddendly the alignment gets MUCH worse (just look at the morning data!!) 96/12/24 - yet another alignment; now the instrument appears to be in proper alignment. We hope that with this alignment the instrument is truly aligned and that the above "alignemnt saga" (reminicent of Homer's Odyssey) has now been happily concluded - only time will tell. |
Measurements: | sgpsirosE7.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
02/21/1997 | 0517 | 03/30/1997 | 1630 |
Subject: | Tower down |
DataStreams: | sgpsirosE7.a1 |
Description: | On about 97/02/21 the tower that supports the |
Measurements: | sgpsirosE7.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
03/11/1997 | 0000 | 03/20/1997 | 2359 |
Subject: | solar tracker inoperative |
DataStreams: | sgpsirosE4.a1 |
Description: | On about 970311 the solar tracker at site E4 apparently stopped working. The NIP then was not pointed at the sun and read 0 all the time, and the DD was not shaded and read too high. The solar tracker was fixed on about 97/03/20. It is not possible to pin down the exact times when the solar tracker was not working because of cloudy conditions. |
Measurements: | sgpsirosE4.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
06/23/1997 | 1700 | 06/23/1997 | 2359 |
Subject: | E9 NIP affected by precipitation |
DataStreams: | sgpsirosE9.a1 |
Description: | Comparison of the dowelling hemishperic solar broadband flux estimated from the unshaded PSP (down_short_hemisp) and that derived from the combination of the NIP (short_direct_normal) and shaded PSP (down_short_diffuse_hemisp) showed significant differences (greater than 100 W/m^2) at times on June 23, 1997. These differences appear to be due to questionable data from the NIP (short_direct_normal) that may have been caused by rainfall on that day. The NIP values recorded values as low as -15 W/m^2 in proximity to when the SMOS recorded precipitation. After the first precipitation event, the NIP appeared to be recording lower values during sunnier periods that may be due to collected precipitation in the NIP affecting the amount of solar radiation reaching the sensor. |
Measurements: | sgpsirosE9.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
06/23/1997 | 1730 | 06/23/1997 | 2359 |
Subject: | E4 NIP affected by precipitation |
DataStreams: | sgpsirosE4.a1 |
Description: | Comparison of the dowelling hemishperic solar broadband flux estimated from the unshaded PSP (down_short_hemisp) and that derived from the combination of the NIP (short_direct_normal) and shaded PSP (down_short_diffuse_hemisp) showed significant differences (greater than 80 W/m^2) at times on June 23, 1997. These differences appear to be due to questionable data from the NIP (short_direct_normal) that may have been caused by rainfall on that day. The NIP values recorded values as low as -20 W/m^2 in proximity to when the SMOS recorded precipitation. After the first precipitation event, the NIP appeared to be recording lower values during sunnier periods that may be due to collected precipitation in the NIP affecting the amount of solar radiation reaching the sensor. |
Measurements: | sgpsirosE4.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
05/27/1992 | 0000 | 05/31/2002 | 2359 |
Subject: | SGP/SONDE - Dry bias in sonde RH |
DataStreams: | sgpsondeB1.00, sgpsondeB1.a0, sgpsondeB1.a1, sgpsondeB4.00, sgpsondeB4.a0, sgpsondeB4.a1, sgpsondeB5.00, sgpsondeB5.a0, sgpsondeB5.a1, sgpsondeB6.00, sgpsondeC1.00, sgpsondeC1.a0, sgpsondeC1.a1, DsgpsondeB1.00, DsgpsondeB1.a0, DsgpsondeB1.a1, DsgpsondeB4.00, DsgpsondeB4.a0, DsgpsondeB4.a1, DsgpsondeB5.00, DsgpsondeB5.a0, DsgpsondeB5.a1, DsgpsondeC1.00, DsgpsondeC1.a0, DsgpsondeC1.a1, sgpsondeptuC1.00, DsgpsondeptuB1.00, DsgpsondeptuB4.00, DsgpsondeptuB5.00, DsgpsondeptuB6.00, DsgpsondeptuC1.00, sgpsondewnpnB1.a0, sgpsondewnpnB1.a1, sgpsondewnpnB4.a0, sgpsondewnpnB4.a1, sgpsondewnpnB5.a0, sgpsondewnpnB5.a1, sgpsondewnpnB6.a0, sgpsondewnpnB6.a1, sgpsondewnpnC1.a0, sgpsondewnpnC1.a1, sgpsondewnprC1.a0, sgpsondewnprC1.a1, sgpsondewrpnB1.00, sgpsondewrpnB1.a0, sgpsondewrpnB1.a1, sgpsondewrpnB4.00, sgpsondewrpnB4.a0, sgpsondewrpnB4.a1, sgpsondewrpnB5.00, sgpsondewrpnB5.a0, sgpsondewrpnB5.a1, sgpsondewrpnB6.00, sgpsondewrpnB6.a0, sgpsondewrpnB6.a1, sgpsondewrpnC1.00, sgpsondewrpnC1.a0, sgpsondewrpnC1.a1, sgpsondewrprB1.00, sgpsondewrprB1.a0, sgpsondewrprB1.a1, sgpsondewrprB4.00, sgpsondewrprB4.a0, sgpsondewrprB4.a1, sgpsondewrprB5.00, sgpsondewrprB5.a0, sgpsondewrprB5.a1, sgpsondewrprC1.00, sgpsondewrprC1.a0, sgpsondewrprC1.a1, DsgpsondeptucalcB1.c1, DsgpsondeptucalcB4.c1, DsgpsondeptucalcB5.c1, DsgpsondeptucalcC1.c1, DsgpsondenogcwrpnB1.c1, DsgpsondenogcwrpnB4.c1, DsgpsondenogcwrpnB5.c1, DsgpsondenogcwrpnC1.c1, DsgpsondenogcptucalcB1.c1, DsgpsondenogcptucalcB4.c1, DsgpsondenogcptucalcB5.c1, DsgpsondenogcptucalcC1.c1 |
Description: | Vaisala has confirmed ARM findings of an apparent dry bias in the relative humidity measured by RS-80H radiosondes. The cause of the dry bias is thought to be contamination of the humidity sensor by volatile organic substances originating from some plastic parts of the radiosonde. The amount of contamination is a function of the time between the date of sonde manufacture and its use. All RS-80H sondes manufactured before week 34 of 1998 will show this bias. After week 34 of 1998 Vaisala changed its packaging to reduce, but not eliminate the contamination problem. Starting with RS-80 radiosonde manufactured in late June 2000 Vaisala enclosed the sensor boom in an inert plastic shield, thereby eliminating the contamination that caused the dry bias. Starting in May 2001 at the SGP, May 2002 at the TWP, and later 2002 at the NSA, ARM has moved to using RS-90 radiosondes. These sondes are not subject to the contaminatino that caused the dry bias. Vaisala is in the process of developing an algorithm that can be used to estimate the correct RH from knowledge of the sonde age. All of the ARM sounding data have sufficient metadata available to apply the correction. Additionally, ARM has funded a Science Team effort (Milosevich) to develop a 'best' correction algorithm for the RS-80 radiosonde humidity data. When completed this algorithm will allow us to reprocess the accumulated RS-80 data and produce a new data platform with what we hope will be more accurate data. |
Measurements: | sgpsondeptuC1.00:
sgpsondeB4.a1:
sgpsondeB4.a0:
DsgpsondeptuB4.00:
sgpsondewrprB1.00:
DsgpsondeC1.a1:
DsgpsondeB5.a0:
DsgpsondeC1.a0:
sgpsondewrpnC1.a1:
sgpsondewnprC1.a1:
DsgpsondenogcptucalcC1.c1:
sgpsondewrpnB5.00:
sgpsondewrpnB4.a0:
sgpsondewnpnB1.a0:
sgpsondewnpnB1.a1:
DsgpsondeB5.a1:
sgpsondewrprB4.a1:
sgpsondewrpnB4.a1:
DsgpsondeB4.a0:
sgpsondewrpnB6.00:
DsgpsondeB4.a1:
sgpsondewrprB4.a0:
DsgpsondeptuB6.00:
sgpsondewnpnC1.a0:
sgpsondewrpnB6.a0:
DsgpsondeptuB5.00:
sgpsondewnpnC1.a1:
DsgpsondenogcwrpnB4.c1:
DsgpsondeB4.00:
sgpsondewrpnB6.a1:
DsgpsondenogcptucalcB4.c1:
DsgpsondeC1.00:
DsgpsondeptuC1.00:
DsgpsondeptucalcB1.c1:
DsgpsondeptucalcB5.c1:
sgpsondewrpnB1.00:
sgpsondewrpnB1.a1:
sgpsondewrpnB1.a0:
DsgpsondeptuB1.00:
DsgpsondeB1.00:
DsgpsondeptucalcB4.c1:
DsgpsondenogcwrpnB5.c1:
sgpsondewrpnB5.a0:
sgpsondewrpnB5.a1:
DsgpsondenogcptucalcB1.c1:
sgpsondeC1.00:
sgpsondewrprB4.00:
sgpsondeB4.00:
sgpsondewrprB1.a0:
sgpsondewrprC1.00:
sgpsondewrprB1.a1:
sgpsondewnpnB5.a0:
sgpsondeB1.a0:
DsgpsondeB5.00:
sgpsondewnpnB5.a1:
sgpsondeB1.a1:
sgpsondewnpnB4.a1:
sgpsondewnpnB6.a0:
sgpsondewnpnB6.a1:
sgpsondewnpnB4.a0:
DsgpsondenogcwrpnB1.c1:
sgpsondeB5.00:
sgpsondeB6.00:
DsgpsondenogcptucalcB5.c1:
sgpsondewrprB5.00:
DsgpsondeptucalcC1.c1:
DsgpsondenogcwrpnC1.c1:
sgpsondeC1.a1:
sgpsondeC1.a0:
DsgpsondeB1.a0:
sgpsondewrpnC1.00:
sgpsondeB5.a0:
sgpsondewrpnB4.00:
sgpsondeB5.a1:
DsgpsondeB1.a1:
sgpsondewrprC1.a1:
sgpsondewrprB5.a0:
sgpsondewrprB5.a1:
sgpsondewrpnC1.a0:
sgpsondewnprC1.a0:
sgpsondeB1.00:
sgpsondewrprC1.a0:
|