[kepler-dev] Stopping a workflow

Norbert Podhorszki pnorbert at cs.ucdavis.edu
Mon Jun 5 15:57:35 PDT 2006


I am looking for an idea about how to stop a (pipeline dataflow) worfklow, 
which runs arbitrarily long but should finish if a certain condition 
holds. Not just stopping immediately: the work inside the pipeline should 
be performed to the end of the pipeline, but no more work should be 
generated at the front.

In the infinitely running workflow, a Ramp generates the tokens on the 
front. If a parameter is put into the firingCountLimit, which is 
originally 0 and is set to e.g. 1 when the condition occurs, the Ramp will 
stop so this is a nearly perfect solution for the above problem. However, 
the parameter remains set to 1 for future runs (i.e. not running long) and 
I do not know, how to set it back (either at the end of this run, or at 
the beginning of the next run).

Is there any actor that generates tokens UNTIL it receives a token 

Note: I would not like to mess up my beautiful straight dataflow pipeline 
with an ugly controlflow construct :-(

Many thanks


      Norbert Podhorszki
      University of California, Davis
      Department of Computer Science
      1 Shields Ave, 2236 Kemper Hall
      Davis, CA 95616
      (530) 754-8188
      pnorbert at cs.ucdavis.edu

More information about the Kepler-dev mailing list