130 likes | 238 Views
Status of Anomalies at GDAC. C. COATANOAN & C. PERTUISOT. Anomalies at GDAC. How are detected the anomalies ? What kind of anomalies are detected ?. Process of quality control. Argo data submission. Flow of raw data ctd, xbt, …. Automatic tests, visual control. Objective analysis.
E N D
Status of Anomalies at GDAC C. COATANOAN & C. PERTUISOT
Anomalies at GDAC How are detected the anomalies ? What kind of anomalies are detected ? Process of quality control Argo data submission Flow of raw data ctd, xbt, … Automatic tests, visual control Objective analysis Detection of anomalies database • Examples of anomalies (some of them corrected after detected by objective analysis) • Drift on salinity • Bad data on the last measurement (and first measurement) • Bad salinity associated to spikes • Bad data on a part of the profile (doubtful sensor)
Anomalies at GDAC Spike
Anomalies at GDAC CORRECTED
Anomalies at GDAC CORRECTED
Anomalies at GDAC CORRECTED
Anomalies at GDAC CORRECTED
Object :Your greylist file collect failed aoml_greylist.csv Sorry, your greylist file was rejected - DAC : aomlMetadata file doesn't exist for platform : 5900230Bad parameter FLUO for platform : 5900230Invalid start date 20080232 for platform : 39008Bad quality code 5 for platform : 39008Bad DAC XX for platform : 39008 Anomalies at GDAC • - Some of all the detected anomalies are due to automatic tests that are not sufficient to detect bad data. • - Some are corrected directly by the DAC with, or not, feedback from the GDAC. • - Actions done : Automatic feedback (in text files) to DAC • for incorrect greylist • in order to update the flags : • a daily email which contains the list of Argo profils highlighted by Objective Analysis and corrected by a Coriolis operator. • Informations also in csv format on • ftp://ftp.ifremer.fr/ifremer/argo/etc/ObjectiveAnalysisWarning • - Using feedback from the Altimetry comparison to correct some profiles (see next presentation)