[kepler-dev] [Bug 2050] - EMLDataSource output as Ptolemy records

Shawn Bowers sbowers at ucdavis.edu
Thu Apr 7 09:39:04 PDT 2005

bugzilla-daemon at ecoinformatics.org wrote:
> http://bugzilla.ecoinformatics.org/show_bug.cgi?id=2050
> ------- Additional Comments From sbowers at ucdavis.edu  2005-04-07 09:33 -------
> I don't think it is correct to have one port per attribute.  This approach
> looses the information that the ports are actually dependent.  This assumes a
> particular domain functionality (i.e., that the director knows the dependency);
> but the constraint cannot be captured in Ptolemy's constraint language.  
>>From a modeling perspective, it is more appropriate in Ptolemy to use a single
> port that outputs a tuple (i.e., a record). Of course, one could always connect
> an array deconstructor after the data set if desired. This approach (of

Sorry: I mean "record dissasembler" not array deconstructor :-)

> outputing tuples instead of individual values) follows more closely the standard
> approach used in database systems and makes collection-oriented
> dataflows/programming much easier.
> _______________________________________________
> Kepler-dev mailing list
> Kepler-dev at ecoinformatics.org
> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-dev

More information about the Kepler-dev mailing list