Basic Cycling

Aims

You will be able to:

✅ Write simple cycling (repeating) workflows.

Repeating Workflows

You may want to repeat the same workflow multiple times. In Cylc this is called cycling, and each repetition is called a cycle.

Each cycle is given a unique label, called a cycle point. For now these will be integers, but they can also be datetimes as we will see in the next section.

To make a workflow repeat we must tell Cylc three things:

The recurrence.

How often to repeat the workflow (or part of it).

The initial cycle point.

The cycle point to start from.

The final cycle point (optional).

We can also tell Cylc where to stop the workflow.

Let’s take the bakery example from the previous section. Bread is baked in batches so the bakery will repeat this workflow for each batch. We can make the workflow repeat by adding three lines:

 [scheduler]
     allow implicit tasks = True
 [scheduling]
+    cycling mode = integer
+    initial cycle point = 1
     [[graph]]
-        R1 = """
+        P1 = """
             buy_ingredients => make_dough
             pre_heat_oven & make_dough => bake_bread
             bake_bread => sell_bread & clean_oven
         """

• cycling mode = integer tells Cylc to give our cycle points integer labels.

• initial cycle point = 1 tells Cylc to start counting cycle points from 1.

• P1 is the recurrence; a P1 graph string repeats at every integer cycle point.

The first three cycles look like this, with the entire workflow repeated at each cycle point:

The number under each task shows which cycle point it belongs to.

Intercycle Dependencies

We’ve just seen how to write a workflow that repeats every cycle.

Cylc runs tasks as soon as their dependencies are met, regardless of cycle point, so cycles will not necessarily run in order. This can be efficient, but it could also cause problems. For instance we could find ourselves pre-heating the oven in one cycle while still cleaning it in another.

To resolve this we can add dependencies between cycles, to the graph. To ensure that clean_oven completes before pre_heat_oven starts in the next cycle, we can write this:

clean_oven[-P1] => pre_heat_oven

In a P1 recurrence, the suffix [-P1] means the previous cycle point, Similarly, [-P2] refers back two cycles. The new dependency can be added to the workflow graph like this:

 [scheduling]
     cycling mode = integer
     initial cycle point = 1
     [[graph]]
         P1 = """
             buy_ingredients => make_dough
             pre_heat_oven & make_dough => bake_bread
             bake_bread => sell_bread & clean_oven
+            clean_oven[-P1] => pre_heat_oven
         """

And the resulting workflow looks like this:

The intercycle dependency forces the connected tasks, in different cycle points, to run in order.

Note that the buy_ingredients task has no arrows pointing at it. This means it has no parent tasks to wait on, upstream in the graph. Consequently all buy_ingredients tasks (out to a configurable runahead limit) want to run straight away. This could cause our bakery to run into cash-flow problems by purchasing ingredients too far in advance of using them.

To solve this problem without running out of ingredients, the bakery wants to purchase ingredients two batches ahead. This can be achieved by adding the following dependency:

 [scheduling]
     cycling mode = integer
     initial cycle point = 1
     [[graph]]
         P1 = """
             buy_ingredients => make_dough
             pre_heat_oven & make_dough => bake_bread
             bake_bread => sell_bread & clean_oven
             clean_oven[-P1] => pre_heat_oven
+            sell_bread[-P2] => buy_ingredients
         """

This means that buy_ingredients will run after the sell_bread task two cycles earlier.

Note

The [-P2] suffix references a task two cycles back. For the first two cycles this doesn’t make sense, so those dependencies (and indeed any before the initial cycle point) will be ignored.

Recurrence Sections

In the previous examples we used a P1recurrence to make the workflow repeat at successive integer cycle points. Similarly P2 means repeat every other cycle, and so on. We can use multiple recurrences to build more complex workflows:

[scheduling]
   cycling mode = integer
   initial cycle point = 1
   [[graph]]
      # Repeat every cycle.
      P1 = foo
      # Repeat every second cycle.
      P2 = bar
      # Repeat every third cycle.
      P3 = baz

We can also tell Cylc where to start a recurrence sequence.

From the initial cycle point:

By default, recurrences start at the: initial cycle point.

From an arbitrary cycle point:

We can give a different start point like this: 5/P3 means repeat every third cycle, starting from cycle number 5. To run a graph at every other cycle point, use 2/P2.

Offset from the initial cycle point:

The start point of a recurrence can also be defined as an offset from the initial cycle point For example, +P5/P3 means repeat every third cycle from 5 cycles after the initial cycle point.

Practical

In this practical we will turn the workflow of the previous section into a cycling workflow.

If you have not completed the previous practical use the following code for your flow.cylc file.

[scheduler]
    allow implicit tasks = True
[scheduling]
    [[graph]]
        R1 = """
            a & c => b => d & f
            d => e
        """

1. Create a new workflow.

   Create a new source directory integer-cycling under ~/cylc-src/, and move into it:

   mkdir -p ~/cylc-src/integer-cycling
   cd ~/cylc-src/integer-cycling
   

   Copy the above code into a flow.cylc file in that directory.

2. Make the workflow cycle.

   Add the following lines to your flow.cylc file:

    [scheduling]
   +    cycling mode = integer
   +    initial cycle point = 1
        [[graph]]
   -        R1 = """
   +        P1 = """
                a & c => b => d & f
                d => e
            """
   

3. Visualise the workflow.

   Try visualising your workflow using cylc graph.

   cylc graph .
   

   Tip

   You can use the -c (--cycles) option to draw a box around each cycle:

   cylc graph -c .
   

   Tip

   By default cylc graph displays the first three cycles of the graph, but you can specify the range of cycles on the command line. Here’s how to display cycles 1 through 5:

   cylc graph . 1 5
   

4. Add another recurrence.

   Suppose we wanted the e task to run every other cycle as opposed to every cycle. We can do this by adding another recurrence.

   Make the following changes to your flow.cylc file.

    [scheduling]
        cycling mode = integer
        initial cycle point = 1
        [[graph]]
            P1 = """
                a & c => b => d & f
   -            d => e
            """
   +        P2 = """
   +            d => e
   +        """
   

   Use cylc graph to see the effect this has on the workflow.

5. intercycle dependencies.

   Now we will add three intercycle dependencies:

   1. Between f from the previous cycle and c.

   2. Between d from the previous cycle and a every odd cycle (e.g. 2/d => 3/a).

   3. Between e from the previous cycle and a every even cycle (e.g. 1/e => 2/a).

   Try adding these to your flow.cylc file to make your workflow match the diagram below.

   Hint

   • P2 means every other cycle, from the initial cycle point.

   • 2/P2 means every other cycle, from cycle point 2.

   Solution

   [scheduler]
       allow implicit tasks = True
   [scheduling]
       cycling mode = integer
       initial cycle point = 1
       [[graph]]
           P1 = """
               a & c => b => d & f
               f[-P1] => c  # (1)
           """
           P2 = """
               d => e
               d[-P1] => a  # (2)
           """
           2/P2 = """
               e[-P1] => a  # (3)
           """