ndown with different start time

Discuss the nesting capability within the model itself and any problems you might have run into.

ndown with different start time

Postby D3Lwrf » Tue Mar 11, 2014 8:10 am

I am trying to use the output from a previous 2 domain wrf run as input for a 3rd domain run over a shorter time period where the start time does not match that of the previous 2 domain run. Is it possible to use ndown in this way?

I have set the start and end times to those I require and I get as far as running ndown with no problems but running ndown produces the following error:
Time in file: 2009-01-04_18:00:00
Time on domain: 2008-12-31_18:00:00
**WARNING** Time in input file not equal to time on domain **WARNING**
**WARNING** Trying next time in file wrfndi_d02 ...
3 input_wrf: wrf_get_next_time current_date: 2009-01-04_18:00:00 Status = -4
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 848
... Could not find matching time in input file wrfndi_d02

Are there additional steps to those used in running a standard ndown run? Are there other namelist setting that need adding/changing? My namelist.input time control settings on running ndown are as follows:

&time_control
start_year = 2008, 2009,
start_month = 12, 01,
start_day = 31, 04,
start_hour = 18, 18,
start_minute = 0, 0,
start_second = 0, 0,
end_year = 2009, 2009,
end_month = 01, 01,
end_day = 06, 06,
end_hour = 0, 0,
end_minute = 0, 0,
end_second = 0, 0,
interval_seconds = 21600,
input_from_file = .true., .true.,
fine_input_stream = 0, 2,
history_interval = 10, 10,
frames_per_outfile = 1000, 1000,
restart = .false.,
restart_interval = 20000,
io_form_history = 2,
io_form_restart = 2,
io_form_input = 2,
io_form_boundary = 2,
io_form_auxinput2 = 2,
debug_level = 0,

Any suggestions?
D3Lwrf
 
Posts: 1
Joined: Tue Mar 11, 2014 7:49 am

Re: ndown with different start time

Postby mulena » Tue Jun 23, 2015 11:17 am

I have the same problem...

ERROR:

alloc_space_field: domain 2 , 11531520 bytes allocated
Time in file: 2014-01-01_00:00:00
Time on domain: 2013-12-31_00:00:00
**WARNING** Time in input file not equal to time on domain **WARNING**
**WARNING** Trying next time in file wrfndi_d02 ...
3 input_wrf: wrf_get_next_time current_date: 2014-01-01_00:00:00 Status = -4
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 883
... Could not find matching time in input file wrfndi_d02
-------------------------------------------
application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0


My time control:



start_year = 2013, 2014, 2014,
start_month = 12, 01, 01,
start_day = 31, 01, 02,
start_hour = 00, 00, 00,
start_minute = 00, 00, 00,
start_second = 00, 00, 00,
end_year = 2014, 2014, 2014,
end_month = 01, 01, 01,
end_day = 03, 03, 03,
end_hour = 00, 00, 00,
end_minute = 00, 00, 00,
end_second = 00, 00, 00,


Thanks for your help. I
mulena
 
Posts: 2
Joined: Mon Apr 27, 2015 5:28 pm


Return to Nesting

Who is online

Users browsing this forum: No registered users and 6 guests

cron