Francesco Casella

One such case is the valve flow equation: > w = Kv*sqrt(dp/(rho/rho0)) where w is the mass flow rate (kg/s), dp is the pressure drop (Pa = N/m2 = kg.m/(s2.m2)...

EDIT: I messed up a bit with the valve formula, my apologies. The correct formula is q = Kv*sqrt(dp/(rho/rho0)) where q is the _volume flow rate_ (m3/s), dp is the...

> I'd say it's not for us to decide how users should express their equations, in other words that it is _being used_ that is the more important criterion. I...

As far as units and unit checking are concerned, IMHO it would be far more important to fix the issue of the units of non-dimensional literal constants in expressions, which...

The goal of smoothOrder is to declare that the function is _continuously_ differentiable n times, is needed for index reduction, since tools can automatically differentiate piecewise-defined functions, but cannot automatically...

@henrikt-ma, my previous comment was incomplete. As I understand, these are the possible scenarios, that are valid both for `smooth()` in expressions and `smoothOrder` in function declarations. **Regarding event handling...

> One of the things I'm trying to improve is to avoid the misinterpretation of `smoothOrder` as a way of requesting that the tool provide automatically generated function derivatives, as...

> Are we right, that the Modelica Specification in fact leaves the initialization of clocked variables during calls to clocked algorithms unspecified? I think so, good point. > Has this...

> Let us also hint to the circumstance, that several Modelica tools behave unconsistently in this situation. (Some using the start value, others using previous value.) That's too bad, but...

> However, if the model was continuous and is then clocked discretized (see #3091 for a discussion of having better names for that) it becomes less clear. Since the goal...