You can try to simulate for a shorter time and enable performance profiling to see which blocks are slow to solve. You could also try a different solver to see if it is dassl that found a stiff system and decreases the step size.

FelixB wrote:

Do you have an idea what might cause this problem?
How do I get debug information when the simulation does not finish?

Too many events, stiff system, hard non-linear systems,
long initialization run, etc. there are a lot of things that might
cause performance issues.

You can run the simulation application with some debug flags:

-lv LOG_SOLVER -> [additional information about solver process]
-lv LOG_EVENTS -> [additional information during event iteration]
-lv LOG_INIT          -> [additional information during initialization]
-lv LOG_SOTI        -> [final solution of the initialization]

so long.
Willi

Thank you two for the tips.

I spent the last couple of days trying to pinpoint the problem and I'm pretty sure that I'm facing the same problem in the fluid library as reported here:
https://www.openmodelica.org/forum/defa … ples#p4720
Unfortunately there seems to be no solution yet.

Anyways - I upgraded to the latest nightly and now I'm getting another weird error. I filed a ticket, because I'm pretty sure that the problem does not lie within my code: https://trac.openmodelica.org/OpenModel … action=new