Opened 4 years ago
Last modified 3 years ago
#6265 new defect
assert() not correctly handled by OM: second case
| Reported by: | Owned by: | Francesco Casella | |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | *unknown* | Version: | 1.16.0 |
| Keywords: | Cc: |
Description
This ticket completes previous ticket #6264.
Refer to model DegradedModeForLoads in package Examples.
I see two issues in the handling of assert():
1/ The assert() not load.U < load.minU is not reported with the correct time. The time is 36.8 and should be 36.0 (exactly the same time as for assert() load.degradedMode == false)
2/An assert is missing. The assert() load.degradedMode = true should be reported a second time at approx. time = 364
No issue with Dymola.
Change History (3)
comment:1 by , 4 years ago
comment:2 by , 4 years ago
| Milestone: | 1.17.0 → 1.18.0 |
|---|
Retargeted to 1.18.0 because of 1.17.0 timed release.
Note:
See TracTickets
for help on using tickets.
Can you reproduce the issue with PowerSysPro 1.4? Seem to be strange...