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.
|
|
|---|
In ecflow 4.0 the definition below can produce unexpected runs.
...
family f1
time 10:00 # set free on Sunday
task t1
day monday # runs Monday@00:00 and Monday@10.00 |
In ecflow 4.0 the day/date act like a guard over any other time attribute.
Hence the time is not considered until the day is free. This has been fixed in ecflow 5.0..
...
family f1
day monday
task t1
time 10:00 # runs on Monday@10.00 |
However both behave the same way for the following definition.
...
family f1
time 10:00 # set free on the sunday
task t1
day monday # runs Monday@00:00 and Monday@10.00 |