[kepler-dev] Best practice for custom actor development

Edward A. Lee eal at eecs.berkeley.edu
Wed Aug 15 12:55:33 PDT 2007


I'm not sure how to set up the actor for use in Kepler,
but in Ptolemy, you don't need to recompile everything.
You can create a subclass of ptolemy.actor.TypedAtomicActor,
(to compile this, you need to specify to the compiler
to reference a Ptolemy jar file or classpath root).
Then when you start vergil (the UI), you can load this
actor as long as it is in the classpath... (you can specify
the classpath on the command line, if you want to put the
actor in some arbitrary place). To load it,
go to the Graph menu, and select Instantiate Entity.
Then just specify the full class name, relative to the
classpath.

Edward

At 09:38 AM 8/15/2007, ian.brown at hsbcib.com wrote:
>Hi Ilkay,
>      I had seen that link in my browsing but I was hoping there would be a
>way to create an actor without having to compile the entire system from
>scratch. The link implies that I need to set up a development environment
>for both ptolemy and kepler and compile both from cvs. That's quite a lot
>of work to add a block.
>
>At the moment I am trying to understand the differences between kepler and
>ptolemy and from that hoping to decide which is better suited. I am
>favouring kepler at the moment because it seems better integrated with R
>and MATLAB and that's what our analysts use. Looking at the integration of
>these though, it would be reasonably trivial to achieve the same
>integration in ptolemy.
>
>Is Kepler an extension to Ptolemy or is it a variant. In other words, if I
>chose Kepler do I sacrifice some options or functionality that are present
>in Ptolemy and if so, what are thet?
>Would the best route for me be to first generate the Actor for Ptolemy and
>then migrate it to Kepler - I think I read somewhere that I could use
>Ptolemy actors in Kepler.
>
>Thanks for you time,
>
>Ian
>
>************************************************************
>HSBC Bank plc may be solicited in the course of its placement efforts for a
>new issue, by investment clients of the firm for whom the Bank as a firm
>already provides other services. It may equally decide to allocate to its
>own proprietary book or with an associate of HSBC Group. This represents a
>potential conflict of interest. HSBC Bank plc has internal arrangements
>designed to ensure that the firm would give unbiased and full advice to the
>corporate finance client about the valuation and pricing of the offering as
>well as internal systems, controls and procedures to identify and manage
>conflicts of interest.
>
>HSBC Bank plc
>Registered Office: 8 Canada Square, London E14 5HQ, United Kingdom
>Registered in England - Number 14259
>Authorised and regulated by the Financial Services Authority.
>************************************************************
>
>-----------------------------------------
>SAVE PAPER - THINK BEFORE YOU PRINT!
>
>This transmission has been issued by a member of the HSBC Group
>"HSBC" for the information of the addressee only and should not be
>reproduced and/or distributed to any other person. Each page
>attached hereto must be read in conjunction with any disclaimer
>which forms part of it. Unless otherwise stated, this transmission
>is neither an offer nor the solicitation of an offer to sell or
>purchase any investment. Its contents are based on information
>obtained from sources believed to be reliable but HSBC makes no
>representation and accepts no responsibility or liability as to its
>completeness or accuracy.
>_______________________________________________
>Kepler-dev mailing list
>Kepler-dev at ecoinformatics.org
>http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-dev

------------ 
Edward A. Lee
Chair of EECS and Robert S. Pepper Distinguished Professor
231 Cory Hall, UC Berkeley, Berkeley, CA 94720-1770
phone: 510-642-0253, fax: 510-642-2845
eal at eecs.Berkeley.EDU, http://ptolemy.eecs.berkeley.edu/~eal  



More information about the Kepler-dev mailing list