No, there will be changes to the  file-naming convention, see Dissemination file-naming changes from IFS Cycle 49r1 to 50r1

You can identify the test data by the version number:

  • IFS Cycle 50r1 test products are available as version 80 (file names include “*80” as expver).
  • Operational files keep the file naming convention remains the same as for your operational data.

You will only see the changes you made or requested if you have confirmed that your feeds are "Ready to Migrate". On the day of implementation, the esuite (TPREd) will then become the operational (PREd). This means all the data requirement changes that were done to test your 50r1 data requirements, will start to be delivered operationally. If you have not marked your feeds as 'Ready to migrate', we will update your operational requirements automatically. 

  • If you're a Basic/Bronze user, the Data Support team can push a test batch of IFS Cycle 50r1 data to the host configuration.
  • If you're a Silver/Gold user, then you can either push the data to yourself or set the data to be delivered in 'NORMAL' mode. If you put the data in 'NORMAL' mode, the data will be disseminated to your host automatically. However, the data are disseminated between operational windows to protect network capacity, meaning the data will not be disseminated according to the usual dissemination schedule. There is no fixed delivery schedule, and products may not be available in real time, delays of up to one day are possible.
Note: 'NORMAL' mode will not be available until w/c 2nd March 2026.

If you put your data normal mode, the data will be disseminated between operational windows to protect network capacity. There is no fixed delivery schedule, and products may not be available in real time, delays of up to one or days are possible. Usually as we get close to implementation the delay gets smaller.

The same TOTP token should be used for the xdiss as for the diss system.

No, the test data are strictly for non-operational use. Test products are intended for internal testing and validation only and must not be used in operational services or shared on social media.

In the test PREd (TPred), you will be able to test as much data as you want (even over your current Volume Band), however when it comes to operational day, if you have made changes that are over your current Volume Band, you will need to do an amendment to your current contract.

No, this will not work. You should use the TPREd (https://products.ecmwf.int/esuite/requirements/) to install test data.

You can only do this if you have the Silver or Gold service package. 

Login to the test ECPDS (XDISS: https://xdiss-monitor.ecmwf.int/) and follow the instructions for pushing data to yourself here: https://confluence.ecmwf.int/pages/viewpage.action?pageId=228871373

Not necessarily. The host configuration of the test system might not be in sync with the operational system. You also might want to receive the data files at a different endpoint. In case, you would like to make changes, please indicate this in the form: RCP 50r1 - Test System User Details or contact us via https://support.ecmwf.int

As a Silver, Gold, or MC/CS user, you can put your feeds in pre-scheduled mode. However, until implementation day, this will function the same as normal mode and you will not receive data pre-schedule. If you would like to start receiving data in pre-scheduled mode after implementation day, we recommend keeping your feeds in this setting. Once you toggle the “Ready to Migrate” button, the pre-scheduled mode will become active then.

IFS Cycle 50r1 beta test data is available from MARS with E-suite experiment version (expver) 0080 (MARS keywords EXPVER=0080, CLASS=OD). If you have access to MARS or if you have an agreement that gives you access to the archive, you can access these data. Archived test data produced before the start of the Release Candidate Phase (before  18Z run), should be used with caution as it may contain errors that were subsequently fixed. The data should not be used for operational forecasting. 

Since the IFS ENS-cf data will be incorporated into the D* files (Set-i), this means the data will be disseminated earlier than the ENS-pf data. For further details, please refer to the Dissemination schedule.

For IFS Cycle 50r1, Ensemble Control forecast (ENS-cf) will become oper-fc and will not have perturbationNumber=0. The plan is to change this in IFS Cycle 50r2, with the GRIB2 migration. 

Yes, we will provide re-forecast products to allow creation of a model climate for both medium-range and extended-range. This will be provided in the next few weeks and more information will follow when they are available. 

Yes, if you would like to switch to the new file naming convention, you can test it in the test PREd (TPREd) environment during the IFS Cycle 50r1 Release Candidate phase.

The current 'legacy' file naming convention will remain available for some time, including after the 50r1 implementation. However, you will need to migrate to the ECMWF file naming convention later this year, as described here:
https://confluence.ecmwf.int/display/DAC/File+naming+convention+and+format+for+real-time+data#Filenamingconventionandformatforrealtimedata-Naming-AIFSviadissemination

If you are already updating your scripts, it would be a good opportunity to switch to the 'ECMWF' file naming convention at the same time.

Yes, AIFS will be upgraded on the same day as IFS Cycle 50r1.

  • AIFS Single, the deterministic model, will be upgraded from v1.1 to v2. Please refer to Implementation of AIFS Single v2 for details of the implementation of AIFS ENS v2.
  • AIFS ENS, the ensemble model, will be upgraded from v1 to v2. Please refer to Implementation of AIFS ENS v2 for details of the implementation of AIFS ENS v2.

AIFS test data will be available later under a different experiment version number. Please subscribe to forecast_changes-request@lists.ecmwf.int to receive notifications about updates, including when the test data will be available.

We can already confirm that AIFS enfo-cf data for AIFS will continue to be disseminated.

Also, there will be no dissemination schedule change for AIFS data.

On implementation day, we start using 50r1 as the operational cycle for IFS. You will only see the changes you made or requested if you have confirmed that your feeds are "Ready to Migrate". On the day of implementation, the esuite (TPREd) will then become the operational (PREd). This means all the data requirement changes that were done to test your 50r1 data requirements, will start to be delivered operationally. If you have not marked your feeds as 'Ready to migrate', we will update your operational requirements automatically. 


Answer one

Answer 1

Answer 2




 AIFS has a separate update cycle from the IFS, but they are synchronised this time. Head over to Implementation of AIFS Single v2 and Implementation of AIFS ENS v2 for more info.

We would encourage this, yes. In the IFS Cycle 49r1, (ex) HRES and Ensemble Control are numerically identical. If the users make this change at IFS Cycle 49r1, then they won't need to make it at IFS Cycle 50r1.

In IFS Cycle 50r1 it will still be a blend of GRIB1 and GRIB2. Full migration to all GRIB2 will happen with IFS Cycle 50r2, planned for implementation in late 2026, with plenty of test data available during the year or so leading up to this. Read more in this article from Spring 2023 Newsletter and In Focus article:  Migration to GRIB2 data format: implications for users.

We are not planning to replace GRIB2 in the near future.

No, we will not be forcing users to migrate to the CCSDS compression with the IFS Cycle 50r1 update. However, we strongly recommend testing and switching to the CCSDS compression.

Have a question that is not answered above? 

Please contact us via the  ECMWF Support Portal.