1 / 50

Argo Status AIC & JCOMMOPS Development

Argo Status AIC & JCOMMOPS Development. M. Belbeoch, Argo TC AST #9 Mar. 2008, Exeter, UKMO. Network Growth. Network Growth. Deployments. Yearly Deployments. Argo Status: Implementation. 2007 Deployments. Network Coverage. Network Age. Age Distribution. Critical Areas.

arista
Download Presentation

Argo Status AIC & JCOMMOPS Development

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. ArgoStatusAIC & JCOMMOPSDevelopment M. Belbeoch, Argo TCAST #9 Mar. 2008, Exeter, UKMO

  2. Network Growth

  3. Network Growth

  4. Deployments

  5. YearlyDeployments

  6. Argo Status: Implementation

  7. 2007 Deployments

  8. Network Coverage

  9. Network Age

  10. Age Distribution

  11. Critical Areas

  12. DeploymentFailure Rate

  13. YearlySurvival Rate

  14. YearlySurvival Rate

  15. Data Management

  16. ArgoStatus: Implementation

  17. AIC: Background • The AIC is participating in the activities of the Argo Project Office and of the JCOMM in situ Observing Platform Support Centre (JCOMMOPS) • The AIC was established in 2001, Toulouse, France. • The AIC is hosted by CLS • TC is employed by IOC and acts in close collaboration with IOC and WMO secretariats • The AIC is funded on a yearly basis through voluntary contributions from Australia, Canada, France, UK and USA • In 2007 China, India and Germany also began providing funds for the AIC

  18. TC Activities In 2007 progress was made on the following issues: • Improve Argo implementation monitoring and planning: • improve and document the notification mechanism • develop new products (maps, statistics, GIS data layers, web pages, text file exports) • Improve Argo Data distribution monitoring: • New set of statistics on real-time and delayed-mode profiles • Rationalize the support to Argo users • Support Centre developed • Improve monthly reporting to PIs/Programmes Managers, float operators and data managers • Upgrade the JCOMMOPS information System: • New server installed and configured • Software upgrade (in particular the GIS) • Routine scripts and procedures reviewed and rationalized (in particular the GIS data layers update and text files export)

  19. TC Activities • Finalisation of the new AIC website • Stability • 24/7 monitoring set up • Many details and content reviewed • Audience Tracking system set up (including Project Office website) • International issues • Reporting to Member States on the status of their EEZs • New tools developed to monitor floats entering EEZs • New tools developed to monitor beached floats • Cooperation initiated with new partners (e.g.: Gabon, Morocco)

  20. TC Missions 2007 TC Missions: • Visit Ifremer / IRD / Meteo-France (with TC DBCP), Brest, France • EURO Argo, and North Atlantic Argo Regional Centre #2 meetings, Brest, France • Argo Steering Team#8, IOC, Paris, France • ABE-LOS #7, Libreville, Gabon • JCOMM OCG, Geneva, WMO Switzerland • Visit SIO/SOA, Hangzhou, China • Argo Data Management Team#8, Hobart, Australia • GEO Ministerial Summit, Cape Town, South Africa • ABE-LOS informal workshop, Washington, USA

  21. TC Missions Proposed Missions for 2008: • Euro-Argo kick-off meeting, Brest, Ifremer, France (done) • Bio-Argo #1 meeting, Villefranche, France (done) • Argo Steering Team#9, Exeter, UK • ABE-LOS #8 Paris, IOC, France • IOC/GOOS & JCOMMOPS, IOC, France • ADMT #9 Hawaii, USA • Euro-Argo Users Workshop, NOC, UK If budget permitsit: • IOC Assembly • Visit new AIC contributor INCOIS, Hyderabad, India / ArgoIndia meeting • Visit new AIC contributor, Germany • New participating Countries (Morocco, Gabon, other) • Visit to Scripps Project Office

  22. InformationSystem • Essential links with platform operators, Argos location system, the GTS of WMO and various Data Centres • Independent float/buoy tracking (XX-6 Resolution.)and network monitoring • New server installed: final architecture set up • 24/7 web services Monitored by CLS operators • Basic maintenance contractedwith host.

  23. Website Audience 4,383 Visits 18,129 Page Views 4.14 Pages/Visit 00:03:16 Avg. Time on Site 3,081 Absolute Unique Visitors Main Pages:FloatSearchEngine, Planning, Interactive Map, News (float of the month), Stats

  24. AIC: Planning and Notification • Core function of the AIC reviewed, improved and documented • Some progress made … but some additionnal efforts required • Information vital for: • Implementation and maintenance of the global array • Project transparency and accordance with international rules • Cooperation within Argo and with other panels (e.g. DBCP)

  25. AIC: Planning & Notification • Argo needs to organize efficiently its own planning • Maintain an optimal coverage • Make an optimal use of ship time • Share and extend deployment opportunities • TC took step to facilitate regional coordinators work • Establishing a centralized mechanism to update all plans • Extending the regular notification process • Draft mode added • Text file loader added • User Guide issued • Many exchanges with float operators • Providing new (R/T) products: web pages, ASCII files, GIS data layers • Monitoring network coverage, age, lifetime • Sensors information added • Argos data formats to be added

  26. Notification delays

  27. AIC: Planning & Notification • Main metadata are QCed by TC • Potential problem can be detected in advance • E.g.: duplicate or wrong WMO/Argos Ids • To notify via the AIC before the DACs • Can help DACs to set up data processing before 1st profile is sent (e.g. Coriolis and EU floats)

  28. AIC: Planning & Notification Goal: cross all data layers: floats, density, age, plans, SOOP lines, past/planned cruises, etc …

  29. AIC: Google Earth More links to be added (DACs, ARCs, models outputs, etc …)

  30. Argo Data Management Monitoring • Float data distribution is verified • on GTS (daily + monthly stats from Meteo-France) • at Argo GDACs (daily stats from Coriolis index files) => need to detect breaks in data distribution • New developments: • Daily update from GDACs improved for delayed-mode files tracking • New charts for RT and DM data distribution (global, per country/program) • Summary put in AIC monthly report • Traj. files monitoring started • Argo Support Centre: • Growing user community • Support activities need to be strengthen and organized properly • Argo Forum/Blog to foster informal discussions

  31. AIC: Support Centre

  32. AIC: Support Centre

  33. AIC: Support Centre

  34. AIC: Support Centre A few requests were already processed through this system concerning: • float metadata files (incomplete for “/gts” directory data) • Data downloading difficulties at GDACs • Argo generalities (e.g.: float end of life) • Access to data in ASCII • Information on all official float deployments • Data in RedSea • Impossible downloading big data files at GDACs • It is suggested to promote this address on ALL Argo websites • Feedback to data producers will be improved …

  35. ADMT #8 Actions • Provide access to the support@argo.net question/answer database to AST/ADMT chairs. Completed: I decided to make the requests public so users can check their request was recorded. Most interesting question/answers can be tagged “FAQ”. • 2) Establish an Argo user mailing list. Completed: argo-du@jcommops.org Need to subscribe appropriate users (keeping in mind upcoming EURO-Argo data users meeting) • Provide to AST chairs the list of operators that notify with delay their floats. Completed • Include J. Gilson report on suspicious floats/profile detected. No input for now. • Modify the text to the Support Centre to encourage users to report on data quality. Completed. To improve. • Argo forum to be set up. Completed: argo-forum@jcommops.org An Argo blog was set up as well: http://argo3000.blogspot.com

  36. International issues: Beached Floats • The adhesive Argo label has proven its worth • AIC assist in the retrieval of beached instruments (if the program requires it) • Excellent opportunity to establish contactsin new regions and communicate on Argoto coastal communities • Tools available at the AIC (based on Argos location Expert System) to locate the float • Tool developed to automatically detect floats on land • Tracked on-line and in monthly reports

  37. UnknownFloattrapped by fishermemen net … • Float arrived last week at the AIC • Usage of Argo label => • Transparency (Notification & tracking via the AIC,...) • Data Sharing • manufacturers were reminded about it

  38. International issues: EEZs • Law of the sea (IOC/ABE-LOS): • IOC Res. XX-6.: “(…) notify to Member States of all floats which might drift into some EEZs (…)” • AIC mechanism could be formally recognized by IOC through a new resolution (next assembly)

  39. International issues: EEZs • In addition to the notification system, some reports are sent to Members States on the status of float within or entering into the EEZs. • Reports are prepared by the AIC and signed by IOC Exec. Secretary (with tables and maps) • Information to be added in the AIC Monthly Report • => Notification is a serious issue • Designate a person representing the institution to record deployment plans via the AIC website • Regularly update the information • Notify the plans when they are finalized • Make sure the information is correct (as best as you can) • DO NOT deploy floats within EEZ without any kind of agreement • ( Daily text file export and GIS data layer are available for floats that entered EEZ).

  40. International issues: Cooperation • Donor programmes: • Develop cooperation • Transfer floats anywhere avoiding custom taxes legally • Fill small gaps in specific areas • Deploy float (for free) in a foreign EEZ avoiding bureaucracy • Foster new participating countries • Modest capacity building initiatives (transfer of marine technology) • Thank countries that helped to retrieve floats • Achieved: Mexico, Costa Rica, Argentina, Mauritius, Brazil, Chile, Ecuador • Ongoing: Dominican Rep. , Kenya, Morocco • Planned: Caribbean Region, Philippines, Columbia, Cape Verde, Sri Lanka, Gabon, Ivory Coast • Time consuming (~2 years of communication ) • Target: long term support • Demand increasing • Contract (approved by UNESCO legal affairs ) ready. • BUT: Kenya story ... 5 floats blocked at Met. Services ...

  41. Planning Beyond AIC routine activities, and AST (and ADMT) suggestions, planning for 2008 can be summarized as follow: • Continue to encourage/assist float operators to notify of deployment plans • Continue to address any issues with the new website • Improve JCOMMOPS Information System operational status • Review AIC/JCOMMOPS Information System documentation • Improve the AIC Monthly Report • Improve the Support Centre • Work on metadata: cycle and Argos/Iridium data formats • Improve data distribution monitoring (GTS/GDACs) • Finalize bi-daily files generation (GIS, text, Google Earth) • Continue to issue reports on EEZ status to IOC Member States. • Improve the Argo websites (work with Megan) • Review all mailing lists subscribers • Update Argo communication material: presentation, poster. • Continue to assist in the float retrieval activities • Continue to foster participation by new countries through donor programmes • Improve (modestly) Argo media coverage via direct contacts or educational initiatives • Assist Bio-Argo initiatives • work on deploymentopportunities

  42. JCOMMOPS JCOMMOPS is a component of the international coordination mechanism, which aims, on behalf of JCOMM, to: • develop synergies between observing systems (Argo, DBCP, SOT) • assist in the planning, implementation and operations of the observing systems • monitor and evaluate the performance of the networks • encourage cooperation between communities and member states • encourage data sharing • assist in data distribution on Internet and GTS • relay users feedback on data quality to platforms operators • provide technical assistance and user worldwide support • act as a clearing house and focal point on all programmes aspects • JCOMMOPS is not a data centre, rather, it: • gathers, QCs, and distributes essential metadata • guides users to data centers • More general information is available at http://www.jcommops.org

  43. JCOMMOPS Challenges • Today, JCOMMOPS faces the challenge of strengthening its infrastructure and eventually extending its operations to new observing systems. • Substantial effort is still required on the JCOMMOPS website and in general within the JCOMMOPS Information System in the integration of all available products. • Main challenge: deployment opportunities information to assist the maintenance of global networks “How can we deploy the required instruments at the required time/space resolution to fill the gaps identified?”

  44. JCOMMOPS & OceanSITES • In 2007: informal discussion (with secretariats and panels chairs) to start OceanSITES coordination within JCOMMOPS • JCOMMOPS would provide support to Argo, DBCP, SOT and OceanSITES: • the DBCP TC would spend 70% of time on DBCP matters and 30% of time on OceanSITES • the Argo TC would spend 70% of time on Argo and 30% on the Ship Observations Team. • JCOMMOPS will gain an additional half-time employee dedicated to I.T. support

  45. JCOMMOPS & OceanSITES • Argo TC mission budget is not sufficient to cover all Argo needs • 10% tax on funds managed via IOC/UNESCO • I.T. support is required for the AIC and JCOMMOPS • Argo TC is more involved in JCOMMOPS administration • The AST is invited to provide feedback on this suggestion • … and to review the Argo TC Terms of Reference

  46. Argo & SOT • SOT (VOS, SOOP):Coordination focused on SOOP • Complementary subsurface observations • Often same agencies/people involved • Potential for tracking deployment opportunities

  47. JCOMMOPS ... JCOMM-OPSC • A Joint WMO/IOC Circular Letter (Sep. 2007) invited institutions in hosting a JCOMM Observing Programme Support Centre (OPSC) • This OPSC would include JCOMMOPS and the AIC • It could include the Project Office and the Argo Director • and coordination for GLOSS, OceanSITES, IOCCP, POGO, ... • 15 Letters of intent received • Short list by April 2008 • 2nd step: Detailed proposals evaluated by a larger committee

  48. JCOMMOPS ... JCOMM-OPSC • 1 CCO Columbia • 2 CPO USA • 3 CLS France • 4 DHN Peru • 5 FMI Finland • 6 ICTP-OGS Italy • 7 IFREMER France • 8 INCOIS India • 9 IMA Trinidad & Tobago • 10 NDBC USA • 11 NMDIS China • 12 NOCS UK • 13 NORI Republic of Korea • 14 SNET El Salvador • 15 VLIZ Belgium It demonstrates a stronginterest for JCOMMOPS activities …

  49. Argo & JCOMM • How Argo could be recognized as a true JCOMM programme? • Informal cooperation for a number of years • In particular through JCOMMOPS joint activities • appropriate time for Argo to move the relationship forward to a more formal level in the context of a “systems” approach to the long term ocean observations • Strongly encouraged by JCOMM • A critical part of this approach has been and will be JCOMMOPS/OPSC. The development of a closer, and perhaps more formal, relationship between the AST and JCOMM/OPA, can only help in this process. • From the perspective of Argo, such a development can also offer substantial advantages: enhanced visibility for Argo and the AST, in particular amongst the national agencies which largely represent Member States on the governing bodies of WMO and IOC; as a side benefit from this, hopefully assistance towards the long-term sustainability of the array; opportunities for closer coordination with other elements of the composite system; etc • The AST is invited to provide feedback to JCOMM on the suggested selection process for the OPSC and on the future relationship Argo-JCOMM.

  50. Thankyou … belbeoch@jcommops.org http://argo.jcommops.org

More Related