Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ICP = next(...) syntax improvement #3187

matthewrmshin opened this issue Jun 10, 2019 · 1 comment


Copy link

commented Jun 10, 2019

Issue discussed in this Discourse thread:

For example, in order to start a crontab job to run every 5 minutes starting from the earliest 5, 10, 15, etc minutes past the hour, the crontab syntax is just:

*/5 * * * * do-stuff

In Cylc, user has to do:

    initial cycle point = next(T-00; T-05; T-10; T-15; T-20; T-25; T-30; T-35; T-40; T-45; T-50; T-55)
             graph = @wall_clock => do-stuff

It is fair to say that Cylc needs to do more than Crontab, but we should at least try to find a way to simplify the initial cycle point = next(...) syntax.

@matthewrmshin matthewrmshin added this to the later milestone Jun 10, 2019


This comment has been minimized.

Copy link

commented Jun 10, 2019

Just to note contemplation of cron-like real time scheduling in Cylc can get quite mind-bending when you consider things like: we could have parts of a cycling Cylc suite tied to a real time schedule while other parts (even with the same cycle points, potentially) are not tied; and note that ICP = now and ICP = next(...) choose ICP relative to real time "now" BUT tasks in the first cycle point will still trigger without regard for the clock unless entirely optional clock-triggers are attached to them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.