DQR ID | Subject | Data Streams Affected |
---|---|---|
D000514.3 | SGP/SIROS/E15 - occasional spikes in readings | sgpsirosE15.a1, DsgpsirosE15.00 |
D020620.46 | SGP/SIROS/E1 - wrong units for broadband irradiance | sgpsirosE1.a1 |
D020620.48 | SGP/SIROS/E11 - wrong units for broadband irradiance | sgpsirosE11.a1 |
D020620.51 | SGP/SIROS/E15 - wrong units for broadband irradiance | sgpsirosE15.a1 |
D020620.52 | SGP/SIROS/E16 - wrong units for broadband irradiance | sgpsirosE16.a1 |
D020620.55 | SGP/SIROS/E24 - wrong units for broadband irradiance | sgpsirosE24.a1 |
D950328.2 | Installation of new data logger PROM | sgpsirosE15.a1 |
D960201.1 | MFRSR out of alignment | sgpsirosE24.a1 |
D960402.2 | ONgoing Data Quality Problems | sgpsirosE2.a1 |
D960404.4 | Unshaded PSP dirty domes | sgpsirosE8.a1, sgpsirosE11.a1 |
D960423.1 | SGP/SIROS/E1 - Wrong units for broadband irradiance | sgpsirosE1.a1 |
D960423.10 | SGP/SIROS/E15 - Wrong units for broadband irradiance | sgpsirosE15.a1 |
D960423.11 | SGP/SIROS/E16 - Wrong units for broadband irradiance | sgpsirosE16.a1 |
D960423.14 | SGP/SIROS/E24 - Wrong units for broadband irradiance | sgpsirosE24.a1 |
D960423.7 | SGP/SIROS/E11 - Wrong units for broadband irradiance | sgpsirosE11.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 |
D960501.3 | NIP (pyrheliometer) calibration coefficient slightly wrong | sgpsirosE2.a1 |
D960510.2 | MFRSR out of alignment | sgpsirosE1.a1 |
D960608.2 | MFRSR out of alignment | sgpsirosE16.a1 |
D960608.3 | MFRSR out of alignment | sgpsirosE11.a1 |
D960608.4 | MFRSR out of alignment | sgpsirosE24.a1 |
D960913.4 | time stamp error | sgpsirosE1.a1 |
D960913.6 | time stamp error | sgpsirosE2.a1 |
D960914.13 | time stamp error | sgpsirosE24.a1 |
D960914.5 | time stamp error | sgpsirosE11.a1 |
D960914.8 | time stamp error | sgpsirosE15.a1 |
D960914.9 | time stamp error | sgpsirosE16.a1 |
D961126.1 | MFRSR out of alignment - E16 | sgpsirosE16.a1 |
D970117.1 | MFRSR out of alignment | sgpsirosE24.a1 |
D970310.1 | solar tracker inoperative | sgpsirosE2.a1 |
D970402.1 | solar tracker inoperative | sgpsirosE11.a1 |
D970428.1 | Data Missing due to HW/Communications Problems | sgpsirosE16.a1 |
D970429.1 | solar tracker inoperative | sgpsirosE2.a1 |
D970626.1 | E1 NIP affected by precipitation | sgpsirosE1.a1 |
D970626.3 | E11 NIP affected by precipitation | sgpsirosE11.a1 |
Start Date | Start Time | End Date | End Time |
---|---|---|---|
12/15/1993 | 0000 | 11/01/1994 | 0000 |
Subject: | SGP/SIROS/E15 - occasional spikes in readings |
DataStreams: | sgpsirosE15.a1, DsgpsirosE15.00 |
Description: | Since installation of this SIROS site to the dates specified, negative spikes occurred in the data streams indicated, especially for down_short_hemisp and down_long_diffuse_hemisp. 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 Splitt 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: | DsgpsirosE15.00:
sgpsirosE15.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
11/15/1995 | 1612 | 01/23/1996 | 2359 |
Subject: | SGP/SIROS/E1 - wrong units for broadband irradiance |
DataStreams: | sgpsirosE1.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: | sgpsirosE1.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
06/30/1995 | 1704 | 01/23/1996 | 2359 |
Subject: | SGP/SIROS/E11 - wrong units for broadband irradiance |
DataStreams: | sgpsirosE11.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: | sgpsirosE11.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
01/12/1994 | 1445 | 01/23/1996 | 2359 |
Subject: | SGP/SIROS/E15 - wrong units for broadband irradiance |
DataStreams: | sgpsirosE15.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: | sgpsirosE15.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
06/02/1995 | 1737 | 01/23/1996 | 2359 |
Subject: | SGP/SIROS/E16 - wrong units for broadband irradiance |
DataStreams: | sgpsirosE16.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: | sgpsirosE16.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
11/07/1995 | 2324 | 01/23/1996 | 2359 |
Subject: | SGP/SIROS/E24 - wrong units for broadband irradiance |
DataStreams: | sgpsirosE24.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: | sgpsirosE24.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
03/08/1995 | 1714 | 03/08/1995 | 2259 |
Subject: | Installation of new data logger PROM |
DataStreams: | sgpsirosE15.a1 |
Description: | DQR No: Platform: sgpsirosE15 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: Ringwood Period of time in question Begin Date 95/03/08 Time 17:14 (GMT) End Date 95/03/08 Time 22:59 (GMT) Data should be labeled: ___ questionable ___ All data fields affected _X_ incorrect ___ Only some data fields affected ___ wrong calibration ___ others Discussion of Problem: The MFRSR head for sgpmsirosE15 was changed by the mentors. The old head, 924, was removed for recalibration, and the new head, 230, was installed. No data was acquired between 95/03/08 17:14-18:39. The data logger PROM was upgraded from Version 12 to Version 13. Data logger flags in the comm program were incorrect during the period 95/03/08 18:39-22:59 and all data during that interval are no good. Other observations/measurements impacted by this problem: The data logger clock lost 17 seconds per day after the PROM upgrade until reset with a new clock constant at 95/03/16 05:18. Suggested Corrections of the Problem: (e.g. change calibration factor and recompute, flag data with this comment, etc.) Data Processing Notes Date |
Measurements: | sgpsirosE15.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
11/07/1995 | 0000 | 02/28/1996 | 2359 |
Subject: | MFRSR out of alignment |
DataStreams: | sgpsirosE24.a1 |
Description: | DQR No: Platform: MFRSR Subject: E24 - MFRSR out of alignment Date Submitted: 1 Feb 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): a1 What location was the data collected at: Period of time in question Begin Date 95/11/07 Time 00:00 (GMT) End Date / / Time : (GMT) - 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 shadowband of the MFRSR is not fully shading the detector head. During the morning hours, this partial shading causes some data to have a "saw tooth" pattern; these data are clearly bad. The direct normal and diffuse irradiances are subject to this problem, however, the total downwelling irradiance is OK. In the afternoon, all the data fields appear to be correct. 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 MFRSR (this is much harder than it seems because of logistical problems - the technicians have to be at the site on a clear day at solar noon to do the alignment ) |
Measurements: | sgpsirosE24.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
03/07/1996 | 0000 | 03/21/1996 | 2130 |
Subject: | ONgoing Data Quality Problems |
DataStreams: | sgpsirosE2.a1 |
Description: | (NOTE: THIS DQR REPLACES P960327.1 SUBMITTED EARLIER) ---------------------------------------------------- Date Submitted: 1 April 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): a1 What location was the data collected at: Period of time in question Begin Date 96/03/07 Time 00:00 (GMT) End Date 96/03/21 Time 21:30 (GMT) (For the NIP, some errors are occasionally observed after the "End Date"). Data should be labeled: ___ questionable ___ All data fields affected _x_ incorrect _x_ Only some data fields affected ___ wrong calibration ___ others Discussion of Problem: Data has been collected at site E2 since about March 7, 1996. From this date to about March 21, 1996, the signal from both IR pyrgeometers (both upwelling and downwelling) is bad. Additionally, the signal from the NIP and the upwelling SW sensor is likewise bad. After March 21, 1996 these instruments were repaired although the status of the NIP is still unclear. After this date, the NIP has been observed to suddenly emit a signal that is far too high. After a few hours, the signal suddenly drops back to its proper value. These excursions are rare, however the data user should be mindful of them. 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.) |
Measurements: | sgpsirosE2.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 |
---|---|---|---|
11/15/1995 | 1611 | 01/23/1996 | 2359 |
Subject: | SGP/SIROS/E1 - Wrong units for broadband irradiance |
DataStreams: | sgpsirosE1.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: | sgpsirosE1.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
01/12/1994 | 1445 | 01/23/1996 | 2359 |
Subject: | SGP/SIROS/E15 - Wrong units for broadband irradiance |
DataStreams: | sgpsirosE15.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: | sgpsirosE15.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
06/02/1995 | 1737 | 01/23/1996 | 2359 |
Subject: | SGP/SIROS/E16 - Wrong units for broadband irradiance |
DataStreams: | sgpsirosE16.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: | sgpsirosE16.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
11/07/1995 | 2324 | 01/23/1996 | 2359 |
Subject: | SGP/SIROS/E24 - Wrong units for broadband irradiance |
DataStreams: | sgpsirosE24.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: | sgpsirosE24.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
06/30/1995 | 1704 | 01/23/1996 | 2359 |
Subject: | SGP/SIROS/E11 - Wrong units for broadband irradiance |
DataStreams: | sgpsirosE11.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: | sgpsirosE11.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/19/1996 | 1520 | 04/24/1996 | 0000 |
Subject: | NIP (pyrheliometer) calibration coefficient slightly wrong |
DataStreams: | sgpsirosE2.a1 |
Description: | DQR No: Platform: SIROS Subject: Site E2 - NIP (pyrheliometer) calibration coefficient slightly wrong for a period of 5 days Date Submitted: 1 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): a1 What location was the data collected at: Period of time in question Begin Date 96/04/19 Time 15:20 (GMT) End Date 96/04/24 Time 00:00 (GMT) (For the NIP, some errors are occasionally observed after the "End Date"). Data should be labeled: ___ questionable ___ All data fields affected ___ incorrect _x_ Only some data fields affected _x_ wrong calibration ___ others Discussion of Problem: The NIP (pyrheliometer) at site E2 was changed on April 19, 1996 at about 1530 GMT. When the NIP was changed, the data ingest was not turned off and continued insouciantly. Later, the mentor was informed about the change and a new calibration file was submitted. This file was applied to the ingested data about April 24, 1996. Instead of redoing the ingest from April 19, 1996 to April 24, 1996, we are submitting this DQR to inform people that the NIP calibration during this time period is not correct. The calibration factor applied to these data during this period is 8.513 x 10^-6 Volts/W/M^2, while the true calibration factor is 8.546 x 10^-6 Volts/W/M^2. This factor is being applied to all the NIP data collected from April 24, 1996 on. Note that the error caused by using the incorrect calibration factor is less than 0.4%. 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.) The error is so small that it can probably be ignored; from a practical standpoint, this DQR is submitted for the sake of completeness. |
Measurements: | sgpsirosE2.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
04/06/1996 | 0000 | 08/22/1996 | 2359 |
Subject: | MFRSR out of alignment |
DataStreams: | sgpsirosE1.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: E1 Period of time in question Begin Date about 96/04/06 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 E1 has been grossly out of alignment from about 96/04/06 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. 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: | sgpsirosE1.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
06/04/1996 | 0000 | 08/14/1996 | 1800 |
Subject: | MFRSR out of alignment |
DataStreams: | sgpsirosE16.a1 |
Description: | DATA QUALITY REPORT (DQR) DQR No: P960608.2 o Date Submitted: 8 June 1996 o Submitted By: Jim Barnard Organization- PNNL Telephone- (509) 372-6145 Email Address- jc_barnard@pnl.gov o Subject: sgp.sirosE16.960604xxxx.xxxxxxxxxx. - E16 MFRSR out of alignment o Data should be labeled: incorrect o Description: The MFRSR at E16 is out of alignment. This poor alignment affects the direct beam and diffuse radiation measurements taken during the afternoon. There's also some evidence that the alignment affected data taken during the morning hours on 05/21/96. It's hard to diagnose a misalignment problem during cloudy or partly cloudy weather, so the data user should beware of all the data taken from about 5/20/96 onward (until the instrument is aligned). o Suggested Corrections: align instrument |
Measurements: | sgpsirosE16.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
05/20/1996 | 0000 | 07/22/1996 | 2359 |
Subject: | MFRSR out of alignment |
DataStreams: | sgpsirosE11.a1 |
Description: | DATA QUALITY REPORT (DQR) DQR No: P960608.3 o Date Submitted: 8 June 1996 o Submitted By: Jim Barnard Organization- PNNL Telephone- (509) 372-6145 Email Address- jc_barnard@pnl.gov o Subject: sgp.sirosE11.960520xxxx.xxxxxxxxxx. - E11 MFRSR out of alignment o Data should be labeled: o Description: The MFRSR at site E11 is out of alignment. The poor alignment affects data (direct beam and diffuse radiation only) taken during the afternoon hours. o Suggested Corrections: align instrument |
Measurements: | sgpsirosE11.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
11/08/1995 | 0000 | 08/29/1996 | 1910 |
Subject: | MFRSR out of alignment |
DataStreams: | sgpsirosE24.a1 |
Description: | The MFRSR at site E24 is out of alignment. The instrument has been out of alignment since about 11/08/95. From about 03/08/96 to 04/15/96 the instrument appeared to be well aligned. After 4/15/96 the alignment problem was again noticeable. (The instrument can be permanently out of alignment but still work well during some parts of the year). The poor alignment only affects the direct beam and diffuse data streams. The alignment problem was particularly severe during the first part of June. On 06/05/96, it appears that an effort was made to solve the problem, with some success, but the problem still persists, albiet it has been significantly reduced (the data is still bad, however). |
Measurements: | sgpsirosE24.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
11/15/1995 | 0000 | 07/24/1996 | 2359 |
Subject: | time stamp error |
DataStreams: | sgpsirosE1.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/24 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: | sgpsirosE1.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
03/07/1996 | 0000 | 08/09/1996 | 2359 |
Subject: | time stamp error |
DataStreams: | sgpsirosE2.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/08/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: | sgpsirosE2.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
11/07/1995 | 0000 | 08/29/1996 | 2359 |
Subject: | time stamp error |
DataStreams: | sgpsirosE24.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/08/29 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: | sgpsirosE24.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
06/04/1996 | 0000 | 08/20/1996 | 2359 |
Subject: | time stamp error |
DataStreams: | sgpsirosE11.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/08/20 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: | sgpsirosE11.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
01/12/1994 | 0000 | 07/16/1996 | 2359 |
Subject: | time stamp error |
DataStreams: | sgpsirosE15.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/16 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: | sgpsirosE15.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
06/02/1995 | 0000 | 07/19/1996 | 2359 |
Subject: | time stamp error |
DataStreams: | sgpsirosE16.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/19 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: | sgpsirosE16.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
07/19/1996 | 0000 | 11/25/1996 | 2359 |
Subject: | MFRSR out of alignment - E16 |
DataStreams: | sgpsirosE16.a1 |
Description: | From about 96/07/19 to about 96/11/25, the MFRSR was out of alignment at site E16. (It's not possible to exactly pin down the beginning and ending dates of the alignment problem because of weather conditions. Also, the alignment problem could recur later on) The misalignment affects data taken during the afternoon. |
Measurements: | sgpsirosE16.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
12/31/1996 | 0000 | 01/15/1997 | 1900 |
Subject: | MFRSR out of alignment |
DataStreams: | sgpsirosE24.a1 |
Description: | From 96/12/31/ to 97/01/15 the MFRSR site E24 was out of alignment. The poor alignment is manifested, by the sawtooth pattern that occurs in the direct and diffuse data; this pattern is particularly evident during the time about local noon. |
Measurements: | sgpsirosE24.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
02/20/1997 | 0000 | 03/06/1997 | 1500 |
Subject: | solar tracker inoperative |
DataStreams: | sgpsirosE2.a1 |
Description: | From about 97/02/20 to 97/03/06 (1500 GMT) the solar tracker was inoperative at site E2. We cannot pin down the exact starting time of this failure because of cloudy conditions around 97/02/20. The failure becomes obvious during clear skis at which time the NIP reads zero (i.e., it isn't pointed at the sun) and the downward diffuse radiation is too large (because the diffuse pyranometer is not being shaded). 97/03/03 was a particularly clear day and the diffuse pyranometer reads almost the same as the total downward pyranometer. The fact that they don't read exactly the same - the discrepency is about 75 W/m^2 at solar noon - is indicative of a large sensor calibration problem. This large calibration error is NOT typical of ARM data, rather it is peculiar to this site. |
Measurements: | sgpsirosE2.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
03/25/1997 | 0000 | 03/30/1997 | 1830 |
Subject: | solar tracker inoperative |
DataStreams: | sgpsirosE11.a1 |
Description: | At site E11 the solar tracker was inoperative from about 970325 to about 970330 (1830 GMT). The exact time at which tracker failed is not known because of weather conditions. |
Measurements: | sgpsirosE11.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
04/03/1997 | 1413 | 04/09/1997 | 1913 |
Subject: | Data Missing due to HW/Communications Problems |
DataStreams: | sgpsirosE16.a1 |
Description: | Between 4/3 and 4/9 only 1-5% expected data volume where collected from the SIROS at E16 (Vici). Site maintenance found the system inoperable 4/9 and power-cycled. |
Measurements: | sgpsirosE16.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
04/12/1997 | 0000 | 04/17/1997 | 1400 |
Subject: | solar tracker inoperative |
DataStreams: | sgpsirosE2.a1 |
Description: | On about 97/04/12 the solar tracker at site E2 stopped working. The solar tracker exhibits its broken state in a particular striking fashion on 97/04/14 - an almost cloud-free day. On this day, the NIP reads zero and the diffuse and direct SW radiation are about the same. The fact that these two data steams are not exactly the same indicates a calibration problem - probably with the diffuse instrument. This poor calibration is not typical of other ARM sites! On about 97/04/17 (1400 GMT) the solar tracker was fixed. (Note: we cannot pinpoint the exact time or date when the solar tracker went out and the date quoted above {97/04/12} should be regarded as approximate) |
Measurements: | sgpsirosE2.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
06/23/1997 | 1700 | 06/23/1997 | 2329 |
Subject: | E1 NIP affected by precipitation |
DataStreams: | sgpsirosE1.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 60 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 -25 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: | sgpsirosE1.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
06/23/1997 | 1600 | 06/23/1997 | 2359 |
Subject: | E11 NIP affected by precipitation |
DataStreams: | sgpsirosE11.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 70 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 -14 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: | sgpsirosE11.a1:
|