Record input connectors wrongly interpreted by the OpenModelica compiler

[mats.l.larsson@…]

It seems that the OpenModelica compiler wrongly interprets inputs based on record data types.

The three following models a,b,c are essentially the same model, but using different set ups of data types.

The use of scalar types (block a) compiles properly, as well as the use of vectorized data types (block b). However, when a record data type (block c) is used the compilation fails with error regarding a mismatch between the number of unknowns (2 equations and 4 unknowns are reported).

This is indeed very strange, since the instantiated model actually has the correct code (see below) that is equivalent to the manually coded block a:

// correct automatically generated code for block c
class inputoutput.c  
  input Real u.a;
  input Real u.b;
  output Real y.a;
  output Real y.b;
equation
  y.a = u.a;
  y.b = u.b;
end inputoutput.c;


package inputoutput

  record sig
    Real a,b;
  end sig;

// block a compiles with OpenModelica 1.9 r17338
  block a
    input Real a,b;
    output Real A,B;
  equation
    A = a;
    B = b;
  end a;

   // block b compiles with OpenModelica 1.9 r17338
  block b
    input Real u[2];
    output Real y[2];
  equation
    y = u;
  end b;

    // block cfails to compile with OpenModelica 1.9 r17338
  block c
    input sig u;
    output sig y;
  equation
    y = u;
  end c;
  annotation(Icon(coordinateSystem(extent = {{-100,-100},{100,100}}, preserveAspectRatio = true, initialScale = 0.1, grid = {2,2})), Diagram(coordinateSystem(extent = {{-100,-100},{100,100}}, preserveAspectRatio = true, initialScale = 0.1, grid = {2,2})), uses(Modelica(version = "3.2")));
end inputoutput;

[Martin Sjölund]

Postponed until 1.9.1

[Martin Sjölund]

This ticket was not closed for 1.9.1, which has now been released. It was batch modified for milestone 1.9.2 (but maybe an empty milestone was more appropriate; feel free to change it).

[Martin Sjölund]

Milestone changed to 1.9.3 since 1.9.2 was released.

[Martin Sjölund]

Moved to new milestone 1.9.4

[Martin Sjölund]

Milestone pushed to 1.9.5

[Martin Sjölund]

Milestone renamed

[Martin Sjölund]

Ticket retargeted after milestone closed

[Martin Sjölund]

Milestone moved to 1.12.0 due to 1.11.0 already being released.

[Francesco Casella]

The milestone of this ticket has been reassigned to "Future".

If you think the issue is still valid and relevant for you, please select milestone 1.13.0 for back-end, code generation and run-time issues, or 2.0.0 for front-end issues.

If you are aware that the problem is no longer present, please select the milestone corresponding to the version of OMC you used to check that, and set the status to "worksforme".

In both cases, a short informative comment would be welcome.