I have just upgraded a suite from Cylc 7.6 to Cylc 8.6 following the CMS tutorial. The model passed validation and execution, but it fails during the post‑processing stage (see error). Thanks in advance for your help
[FAIL] Unable to determine cycle point in ISO format: None
[FAIL] Terminating PostProc…
[FAIL] main_pp.py cice # return-code=1
I suspect it may be because you have changed rose date to isodatetime in the [[POSTPROC_RESOURCE]] section in site/archer2.rc. Please try changing it back to rose date - this is what we have in the other ARCHER2 suites.
I changed back the isodatetime to rose date, but the model still blowing with that error. I wonder if it is anything wrong with the $CYLC_TASK_CYCLE_POINT because the error says “Unable to determine cycle point in ISO format: None“. Like the variable is empty
CYLC_TASK_CYCLE_POINT seems to be set correctly elsewhere and that error message comes out of the routine using CYCLEPERIOD which is why I hoped it was the use of isodatetime. I’ll take another look. Unfortunately, when I tried to run your suite yesterday I couldn’t get it to run at all - hopefully it was just ARCHER2. I’ll try again now.
thanks so much for your help. You should be able to reach postproc without any other errors. I have just commited all the changes. There was a small error in one of the rose date (a missing -c).
After some investigation, the problem is because postproc can’t determine what the final cycle point is. The postproc code figures this out by one of 3 environment variables, none of which are currently set in your suite. The easiest way to fix this is to add the environment variable ARCHIVE_FINAL to the postproc settings.
In app/postproc/rose-app.conf in the [env] section add:
ARCHIVE_FINAL=false
You’ll need to manually switch this to true for the final cycle.
Thank you so much for your help. The suite runs perfectly with the addition of the variable ARCHIVE_FINAL. It also works with the new syntax changes (i.e., isodatetime and CYLC_WORKFLOW_*).