Opened 9 years ago
Last modified 7 years ago
#3849 accepted defect
Wrong constant evaluation of final parameter arrays in the back-end
| Reported by: | Adrian Pop | Owned by: | Adrian Pop |
|---|---|---|---|
| Priority: | high | Milestone: | Future |
| Component: | Backend | Version: | |
| Keywords: | Cc: |
Description
I have a non-public wind power model that sends an array of zeros to a function instead the of the correct array. The model works with +d=evalparam which forces the evaluation in the front-end.
I'm opening this bug so we don't forget about it.
Change History (8)
comment:1 by , 9 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → accepted |
comment:2 by , 9 years ago
comment:3 by , 9 years ago
I tried to make a smaller model and it worked fine. I'm running the debugger on it now to see if I can find the error quickly.
comment:4 by , 9 years ago
I found the issue, the Ceval.ceval we do in the back-end evaluates to wrong results for some weird models. I think I can make a smaller model now. I think we should not use Ceval.ceval in the back-end at all as is not needed, all the things we need are in the DAE already.
comment:5 by , 9 years ago
Also, -d=-backendKeepEnv helps to not ceval bad things in the backend. But some optimizations fail with that flag.
comment:7 by , 8 years ago
| Milestone: | 1.11.0 → 1.12.0 |
|---|
Milestone moved to 1.12.0 due to 1.11.0 already being released.
comment:8 by , 7 years ago
| Milestone: | 1.12.0 → Future |
|---|
The milestone of this ticket has been reassigned to "Future".
If you think the issue is still valid and relevant for you, please select milestone 1.13.0 for back-end, code generation and run-time issues, or 2.0.0 for front-end issues.
If you are aware that the problem is no longer present, please select the milestone corresponding to the version of OMC you used to check that, and set the status to "worksforme".
In both cases, a short informative comment would be welcome.
Can you reproduce the issue with a smaller model?