[kepler-dev] gt, ptera and modal added to kepler configuration

Christopher Brooks cxh at eecs.berkeley.edu
Wed May 13 18:39:48 PDT 2009


I added gt, ptera and modal to the kepler configuration.
gt is the Graph Transformation facility.

ptera is:
"Ptera is a concurrency model that focuses on the events of the system,
rather than the states of the system as in state machines. It's
partially a concurrency model because it can model concurrent systems,
though in its current form, the execution is completely sequential and
deterministic. There also seems to be a duality between the discrete
event model and the Ptera model."

domains.modal is a replacement for domains.fsm.  We will eventually
also replace domains.ct with domains.continuous.

The reason I added these is that there were demos in Kepler that
used these facilities.  However, Kepler might not want gt and ptera.
Kepler will likely want domains.modal.

To check out gt and ptera:
1) Start up Kepler
2) Help -> Documentation
3) Follow the  "Background information on Ptolemy" link
4) Under "Basic Modeling Capabilities", see
Event-Oriented Modeling with Ptera: CarWash with DE, Ptera and FSM (See 
also GameOfLife, TrafficLight). The Ptera (Ptolemy Event Relationship 
Actor) domain is a discrete-event model of computation. A model in Ptera 
is represented with a graph of nodes and edges, where nodes represent 
events and directed edges between events represent scheduling relation. 
One or more events can be selected as initial events, which are 
scheduled at model time 0.0. When an event is fired, it possibly 
performs certain actions, and if there are outgoing edges from that 
event, the events at the end points of those edges are scheduled after 
non-negative delays. One or more events can also be selected as final 
events. The firing of final events causes the event queue to be emptied 
after their actions are performed, and therefore no more events can be 
processed.


I think GT and Ptera could be very useful for workflow builders.

However, I'm more than willing to remove them if the consensus is that
adding these to the Kepler UI makes life too complicated.

_Christopher

-- 
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-dev mailing list