[Wrf-users] Fwd: two way nest run crashes without errors
Xin Xi
xxi at gatech.edu
Mon Jun 9 16:03:53 MDT 2014
I finally got the model to come to the init time of nest domain by
adjusting the number of processors. This seems to be a known issue. for
example,
http://forum.wrfforum.com/viewtopic.php?f=6&t=2202
Still, my program stops and reports an error of missing variable TOPOSTDV
(err msg below). This is strange to me, since there is no such input
variable in the wrf version I am using (3.6). Any ideas?
(meanwhile, I am trying to use 3-nest setup to see how the model runs)
*************************************
Nesting domain
ids,ide,jds,jde 1 166 1 166
ims,ime,jms,jme -4 30 -4 30
ips,ipe,jps,jpe 1 14 1 14
INTERMEDIATE domain
ids,ide,jds,jde 18 34 18 34
ims,ime,jms,jme 13 30 13 30
ips,ipe,jps,jpe 16 20 16 20
*************************************
d01 2013-03-11_00:00:00 alloc_space_field: domain
2,
53777088 bytes allocated
d01 2013-03-11_00:00:00 DEBUG wrf_timetoa(): returning with str =
[2013-03-11
_00:00:00]
d01 2013-03-11_00:00:00 DEBUG wrf_timetoa(): returning with str =
[2013-03-11
_00:00:00]
d01 2013-03-11_00:00:00 DEBUG wrf_timetoa(): returning with str =
[2013-03-14
_00:00:00]
d01 2013-03-11_00:00:00 DEBUG wrf_timeinttoa(): returning with str =
[0000000
000_000:000:010]
DEBUG setup_timekeeping(): clock after creation, clock start time =
2013-03-
11_00:00:00
DEBUG setup_timekeeping(): clock after creation, clock current time =
2013-0
3-11_00:00:00
DEBUG setup_timekeeping(): clock after creation, clock stop time =
2013-03-1
4_00:00:00
DEBUG setup_timekeeping(): clock after creation, clock time step =
000000000
0_000:000:010
d01 2013-03-11_00:00:00 setup_timekeeping: set xtime to 720.0000
d01 2013-03-11_00:00:00 setup_timekeeping: set julian to 69.00000
d01 2013-03-11_00:00:00 setup_timekeeping: returning...
d01 2013-03-11_00:00:00 alloc_space_field: domain
2,
2414448 bytes allocated
d01 2013-03-11_00:00:00 calling inc/HALO_INTERP_DOWN_inline.inc
d01 2013-03-11_00:00:00 *** Initializing nest domain # 2 from an input
file. **
*
d01 2013-03-11_00:00:00 wrf main: calling open_r_dataset for wrfinput
d01 2013-03-11_00:00:00 DEBUG wrf_timetoa(): returning with str =
[2013-03-11
_00:00:00]
d01 2013-03-11_00:00:00 module_io.F: in wrf_open_for_read
d01 2013-03-11_00:00:00 med_initialdata_input: calling input_auxinput2
d01 2013-03-11_00:00:00 input_wrf: begin, fid = 3
d01 2013-03-11_00:00:00 module_io.F: in wrf_inquire_filename
d01 2013-03-11_00:00:00 input_wrf: fid,filestate = 3
103
d01 2013-03-11_00:00:00 input_wrf: dryrun = F switch 28
d01 2013-03-11_00:00:00 module_io.F (md_calls.m4) : in
wrf_get_dom_ti_integer_s
ca
d01 2013-03-11_00:00:00 module_io.F (md_calls.m4) : in
wrf_get_dom_ti_integer_s
ca
d01 2013-03-11_00:00:00 module_io.F (md_calls.m4) : in
wrf_get_dom_ti_real_sca
d01 2013-03-11_00:00:00 input_wrf: wrf_get_dom_ti_real for CEN_LAT
returns
10.02998
d01 2013-03-11_00:00:00 module_io.F (md_calls.m4) : in
wrf_get_dom_ti_real_sca
d01 2013-03-11_00:00:00 input_wrf: wrf_get_dom_ti_real for CEN_LON
returns -
83.76000
d01 2013-03-11_00:00:00 module_io.F (md_calls.m4) : in
wrf_get_dom_ti_real_sca
d01 2013-03-11_00:00:00 input_wrf: wrf_get_dom_ti_real for TRUELAT1
returns
10.03000
d01 2013-03-11_00:00:00 module_io.F (md_calls.m4) : in
wrf_get_dom_ti_real_sca
d01 2013-03-11_00:00:00 input_wrf: wrf_get_dom_ti_real for TRUELAT2
returns
0.0000000E+00
d01 2013-03-11_00:00:00 module_io.F (md_calls.m4) : in
wrf_get_dom_ti_real_sca
d01 2013-03-11_00:00:00 input_wrf: wrf_get_dom_ti_real for MOAD_CEN_LAT
return
s 10.02999
d01 2013-03-11_00:00:00 module_io.F (md_calls.m4) : in
wrf_get_dom_ti_real_sca
d01 2013-03-11_00:00:00 input_wrf: wrf_get_dom_ti_real for STAND_LON
returns
-83.76000
d01 2013-03-11_00:00:00 module_io.F (md_calls.m4) : in
wrf_get_dom_ti_real_sca
d01 2013-03-11_00:00:00 input_wrf: wrf_get_dom_ti_real for POLE_LAT
returns
90.00000
d01 2013-03-11_00:00:00 module_io.F (md_calls.m4) : in
wrf_get_dom_ti_real_sca
d01 2013-03-11_00:00:00 input_wrf: wrf_get_dom_ti_real for POLE_LON
returns
0.0000000E+00
d01 2013-03-11_00:00:00 module_io.F (md_calls.m4) : in
wrf_get_dom_ti_real_sca
d01 2013-03-11_00:00:00 input_wrf: wrf_get_dom_ti_real for GMT returns
0.000
0000E+00
d01 2013-03-11_00:00:00 module_io.F (md_calls.m4) : in
wrf_get_dom_ti_integer_s
ca
d01 2013-03-11_00:00:00 input_wrf: wrf_get_dom_ti_integer for JULYR
returns
2013
d01 2013-03-11_00:00:00 module_io.F (md_calls.m4) : in
wrf_get_dom_ti_integer_s
ca
d01 2013-03-11_00:00:00 input_wrf: wrf_get_dom_ti_integer for JULDAY
returns
70
d01 2013-03-11_00:00:00 module_io.F (md_calls.m4) : in
wrf_get_dom_ti_integer_s
ca
d01 2013-03-11_00:00:00 input_wrf: wrf_get_dom_ti_integer for MAP_PROJ
returns
3
d01 2013-03-11_00:00:00 module_io.F (md_calls.m4) : in
wrf_get_dom_ti_char_arr
d01 2013-03-11_00:00:00 mminlu = 'USGS'
d01 2013-03-11_00:00:00 input_wrf: wrf_get_dom_ti_char for MMINLU returns
USGS
d01 2013-03-11_00:00:00 module_io.F (md_calls.m4) : in
wrf_get_dom_ti_integer_s
ca
d01 2013-03-11_00:00:00 input_wrf: wrf_get_dom_ti_integer for ISWATER
returns
16
d01 2013-03-11_00:00:00 module_io.F (md_calls.m4) : in
wrf_get_dom_ti_integer_s
ca
d01 2013-03-11_00:00:00 input_wrf: wrf_get_dom_ti_integer for ISLAKE
returns
-1
d01 2013-03-11_00:00:00 module_io.F (md_calls.m4) : in
wrf_get_dom_ti_integer_s
ca
d01 2013-03-11_00:00:00 input_wrf: wrf_get_dom_ti_integer for ISICE
returns
24
d01 2013-03-11_00:00:00 module_io.F (md_calls.m4) : in
wrf_get_dom_ti_integer_s
ca
d01 2013-03-11_00:00:00 input_wrf: wrf_get_dom_ti_integer for ISURBAN
returns
1
d01 2013-03-11_00:00:00 module_io.F (md_calls.m4) : in
wrf_get_dom_ti_integer_s
ca
d01 2013-03-11_00:00:00 input_wrf: wrf_get_dom_ti_integer for ISOILWATER
retur
ns 14
d01 2013-03-11_00:00:00 module_io.F: in wrf_get_next_time
d01 2013-03-11_00:00:00 3 input_wrf: wrf_get_next_time
current_date:
2013-03-11_00:00:00 Status = 0
d01 2013-03-11_00:00:00 DEBUG wrf_timetoa(): returning with str =
[2013-03-11
_00:00:00]
d01 2013-03-11_00:00:00 DEBUG wrf_timetoa(): returning with str =
[2013-03-11
_00:00:00]
d01 2013-03-11_00:00:00 DEBUG wrf_timetoa(): returning with str =
[2013-03-11
_00:00:00]
d01 2013-03-11_00:00:00 DEBUG wrf_timetoa(): returning with str =
[2013-03-14
_00:00:00]
d01 2013-03-11_00:00:00 DEBUG wrf_timeinttoa(): returning with str =
[0000000
000_000:000:010]
DEBUG input_wrf(): get CurrTime from clock, clock start time =
2013-03-11_00
:00:00
DEBUG input_wrf(): get CurrTime from clock, clock current time =
2013-03-11_
00:00:00
DEBUG input_wrf(): get CurrTime from clock, clock stop time =
2013-03-14_00:
00:00
DEBUG input_wrf(): get CurrTime from clock, clock time step =
0000000000_000
:000:010
input_wrf.F reading 2d real xlat
date 2013-03-11_00:00:00
ds 1 1 1
de 165 165 1
ps 1 1 1
pe 14 14 1
ms -4 -4 1
me 30 30 1
d01 2013-03-11_00:00:00 module_io.F: in wrf_read_field
input_wrf.F reading 2d real xlat Status = 0
input_wrf.F reading 2d real xlong
date 2013-03-11_00:00:00
ds 1 1 1
de 165 165 1
ps 1 1 1
pe 14 14 1
ms -4 -4 1
me 30 30 1
d01 2013-03-11_00:00:00 module_io.F: in wrf_read_field
input_wrf.F reading 2d real xlong Status = 0
input_wrf.F reading 2d real lu_index
date 2013-03-11_00:00:00
ds 1 1 1
de 165 165 1
ps 1 1 1
pe 14 14 1
ms -4 -4 1
me 30 30 1
d01 2013-03-11_00:00:00 module_io.F: in wrf_read_field
input_wrf.F reading 2d real lu_index Status = 0
input_wrf.F reading 2d real topostdv
date 2013-03-11_00:00:00
ds 1 1 1
de 165 165 1
ps 1 1 1
pe 14 14 1
ms -4 -4 1
me 30 30 1
d01 2013-03-11_00:00:00 module_io.F: in wrf_read_field
d01 2013-03-11_00:00:00 NetCDF error: NetCDF: Variable not found
d01 2013-03-11_00:00:00 NetCDF error in wrf_io.F90, line 2861
Varname T
OPOSTDV
On Mon, Jun 9, 2014 at 2:46 PM, Eric Altshuler <ela at cola.iges.org> wrote:
> For a 1km domain, a time step of 10s is too large. The rule of thumb is
> the time step should be no larger than 6*dx where dx is in km, and
> sometimes the time step has to be smaller than 6*dx or the model will
> become unstable. In general, it's a good idea to set parent_time_step_ratio
> to be the same as parent_grid_ratio, except possibly for some special cases.
>
>
> ------------------------------
> *From: *"Xin Xi" <xxi at gatech.edu>
> *To: *"Eric Altshuler" <ela at cola.iges.org>
> *Cc: *wrf-users at ucar.edu
> *Sent: *Monday, June 9, 2014 4:43:06 PM
> *Subject: *Re: [Wrf-users] Fwd: two way nest run crashes without errors
>
>
> Thanks Eric! I will look into using 3 nests.
> Just to clarify, if I use time step of 60sec for parent domain and
> parent_time_step_ratio of 6, the nest domain will run at 10sec, correct? I
> suspect a small time step (like 10 sec) is needed for such fine resolution
> domain (e.g. 1km). Why did you say that would make the time step too large
> on the nest domain?
>
>
> On Mon, Jun 9, 2014 at 1:10 PM, Eric Altshuler <ela at cola.iges.org> wrote:
>
>> I would think a nest grid ratio of 15 is too large. The recommended value
>> is 3, and 5 can also be used. Also, your time step ratio is 6, which would
>> probably make the time step too large on your nest domain with a grid ratio
>> of 15. You need to use a triple nest if your high resolution domain is 1
>> km. One suggestion might be:
>>
>> dx = 15000, 5000, 1000
>> dy = 15000, 5000, 1000
>> parent_grid_ratio = 1, 3, 5
>> parent_time_step_ratio = 1, 3, 5
>>
>> or:
>>
>> dx = 15000, 3000, 1000
>> dy = 15000, 3000, 1000
>> parent_grid_ratio = 1, 5, 3
>> parent_time_step_ratio = 1, 5, 3
>>
>> I'm not sure which one is preferable.
>>
>> Best regards,
>>
>>
>>
>> Eric L. Altshuler
>> Research Scientist
>> Center for Ocean-Land-Atmosphere Studies
>> 253 Research Hall, Mail Stop 6C5
>> George Mason University
>> 4400 University Drive
>> Fairfax, VA 22030 USA
>>
>> E-mail: ela at cola.iges.org
>> Phone: (703) 993-5725
>> Fax: (703) 993-5770
>>
>>
>> ------------------------------
>> *From: *"Xin Xi" <xxi at gatech.edu>
>> *To: *wrf-users at ucar.edu
>> *Sent: *Monday, June 9, 2014 11:12:26 AM
>> *Subject: *[Wrf-users] Fwd: two way nest run crashes without errors
>>
>> Hi I am running wrf 3.6 with two way nesting. After the spinning up on
>> outer domain, the program stopped without any warning or errors. in other
>> words, the program simply stopped at the beginning of the nest domain start
>> time. I wonder whether this is an issue of parent_grid_ratio (=15), time
>> step or the vertical lvls. Please help. Thanks.
>>
>> Here is excerpt of namelist.input:
>>
>> &time_control
>> run_days = 3,
>> run_hours = 13,
>> run_minutes = 0,
>> run_seconds = 0,
>> start_year = 2013, 2013, 2000,
>> start_month = 03, 03, 01,
>> start_day = 10, 11, 24,
>> start_hour = 12, 00, 12,
>> start_minute = 00, 00, 00,
>> start_second = 00, 00, 00,
>> end_year = 2013, 2013, 2000,
>> end_month = 03, 03, 01,
>> end_day = 14, 14, 25,
>> end_hour = 00, 00, 12,
>> end_minute = 00, 00, 00,
>> end_second = 00, 00, 00,
>> interval_seconds = 21600
>> input_from_file = .true.,.true.,.true.,
>> history_interval = 60, 60, 60,
>> frames_per_outfile = 24, 24, 1000,
>> restart = .false.,
>> restart_interval = 5000,
>> io_form_history = 2
>> io_form_restart = 2
>> io_form_input = 2
>> io_form_boundary = 2
>> debug_level = 5000
>> fine_input_stream = 0, 2, 2,
>> io_form_auxinput2 = 2
>> /
>>
>> &domains
>> time_step = 60,
>> time_step_fract_num = 0,
>> time_step_fract_den = 1,
>> max_dom = 2,
>> e_we = 50, 166, 94,
>> e_sn = 50, 166, 91,
>> e_vert = 57, 57, 30,
>> p_top_requested = 5000,
>> num_metgrid_levels = 27,
>> num_metgrid_soil_levels = 4,
>> dx = 15000, 1000, 3333.33,
>> dy = 15000, 1000, 3333.33,
>> grid_id = 1, 2, 3,
>> parent_id = 0, 1, 2,
>> i_parent_start = 1, 20, 30,
>> j_parent_start = 1, 20, 30,
>> parent_grid_ratio = 1, 15, 3,
>> parent_time_step_ratio = 1, 6, 3,
>> feedback = 1,
>> smooth_option = 0,
>> eta_levels = 1.000, 0.999, 0.998, 0.997, 0.996,
>> 0.995, 0.994, 0.993,
>> 0.991, 0.988, 0.985, 0.982, 0.978,
>> 0.974, 0.970, 0.965,
>> 0.960, 0.955, 0.950, 0.945, 0.935,
>> 0.925, 0.915, 0.905,
>> 0.895, 0.875, 0.855, 0.840, 0.820,
>> 0.800, 0.760, 0.720,
>> 0.680, 0.640, 0.600, 0.575, 0.525,
>> 0.485, 0.445, 0.400,
>> 0.350, 0.300, 0.285, 0.251, 0.217,
>> 0.192, 0.164, 0.141,
>> 0.119, 0.103, 0.083, 0.067, 0.055,
>> 0.043, 0.033, 0.024,
>> 0.000,
>>
>> /
>>
>>
>>
>>
>> --
>>
>>
>>
>> *Xin XiSchool of Earth and Atmospheric SciencesGeorgia Institute of
>> Technology 311 Ferst Drive, Atlanta, GA 30332-0340*
>>
>> _______________________________________________
>> Wrf-users mailing list
>> Wrf-users at ucar.edu
>> http://mailman.ucar.edu/mailman/listinfo/wrf-users
>>
>
>
>
> --
>
>
>
> *Xin XiSchool of Earth and Atmospheric SciencesGeorgia Institute of
> Technology 311 Ferst Drive, Atlanta, GA 30332-0340*
>
--
*Xin XiSchool of Earth and Atmospheric SciencesGeorgia Institute of
Technology311 Ferst Drive, Atlanta, GA 30332-0340*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ucar.edu/pipermail/wrf-users/attachments/20140609/afefca18/attachment-0001.html
More information about the Wrf-users
mailing list