[kepler-dev] [Bug 3985] - Types resolved to unacceptable types

bugzilla-daemon at ecoinformatics.org bugzilla-daemon at ecoinformatics.org
Tue May 5 09:50:05 PDT 2009


http://bugzilla.ecoinformatics.org/show_bug.cgi?id=3985





------- Comment #3 from soong at nceas.ucsb.edu  2009-05-05 09:50 -------
It seems like the error is thrown before R even runs, in which case it probably
wouldn't be a problem with R itself.  R does have its own types, which the R
actor converts to Ptolemy types.  Since the Expression actor also works with
undeclared types, there is something in particular about the R actor that the
type resolution code doesn't seem to like.  Although explicitly specifying the
type will work, it's clearly not necessary from a user's perspective (why do
Expressions work but RExpressions not) and it imposes constraints on the code
users are able to run.  This problem doesn't happen every time two R actors are
connected, either.  I might be able to help more if I knew more about unknown
<= unknown, since presumably type = type is allowable.

In playing around a little more, if I set the two port types to int, run the
workflow, then set the port types to be blank (unknown?) and change the code to
be irisdf <- "1", the token will be converted to a number on output.  Setting
the output port explicitly to a string will cause another type error that
claims the input port is an int type.  Ke/Pt is throwing an exception based on
outdated information on undeclared types, which is also what the workaround in
comment 1 relies upon.


More information about the Kepler-dev mailing list