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

Run wrf.exe error when using surface analysis nudging - solved

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.

pengzimu

New member
Trouble description:
I met with a problem when I ran WRF with surface analysis nudging.
I successfully created met_em* files by WPS. And then I successfully got metoa_em* files and wrfsfdda files by running obsgrid.exe. After that, real.exe is also run successfully. However, when I ran wrf.exe, the problem occurred and it seemed that wrf.exe stopped while initializing nest domain 3.
Here is a part of message in rsl.error files.

d02 2015-08-19_12:00:00 alloc_space_field: domain 3 , 7252128 bytes allocated
d02 2015-08-19_12:00:00 alloc_space_field: domain 3 , 40721948 bytes allocated
d02 2015-08-19_12:00:00 *** Initializing nest domain # 3 from an input file. ***
d02 2015-08-19_12:00:00 med_initialdata_input: calling input_input
d02 2015-08-19_12:00:00 Input data is acceptable to use:
INPUT LandUse = "MODIFIED_IGBP_MODIS_NOAH"
LANDUSE TYPE = "MODIFIED_IGBP_MODIS_NOAH" FOUND 33 CATEGORIES 2 SEASONS WATER CATEGORY = 17 SNOW CATEGORY = 15
INITIALIZE THREE Noah LSM RELATED TABLES
INPUT LandUse = "MODIFIED_IGBP_MODIS_NOAH"
LANDUSE TYPE = "MODIFIED_IGBP_MODIS_NOAH" FOUND 33 CATEGORIES 2 SEASONS WATER CATEGORY = 17 SNOW CATEGORY = 15
INITIALIZE THREE Noah LSM RELATED TABLES
INPUT LandUse = "MODIFIED_IGBP_MODIS_NOAH"
LANDUSE TYPE = "MODIFIED_IGBP_MODIS_NOAH" FOUND 33 CATEGORIES 2 SEASONS WATER CATEGORY = 17 SNOW CATEGORY = 15
INITIALIZE THREE Noah LSM RELATED TABLES
d02 2015-08-19_12:00:00 Yes, this special data is acceptable to use: SFCFDDA FILE: SURFACE ANALYSES FOR NUDGING
d02 2015-08-19_12:00:00 Input data is acceptable to use:
d02 2015-08-19_12:00:00 Input data processed for aux input 9 for domain 2
d02 2015-08-19_12:00:00 Input data is acceptable to use:
d02 2015-08-19_12:00:00 Input data processed for aux input 10 for domain 2
Tile Strategy is not specified. Assuming 1D-Y
WRF TILE 1 IS 71 IE 85 JS 48 JE 62
WRF NUMBER OF TILES = 1
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 1076
In grid FDDA
-------------------------------------------
Abort(1) on node 23 (rank 23 in comm 0): application called MPI_Abort(MPI_COMM_WORLD, 1) - process 23


I found this problem using the command, grep -i 'fatal' rsl.* . The results are shown as below:

rsl.error.0023:-------------- FATAL CALLED ---------------
rsl.error.0023:FATAL CALLED FROM FILE: <stdin> LINE: 1076
rsl.error.0028:-------------- FATAL CALLED ---------------
rsl.error.0028:FATAL CALLED FROM FILE: <stdin> LINE: 1076
rsl.error.0029:-------------- FATAL CALLED ---------------
rsl.error.0029:FATAL CALLED FROM FILE: <stdin> LINE: 1076
rsl.error.0034:-------------- FATAL CALLED ---------------
rsl.error.0034:FATAL CALLED FROM FILE: <stdin> LINE: 1076
rsl.error.0035:-------------- FATAL CALLED ---------------
rsl.error.0035:FATAL CALLED FROM FILE: <stdin> LINE: 1076
rsl.out.0023:-------------- FATAL CALLED ---------------
rsl.out.0023:FATAL CALLED FROM FILE: <stdin> LINE: 1076
rsl.out.0028:-------------- FATAL CALLED ---------------
rsl.out.0028:FATAL CALLED FROM FILE: <stdin> LINE: 1076
rsl.out.0029:-------------- FATAL CALLED ---------------
rsl.out.0029:FATAL CALLED FROM FILE: <stdin> LINE: 1076
rsl.out.0034:-------------- FATAL CALLED ---------------
rsl.out.0034:FATAL CALLED FROM FILE: <stdin> LINE: 1076
rsl.out.0035:-------------- FATAL CALLED ---------------
rsl.out.0035:FATAL CALLED FROM FILE: <stdin> LINE: 1076

The &fdda section in the namelist.input is shown below:

&fdda
grid_fdda = 1, 1, 0,
gfdda_inname = "wrffdda_d<domain>",
gfdda_end_h = 162, 162, 0,
gfdda_interval_m = 360, 360, 0,
fgdt = 0, 0, 0,
if_no_pbl_nudging_uv = 0, 0, 0,
if_no_pbl_nudging_t = 1, 1, 1,
if_no_pbl_nudging_q = 1, 1, 1,
if_zfac_uv = 0, 0, 0,
k_zfac_uv = 10, 10, 10,
if_zfac_t = 0, 0, 0,
k_zfac_t = 10, 10, 10,
if_zfac_q = 0, 0, 0,
k_zfac_q = 10, 10, 10,
guv = 0.0003, 0.0003, 0.0003,
gt = 0.0003, 0.0003, 0.0003,
gq = 0.0003, 0.0003, 0.0003,
if_ramping = 1,
dtramp_min = 60.0,
io_form_gfdda = 2,
grid_sfdda = 1, 1, 0,
sgfdda_inname = "wrfsfdda_d<domain>",
sgfdda_end_h = 162, 162, 0,
sgfdda_interval_m = 180, 180, 0,
io_form_sgfdda = 2,
guv_sfc = 0.0003, 0.0003, 0.0003,
gt_sfc = 0.0003, 0.0003, 0.0003,
gq_sfc = 0.0003, 0.0003, 0.0003,
rinblw = 250.,
/

The attachment contains namelist, rsl.error and rsl.out.

Solution:
The description about rinblw in Registry/Registry.EM_COMMON is :
Code:
rconfig   real    rinblw                  namelist,fdda         max_domains    0       h        "grid_fdda"            ""      ""
The "max_domains" means we should set rinblw for each domain.
So set the rinblw like this:
Code:
rinblw                       = 250., 250., 250.,
The wrf.exe can run successfully.

Version information:
WRF v4.2
WPS v4.2
OBSGRID v3.7
netcdf-c-4.7.3
netcdf-fortran-4.5.2
ioapi-3.2
jasper-2.0.14
libpng-1.6.37
zlib-1.2.11
Intel 19.1

p.s. thanks Dave and the admin for helping me solve the wrf running problem and the trouble posting in the forum.
 

Attachments

  • namelistAndErrorLog.zip
    112 KB · Views: 65
Top