Branch & Node Checking and Services[LINK]

BranchInputManager[LINK]

For the most part, new modules do not use the BranchInputManager directly. Branches are “gotten” at a high management level. The main routines that might be used from the BranchInputManager are: NumBranchesInBranchList, GetBranchList and GetBranchData. The BranchInputManager also houses the Splitter and Mixer data: GetLoopSplitter and GetLoopMixer.

NumBranchesInBranchList[LINK]

This routine is used to get the number of branches in a branch list name (so that an appropriate array can be allocated).

INTEGER FUNCTION NumBranchesInBranchList(BranchListName)

An example of use:

= = = Example = = =

USE BranchInputManager, ONLY: NumBranchesInBranchList,. . .

GetBranchList[LINK]

This routine is used to get the names of the branches on a Loop.

SUBROUTINE GetBranchList(LoopName, BranchListName, NumBranchNames, BranchNames, LoopType)

= = = Example = = =

USE BranchInputManager, ONLY: GetBranchList, . . .

GetBranchData[LINK]

This routine is used to get pieces of data about a branch.

SUBROUTINE GetBranchData(LoopName, BranchName, BranchMaxFlow, NumComps, CompType, CompName, CompCtrlType, CompInletNodeNames, CompInletNodeNums, CompOutletNodeNames, CompOutletNodeNums, ErrorsFound)

= = = Example = = =

! Cycle through all of the branches and set up the branch data

DO BNum = 1,PrimeAirSys(ASysNum)%NumBranches

PrimeAirSys(ASysNum)%Branch(BNum)%Name = BranchNames(BNum)

NumBComps = NumCompsInBranch(BranchNames(BNum))

ALLOCATE(CompTypes(NumBComps))

CompTypes = ’’

ALLOCATE(CompNames(NumBComps))

CompNames = ’’

ALLOCATE(CompCtrls(NumBComps))

CompCtrls = ’’

ALLOCATE(InletNodeNames(NumBComps))

InletNodeNames = ’’

ALLOCATE(InletNodeNumbers(NumBComps))

InletNodeNumbers = 0

ALLOCATE(OutletNodeNames(NumBComps))

OutletNodeNames = ’’

ALLOCATE(OutletNodeNumbers(NumBComps))

OutletNodeNumbers = 0

CALL GetBranchData(PrimeAirSys(ASysNum)%Name, &

BranchNames(BNum), &

PrimeAirSys(ASysNum)%Branch(BNum)%MaxVolFlowRate, &

NumBComps, &

CompTypes,CompNames,CompCtrls, &

InletNodeNames,InletNodeNumbers, &

OutletNodeNames,OutletNodeNumbers,ErrorsFound)

ALLOCATE &

(PrimeAirSys(ASysNum)%Branch(BNum)%Comp(NumBComps))

PrimeAirSys(ASysNum)%Branch(BNum)%TotalComponents = &

NumBComps

PrimeAirSys(ASysNum)%Branch(BNum)%TotalNodes = &

NumBComps+1

ALLOCATE (PrimeAirSys(ASysNum)%Branch(BNum)%NodeNum(NumBComps+1))

PrimeAirSys(ASysNum)%Branch(BNum)%NodeNum(1) = &

InletNodeNumbers(1)

PrimeAirSys(ASysNum)%Branch(BNum)%DuctType = Main

DO CNum = 1,PrimeAirSys(ASysNum)%Branch(BNum)%TotalComponents

PrimeAirSys(ASysNum)%Branch(BNum)%Comp(CNum)%TypeOf = &

CompTypes(CNum)

PrimeAirSys(ASysNum)%Branch(BNum)%Comp(CNum)%Name = &

= CompNames(CNum)

PrimeAirSys(ASysNum)%Branch(BNum)%Comp(CNum)%Index = 0

PrimeAirSys(ASysNum)%Branch(BNum)%Comp(CNum)%FlowCtrl = &

CompCtrls(CNum)

PrimeAirSys(ASysNum)%Branch(BNum)%Comp(CNum)%NodeNameIn = &

InletNodeNames(CNum)

PrimeAirSys(ASysNum)%Branch(BNum)%Comp(CNum)%NodeNumIn = &

InletNodeNumbers(CNum)

PrimeAirSys(ASysNum)%Branch(BNum)%Comp(CNum)%NodeNameOut = &

OutletNodeNames(CNum)

PrimeAirSys(ASysNum)%Branch(BNum)%Comp(CNum)%NodeNumOut = &

OutletNodeNumbers(CNum)

PrimeAirSys(ASysNum)%Branch(BNum)%NodeNum(CNum+1) = &

OutletNodeNumbers(CNum)

NodeInputManager[LINK]

The NodeInputManager is responsible for getting all the node names and assigning each a number. Node names are learned in random order – which can make validation difficult. Internally nodes are referenced as number and should be integers in any data structure or reference. Two key routines are used for obtaining node numbers: GetOnlySingleNode and GetNodeNums.

Node Information Arguments[LINK]

Both routines need some extra information about the node as the number is obtained.This information is used to support fluid property calculations, the HVAC Diagram utility, and various diagnostic checks.

NodeFluidType[LINK]

This argument defines the type of fluid at this node such as air or water. The node fluid type is used for fluid property calculations and is reported in the list of nodes in the bnd output file. Parameter definitions for this argument can be found in DataLoopNode. As of version 1.3, the list of valid choices is:

! Valid Fluid Types for Nodes

INTEGER, PARAMETER :: NodeType_Unknown = 0 ! ‘blank’

INTEGER, PARAMETER :: NodeType_Air = 1 ! ‘Air’

INTEGER, PARAMETER :: NodeType_Water = 2 ! ‘Water’

INTEGER, PARAMETER :: NodeType_Steam = 3 ! ‘Steam’

INTEGER, PARAMETER :: NodeType_Electric = 4 ! ‘Electric’

CHARACTER(len = *), PARAMETER, DIMENSION(0:4) :: ValidNodeFluidTypes = &

(/‘blank ’, &

‘Air ’, &

‘Water ’, &

‘Steam ’, &

‘Electric’/)

INTEGER, PARAMETER :: NumValidNodeFluidTypes = 4

Note that the argument passed in is an integer value – you can “USE DataLoopNode” and use the above definitions (preferred over either defining your own or passing in a number). In many cases, a component may not know the fluid type. For example, most SET POINT MANAGERS are applicable to both air and water nodes. In this case, NodeType_Unknown should be used. It is assumed that for any given node, at least one object referencing it will know the fluid type. Once a known fluid type is passed for a given node, it cannot be changed. All references to the same node must specify the same fluid type or unknown. When all input has been gotten, all node fluid types should be known, but this is not being validated currently.

NodeObjectType[LINK]

This is the type of object which is referencing the node (e.g. Chiller:Electric). This information is used to generate the list of Parent and Non-Parent Node Connections in the bnd output file. This list is used by the HVAC Diagram utility.

NodeObjectName[LINK]

This is the name of the object which is referencing the node (e.g. My Chiller). This information is used to generate the list of Parent and Non-Parent Node Connections in the bnd output file. This list is used by the HVAC Diagram utility.

NodeConnectionType[LINK]

Parameter definitions for this argument can be found in DataLoopNode. .As of version 1.2.0, the current list of choices is:

! Valid Connection Types for Nodes

CHARACTER(len = *), PARAMETER, DIMENSION(13) :: ValidConnectionTypes = &

(/‘Inlet ’, &

‘Outlet ’, &

‘Internal ’, &

‘ZoneNode ’, &

‘Sensor ’, &

‘Actuator ’, &

‘OutsideAir’, &

‘ReliefAir ’, &

‘ZoneInlet ’, &

‘ZoneReturn’, &

‘ZoneExhaust’, &

‘Setpoint ’, &

‘Electric ’/)

INTEGER, PARAMETER :: NumValidConnectionTypes = 13

INTEGER, PARAMETER :: NodeConnectionType_Inlet = 1

INTEGER, PARAMETER :: NodeConnectionType_Outlet = 2

INTEGER, PARAMETER :: NodeConnectionType_Internal = 3

INTEGER, PARAMETER :: NodeConnectionType_ZoneNode = 4

INTEGER, PARAMETER :: NodeConnectionType_Sensor = 5

INTEGER, PARAMETER :: NodeConnectionType_Actuator = 6

INTEGER, PARAMETER :: NodeConnectionType_OutsideAir = 7

INTEGER, PARAMETER :: NodeConnectionType_ReliefAir = 8

INTEGER, PARAMETER :: NodeConnectionType_ZoneInlet = 9

INTEGER, PARAMETER :: NodeConnectionType_ZoneReturn = 10

INTEGER, PARAMETER :: NodeConnectionType_ZoneExhaust = 11

INTEGER, PARAMETER :: NodeConnectionType_Setpoint = 12

INTEGER, PARAMETER :: NodeConnectionType_Electric = 13

This information is used to generate the list of Parent and Non-Parent Node Connections in the bnd output file. This list is used by the HVAC Diagram utility.

After all input has been gotten, node connection types are also validated in CheckNodeConnections in NodeInputManager according to the following rules. The rules are intended to catch user input errors without placing unnecessary constraints on system configurations. The validation checks are not exhaustive, so it is possible to pass all of the checks yet have a misconnected simulation. The main goal here is to prevent dangling nodes which do not behave as the user expects and can often go undetected without scrutinizing detailed outputs.

• For any node which is used as an actuator, the same node must also be used at least once as a node type which is not sensor or actuator or outsideair.

• For any node which is used as a setpoint, the same node must also be used at least once as a node type which is not a setpoint or outsideair.

• Every ZoneInlet must appear as an outlet from something, otherwise it will do nothing.

• Every ZoneExhaust must appear as an inlet to something, otherwise it will do nothing.

• Every inlet node should match either an Outlet, ZoneReturn, ZoneExhaust, ReliefAir, or OutsideAir node, with the following exceptions:

• If an InletNode’s object is AIR PRIMARY LOOP, CONDENSER LOOP, or PLANT LOOP, then skip the test.

• If an InletNode’s object is not one of the above types, it is valid if the same node name appears as an INLET to an AIR PRIMARY LOOP, CONDENSER LOOP, or PLANT LOOP.

If a node fails any of the above tests, a severe error message is generated. If a new module generates unexpected errors, check the node connection types used by a similar module. If a given node is used in more than one way by an object, it may be necessary to register the node more than once by successive calls to GetOnlySingleNode or GetNodeNums with different arguments in each call.

NodeConnectionType_OutsideAir is intended to specify nodes which are connected to the outside air. For example, OUTSIDE AIR MIXER has an Outside_Air_Stream_Node which is registered as NodeConnectionType_Inlet, because it may have other components such as a preheat coil between it and the outside air. Whichever node ultimately connects to the outside air in this case will be registered as NodeConnectionType_OutsideAir by an OUTSIDE AIR INLET NODE LIST object.

Some types of equipment take in outside air directly without relying on OUTSIDE AIR INLET NODE LIST to set the conditions on that node. For example, UNIT VENTILATOR and chillers with air cooled condensers do not require the use of an OUTSIDE AIR INLET NODE LIST. In these cases, the component registers the outside air node directly as NodeConnectionType_OutsideAir. Given that the use of outside air nodes is not consistent throughout the code, it may be necessary at some point to relax or alter the validation rules associated with outside air nodes to accommodate a new type of module. Please consult with the team before changing these rules.

NodeFluidStream[LINK]

This is an integer indicating which fluid stream this node belongs to (1, 2, 3). For components with a single fluid stream, such as a fan, set this to one for the inlet and outlet nodes. For components with multiple fluid streams, such as a water coil, matching inlets and outlets should use the same fluid stream number. For example, the air inlet and air outlet would be stream 1, and the water inlet and water outlet would be stream 2. This information is used to generate the list of Parent and Non-Parent Node Connections in the bnd output file. This list is used by the HVAC Diagram utility.

ObjectIsParent[LINK]

True If the object is a parent object, false if not. Parameters are defined in DataLoopNode. As of version 1.2.0, the current list of choices is:

! Valid IsParent Types for Node Connections

LOGICAL, PARAMETER :: ObjectIsParent = .TRUE.

LOGICAL, PARAMETER :: ObjectIsNotParent = .FALSE.

What is a parent object? A parent object is one which encloses and references other objects. For example, FAN COIL UNIT:4 PIPE is a parent to a fan, a heating coil, a cooling coil, and an outside air mixer. In most cases, all nodes referenced by a parent object are duplicated in the non-parent objects which are the components which ultimately act on the fluid stream. From the perspective of the HVAC Diagram utility, every fluid loop must be a continuous connection of non-parent objects and zones. In this example, the nodes of the mixer, fan, coils, and zone form a complete loop. Some components, such as UNIT VENTILATOR are part parent and part non-parent. It is a parent to a fan, a heating coil, and a cooling coil, but it does not reference an explicit outside air mixer. The mixer is an implied component within the unit ventilator. In these cases, to facilitate drawing a loop in HVAC Diagram, it is necessary to create a non-parent component to carry the fluid. So, the unit ventilator uses the following approach as illustrated by the comments and source code. Note that Alphas(3), the air inlet node, is registered twice, once as an inlet to parent object UNIT VENTILATOR, and once as an inlet to the implicit non-parent object UNIT VENTILATOR-OA MIXER.

Excerpt from GetUnitVentilatorInput in UnitVentilator

! Main air nodes (except outside air node):

! For node connections, this object is both a parent and a non-parent, because the

! OA mixing box is not called out as a separate component, its nodes must be connected

! as ObjectIsNotParent. But for the fan and coils, the nodes are connected as ObjectIsParent

! To support the diagramming tool, the unit ventilator inlet node must appear both as

! an inlet to the unit ventilator parent object and as an inlet to the implied

! non-parent OA mixing box within the unit ventilator.

! Because there is overlap between the nodes that are parent and non-parent, use a different

! object type for the non parent nodes

UnitVent(UnitVentNum)%AirInNode = &

GetOnlySingleNode(Alphas(3),ErrorsFound,‘UNIT VENTILATOR’,Alphas(1), &

NodeType_Air,NodeConnectionType_Inlet,1,ObjectIsParent)

UnitVent(UnitVentNum)%AirInNode = &

GetOnlySingleNode(Alphas(3),ErrorsFound,‘UNIT VENTILATOR-OA MIXER’,Alphas(1), &

NodeType_Air,NodeConnectionType_Inlet,1,ObjectIsNotParent)

UnitVent(UnitVentNum)%AirOutNode = &

GetOnlySingleNode(Alphas(4),ErrorsFound,‘UNIT VENTILATOR’,Alphas(1), &

NodeType_Air,NodeConnectionType_Outlet,1,ObjectIsParent)

UnitVent(UnitVentNum)%FanOutletNode = &

GetOnlySingleNode(Alphas(5),ErrorsFound,‘UNIT VENTILATOR’,Alphas(1), &

NodeType_Air,NodeConnectionType_Internal,1,ObjectIsParent)

GetOnlySingleNode[LINK]

This is used when only one node is expected as the input point. If this name points to a NodeList, an appropriate error message will be issued and errFlag (the second argument) will be set .true.

GetOnlySingleNode(NodeName,errFlag,NodeObjectType,NodeObjectName,NodeFluidType,NodeConnectionType,NodeFluidStream,ObjectIsParent)

It is used:

Example:

USE NodeInputManager, ONLY: GetOnlySingleNode

GetNodeNums[LINK]

This is used when more than one node is valid for an input. Like the GetOnlySingleNode invocation, GetNodeNums needs the extra information for a node:

SUBROUTINE GetNodeNums(Name,NumNodes,NodeNumbers,ErrorsFound, &

NodeFluidType,NodeObjectType,NodeObjectName, &

NodeConnectionType,NodeFluidStream,ObjectIsParent)

Example:

USE NodeInputManager, ONLY: GetNodeNums

Unique Node Checking[LINK]

A set of routines will allow you to use the NodeInputManager to check for unique node names across a set of inputs. This is used currently in the CONTROLLED ZONE EQUIP CONFIGURATION object where each zone node mentioned must be unique. Three routines comprise the unique node check: InitUniqueNodeCheck, CheckUniqueNodes, EndUniqueNodeCheck

InitUniqueNodeCheck[LINK]

A call to this routine starts the collection and detection of unique/non-unique nodes by the NodeInputManager:

USE NodeInputManager, ONLY: InitUniqueNodeCheck, CheckUniqueNodes, &

EndUniqueNodeCheck

CheckUniqueNodes[LINK]

SUBROUTINE CheckUniqueNodes(NodeTypes,CheckType,ErrorsFound, &

CheckName,CheckNumber)

This is the routine called during the getting of the nodes. The CheckType argument can be ‘Nodename’ or ‘NodeNumber’ and then pass in the appropriate argument to CheckName or CheckNumber. CheckName and CheckNumber are optional arguments – only the necessary one need be supplied.

Argument 1, NodeTypes, is the type of node being looked for – this argument is used for error messages within the NodeInput processing. Argument 2, ErrorsFound, will be set to true of this node is not unique in the current context.

Example:

UniqueNodeError = .false.

CALL CheckUniqueNodes(’Zone Air Node’,‘NodeName’,UniqueNodeError, &

CheckName = AlphArray(5))

IF (UniqueNodeError) THEN

CALL ShowContinueError(‘Occurs for Zone =’//TRIM(AlphArray(1)))

ErrorsFound = .true.

ENDIF

EndUniqueNodeCheck[LINK]

This routine terminates the unique node check – allows arrays to be deallocated, etc.

CALL EndUniqueNodeCheck(‘CONTROLLED ZONE EQUIP CONFIGURATION’)

The only argument is the Context String – which must match the string given in the InitUniqueNodeCheck routine.

SetUpCompSets and TestCompSet[LINK]

SetUpCompSets and TestCompSet are used to develop a list of hierarchical relationships between HVAC objects. The CompSet routines are housed in the BranchInputManager. A list of component sets is built which contains the following information:

Parent Object Type (Currently cannot be SPLITTER or MIXER)

Parent Object Name

Child Component Type (Currently cannot be SPLITTER or MIXER)

Child Component Name

Child Component InletNodeName

Child Component OutletNodeName

Node Description

Parent and child refer to a hierarchical relationship of two HVAC objects. For example, a branch is the parent to a pump, and a fan coil is the parent to a fan. The component sets do not include peer-to-peer connections such as a splitter connected to a branch, or a zone supply air path connected to an air loop.

The following rules apply to component sets:

• Each parent/child component set is unique. The same pair of components should never appear in the component sets list more than once.

• Each set of child component plus inlet and outlet nodes is unique.

• Each child component must have a parent component.

• A given component may appear in multiple component sets as a parent component.

• A given component may appear in multiple component sets as a child component only if there is a different set of inlet/outlet nodes. (This was originally the intent, but some new components do not fit this rule well and it may need to be relaxed.)

• If a given node name appears more than once as an inlet node, the two components which use it must share a parent/child relationship.

• If a given node name appears more than once as an outlet node, the two components which use it must share a parent/child relationship.

• After the program has read all the input data, there should be no “UNDEFINED” values in the list of component sets.

When any of these rules are violated, a warning is issued indicating a possible node connection error.

** Warning ** Potential Node Connection Error for object PIPE, name = CW_BYPASS

** _~ ** Node Types are still UNDEFINED – See Branch/Node Details file for further information

** _~ ** Inlet Node : CW_BYPASS_INLET

** _~ ** Outlet Node: CW_BYPASS_OUTLET

The component sets are reported in the eplusout.bnd file:

! <Component Set>,<Component Set Count>,<Parent Object Type>,<Parent Object Name>,<Component Type>,<Component Name>,<Inlet Node ID>,<Outlet Node ID>,<Description>

Component Set,1,BRANCH,COOLING SUPPLY INLET BRANCH,PUMP:VARIABLE SPEED,CHW CIRC PUMP,CHW SUPPLY INLET NODE,CHW PUMP OUTLET NODE,Water Nodes

Component Set,21,FAN COIL UNIT:4 PIPE,ZONE1FANCOIL,FAN:SIMPLE:CONSTVOLUME,ZONE1FANCOILFAN,ZONE1FANCOILOAMIXEROUTLETNODE,ZONE1FANCOILFANOUTLETNODE,Air Nodes

SetUpCompSets[LINK]

SetUpCompSets should be called any time a parent object such as a branch or a compound object (e.g. furnace) references a child component which is connected to it. If an object has more than one child component, then SetUpCompSets is called once for each child.

SetUpCompSets first looks for the child component in the existing list of component sets by looking for a matching component type and name. If it is found, then the parent name and type are filled in. If the child component is not found is the exisiting list, then a new component set is created.

SUBROUTINE SetUpCompSets(ParentType,ParentName,CompType,CompName,InletNode,OutletNode,Description)

The arguments are:

ParentType Parent Object Type

ParentName Parent Object Name

CompType Child Component Type

CompName Child Component Name

InletNode Child Component Inlet Node Name

OutletNode Child Component Outlet Node Name

Description Description of nodes (optional)

For example, AirLoopHVAC:Unitary:Furnace:HeatOnly references a fan and a heating coil:

AirLoopHVAC:Unitary:Furnace:HeatOnly,

\memo identical to the AirLoopHVAC:UnitaryHeatOnly object

\min-fields 13

A1, \field Name

\required-field

\type alpha

A2, \field Availability Schedule Name

\required-field

\type object-list

\object-list ScheduleNames

A3, \field Furnace Air Inlet Node Name

\required-field

\type node

A4, \field Furnace Air Outlet Node Name

\required-field

\type node

A5, \field Supply Air Fan Operating Mode Schedule Name

\type object-list

\object-list ScheduleNames

\note A fan operating mode schedule value of 0 indicates cycling fan mode (supply air

\note fan cycles on and off in tandem with the heating coil).

\note Any other schedule value indicates continuous fan mode (supply air fan operates

\note continuously regardless of heating coil operation).

\note Leaving this schedule name blank will default to cycling fan mode for the

\note entire simulation period.

N1, \field Maximum Supply Air Temperature

\type real

\units C

\autosizable

\default 80.0

N2, \field Supply Air Flow Rate

\required-field

\type real

\note This value should be > 0 and < = than the fan air flow rate.

\units m3/s

\minimum> 0.0

\autosizable

A6, \field Controlling Zone or Thermostat Location

\required-field

\type object-list

\object-list ZoneNames

A7, \field Supply Fan Object Type

\required-field

\type choice

\key Fan:OnOff

\key Fan:ConstantVolume

\note Fan:ConstantVolume only works with continuous fan operating mode (i.e. fan

\note operating mode schedule values are greater than 0).

A8, \field Supply Fan Name

\required-field

\type object-list

\object-list FansCVandOnOff

A9 , \field Fan Placement

\type choice

\key BlowThrough

\key DrawThrough

\default BlowThrough

A10, \field Heating Coil Object Type

\required-field

\type choice

\key Coil:Heating:Fuel

\key Coil:Heating:Electric

\key Coil:Heating:Water

\key Coil:Heating:Steam

\note works with gas, electric, hot water and steam heating coils

A11; \field Heating Coil Name

\required-field

\type object-list

\object-list HeatingCoilName

In this case, the furnace is the parent object to the fan and the heating coil. To set up the component set for the furnace and its fan, the furnace type and name, the fan type and name (A7 and A8), and the furnace/fan inlet and fan outlet nodes (A3 and A9) are passed to SetUpCompSets:

Example:

USE BranchInputManager, ONLY: SetUpCompSets

TestCompSet[LINK]

TestCompSet should be called by every HVAC object which has a parent object. A given object may be both a parent and a child. For example, AirLoopHVAC:Unitary:Furnace:HeatOnly is a child to a branch and a parent to a fan and coils.

TestCompSet first looks for the calling component in the existing list of component sets by looking for a matching component type and name. If the found compset has inlet and outlet nodes defined, then these must also match. If a match is found, then any undefined node names are filled in and the description string for the nodes is added. If the component is not found, then a new component set is created with undefined parent object type and name.

SUBROUTINE TestCompSet(CompType,CompName,InletNode,OutletNode,Description)

The arguments are:

• CompType Child Component Type

• CompName Child Component Name

• InletNode Child Component Inlet Node Name

• OutletNode Child Component Outlet Node Name

• Description Description of nodes

For example, AirLoopHVAC:Unitary:Furnace:HeatOnly is a child component with inlet and outlet nodes:

AirLoopHVAC:Unitary:Furnace:HeatOnly,

\memo identical to the AirLoopHVAC:UnitaryHeatOnly object

\min-fields 14

A1, \field Name

\required-field

\type alpha

A2, \field Availability Schedule Name

\required-field

\type object-list

\object-list ScheduleNames

A3, \field Furnace Air Inlet Node Name

\required-field

\type alpha

A4, \field Furnace Air Outlet Node Name

\required-field

\type alpha

To register the component set for the furnace (as a child component), the furnace type and name, and the furnace inlet and outlet nodes (A3 and A4) along with a node descriptor are passed to TestCompSets:

Example:

USE BranchInputManager, ONLY: TestCompSet

CALL TestCompSet (Furnace(FurnaceNum)%FurnaceType,AlphArray(1), &

AlphArray(3),AlphArray(4),‘Air Nodes’)

CheckOutAirNodeNumber[LINK]

Outside Air Nodes are special nodes connected to the outside environment. With the introduction of the Site Atmospheric Variation parameters, it becomes important to know whether the node name (e.g. Condenser Inlet Node on Air Cooled Chillers) is a legitimate outside air node or not. CheckOutAirNodeNumber allows you to determine if an entered node is, in fact, a proper outside air node.

Declaration:

FUNCTION CheckOutAirNodeNumber(NodeNumber) RESULT(Okay)

Example:

USE OutAirNodeManager, ONLY: CheckOutAirNodeNumber

! outdoor condenser node

IF (lAlphaBlanks(10)) THEN

DXCoil(DXCoilNum)%CondenserInletNodeNum(1) = 0

ELSE

DXCoil(DXCoilNum)%CondenserInletNodeNum(1) = &

GetOnlySingleNode(Alphas(10),ErrorsFound,TRIM(CurrentModuleObject),DXCoil(DXCoilNum)%Name, &

NodeType_Air,NodeConnectionType_OutsideAirReference,1,ObjectIsNotParent)

IF (.not. CheckOutAirNodeNumber(DXCoil(DXCoilNum)%CondenserInletNodeNum(1))) THEN

CALL ShowWarningError(RoutineName//trim(CurrentModuleObject)//‘= “’//trim(DXCoil(DXCoilNum)%Name)//”’, may be invalid’)

CALL ShowContinueError(TRIM(cAlphaFields(10))//’ = “’//TRIM(Alphas(10))// &

’“, node does not appear in an OutdoorAir:NodeList or as an OutdoorAir:Node.’)

CALL ShowContinueError(‘This node needs to be included in an air system or the coil model will not be valid’ &

//‘, and the simulation continues’)

END IF

ENDIF

Note that GetOnlySingleNode is used to get the proper node number, then the node number is used in the outside air node verification.

CheckAndAddAirNodeNumber[LINK]

Should you feel really nice about your users (or more likely be updating older code that may have allowed blanks in places that are properly outside air nodes), you can use the CheckAndAddAirNodeNumber routine to not only check to see if it is an outside air node but also add it at the same time.

Declaration:

SUBROUTINE CheckAndAddAirNodeNumber(NodeNumber,Okay)

USE OutAirNodeManager, ONLY: CheckAndAddAirNodeNumber

Example:

ElectricChiller(ChillerNum)%CondInletNodeNum = &

GetOnlySingleNode(AlphArray(5),ErrorsFound, &

‘Chiller:Electric’,AlphArray(1), NodeType_Air, &

NodeConnectionType_OutsideAirReference, 2, ObjectIsNotParent)

CALL CheckAndAddAirNodeNumber( &

ElectricChiller(ChillerNum)%CondInletNodeNum, &

Okay)

IF (.not. Okay) THEN

CALL ShowWarningError(‘Chiller:Electric, Adding Outside Air Node =’// &

AlphArray(5)))

ENDIF

Note that here “not Okay” is not an error condition but rather the opportunity to notify the user that you are adding an air node.