1 / 35

WP 09 Monitoring & Forecasting Thematic & Assemby Center for IBI MyOcean2

WP 09 Monitoring & Forecasting Thematic & Assemby Center for IBI MyOcean2 V4.1 Acceptance & V5 Design Workshops – June 2014. MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014. List of PUs / Du.

effie
Download Presentation

WP 09 Monitoring & Forecasting Thematic & Assemby Center for IBI MyOcean2

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. WP 09Monitoring & Forecasting Thematic & Assemby Center for IBI MyOcean2 V4.1 Acceptance & V5 Design Workshops – June 2014 MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014

  2. List of PUs / Du MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014

  3. Products evolution in V4.1 MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014

  4. Products evolution in V4.1 • IBI_ANALYSIS_FORECAST_PHYS_005_001 • dataset-ibi-analysis-forecast-phys-005-001-hourly • dataset-ibi-analysis-forecast-phys-005-001-daily • IBI_REANALYSIS_PHYS_005_002 • dataset-ibi-reanalysis-phys-005-002-hourly-regulargrid • dataset-ibi-reanalysis-phys-005-002-daily-regulargrid • dataset-ibi-reanalysis-phys-005-002-monthly-regulargrid • dataset-ibi-reanalysis-phys-005-002-monthly-nativegrid • IBI_REANALYSIS_BIO_005_003 • dataset-ibi-reanalysis-bio-005-003-monthly-regulargrid • dataset-ibi-reanalysis-bio-005-003-monthly-nativegrid PHY Vars: Tmp, Sal, U, V, SSH BGC Vars: Chl,Fer,NH4,NO3,O2,PO4,Si,Phytoplanckton, primary production & euphotic zone depth MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014

  5. Products evolution in V4.1 • IBI-REA & IBI-OP Systems: Analogies & differences… IBI-REA System IBI-OP Ocean Forecast System Model: NEMO (v2.3) Resolution: 1/12º (6Km)/75lev Atm. forcing: 3h - ERAinterim Ocean BC & IC: MyO GLO-Reanalysis Tidal forcing: 11 harmonic components (FES2004 & TPXO7.1) River discharges: flowrates for 33 rivers, usingclimatological data Model: NEMO (v3.4) Resolution: 1/36º (2Km)/50lev Atm. forcing: 3h ECMWF Model Ocean BC & IC: MyO GLO Forecast System Tidal forcing: 11 harmonic components (FES2004 & TPXO7.1) River discharges: flowrates for 33 rivers, using PREVIMER obs, SMHI E-HYPE model & clim data Data Assimilation component SAM2 (Mercator-Ocean; Lellouche et al., 2013), Reduced-order Kalman filter (SEEK or Singular Extended Evolutive Kalman filter). Observations: SST: AVHRR + HR Multi-Sat SLA: all sat data available In-situ OBS: CORA3.4 (including ARGO T&S obs) IBIop-PHY Today… 04/2011 IBIre-PHY 12/2011 02/2002 IBIre-BGQ

  6. Interfaces evolution in V4.1 • IBI Interface tests performed for V4.1 • Interfaces tested: DGF/SUBS/WMS • No MyO-FTP used for IBI product dissemination • Datasets tested: new V4.1 IBI REA products • IBI DU Interface tests done in a testing environment • DU testing environment independent from the Operational DU • (as in previous Vx Reviews). • Virtual machine used for testing, analogous (in terms of resources & communication facilities) to the operational one. • Adequate extrapolation of performance result from test environemnt to future operational ones. DU OP Dissemination (V4 & future V4.1): http://puertos.cesga.es/mis-gateway-servlet/Motu While testing environment: http://test-puertos.cesga.es/mis-gateway-servlet/Motu MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014

  7. Technical tests on Interfaces for V4.1 • IBI DU pass successfully the performance test • Both in terms of processing time, download rate and number of simultaneous connexions. MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014

  8. Technical tests on Interfaces for V4.1 • However, a last-minute “surprise” when testing!: • Problem to disseminate IBI-REA datasets in native grid through SUBS interface. • Problem seems related to have in the same file variables defined in different grids (native grid is a staggered ARAKAWA-C): • netcdf IBIreV1r1_PHYNA_01mav_20040201_20040229_R20131106_RE01 { • dimensions: • depth = 75 ; • latitude = 504 ; • longitude = 296 ; • longitude_U = 297 ; • latitude_V = 503 ; • time = 1 ; • Dimensional variables: • float time(time) ; • float depth(depth) ; • float latitude(latitude, longitude) ; • float latitude_U(latitude, longitude_U) ; • float latitude_V(latitude_V, longitude) ; • float longitude(latitude, longitude) ; • float longitude_U(latitude, longitude_U) ; • float longitude_V(latitude_V, longitude) ; • Variables: • short temperature(time, depth, latitude, longitude) ; • short salinity(time, depth, latitude, longitude) ; • short ssh(time, latitude, longitude) ; • short u(time, depth, latitude, longitude_U) ; • short v(time, depth, latitude_V, longitude) ; MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014

  9. Technical tests on Interfaces for V4.1 • Problem limited to MOTU SUBS. IBI-REA Nativegrid files OK with: • THREDDS (Catalog OK). • OpenDap / Subsetter services • WMS • IBI-REA Nativegrid datasets served through DGF without problems. • SUBS Issue scaled to CIS-Op Team. Waiting for advise, in the meantime, Natrivegrid datasets declared in the EPST as …. MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014

  10. Product Content Verifications for V4.1 • Consultation to CF-metadata mailing list • CF-metadata@cgd.ucar.edu • http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata • Evolving situation in CF convention for the 2 BGQ variables (name/unit). • currently, not rightly included in the Reference Table (v26). But should be OK in the following CF Table update (v27). • CF Inconsistency in BIO datasets • 2 errors found in monthly BIO files • Variable name for Euphotic Zone Depth var • Units for the Primary Production variable MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014

  11. Scientific reporting for V4.1 • Product validated & Validation Tasks: • IBI_REANALYSIS_PHYS_005_002 • Validation focused on monthly data • MO PU (producer of the IBI-REA) • Validation focused on high-frequency data • PdE PC • IBI_REANALYSIS_BIO_005_003 • Validation based on metrics computed from monthly data (MO PU) • Overview & Results on the IBI-REA Validation Activities in: • MYO2-ScVR-REA-IBI-v1.0 • MYO2-IBI-QUID-REA-005-002 (PHY) • MYO2-IBI-QUID-REA-005-003 (BGQ) MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014

  12. Scientific reporting for V4.1 • IBI_REANALYSIS_PHYS_005_002 T-CLASS1-SST-MEAN T-CLASS1-SST-TREND IBI-REA Vs AVHRR (2002-2011) This kind of IBI-REA metric will be included in the OSR MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014

  13. Scientific reporting for V4.1 • IBI_REANALYSIS_PHYS_005_002 S-CLASS4-LAYER T-CLASS4-LAYER Regional IBI-REA improves significantly Climatology & provides some added value regarding global GLO REA MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014

  14. Scientific reporting for V4.1 • IBI_REANALYSIS_PHYS_005_002 Estimated Accuracy Number computation: MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014

  15. Scientific reporting for V4.1 • IBI_REANALYSIS_PHYS_005_002 • Example of IBI-REA Validation on monthly basis UV-CLASS1-15m_MEAN Information from a long list of metrics based on monthly data (> 20) available in the QUID…. MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014

  16. Scientific reporting for V4.1 • High frequency IBI REA Val with in-situ data from moorings (PdE PC) • Metrics computed using high frequency (1-h) in-situ measured data over the 10-yr period across 14 moorings from the Puertos del Estado Network. • Remark: This validation exercise is performed with independent in-situ observational data (in the sense of non-assimilated in the IBI-REA system). • Quite valuable exercise to evaluate the skill of the IBI-REA system in coastal areas. MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014

  17. Scientific reporting for V4.1 • IBI_REANALYSIS_PHYS_005_002 • High frequency IBI REA Val with data from moorings SST-CLASS2-HF-MOORINGS MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014

  18. Scientific reporting for V4.1 • IBI_REANALYSIS_PHYS_005_002 • High frequency IBI REA Val with data from moorings SST-CLASS2-HF-MOORINGS MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014

  19. Scientific reporting for V4.1 MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014

  20. Scientific reporting for V4.1 • IBI_REANALYSIS_PHYS_005_002 • Water masses (density) Bilbao, 2011 Silleiro, 2011 Valencia, 2011 Cadiz, 2011 vv Tenerife, 2011 T/S Diagrams MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014

  21. Scientific reporting for V4.1 UV-CLASS2-HF-MOORINGS Gran Canaria, 2011 v OBS IBI-REA IBI-REA AUG-2011 OBS Gran Canaria, DJF-2011 OBS IBI-REA IBI-REA OBS SEP-2011 Progressive Vectors MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014

  22. Scientific reporting for V4.1 • IBI_REANALYSIS_PHYS_005_002 • High frequency IBI REA Val with data from moorings Bilbao, 2011 Silleiro, 2011 Valencia, 2011 Cadiz, 2011 Tenerife, 2011 Taylor Diagrams MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014

  23. Transition Planning for V4.1 • Provide planning information regarding parallel availability from V4.1 launch : • Are you able to provide a double dissemination • If yes, which will be the period of double dissemination… • If not, which are the difficulties (to anticipate user communication) Not Applied: new V4.1 IBI-REA Products Static MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014

  24. Documentation delivered MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014

  25. Main Architecture Elements reminder ECMWF Atm forcing Glo MFC: Provision of Initial and bdy data SST TAC SL TAC INSITU TAC External inputs Internal inputs ftp ftp ftp, Motu OBS Preprocess. OBS Preprocess. log files log files Validation Validation NEMO IBI PdE PU: CESGA, Finisterrae NEMO IBI MO PU:Meteo France Outputs Outputs Products Products BACK-UP Capability: exchange Of files in case of incident ftp IBI-CLS-TOULOUSE-FR DU IBI-PUERTOS-MADRID-SP DU MIS-GW (Subsetting, WMS, DGF) MIS-GW (Subsetting, WMS, DGF) MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014

  26. List of implemented interfaces <PU> = SST-IFREMER-BREST-FR • highlight scheduled changes MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014

  27. List of implemented Interfaces :<PU> = IBI-PUERTOS-MADRID-SP MyOcean2 Design Workshop – Barcelona 6,7,8th June 2012

  28. List of implemented Interfaces :<DU> =IBI-CLS-TOULOUSE-FR MyOcean2 Design Workshop – Barcelona 6,7,8th June 2012

  29. Products evolution foreseen for V5 MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014

  30. Interfaces and system evolution foreseen in V5 • Provide information on interfaces evolution foreseen in V5 • No changes expected on interfaces • 2 types of system changes foreseen for V5 • Changes associated to potential upgrades in the IBI NEMO model application or updates of any required external inputs. • Changes required in the IBI operational suite to adapt it to any novelty (upgrade) of the computing environment existing at that time. MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014

  31. V5 Master schedule plan • Present here the main steps and planned dates of the developments for your WP in V5 • List issues, risks … (if any) MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014

  32. Master Schedule (review of the 1st MyO-2 Master Plan)    Tested, but decided not to be applied at MyO2 stage Testing delayed to MyO2 end (Op impl. at V5; if demonstrated) Testing delayed to MyO2 end (Op impl. at V5; if demonstrated)  Tested, but decided not to be applied at MyO2 stage Still on the plan … MyOcean2 Design Workshop – Barcelona 6,7,8th June 2012

  33. Master Schedule Plan for MyO-FO and beyond (Copernicus….) MyOcean2 Design Workshop – Barcelona 6,7,8th June 2012

  34. V5 Master schedule plan • List issues, risks … (if any) • V5 fixed at the end of MyO-FO. (Acceptance in Dec-2014) • Jump from MyO-2 to MyO-FO and the short time extension of MyO-FO (6 months) introduce some risk of discontinuity in the Team (risk high at PdE PC). • Very likely we will have to face a temporary limitation in terms of human resources for the MyO-FO period. • Activities related to provide the committed Operational Service will be the priority (and will not be affected). • However, R&D activities, Tier-1 and system updates capabilities may be affected by the human resources gap. • This is main reason because some continuity between V4 and V5 is planned. • Leaving significant changes ahead for further Copernicus upgrades. MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014

  35. V5 Change impact • Provide information on products updates likely impact (on external or internal users (TAC MFC)) • Provide information on impact mitigation (double dissemination timeframe, availability of samples, …) MyOcean2 V4.1 Acceptance & V5 Product Design Workshops – June 2014

More Related