Remaining issues with HelmholtzMedia

[Francesco Casella]

As of 25 Aug 2020, we have ​42 runnable models in the library, which all go through all phases of code generation.

One fails during C-code compilation, see #6087.

Another five fail at runtime

• ​HelmholtzMedia.Examples.ConvergenceTest.Ancillary_Saturation apparently go above critical temperature
• ​HelmholtzMedia.Examples.ConvergenceTest.setSat has convergence issues with setSat_T at time 8.5363
• ​HelmholtzMedia.Examples.MediaTestModels.IsopentaneTestModel fails at initialization, probably because of bad initialization values:

  assert            | warning | The following assertion has been violated at time 0.000000
  |                 | |       | false
  assert            | warning | Nominal variable violating min/max constraint: -725000.0 <= ambient.h_ambient <= 700000.0, has value: 1e+06
  

• ​HelmholtzMedia.Examples.Validation.Derivatives_SaturationBoundary fails at initialization because of multiple issues with out-of-range values
• ​HelmholtzMedia.Examples.Validation.idealGasLimit runs into numerical problems at time = 480

@matthis, feel free to further investigate and comment or ask for clarifications here.

[Karim Adbdelhak]

I looked at HelmholtzMedia.Examples.Validation.Derivatives_SaturationBoundary and it looks like it has the same problem as HelmholtzMedia.Examples.ConvergenceTest.setSat because it is that very function that fails.

When running the compiled code multiple times and looking at the values i realized that this function always returns different values (with same setup!), so there is some uninitialized stuff happening. That lead me to think that there is something wrong with matching, the order does not seem to be correct and i tried DAEMode (--daeMode) which simulates without causalization and a wrong matching would only mess event handling up a little. And indeed it works with that setting.

Could someone try and verify the results? (see attached file) If you want to reproduce the results please update to the newest development version because some of my latest commits could have major impact here.

I will look into the function and its ordering and try to come up with a minimal model. Is there something special about this function in particular that differs from other functions?

[Karim Adbdelhak]

The failing function is HelmholtzMedia.Interfaces.PartialHelmholtzMedium.setSat_T, the name of the function test confused me sorry!

Also i am on the train currently and the upload of the result file does not work. I will add that later.

[Karim Adbdelhak]

created with -d=newInst and --daeMode

[matthis.thorade@…]

I tried loading the _res.mat file in Dymola, but it gives me the error message:

Error when reading matrix "data_2 (1001,62)" from file "C:/Users/matthis.thorade/Downloads/HelmholtzMedia.Examples.Validation.Derivatives_SaturationBoundary_res.mat",
because abscissa values are not strict monotonically increasing
((7,1) = -2147483648 < (8,1) = 1073741824).

[matthis.thorade@…]

results from Dymola simulation

[Karim Adbdelhak]

Replying to matthis.thorade@…:

I tried loading the _res.mat file in Dymola, but it gives me the error message:

Error when reading matrix "data_2 (1001,62)" from file "C:/Users/matthis.thorade/Downloads/HelmholtzMedia.Examples.Validation.Derivatives_SaturationBoundary_res.mat",
because abscissa values are not strict monotonically increasing
((7,1) = -2147483648 < (8,1) = 1073741824).

I don't know if our result files are 100% compatible with Dymola. Opening it with OpenModelica works. But i compared it with your results and there are major differences, it looks like DAEMode just does not complain about the uninitialized values and just uses them.

Good for debugging though... i try to figure it out!