Dear Community,
I noticed that when the suite has the archive_restart flag enabled, NEMO cannot find the restart files because the post‑processing routine rebuilds and transfers the restart file (and everything else) to the archive. Is there any way to fix this? I cannot change the order because I risk losing the post‑processing during the last cycle.
Best regards,
Estanislao
Hi Estanislao,
What’s the suite id please?
The archive_restart flag only triggers restart files to be archived at the specified intervals during the run when they are no longer required. There is a separate flag to trigger archiving of all the dumps in the final cycle. Don’t understand what you mean about changing the order; changing the order of what?
Cheers,
Ros
Hi Ros,
I meant not to transfer the files until the next cycle has started. To do that, I can modify the order of the post‑processing tasks in the workflow. How do you set the flag so that all restart files are archived in the final cycle? The suite is u‑dy120.
Best regards,
Estanislao
Hi Estanislao,
I think it’s because you have all the restart_buffers variables set to 0 so it’s not leaving any on disk.
In postproc → NEMO → restart files set:
archive_restarts = true
archive_restart_buffer = 2 (or 1)
In postproc → CICE → restart files set:
archive_restarts = true
archive_restart_buffer = 1
Regarding final cycle archiving I think it should figure it out itself, if it doesn’t you can set ARCHIVE_FINAL=true in app/postproc/rose-app.conf for the last cycle.
Cheers,
Ros
Hi Ros,
It’s because I am using the Gregorian calendar, and it is quite hard to set the restart files properly in the namelist. So I leave it at zero, and I only get the last restart file — that’s the only one I’m interested in. I will set archive_final then.
Thanks so much for your help.
Estanislao