Skip to content

Component vs. Node Data (CR #796) #2

@Myoldmopar

Description

@Myoldmopar
Added on 1999-03-03 13:56 by @lklawrie

Description

Node Data currently contains Max/Min that are usually assigned to the outlet side of a component. This data is really particular to the component itself and this assignment to the nodes should be revisited prior to final release.

Fix

Yes that's right . A design decision was made to put the component
flow max and min on the component outlet node. Other max and mins
(temperature and humidity ratio) aren't really being used yet. The
reason for doing this was that the component data is not easily available
to the loop solver whereas the node data is available. Still, it is a
somewhat ad hoc procedure. Let's think about this again & discuss
it at our next meeting (Golden CO, May 2000).

FB 3/31/2000

We've let this as is.
FB 02/25/2002

External Ref: 19
Last build tested: 99.02.25 Build of EnergyPlus

Metadata

Metadata

Assignees

No one assigned

    Labels

    DefectIncludes code to repair a defect in EnergyPlusSeverityMediumThis defect is medium severity, indicating moderate impact and generally no workaround available

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions