Opened 11 years ago
Closed 4 years ago
#2735 closed defect (fixed)
simulation fails without any error message in OMEdit
Reported by: | Lennart Ochel | Owned by: | somebody |
---|---|---|---|
Priority: | high | Milestone: | 1.16.0 |
Component: | Backend | Version: | trunk |
Keywords: | Cc: | Adrian Pop, Adeel Asghar, Martin Sjölund |
Description
Please, check the following model:
trunk/testsuite/simulation/modelica/initialization/OverdeterminedInitialization.Fluid.TwoVolumesFullInitial.mos
It fails without any error message in OMEdit if it get simulated.
checkModel + getErrorString output:
"Check of OverdeterminedInitialization.Fluid.TwoVolumesFullInitial completed successfully. Class OverdeterminedInitialization.Fluid.TwoVolumesFullInitial has 178 equation(s) and 178 variable(s). 101 of these are trivial equation(s). " ""
buildModel + getErrorString output
{"",""} ""
instantiateModel + getErrorString output
"" "Error: Tried to use function .Modelica.Fluid.Vessels.ClosedVolume.Medium.T_h, .Modelica.Fluid.Vessels.ClosedVolume.Medium.T_h.Internal.solve, but it was not instantiated. "
simulate + getErrorString output
record SimulationResult resultFile = "", simulationOptions = "startTime = 0.0, stopTime = 1.0, numberOfIntervals = 500, tolerance = 1e-06, method = 'dassl', fileNamePrefix = 'OverdeterminedInitialization.Fluid.TwoVolumesFullInitial', options = '$ messages = "Failed to build model: OverdeterminedInitialization.Fluid.TwoVolumesFullInitial", timeFrontend = 0.0, timeBackend = 0.0, timeSimCode = 0.0, timeTemplates = 0.0, timeCompile = 0.0, timeSimulation = 0.0, timeTotal = 0.0 end SimulationResult; ""
Change History (9)
comment:1 by , 10 years ago
Milestone: | 1.9.1 → 1.9.2 |
---|
comment:2 by , 10 years ago
Milestone: | 1.9.2 → 1.9.3 |
---|
Milestone changed to 1.9.3 since 1.9.2 was released.
comment:7 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:8 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.
comment:9 by , 4 years ago
Component: | Frontend → Backend |
---|---|
Milestone: | Future → 1.16.0 |
Resolution: | → fixed |
Status: | new → closed |
The test case was enabled in r24361.
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).