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

Problem when running 1km nested domain

antonianna

New member
Hello everyone!

I have 3 domains (1 parent=15km, 1 nested=3km and 1 nested=1km) but I have a problem when running 1km domain (domain 3). When i put the max_dom=2 then the wrf.exe is running correctly. I do not know whats wrong with the 3rd domain. I have attached my namelist.input file and an image to show the location of the nested domains. This is an one-way nesting. Do you have any idea to solve this problem?
projection.jpg
&time_control
run_days = 5,
run_hours = 0,
run_minutes = 0,
run_seconds = 0,
start_year = 2017, 2017, 2017,
start_month = 11, 11, 11,
start_day = 10, 10, 10,
start_hour = 00, 00, 00,
start_minute = 00, 00, 00,
start_second = 00, 00, 00,
end_year = 2017, 2017, 2017,
end_month = 11, 11, 11,
end_day = 15, 15, 15,
end_hour = 00, 00, 00,
end_minute = 00, 00, 00,
end_second = 00, 00, 00,
interval_seconds = 10800
input_from_file = .true., .true., .true.,
history_interval = 5, 5, 5,
frames_per_outfile = 1000, 1000, 1000,
restart = .false.,
restart_interval = 1440,
io_form_history = 2
io_form_restart = 2
io_form_input = 2
io_form_boundary = 2
debug_level = 10
auxhist3_outname = "wrfxtrm_<domain>_<date>",
auxhist3_interval = 1440,
frames_per_auxhist3 = 7,
io_form_auxinput4 = 2
auxinput4_inname = "wrflowinp_d<domain>"
auxinput4_interval = 360,360,360
/

&domains
time_step = 90,
time_step_fract_num = 0,
time_step_fract_den = 1,
max_dom = 2,
e_we = 242, 381, 481,
e_sn = 181, 311, 376,
e_vert = 50, 50, 50,
p_top_requested = 5000,
num_metgrid_levels = 31,
num_metgrid_soil_levels = 4,
dx = 15000, 3000, 1000,
dy = 15000, 3000, 1000,
grid_id = 1, 2, 3,
parent_id = 1, 1, 2,
i_parent_start = 1, 130, 44,
j_parent_start = 1, 40, 164,
parent_grid_ratio = 1, 5, 3,
parent_time_step_ratio = 1, 5, 3,
feedback = 0,
smooth_option = 0
/

&physics
mp_physics = 8, 8, 8,
ra_lw_physics = 4, 4, 4,
ra_sw_physics = 4, 4, 4,
radt = 15, 15, 15,
sf_sfclay_physics = 2, 2, 2,
sf_surface_physics = 2, 2, 2,
bl_pbl_physics = 2, 2, 2,
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,
sf_urban_physics = 0, 0, 0,
maxiens = 1,
maxens = 3,
maxens2 = 3,
maxens3 = 16,
ensdim = 144,
sst_skin = 1,
sst_update = 1,
tmn_update = 1,
/

&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,
/
 

Attachments

  • namelist.input
    4.3 KB · Views: 2
Hi,
Without seeing the error logs, I would guess that the issue is due to the placement of d03 inside of d02. It needs to be further away from the boundaries. Take a look at this page, which discusses best practices for setting up your domain.
 
Top