Francesco Casella
Francesco Casella
> With a conversion script it should be (somehow) defined that models without balance definition, use balance=false (= the current definition) I read the [specification](https://specification.modelica.org/v3.4/Ch18.html#conversion-rules) of convertModifiers carefully, but I...
> The problem is that users might have added enough initial conditions in their models and with > a new MSL version, suddenly they will get an error, even if...
> > > Here you go: > > ``` > convertModifiers({"Modelica.Blocks.Nonlinear.PadeDelay"}, fill("",0), {"balance=false"}) > ``` @beutlich, are we sure? The specification says > If OldModifer list is empty it (=...
> > > Conversion script still is missing. Sure. That will take some time. After the coronavirus hit I no longer had time to deal with that. Will take care...
I double-checked the BevelGear1D test case, the [CSV reference file](https://github.com/modelica/MAP-LIB_ReferenceResults/blob/6c0e36a3ca61cfd3b313dc01e04bde66cf9b1c98/Modelica/Mechanics/MultiBody/Examples/Rotational3DEffects/BevelGear1D/BevelGear1D.csv#L2002 ) ends at time = 0.40000001, so the CSV-compare tool should definitely compute the high and low tubes only up...
Apparently something was fixed on the LTX servers, by looking at the latest [Modelica regression test report](https://www.ltx.de/download/MA/Compare_MSL_v4.1.0/Compare/Modelica/testrun_report.html), the BevelGear1D model passes the verification phase. All's well that ends well.
@mestinso the reason why we used head instead of specific energy is that manufacturers of pumps usually provide data in terms of head vs. volumetric flow curves, so the most...
@HansOlsson I completely agree. In any case, handling that case requires a different library, because the acceleration is time-varying, so it's beyond the scope of Modelica.Fluid.
> It seems like this proposal has a similar shortcoming as in #3257 when it comes to allowing for connector variable unit inference. I think both proposals should to be...
> My main concern is that we seem to have a number of models where numbers are assumed to have a unit, e.g. Modelica.Electrical.Batteries.Examples.BatteryDischargeCharge where `Ri=cellData1.OCVmax/1200` (the 1200 is assumedly...