Description
Hi cylc devs,
I would find it useful if the graph time specification could be a bit more flexible in regards to making something not run at a specific cycle.
[[[PT6H ! ^]]]
works fine, but sometimes it isn't ideal for flexibility to specify that sort of syntax. If I have a suite that will have different hours used based on the chosen runtime configuration, I migh
57E8
t have something like
[[[T00,T12]]]
graph
[[[T06,T18]]]
graph
[[[T03,T09]]]
graph
[[[T06,T18]]]
graph
In these cases, I'm not wanting to run certain tasks on the first cycle point, but I can't just combine the two hour specifiers into one thing cleanly. I have tried using ```[[[ T00, T06, T12, T18 ! ^ ]]]but this doesn't work. It validates, but the desired impact doesn't happen because it seems the
! ^` only applies to the last entry. If I specify `[[[ T00 ! ^, T06 ! ^, T12 ! ^, T18 ! ^ ]]]` I get the desired result.
I think it would be useful, for me, to be able to do [[[ (T00, T06, T12, T18) ! ^ ]]]
, which would keep it in line with the [[[ T-00 ! (T00, T06, T12, T18) ]]]
syntax which already exists.
I hope this makes sense as I'm struggling with the wording. Basically I think it boils down to me having trouble with not running tasks at the initial cycle point for an unknown cycle frequency or irregular cycling frequency suite. By accepting the ( ... )
syntax (which cylc could expand in the background) extra flexibility would be gained.