Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

ERA5 Forecast Field Data

This post was from a previous version of the WRF&MPAS-A Support Forum. New replies have been disabled and if you have follow up questions related to this post, then please start a new thread from the forum home page.

xkcd_xkcd

New member
Hi,
I want to do a forecast with ERA5 data. So I download ERA5 reanalysis data (https://cds.climate.copernicus.eu/cdsapp#!/dataset/reanalysis-era5-single-levels?tab=overview) as initial condition and forecast data (https://apps.ecmwf.int/data-catalogues/era5/?class=ea) as boundary forcing condition.
An error occurred when I run ungrib.exe.
./ungrib.exe
*** Starting program ungrib.exe ***
Start_date = 2019-01-01_00:00:00 , End_date = 2019-01-02_00:00:00
output format is WPS
Path to intermediate files is ./
Unknown Data Representation Type, ksec2(4)= 50
rd_grib1
Who can help me with this? Thanks very much in advance!

Kind regards!
Peng
 
Hi,
Just to make sure you're downloading the correct data, take a look at this FAQ that discusses using ERA5 data.

Are you able to use the g1print.exe or g2print.exe utility on the data to read it?
If you're still having problems, can you attach one time stamp of your data files so that I can test it, along with your namelist.wps file?
Please also let me know the version of WPS you are using, and which Vtable. Thanks!
 
Hi,
Thanks very much for your reply!
I have run the WRF Model with ERA5 reanalysis data (from 2019-01-01-0000 to 2019-01-02-0000) successfully following the tutorial from https://dreambooker.site/2019/10/03/Initializing-the-WRF-model-with-ERA5-pressure-level/, I think this is a simulation case.

But what I want is a WRF forecast case. So I downloaded the reanalysis 2019-01-01-0000 data as the initial condition, and I downloaded the forecast field data as the boundary forcing condition, which starts from 2019-01-01-0600 and forecasts to 2019-01-02-0000 every hour. Then the error occurred after executing ungrib.exe. (All the data I downloaded is based on the tutorial)

What confuses me is that I can succeed with ERA5 reanalysis data but not with forecast field data.

I have run a 3.7.1 version WRF, the vtable is Vtable.ERA-interim.pl and the namelist.wps is as follows.

Kind regards!
Peng
 

Attachments

  • namelist.wps
    1.5 KB · Views: 73
Hi,
Can you try to use the Vtable.ECMWF to ungrib this data and see if it makes any difference? Please keep me posted. Thanks!
 
Hi Kelly, I couldn't post in the ERA5 FAQ (https://forum.mmm.ucar.edu/phpBB3/viewtopic.php?f=75&t=9714) so I'm posting in this thread:

For the attached file name in that post, the correct line to add to namelist.wps is:
Code:
constants_name = 'ERA5_INVARIANT.txt'
 
hi,
I have tried with Vtable.ECMWF and the same error occurred.
I think this error may be due to the difference between the reanalysis data and forecast data of ERA5. Because I can run WRF successfully with reanalysis data. But I don't know the reason.
I wonder is there anyone who has run WRF with ERA5 forecast data as boundary forcing condition.

Kind regards.
Peng
 
Peng,
Thanks for letting me know about the update to the FAQ for ERA5 data. I made some modifications.

I asked our data specialist, who hasn't used the ERA5 forecast data, but thinks the format should be the same as the analysis data; however, maybe that's not the case. Can you attach one time stamp of your data files so that I can test it? Thanks!
 
Hi,

Thank you very much for your reply.

Initial data is the ERA5 reanalysis data of 2019-01-01-0600 including pressure level and single level. Boundary forcing data is the ERA5 forecast data of 2019-01-01-0600 to 2019-01-01-1200 including pressure level and single level.

The attachments provide namelist.wps and the variables I have downloaded including both reanalysis data and forecast data. And the URL of the data is in the previous forum reply.

Hope my reply is clear. Looking forward to your reply.
Kind regards.
Peng
 

Attachments

  • singel_level.png
    singel_level.png
    31.9 KB · Views: 2,241
  • pressure_level.png
    pressure_level.png
    36.5 KB · Views: 2,238
  • namelist.wps
    1.5 KB · Views: 77
Hi,
Is it not possible for you to simply attach the input files (you can package multiple files in a single .tar file)? It will take me much more time to follow the website you sent, choosing each individual field, level, time, etc. and our resources are limited for time. I also want to ensure I'm using the EXACT data files as you, to repeat the problem. If I download the files, there's a decent chance I'll do something differently than you. If the file(s) are too large, take a look at the home page of this forum for information on attaching large files. Thanks.
 
Hi,
Thank you so much for sending that, and I would like to apologize for the delay. I was out of the office last week and am trying to get caught up now. Thank you for your patience.

I am seeing the same error as you. The difference I see in your reanalysis data, and in the forecast data is that the forecast data includes several forecast times within a single file. The WPS program sometimes has problems with multiple times in a file. As a test, is it possible to just download a single forecast time and see if that would work, or whether you get the same error?
 
Hi,

Thank you very much for your reply.
I have tried but unfortunately, the same error occurred.
I will post again if I solve this problem in the future.
Thanks again and best wishes.

Peng
 
Peng,
Yes, please keep us posted. As we've not worked with the forecast data previously, it would be nice to know what the trick is to making this work, if you get it working. We could share it with future users with the same problem.
 
Top