Opened 12 years ago
Last modified 7 years ago
#1817 assigned defect
Exporting "Modelica.Electrical.Machines.Examples.AIMS_Start" to FMI generates invalid modelDescription.xml
Reported by: | dh | Owned by: | Willi Braun |
---|---|---|---|
Priority: | high | Milestone: | Future |
Component: | Code Generation | Version: | |
Keywords: | Cc: |
Description
modelDescription.xml does not contain a valid min or starting attribute for ScalarVariable aims.airGapS.p
while simulation the model the default value is set to "2"
Exporting the example via Dymola 2013 resulsts in a correct behaivor
extract from modelDescription.xml
<ScalarVariable name="aims.airGapS.p" valueReference="11" description="number of pole pairs" variability="parameter" causality="internal" alias="noAlias"> <Integer/> </ScalarVariable>
The missing start/min value causes this error
division by zero in partial equation: (aims.airGapS.gamma - (-Real(aims.airGapS.p)) * aims.fixed.phi0) / Real(aims.airGapS.p) because Real(aims.airGapS.p) == 0
| [line] 5463 | [file] Modelica_Electrical_Machines_Examples_AIMS_Start.c
Change History (10)
comment:1 by , 12 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:3 by , 10 years ago
Milestone: | 1.9.1 → 1.9.2 |
---|
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).
comment:4 by , 10 years ago
Milestone: | 1.9.2 → 1.9.3 |
---|
Milestone changed to 1.9.3 since 1.9.2 was released.
comment:9 by , 8 years ago
Milestone: | 1.11.0 → 1.12.0 |
---|
Milestone moved to 1.12.0 due to 1.11.0 already being released.
comment:10 by , 7 years ago
Milestone: | 1.12.0 → Future |
---|
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.
Seems to give bad initial conditions for the non-linear solver also for the regular code.