Opened 8 years ago

Closed 7 years ago

#4441 closed defect (fixed)

Incorrect calculation of stream variables

Reported by: j.schulz@… Owned by: Vitalij Ruge
Priority: high Milestone: 1.13.0
Component: Backend Version: v1.11.0
Keywords: stream variable, incorrect calculation Cc:

Description

The discrepancy in calculation will occur if a node connects more than two components and one component’s mass flow rate is explicitly set to zero. In case of three components with one component’s mass flow rate set to zero, the incorrectly calculated stream variable amounts to exactly 50 % of its proper value. If this component, the mass flow rate of which is set to zero, is removed, the stream variable will be calculated correctly.

The ZIP archive contains two packages: “StreamSolarSystem2” and “TILMedia”. The latter is included to provide necessary thermophysical property data. The “StreamSolarSystem2” package contains two system models: Running “System1” will deliver the incorrect result for the stream variable “pump.portA.hOut”. In “System1_withoutSensor” the component, the mass flow rate of which has been set to zero is removed, and, thus, the correct value for “pump.portA.hOut” will be calculated.

Other tools detect if a model sets the mass flow rate explicitly to zero, and treat them as if they were not existing. The inStream() value in the other connected models only refer to each other, not to the model with m_flow = 0. The treatment and behaviour of two connected models is exactly the same, as of three connected models with one having m_flow set to zero.

Attachments (1)

Incorrect calculation of stream variables.zip (10.5 MB ) - added by j.schulz@… 8 years ago.
Example

Change History (6)

by j.schulz@…, 8 years ago

Example

comment:1 by Vitalij Ruge, 7 years ago

Owner: changed from Lennart Ochel to Vitalij Ruge
Status: newassigned

comment:2 by Vitalij Ruge, 7 years ago

Status: assignedaccepted

fixed with PR2319.

comment:3 by Willi Braun, 7 years ago

Milestone: Future1.13.0

in reply to:  2 comment:4 by Lennart Ochel, 7 years ago

Replying to vitalij:

fixed with PR2319.

Did you forget to close this?

comment:5 by anonymous, 7 years ago

Resolution: fixed
Status: acceptedclosed
Note: See TracTickets for help on using tickets.