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

real.exe running error

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.


New member
Dear WRF community,
I'm running the WRF version 4.1. The model is driven by ERA5 hourly dataset and the met_em* files have been created successfully. But when I run the real.exe, there was some error I can't find solution on the forum or google. Here I attached the namelist.input file and the rsl.error.0000 was shown as following:
DYNAMICS OPTION: Eulerian Mass Coordinate
alloc_space_field: domain 1 , 19250553924 bytes allocated
d01 2018-05-16_00:00:00 Yes, this special data is acceptable to use: OUTPUT FROM METGRID V4.1
d01 2018-05-16_00:00:00 Input data is acceptable to use:
metgrid input_wrf.F first_date_input = 2018-05-16_00:00:00
metgrid input_wrf.F first_date_nml = 2018-05-16_00:00:00
d01 2018-05-16_00:00:00 Timing for input 1 s.
d01 2018-05-16_00:00:00 flag_soil_layers read from met_em file is 1
Max map factor in domain 1 = 1.33. Scale the dt in the model accordingly.
Using sfcprs3 to compute psfc
d01 2018-05-16_00:00:00 No average surface temperature for use with inland lakes
Assume Noah LSM input
d01 2018-05-16_00:00:00 forcing artificial silty clay loam at 812 points, out of 421368
-------------- FATAL CALLED ---------------
grid%tsk unreasonable
application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0
[unset]: write_line error; fd=-1 buf=:cmd=abort exitcode=1
system msg for write_line failure : Bad file descriptor

I am not sure what caused the error and have no idea how to correct it.
I hope I can get some advise from you. And thank you for your help.


  • namelist.input
    4.3 KB · Views: 74
The error message "grid%tsk unreasonable" indicates that either the tsk value is not reasonable or it is no consistent with landmask.

Can you look at your met-em files, and check whether the variable tsk looks reasonable? Is it consistent with landmarks, i.e, it should have reasonable values at land points?