1 / 14

International Argo Data Management Team

International Argo Data Management Team. S Pouliquen 9th Argo Steering Team meeting Paris 18-20 March 2009. Current Status: Active Floats by DAC. 2008 Compared to 2007 Active Floats: 2 949 (216 on Grey List) + 259 floats( +10% )

aviv
Download Presentation

International Argo Data Management Team

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. InternationalArgo Data Management Team S Pouliquen 9th Argo Steering Team meeting Paris 18-20 March 2009 AST9 Exeter March 18-20

  2. Current Status: Active Floats by DAC 2008 Compared to 2007 Active Floats: 2 949 (216 on Grey List) + 259 floats( +10% ) Total Floats: 5 258 (688 on Grey List) +753 floats ( +16,7%) 10 Dacs (+ GTS) + 1 Dac AST9 Exeter March 18-20

  3. Current Status: Real-time Distribution • 90% within 24 hours • GTS problems solved - mostly • BUFR distribution started in Nov 2007 at JMA MEDS is about to start. Others are testing with ir tools to transform NetCDF into BUFR provided by JMA and MEDS AST9 Exeter March 18-20

  4. GTS only floats • Most of active floats are processed by DACs • GTS directory • Data quality suspicious • Inappropriate for DM applications • mainly USA Argo equivalent • Generate a lot of questions and interrogation from users • Decision taken to remove this directory from GDAC AST9 Exeter March 18-20

  5. What need to be improved • Some bad data still passing through the automatic tests improvement of RT test accepted . Some more improvement under test • Perform RT consistency test in near-real time to detect earlier that in DMQC suspicious floats. AST9 Exeter March 18-20

  6. Delayed mode processing Total Profiles: over 400 000 Delayed Mode 175 084 43.7% +86% DM profiles compared to 2007 _ AST9 Exeter March 18-20

  7. Delayed mode processing • All teams are making progress • But slower then planned as procedures were not stable yet and a lot a reprocessing have been necessary and man power insufficient • More training in some “difficult” areas would be welcome • The new version of the DMQC software was welcomed in some areas • There is a need for DMQC-3 workshop AST9 Exeter March 18-20

  8. DMQC on trajectory • Some progress at national level but missing a leader on this activity • Coriolis took the lead on Provor and will provide guidelines. • What about APEX ? • A real effort need to be put on cleaning up trajectory files before a good velocity product is issued • Important to know for each float what is it’s version and may be an information provided in notification forms as critical for technical parameters decoding which have not yet been really used… AST9 Exeter March 18-20

  9. Developments Done at GDACS • Expanded consistency checks at GDACs • Implement recommendations of DMQC-2 • Implemented consistency check within profile files ( under test) • Metadata checker • Nothing done on trajectory because no clear recommendations provided • GDAC are stable and working • GDAC synchronization : it’s working. Improvement in monitoring and reporting has been done _ AST9 Exeter March 18-20

  10. Developments done in 2007 • Real-time salinity drift adjustment • Persistence from last DM offset computed from the deep profile • JMA done 07 • Meds done 07 • AOML : done in RT MAR 07, ( started on past profiles mifd Dec) • Coriolis : June 07 • INCOIS: August 07 • CSIRO: want to do additional test to verify against CDT correction applied at present in RT • BODC : no offset to apply • CSIO: ?? • Korea: no offset to apply AST9 Exeter March 18-20

  11. Reference DB for Argo • Decision on how to progress : • Provide visibility on what exists • Coordinate with NODCs and CCHDO to set up appropriate data flows • Develop procedures for yearly updates • End 2006: Provide a WWW page at GDAC that provide links to the different Regional Reference Databases: http://www.coriolis.eu.org/cdc/argo_rfc.htm • April 2008 : new version of the Reference DB including WOD2005 and CCHDO/NODC updates AST9 Exeter March 18-20

  12. Data Format • Technical Parameters : a nomenclature was proposed to name the parameters . Should be validated by Dacs this month and implementation planned before ADMT9 • Example • PRESSURE_SurfaceOffsetTruncatedPlus5M_dBAR: If the pressure is truncated and 5m has been added (Apex floats with the older APF8 boards) • PRESSURE_SurfaceOffsetNotTruncated_dBAR If the pressure is true as measured (+/-, nothing added) (most other floats and APEX floats with new APF8or APF9 boards), AST9 Exeter March 18-20

  13. Developments for the Coming Year • Argo Regional Centers • Developing at very different rates • There is a need to coordinate activities of ARCs • Lack of scientific man power on the Data consistency issue which is not as trivial as expected • Actions are progressing less rapidly that it used to be/ Does it show a Man power problem at Dacs to handle these 3000 floats … AST9 Exeter March 18-20

  14. Messages to AST • RT processing is automatic and bad data are passing through: important to get tools to detect bad data in the Argo dataset earlier than DMQC • There are still bad flagging/data in DM files and it’s urgent to review the DM dataset… Moreover some training on the method is needed • Need a leader who can dedicate significant time on trajectory data to steer the work • What about Glider data and Argo : We have a format to propose but to whom??? • Man power is an issue in data management and must be taken into account while setting priorities AST9 Exeter March 18-20

More Related