1 / 12

Argo & New Telecom. Systems Technical Workshop Introduction and Summary.

Argo & New Telecom. Systems Technical Workshop Introduction and Summary. ADMT#11 October 2010, Hamburg/Germany. Workshop Objectives. Need for an overview on the (heterogeneous) practices Users have gained enough experience to feedback Forum to: share some of the knowledge

hila
Download Presentation

Argo & New Telecom. Systems Technical Workshop Introduction and Summary.

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 & New Telecom. SystemsTechnical WorkshopIntroduction and Summary. ADMT#11 October 2010, Hamburg/Germany

  2. Workshop Objectives • Need for an overview on the (heterogeneous) practices • Users have gained enough experience to feedback • Forum to: • share some of the knowledge • discuss the impacts on data processing chains and data formats • Discuss advantages/disadvantages, problems, plans, etc • encourage a broader use of the new systems • report back to the AST Long run objectives: • Rational (raw) formats management • Reduce data management costs • Harmonize practices • Set up a task team (within the AST) to follow up.

  3. Status, as of September 2010

  4. Status, as of September 2010

  5. Status, as of September 2010 350 Iridium floats deployed so far

  6. Status, as of September 2010 • APEX • Start in 2005 • #20 000 profiles available (users interest) • 102 Cycles per Float (CPF) • 82% efficiency • Max age= 1902 days • Dep. failure rate: 4%

  7. Status, as of September 2010 • SOLO • ~70 floats WHOI • High deployment failure rate in the early years • PROVOR/ARVOR • 16 Provor (14 Bio Argo, 2 IFM) • 3 Arvor (France & Italy) • ~100 CPF • Dep. failure rate 0% • POPS: JAMSTEC • NEMO • 10 JAMSTEC & Eq., 2 AWI, 1 POLAND • 84 CPF, 100 PPF • Dep. failure rate 1%

  8. Real-time tracking by the AIC/JCOMMOPS Existing: Argos/Argos-3: database link with CLS (oracle-oracle) Iridium: AOML .phy files (CLS-A), CLS DB, GTS, GDACs, manual Need: • Real-time, impartial, at the air-time provider level. Advantage: • rigorous and transparent Argo status (reliability stats.) • can track float that do not distribute data (or forgotten by their PI) • can detect floats back on line, beached floats, … floats for which data distribution was stopped. • can track new float users and invite them to join Argo, share data … (or not!) Solutions: • SBD (copy the AIC as one of the 5 email addresses) • Copy/Download of RUDICS .msg directly on AIC’s FTP • Synchronization with central Iridium data services (CLS, Joubeh, ?)

  9. Argo & New Telecom. SystemsWorkshop Summary • Workshop was a good initiative. Information need to circulate further. • Most of Argo groups are experimenting Iridium or planning toFirst Argos-3 float will be deployed next month • Good overview on practices that can be compiled (mission/data flow) • Sampling requirements were discussed. • potential bias on the array if mission parameters become too heterogeneous (using downlink or interactively). • Possibility to compress the .msg files in dialup/RUDICS to decrease air-time cost could be requested to manufacturer(s). • difficulties for some users on dialup (multiple connections required => increase cost dramatically). Decrease the number of levels, or use a “kill cmd” might help reduce costs • Users need help to choose between the 3 telecom. methods available: SBD (binary) or dialup/CSD/RUDICs (txt).

  10. Workshop Summary • Concerns with the long run archival of raw data. DAC duty. • Difficulties to fill up meta files properly with mission parameters. Mission conf. changes should be transmitted by floats when possible. • Need of recommendations for reducing the number of sampling levels for TESAC (until we switch to BUFR). • Suggestion to use some standard Argo vocabulary in .msg file (not possible in .sbd) and in manufacturers Users’ manual. • AIC needs a cc of .sbd messages (reserve an email address for the AIC) • Possible “reserved block” for AIC use in iridium .sbd messages. Harmonization? • AIC needs access (FTP) dialup/RUDICS raw .msg files (via dl./upl.) ftp.jcommops.org user=iridium / pw=argofolks • AIC Notification: TELECOM_ID IMEI for SBD / Board# for Dialup/RUDICS (and for netCDFPTT…)

  11. Workshop Summary • Suggestion to run another workshop aside of the AST • Suggestion to set up a Task Team to work on data formats and seewhere harmonization is possible and, where recommendations can be made to Argo groups and manufacturers, in order to, strengthen the Argo core mission, reduce data management costs and,allow flexibility for the future. Short Term Actions • TC to prepare the summary for the ADMT Report • TC put all talks on the AIC website • TC to compile the workshop report (and circulate it before final distribution)

  12. Actions Items • Make recommendations regarding netCDF file. Update Manual. • Make recommendations regarding TESAC levels compression. Update Manual. • DACs are recalled to make sure to archive all raw data (Iridium) • AST to make recommendations regarding sampling scheme(China/India to send their sampling details). • All Argo Programmes to cc AIC on iridium data (.sbd, .msg) • To work ad hoc. • Discuss the workshop outcomes and potential follow up within the AST. (Agenda item for AST#12 and why not another workshop)

More Related