[kepler-dev] Query on kepler command

[Christopher Brooks]

There is not much difference in the execution.  The difference is in the 
look and feel.

ptolemy.moml.MoMLCommandLineApplication extends 
ptolemy.moml.MoMLSimpleApplication.

See 
http://sisyphus.eecs.berkeley.edu:8079/hudson/job/ptII/javadoc/ptolemy/moml/MoMLCommandLineApplication.html

org.kepler.KeplerConfiguration extends ptolemy.actor.gui.Configuration 
and uses Ptolemy configurations to define what actors are available in a 
UI and the look and feel of the run control panel.
See 
http://sisyphus.eecs.berkeley.edu:8079/hudson/job/kepler/javadoc/org/kepler/KeplerConfigurationApplication.html

So, the two classes have different parent class hierarchies.

MoMLCommandLineApplication is better for non-graphical models, 
KeplerConfiguration is better for graphical applications.

For information about invoking Ptolemy and configurations, see 
http://ptolemy.eecs.berkeley.edu/ptolemyII/ptIIfaq.htm#invoking%20Ptolemy%20II?

_Christopher.

On 4/25/13 12:51 AM, Yogini Joshi wrote:
>
> Hi,
>
> My existing project is using below command ,
>
> Kepler -runwf -nogui -redirectgui dir -nocache -noilwc   workflow.xml
>
> Which initializes  "ptolemy.moml.MoMLCommandLineApplication" . 
> Therefore the call is blocking means it will return only when workflow 
> execution is finished.
>
> However if I change the command with no cache as below,
>
> Kepler -runwf -nogui -redirectgui dir  -noilwc   workflow.xml
>
> It will call "org.kepler.KeplerConfigurationApplication". This is non 
> blocking as it will spawn new thread for each model and return.
>
> My query if I choose second approach ie using 
>  org.kepler.KeplerConfigurationApplication instance, then is there any 
> difference in the workflow execution behavior. If so can you please 
> describe in detail the difference in both these flows.
>
> Regards,
>
> Yogini
>
> DISCLAIMER ========== This e-mail may contain privileged and 
> confidential information which is the property of Persistent Systems 
> Ltd. It is intended only for the use of the individual or entity to 
> which it is addressed. If you are not the intended recipient, you are 
> not authorized to read, retain, copy, print, distribute or use this 
> message. If you have received this communication in error, please 
> notify the sender and delete all copies of this message. Persistent 
> Systems Ltd. does not accept any liability for virus infected mails.
>
>
>
> _______________________________________________
> Kepler-dev mailing list
> Kepler-dev at kepler-project.org
> http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev

-- 
Christopher Brooks, PMP                       University of California
Academic Program Manager & Software Engineer  US Mail: 337 Cory Hall
CHESS/iCyPhy/Ptolemy/TerraSwarm               Berkeley, CA 94720-1774
cxh at eecs.berkeley.edu, 707.332.0670           (Office: 545Q Cory)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nceas.ucsb.edu/kepler/pipermail/kepler-dev/attachments/20130425/33024332/attachment.html>