...
In ecflow 4.0 the definition below can produce unexpected runs.
ecflow 4.0 each time attributes is treated individually.
Here time was set free on Sunday.
Code Block | ||
---|---|---|
| ||
...
family f1
day monday
task t1
time 10:00 # runs Monday@00:00 and Monday@10.00 |
Code Block |
---|
...
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
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.)
|
---|
...