nonlinear systems around external functions

[c.schulze@…]

In the tester an external function is called. The inputs of the function are given. Nevertheless OpenModelica puts a nonlinear system around the function to iterate the outputs.

[c.schulze@…]

example package

[Martin Sjölund]

The non-linear system looks like this:

    <nonlinear indexNonlinear="1">
      <defines name="h_i[3]" />
      <defines name="h_i[2]" />
      <defines name="delta_hv" />
      <defines name="h_i[1]" />
      <defines name="h_i[5]" />
      <defines name="h_i[4]" />
      <defines name="delta_hd" />
      <defines name="p_s" />
      <eq index="15"/>
      <eq index="16"/>
      <eq index="17"/>
      <eq index="18"/>
      <eq index="19"/>
      <eq index="20"/>
      <eq index="21"/>
      <eq index="22"/>
      <eq index="23"/>
    </nonlinear>

These are all outputs of the call in the flat Modelica:

(p_s, delta_hv, delta_hd, h_i) = FalseIterationVar.pureComponentProperties_pTnc(p, T, nc)

So not only is a non-linear solver used; it also calls the external function 9 times for each iteration of the NLS solver.

[Willi Braun]

fixed in r22773.

[Dietmar Winkler]

It doesn't make sense to keep closed ticket in the "Future" milestone that were simply forgotten to assign to the correct milestone in the past.

[Martin Sjölund]

Removing the pre1.9.4 milestone in favor of 1.9.4.