Versions Compared

Old Version 1

changes.mady.by.user Unknown User (ma0)

Saved on

compared with

New Version 2

changes.mady.by.user Unknown User (ma0)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.


Code Block
task t1      # run on Monday @ 10:00
  day monday
  time 10:00



Code Block
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.)

Code Block
titleecflow 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.

Code Block
titleecflow 5.0
...
family t1
  day monday
  task t1
    time 10:00 # run on Monday @ 10:00