#3759 closed defect (fixed)
[Clock] time values are not strict monotonically increasing
Reported by: | Lennart Ochel | Owned by: | Lennart Ochel |
---|---|---|---|
Priority: | high | Milestone: | 1.19.0 |
Component: | Run-time | Version: | |
Keywords: | Cc: | Bernhard Thiele |
Description
The following simple test case produces a result file with time values that are not strict monotonically increasing.
setCommandLineOptions("+std=3.3"); getErrorString(); loadString(" model TestClock Integer nextInterval(start=1); Clock c = Clock(nextInterval, 10); equation when c then nextInterval = previous(nextInterval) + 1; end when; end TestClock; "); getErrorString(); simulate(TestClock, outputFormat="csv"); getErrorString();
Change History (8)
comment:1 by , 9 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:2 by , 9 years ago
Milestone: | 1.9.5 → 1.10.0 |
---|
comment:4 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:5 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:6 by , 7 years ago
Cc: | added |
---|---|
Summary: | time values are not strict monotonically increasing → [Clock] time values are not strict monotonically increasing |
This issue still remains in the master. 0.096, 0.098, 1.0, 1.0, 0.098
comment:7 by , 3 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:8 by , 3 years ago
Milestone: | Future → 1.19.0 |
---|
Milestone renamed