WRFV3.6.1 - Adaptive Time Step no longer effective?
-
meteoadriatic
- Posts: 1574
- Joined: Wed Aug 19, 2009 10:05 am
Re: WRFV3.6.1 - Adaptive Time Step no longer effective?
Just to add, here also everything works OK on 3.6.1.
Re: WRFV3.6.1 - Adaptive Time Step no longer effective?
I did a lot of runs with different physics schemes, but the problem si still beresmartie wrote:Just got round to upgrading to 3.6.1.
Can't see any problems with the adaptive time step.
Pretty standard compile with iFort 13.x , netCDF 4 etc. Got a Fortran 2003 warning.
Did you find a solution?
So I have to stay on v3.6 
Please can you share your complete working namelist.input? I would like to compare with mine, just so to be sure I don't have some strange value ...
FORTRAN 2003 Warning also in my configure output, but the compiling was OK.
Many thanks
Re: WRFV3.6.1 - Adaptive Time Step no longer effective?
Just did a 5km run on the western Med storm y'day. Physics is a bit simpler than I usually use. I was getting time steps of 60 secs + for long periods. Even with more complex physics I get expected results.
Code: Select all
&time_control
start_year = 2014
start_month = 11
start_day = 06
start_hour = 12
start_minute = 00
start_second = 00
end_year = 2014
end_month = 11
end_day = 08
end_hour = 00
end_minute = 00
end_second = 00
interval_seconds = 10800
input_from_file = T
history_interval = 60
history_outname = "wrfout_d<domain>_<date>"
frames_per_outfile = 1
io_form_history = 2
io_form_input = 2
io_form_restart = 2
io_form_boundary = 2
io_form_auxinput2 = 2
restart = F
restart_interval = 4320
auxhist1_outname = "auxhist1_d<domain>_<date>"
auxhist1_interval = 15
frames_per_auxhist1 = 999
io_form_auxhist1 = 2
auxhist2_outname = "auxhist2_d<domain>_<date>"
auxhist2_interval = 0
output_diagnostics = 0
auxhist3_outname = "wrfxtrm_d<domain>_<date>"
auxhist3_interval = 0
frames_per_auxhist2 = 1
io_form_auxhist2 = 2
auxinput4_inname = "wrflowinp_d<domain>"
auxinput4_interval = 360
io_form_auxinput4 = 2
nwp_diagnostics = 1
fine_input_stream = 0
adjust_output_times = T
reset_simulation_start = F
cycling = F
iofields_filename = "my_iofields_list.txt", "my_iofields_list.txt"
ignore_iofields_warning = T
diag_print = 0
debug_level = 0
/
&domains
time_step = 30
time_step_fract_num = 0
time_step_fract_den = 10
time_step_dfi = 60
max_dom = 1
s_we = 1
e_we = 360
s_sn = 1
e_sn = 360
s_vert = 1
e_vert = 35
dx = 5000.0000
dy = 5000.0000
grid_id = 1
parent_id = 1
i_parent_start = 1
j_parent_start = 1
parent_grid_ratio = 1
parent_time_step_ratio = 1
grid_allowed = T
max_dz = 1000.
numtiles = 12
nproc_x = 1
nproc_y = 4
num_metgrid_soil_levels = 4
num_metgrid_levels = 27
interp_type = 2
extrap_type = 2
t_extrap_type = 2
use_levels_below_ground = T
use_surface = T
lagrange_order = 1
zap_close_levels = 500
lowest_lev_from_sfc = F
force_sfc_in_vinterp = 1
sfcp_to_sfcp = T
smooth_cg_topo = F
use_tavg_for_tsk = F
aggregate_lu = F
rh2qv_wrt_liquid = T
rh2qv_method = 1
p_top_requested = 5000
vert_refine_fact = 1
use_adaptive_time_step = T
adaptation_domain = 1
step_to_output_time = T
target_cfl = 1.2
target_hcfl = 0.84
max_step_increase_pct = 5
starting_time_step = -1
max_time_step = -1
min_time_step = -1
/
&dfi_control
dfi_opt = 0
/
&physics
mp_physics = 5
cu_physics = 0
cudt = 0
shcu_physics = 0
sf_sfclay_physics = 2
sf_surface_physics = 2
num_soil_layers = 4
sf_urban_physics = 0
num_land_cat = 20
num_soil_cat = 16
bl_pbl_physics = 2
bldt = 0
ra_lw_physics = 1
ra_sw_physics = 1
radt = 5
mp_zero_out = 0
mp_zero_out_thresh = 1.e-8
no_mp_heating = 0
surface_input_source = 1
icloud = 1
swrad_scat = 1
slope_rad = 0
topo_shading = 0
cu_rad_feedback = F
gsmdt = 0
omlcall = 0
seaice_threshold = 271
fractional_seaice = 0
mfshconv = 0
iz0tlnd = 0
ra_call_offset = -1
rdmaxalb = T
rdlai2d = F
bucket_mm = -1
bucket_j = -1
tmn_update = 0
sst_skin = 1
mp_tend_lim = 10.
prec_acc_dt = 0
topo_wind = 0
imomentum = 0
sst_update = 0
do_radar_ref = 1
chem_opt = 0
/
&noah_mp
/
&dynamics
non_hydrostatic = T
gwd_opt = 0
rk_ord = 3
h_mom_adv_order = 5
h_sca_adv_order = 5
v_mom_adv_order = 3
v_sca_adv_order = 3
moist_adv_opt = 1
moist_adv_dfi_opt = 0
scalar_adv_opt = 1
momentum_adv_opt = 1
chem_adv_opt = 1
tke_adv_opt = 1
diff_opt = 1
km_opt = 4
km_opt_dfi = 1
w_damping = 1
diff_6th_opt = 2
diff_6th_factor = 0.12
damp_opt = 0
zdamp = 5000.
dampcoef = 0.2
khdif = 0
kvdif = 0
time_step_sound = 0
do_avgflx_em = 0
do_avgflx_cugd = 0
smdiv = 0.1
emdiv = 0.01
epssm = 0.1
top_lid = F
mix_isotropic = 0
mix_upper_bound = 0.1
rotated_pole = F
tke_upper_bound = 1000.
sfs_opt = 0
m_opt = 0
iso_temp = 0.
tracer_opt = 0
tracer_adv_opt = 0
/
&fdda
grid_fdda = 0
/
&tc
insert_bogus_storm = F
remove_storm = F
num_storm = 1
latc_loc = -999.
lonc_loc = -999.
vmax_meters_per_second = -999.
rmax = -999.
vmax_ratio = -999.
/
&fire
/
&bdy_control
spec_bdy_width = 5
spec_zone = 1
relax_zone = 4
spec_exp = 0
specified = T
nested = F
/
&grib2
/
&namelist_quilt
nio_tasks_per_group = 0
nio_groups = 1
/
&afwa
afwa_diag_opt = 0, 0
afwa_ptype_opt = 0, 0
afwa_vil_opt = 0, 0
afwa_radar_opt = 0, 0
afwa_severe_opt = 0, 0
afwa_icing_opt = 0, 0
afwa_vis_opt = 0, 0
afwa_cloud_opt = 0, 0
afwa_therm_opt = 0, 0
afwa_turb_opt = 0, 0
afwa_buoy_opt = 0, 0
afwa_hailcast_opt = 0, 0
afwa_ptype_ccn_tmp = 288.15
afwa_ptype_tot_melt = 25
/
-
meteoadriatic
- Posts: 1574
- Joined: Wed Aug 19, 2009 10:05 am
Re: WRFV3.6.1 - Adaptive Time Step no longer effective?
Edit: forget this post, I was wrong. Sorry.
***************************************************
Thanks smartie and meteoadriatic for namelist
It seems that the longer time steps in WRFV3.6.1 are related to mp_physics = 6.
Using mp_physics = 4 or 5, time steps for the coarser domain are adapted exactly like in WRFV3.6 and earlier versions.
In my previous test I must have missed something ...
To do: as suggested by smartie, differing the source code of 3.6 and 3.6.1 for WSM6 physics scheme ...
***************************************************
Edit: forget this post, I was wrong. Sorry.
***************************************************
Thanks smartie and meteoadriatic for namelist
It seems that the longer time steps in WRFV3.6.1 are related to mp_physics = 6.
Using mp_physics = 4 or 5, time steps for the coarser domain are adapted exactly like in WRFV3.6 and earlier versions.
In my previous test I must have missed something ...
To do: as suggested by smartie, differing the source code of 3.6 and 3.6.1 for WSM6 physics scheme ...
***************************************************
Edit: forget this post, I was wrong. Sorry.
Last edited by oib on Tue Nov 11, 2014 4:57 pm, edited 5 times in total.
-
meteoadriatic
- Posts: 1574
- Joined: Wed Aug 19, 2009 10:05 am
Re: WRFV3.6.1 - Adaptive Time Step no longer effective?
Hi,
I do use mp_physics=6 but only on finer domain. I'll try when I get time turn it on al both domains to see the possible difference.
I do use mp_physics=6 but only on finer domain. I'll try when I get time turn it on al both domains to see the possible difference.
Re: WRFV3.6.1 - Adaptive Time Step no longer effective?
I can't find any issue with WSM6 on single or nested domains. Everything works as expected.
Corrupted file somewhere?
Corrupted file somewhere?
Re: WRFV3.6.1 - Adaptive Time Step no longer effective?
Sorry guys, smartie is right, adaptive time step works perfectly with mp_physics = 6 
It must be some other option that I have changed in many many tests I've done...
Will let you know if I find out what this option.
It must be some other option that I have changed in many many tests I've done...
Will let you know if I find out what this option.
-
meteoadriatic
- Posts: 1574
- Joined: Wed Aug 19, 2009 10:05 am
Re: WRFV3.6.1 - Adaptive Time Step no longer effective?
But finally you don't have that issue anymore? At least that is good, regardless you find a cause or not
Re: WRFV3.6.1 - Adaptive Time Step no longer effective?
Yes, finally I can use V3.6.1 taking advantage of adaptive time stepmeteoadriatic wrote:But finally you don't have that issue anymore? At least that is good, regardless you find a cause or not