...
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.
...
Gliffy Diagram macroId d902c4d7-3202-4686-80e5-912c806c7570 displayName moving from cf to fc name moving from cf to fc pagePin 2
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
- Filenames 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.
- "MARS" keywords in GRIB files. If your data-processing tools are using "stream" and "type" keywords encoded in GRIB files, these will need to be adjusted to reflect new values of stream and type.
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
...