Opened 4 years ago
Last modified 4 years ago
#6284 new defect
When condition with dae mode
| Reported by: | Owned by: | Andreas Heuermann | |
|---|---|---|---|
| Priority: | high | Milestone: | NeedsInput |
| Component: | Run-time | Version: | 1.16.0 |
| Keywords: | when condition, dae mode | Cc: | florentine.rosiere@…, maria.nuschke@…, luis.david.pabon.ospina@…, francesco.casella@…, adrien.guironnet@…, Bernhard Bachmann, Karim Adbdelhak, Andreas Heuermann |
Description
Such an example works fine with ida but not anymore when adding the dae mode (the variable U stays constant equals to 1):
Real U(start = 1);
equation
when time >1 then
U = 0.8;
end when;
We are working on an electrical test system and we need the dae mode so that we can simulate within acceptable time, but we also need to simulate the tapChanger behavior, which is impossible in dae mode because the tap stays constant.
This problem can also be observed with PowerGrids/Electrical/Tests test case "TestTransformerWithTapChangerInterval": when adding the dae mode, the tap doesn't move anymore.
Change History (1)
comment:1 by , 4 years ago
| Cc: | added |
|---|---|
| Component: | *unknown* → Run-time |
| Owner: | changed from to |
Note:
See TracTickets
for help on using tickets.
@marianne, thanks for bringing this up. In fact, daeMode was initially developed with a main focus on continuous-time behaviour, and we really never worked out the event handling in a thorough way. See, e.g., #4034, which is four years old already.
That event handling is weak in daeMode is also visible when comparing the results of libraries such as PNLib when odeMode is used, and when daeMode is used.
I think we should re-assess the current status with Bernhard Bachmann, and then make some plans for the future.