Opened 11 years ago
Closed 4 years ago
#2488 closed defect (invalid)
noEvent doesnt work correctly
Reported by: | Owned by: | somebody | |
---|---|---|---|
Priority: | high | Milestone: | Future |
Component: | Frontend | Version: | trunk |
Keywords: | Cc: |
Description
Hello,
I am using the nightly build from 20.11.2013.
In one of my models I am using the noEvent-operator, but it doesnt work correctly.
I reduced the model to a minimal and the error still apear.
The variable should be either s or Smax, depending on the movement of s.
If s should be smaller then a previous smax should hold on the maximum.
Find the model attached
Attachments (2)
Change History (12)
by , 11 years ago
Attachment: | testcase.mo added |
---|
by , 11 years ago
comment:1 by , 11 years ago
Component: | OMEdit → Frontend |
---|---|
Owner: | changed from | to
comment:2 by , 10 years ago
Milestone: | 1.9.1 → 1.9.2 |
---|
This ticket was not closed for 1.9.1, which has now been released. It was batch modified for milestone 1.9.2 (but maybe an empty milestone was more appropriate; feel free to change it).
comment:3 by , 10 years ago
Milestone: | 1.9.2 → 1.9.3 |
---|
Milestone changed to 1.9.3 since 1.9.2 was released.
comment:8 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:9 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.
comment:10 by , 4 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Closed due to lack of feedback.
Could you please elaborate on what isn't working correctly? max/min does not generate events, so noEvent has no effect in your example and is optimized away by the compiler.
Edit: Removed wrong analysis, I didn't realise that the test model was just supposed to be part of testcase.