Francesco Casella

I guess this problem became stale in the meantime, as we have developed further simplifications to avoid getting such huge nonlinear models in the first place.

BTW, I understand there is no reason to use redeclare final. Only if you do redeclare replaceable should the redeclared class be further redeclared.

This is related to #8425.

> @casella thanks for the detailed investigation! This should make it easy to find the root cause. I found https://trac.openmodelica.org/OpenModelica/ticket/5104 in which replacements, similar to those you mention here, were...

I report the list of simplification rules from the old ticket here, for convenience 1. inStream introduces positiveMax(cref, eps) and positiveMax(-cref, eps) 2. simplify positiveMax in Backend after removeSimpleEquation and...

I guess I went too far with them. The first idea is that if a fluid never flows out of a certain port (as guaranteed by min/max flow variable attributes),...

I did some analysis with `-d=optdaedump`. `hvac.cooCoi.m1_flow` starts having `min = -100000` and `max = 100000`, but after `removeSimpleEquations` it inherits some additional constraints from some other variables it is...

Here is the set of revised rules. I made them conservative, putting a premium on avoiding ill-posed systems over avoiding nonlinear behaviour. If one wants further optimizations, this can always...

> `w` would be evaluated due to the `Evaluate` annotation, but the frontend doesn't simplify `positiveMax` calls in any way. OK, sorry, I misinterpreted your statement in [#3885](https://trac.openmodelica.org/OpenModelica/ticket/3885#comment:23). There you...

@phannebohm, I played around a bit with this simple test case [TestInStreamConst.mo.txt](https://github.com/OpenModelica/OpenModelica/files/10125415/TestInStreamConst.mo.txt), where the two flow rates are a parameter and a constant, respectively. What I see happening in the...