Hello, I am running the public ICON 2025.10 atmosphere-only model on an HPC cluster using mkexp. I generated a simple Jablonowski–Williamson (JW) experiment with
INITIAL_DATE = 2000-01-01T00:00:00Z
FINAL_DATE = 2001-01-11T00:00:00Z
The generated namelist contains
checkpointtimeintval = P1Y
restarttimeintval = P1Y
The model behaves as expected:
- It runs successfully from 2000-01-01 to 2001-01-01.
- It writes the restart directory: jw5_restart_atm_20010101T000000Z.nc/
- It writes finish.status = RESTART.
- It exits normally without any errors.
The restart files are present and appear to be complete. However, the experiment does not continue automatically to the final experiment date (2001-01-11). It stops after the first restart interval.
My questions are:
-
Is this the expected behaviour in the public ICON 2025.10 release?
-
After finish.status = RESTART, is the continuation of the experiment supposed to be handled automatically by mkexp, or is an external workflow manager (or manual resubmission) expected?
-
If automatic restart chaining is supported, is there an additional mkexp configuration or workflow option that needs to be enabled? Any guidance would be greatly appreciated.
While investigating, I noticed that run_start explicitly resolves to .trigger = “” in the generated *.dump, so the restart-submission block in DEFAULT.run.tmpl is not rendered. Is this the intended design, and if so, what is the expected mechanism for invoking the logical run job after the initial segment?
Thank you.