mlwasserstein
New member
Hello:
I am running a WRF simulation which requires me to execute a restart run due to wall time restrictions. For some reason, though, despite specifying a restart_interval of 60 (1 hour), restart files are not produced at the exact hour:

This is problematic because when trying to execute a restart run which starts at 2019-03-22_20:00:03 (my latest restart time), my wrfout files are then not produced at exact hourly intervals, which is what I want (e.g. wrfout_d04_2019-03-23_02:29:55 gets produced). I suspect this issue is due to my very short time step of 4.05 s (namelist.input) attached, which is what I've needed to use to get the model to run successfully.
Is there any way I can remedy this issue and produce restart files at the exact hour, so that my wrfout files in a restart run are produced on the exact hour?
I am running a WRF simulation which requires me to execute a restart run due to wall time restrictions. For some reason, though, despite specifying a restart_interval of 60 (1 hour), restart files are not produced at the exact hour:

This is problematic because when trying to execute a restart run which starts at 2019-03-22_20:00:03 (my latest restart time), my wrfout files are then not produced at exact hourly intervals, which is what I want (e.g. wrfout_d04_2019-03-23_02:29:55 gets produced). I suspect this issue is due to my very short time step of 4.05 s (namelist.input) attached, which is what I've needed to use to get the model to run successfully.
Is there any way I can remedy this issue and produce restart files at the exact hour, so that my wrfout files in a restart run are produced on the exact hour?