[kepler-users] internally connect actor

Christopher Brooks cxh at eecs.berkeley.edu
Tue Jul 14 08:26:40 PDT 2009


Hi Bertram,
I think Man-Kit took the approach of dragging in attributes that
contain solvers and analyzers that do the right thing.

I think a model can really have only one active director.  One
may drag in multiple directors, but only the last directory is
active.

_Christopher

Bertram Ludaescher wrote:
> Hi Chris (and Christopher):
> 
> Just a philosophical question: wouldn't it be more a director-level
> component that would deal with "global" properties of a workflow/model? In
> my mind, actors are those selfish little guys who don't care about the rest
> of the world: just what the read, compute,  and what they write. Never mind
> the predecessor, successor actors ...
> (of course I understand that at the implementation level, they might "know"
> much more)
> 
> Having said that, attaching the code (or hooks for it) for semantic type
> checking etc. to the actor itself also seems quite neat, as it allows a more
> object-centric, localized control, where each actor can "say" how much it
> "likes" the connections being made to/from it...
> 
> interesting..
> 
> Bertram
> 
> 
> On Tue, Jul 14, 2009 at 7:51 AM, Christopher Brooks
> <cxh at eecs.berkeley.edu>wrote:
> 
>> Hi Chris,
>> Take a look at some of the higher order component actors
>> in ptolemy/actor/lib/hoc.
>>
>> ApplyFunction.java is a good place to start.
>> MultiInstanceComposite is another one.
>>
>> See also ptolemy/domains/ddf/lib/ActorRecursion.java
>>
>> See also Edward's curriculum demo in Ptolemy II
>> ptII/ptolemy/domains/curriculum/demo/Curriculum/Curriculum.xml
>>
>> Man-Kit Leung and people from Bosch are doing something somewhat
>> similar with Properties, see the ptolemy/data/properties work.
>>
>>
>>
>> Chris Weed wrote:
>>
>>> Hi,
>>> I would like to create an actor that when connected to other actors
>>> will inspect the actors it is connected to and show the user the set
>>> of actors that could fulfill this connection based on the Semantic
>>> info.
>>> The user would be able to select from this set, and the actor would be
>>> internally created in my connector actor and connected to the ports.
>>> Is there an example of an actor that does this internal construction
>>> and connection of actor ports?
>>>
>>> Thanks,
>>> Chris
>>> _______________________________________________
>>> Kepler-users mailing list
>>> Kepler-users at kepler-project.org
>>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users
>>>
>> --
>> Christopher Brooks (cxh at eecs berkeley edu) 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 (W-F) 510.655.5480
>>
>> _______________________________________________
>> Kepler-users mailing list
>> Kepler-users at kepler-project.org
>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users
>>
> 

-- 
Christopher Brooks (cxh at eecs berkeley edu) 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 (W-F) 510.655.5480



More information about the Kepler-users mailing list