[kepler-users] Ecoinformatics CVS account - Kepler

[Dan Higgins]

Hi Ralph,

    As you discovered, the procedure for adding actors to Kepler is 
quite a bit different than for Ptolemy. (And, currently, not easy and 
obvious.)  annotations.owl and ontology.owl are the key files for adding 
to the actor list, but I suspect that your main problem is getting 
Kepler to see the jar file you refer to. All jar files need to added to 
the classpath. If you are running kepler from ant (using 'ant run-dev') 
then placing your jar inside the $Kepler/lib/jar directory should make 
it visible. Then just opening the appropriate workflow (*.xml file) 
should work even if your actor is not present on Kepler's actor list. If 
you use the .bat or .sh files, then your jar file must be explicitly 
added to the classpaths in these files (I don't know what OS or version 
your are using.) If you are using the 1.6alpha installers from the 
Kepler web page, adding to the classpath is tricky and I suggest using 
the .bat or .sh files.

    To add your actor to Keplers list, you can just right click on the 
appropriate caregory in the actor tree and add it by entering the Java 
class name if it is an atomic actor. Currenly, composite actors cannot 
be added this way.

    Hopefully this info helps. If not, feel free to ask more questions.

Dan Higgins
NCEAS


Seguin, Ralph P wrote:

>Hi.
>Thanks for the access.
>I'll get around to checking things out soon, after I get Kepler working with our actors/components.
>Is there a quickstart doc somewhere that describes the process of putting your actors into Kepler?
>
>Also, it looks like the web services actor, the WSDL URL is strictly a static pulldown menu of choices rather than allowing a typein (in addition)
>
>I'm under the gun timewise for a demo, so sorry for the 
>late notice.
>
>I'm having trouble getting something that works in Ptolemy 
>II (4.0.1) to work in Kepler.
>I have a .jar file and some component description files 
>(.xml) that worked fine for Ptolemy II 
>(MyUserLibrary.xml), or through the Graph->ImportLibrary, 
> Graph->Save In Library items.
>
>However, if I do this in Kepler, no go (nothing shows up 
>in the component tree at least).
>I put the .jar file in the right place (I believe).
>
>I've been poking around in the Kepler tree under 
>configs/ptolemy/configs/kepler
>and I was looking at annotations.owl and ontology.owl, and 
>I believe that I could hack these things in by hand, if 
>need be, but I'd prefer to do it right.
>
>Sooo... what is the appropriate means of having your 
>components/actors show up in the Kepler GUI?
>
>Thanks.
>-Ralph
>seguin at lmsal.com
>rpseguin at gmail.com
>408-718-4632
>
>
>-----Original Message-----
>From: Colby Walsworth [mailto:walswort at nceas.ucsb.edu]
>Sent: Thursday, May 12, 2005 5:06 PM
>To: Seguin, Ralph P
>Cc: Matt Jones
>Subject: Ecoinformatics CVS account - Kepler
>
>
>
>Hello Ralph,
>
>We have created a new CVS account on cvs.ecoinformatics.org  for you to
>access and contribute to the latest source code and document
>repositories for the Kepler project.  You will probably want to check
>out the "kepler" module, or possibly the subprojects underneath these
>which might be of more specific interest.  Most files are organized by
>subproject.   You can find information on this project here:
>
>http://kepler.ecoinformatics.org
>
>
>
>Following is some information about your account and CVS:
>
>A. Here is your username and password for your new account:
>username: seguin
>password: 4aoE2Sa
>
>You should log into ecoinformatics.org using a secure shell program
>(ssh)(Only ssh v.2 is supported on this server)and change your password.
>  Once you are logged in you may change your password by typing
>"passwd". It will prompt you for your new password twice. Your password
>should be 6-8 characters with a mix of letters and numbers and should
>not resemble a dictionary word. Also there is a file named ".forward" in
>your home directory that has you email address that all your mail needs
>to be forwarded to. You may edit this if your email address changes.
>
>B. *How to set up CVS under Windows using TortoiseCVS *
>We recommend that you use TortoiseCVS v. 1.4.5 or higher to access CVS
>via Windows.  You will need to run CVS thru SSH version 2.  SSH version
>1 will not work correctly.  TortoiseCVS v.1.4.5 and higher include
>instructions about how to setup SSH version 2 using TortoisePlink.
>An older document that might be of use describes how to generically run
>CVS with SSH--
>http://cvs.ecoinformatics.org/HOWTO-cvs-over-ssh.html
>
>C. *Email lists*
>As part of the Kepler groups, you are enrolled in
>several email lists which will provide notification of repository
>updates, as well as serve as general archived forums for discussion.
>You have been enrolled in these lists:
>
>There is a kepler developemnt email list you may want to check out and
>subscribe to. Here is the list info:
>http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-dev
>
>
>
>Again, welcome to the kepler development project.  If you have any
>questions about using CVS or SSH, or membership on the kepler email lists,
>please send us a note at "help at nceas.ucsb.edu".
>
>Cheers,
>
>  
>