[kepler-users] Kepler Question

ted leslie tleslie at tcn.net
Thu Oct 2 02:23:55 PDT 2008


On Thu, 2 Oct 2008 05:07:05 -0400
ted leslie <tleslie at tcn.net> wrote:

> 
> Ah, composite actor did the trick in so far as putting that WF in another,
> i see it can inherit the directory (as I did in my experimenting and checking docs),
> but I notice it doesn't "fire" when you run the main work flow. 
> (it has its own controls). It would be nice if when I run the outer WF, that
> the composite ones run too. Probably I am missing something simple?

Got it, never mind. Time for me to dive it deep now :) 


> 
> -tl
> 
> On Thu, 2 Oct 2008 01:36:21 -0700
> "Bertram Ludaescher" <ludaesch at ucdavis.edu> wrote:
> 
> > On Thu, Oct 2, 2008 at 1:27 AM, ted leslie <tleslie at tcn.net> wrote:
> > 
> > >
> > > I just stumpled upon Kepler and am absolutly blown away!
> > >
> > > I think it will be very useful for me,
> > > but one requirement that I would have is,
> > >
> > > Can I have workflows interact?
> > > Can one trigger another, or start it up?
> > > Can they communicate to one another?
> > > (maybe even a WF run within a WF?, import a WF as a data provider to
> > > another WF?)
> > 
> > 
> > There are several answers to this: First, a workflow running within a
> > workflow is called a "composite actor" or "subworkflow" in our terminology.
> > When one nests a wf inside another one, the question arises: how should this
> > be executed? What's the model of computation. Thanks to Ptolemy's various
> > underlying models of computation, we can use in Kepler different ways of
> > nesting workflows inside one another, all with clear semantics (there are
> > papers and documentation describing how this works).
> > 
> > Having said this, we normally don't think of multiple instances of workflows
> > as running indepdently and then somehow communicating. Although such a thing
> > is possible (e.g. this *might* be related somewhat to Ptolemy's life cycle
> > models, where one model (aka workflow in Kepler lingo) can start another
> > one), we rather think of workflows typically as data-driven analysis
> > pipelines (dataflow process networks).
> > 
> > >
> > > Also, I use Linux exclusively, but to avoid Java installs and other prereq.
> > > I just put it into a Windows OS on vmware, to give it a quick look.
> > > Is the Linux version as full featured as the Windows? (or fuller, or
> > > lessor?)
> > > (If not what are diffs?)
> > >
> > 
> > I'm not aware of a difference. And you can always get the latest version via
> > the source code repository.
> > 
> > 
> > >
> > > These might be very noob questions, and I don't mind  "RTFM",
> > > but these are fundimental Q's I would appreacate brief feed back on,
> > > (or reference pointers)
> > > before I take a much deeper dive in.
> > >
> > 
> > Here is a good starting point:
> > http://www.kepler-project.org/Wiki.jsp?page=Documentation
> > 
> > Bertram
> > 
> > 
> > >
> > > Thanks,
> > >
> > >
> > > --
> > > ted leslie <tleslie at tcn.net>
> > > _______________________________________________
> > > Kepler-users mailing list
> > > Kepler-users at ecoinformatics.org
> > > http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-users
> > >
> > >
> > 
> 
> 
> -- 
> ted leslie <tleslie at tcn.net>
> _______________________________________________
> Kepler-users mailing list
> Kepler-users at ecoinformatics.org
> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-users
> 


-- 
ted leslie <tleslie at tcn.net>


More information about the Kepler-users mailing list