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

Large differences of simulated fields (U, V, W, T) with lightning_option = 3 (LPI) on and off

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.

bmalecic

New member
I used WRF4.1.5 to simulate days with observed convection activity. One of the diagnostics I am interested in analysing is LPI (lightning_option = 3). I've noticed large differences in simulated fields (U, V, W, T, ...) with lightning_option = 3 on and off, even though LPI is a diagnostic variable. Has anyone seen this kind of problem before? If so, any recommendation on how to fix this problem?

Attached is my namelist.input and a few difference plots.


&time_control
run_days = 1,
run_hours = 12,
run_minutes = 0,
run_seconds = 0,
start_year = 2016, 2016, 2016, 2016,
start_month = 06, 06, 06, 06,
start_day = 25, 25, 25, 25,
start_hour = 12, 12, 12, 12,
start_minute = 00, 00, 00, 00,
start_second = 00, 00, 00, 00,
end_year = 2016, 2016, 2016, 2016,
end_month = 06, 06, 06, 06,
end_day = 27, 27, 27, 27,
end_hour = 00, 00, 00, 00,
end_minute = 00, 00, 00, 00,
end_second = 00, 00, 00, 00,
interval_seconds = 21600
input_from_file = .true.,.true.,.true.,.true.,
history_interval = 60, 60, 10, 1,
frames_per_outfile = 1000, 24, 6, 60,
! iofields_filename = "hail.txt","hail.txt","hail.txt","hail.txt",
! auxhist7_outname = "hail_d<domain>_<date>",
! auxhist7_interval = 60, 60, 10, 1, 1,
! frames_per_auxhist7 = 1000, 1000, 6,
! io_form_auxhist7 = 2
restart = .false.,
restart_interval = 360,
write_hist_at_0h_rst = .true.
override_restart_timers = .true.
io_form_history = 2
io_form_restart = 2
io_form_input = 2
io_form_boundary = 2
debug_level = 0
! history_outname ='/scratch/telisman/wrfout_d<domain>_<date>',
/

&domains
time_step = 30,
time_step_fract_num = 0,
time_step_fract_den = 1,
max_ts_locs = 40,
max_dom = 3,
e_we = 79, 133, 280,
e_sn = 79, 118, 190,
e_vert = 97, 97, 97, 97,
use_levels_below_ground = .true.
use_surface = .true.
smooth_cg_topo = .true.
p_top_requested = 5000,
num_metgrid_levels = 26,
num_metgrid_soil_levels = 4,
dx = 9000, 3000, 1000, 500,
dy = 9000, 3000, 1000, 500,
grid_id = 1, 2, 3, 4,
parent_id = 0, 1, 2, 3,
parent_grid_ratio = 1, 3, 3, 3,
i_parent_start = 1, 12, 15,
j_parent_start = 1, 22, 30,
parent_time_step_ratio = 1, 3, 3, 3,
feedback = 0,
smooth_option = 2,
! numtiles = 3,
! nproc_x = 6,
! nproc_y = 8,
eta_levels =
0.00000,0.00333,0.00680,0.01040,0.01400,0.01806,0.02211,
0.02630,0.03068,0.03520,0.03990,0.04470,0.04984,0.05507,
0.06050,0.06612,0.07193,0.07796,0.08400,0.09060,0.09730,
0.10400,0.11133,0.11870,0.12630,0.13400,0.14230,0.15000,
0.15900,0.16800,0.17750,0.18700,0.19680,0.20690,0.21700,
0.22800,0.23900,0.25000,0.26200,0.27400,0.28600,0.29900,
0.31300,0.32600,0.34000,0.35500,0.37000,0.38500,0.40110,
0.41700,0.43350,0.45090,0.46850,0.48660,0.50500,0.52400,
0.54380,0.56395,0.58460,0.60580,0.62760,0.65000,0.67300,
0.69660,0.72080,0.74500,0.77100,0.79510,0.81908,0.84230,
0.86600,0.88800,0.90919,0.92880,0.94200,0.95100,0.95745,
0.96100,0.96400,0.96680,0.96940,0.97192,0.97438,0.97675,
0.97900,0.98120,0.98330,0.98530,0.98720,0.98900,0.99070,
0.99239,0.99402,0.99562,0.99725,0.99874,1.00000,
/


&physics
mp_physics = 10, 10, 10, 10,
lightning_option = 0, 3, 3, 3,
lightning_start_seconds = 3600., 3600., 3600., 3600.,
flashrate_factor = 1, 1, 1, 1,
cldtop_adjustment = 2., 2., 2., 2.,
iccg_method = 2, 2, 2, 2,
do_radar_ref = 1,
ra_lw_physics = 1, 1, 1, 1,
ra_sw_physics = 1, 1, 1, 1,
topo_shading = 1,
radt = 9, 9, 9, 9,
sf_sfclay_physics = 1, 1, 1, 1,
sf_surface_physics = 4, 4, 4, 4,
bl_pbl_physics = 8, 8, 8, 8,
bldt = 0, 0, 0, 0,
cu_physics = 1, 0, 0, 0,
hailcast_opt = 0, 1, 1, 1,
num_land_cat = 21,
cudt = 5, 5, 5, 5,
cugd_avedx = 3,
isfflx = 1,
ifsnow = 0,
icloud = 1,
surface_input_source = 1,
num_soil_layers = 4,
sf_urban_physics = 0,
maxiens = 1,
maxens = 3,
maxens2 = 3,
maxens3 = 16,
ensdim = 144,
/

&fdda
/

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

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

&grib2
/

&namelist_quilt
nio_tasks_per_group = 0,
nio_groups = 1,
/
! mp_zero_out = 2,
! mp_zero_out_thresh = 1.e-8,
! sst_update = 1,
! gwd_opt = 1,
 

Attachments

  • namelist_lpi_off.input
    7.2 KB · Views: 59
  • namelist_lpi_on.input
    7.2 KB · Views: 64
  • diff_W.png
    diff_W.png
    162 KB · Views: 1,461
  • diff_U.png
    diff_U.png
    308.2 KB · Views: 1,461
  • diff_T.png
    diff_T.png
    352.7 KB · Views: 1,461
We are notifying the developer of this scheme to see if they have any insight. They will either respond directly, or we will let you know when we get a response. Thank you for your patience.
 
Hello:

There should be no differences in the simulated cloud or wind fields. The LPI is a passive or diagnostic variable. I was not the one who coded it into the lightning driver, and recently pointed out that there may be a problem with the Registry in regard to calling this driver.

An alternative is to calculate the LPI from the model output. This can be done quite simply using an NCL program I wrote. I would be glad to send it to you.

Barry Lynn
 
Hi,

I also tried to use the lightning physics option in WRF 4.1.5, but when I set lightning_option = 3, 2, 2, 2, the model exited with a fatal error. So with the LPI option the model does not work properly. Is there another possibility to calculate the LPI?

Best regards
Mariusz
 
I just had a series of unexplained crashes on the surface scheme, until I found out that it runs fine again when I remove lightning_option = 3 from the namelist. This seems definitely bugged. My version is 4.1.1.
 
We believe this option introduces bugs, but we heaven't figured out yet what is wrong. Please avoid using this option at present.
 
I've also tried lightning_option = 3 and it seems the bug is still occurring. Any plans for remedy?
 
Top