1 / 19

Argo data management report IAST6 9-10 March 2004 S Pouliquen- M Ignaszewski- B Keeley

Argo data management report IAST6 9-10 March 2004 S Pouliquen- M Ignaszewski- B Keeley. The Argo Data System. Data collection and certification. Prepare data for distribution. Data sent ashore in hours. Information about Argo. Long term archive. Here is the master copy of the data.

osgood
Download Presentation

Argo data management report IAST6 9-10 March 2004 S Pouliquen- M Ignaszewski- B Keeley

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. Argo data management reportIAST6 9-10 March 2004S Pouliquen- M Ignaszewski- B Keeley Data Management Report AST6 9-10 March 2004

  2. The Argo Data System Data collection and certification Prepare data for distribution Data sent ashore in hours Information about Argo Long term archive Here is the master copy of the data Regional analyses Data Management Report AST6 9-10 March 2004

  3. Functions - - - - - Delayed mode QC - Interface with DACs PI - - DAC - - - Data collection - Real Time QC - Interface with PIs - National Distribution - Archive UnderPIControl Provide a unique access both in Real Time andDelayed mode to all the Argo data processed by the DACs GDAC - Delayed mode QC at Basin Level- Elaboration of Products RDAC Data from Instruments Data Management Report AST6 9-10 March 2004

  4. Argo data quality control elements * All data can be obtained from the two Argo Global Data Assembly Centres: Coriolis at IFREMER, and USGODAE at Monterey. Real-time (RT) data stream Function: Apply agreed RT QC tests to float data. Assign quality flags. Users: Operational centres, data assimilation, researchers needing timely data. Timeframe: 24-48 hrs after transmission. Who/Where: Perform by National Data Assembly Centres. Data from floats Delayed-mode (DM) data stream Function: Apply accepted DM procedures to float data. Provide statistically justified corrections using accepted methods. Provide feedback to RT system. Users: All needing adjusted data with error estimates. Timeframe: 6-12 months after transmission. Who/Where: Perform by PIs with DM Agencies or Regional Centres. Regional Analysis Function: Provide basin-wide synthesis of all float data with other available data. Users: Researchers of climate change and model validation. Timeframe: Lifespan of float. Who/Where: Perform by Regional Centres. FUTURE Data Management Report AST6 9-10 March 2004

  5. Argo profiles at GDACS Real time status • 6 Dacs reporting to GTS and GDACS Actif Float profiles at GDACS Data Management Report AST6 9-10 March 2004

  6. Real time status Data Management Report AST6 9-10 March 2004

  7. Real time status Data Management Report AST6 9-10 March 2004

  8. Real Time Status Actions on the way to reduce the number cycles only received on GTS • Data arriving in REAL TIME: mainly put on GTS by CLS • At French level : CLS will transmit data of the floats they put on GTS (after the agreement of the PI) to Coriolis in order to generate the GDAC netcdf file. • AT USA level Navocean will work with AOML to put their data on GDAC • Historical data that arrived through GTS • An inventory will be made by GDAC and each country will have the list of their country floats. • An action will be made by these dacs with Pis to recover part of backlog with priority to still active floats. • Our (ambitious ?)goal reduce GTS to less than 5% in realtime data flow and 10% in historical dataset Data Management Report AST6 9-10 March 2004

  9. Real Time status Data on GTS Data Management Report AST6 9-10 March 2004

  10. Real Time Status 3131 new profiles arriving at Gdac from 26th January to 26th February from more than 1100 floats Data Management Report AST6 9-10 March 2004

  11. Good coverage complementary to other data sets…. XBT/CTD fromResearch and opportunity vessels Moorings Data Management Report AST6 9-10 March 2004

  12. On the way to delayed mode data • On 11 February the data format was changed to Version 2.1 at the GDACs to prepare for the transmission of delayed mode data from the Dacs to Gdacs • The transition went smoothly at both GDACs. Normal GDAC operations were affected only minimally. All of the data files on both GDACs are in the new format. • The Format Control document will be updated to address problems encountered during the transition. • The consistency of the file formats between DACs is much better now. • Better communication of changes with users are necessary. More lead time and wider dissemination required. • Some Numbers: • 1422 Floats • 57479 Profiles coming from AOML 22662 / BODC 3954 / CORIOLIS 12229 CSIRO 1806 / JMA 12421 / MEDS 4407 Data Management Report AST6 9-10 March 2004

  13. Delayed mode data • No data yet available at Gdacs end of February 2004 • Format conversion was needed to handle the DM data and we only agreed in November • QC process wasn’t nailed down before DM meeting last November • A few dacs are either ready to send data (CSIRO, MEDS, AOML) or setting up the system to provide data ( Coriolis ). Status of BODC and Japan not known yet. • Next goal is to have some delayed mode data before summer 2004 or at latest next ADMT meeting Data Management Report AST6 9-10 March 2004

  14. Some new topics • New QC tests implemented in Realtime to make automatic QC more robust: • Detection of parameter Jumps • Identification of suspicious Floats (grey list) • Frozen profile ( definition ofthe test under ADTM validation) • New parameters available: • Oxygen value are available on floats delivered by AOML and soon by MEDS • Format able to handle them easily Data Management Report AST6 9-10 March 2004

  15. Global Argo Data Repository The Roles of GADR and GDAC have been clearly defined • GDAC: • Acquire float metadata ,real-time profile, trajectory, and technical information from DACs within 24 hours of float reporting for and within 6 months for delayed mode. • Refresh delayed mode profile, trajectory, and technical information from DACs as corrections come from PIs resulting from QC or data analysis activities. • Provide ftp access to data and information on a basin, float or receipt time basis and WWW to data and information based on a variety of selection criteria including area, time range, float identifiers. • GADR • Archive metadata from GDAC on a regular schedule and delayed profile, trajectory and technical information from GDAC on a regular schedule. • Provide WWW data integration tools to allow clients to get Argo float data combined with data collected with other instruments. • Provide tools to allow transformation of Argo and other profile data into other forms such as would be suitable for display software such as ODV or OceanAtlas. • Provide hardcopy data sets for distribution to users. • "Register" the Argo data in international data inventories such as FGDC. Data Management Report AST6 9-10 March 2004

  16. GADR • Elaboration of the first issue of the ARGO CD is on the way: • Provide both Data, tools and documentation • Data format is the same as at Gdacs • Some HTML visualization are provided derived from WOCE experience • A draft have been issued and review by an ad hoc group • Second draft is on the way. Do some members of AST want to review this new issue? http://argo.nodc.noaa.gov/cd_1 and http://argo.nodc.noaa.gov/cd_2 • The goal is to get the master before summer and distribute it before the end of the year 2004 Data Management Report AST6 9-10 March 2004

  17. Ifremer JAMSTEC IPRC INCOIS IPRC JAMSTEC CSIRO BODC BODC BODC Regional Dac: the step to start in 2004 • 1.   Compare all of the Argo data in their region of interest with each other and with the best available recent CTD/hydrographic data. • 2.    Establish a mechanism, in concert with other regional centres and DACs, for sending feedback to the PIs to alert them to apparent problems in their data. • 3.    Develop climatologies in concert with other regional centres.. • 4.    Prepare and distribute Argo data products and services on a regular schedule.. • 5. Provide documentation of their procedures. AOML Data Management Report AST6 9-10 March 2004

  18. Next steps and questions to science team • Delay Mode QC: • The question of QC on sliding window was not solved at ADMT meeting. If we do a sliding window QC what is the size of the window12month window with 6 month delay ? [T-6: T+6] • Feedback to real time of correction made in delayed mode?1-Tank/Lab/ First CTD offset to provide early Param-Ajusted data2- offset and drift calculated for ]T: T+6] in Param-Ajusted data • How to organize feedback from users especially operational users ? • Do we need to improve trajectories data? If yes how ? • AST to stamp Scientific products that should be advertised through AIC • AST to define the statistic to evaluate the behaviour of the Argo fleet • AST to help setting up RDACs Data Management Report AST6 9-10 March 2004

  19. Data and Information Access Information on Argo http://argo.jcommops.org/ Data from GDACs http://usgodae1.fnmoc.navy.mil/argo/argo.html http://www.ifremer.fr/coriolis/cdc/ Global Argo Data Repository http://www.nodc.noaa.gov/argo Data Management Report AST6 9-10 March 2004

More Related