Francesco Casella

I checked, the bug is present with the latest nightly, both under Windows 10 and under Ubuntu focal.

> I added that uses by hand. OK. I was worried that OMEdit added them, which shouldn't be the case. > Ok, that uses annotation should have been in the...

> On the third line of the above output, you can see `drive.limTau.wMax` is being set to its min value. Updating the min value is **immediately followed** by setting it...

> I'm TOTALLY in favour of this approach! The contribution of OM to keep modelica stable is fundamental. 👌 > it seems that there is coherency in the OM behaviour...

> > The real question is: why on Earth, after the code to set drive.limTau.wMax.min = 250, we also generate code that sets the parameter to its start attribute? This...

BTW, I'm not sure if the point of "Only reassign start value if it has been overwritten" was to fix some mechanism that led to wrong results, or just to...

@mahge so far I had misunderstood how this thing works, it's a bit tricky 😅. Now maybe I get it. When I see this statement ```C data->modelData->realParameterData[35].attribute /* drive.limTau.wMax */.min...

@mahge, I think I got it right in the previous comment. In M_08_bnd.c I see: ```C static void M_eqFunction_101(DATA *data, threadData_t *threadData) { TRACE_PUSH const int equationIndexes[2] = {1,101}; (data->simulationInfo->realParameter[35]/*...

GOTCHA! @mahge I think I know how to fix this issue. There a few places in initialization.c with these two lines: ```C data->callback->updateBoundParameters(data, threadData); data->callback->updateBoundVariableAttributes(data, threadData); ``` As we said,...

Now that I think of it, there could be a much better and more efficient alternative. When handling the min/max/nominal equations, the template generates functions such as ```C static void...