WP 09 Monitoring & Forecasting Thematic & Assemby Center for IBI MyOcean2 V4.1 Acceptance & V5 Design Workshops – June 2014 MyOcean2 V4.1 Acceptance &

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

List of PUs / Du


Products evolution in V4.1

Product Customer Name Status

IBI-ANALYSIS-FORECAST-PHYS-005-001-b BaU

IBI_REANALYSIS_PHYS_005_002 New

IBI_REANALYSIS_BIO_005_003 New




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

BGC Vars: Chl,Fer,NH4,NO3,O2,PO4,Si,Phytoplanckton, primary production & euphotic zone depth

PHY Vars: Tmp, Sal, U, V, SSH

Model: NEMO (v2.3) Resolution: 1/12º (6Km)/75levAtm. forcing: 3h - ERAinterim Ocean BC & IC: MyO GLO-ReanalysisTidal forcing: 11 harmonic components (FES2004 & TPXO7.1)River discharges: flowrates for 33 rivers, using climatological data

IBI-REA System

04/2011 Today…IBIop-PHY

IBIre-BGQ

12/2011

IBIre-PHY

02/2002

IBI-REA & IBI-OP Systems: Analogies & differences…

Model: NEMO (v3.4) Resolution: 1/36º (2Km)/50levAtm. forcing: 3h ECMWF ModelOcean BC & IC: MyO GLO Forecast SystemTidal 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 availableIn-situ OBS: CORA3.4 (including ARGO T&S obs)


IBI-OP Ocean Forecast System

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

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.Dataset and Volume/time per Data access service FTP Direct get file Subsetter DataSet Size

Downloading time Processing time Downloading time Total time Processing time Downloading time Total time

Tests 1.1.1 N/A

Tests 1.1.2 00:00:24.94 00:00:04.20 00:00:29.25 58,2MB

Tests 1.1.3 00:00:06.10 00:00:04.34 00:00:10.44 60,1MB

Tests 1.2.1 N/A

Tests 1.2.2 00:00:29.46 00:00:04.64 00:00:34.10 50,5MB

Tests 1.2.3 00:00:05.47 00:00:04.24 00:00:09.71 62,6MB

Tests 2.1.1 N/A

Tests 2.1.2 00:01:47.40 00:00:18.28 00:01:53.43 209MB

Tests 2.1.3 00:00:19.82 00:00:19.90 00:00:39.72 160MB

Tests 2.2.1 N/A

Tests 2.2.2 00:01:47.40 00:00:18.28 00:02:05.69 202MB

Tests 2.2.3 00:01:06.79 00:00:27.10 00:01:33.89 220MB

Tests 3.1.1 N/A

Tests 3.1.2 00:05:43.24 00:00:57.61 00:06:40.85 829MB

Tests 3.1.3 00:02:45.39 00:01:49.11 00:04:34.50 1GB

Tests 3.2.1 N/A

Tests 3.2.2 00:06:27.64 00:01:15.04 00:06:56.76 645MB

Tests 3.2.3 00:04:57.61 00:04:57.61 00:04:57.61 1,3MB



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) ;

http://www.google.es/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&docid=ffu9MYHMOz57OM&tbnid=muPJbib6PnhKDM:&ved=0CAUQjRw&url=http%3A%2F%2Ftrac.mcs.anl.gov%2Fprojects%2Fparvis%2Fwiki%2FDiscretizations&ei=BlODU87EHaez0QX58YHIBQ&bvm=bv.67720277,d.d2k&psig=AFQjCNFn9tHWkF959jaJMQB0L95gGKpLVg&ust=1401201769447102



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 ….

IBI WP9 SUBS DGF WMS IBI_REANALYSIS_PHYS_005_002 dataset-ibi-reanalysis-phys-005-002-hourly-regulargrid

IBI WP9 SUBS DGF WMS IBI_REANALYSIS_PHYS_005_002 dataset-ibi-reanalysis-phys-005-002-daily-regulargrid

IBI WP9 SUBS DGF WMS IBI_REANALYSIS_PHYS_005_002 dataset-ibi-reanalysis-phys-005-002-monthly-regulargrid

IBI WP9 DGF WMS IBI_REANALYSIS_PHYS_005_002 dataset-ibi-reanalysis-phys-005-002-monthly-nativegrid

IBI WP9 SUBS DGF WMS IBI_REANALYSIS_BIO_005_003 dataset-ibi-reanalysis-bio-005-003-monthly-regulargrid

IBI WP9 DGF WMS IBI_REANALYSIS_BIO_005_003 dataset-ibi-reanalysis-bio-005-003-monthly-nativegrid

Product Content Verifications for V4.1


Product specification & dataset/Dataset Status CF Checker NetCDF File Title Date in the WMS

ibi-analysis-forecast-phys-005-001 Ok Ok Ok

dataset-ibi-analysis-forecast-phys-005-001-daily Ok Ok Ok

dataset-ibi-analysis-forecast-phys-005-001-hourly Ok Ok Okdataset-ibi-reanalysis-phys-005-002 dataset-ibi-reanalysis-phys-005-002-hourly-regulargrid Ok Ok Ok dataset-ibi-reanalysis-phys-005-002-daily-regulargrid Ok Ok Ok dataset-ibi-reanalysis-phys-005-002-monthly-regulargrid Ok Ok Ok dataset-ibi-reanalysis-phys-005-002-monthly-nativegrid Ok Ok Ok dataset-ibi-reanalysis-bio-005-003 dataset-ibi-reanalysis-bio-005-003-monthly-regulargrid KO* Ok Ok dataset-ibi-reanalysis-bio-005-003-monthly-nativegrid KO* Ok Ok

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

Consultation to CF-metadata mailing list

[email protected]

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).

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)



IBI_REANALYSIS_PHYS_005_002


T-CLASS1-SST-MEAN

IBI-REA Vs AVHRR (2002-2011)

T-CLASS1-SST-TREND

This kind of IBI-REA metric will be included in the OSR




T-CLASS4-LAYER S-CLASS4-LAYER

Regional IBI-REA improves significantly Climatology & provides some added value regarding global GLO REA




Estimated Accuracy Number computation: Variable Mean RMS error

Temperature (°C) 0-5m 0.16 0.84

Temperature (°C) 5-200m 0.02 0.56

Temperature (°C) 200-600m 0.07 0.40

Temperature (°C) 600-1500m 0.09 0.48

Temperature (°C) 1500-2000m 0.06 0.37

Temperature (°C) 0-2000m 0.07 0.45

Salinity (psu) 0-5m -0.05 0.29

Salinity (psu) 5-200m -0.02 0.15

Salinity (psu) 200-600m 0.01 0.05

Salinity (psu) 600-1500m 0.01 0.08

Salinity (psu) 1500-2000m 0.01 0.06

Salinity (psu) 0-2000m 0.00 0.09


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….


High frequency IBI REA Val with in-situ data from moorings (PdE PC)

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.

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.


IBI_REANALYSIS_PHYS_005_002 High frequency IBI REA Val with data from moorings

SST-CLASS2-HF-MOORINGS



SSTBuoy Year N Obs IBIre Bias RMSE R SI

Bares

2002 6330 15.75 15.26 -0.48 0.80 0.96 0.052003 2653 16.59 16.42 -0.17 0.45 0.99 0.032004 7913 16.15 15.81 -0.34 0.58 0.99 0.042005 6375 17.20 16.90 -0.30 0.55 0.99 0.032006 7285 16.39 16.07 -0.32 0.55 0.99 0.032007 4814 16.29 15.95 -0.35 0.58 0.98 0.042008 7125 16.59 16.32 -0.27 0.49 0.99 0.032009 6317 16.17 15.75 -0.42 0.72 0.99 0.042010 408 20.54 20.28 -0.26 0.46 0.60 0.022011 6406 17.33 16.88 -0.44 0.58 0.98 0.03

Bilbao

2006 345 15.64 15.18 -0.46 0.52 0.54 0.032007 8752 16.78 16.35 -0.43 0.77 0.98 0.052008 5535 16.19 15.73 -0.46 0.67 0.99 0.042009 3116 15.92 15.46 -0.46 0.67 0.99 0.042010 8593 16.96 16.41 -0.55 0.75 0.99 0.042011 8544 17.54 16.98 -0.56 0.71 0.99 0.04

Peñas

2002 4383 14.87 14.18 -0.69 0.97 0.87 0.072003 3341 13.68 13.09 -0.60 0.70 0.85 0.052004 6946 15.84 15.29 -0.55 0.73 0.99 0.052005 5974 15.89 15.24 -0.65 0.91 0.98 0.062006 4066 18.08 17.61 -0.47 0.77 0.99 0.042007 6976 15.72 15.43 -0.29 0.61 0.98 0.042008 7071 17.10 16.33 -0.78 0.99 0.98 0.062009 7142 16.79 16.27 -0.52 0.85 0.97 0.052010 6025 15.90 15.19 -0.71 1.18 0.96 0.072011 7921 17.07 16.62 -0.45 0.68 0.98 0.04


SST-CLASS2-HF-MOORINGS

SSTBuoy Year N Obs IBIre Bias RMSE R SI

Alborán

2002 6369 20.04 17.30 -2.73 3.39 0.71 0.172003 2154 17.47 16.33 -1.14 1.40 0.96 0.082004 641 17.09 15.70 -1.38 1.43 0.48 0.082005 5696 17.17 16.11 -1.06 1.54 0.88 0.092006 1342 15.21 15.07 -0.14 0.35 0.39 0.022009 8735 21.00 21.12 0.12 0.49 0.98 0.02

Cádiz

2002 4618 19.99 19.32 -0.67 1.46 0.86 0.072003 6083 19.56 18.66 -0.90 1.32 0.97 0.072004 5452 20.03 19.30 -0.74 1.23 0.93 0.062005 7095 20.07 19.53 -0.54 0.72 0.98 0.042006 6954 19.65 18.92 -0.73 0.89 0.99 0.052007 7474 19.00 18.55 -0.45 0.77 0.97 0.042008 7675 19.17 18.62 -0.55 0.87 0.96 0.052009 7735 20.02 19.62 -0.40 0.76 0.97 0.042010 4957 20.32 20.10 -0.22 0.56 0.97 0.032011 8568 20.18 19.74 -0.43 0.76 0.97 0.04

Gata

2002 3583 21.99 21.14 -0.85 1.57 0.83 0.072003 4993 20.47 19.91 -0.56 1.23 0.95 0.062004 6709 19.50 18.72 -0.78 1.15 0.98 0.062005 5935 20.03 19.36 -0.67 1.23 0.96 0.062006 4609 17.17 16.31 -0.87 1.17 0.97 0.072007 8639 19.25 19.21 -0.05 0.75 0.98 0.042008 4928 18.61 17.85 -0.76 1.12 0.97 0.062009 8566 21.35 21.21 -0.14 0.45 0.98 0.022010 6090 20.82 20.02 -0.79 1.19 0.96 0.062011 5636 19.51 19.14 -0.37 0.94 0.96 0.05





IBI_REANALYSIS_PHYS_005_002 Water masses (density)

T/S Diagrams

Silleiro, 2011

Tenerife, 2011

vvCadiz, 2011

Valencia, 2011

Bilbao, 2011



UV-CLASS2-HF-MOORINGS Gran Canaria, 2011

IBI-REA OBS

v

Gran Canaria, DJF-2011

IBI-REA OBS

IBI-REA

IBI-REA

OBS

OBS

AUG-2011

SEP-2011Progressive Vectors




Taylor Diagrams

Silleiro, 2011

Tenerife, 2011Cadiz, 2011

Valencia, 2011

Bilbao, 2011



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

Documentation delivered

Document Title (+ version) Version

V4.1_EPST_External_Product_Spec_Table-1.114_IBI V1.114

V4.0_PDD_Product-Dependencies_1.21_IBIv4.1 V4.1

MYO2-WP9-DUs-TD_IBI-PUERTOS-MADRID-ES_V4.1 V4.1

IBI-PUERTOS-MADRID-ES-Tests results-Summary_V4.1 V4.1

File1_V4.1_IBI-REANALISYS-PHYS V4.1

File1_V4.1_IBI-REANALISYS-BIO V4.1

MYO2-ScVR-REA-IBI-v1.0 V1.0


Product Specification Customer Name Associated PUM VersionDate Associated QUID Version

Date

IBI_REANALYSIS_PHYS_005_002 MYO2-IBI-PUM-005-002 V0.1 04/14 MYO2-IBI-QUID-REA-005-002 V1.0 04/14

IBI_REANALYSIS_BIO_005_003 MYO2-IBI-PUM-005-003 V0.1 04/14 MYO2-IBI-QUID-REA-005-003 V1.0 04/14

Main Architecture Elements reminder


Glo MFC:Provision of Initial and bdy data

ECMWFAtm forcing

NEMO

Preprocess.

Ou

tpu

ts

Validation

Products

OBS

SST TACSL TACINSITU TAC

NEMO

Preprocess.

Ou

tpu

ts

Validation

Products

OBS

IBI-CLS-TOULOUSE-FR DU

IBI P

dE P

U: C

ES

GA

, Fin

iste

rrae

IBI M

O P

U:M

eteo

Fra

nce

IBI-PUERTOS-MADRID-SP DU

BACK-UPCapability: exchangeOf files in case of incident

External inputs

Internal inputs

ftp ftp, Motuftp

MIS-GW(Subsetting, WMS, DGF)

ftplo

g f

iles

MIS-GW(Subsetting, WMS, DGF)

log

file

s

List of implemented interfaces<PU> = SST-IFREMER-BREST-FR

Ports Interface types Interface unique name Will be provided? When ?Delivery / Download FTP EI_D_FTP_ EI_D_FTP_<PU>

FTPS EI_D_FTPS_ EI_D_FTPS_<PU> OPENDAP EI_D_OPENDAP_ EI_D_OPENDAP_<PU>

SUBSETTER EI_D_SUBSETTER_ EI_D_SUBSETTER_<PU>

DirectGetFIle EI_D_DGF_ EI_D_DGF_<PU>

Viewing Interactive maps (Gridded

products)EI_Vi_MAP_GRIDDED_ EI_Vi_MAP_GRIDDED_<PU>

Interactive maps (InSitu and

along-the-track products) EI_Vi_MAP_ALL_ EI_Vi_MAP_ALL_<PU>

Monitoring & Control (Basic) Push Monitoring II_C_BASIC_PUSH_MONITORING_ II_C_BASIC_PUSH_MONITORING_<PU>

(Advanced) Push Monitoring II_C_ADV_PUSH_MONITORING_ II_C_ADV_PUSH_MONITORING_<PU>

Support Services ITIL support processes

(hooks)II_S_ITIL_SUPPORT_ II_S_ITIL_SUPPORT_<PU>

Products Management support processes (hooks)

II_S_ PRODUCTS_MNGT_ II_S_ PRODUCTS_MNGT_<PU>

Components deployment Will be deployed ? When ?THREDDS V4.1

OPENDAP (as THREDDS service) WMS 1.0 (as THREDDS service)

MIS Gateway

highlight scheduled changes


List of implemented Interfaces :<PU> = IBI-PUERTOS-MADRID-SP

Ports Interface types Interface unique nameWill be provided? When ?

Delivery / Download

FTP EI_D_FTP_IBI-PUERTOS-MADRID-SP NO Cancelled, linked to V0

FTPS EI_D_FTPS_IBI-PUERTOS-MADRID-SP Yes Active from V2

OPENDAP EI_D_OPENDAP_IBI-PUERTOS-MADRID-SP yes Active from V1

SUBSETTER EI_D_SUBSETTER_IBI-PUERTOS-MADRID-SP yes Active from V2

Viewing Interactive maps (Gridded prd.) EI_Vi_MAP_GRIDDED_IBI-PUERTOS-MADRID-SP yes Active from V2

Interactive maps EI_Vi_MAP_ALL_IBI-PUERTOS-MADRID-SP yes Active from V2

Monitoring & Control

(Basic) Push Monitoring II_C_BASIC_PUSH_MONITORING_IBI-PUERTOS-MADRID-SP -

(Advanced) Push Monitoring II_C_ADV_PUSH_MONITORING_IBI-PUERTOS-MADRID-SP yes Active from V2

Support Services

ITIL support processes (hooks) II_S_ITIL_SUPPORT_IBI-PUERTOS-MADRID-SP Yes Active from V1


II_S_ PRODUCTS_MNGT_IBI-PUERTOS-MADRID-SPYes Active from V1

Components deploymentWill be deployed ? When ?

THREDDS V4.1 yes Active from V1

OPENDAP (as THREDDS service) yes Active from V1

WMS 1.0 (as THREDDS service) yes Active from V2

MIS Gateway yes Active from V2

MyOcean2 Design Workshop – Barcelona 6,7,8th June 2012

List of implemented Interfaces :<DU> =IBI-CLS-TOULOUSE-FR

Ports Interface types Interface unique nameWill be provided? When ?

Delivery / Download

FTP EI_D_FTP_IBI-CLS-TOULOUSE-FR YES 2011

FTPS EI_D_FTPS_IBI-CLS-TOULOUSE-FR NO

OPENDAP EI_D_OPENDAP_IBI-CLS-TOULOUSE-FR YES 2011

SUBSETTER EI_D_SUBSETTER_IBI-CLS-TOULOUSE-FR YES 2011

Viewing Interactive maps (Gridded pr.) EI_Vi_MAP_GRIDDED_IBI-CLS-TOULOUSE-FR YES 2011

Interactive maps EI_Vi_MAP_ALL_IBI-CLS-TOULOUSE-FR NO

Monitoring & Control

(Basic) Push Monitoring II_C_BASIC_PUSH_MONITORING_IBI-CLS-TOULOUSE-FR -

(Advanced) Push Monitoring II_C_ADV_PUSH_MONITORING_IBI-CLS-TOULOUSE-FR YES 2011

Support Services

ITIL support processes (hooks) II_S_ITIL_SUPPORT_IBI-CLS-TOULOUSE-FR YES 2011


II_S_ PRODUCTS_MNGT_IBI-CLS-TOULOUSE-FRYES 2011

Components deploymentWill be deployed ? When ?

THREDDS V4.1 YES 2011

OPENDAP (as THREDDS service) YES 2011

WMS 1.0 (as THREDDS service) YES 2011

MIS Gateway YES 2011


Products evolution foreseen for V5

Product Customer Name Status

IBI-ANALYSIS-FORECAST-PHYS-005-001-b Updated

IBI_REANALYSIS_PHYS_005_002 Keep Static

IBI_REANALYSIS_BIO_005_003 Keep Static


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.

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)



Master Schedule (review of the 1st MyO-2 Master Plan)

Model improvement DeliveryImprovement of operational suite: decrease CPU time, increase robustness

V3 and V4

River input improvement V3

Solving the BU issue V3 New stress parameterization taking waves into account

V4

Possible new Heat flux formulation V4

Nudging for spin-up V4

Change of model version from 2.3 to 3.4 V4

Vertical turbulence with input form waves

V4

Data assimilation ECOMF…

Still on the plan …

Tested, but decided not to be applied at MyO2 stage

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)


Master Schedule Plan for MyO-FO and beyond (Copernicus….)

Model improvement DeliveryPossible new Heat flux formulation V5 (if demonstrated at the end MyO2)

Nudging for spin-up V5 (if demonstrated at the end MyO2)

Production and/or Dissemination of waves products

Copernicus (if decided at Top Level)

New stress parameterization taking waves into account

Copernicus

Vertical turbulence with input form waves

Copernicus

Data assimilation Copernicus

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.


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, …)

WP 09 Monitoring & Forecasting Thematic & Assemby Center for IBI MyOcean2 V4.1 Acceptance & V5 Design Workshops – June 2014 MyOcean2 V4.1 Acceptance &

Documents

1myocean2 v4

new v4

ibimyocean2 v4

2014myocean2 v4

new ibi

op dissemination v4

bbau ibi

acceptance v5 design