Data Quality Reports for Session: 185822 User: salgueirov1 Completed: 05/24/2017


TABLE OF CONTENTS

DQR IDSubjectData Streams Affected Data Quality Metric
D141023.4ENA/MAG/PVC/TMP/CCN/C1 - Reprocess: CCN temperature unstable flag reversedenaaosccn100C1.a1Incorrect
D141216.2ENA/CCN/C1 - Problem with time fieldsenaaosccn100C1.a1Suspect
D160427.7ENA/C1 - Reprocess: Slightly incorrect location fieldsenaaosccn100C1.a1Suspect


DQRID : D141023.4
Start DateStart TimeEnd DateEnd Time Data Quality Metric
02/16/2012000010/20/20142359Incorrect
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:
  • CCN_temp_unstable_flag


Back To Table of Contents

DQRID : D141216.2
Start DateStart TimeEnd DateEnd Time Data Quality Metric
10/04/2013080012/02/20142028Suspect
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:
  • AOS bin number of lowest channel of OPC include in summation of N_CCN(N_CCN_bin_number)
  • CCN_proportional_valve_voltage
  • CCN_P_sample
  • CCN_Q_sheath
  • CCN_temperature_gradient
  • Altitude above mean sea level(alt)
  • base_time
  • CCN_super_saturation_calculated
  • CCN_laser_current
  • CCN_T_nafion
  • AOS number concentration of CCN(N_CCN)
  • CCN_Q_sample
  • CCN_T_sample
  • CCN_t_read_TEC2
  • CCN_t_read_TEC1
  • AOS CCN droplet count by bin size(N_CCN_dN)
  • CCN_t_read_TEC3
  • CCN_T_OPC
  • time_offset
  • CCN_ss_set
  • East longitude(lon)
  • North latitude(lat)
  • CCN_temperature_std
  • CCN_first_stage_monitor_voltage
  • CCN_T_inlet
  • CCN_temp_unstable_flag
  • time


Back To Table of Contents

DQRID : D160427.7
Start DateStart TimeEnd DateEnd Time Data Quality Metric
09/29/2013094104/30/20162359Suspect
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:
  • North latitude(lat)
  • Altitude above mean sea level(alt)
  • East longitude(lon)


Back To Table of Contents



END OF DATA