[kepler-dev] DDFSingleTokenCommuntator depends on SR

[Matthew Jones]

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 SR 
computational model.  Could someone explain how it might be useful in a 
scientific analysis by an ecologist or other natural scientist?  Thanks 
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
> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-dev
> 

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~