[kepler-dev] DDFSingleTokenCommuntator depends on SR

[Dan Higgins]

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.

Dan

Matthew Jones wrote:
> 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
>>
>>     
>
>   


-- 
*******************************************************************
Dan Higgins                                  higgins at nceas.ucsb.edu
http://www.nceas.ucsb.edu/    Ph: 805-893-5127
National Center for Ecological Analysis and Synthesis (NCEAS) Marine Science Building - Room 3405
Santa Barbara, CA 93195
*******************************************************************