ecFlow's documentation is now on readthedocs!

Please go to https://ecflow.readthedocs.io/en/latest/index.html

  • Created by Unknown User (ma0), last modified on Aug 12, 2019

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

The way day/date attributes are used has changed.  Recall how day/date with time attributes:

Here the day/date act like a guard over the time. Hence the time is not considered until the day/date is free.

task t1      # run on Monday @ 10:00
  day monday
  time 10:00
task t1   # run on Monday @ 10:00
   date 05.08.2019
   time 10:00

This show the change when we have day/date:

In ecflow 4.0 the definition below can produce unexpected runs.

The behaviour in ecflow 4.0 happens because the time attribute are treated individually.

Here the time 10:00, was set free on Sunday. 

(when time attributes are set free, they stay free, until re-queue.)

ecflow 4.0
...
family f1
   day monday
   task t1
      time 10:00  # runs Monday an midnight and Monday at 10.00

In ecflow 5.0, The day acts like a guard over the time.

Hence this produces the expected results.

ecflow 5.0
...
family t1
  day monday
  task t1
    time 10:00 # run on Monday @ 10:00
  • No labels