OMEdit crashes: When set record parameter in Function

[arnesinnema@…]

OMEdit crashes when a record parameter is set in a function (see code below), it looks very similar to bug #3082.

model TestRecord 
  function setRecordFunction 
    output Real[3] y; 
  protected 
    Rec[3] x; 
  algorithm 
    for i in 1:3 loop 
      x[i].r := i; 
      y[i] := x[i].r; 
    end for; 
  end setRecordFunction; 

  record Rec 
    Real r; 
  end Rec; 

  model CallRecordFunction 
    Real[3] y; 
    //Real[4] y2; 
  equation 
    y = setRecordFunction(); 
    //y2 = setRecordFunction2(4); 
  end CallRecordFunction; 

  function setRecordFunction2 
    input Integer N; 
    output Real[N] y; 
  protected 
    Rec[N] x; 
  algorithm 
    for i in 1:N loop 
      x[i].r := i; 
      y[i] := x[i].r; 
    end for; 
  end setRecordFunction2; 
end TestRecord;

[Per Östlund]

Seems like the run-time is having some issues with assigning record components like that. A workaround is to rewrite

for i in 1:3 loop
  x[i].r := i;
  y[i] := x[i].r;
end for;

as

x.r := 1:3;
y := x.r;

Of course, your example is simplified, so maybe it's not possible for you to get rid of the loop in your actual model.

[Per Östlund]

Fixed in r25245.

[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.