Missing time steps in wrfinput files

Discuss the nesting capability within the model itself and any problems you might have run into.

Missing time steps in wrfinput files

Postby jkmeher » Fri Nov 09, 2018 5:55 am

Hello there,
I was running a 3 domain nested run in WRF3.8.1. I found the the real.exe runs perfectly fine. The wrfbdy_d01 file hass all the time steps. But, the wrfinput_d01, wrfinput_d02, and wrfinput_d03, have only first time step. The problem only occurring for three domain run. For one domain and for two domain, I don't get any error.
The ncdump command shows following time step for wrfbdy_d01
Times =
"2011-08-05_00:00:00",
"2011-08-05_06:00:00",
"2011-08-05_12:00:00",
"2011-08-05_18:00:00",
"2011-08-06_00:00:00",
"2011-08-06_06:00:00",
"2011-08-06_12:00:00",
"2011-08-06_18:00:00" ;
But, the ncdum command only shows the first time step (i.e. "2011-08-05_00:00:00") for wrfinput_d01, wrfinput_d02, and wrfinput_d03.

I changed time step from 150 to 90 in namelist.input, still i am facing the same problem.

The rsl.error.0000 has no issue presently as it is as follows,
*************************************
d02 2011-08-05_06:00:00 alloc_space_field: domain 3, 22
8702800 bytes allocated
d02 2011-08-05_06:00:00 alloc_space_field: domain 3, 900
1480684 bytes allocated
metgrid input_wrf.F first_date_input = 2011-08-05_00:00:00
metgrid input_wrf.F first_date_nml = 2011-08-05_00:00:00
d03 2011-08-05_00:00:00 Timing for input 5 s.
d03 2011-08-05_00:00:00 flag_soil_layers read from met_em file is 1
d03 2011-08-05_00:00:00 Turning off use of MAX WIND level data in vertical interr
polation
d03 2011-08-05_00:00:00 Turning off use of TROPOPAUSE level data in vertical intt
erpolation
Using sfcprs3 to compute psfc
d03 2011-08-05_00:00:00 flag value of flag_qnwfa is 1
d03 2011-08-05_00:00:00 No average surface temperature for use with inland lakes
Assume Noah LSM input
d03 2011-08-05_00:00:00 forcing artificial silty clay loam at 19 points, out oo
f 32232
d03 2011-08-05_00:00:00 Timing for processing 1 s.
d03 2011-08-05_00:00:00 Timing for output 3 s.
d03 2011-08-05_00:00:00 Timing for loop # 1 = 10 s.
d01 2011-08-07_00:00:00 real_em: SUCCESS COMPLETE REAL_EM INIT

What is the possible solution for this problem?

Please see my attached namelist files.
namelist.wps
&share
wrf_core = 'ARW',
max_dom = 3,
start_date = '2011-08-05_00:00:00','2011-08-05_00:00:00','2011-08-05_00:00:00',
end_date = '2011-08-07_00:00:00','2011-08-07_00:00:00','2011-08-07_00:00:00',
interval_seconds = 21600,
io_form_geogrid = 2,
/

&geogrid
parent_id = 1, 1, 2,
parent_grid_ratio = 1, 3, 3,
i_parent_start = 1, 15, 41,
j_parent_start = 1, 14, 43,
e_we = 100, 214, 409,
e_sn = 93, 190, 316,
!
!!!!!!!!!!!!!!!!!!!!!!!!!!!! IMPORTANT NOTE !!!!!!!!!!!!!!!!!!!!!!!!!!!!
! The default datasets used to produce the HGT_M, GREENFRAC,
! and LU_INDEX/LANDUSEF fields have changed in WPS v3.8. The HGT_M field
! is now interpolated from 30-arc-second USGS GMTED2010, the GREENFRAC
! field is interpolated from MODIS FPAR, and the LU_INDEX/LANDUSEF fields
! are interpolated from 21-class MODIS.
!
! To match the output given by the default namelist.wps in WPS v3.7.1,
! the following setting for geog_data_res may be used:
!
! geog_data_res = 'gtopo_10m+usgs_10m+nesdis_greenfrac+10m','gtopo_2m+usgs_2m+nesdis_greenfrac+2m',
!
!!!!!!!!!!!!!!!!!!!!!!!!!!!! IMPORTANT NOTE !!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
geog_data_res = 'gtopo_10m+usgs_10m+nesdis_greenfrac+10m','default',
dx = 74200,
dy = 74200,
map_proj = 'mercator',
ref_lat = 31.161,
ref_lon = 79.992,
truelat1 = 31.161,
truelat2 = 0,
stand_lon = 79.992,
geog_data_path = '../Fix_data/geog'
/

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

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

namelist.input
&time_control
run_days = 0,
run_hours = 48,
run_minutes = 0,
run_seconds = 0,
start_year = 2011, 2011, 2011,
start_month = 08, 08, 08,
start_day = 05, 05, 05,
start_hour = 00, 00, 00,
start_minute = 00, 00, 00,
start_second = 00, 00, 00,
end_year = 2011, 2011, 2011,
end_month = 08, 08, 08,
end_day = 07, 07, 07,
end_hour = 00, 00, 00,
end_minute = 00, 00, 00,
end_second = 00, 00, 00,
interval_seconds = 21600,
input_from_file = .true.,.true.,.true.,
history_interval = 180, 180, 180,
frames_per_outfile = 1000, 1000, 1000,
restart = .false.,
restart_interval = 5000,
io_form_history = 2,
io_form_restart = 2,
io_form_input = 2,
io_form_boundary = 2,
debug_level = 0,
/

&domains
time_step = 90,
time_step_fract_num = 0,
time_step_fract_den = 1,
max_dom = 3,
e_we = 100, 214, 409,
e_sn = 93, 190, 316,
e_vert = 30, 30, 30,
p_top_requested = 5000,
num_metgrid_levels = 27,
num_metgrid_soil_levels = 4,
dx = 74200, 24733.333, 8244.444,
dy = 74200, 24733.333, 8244.444,
grid_id = 1, 2, 3,
parent_id = 1, 1, 2,
i_parent_start = 1, 15, 41,
j_parent_start = 1, 14, 43,
parent_grid_ratio = 1, 3, 3,
parent_time_step_ratio = 1, 3, 3,
feedback = 1,
smooth_option = 0,
/

&physics
mp_physics = 3, 3, 3,
use_aero_icbc = .true.,
ra_lw_physics = 1, 1, 1,
ra_sw_physics = 1, 1, 1,
radt = 30, 30, 30,
sf_sfclay_physics = 1, 1, 1,
sf_surface_physics = 2, 2, 2,
bl_pbl_physics = 1, 1, 1,
bldt = 0, 0, 0,
cu_physics = 1, 1, 0,
cudt = 5, 5, 5,
isfflx = 1,
ifsnow = 0,
icloud = 1,
surface_input_source = 1,
num_soil_layers = 4,
num_land_cat = 24,
sf_urban_physics = 0, 0, 0,
/

&fdda
/

&dynamics
w_damping = 0,
diff_opt = 1,
km_opt = 4,
diff_6th_opt = 0, 0, 0,
diff_6th_factor = 0.12, 0.12, 0.12,
base_temp = 290.
damp_opt = 0,
zdamp = 5000., 5000., 5000.,
dampcoef = 0.2, 0.2, 0.2
khdif = 0, 0, 0,
kvdif = 0, 0, 0,
non_hydrostatic = .true., .true., .true.,
moist_adv_opt = 1, 1, 1,
scalar_adv_opt = 1, 1, 1,
/

&bdy_control
spec_bdy_width = 5,
spec_zone = 1,
relax_zone = 4,
specified = .true., .false., .false.,
nested = .false., .true., .true.,
/

&grib2
/

&namelist_quilt
nio_tasks_per_group = 0,
nio_groups = 1,
/
Jitendra
jkmeher
 
Posts: 4
Joined: Mon Sep 10, 2018 7:34 am

Re: Missing time steps in wrfinput files

Postby kwthomas » Fri Nov 09, 2018 4:59 pm

Jitendra...

Check all the rsl.* files for complaints. Sometimes, a complaint may only be in one file.

If there are no errors in any of these files, and there are no complaints in any log, it is possible that your job
required too much memory. If it looks like the job abruptly just stopped, it could be OOM as in "Out Of Memory".
Computers have to kill off big memory jobs when it has no more memory (or swap, if configured) to prevent
a crash. You can use "top" top monitor memory usage while your job is running.

You can also rerun WRF with "debug_level" set to a large number. I used 9999. This will give a *lot* of
debug information the the rsl* files.
Kevin W. Thomas
Center for Analysis and Prediction of Storms
University of Oklahoma
kwthomas
 
Posts: 249
Joined: Thu Aug 07, 2008 6:53 pm


Return to Nesting

Who is online

Users browsing this forum: No registered users and 1 guest