Page 1 of 1

Automatci Moving Nest in WRF3.0 (ARW)

PostPosted: Mon Jun 30, 2008 11:55 pm
by rgashrit
Hai
I am working with WRF3.0 ARW. I have configured and compiled for vortex tracking (automatic moving) nested runs.
I am trying with a 15Km static nest and a 5Km moving nest. It is doing fine. However in my 78 hr forecast runs, the model comes to a grinding halt (without any core dump etc) with following msg in the rsl.error.0000 and rsl.out.0000

i,j,is,ie,js,je,imloc,jmloc,maxi,maxj 62 58 47 61 42 57 -1 -1 -1 -1
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: mediation_nest_move.b LINE: 508
time_for_move2: Method failure searching max/min of height.
-------------------------------------------
[0] [MPI Abort by user] Aborting Program!

What does that mean? and how to fix it??

raghu

Re: Automatci Moving Nest in WRF3.0 (ARW)

PostPosted: Mon Jul 07, 2008 4:51 pm
by wrfhelp
Would it be possible that the 500 mb low has moved out the domain by 78 hours? Or the low has
become so weak that it is no longer trackable?

wrfhelp

Re: Automatci Moving Nest in WRF3.0 (ARW)

PostPosted: Tue Jul 08, 2008 4:07 am
by rgashrit
wrfhelp wrote:Would it be possible that the 500 mb low has moved out the domain by 78 hours? Or the low has
become so weak that it is no longer trackable?

wrfhelp


NO. In the 78 hr run the model stops just after about 24 or 25 hours of integration. More over the storm is still active
during the chosen period (NARGIS of May 2008). I have checked in case of some other cyclones, in case if the
storm becomes weak, the inner (moving) nest stops, while the outer domain completes the run until the time mentioned in the namelist.

My doubt is the number of moves for the nest. I have no way of finding the actual number of moves made by the nest and if that has exceeded the specified number in the code.

raghu

Re: Automatci Moving Nest in WRF3.0 (ARW)

PostPosted: Thu Apr 12, 2012 6:52 am
by Shepherd_NZ
Hi,

did you manage to solve this problem? I am experiencing a similar issue:

d04 2007-11-12_12:45:15+05/09 calling inc/HALO_EM_SCALAR_E_5_inline.inc
Timing for main: time 2007-11-12_12:45:20 on domain 4: 2.11590 elapsed seconds.
i,j,is,ie,js,je,imploc,jmploc 75 77 20 74
22 76 -1 -1
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 575
time_for_move2: Method failure searching for minimum psfc.


When I examine the data from the 1.33km nest 2 hours before this time, the vortex is near the edge of the domain. I wondered if the nest had lost the vortex so I ran the model again using "corral_dist" but this did not help. I am running the model in restart mode, breaking the simulation down into 12 hour blocks. I am able to run 3x 12 hour blocks before it crashes.

I am not sure what the problem might be, given the vortex is becoming more intense and I am using the following namelist (in particular see vortex tracking switches).


&time_control
run_days = 0,
run_hours = 12,
run_minutes = 0,
run_seconds = 0,
start_year = 2007, 2007, 2007, 2007,
start_month = 11, 11, 11, 11,
start_day = 12, 12, 12, 12,
start_hour = 12, 12, 12, 12,
start_minute = 00, 00, 00, 00,
start_second = 00, 00, 00, 00,
end_year = 2007, 2007, 2007, 2007,
end_month = 11, 11, 11, 11,
end_day = 13, 13, 13, 13,
end_hour = 00, 00, 00, 00,
end_minute = 00, 00, 00, 00,
end_second = 00, 00, 00, 00,
interval_seconds = 43200
input_from_file = .true.,.false.,.false.,.false,
history_interval = 60, 60, 60, 60,
frames_per_outfile = 1, 1, 1, 1,
restart = .true.,
restart_interval = 720,
io_form_history = 2
io_form_restart = 2
io_form_input = 2
io_form_boundary = 2
debug_level = 10

auxinput1_inname = "met_em.d<domain>.<date>"
/
auxinput1_inname = "wrf_real_input_em.d<domain>.<date>"

&domains
time_step = 120,
time_step_fract_num = 0,
time_step_fract_den = 1,
max_dom = 4,
s_we = 1, 1, 1, 1,
e_we = 150, 100, 100, 100,
s_sn = 1, 1, 1, 1,
e_sn = 150, 100, 100, 100,
s_vert = 1, 1, 1, 1,
e_vert = 33, 33, 33, 33,
num_metgrid_levels = 27
eta_levels = 1.000, 0.999,
0.998, 0.997,
0.995, 0.993,
0.991, 0.989,
0.987, 0.985,
0.982, 0.979,
0.976, 0.973,
0.970, 0.950,
0.900, 0.850,
0.800, 0.750,
0.700, 0.650,
0.600, 0.550,
0.500, 0.450,
0.400, 0.350,
0.300, 0.250,
0.200, 0.100,
0.000,

dx = 36000, 12000, 4000, 1333.333,
dy = 36000, 12000, 4000, 1333.333,
grid_id = 1, 2, 3, 4,
parent_id = 1, 1, 2, 3,
i_parent_start = 1, 75, 45, 40
j_parent_start = 1, 60, 35, 30,
parent_grid_ratio = 1, 3, 3, 3,
parent_time_step_ratio = 1, 3, 3, 3,
feedback = 0,
smooth_option = 0,
vortex_interval = 15, 15, 15, 15,
max_vortex_speed = 40, 40, 40, 40,
corral_dist = 8, 12, 12,
track_level = 70000,
time_to_move = 360
/

&physics
mp_physics = 3, 3, 3, 3,
ra_lw_physics = 1, 1, 1, 1,
ra_sw_physics = 5, 5, 5, 5,
radt = 15, 15, 15, 15,
sf_sfclay_physics = 1, 1, 1, 1,
sf_surface_physics = 1, 1, 1, 1,
bl_pbl_physics = 5, 5, 5, 5,
bldt = 0, 0, 0, 0,
cu_physics = 1, 1, 0, 0,
cudt = 30, 30, 30, 30,
isftcflx = 1,
isfflx = 1,
ifsnow = 1,
icloud = 1,
surface_input_source = 1,
num_soil_layers = 5,
sf_urban_physics = 0,
mp_zero_out = 0,
maxiens = 1,
maxens = 3,
maxens2 = 3,
maxens3 = 16,
ensdim = 144,
/

&fdda
/

&dynamics
w_damping = 0,
diff_opt = 1,
km_opt = 4,
diff_6th_opt = 0,
diff_6th_factor = 0.12,
damp_opt = 0,
base_temp = 290.
zdamp = 5000., 5000., 5000., 5000.,
dampcoef = 0.01, 0.01, 0.01, 0.01,
khdif = 0, 0, 0, 0,
kvdif = 0, 0, 0, 0,
non_hydrostatic = .true., .true., .true., .true.,
moist_adv_opt = 0, 0, 0, 0,
scalar_adv_opt = 0, 0, 0, 0,
tke_adv_opt = 0, 0, 0, 0,
chem_adv_opt = 0, 0, 0, 0,
/
fdlssfskfskfsdfks;
&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,
/

Re: Automatci Moving Nest in WRF3.0 (ARW)

PostPosted: Wed Jan 30, 2019 2:06 pm
by JamesH
Hi,

I'm having the same issue; I get the error "time_for_move2: Method failure searching for minimum psfc" after 1 vortex_interval unit. Using print statements, I've found that the psfc values called in by the subroutine "time_for_move2" in mediation_nest_move.F are overwritten as either 0 or NaN.

Has anyone found a solution?

Cheers
JamesH

Re: Automatci Moving Nest in WRF3.0 (ARW)

PostPosted: Wed Jan 30, 2019 3:33 pm
by JamesH
Also, this problem only occurs when I add the following lines to module_initialize_em_quarter_ss.F, which I copied over from module_initialization_real.F:

! Process the soil; note that there are some things hard-wired into
! share/module_soil_pre.F
CALL process_soil_ideal(grid%xland,grid%xice,grid%vegfra,grid%snow,grid%canwat, &
grid%ivgtyp,grid%isltyp,grid%tslb,grid%smois, &
grid%tsk,grid%tmn,grid%zs,grid%dzs,model_config_rec%num_soil_layers,&
model_config_rec%sf_surface_physics(grid%id), &
ids,ide, jds,jde, kds,kde,&
ims,ime, jms,jme, kms,kme,&
its,ite, jts,jte, kts,kte )