#5062 closed defect (fixed)
[NF] Handling of parameters (fixed=false, start=value) with annotation(Evaluate=true)
Reported by: | adrpo | Owned by: | perost |
---|---|---|---|
Priority: | high | Milestone: | 2.0.0 |
Component: | New Instantiation | Version: | |
Keywords: | Cc: | casella |
Description
It seems that in MSL we have final parameters with fixed=false, a start value and annotation(Evaluate=true).
The question is how do we handle these?
- Do we give an warning that it has no binding?
- Do we just ignore that it has no binding?
- Do we use the start value as a binding, they are final!?
Change History (6)
comment:1 Changed 6 years ago by adrpo
comment:2 Changed 6 years ago by adrpo
I will add a warning if we have a parameter Type p(fixed=true) annotation(Evaluate=true); with no binding.
I've seen some discussion on making parameters without binding an error, if we decide on that it will be easy to add (#5051).
comment:3 in reply to: ↑ description Changed 6 years ago by casella
Replying to adrpo:
It seems that in MSL we have final parameters with fixed=false, a start value and annotation(Evaluate=true).
This sounds really odd to me. The front-end should be able to analyze and solve the initial equations in order to compute the value, which seems quite far-fetched.
Can you point out where are these parameters found?
comment:4 Changed 6 years ago by adrpo
- Resolution set to fixed
- Status changed from new to closed
comment:5 Changed 6 years ago by adrpo
See:
https://github.com/modelica/ModelicaStandardLibrary/blob/master/Modelica/Mechanics/MultiBody/Joints.mo#L6181
Also there is a small related discussion here:
https://github.com/modelica/ModelicaStandardLibrary/issues/1116
comment:6 Changed 6 years ago by adrpo
- Summary changed from [NF] Handling of parameters (flxed=false, start=value) with annotation(Evaluate=true) to [NF] Handling of parameters (fixed=false, start=value) with annotation(Evaluate=true)
Modelica Spec says:
This would imply that the parameter should have a value.