[kepler-dev] To know the end of an actor

[Ivens]

Hi Marcin,

The Display thing was an example.
My problem occurs with any actor that doesn't have output ports.

In a Composite actor there is 3 actors:
Actor1 (developed by me)
Actor2 (developed by me)
and a third actor (that can be any of the Kepler's native actors)

The problem is that Actor2 must execute after the "main" actor.
It works well, when the "main" actor has input and ouput ports, because i
can connect the Actor2 after the "main" actor.

But with Display, and other "output port"less actors, things get difficult.

How can Listeners help me?

Thanks
Ivens

On Wed, Aug 25, 2010 at 11:14 AM, Marcin Plociennik
<marcinp at man.poznan.pl>wrote:

>
> Hi Ivens,
> Multidisplay that is extension of Display works both with Kepler 1.0 and
> 2.0, so shoudn't be a problem in using it.
>
> regards
> marcin
>
>
> Ivens wrote:
>
>> Michal,
>>
>> Thank you for your help, but i am developing a work that needs Kepler1.0.
>> I think i have a heading after the "listener thing".
>>
>> Well,
>> which of the listeners knows about the end of the execution of an actor in
>> the model?
>> ChangeListener
>> DebugListener
>> ExecutionListener
>> ?
>>
>> Thanks
>> Ivens
>>
>>
>> 2010/8/25 Michal Owsiak <michalo at man.poznan.pl <mailto:
>> michalo at man.poznan.pl>>
>>
>>
>>    We have developed, recently, slightly modified version of Display
>>    that is called MultiDisplay.
>>
>>    It has few advantages over Display:
>>
>>    1. it has output port that produces outputs in case there are
>>    listeners (this solves the issue you are describing)
>>
>>    2. we are using tabs for displaying messages - this solution makes
>>    it possible to collect all messages within single window
>>
>>    If you are interested with that, I can prepare demo workflow for
>>    you (for tomorrow).
>>
>>    Cheers
>>
>>    Michal
>>
>>    --     Michal Owsiak <michal.owsiak at man.poznan.pl
>>    <mailto:michal.owsiak at man.poznan.pl>>
>>
>>
>>    Institute of Bioorganic Chemistry PAS
>>    Poznan Supercomputing and Networking Center
>>    Noskowskiego 12/14, 61-704 Poznan, POLAND
>>
>>    http://www.man.poznan.pl
>>
>>
>>        Christopher,
>>
>>        I have an Actor1 that needs to be executed after Display.
>>        I dont know who will be called first, so, i tried to use
>>        listeners to solve
>>        my problem.
>>
>>        But, i dont know too much of them.
>>        Do you have some examples?
>>
>>        Thanks
>>        Ivens
>>
>>        On Wed, Aug 25, 2010 at 10:39 AM, Christopher Brooks
>>        <cxh at eecs.berkeley.edu <mailto:cxh at eecs.berkeley.edu>>wrote:
>>
>>
>>            Hi Ivens,
>>
>>            Display.wrapup() will be called by the director when the actor
>>            is finished with its execution.
>>            It is possible to register ptolemy.actor.ExectionListeners
>>            with the ptolemy.actor.Manager and listen to the state of
>>            the iteration for the entire model.
>>
>>            You can also add a listener to listen to debug messages, see
>>            ptolemy/vergil/kernel/ListenToAction.java
>>
>>            _Christopher
>>
>>
>>
>>            On 8/25/10 5:39 AM, Ivens wrote:
>>
>>                Hi,
>>
>>                I would like to know if there is a way to detect that
>>                an actor has
>>                finished its execution.
>>                (for example: the actor Diplay... how can I know (in
>>                Java) that this
>>                actor has finished?)
>>                Thanks
>>
>>                Ivens
>>
>>
>>
>>                _______________________________________________
>>                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
>>
>>
>>            --
>>            Christopher Brooks, PMP                       University
>>            of California
>>            CHESS Executive Director                      US Mail: 337
>>            Cory Hall
>>            Programmer/Analyst CHESS/Ptolemy/Trust        Berkeley, CA
>>            94720-1774
>>            ph: 510.643.9841 fax:510.642.2718             (Office:
>>            545Q Cory)
>>            home: (F-Tu) 707.665.0131 cell: 707.332.0670
>>
>>
>>
>>
>>        _______________________________________________
>>        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
>>
>>
>
>
> --
>             Marcin Plociennik
>
> Poznan Supercomputing and Networking Center
>
> 61-704 Poznan, ul. Noskowskiego 10 POLAND
> phone (+48 61) 8582181
> e-mail: marcinp at man.poznan.pl
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mercury.nceas.ucsb.edu/kepler/pipermail/kepler-dev/attachments/20100825/d98b81c7/attachment-0001.html>