Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
06/07/2010 | 0000 | 06/29/2010 | 2359 | Incorrect |
Subject: | SGP/SIRS/E21 - Reprocess: TimeCheck Error |
DataStreams: | sgpsirsE21.00, sgpsirsE21.b1, sgpsirs20sE21.a0 |
Description: | The EF data system lost communication with the GPS likely starting on or around June 7th, the max time set For E21 was -5.04 sec. Since then, it has been increasing steadily: Jun 8 Offset: -267.449039 Jun 9 Offset: -541.038624 Jun 10 Offset: -814.469141 Jun 11 Offset: -1076.862114 Jun 12 Offset: -1350.330223 Jun 13 Offset: -1623.639335 Jun 14 Offset: -1897.047754 Jun 15 Offset: -2170.552312 Jun 16 Offset: -2422.130746 Jun 17 Offset: -2684.607495 Jun 18 - Jun 22 (unknown) Jun 23 Offset: -4204.730579 If the E21 system clock drifts the E21 Datalogger clocks will be set to the same incorrect time. SIRS irradiance data will be correct but the corresponding time stamp cannot be accurately known or simply corrected for. |
Suggestions: | Data time stamp cannot be considered accurate and hence users are advised to disregard this data. PRB note: We may be able to recommend a correction based on assumption of linear drift between site data system time sets. This may not be worth the effort since so much data is missing in the later date range (6/24 to 7/14) due to data collection problems and time drift is unknown from Jun 18 to Jun 22. Data time stamp cannot be considered accurate and hence users are advised to disr egard this data. PRB note: We may be able to recommend a correction based on assumption of linear drift between site data system time sets. This may not be worth the effort since so much data is missing in the later date range (6/24 to 7/14) due to data collection problems and time drift is unknown from Jun 18 to Jun 22. |
Measurements: | sgpsirs20sE21.a0: more
sgpsirsE21.00: more sgpsirsE21.b1: more |