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

Persistent "grid%tsk unreasonable" Error in real.exe

S

spark1

New member
During the execution of real.exe, I have consistently encountered the following error message:

error in the grid%tsk i,j= 24 12
grid%landmask= 0.00000000
grid%tsk, grid%sst, grid%tmn= 0.00000000 0.00000000 0.00000000
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 3110
grid%tsk unreasonable

I confirmed the presence of reasonable values for LANDSEA, SST, and SKINTEMP variables in the met_em* files.

I sourced the ERA5_INVARIANT from here and followed the specified procedures to integrate it into my WRF setup.

Despite my efforts, I have been unable to pinpoint the root cause of the persistent "grid%tsk unreasonable" error.
I kindly request your expertise and guidance to diagnose and resolve this issue.
Any insights, suggestions, or alternative approaches you can provide would be immensely helpful.
 
This seems like a landmask issue, i.e., at the GRID point (24,12), LANDMASK indicates it is a water point, but SST is zero at this point, which apparently is not reasonable.

Did you ungrib ERA5 data? Where did you download the data?
 
Ming Chen said:
This seems like a landmask issue, i.e., at the GRID point (24,12), LANDMASK indicates it is a water point, but SST is zero at this point, which apparently is not reasonable.

Did you ungrib ERA5 data? Where did you download the data?
Click to expand...
At first I downloaded from cds copernicus. Since I had the same issue I tried again with the one from rda ucar. But, when I check ncview of the met file, it has reasonable temperature for both land and lake.
 
@Ming Chen,
yes, I got the same error from RDA and CDS. One of the previous post in this forum solved the issue by modifying SST in METGRID.TBL. I wonder if that could work. What do you think about THIS LINK?

Also, instead of using ERA5_INVARIANT from How to Process ERA5 Data, are there other ways of including landmask? e,g, I did ungrib, for PL and SFC separately with the ERA5_INVARIANT file in the directory and add constants_name = 'ERA5_INVARIANT' in the &metgrid section in the namelist.wps. If I use e5.oper.invariant.128_172_lsm.ll025sc.1979010100_1979010100.grb from RDA with pressure level data and surface data, how should I ungrib this file then?
 
I also faced the same issue. while running real.exe
Using sfcprs to compute psfc
d01 2017-11-27_00:00:00 No average surface temperature for use with inland lakes
Assume Noah LSM input
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 3062
grid%tsk unreasonable

The error was related to the geogrid.exe. The geographic data was not full. But the geogrid.log didn't show any error.
## Error
1. geo_em files show unreliable values for LANDMASK, SKINTEMP , SOILTEMP, HGT_M and ALBEDO12M variables.
2. It will reflect to met_em files also.
3. So real.exe cant read these inputs from met_em files, if you are using sf_surface_physics =2, 3, 4, or 5 (LSM)
## solution
1. Make sure the path to GEOG files is correct eg: /home/user/WPS_GEOG/ (Sometimes path starting with ~/WPS_GEOG/ won't work )
2. Re-run geogrid.exe, ungrib.exe and metgrid.exe

My error has been solved and here I attach the solution for the public.!
 
spark1 said:
@Ming Chen,
yes, I got the same error from RDA and CDS. One of the previous post in this forum solved the issue by modifying SST in METGRID.TBL. I wonder if that could work. What do you think about THIS LINK?

Also, instead of using ERA5_INVARIANT from How to Process ERA5 Data, are there other ways of including landmask? e,g, I did ungrib, for PL and SFC separately with the ERA5_INVARIANT file in the directory and add constants_name = 'ERA5_INVARIANT' in the &metgrid section in the namelist.wps. If I use e5.oper.invariant.128_172_lsm.ll025sc.1979010100_1979010100.grb from RDA with pressure level data and surface data, how should I ungrib this file then?
Click to expand...
Hi spark1, I am having the same problem. Were you able to solve this, and if so, how? Thanks
 
akash.pathaikara said:
I also faced the same issue. while running real.exe
Using sfcprs to compute psfc
d01 2017-11-27_00:00:00 No average surface temperature for use with inland lakes
Assume Noah LSM input
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 3062
grid%tsk unreasonable

The error was related to the geogrid.exe. The geographic data was not full. But the geogrid.log didn't show any error.
## Error
1. geo_em files show unreliable values for LANDMASK, SKINTEMP , SOILTEMP, HGT_M and ALBEDO12M variables.
2. It will reflect to met_em files also.
3. So real.exe cant read these inputs from met_em files, if you are using sf_surface_physics =2, 3, 4, or 5 (LSM)
## solution
1. Make sure the path to GEOG files is correct eg: /home/user/WPS_GEOG/ (Sometimes path starting with ~/WPS_GEOG/ won't work )
2. Re-run geogrid.exe, ungrib.exe and metgrid.exe

My error has been solved and here I attach the solution for the public.!
Click to expand...
This solution did in fact fix it for me too.
 
Hi,
@Ming Chen ,@blueade7

I followed the Coupled WRF | WRF-Hydro Test Case User Guide (WRF v4.6.1, WRF-Hydro v5.4.0). I have occured similar issues with you.
I have configured and complied the WPS and WRF-Hydro. When I am running the command "mpirun -np 2 ./real >& real.log", I got the similar problem as you in the "real.log":

starting wrf task 0 of 2
starting wrf task 1 of 2
--------------------------------------------------------------------------
MPI_ABORT was invoked on rank 1 in communicator MPI_COMM_WORLD
with errorcode 1.

NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
You may or may not see output from other processes, depending on
exactly when Open MPI kills them.
--------------------------------------------------------------------------

in the rsl.error.0001:

Assume Noah LSM input
d01 2013-09-09_18:00:00 forcing artificial silty clay loam at 13 points, out of 820
-------------- FATAL CALLED ---------------
grid%tsk unreasonable
-------------------------------------------

I have checked the WPS generated files. The SKINTEMP variable was not found in the geo_em files, but was found in the met_em files. Other variables like LANDMASK, SOILTEMP, HGT_M and ALBEDO12M were both available. I am using sf_surface_physics = 4, 4.

I have re-run geogrid.exe, ungrib.exe and metgrid.exe but the issue still exists.

Could you tell how to examine whether the geographic data was full or not? If not, then how to get the relieable variables and fix it?
Or if there are any other reasons for the issue?

Any help would be appreciated!
 

Attachments

  • namelist.input
    4.6 KB · Views: 0
  • real.log
    497 bytes · Views: 0
  • rsl.error.0000
    2 KB · Views: 0
  • rsl.out.0000
    130.5 KB · Views: 0
  • geogrid.log
    72.5 KB · Views: 0
  • namelist.wps
    896 bytes · Views: 0
You must log in or register to reply here.
Top