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 ./real.exe

V

vanessalmeida24

New member
Good morning, I'm trying to run the WRF 4.2 model and the metgrid ran excellently but the ./real is giving the error below, has anyone seen a similar problem? Thank you in advance. Attached my namelist.input. It kills the process with this message below

tail rsl.error.0000

starting wrf task 0 of 1
Morto

Input data is acceptable to use: met_em.d01.2022-01-03_12:00:00.nc
metgrid input_wrf.F first_date_input = 2022-01-03_12:00:00
metgrid input_wrf.F first_date_nml = 2022-01-01_00:00:00
Timing for input 8 s.
flag_soil_layers read from met_em file is 1
Using sfcprs to compute psfc
No average surface temperature for use with inland lakes
Soil temperature closest to 30.00 at level 17
forcing artificial silty clay loam at 113 points, out of 27661
Timing for processing 2 s.
 

Attachments

  • namelist.input
    6.1 KB · Views: 4
Can you look at all your RSL files and find those error messages hidden somewhere? Note that the error message may exist in any rsl files. we need such information to help figure out what is wrong.
 
vanessalmeida24 said:
Good morning, I'm trying to run the WRF 4.2 model and the metgrid ran excellently but the ./real is giving the error below, has anyone seen a similar problem? Thank you in advance. Attached my namelist.input. It kills the process with this message below

tail rsl.error.0000

starting wrf task 0 of 1
Morto

Input data is acceptable to use: met_em.d01.2022-01-03_12:00:00.nc
metgrid input_wrf.F first_date_input = 2022-01-03_12:00:00
metgrid input_wrf.F first_date_nml = 2022-01-01_00:00:00
Timing for input 8 s.
flag_soil_layers read from met_em file is 1
Using sfcprs to compute psfc
No average surface temperature for use with inland lakes
Soil temperature closest to 30.00 at level 17
forcing artificial silty clay loam at 113 points, out of 27661
Timing for processing 2 s.
Click to expand...

Ming Chen said:
Can you look at all your RSL files and find those error messages hidden somewhere? Note that the error message may exist in any rsl files. we need such information to help figure out what is wrong.
Click to expand...

Try looking at the last rsl.error file. Usually it hides in the last one from what I have found. But @Ming Chen is right it can be in any one.
 
You must log in or register to reply here.
Top