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

bugzilla-daemon@ecoinformatics.org bugzilla-daemon at ecoinformatics.org
Thu Apr 7 09:33:51 PDT 2005


------- 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
outputing tuples instead of individual values) follows more closely the standard
approach used in database systems and makes collection-oriented
dataflows/programming much easier.

More information about the Kepler-dev mailing list