ecFlow's documentation is now on readthedocs!

Please go to https://ecflow.readthedocs.io/en/latest/index.html

  • Created by Unknown User (ma0), last modified on Jul 29, 2020

By default when we create an event, its default value is unset(i.e. False or clear).

suite test_events
  family family1
     task a
       # initial value is clear(default), 
       # child command is expected to set
       event myEvent     
     task b
       trigger a:myEvent #  or use ( a:myEvent == set)
   endfamily
endsuite

The event is set like:

a.ecf
<head.h>
...
ecflow_client --event=myEvent
...
<tail.h>


However sometimes we want to invert the event, we want to default value to be set, and a child command to clear it.  This capability has been added to ecFlow 5

suite test_events
  family family1
     task a
       # initial value is set, 
       # child command is expected to clear
       event myEvent set       
     task b
       trigger a:myEvent == clear
   endfamily
endsuite

The event is cleared like:

a.ecf
<head.h> 
... 
ecflow_client --event=myEvent clear
...
<tail.h>





1 Comment

  1. Axel Bonet

    ability to set/unset from within a task throughout the process life can lead to

    difficulty to understand the logic in a suite (suite behaviourflow difficult to simulate)


    there is memory of this pattern already used in a "very creative" way in the past

    while it could be done so far with alter


    good luck.