Hi all! We are in the process of verifying our first full workflow in order to put it in production (yey!), and I am already trying to figure out how to handle a variation of it.
This workflow would be relatively easy to achieve except for the pesky nowcast that has a varying model cycles length.
What would be the best way to keep track of where I am at? I can’t think of making it work without having a file that captures how many model cycles I am running with at the moment. I am thinking in particular when having to restart the model because of some problem or other.
Each “cast” runs in its own workflow, with triggers managing the dependencies bewteen the casts, and clock triggers for scheduling the runs
Cheers!
Gaby
Hi,
I’m not sure I’ve understood the setup, but here’s a Cylc translation of the diagram:
[scheduling]
[[graph]]
P3D = b3[-P3D] => b3 => h3 => n3 => f10
+P1D/P3D = h3[-P1D] => n4 => f10
+P2D/P3D = n4[-P1D] => n5 => f10
It would be possible to use Jinja2 to adapt this for an arbitrary number of n<x> cycles.
Hi Oliver, it’s food for thought, thanx.