i have a postprocessing/visualisation workflow (let’s call it foo) which runs after every year of my climate simulation (i think many others do to but not sure) and so for a standard 65 year run, i get foo/run1, foo/run2, ..., foo/run65.
I don’t and won’t need to keep any of them so is there a way i can either automatically cylc clean them after they’ve successfully finished or maybe always get it to repeat run1?
any ideas/suggestions welcome!
@hilary.j.oliver this will help a lot to reduce my installed workflow count!
Well, maybe, if you really want a strained analogy!
A post-script is a fragment of task scripting that executes in a running task job.
Event handlers are run by the scheduler (not by tasks) when certain events occur.
Shutdown handlers are run by the scheduler at the last instant before shut down, when the workflow is finished. So they have nothing to do with task scripting.
in this particular example the workflow isn’t creating anything inside the cylc-run directory that i need to keep so your suggestion is safe but i appreciate that this isn’t true in general.
The cylc clean command is quite flexible in terms of what it does (not?) delete. Worth looking the --help docs. But ultimately it’s a deletion command. A sharp axe is still an axe.