wrf.exe fail auxinput4_interval sst_update=1

[AndrewLowry]

I am trying to run wrf for a long climatological run with time varying sst. Unfortunately some input files were lost, so I needed to modify the simulation for 1.75 days, to in essence hop over the missing data. The climatological run uses 6hrly data and was stopped at the last timestamp before the data gap and a restart file created. Then WPS and real.exe were run for the data gap period, 42hours.

The problem is wrf is not coping with the change for the namelist variable auxinput4_interval. The key values in the namelist.input are (the whole namelist.input is attached)
interval_seconds = 151200,
input_from_file = .true.,
auxinput4_inname = "wrflowinp_d<domain>",
auxinput4_interval = 2520,
sst_update = 1,
max_dom = 1,

Here are the values from the real.exe files
ncdump -v Times wrfbdy_d01
Times =
"1866-10-01_00:00:00"

ncdump -v Times wrflowinp_d01
Times =
"1866-10-01_00:00:00",
"1866-10-02_18:00:00"

There is a model restart file wrfrst_d01_1866-10-01_00:00:00

The model starts and runs for 6 hours, then if fails with the error (see attached rsl.out.0000 and rsl.error.0000):

Timing for Writing wrfout_d01_1866-10-01_06:00:00 for domain 1: 1.24212 elapsed seconds
d01 1866-10-01_06:00:00 Input data is acceptable to use: wrflowinp_d01
Time in file: 1866-10-02_18:00:00
Time on domain: 1866-10-01_06:00:00
**WARNING** Time in input file not equal to time on domain **WARNING**
**WARNING** Trying next time in file wrflowinp_d01 ...
2 input_wrf: wrf_get_next_time current_date: 1866-10-02_18:00:00 Status = -4
d01 1866-10-01_06:00:00 ---- ERROR: Could not find matching time in input file wrflowinp_d01
NOTE: 1 namelist vs input data inconsistencies found.
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 1297
NOTE: Please check and reset these options
-------------------------------------------

What I think is happening is the value auxinput4_interval = 2520 is being ignored, I suspect because sst_update=1. The model seems to be reverting to a default of auxinput4_interval = 360, and thus failing at 6 hours.
I noted two other threads with similar issues auxinput4 error on wrf.exe (ecmwf hres) and Could not find matching time in input file when use sst_update Neither of the solutions there seem to apply.

 

[Ming Chen]

For WRF restart run, the clock-alarms are always derived from the restart file and thus follows the settings in the previous run.

This is why the model tries to find SST update at the time of 1866-10-01_06:00:00.

The option override_restart_timers doesn't work for sst_update interval.

You may take a look how override_restart_timers works, and follow the same approach to add an option to control clock-alarm for sst_update. Note that this is tedious and time-expensive if you are not familiar with the clock-alarm system in WRF.