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

Error in running real.exe

S

Shaivi Shukla

New member
Hello, @kwerner @William.Hatheway @Ming Chen


I’ve been running WRF v4.4.2 with my usual setup for simulations starting from 1991-05-01, which used to work fine earlier. However, now when I try to run real.exe, it fails with the following error:
metgrid input_wrf.F first_date_input = 1991-05-04_00:00:00
metgrid input_wrf.F first_date_nml = 1991-05-01_00:00:00
forrtl: severe (64): input conversion error, unit -5, file Internal Formatted Read
Image PC Routine Line Source
real.exe 00000000031570E9 for__io_return Unknown Unknown
real.exe 0000000003182C26 for_read_int_fmt_ Unknown Unknown
real.exe 00000000031814EB for_read_int_fmt Unknown Unknown
real.exe 000000000165C6EB Unknown Unknown Unknown
real.exe 0000000001750E08 Unknown Unknown Unknown
real.exe 000000000041F6C8 Unknown Unknown Unknown
real.exe 000000000041E422 Unknown Unknown Unknown
libc-2.17.so 00007F5ED1B6C555 __libc_start_main Unknown Unknown
real.exe 000000000041E329 Unknown Unknown Unknown
 
Hello, @Ming Chen


These are the input files. Earlier, with the same inputs the simulation had run successfully. I am using CESM climate model data as the boundary conditions.

However, I am now encountering an error while running real.exe. Interestingly, the crash does not always occur at the same timestamp—when I re-run metgrid.exe, the time at which real.exe fails seems to vary.

I have not made any changes to the input files or the namelist. Could someone help identify what might be causing this issue?


Thank you.
 

Attachments

  • namelist.input
    6 KB · Views: 1
  • namelist.wps
    1.5 KB · Views: 1
  • rsl.error.0000
    4 KB · Views: 1
@Ming Chen Sir,

I have rechecked the issue thoroughly. When I perform a completely new run using the default topography, the simulation executes without any problems. However, the error arises when I incorporate the SRTM DEM into the static dataset. Specifically, I used the SRTM DEM for domains 2 and 3, while retaining the default topography for domain 1.

I would also like to mention that initially, the default topography was working fine. But once I attempted to run the simulation using the SRTM DEM, it started failing—even when I switched back to the default DEM. To resolve this, I used a different system and reran the simulation using only the default DEM, and it worked successfully again.

I prepared the datasets using GIS4WRF.
 

Attachments

  • New folder.zip
    15 KB · Views: 0
Last edited:
@Ming Chen Sir,
Thank you for the suggestion. However, since my study area lies in a region of complex terrain, I would like to improve the simulation results by incorporating a higher-resolution DEM. Additionally, for the purpose of my study, I also need to include a land use/land cover (LULC) dataset.

Could you please advise me how to resolve this issue? Your guidance would be greatly appreciated.

After deeper inspection, I found that real.exe crashes are linked to specific met_em files that contain a blank Times variable (b''). These files also show anomalies in the HGT_M field — such as unexpected grid values or structural inconsistencies.

All met_em files were generated in a single run of metgrid.exe using the same namelist.wps, yet only a few files exhibit this issue. Moreover, when I rerun metgrid.exe, the problem shifts to different timesteps, indicating that the faulty files are not consistent across runs.

I’ve attached terrain images (HGT_M) from two met_em files — one corresponding to a timestep where real.exe crashed, and the other where it ran successfully — to illustrate the difference.

Could someone please help identify what might be causing these inconsistent faulty files and how to avoid this in future runs?1753793998004.png1753794011746.png
 
Last edited:
Due to limited human power, we are no longer able to handle each individual user's dataset for application to WRF. However, we provide the document here, which describes in detail how to implement new dataset in geogrid.

Note that you still need to prepare the data in the format that geogrid.exe can recognize. Chapter 3 of WRF USER GUIDE provides instruction.

Hope this is helpful for you.
 
@Ming Chen Sir,

Thank you for your response and for sharing the documentation.

However, I would like to clarify that the error I’m encountering occurs even when running domain 1, which is configured to use the default static dataset, not any newly added dataset. This suggests that the issue may not be related to the incorporation of a new dataset in geogrid.

I would appreciate it if you could kindly help me understand what might be causing this, considering that the same setup worked previously.
 
Can you use GFS as input for your case and see whether it works?

If the case still fails, Please upload your namelist.wps and namelist.input for me to take a look. It will also be helpful to tell which version of WRF you are using.

Thanks.
 
You must log in or register to reply here.
Top