[kepler-dev] [Kepler - Bug #6629] (Closed) type resolution problem when using RecordAssembler
noreply at nceas.ucsb.edu
noreply at nceas.ucsb.edu
Tue Feb 3 02:09:08 PST 2015
Issue #6629 has been updated by Marten Lohstroh.
Status changed from New to Closed
Assignee changed from Daniel Crawl to Marten Lohstroh
% Done changed from 0 to 100
The arbitrary order in which Mogensen's algorithm resolves type constraints seemed to trigger non-deterministic type errors due to an error in ParseTreeTypeInference.visitMethodCallNode(). Changes were made in revision 71540 and the supplied model now runs without errors.
----------------------------------------
Bug #6629: type resolution problem when using RecordAssembler
https://projects.ecoinformatics.org/ecoinfo/issues/6629#change-21922
* Author: Daniel Crawl
* Status: Closed
* Priority: High
* Assignee: Marten Lohstroh
* Category: actors
* Target version:
* Bugzilla-Id:
----------------------------------------
Using RecordAssembler can cause type resolution to fail. Attached are two models that demonstrate the problem.
In rec-assembler-1.xml, a type resolution error will usually, but not always, occur when you run it.
In rec-assembler-2.xml, the second RecordAssembler actor is replaced with an Expression actor that constructs the same record, and no type resolution error occurs.
--
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: https://projects.ecoinformatics.org/ecoinfo/my/account
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nceas.ucsb.edu/kepler/pipermail/kepler-dev/attachments/20150203/53f4c59a/attachment.html>
More information about the Kepler-dev
mailing list