[kepler-dev] [Ptolemy] Re: DDFSingleTokenCommuntator depends on SR

Christopher Brooks cxh at eecs.berkeley.edu
Tue Jan 29 14:37:20 PST 2008

The DDF-SR dependency is gross, so I'm going to fix it right now.
I'd like to see Kepler include SR, but I really understand not
wanting to add yet another director to Kepler.

Kepler should _definitely_ include DDF because DDF models compose
much better than PN models.


Dan wrote:
> Currently we modified the ant build to include both DDF and SR. SR is 
> not set to appear in our director list, but it can be added. We are 
> using the ptII tagged version and not removing sr.

Steve wrote:

    If you have a work product which may be updated in response to any one
    of a number of dependancies being updated, (think 'make' semantics) then
    SR is likely better than DDF.  In strict DDF, you would end up
    hardcoding the ways in which the dependancies can affect eachother into
    every actor, which is probably bad.  An alternative would be to have a
    slightly different version of DDF where actors can check for the
    presence of data on inputs e.g. "DDF with peek".  SR is deterministic,
    whereas DDF with peek can be nondeterministic if you're not careful.
    > -----Original Message-----
    > From: ptolemy-admin at chess.eecs.berkeley.edu
    [mailto:ptolemy-admin at chess.eecs.berkeley.edu] On Behalf
    > Of Matthew Jones
    > Sent: Tuesday, January 29, 2008 12:54 PM
    > To: Christopher Brooks
    > Cc: kepler-dev at ecoinformatics.org; ptresearch at chess.eecs.berkeley.edu
    > Subject: [Ptolemy] Re: [kepler-dev] DDFSingleTokenCommuntator depends
    on SR
    > I think shipping DDF is very much needed for Kepler.
    > I'm happy to ship SR with Kepler if it is needed to ship DDF.
    > What is the use case for shipping SR for scientific workflows in the
    > absence of DDF depending on it?  I'm sorry I'm not familiar with the
    > computational model.  Could someone explain how it might be useful in
    > scientific analysis by an ecologist or other natural scientist?
    > for the tutorial, or a pointer.
    > Matt
    > Christopher Brooks wrote:
    > > DDFSingleTokenCommutator depends on sr.lib.SingleTokenCommutator.
    > >
    > > This means that Kepler, which uses DDF, must also ship SR.
    > >
    > > Personally, I'd like to see Kepler include the SR director.
    > >
    > > However, this dependency DDF-SR is _really_ wrong, since it
    > > means that we can't deploy a DDF only interpreted ptolemy system
    > > without including SR.  In general, domains should be standalone.
    > >
    > > I'm thinking of moving sr.lib.SingleTokenCommutator to
    > > actor.lib and then adding some code that would indicate that the
    > > actor is not safe for use within SDF.
    > >
    > > _Christopher
    > >
    > > _______________________________________________
    > > Kepler-dev mailing list
    > > Kepler-dev at ecoinformatics.org
    > >
    > >
    > --
    > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    > Matthew B. Jones
    > Director of Informatics Research and Development
    > National Center for Ecological Analysis and Synthesis (NCEAS)
    > UC Santa Barbara
    > jones at nceas.ucsb.edu                       Ph: 1-907-523-1960
    > http://www.nceas.ucsb.edu/ecoinfo
    > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    > _______________________________________________
    > Ptolemy maillist  -  Ptolemy at chess.eecs.berkeley.edu
    > http://chess.eecs.berkeley.edu/ptolemy/listinfo/ptolemy
    Ptolemy maillist  -  Ptolemy at chess.eecs.berkeley.edu

More information about the Kepler-dev mailing list