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

ERROR: Ran out of valid boundary conditions in file wrfbdy_d01

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.

R

robson_passos

New member
Dear,
I am running WRF for 4 days of simulation. My simulation starts on the date 2016-09-20_00:00:00 and ends on the date 2016-09-23_23:00:00 with interval_seconds = 3600. However, the following error is occurring in the last hour of the simulation:

d01 2016-09-23_23: 00: 00 Input data is acceptable to use: wrfbdy_d01
2 input_wrf: wrf_get_next_time current_date: 2016-09-23_23: 00: 00 Status = -4
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 1151
---- ERROR: Ran out of valid boundary conditions in file wrfbdy_d01
-------------------------------------------
Click to expand...

I don't understand what the problem is, as the date in the namelist.wps file is set to the correct range:

& share
wrf_core = 'ARW',
max_dom = 2,
start_date = '2016-09-20_00: 00: 00', '2016-09-20_00: 00: 00',
end_date = '2016-09-23_23: 00: 00', '2016-09-23_23: 00: 00',
interval_seconds = 3600
io_form_geogrid = 2,
/
Click to expand...

And in the namelist.input file too:

& time_control
run_days = 4,
run_hours = 0,
run_minutes = 0,
run_seconds = 0,
start_year = 2016, 2016,
start_month = 9, 9,
start_day = 20, 20,
start_hour = 0, 0,
start_minute = 00, 00,
start_second = 00, 00,
end_year = 2016, 2016,
end_month = 9, 9,
end_day = 23, 23,
end_hour = 23, 23,
end_minute = 00, 00,
end_second = 00, 00,
interval_seconds = 3600,
input_from_file = .true., .true.,
history_interval = 10, 10,
frames_per_outfile = 144, 144,
restart = .false.,
restart_interval = 99999,
io_form_history = 2,
io_form_restart = 2,
io_form_input = 2,
io_form_boundary = 2,
debug_level = 0,
/
Click to expand...

Could anyone clarify where the problem is?
Thank you very much in advance.
Robson
 
Robson,
This is because your wrfbdy flie covers a period shorter than the integration time you specify in namelist.input.
Please type the command:
ncdump -v Times wrfbdy_d01,
You will see the times when data are available in wrfbdy. You need to specify the start and end time of model integration based on when the data are available.
 
Dear Ming Chen, thank you very much for your reply. In fact, the file wrfbdy_d01 has a date range from 2016-09-20_00: 00: 00 to 2016-09-23_22: 00: 00 and not from 2016-09-20_00: 00: 00 to 2016-09-23_23: 00 : 00, so this error happens, as you mentioned.

I just don't understand why the wrfbdy_d01 file has a date range until 2016-09-23_22: 00: 00, because my meteorological data in grib format has the date 2016-09-23_23: 00: 00. Do I have to download an extra hour for my simulation to run until 2016-09-23_23: 00: 00?

Thank you very much in advance,
Robson
 
Robson,
In your case, if the wrfbdy_d01 file has a date range until 2016-09-23_22: 00:00, then it is fine for a run ending at 2016-09-23_23: 00:00. This is because the lateral boundary tendencies for the period 2016-09-23_22: 00:00 - 2016-09-23_23: 00:00 have been included in wrfbdy at 2016-09-23_22: 00:00.

Please set
run_days = 3,
run_hours = 23,

Then try again.
 
You must log in or register to reply here.
Top