...
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
| Code Block | ||
|---|---|---|
| ||
...
family f1
day monday
task t1
time 10:00 # runs on Monday@10.00 |
| Code Block |
|---|
...
family f1
time 10:00 # set free on the sunday
task t1
day monday # runs Monday@00:00 and Monday@10.00 |
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.)
. This has been fixed in ecflow 5.0..
| Code Block | ||
|---|---|---|
|
...
| |
...
family f1
day monday
task t1
time 10:00 # runs |
...
| title | ecflow 4.0 |
|---|
...
|
...
on |
...
Monday@10.00 |
However both behave the same way for the following definition.
| Code Block |
|---|
In ecflow 5.0, The day acts like a guard over the time.
The time is not set free, until Monday is free.
Hence this produces the expected results.
| Code Block | title | ecflow 5.0|
|---|---|---|
... family t1f1 day monday task t1 time 10:00 # run on Monday @ 10:00 | ||
| Code Block | ||
| ||
... family f1 time 10:00 # time set free on Sunday. Stays free until re-queuethe sunday task t1 day monday # runs Monday an midnight and Monday at 10.00 |
Hence in ecflow 5.0, in the following definition, the task will never run:
...
Monday@00:00 and Monday@10.00 |