id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
5390	The NF should not evaluate final record parameters unless they only depend on structural or final parameters	Francesco Casella	Karim Adbdelhak	"Please consider the {{{Modelica.Mechanics.MultiBody.Examples.Elementary.HeatLosses}}} model. The {{{final}}} parameter {{{body1.R_start}}} is currently constant-evaluated, to avoid the bindings ending up in the initial equation sections, where the back-end doesn't handle them correctly.

However, the {{{Body}}} model contains the following declaration:
{{{
  final parameter Frames.Orientation R_start=
      Modelica.Mechanics.MultiBody.Frames.axesRotations(
        sequence_start,
        angles_start,
        zeros(3))
    ""Orientation object from world frame to frame_a at initial time"";
}}}
where {{{angles_start}}} is not {{{final}}}, nor it has an {{{Evaluate = true}}} annotation. Hence, {{{R_start}}} should not be constant evaluated, and it should be possible to get it automatically updated if {{{angles_start}}} is changed at run time, without the need to recompile the model from scratch. In fact, that's exactly what Dymola does.

Notice that with the current new front-end and backend, simply moving the final binding to the initial equation section produces incorrect results, see the original bug report in #5288."	defect	assigned	high	2.1.0	Backend				Karim Adbdelhak