id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
3717	Force evaluation of parameters	Rüdiger Franke	Rüdiger Franke	"The current implementation in BackEnd/SynchronousFeatures.mo treats clock settings as rational numbers. This only works for constants or evaluated parameters. In fact Modelica_Synchronous uses the Evaluate=true annotation a lot. Not so in the ShiftSample model. See the following simple example:
{{{#!mo
model ShiftSample
  parameter Integer shiftCounter = 1; // annotation(Evaluate=true);
  parameter Integer resolution = 1; // annotation(Evaluate=true);
  Real x, y;
equation
  when Clock(1) then
    x = previous(x) + 1;
  end when;
  y = shiftSample(x, shiftCounter, resolution);
end ShiftSample;
}}}
Translation fails when attempting to get integer constants out of the parameters shiftCounter=e2 and resolution=e3 with:
{{{
        DAE.ICONST(i1) := e2; DAE.ICONST(i2) := e3;
}}}
The model works when uncommenting the Evaluate=true annotations above.

Is there a way to force the evaluation of a parameter, i.e. making it structural during model translation?"	defect	closed	high	Future	Frontend	v1.9.4-dev-nightly	fixed		martin.otter@…