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

Forcing WRF with boundary conditions from ERA5

Hi,
This is the error message at the bottom of your metgrid.log
Code: 
2023-09-08 14:17:58.470 --- ERROR: Error in ext_pkg_write_field

This error typically means there is no surface data included. Did you make sure to obtain the surface fields, as well as the 3d fields? Check this list for mandatory fields/levels.
 
kwerner said:
Hi,
This is the error message at the bottom of your metgrid.log
Code: 
2023-09-08 14:17:58.470 --- ERROR: Error in ext_pkg_write_field

This error typically means there is no surface data included. Did you make sure to obtain the surface fields, as well as the 3d fields? Check this list for mandatory fields/levels.
Click to expand...
Hi Kwerner, thanks for your response. This is a list of all the surface variables. I checked all the boxes and then downloaded the files. However, I still get the error message. It seems some 3d variables are not available (or I am not doing it correctly). Thanks for your help.
 

Attachments

  • Screen Shot 2023-09-11 at 3.21.55 PM.png
    Screen Shot 2023-09-11 at 3.21.55 PM.png
    345.1 KB · Views: 19
I read a previous post that mentioned ERA5 providing boundary data every hour. However, when I download the data, they don't show up to have an hourly time stamp. For example, one surface data is e5.oper.an.sfc.128_165_10u.ll025sc.2023060100_2023063023.grb spanning a whole month range. Do I have to do anything to convert it to hourly data, or ungrib will handle it? Thanks again for your help.
kwerner said:
Hi,
This is the error message at the bottom of your metgrid.log
Code: 
2023-09-08 14:17:58.470 --- ERROR: Error in ext_pkg_write_field

This error typically means there is no surface data included. Did you make sure to obtain the surface fields, as well as the 3d fields? Check this list for mandatory fields/levels.
Click to expand...
 
I figured that the problem was due to insufficient boundary data. I downloaded the required data, and it ran successfully. Thanks for your insight.
 
You must log in or register to reply here.
Top