Opened 9 years ago
Closed 6 years ago
#3839 closed defect (fixed)
Medium.nC incorrectly set to 0 instead of 1.
Reported by: | Michael Wetter | Owned by: | Per Östlund |
---|---|---|---|
Priority: | high | Milestone: | 2.0.0 |
Component: | New Instantiation | Version: | |
Keywords: | Cc: |
Description
The regression tests
Annex60.Fluid.MixingVolumes.Validation.MixingVolumeTraceSubstanceReverseFlow Annex60.Fluid.MixingVolumes.Validation.MixingVolumeTraceSubstanceReverseFlowPrescribedHeatFlowRate
fail with
[/var/lib/hudson/jobs/OpenModelica_TEST_ALL_LIBRARIES/workspace/OpenModelica/build/lib/omlibrary/Annex60 0.1/Fluid/MixingVolumes/Validation/MixingVolumeTraceSubstanceReverseFlow.mo:12:3-13:47:writable] Error: Subscript '1' for dimension 1 (size = 0) of volSte.C_flow[1] is out of bounds. Error: Error occurred while flattening model Annex60.Fluid.MixingVolumes.Validation.MixingVolumeTraceSubstanceReverseFlow
The problem seems to be that OpenModelica does not assign Medium.nC
correctly (which is declared in PartialMedium
as
final constant Integer nC=size(extraPropertiesNames, 1)
).
If I move the assignment
package Medium = Annex60.Media.Air ( Medium(extraPropertiesNames={"CO2"})) "Medium model";
from Annex60.Fluid.MixingVolumes.Validation.MixingVolumeTraceSubstanceReverseFlow
to its base class
Annex60.Fluid.MixingVolumes.Validation.BaseClasses.MixingVolumeReverseFlow
,
then omc
hangs.
There doesn't seem to be a work-around.
Change History (5)
comment:1 by , 7 years ago
Component: | *unknown* → NF - New FrontEnd |
---|---|
Milestone: | Future → 2.0.0 |
Owner: | changed from | to
Status: | new → assigned |
comment:2 by , 7 years ago
Component: | NF - New FrontEnd → New Instantiation |
---|
Move all tickets from NF - New Frontend to New Instantiation so we don't have two different categories for the same thing.
comment:3 by , 6 years ago
The NF still fails on this example for other reasons, see Annex60.Fluid.MixingVolumes.Validation.MixingVolumeTraceSubstanceReverseFlow.
This should be checked periodically until the NF can handle it.
comment:4 by , 6 years ago
The issue described in this ticket is solved. The new problem is reported in #5338
comment:5 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
@perost can you make sure this works properly with the new front end?