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 while running real.exe using ERA5 data

P

preritaagarwal

Member
Hi,

I am using ERA5 data for initial and boundary conditions for my single domain. I linked the met_em files with my current directory and getting the following error in the rsl.error.0000 file

DYNAMICS OPTION: Eulerian Mass Coordinate
alloc_space_field: domain 1, 789451508 bytes allocated
d01 2016-01-01_00:00:00 Yes, this special data is acceptable to use: OUTPUT FROM METGRID V4.1
d01 2016-01-01_00:00:00 Input data is acceptable to use: met_em.d01.2016-01-01_00:00:00.nc
metgrid input_wrf.F first_date_input = 2016-01-01_00:00:00
metgrid input_wrf.F first_date_nml = 2016-01-01_00:00:00
d01 2016-01-01_00:00:00 Timing for input 0 s.
d01 2016-01-01_00:00:00 flag_soil_layers read from met_em file is 1
Max map factor in domain 1 = 1.18. Scale the dt in the model accordingly.
Using sfcprs to compute psfc
d01 2016-01-01_00:00:00 No average surface temperature for use with inland lakes
Assume Noah LSM input
d01 2016-01-01_00:00:00 forcing artificial silty clay loam at 95 points, out of 20111
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 2977
grid%tsk unreasonable


Could you please help?
 
Hi,
First take a look at these 2 forum posts regarding the same error and see if they are helpful to you at all:

https://forum.mmm.ucar.edu/phpBB3/viewtopic.php?f=39&t=8711&p=15296&hilit=grid%25tsk+unreasonable#p15296

https://forum.mmm.ucar.edu/phpBB3/viewtopic.php?f=39&t=5564&p=10755&hilit=grid%25tsk+unreasonable#p10755
 
Hi,

Many thanks for your reply.

I see that in my met_em files TSK variable is missing.

Grepping 'land; variable prompts the following-
float LANDUSEF(Time, z-dimension0021, south_north, west_east) ;
LANDUSEF:FieldType = 104 ;
LANDUSEF:MemoryOrder = "XYZ" ;
LANDUSEF:units = "category" ;
LANDUSEF:description = "Noah-modified 21-category IGBP-MODIS landuse" ;
LANDUSEF:stagger = "M" ;
LANDUSEF:sr_x = 1 ;
LANDUSEF:sr_y = 1 ;
float LANDMASK(Time, south_north, west_east) ;
LANDMASK:FieldType = 104 ;
LANDMASK:MemoryOrder = "XY " ;
LANDMASK:units = "none" ;
LANDMASK:description = "Landmask : 1=land, 0=water" ;
LANDMASK:stagger = "M" ;
LANDMASK:sr_x = 1 ;
LANDMASK:sr_y = 1 ;
:NUM_LAND_CAT = 21 ;
Do I need to download the data again with skin temp included?
I see 'invariant data' on CDS. Do I need to download that?

Thanks,
Prerita
 
Hi!
I downloaded the data again from CDS including skin temp and soil levels in my Single level ERA5 data.
It solved my error.

Thanks, Prerita
 
I
preritaagarwal said:
Hi!
I downloaded the data again from CDS including skin temp and soil levels in my Single level ERA5 data.
It solved my error.

Thanks, Prerita
Click to expand...
'm using ERA5 data with the following variables from Single Levels: 10m u-component of wind, 10m v-component of wind, 2m dewpoint temperature, 2m temperature, Land-sea mask, Mean sea level pressure, Sea surface temperature, Sea-ice cover, Skin temperature, Snow depth, Soil temperature level 1, Soil temperature level 2, Soil temperature level 3, Soil temperature level 4, Surface pressure, Volumetric soil water layer 1, Volumetric soil water layer 2, Volumetric soil water layer 3, Volumetric soil water layer 4

and from Single Levels:
Divergence, Geopotential, Relative humidity, Specific humidity, Temperature, U-component of wind, V-component of wind

I too am getting the following error are encountered:
YNAMICS OPTION: Eulerian Mass Coordinate
alloc_space_field: domain 1 , 3315992912 bytes allocated
d01 2013-05-27_00:00:00 Yes, this special data is acceptable to use: OUTPUT FROM METGRID V4.3
d01 2013-05-27_00:00:00 Input data is acceptable to use: met_em.d01.2013-05-27_00:00:00.nc
metgrid input_wrf.F first_date_input = 2013-05-27_00:00:00
metgrid input_wrf.F first_date_nml = 2013-05-27_00:00:00
d01 2013-05-27_00:00:00 Timing for input 0 s.
d01 2013-05-27_00:00:00 flag_soil_layers read from met_em file is 1
Max map factor in domain 1 = 1.04. Scale the dt in the model accordingly.
Using sfcprs to compute psfc
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line Source
real.exe 0000000002B9F41A for__signal_handl Unknown Unknown
libpthread-2.17.s 00007F6FC5DBA5D0 Unknown Unknown Unknown
real.exe 0000000000450779 Unknown Unknown Unknown
real.exe 0000000000490B50 Unknown Unknown Unknown
real.exe 000000000049B68D Unknown Unknown Unknown
real.exe 000000000041A590 Unknown Unknown Unknown
real.exe 0000000000418D12 Unknown Unknown Unknown
libc-2.17.so 00007F6FC5A003D5 __libc_start_main Unknown Unknown
real.exe 0000000000418C29 Unknown Unknown Unknown



Can you please help how to solve this issue.
 
srikar_iist said:
I

'm using ERA5 data with the following variables from Single Levels: 10m u-component of wind, 10m v-component of wind, 2m dewpoint temperature, 2m temperature, Land-sea mask, Mean sea level pressure, Sea surface temperature, Sea-ice cover, Skin temperature, Snow depth, Soil temperature level 1, Soil temperature level 2, Soil temperature level 3, Soil temperature level 4, Surface pressure, Volumetric soil water layer 1, Volumetric soil water layer 2, Volumetric soil water layer 3, Volumetric soil water layer 4

and from Single Levels:
Divergence, Geopotential, Relative humidity, Specific humidity, Temperature, U-component of wind, V-component of wind

I too am getting the following error are encountered:
YNAMICS OPTION: Eulerian Mass Coordinate
alloc_space_field: domain 1 , 3315992912 bytes allocated
d01 2013-05-27_00:00:00 Yes, this special data is acceptable to use: OUTPUT FROM METGRID V4.3
d01 2013-05-27_00:00:00 Input data is acceptable to use: met_em.d01.2013-05-27_00:00:00.nc
metgrid input_wrf.F first_date_input = 2013-05-27_00:00:00
metgrid input_wrf.F first_date_nml = 2013-05-27_00:00:00
d01 2013-05-27_00:00:00 Timing for input 0 s.
d01 2013-05-27_00:00:00 flag_soil_layers read from met_em file is 1
Max map factor in domain 1 = 1.04. Scale the dt in the model accordingly.
Using sfcprs to compute psfc
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line Source
real.exe 0000000002B9F41A for__signal_handl Unknown Unknown
libpthread-2.17.s 00007F6FC5DBA5D0 Unknown Unknown Unknown
real.exe 0000000000450779 Unknown Unknown Unknown
real.exe 0000000000490B50 Unknown Unknown Unknown
real.exe 000000000049B68D Unknown Unknown Unknown
real.exe 000000000041A590 Unknown Unknown Unknown
real.exe 0000000000418D12 Unknown Unknown Unknown
libc-2.17.so 00007F6FC5A003D5 __libc_start_main Unknown Unknown
real.exe 0000000000418C29 Unknown Unknown Unknown



Can you please help how to solve this issue.
Click to expand...
This problem is caused by the server running out of memory. You can try parallel computing.
 
You must log in or register to reply here.
Top