DQR ID | Subject | Data Streams Affected | Data Quality Metric |
---|---|---|---|
D141023.4 | ENA/MAG/PVC/TMP/CCN/C1 - Reprocess: CCN temperature unstable flag reversed | enaaosccn100C1.a1 | Incorrect |
D141124.6 | ENA/CCN/C1 - Low concentrations in marine environment | enaaosccn100C1.a1 | Does not affect quality |
D141216.2 | ENA/CCN/C1 - Problem with time fields | enaaosccn100C1.a1 | Suspect |
D160427.7 | ENA/C1 - Reprocess: Slightly incorrect location fields | enaaosccn100C1.a1 | Suspect |
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
02/16/2012 | 0000 | 10/20/2014 | 2359 | Incorrect |
Subject: | ENA/MAG/PVC/TMP/CCN/C1 - Reprocess: CCN temperature unstable flag reversed |
DataStreams: | enaaosccn100C1.a1 |
Description: | The variable CCN-temp unstable is incorrectly defined as a hexadecimal value. The values are 0 or 1 only. The description is also reversed. A value of 1 indicates the instrument is operating stably. |
Measurements: | enaaosccn100C1.a1:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
10/15/2014 | 1200 | 10/21/2014 | 2330 | Does not affect quality |
Subject: | ENA/CCN/C1 - Low concentrations in marine environment |
DataStreams: | enaaosccn100C1.a1 |
Description: | The instrument mentor has been looking at marine CCN results for many years now, and is not really convinced there is a problem. CCN counts get very low in marine environments, down to 5 to 10 counts. Many times this is sudden with a change in the wind. |
Measurements: | enaaosccn100C1.a1:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
10/04/2013 | 0800 | 12/02/2014 | 2028 | Suspect |
Subject: | ENA/CCN/C1 - Problem with time fields |
DataStreams: | enaaosccn100C1.a1 |
Description: | During the ENA deployment the CCN instrument clock was not synched with a time server until 12/2/2014. Starting at about 11/03/2013 the CCN was 60 seconds slow. From that time until the time was manually corrected on 10/07/2014 at 16:00:00 the CCN time gradually got faster relative to the CPC until it was approximately 10 minutes fast. On 12/2/2014 at 20:28:30 the CCN was configured to automatically correct its time from the Unit 1 CPU. Since that time the CCN has been within 2 seconds of the time server except at startup. More recently the setting was changed to keep the CCN within about .6 sec. Generally the time is being corrected by time client about once every 3 days. There have been 2 startups since the time synching was configured. At these times the time was off by more, but was immediately corrected. On 12/30/2014 at 19:28:01 the time was fast 66.235 sec. at startup. On 01/16/2015 the time was fast 38.512 sec. at startup. The Document shows the times of the peaks used to approximate the error in the time. The time was checked about once a week and its assumed that the time drifted gradually between the times in the file. |
Measurements: | enaaosccn100C1.a1:
|
Start Date | Start Time | End Date | End Time | Data Quality Metric |
---|---|---|---|---|
09/29/2013 | 0941 | 04/30/2016 | 2359 | Suspect |
Subject: | ENA/C1 - Reprocess: Slightly incorrect location fields |
DataStreams: | enaaosccn100C1.a1 |
Description: | Some of the instruments are being processed with the previous "GRW-Azores" lat/lon/alt instead of the new "ENA-Azores" lat/lon/alt. The differences are minor, but will be corrected. The respective GRW and ENA lat, lon, and alt values are as follows: GRW lat = 39.0911 ; ENA lat = 39.0916 ; GRW lon = -28.0297 ; ENA lon = -28.0257 ; GRW alt = 26 ; ENA alt = 30.48 ; |
Measurements: | enaaosccn100C1.a1:
|