I am having strange error while running real.exe, using ERA5 data. I downloaded the ERA5 pressure/surface level data from the RDA website:
I am using the standard Vtable.ECMWF file for both surface and pressure level data. I believe there is no need to run ecmwf_calc_p.exe program for the above dataset so I am not running it.
Ungrib, metgrid all went well. The met_em* files generated look all good. The real program runs fine if I run only for a 2-3 day period. But when I try to run it for the entire 1-month period, it gives me this error:
d01 2020-03-29_01:00:00 Timing for output 1 s.
d01 2020-03-29_01:00:00 Timing for loop # 98 = 1 s.
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 409
error opening met_em.d01.2020-03-29_02:00:00.nc for input; bad date in namelist or file not in directory
The file is there, and the date is fine too so this is a strange problem. What is noticeable is that when I change the initial date to another day, the error also gets shifted to another met_em* file as if the error occurs at a certain time interval.
This issue was noted in a previous post here:
forum.mmm.ucar.edu
Although the above post says that the problem was solved, it was not actually solved. The suggested workaround in another post is not actually a solution. So I would greatly appreciate if someone could look into this issue.
Note: I compiled WPS using GNU compilers.
I am using the standard Vtable.ECMWF file for both surface and pressure level data. I believe there is no need to run ecmwf_calc_p.exe program for the above dataset so I am not running it.
Ungrib, metgrid all went well. The met_em* files generated look all good. The real program runs fine if I run only for a 2-3 day period. But when I try to run it for the entire 1-month period, it gives me this error:
d01 2020-03-29_01:00:00 Timing for output 1 s.
d01 2020-03-29_01:00:00 Timing for loop # 98 = 1 s.
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 409
error opening met_em.d01.2020-03-29_02:00:00.nc for input; bad date in namelist or file not in directory
The file is there, and the date is fine too so this is a strange problem. What is noticeable is that when I change the initial date to another day, the error also gets shifted to another met_em* file as if the error occurs at a certain time interval.
This issue was noted in a previous post here:
real.exe stops with error bad date in namelist or file not in directory
Hello, I'm using wrf version 4.0 to downscale EC-EARTH data to a 5km grid for an entire year. I have three nested domains, d01, d02 and d03, with 45 x 10 x 5 km resolution and the following dimensions: e_we =115, 145, 181, e_sn = 91, 106, 157, I have already all the met_em files linked in the...
forum.mmm.ucar.edu
Although the above post says that the problem was solved, it was not actually solved. The suggested workaround in another post is not actually a solution. So I would greatly appreciate if someone could look into this issue.
Note: I compiled WPS using GNU compilers.