Opened 12 years ago
Last modified 8 years ago
#2599 new defect
Handling of (tuple) = f(...) when solving non-linear — at Initial Version
| Reported by: | Willi Braun | Owned by: | probably noone |
|---|---|---|---|
| Priority: | high | Milestone: | Future |
| Component: | Backend | Version: | trunk |
| Keywords: | Cc: |
Description
Examples like following were handled wrong in SimCodeUtil:
model TupleNonLinear
function ftest
input Real a;
output Real b;
output Integer c;
algorithm
b := 0;
for i in {1} loop //prevent inlining
b := b + sin(a);
c := i;
end for;
end ftest;
Real a;
Integer c;
Real x;
equation
der(x) = a;
(x,c) = ftest(a);
end TupleNonLinear;
We try to solve the equation
(x,c) = ftest(a) non-linear for
{a,c} but actually only a should be solved
non-linear and c can be calculated then directly.
Note:
See TracTickets
for help on using tickets.
