8000 Cycling - run every [date-time] *starting from* some offset of the ICP · Issue #2668 · cylc/cylc-flow · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Cycling - run every [date-time] *starting from* some offset of the ICP #2668
Open
@dwsutherland

Description

@dwsutherland

I’m a little stumped about how to define the following cycling schedules:

a. Run every T18 hour starting 6weeks after the initial cycle point (ICP)
b. Run on the 5th day and 18th hour of every month starting 6 weeks after the ICP

Now without the “6 week after ICP” thing they are:

a. [[[ T18 ]]]
b. [[[ 05T18 ]]]

With the delayed start:

a. [[[ +P6W/PT6H ! ( T00, T06, T12 )]]] ?
b. [[[ +P6W/PT6H ! ( +P6W/PT6H ! ( 05T18 ))]]]?

These produce a recursion error
[FAIL] cylc validate -v -o /tmp/tmp1COnZH --strict NZLAM_4P4KM # return-code=1, stderr=
[FAIL] 'ERROR: Cannot process recurrence +PT6W/PT6H ! (T00,T06,T12) (initial cycle point=20180515T12) (final cycle point=None)'

And they are too convoluted as a solution to the issue of scheduling the following phrase:
Run every [date-time] starting from some offset of the ICP

Perhaps; need provide more than:
R[ limit ?]/[ date - time ]
R[ limit ?]//[ interval ]
[date - time ]/[ interval ]
R[ limit ?] # Special limit of 1 case
[date - time ]
[ interval ]

[date - time] often is represented by a date string or an offset (i.e 01T00 or [+/-]PT1D), could these be two different items; [date - time] and [offset]?

So:
R[ limit ?]/[ date - time ]
R[ limit ?]//[ interval ]
R[ limit ?]/[ date - time ]/[offset]
R[ limit ?]//[ interval ]/[offset]
[date - time ]/[ interval ]
[date - time ]/[ interval ]/[offset]
[date - time ]/[offset]
[ interval ]/[offset]

Thoughts?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0