Please help with cycling behaviour

Cylc Cylc Support
1

Hello, please help me understand this behaviour. I have a test workflow that is supposed to run every monday and wednesday, with the restart files of the previous run.

[ scheduling ]
    initial cycle point = 20260323
    final cycle point = 20260403
    [[ xtriggers ]]
        clock_trigger = wall_clock()
    [[ graph ]]
        R1 = """ clean """
        R//P7D, R/+P3D/P7D = """
            clean[^] => init => block_DATA => block_NEMO<cycle=0>
                block_NEMO<cycle=0> => ola2wola<cycle=0> & concat_bias_hts
                block_NEMO<cycle=0> => com2newcom => MROA
                ola2wola<cycle=0> & concat_bias_hts => create_lightout
                create_lightout => block_BIASTS
                block_NEMO<cycle=1> => ola2wola<cycle=1>
                MROA => cpmxpackcmz2cpmx => cpmx2cdf => cdf2cmx
                cdf2cmx => cmx2splitcmx => canredcmx2cmx_forsplit
                canredcmx2cmx_forsplit => cpmx2cdf_forsplit
                block_BIASTS & cdf2cmx => block_NEMO<cycle=1>
        """
        R/P7D = block_NEMO<cycle=1>[-P4D] => block_NEMO<cycle=0>
        R/+P3D/P7D = block_NEMO<cycle=1>[-P3D] => block_NEMO<cycle=0>

but when I run it, it runs on 23, 27, 30, 03 instead of 23, 26, 30, 02
If I change the final cycle point to 20260301 then it runs on 23, 25, 26, 30 instead of just on 23, 26, 30
What am I missing?
Thanx
Gaby

2

Hi,

R//P7D and R/P7D mean different things.

Try this example:

[scheduler]
    allow implicit tasks = True

[scheduling]
    initial cycle point = 2000-01-01
    final cycle point = 2000-02-02
    [[graph]]
        # count forwards from the ICP
        R//P1W = one
        # count backwards from the FCP
        R/P1W = two
3

Darn, that was not even intended on my part, it’s a typo. Thanx for clearing that up @oliver.sanders