1 / 13

Monitoring Anomalies in GDAC: Detection, Quality Control, and Correction Processes

This document discusses the status of anomalies detected at GDAC, focusing on the methods used for identification, types of anomalies encountered, and the processes of quality control in Argo data submission. It highlights the flow of raw data, including CTD and XBT measurements, and the automatic tests alongside visual controls employed for analysis. Examples of identified anomalies include salinity drift, bad last measurements, and spikes in salinity. Furthermore, it outlines corrective actions taken by the DAC and daily communications regarding flagged profiles.

sharis
Télécharger la présentation

Monitoring Anomalies in GDAC: Detection, Quality Control, and Correction Processes

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Status of Anomalies at GDAC C. COATANOAN & C. PERTUISOT

  2. 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)

  3. Anomalies at GDAC Spike

  4. Anomalies at GDAC

  5. Anomalies at GDAC CORRECTED

  6. Anomalies at GDAC

  7. Anomalies at GDAC CORRECTED

  8. Anomalies at GDAC

  9. Anomalies at GDAC

  10. Anomalies at GDAC CORRECTED

  11. Anomalies at GDAC CORRECTED

  12. Anomalies at GDAC

  13. 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)

More Related