FHMAX in regression tests #1559
-
I had a question about the settings in model_configure and nems.configure. nhours_fcst in model_configure.IN and stop_n in nems.configure.cpld.IN are both set to @[FHMAX]. According to the documentation here that is correct for the initial run, but on restart stop_n does not increase while nhours_fcst does. It seems like these should not both be set to @[FHMAX], unless there is a change happening on restart in rt.sh that I haven't been able to track down. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
Our restart tests always utilize checkpoint restarts; so the control run will be from hr 0-> hr 24 and a restart written at hour 12. The restart run starts from hr 12 -> hr 24. So the fhmax does not change...we're still forecasting 24 hours from the initial (start) time. |
Beta Was this translation helpful? Give feedback.
-
@benjamin-cash I don't believe The In med_phases_restart_mod.F90, the alarm is used to write a restart file, but only if the
|
Beta Was this translation helpful? Give feedback.
@benjamin-cash I don't believe
stop_n
has any impact unless an additional configuration variable (write_restart_at_endofrun
) is also set. This forces the creation of a mediator restart file at the end of the run.The
stop_alarm
is created usingstop_n
,stop_option
andstop_ymd
in med.F90 and these need to be present because they are not currently protected w/isPresent
,isSet
conditionals.In med_phases_restart_mod.F90, the alarm is used to write a restart file, but only if the
write_restart_at_endofrun
is also set true (false by default).