Real.exe not generating wrfinput_d01

[wr1989]

Greetings,

I've been troubleshooting the past couple days trying to figure out a solution to the following error I'm receiving:

I'm running WRF v4.6.1

-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 70
program wrf: error opening wrfinput_d01 for reading ierr= -1021
-------------------------------------------

Initially, there was an issue with a mismatch between my HRRR grib files not containing the correct number of soil levels that are listed in the HRRR VTable but after a fresh download of those initialization files, that was resolved. However, I'm still getting the error.

I've confirmed my namelist.wps and namelist.input have the same input fields and are compatible but when I run my shell script that runs both ./real.exe and /.wrf.exe, it fails instantly. Running them separately results in the same issue with no wrfinput_d01 file being generated by ./real.exe.

Additionally, I've confirmed the met_em.* files are all linked and valid.

I've attached my shell script and both namelists in case I've overlooked something.

Appreciate any insight. I'm stumped.

- Billy

 

[kwerner]

Hi,
Will you please attach out/error logs for the real.exe run? If there are multiple rsl* files, package them into a single *.tar or zipped file.

 

[wr1989]

Greetings,

I've attached a list of files that may/may. not help. Included are the following:
- rsl.out.* files
- rsl.error.* files
- log.real.txt
- log.wrf.txt
- slurm-*.out files from my past few attempts.

My run.sh file is what I use to kick off both real.exe and wrf.exe (obtained from my professor) and it worked for my first two simulations with 1 and 2 domains.

I've attempted to run real.exe separately but it fails instantly with the same error as when I use my run.sh file.

Additional information:
- I am initializing my data with WRF simulation with HRRR analysis files
- Since the wrfbdy and wrfinput_d01 files aren't being created, I checked to see if it was a Vtable or METGRID.TBL issue but troubleshooting with ChatGPT was taking me in circles so I never got to the root cause. I've attached those files as well in case they are helpful.

I appreciate the assistance.

 

[kwerner]

Hi,
Thanks for sharing that. The error you're seeing:

-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 70
program wrf: error opening wrfinput_d01 for reading ierr= -1021
-------------------------------------------

is coming from the wrf.exe. It's unable to run because real.exe did not run correctly. I know you mentioned you tried to run them separately, but I really need to see the rsl* files from just the real.exe run. Can you run that again, without using the script that runs both together, and then send the rsl* files from just real.exe? Thanks!

 

[wr1989]

Sorry about that! Here are the real.exe rsl files.

 

[kwerner]

Thanks! The error for real is:

-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE:  <stdin>  LINE:     409
error opening met_em.d01.2022-04-29_12_00_00.nc for input; bad date in namelist or file not in directory
-------------------------------------------

I assume that date is correct. Did you remember to link the met_em* files to the real/wrf running directory? If you don't think that's the issue, will you issue the following in the real/wrf running directory?

ls -ls >& ls.txt

and then attach the ls.txt file? Thanks.

 

[wr1989]

Yeah, the date is correct. My research project is centered on the Andover, KS 04-29-2022 tornado.

I've attached the script you requested. Appreciate the help troubleshooting!

 

[kwerner]

Thanks! Try removing this line in the namelist.input file, and then run real.exe again to see if that makes a difference.

nocolons   = .true.,

If not, please attach the updated namelist.input and rsl files. Thanks.

 

[wr1989]

Okay removing that and changing the 'ignore_iofields_warning' to false (after receiving another error message), it seems to have ran. It created wrfbdy and wrfinput finally.

 

[kwerner]

That's great news! Thank you for the update, and good luck.