We have learnt from experience that suite designers were using trigger‘s in
two different ways: as data dependency triggers and as courtesy triggers.
The former are for what triggers where designed. The latter are used to prevent too
many jobs running at once and are actually an artificial way of queueing jobs.
Because ECF does not distinguish between the two sorts of triggers, suites can become
difficult to maintain after a while. So the concept of limit was introduced.
Limits are declared with the limit keyword
Let us modify our suite definition file:
# Definition of the suite test.
suite test
edit ECF_INCLUDE "$HOME/course"
edit ECF_HOME "$HOME/course"
limit l1 2
family f1
edit SLEEP 20
task t1
meter progress 1 100 90
task t2
trigger t1 eq complete
event a
event b
task t3
trigger t2:a
task t4
trigger t2 eq complete
complete t2:b
task t5
trigger t1:progress ge 30
task t6
trigger t1:progress ge 60
task t7
trigger t1:progress ge 90
endfamily
family f2
edit SLEEP 20
task t1
time 00:30 23:30 00:30
task t2
day sunday
task t3
date 01.*.*
time 12:00
task t4
time +00:02
task t5
time 00:02
endfamily
family f3
task t1
label info ""
endfamily
family f4
edit SLEEP 2
repeat string NAME a b c d e f
family f5
repeat integer VALUE 1 10
task t1
repeat date DATE 19991230 20000105
label info ""
endfamily
endfamily
family f5
inlimit l1
edit SLEEP 20
task t1
task t2
task t3
task t4
task t5
task t6
task t7
task t8
task t9
endfamily
endsuite
In python this would be:
#!/usr/bin/env python2.5
import os
import ecflow
def create_family_f5() :
f5 = ecflow.Family("f5")
f5.add_inlimit("l1")
f5.add_variable("SLEEP",20)
for i in range(1,10):
f5.add_task( "t" + str(i) )
return f5
defs = ecflow.Defs("test.def")
suite = defs.add_suite("test")
suite.add_variable("ECF_INCLUDE",os.getenv("HOME") + "/course")
suite.add_variable("ECF_HOME ",os.getenv("HOME") + "/course")
suite.add_limit("l1",2)
suite.add_family( create_family_f5() )
What to do:
- Edit the changes
- Play and begin the suite
- In ecFlowview, observe the triggers of the limit l1
- Open the Info panel for l1
- Change the value of the limit
- Open the Why? panel for one of the queued tasks of /test/f5