Francesco Casella

1.20.0-dev.beta4, which should be identical to 1.20.0 official. If this has already been solved with the latest nightly, that would be it :) @albertoleva can you try with the latest...

> I think this might be related to tearing. Tearing sometimes picks boolean variables as iteration variables. This is perfectly legitmate. In fact, it's the only sound way we have...

> IIRC `minimalTearing` is supposed to never pick any discrete variables as iteration variables. If it can not do that it is supposed to fail at Modelica compilation time. At...

> I think this might be related to tearing. Tearing sometimes picks boolean variables as iteration variables. Perhaps it works if you use minimal tearing. `--tearingMethod=minimalTearing` Inded it does. The...

@albertoleva reports still having the same problem with the nightly build. @mahge maybe you have some system settings for `--tearingMethod=noTearing`?

>The question is, is it legitimate to pick booleans as iteration variables? In general, I guess so. For example, consider this MWE: ```modelica model TestTearing2 Real x,y,z; Boolean b; equation...

OK, so given the current state of the art the problem with this model is that the tearing algorithm picks $whenCondition2`as an iteration variable, which it shouldn't. The problem with...

I changed the title of the ticket to better reflect what is the problem with it.

> In the meantime I can modify my work for #8164 to try and cover step 2. as comprehensive as possible by selecting iteration variables on the rhs of solved...

Decision during today's webmeeting: - try with the current tearing setup (in terms of --tearingStrictness and --tearingMethod) - if some $cse, $whenCondition or any Boolean/Integer variables end up as iteration...