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

How to solve this problem? when i run real.exe

P

pline

Member
When I set namelist.input
num_metgrid_levels = 32,
It pops up an error like this.
-----------------------------------------------------------------------
0taskid: 0 hostname: x1001c0s3b0n0
module_io_quilt_old.F 2931, T
Ntasks in X 4 , ntasks in Y 4
*************************************
Configuring physics suite 'tropical'

mp_physics: 6* 6*
cu_physics: 1* 1*
ra_lw_physics: 1* 1*
ra_sw_physics: 1* 1*
bl_pbl_physics: 1* 1*
sf_sfclay_physics: 1* 1*
sf_surface_physics: 2* 2*

(* = option overrides suite setting)
*************************************
Domain # 1: dx = 27000.000 m
Domain # 2: dx = 9000.000 m
REAL_EM V4.4.2 PREPROCESSOR
No git found or not a git repository, git commit version not available.
*************************************
Parent domain
ids,ide,jds,jde 1, 68, 1, 78
ims,ime,jms,jme -4, 24, -4, 27
ips,ipe,jps,jpe 1, 17, 1, 20
*************************************
DYNAMICS OPTION: Eulerian Mass Coordinate
alloc_space_field: domain 1 , 35973392 bytes allocated
Yes, this special data is acceptable to use: OUTPUT FROM METGRID V4.4
Input data is acceptable to use: met_em.d01.2016-05-01_00:00:00.nc
metgrid input_wrf.F first_date_input = 2016-05-01_00:00:00
metgrid input_wrf.F first_date_nml = 2016-05-01_00:00:00
input_wrf.F: SIZE MISMATCH: namelist num_metgrid_levels = 32
input_wrf.F: SIZE MISMATCH: input file BOTTOM-TOP_GRID_DIMENSION = 27
---- ERROR: Mismatch between namelist and input file dimensions
NOTE: 1 namelist vs input data inconsistencies found.
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 1297
NOTE: Please check and reset these options
-------------------------------------------
MPICH ERROR [Rank 0] [job id 758206.0] [Mon Jan 1 10:51:20 2024] [x1001c0s3b0n0] - Abort(1) (rank 0 in comm 0): application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0

aborting job:
application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0
--------------------------------------------------------------------------------------------------------
But when I set namelist.input
num_metgrid_levels = 27,
It pops up an error like this.
---------------------------------------------------------------------------------------------
forcing artificial silty clay loam at 1 points, out of 340
Timing for processing 0 s.
Timing for output 0 s.
Timing for loop # 41 = 0 s.
Yes, this special data is acceptable to use: OUTPUT FROM METGRID V4.4
Input data is acceptable to use: met_em.d01.2016-05-11_06:00:00.nc
metgrid input_wrf.F first_date_input = 2016-05-11_06:00:00
metgrid input_wrf.F first_date_nml = 2016-05-01_00:00:00
Timing for input 0 s.
flag_soil_layers read from met_em file is 1
Turning off use of MAX WIND level data in vertical interpolation
Turning off use of TROPOPAUSE level data in vertical interpolation
Bathymetry dataset from GEBCO Compilation Group. Please acknowledge the following in presentations and publications: GEBCO Compilation Group (2021) GEBCO 2021 Grid (doi:10.5285/c6612cbe-50b3-0cff-e053-6c86abc09f8f).
Using sfcprs2 to compute psfc
No average surface temperature for use with inland lakes
Assume Noah LSM input
forcing artificial silty clay loam at 1 points, out of 340
Timing for processing 0 s.
Timing for output 0 s.
Timing for loop # 42 = 0 s.
Yes, this special data is acceptable to use: OUTPUT FROM METGRID V4.4
Input data is acceptable to use: met_em.d01.2016-05-11_12:00:00.nc
metgrid input_wrf.F first_date_input = 2016-05-11_12:00:00
metgrid input_wrf.F first_date_nml = 2016-05-01_00:00:00
input_wrf.F: SIZE MISMATCH: namelist num_metgrid_levels = 27
input_wrf.F: SIZE MISMATCH: input file BOTTOM-TOP_GRID_DIMENSION = 32
---- ERROR: Mismatch between namelist and input file dimensions
NOTE: 1 namelist vs input data inconsistencies found.
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 1297
NOTE: Please check and reset these options
-------------------------------------------
MPICH ERROR [Rank 0] [job id 758211.0] [Mon Jan 1 11:33:17 2024] [x1001c0s3b0n1] - Abort(1) (rank 0 in comm 0): application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0

aborting job:
application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0
 

Attachments

  • namelist.input.txt
    3.8 KB · Views: 2
  • namelist.wps.txt
    836 bytes · Views: 2
Note that the vertical level must be the same for all the met_em files. in yoir case, apparently that some data have 32 levels while other data have 27 levels. Please double check your data and make sure they all have the same number of vertical levels.

Just in case you don't know, WPS provides the utility mod_levs.exe to process data with different vertical levels. please take a look at Chapter 3: WRF Standard Initialization

Please follow the instruction to process your data and pot them on the same vertical levels. Let me know if you still have troubles regarding this issue.
 
I still don't really understand how mod_levs.exe works.
What I understand is
1) Let me define namelist.wps
&share
wrf_core = 'ARW',
max_dom = 2,
start_date = '2019-05-01_00:00:00','2019-05-01_00:00:00'
end_date = '2019-09-01_00:00:00','2019-09-01_00:00:00'
interval_seconds = 21600,
debug_level = 0,
io_form_geogrid = 2,
/

&geogrid
parent_id = 1, 1,
parent_grid_ratio = 1, 3,
i_parent_start = 1, 17,
j_parent_start = 1, 48,
e_we = 68, 73,
e_sn = 78, 67,
geog_data_res = 'default','default',
dx = 27000,
dy = 27000,
map_proj = 'mercator',
ref_lat = 13.692,
ref_lon = 100.750,
truelat1 = 16.729,
truelat2 = 16.729,
stand_lon = 101.886,
geog_data_path = '/project/common/WPS_Static/geog'
/

&ungrib
out_format = 'WPS',
prefix = 'FILE',
pmin = 5000,
/

&metgrid
fg_name = 'FILE',
io_form_metgrid = 2,
/

&mod_levs
press_pa = 201300 , 200100 , 100000 ,
95000 , 90000 ,
85000 , 80000 ,
75000 , 70000 ,
65000 , 60000 ,
55000 , 50000 ,
45000 , 40000 ,
35000 , 30000 ,
25000 , 20000 ,
15000 , 10000 ,
5000 , 1000
/

2) Run geogrie -> ungrid -> metgrid
3) define namelist.input
&domains
num_metgrid_levels = 24,
4) Run real.exe -> wrf.exe
Did I understand correctly?
 
Last edited:
This utility should be employed to process intermediate files (output files of ungrib.exe).

"press_pa" is used to specify a list of levels you want to keep

You can run this program by ./mod_levs.exe old-intermediate file new-intermediate file

After running this program, your intermediate files should have the same vertical levels (specified by press_pa)

Then you can move on to run metgrid.exe, real.exe and wrf.exe.
 
Hi I am trying to run the mod_levs.exe
So I gave the command
./mod_levs.exe GRIB.AAA GRIB.AAA and I have the namelist.wps in the same directory
But it is showing me an error : Didnt recognize format version of data in /home/../WPS/GRIBFILE.AAA /nFound version 2 but expected either 3, 4 , or 5. This could be an endian problem.
I was actually having trouble running the real.exe using ds 083.2 for data before 2015, and the p sfc error is popping up even if I correct all vertical level errors. Just cant find the right combination or maby the data must prepared as per the press_pa, hence I am here.

Thank you
 
Alfred-Jose said:
Hi I am trying to run the mod_levs.exe
So I gave the command
./mod_levs.exe GRIB.AAA GRIB.AAA and I have the namelist.wps in the same directory
But it is showing me an error : Didnt recognize format version of data in /home/../WPS/GRIBFILE.AAA /nFound version 2 but expected either 3, 4 , or 5. This could be an endian problem.
I was actually having trouble running the real.exe using ds 083.2 for data before 2015, and the p sfc error is popping up even if I correct all vertical level errors. Just cant find the right combination or maby the data must prepared as per the press_pa, hence I am here.

Thank you
Click to expand...

Since this is a different issue can you open a new thread? The admins like to keep the issues seperate
 
@ Alfred-Jose

Please note that the utility ./mod_levs.exe only works for intermediate file. Therefore you can use the command as follows:

./mod_levs.exe old-intermediate file new-intermediate file
 
./mod_levs.exe old-intermediate file new-intermediate file
Can you give an example of how it works?
Suppose, if I want to define
&mod_levs
press_pa = 201300 , 200100 , 100000 ,
95000 , 90000 ,
85000 , 80000 ,
75000 , 70000 ,
65000 , 60000 ,
55000 , 50000 ,
45000 , 40000 ,
35000 , 30000 ,
25000 , 20000 ,
15000 , 10000 ,
5000 , 1000
/
What do I have to do?
 
You must log in or register to reply here.
Top