In the current operational cycle 49R1 Ensemble Control Forecast (stream:type = enfo:cf) is bit-identical to deterministic forecast (oper:fc (00/12) / scda:fc (06/18)) and Wave Ensemble Control Forecast (waef:cf) is bit-identical to Wave Deterministic Forecast (wave:fc (00/12) / scwv:fc (06/18)).
| Initialisation time [UTC] | stream | type | stream | type |
|---|---|---|---|---|
| 0 / 12 | enfo | cf | oper | fc |
| 6 / 18 | scda | |||
| 0 / 12 | waef | cf | wave | fc |
| 6 / 18 | scwv |
As part of the 50r1 IFS Cycle implementation, the composition of the data production will change. The 'HRES' will be deprecated in concept, but the oper:fc and wave:fc will continue. enfo:cf and waef:cf are going to be stopped. scda and scwv streams will be merged with oper and wave respectively.
Impact on dissemination
Dissemination requirement containing control forecast of enfo and waef streams will need to be modified to equivalent streams presented on the diagram.
It is possible to make changes early, before start of the release candidate suite as indicated with vertical arrows on the diagram. e.g. from enfo:cf:00/12 to oper:fc:00/12. Making early changes would give more time for adjustment of programs using disseminated data. However, we do not recommend changing dissemination requirements containing 06/18 runs. This is because current equivalent deterministic streams scda and scwv are going to be discontinued and integrated to oper and wave in 50R1. Therefore, it will be easier to adjust these during the release candidate phase.
Examples of dissemination requirements
| Time | Requirement in 49R1 | Equivalent requirement in 49R1 | Equivalent in 50R1 | Notes! |
|---|---|---|---|---|
| 00/12 | Filename: "{Feed name}E*" / "{Feed name}X*" (if use=bc) | Filename: "{Feed name}D*" / "{Feed name}S*" (if use=bc) | Filename: "{Feed name}D*" | Since the equivalent deterministic request will not change in 50R1, this requirement can be migrated before start of the 50R1 release candidate suite. If testing migration from ENFO:CF to OPER:FC before the release candidate phase, we recommend doing it in new test feed of PREd. |
| 06/18 | Filename: "{Feed name}E*" / "{Feed name}X*" (if use=bc) | Filename: "{Feed name}D*" / "{Feed name}S*" (if use=bc) | Filename: "{Feed name}D*" | It is recommended to migrate such requirement during the release candidate phase. |
| 00/06/12/18 | Filename: "{Feed name}E*" / "{Feed name}X*" (if use=bc) | Filename: "{Feed name}D*" / "{Feed name}S*" (if use=bc) | Filename: "{Feed name}D*" | It is recommended to migrate such requirement during the release candidate phase. |
| 00/12 | Filename: "{Feed name}W*" / "{Feed name}G*" (if use=bc) | Filename: "{Feed name}P*" | Filename: "{Feed name}P*" | Since the equivalent deterministic request will not change in 50R1, this requirement can be migrated before start of the 50R1 release candidate suite. If testing migration from WAEF:CF to WAVE:FC before the release candidate phase, we recommend doing it in new test feed of PREd |
| 06/18 | Filename: "{Feed name}W*" / "{Feed name}G*" (if use=bc) | Filename: "{Feed name}Q*" | Filename: "{Feed name}P*" | It is recommended to migrate such requirement during the release candidate phase. |
| 00/06/12/18 | Filename: "{Feed name}W*" / "{Feed name}G*" (if use=bc) | Filename: "{Feed name}P*" and "{Feed name}Q*" | Filename: "{Feed name}P*" | It is recommended to migrate such requirement during the release candidate phase. |
What will change after moving from CF to FC
- LEGACY template file-naming will change according to File naming convention and format for real-time data e.g. {feed name}E* filename would change to {feed name}D*.
- Dissemination schedule will change following Dissemination schedule i.e. the files will be delivered earlier, following HRES dissemination schedule.
- GRIB metadata will change as per table below
Keyword Value stream:type oper:fc enfo:cf GRIB edition 1 2 1 2 perturbationNumber 0 N/A 0 0 numberOfForecastsInEnsemble 0 N/A 51 51 typeOfProcessedData N/A 1 N/A 3 marsType
fc fc cf cf marsStream
oper oper enfo enfo typeOfGeneratingProcess
N/A 2 N/A 4 typeOfEnsembleForecast
N/A N/A N/A 255 oceanAtmosphereCoupling
N/A N/A 2 2 localDefinitionNumber
1 N/A 30 N/A
Impact on MARS
MARS will not contain datasets with enfo:cf and waef:cf nor scda and scwv streams with date >= {50R1 implementation date}. The 50R1 implementation date is to be confirmed.
Abbreviations
cf - Control forecast
fc - Forecast
enfo - Ensemble prediction system, Probabilistic forecast
oper - Atmospheric model, Deterministic forecast
scda - Atmospheric model, Boundary conditions
scwv - Wave forecast, Boundary conditions
waef - Wave ensemble forecast, Probabilistic forecast
wave - Wave forecast, Deterministic model