Sometimes a task
should not be run when a certain condition is met.
The condition can be signalled by an event. For example, event t2:b
might indicate that task t2 did not manage to produce expected result, so
we do not need to run task t4.
This has a similar syntax to the trigger
keyword but sets a task
complete expression evaluation takes precedence over the trigger.
Completes can be between tasks, between families, or both.
It can be used in conjunction with a trigger
. For example:
# Definition of the suite test.
edit ECF_INCLUDE "$HOME/course" # replace '$HOME' with the path to your home directory
edit ECF_HOME "$HOME/course"
edit SLEEP 20
trigger t1 eq complete # task t2 will only start when task t1 is complete
event a # task t2 will set an event a
event b # task t2 will set an event b
trigger t2:a # task t3 will start when event a is set in task t2
trigger t2 eq complete # task t4 will start when task t2 is complete
complete t2:b # task t4 will complete if event b is set in task t2
from ecflow import Defs,Suite,Family,Task,Edit,Trigger,Complete,Event
Trigger("t1 == complete"),
Trigger("t2 == complete"),
print("Creating suite definition")
home = os.path.join(os.getenv("HOME"), "course")
defs = Defs(
print("Checking job creation: .ecf -> .job0")
print("Saving definition to file 'test.def'")
What to do
- Update test.def or test.py to add a complete expression to task t4
- Replace the suite
python: python test.py ; python client.py
text: ecflow_client --suspend=/test ; ecflow_client --replace=/test test.def
- Observe the tasks in ecflow_ui
- See the triggers by selecting t4
- See the trigger relation by clicking on the arrow
- See the triggers in the tree, using the Show menu
- Note the icon indicating that the task has not run
- To check the triggers modify task t2 so that event b is not triggered; task t4 should run when t2 completes.