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

WRF restart run cannot find a valid time to start the LBC

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.

edougherty

New member
Hi there,

I am attempting to run a WRF restart run. I ran my first run with the following set-up in my namelist.input file:

Code:
&time_control
 run_days                            = 0,
 run_hours                           = 12,
 run_minutes                         = 0,
 run_seconds                         = 0,
 start_year                          = 2008, 2008, 2008, 2008,
 start_month                         = 03,   03,   03,   03,
 start_day                           = 17,   17,   17,   17,
 start_hour                          = 18,   18,   18,  18,
 end_year                            = 2008, 2008, 2008, 2008,
 end_month                           = 03,   03,   03,   03,
 end_day                             = 18,   18,   18,   18,
 end_hour                            = 06,   06,   06,   06,
 interval_seconds                    = 21600
 input_from_file                     = .true.,.true.,.true.,.true.,
 history_interval                    = 180,   180,    60,    60,
 frames_per_outfile                  = 1,     1,     1,     1,
 restart                             = .false.,
 restart_interval                    = 720,
 io_form_history                     = 2
 io_form_restart                     = 102

And this generated the correct wrfout and wrfrst files.

However, when I try to run the restart run with the following namelist configuration:
Code:
&time_control
 run_days                            = 0,
 run_hours                           = 12,
 run_minutes                         = 0,
 run_seconds                         = 0,
 start_year                          = 2008, 2008, 2008, 2008,
 start_month                         = 03,   03,   03,   03,
 start_day                           = 18,   18,   18,   18,
 start_hour                          = 06,   06,   06,   06,
 end_year                            = 2008, 2008, 2008, 2008,
 end_month                           = 03,   03,   03,   03,
 end_day                             = 18,   18,   18,   18,
 end_hour                            = 18,   18,   18,   18,
 interval_seconds                    = 21600
 input_from_file                     = .true.,.true.,.true.,.true.,
 history_interval                    = 180,   180,    60,    60,
 frames_per_outfile                  = 1,     1,     1,     1,
 restart                             = .true.,
 restart_interval                    = 720,
 io_form_history                     = 2
 io_form_restart                     = 102

I receive the following error messages in my rsl files:
Code:
d01 2008-03-18_06:00:00  Input data is acceptable to use: wrfbdy_d01
d01 2008-03-18_06:00:00 WRF restart, LBC starts at 2008-03-17_18:00:00 and restart starts at 2008-03-18_06:00:00
 LBC for restart: Starting valid date = 2008-03-17_18:00:00, Ending valid date = 2008-03-18_00:00:00
 LBC for restart: Restart time            = 2008-03-18_06:00:00
 LBC for restart: Looking for a bounding time
 LBC for restart: Starting valid date = 2008-03-18_00:00:00, Ending valid date = 2008-03-18_06:00:00
d01 2008-03-18_06:00:00 ---- ERROR: Cannot find a valid time to start the LBC during this restart, likely ran out of time periods to test

Can you please help me figure out how to fix this issue?
 
First, Please confirm that you have wrfrst file at 2008-03-18_06

Then check the wrfbdy file to make sure int covers the period of your integration. Please issue the command below:
ncdump -v Times wrfbdy_d01, and look at the time slices it include.
 
Yes, I have wrfrst files for 2008-03-18_06:00.

I checked the times in wrfbdy_d01 and the time slice is from 2008-03-17_18:00:00 to 2008-03-18_00:00:00, so I'm guessing this is the issue.

I will try running real.exe and wrf.exe to see if this fixes the issue. Thanks!
 
You need to rerun real.exe to produce new wrfbdy that covers the entire period of your integration.
 
Top