[kepler-dev] Running multiple Kepler models programmatically

[Christopher Brooks]

BTW - 

My understanding is that currently kepler can only run one invocation
of Kepler per user because of issues with ~/.kepler and the database.
See

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=2315

_Christopher
Edward wrote:
--------

    
    Paul,
    
    You may want to take a look at the contents of $PTII/demo.
    
    In that directory, there are some Ptolemy II models that execute other
    models, in their own threads, sequentially, or in their own JVM.
    
    Edward
    
    At 09:04 AM 2/27/2008, Paul Allen wrote:
    >I wanted to get some advice from the Kepler architects about the best 
    >approach for running multiple Kepler models programmatically, using 
    >something like ptolemy.actor.gui.MoMLSimpleApplication. I'm creating a 
    >generic workflow engine service to run models (without GUI) and need to 
    >know whether I should run each model in it's own JVM or whether I can 
    >just use a separate thread for each model, while using the same JVM. I 
    >think that the multiple thread approach would be easier to deal with, 
    >but I'm getting some indications that models running in the same JVM 
    >aren't entirely separate, even when I try to give them different 
    >workspaces to use.
    >
    >- Paul
    >
    >
    >_______________________________________________
    >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://www.eecs.berkeley.edu/Faculty/Homepages/lee.h
   tml  
    
    _______________________________________________
    Kepler-dev mailing list
    Kepler-dev at ecoinformatics.org
    http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-dev
--------