[kepler-dev] SampleDelay Actor Query

subhav mital mital.subhav at gmail.com
Thu Apr 22 08:54:11 PDT 2010


Hi Edward,

This looks great! Thanks for this.
However, is the FSMActor or the ModalModel actor available in the repository
for use?

As shown in the demo here:
http://ptolemy.eecs.berkeley.edu/ptolemyII/ptII8.0/jnlp-books/doc/books/design/modal/BasicFSM.swf

Or would this be applicable to any actor to be modeled as a FSM?

Thanks.



On Thu, Apr 22, 2010 at 12:16 AM, Edward A. Lee <eal at eecs.berkeley.edu>wrote:

>
> I would use a ModalModel.
> See:
>
> http://www.eecs.berkeley.edu/Pubs/TechRpts/2009/EECS-2009-151.html
>
> Edward
>
>
>
> On 4/21/10 2:59 PM, subhav mital wrote:
>
>> Hi,
>>
>> Just wondering if any one has any idea on how to proceed or has
>> implemented anything similar? Just a conditional branching execution,
>> but in this case, both the conditions get executed despite having
>> enforced a condition.
>>
>> Would be glad to know your thoughts/suggestions.
>>
>> Thanks.
>>
>>
>> On Tue, Apr 20, 2010 at 7:47 PM, subhav mital <mital.subhav at gmail.com
>> <mailto:mital.subhav at gmail.com>> wrote:
>>
>>    Hi,
>>
>>    Please find attached my workflow is currently giving some errors
>>    which I am unable to ascertain why
>>    ?
>>
>>    I wish to simulate the following:
>>
>>    Move from Stage 0 to Stage 1. At the end of Stage 1, it must prompt
>>    the user with an option to either execute Stage 2 (the next stage)
>>    or execute the previous stage (Stage 0) again.
>>
>>    Is there any way to do this? (Would be glad to know) As of now, both
>>    sides of the branches get executed, despite putting the condition
>>    for each branch. (i.e input==1 perform xyz else perform abc if
>>    input==0).
>>
>>    I have tried all actors and directors but get some error. Would be
>>    glad if someone can help in this and suggest ways to proceed?
>>
>>
>>    Thanks.
>>
>>
>>    On Mon, Apr 5, 2010 at 3:39 AM, Jianwu Wang <jianwu at sdsc.edu
>>    <mailto:jianwu at sdsc.edu>> wrote:
>>
>>        Hi Subhav,
>>
>>             I'm not familiar with Sample Delay Actor. Maybe some one
>>        else can help.
>>
>>             About yhour workflow pausing until some condition is met.
>>        It seems to me that you can use 'Boolean Switch' to do it. Let
>>        the false branch be connected to its input, so that the 'Boolean
>>        Switch' actor will wait for another condition if the current
>>        condition is false. The true branch will be connected to the
>>        sub-workflow you want to execute.
>>
>>             I attached a sample workflow using 'Boolean Switch' and
>>        'Interactive Shell' actor. Yet one weird phenomena of its
>>        execution is that the output is according to the previous input
>>        in 'Interactive Shell', not the current one. I'll keep digging it.
>>
>>        Best wishes
>>
>>        Sincerely yours
>>
>>        Jianwu Wang
>>        jianwu at sdsc.edu  <mailto:jianwu at sdsc.edu>
>>
>>        http://users.sdsc.edu/~jianwu/
>>
>>        Scientific Workflow Automation Technologies (SWAT) Laboratory
>>        San Diego Supercomputer Center
>>        University of California, San Diego
>>        San Diego, CA, U.S.A.
>>
>>
>>        On 4/4/2010 5:15 PM, subhav mital wrote:
>>
>>>        Alternatively, is there any actor that "pauses" the workflow
>>>        until some condition is met?
>>>
>>>        ie. Similar to a flag value which upon getting reset (0),
>>>        halts the workflow and upon getting set (1) resumes the workflow.
>>>
>>>        Thanks.
>>>
>>>
>>>        On Sun, Apr 4, 2010 at 8:09 PM, subhav mital
>>>        <mital.subhav at gmail.com <mailto:mital.subhav at gmail.com>> wrote:
>>>
>>>            Hi,
>>>
>>>            I wish to use the Sample Delay Actor but am confused how
>>>            is it used to resolve deadlocks? Please let me know if
>>>            there is any sample demo of this?
>>>
>>>            Moreover, the documentation of interactive shell actor
>>>            states: "The actor is typically preceded by a SampleDelay
>>>            actor, which provides an initial welcome message or
>>>            instructions"
>>>
>>>            Any explanation on how to incorporate these welcome messages?
>>>
>>>            Thanks...
>>>
>>>
>>>
>>>        _______________________________________________
>>>        Kepler-dev mailing list
>>>        Kepler-dev at kepler-project.org
>>>        <mailto:Kepler-dev at kepler-project.org>
>>>
>>>        http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Kepler-dev mailing list
>> Kepler-dev at kepler-project.org
>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mercury.nceas.ucsb.edu/kepler/pipermail/kepler-dev/attachments/20100422/b1f9895b/attachment.html>


More information about the Kepler-dev mailing list