Opened 5 years ago
Last modified 3 years ago
#5709 new defect
Equidistant time grid not working properly
Reported by: | ceraolo | Owned by: | somebody |
---|---|---|---|
Priority: | blocker | Milestone: | 1.19.0 |
Component: | *unknown* | Version: | |
Keywords: | Cc: |
Description (last modified by ceraolo)
The Simulation setup, checking the option "equidistant time grid", while simultaneously unchecking "Store Variables at events", should give, in my understanding, control on the number of points stored in the output file.
This is very important when one wants to post-process results, for instance using an algorithm to find harmonics in periodic curves, which often require uniform sampling time.
Take for instance:
Modelica.Electrical.PowerConverters.Examples.DCAC.SinglePhaseTwoLevel.SinglePhaseTwoLevel_R
Let us set:
- set Stop time: 0.1
- set Number of Intervals 5000
- select "Equidistant time Grid"
- unselect "Store Variables at Events".
According to these options, I would expect to have exactly 5001 points in the output file, and, in fact, with Dymola this is what happens.
With OM, instead, I produce 4901 points. I suspect that these are not equidistant.
Change History (7)
comment:1 Changed 5 years ago by casella
- Priority changed from high to blocker
- Summary changed from Equidistant time grind not working properly to Equidistant time grid not working properly
comment:2 Changed 5 years ago by ceraolo
- Description modified (diff)
comment:3 Changed 4 years ago by casella
- Milestone changed from 1.15.0 to 1.16.0
comment:4 Changed 4 years ago by casella
- Milestone changed from 1.16.0 to 1.17.0
Retargeted to 1.17.0 after 1.16.0 release
comment:5 Changed 4 years ago by casella
- Milestone changed from 1.17.0 to 1.18.0
Rescheduled to 1.18.0
comment:6 Changed 3 years ago by casella
- Milestone 1.18.0 deleted
Ticket retargeted after milestone closed
comment:7 Changed 3 years ago by casella
- Milestone set to 1.19.0
1.18.0 blocker tickets moved to 1.19.0
Release 1.15.0 was scrapped, because replaceable support eventually turned out to be more easily implemented in 1.16.0. Hence, all 1.15.0 tickets are rescheduled to 1.16.0