| Start Date | Start Time | End Date | End Time | Data Quality Metric |
|---|---|---|---|---|
| 09/01/1994 | 1700 | 09/01/1994 | 2230 | Incorrect |
| 09/03/1994 | 1530 | 09/07/1994 | 1700 | Incorrect |
| Subject: | SGP/EBBR/E8 - Data Corruption and Loss |
| DataStreams: | sgp30ebbrE8.b1, sgp15ebbrE8.b1, sgp5ebbrE8.b1 |
| Description: | Data loss was experienced during the periods indicated for unknown reasons. My understanding is that ingestion of the data failed for these periods because the record length was shorter than it is supposed to be. Site Operations personnel visited the site on September 7 and powered down and then up, the EBBR, essentially causing a reload of the CR10 program. All output locations had been -9999 or 0000 when they had arrived. The battery condition was normal. Failure of a portion of the storage module may be indicated; data sneakernetted from the storage module shows an alternating sequence of two days, September 2 and 3 and then a stretch of garbage characters. No other days of data are found. The portion of the storage module memory that contained the program was not corrupted, as the CR10 program compiled and ran properly when it was reloaded from the storage module. The data after the period above is reasonable. The last part of the storage module memory may be bad and perhaps in trying to access it remotely multiple times the situation above resulted. |
| Suggestions: | |
| Measurements: | sgp5ebbrE8.b1: more
sgp15ebbrE8.b1: more sgp30ebbrE8.b1: more |