Nodes of different colours represent the following:
Solid arrows point from a parent (sub)module to the submodule which is descended from it. Dashed arrows point from a module being used to the module or program unit using it. Where possible, edges connecting nodes are given different colours to make them easier to distinguish in large graphs.
Nodes of different colours represent the following:
Solid arrows point from a procedure to one which it calls. Dashed arrows point from an interface to procedures which implement that interface. This could include the module procedures in a generic interface or the implementation in a submodule of an interface in a parent module. Where possible, edges connecting nodes are given different colours to make them easier to distinguish in large graphs.
Nodes of different colours represent the following:
Solid arrows point from a procedure to one which it calls. Dashed arrows point from an interface to procedures which implement that interface. This could include the module procedures in a generic interface or the implementation in a submodule of an interface in a parent module. Where possible, edges connecting nodes are given different colours to make them easier to distinguish in large graphs.
SUBROUTINE ManageHeatBalance
! SUBROUTINE INFORMATION:
! AUTHOR Rick Strand
! DATE WRITTEN January 1997
! MODIFIED February 1998 Richard Liesen
! RE-ENGINEERED na
! PURPOSE OF THIS SUBROUTINE:
! This subroutine manages the heat balance method of calculating
! building thermal loads. It is called from the SimulationManager
! at the time step level. This driver manages the calls to all of
! the other modules, drivers, and simulation algorithms.
! METHODOLOGY EMPLOYED:
! The order of this routine was taken from HeatBalanceModule with routine
! and Data Structuring
! REFERENCES:
! Legacy code from (I)BLAST, subroutine SIMZGD.
! USE STATEMENTS:
USE HeatBalanceSurfaceManager
USE EMSManager , ONLY: ManageEMS, UpdateEMSTrendVariables
USE DataGlobals, ONLY: emsCallFromEndZoneTimestepBeforeZoneReporting, emsCallFromEndZoneTimestepAfterZoneReporting, &
emsCallFromBeginNewEvironmentAfterWarmUp
IMPLICIT NONE ! Enforce explicit typing of all variables in this routine
! SUBROUTINE ARGUMENT DEFINITIONS:
! na
! SUBROUTINE PARAMETER DEFINITIONS:
! na
! INTERFACE BLOCK SPECIFICATIONS:
! na
! DERIVED TYPE DEFINITIONS:
! na
! SUBROUTINE LOCAL VARIABLE DECLARATIONS:
LOGICAL,SAVE :: GetInputFlag=.true.
! FLOW:
! Get the heat balance input at the beginning of the simulation only
IF (GetInputFlag) THEN
CALL GetHeatBalanceInput ! Obtains heat balance related parameters from input file
GetInputFlag=.false.
ENDIF
! These Inits will still have to be looked at as the routines are re-engineered further
CALL InitHeatBalance ! Initialize all heat balance related parameters
! Solve the zone heat balance by first calling the Surface Heat Balance Manager
! and then the Air Heat Balance Manager is called by the Surface Heat Balance
! Manager. The order of execution is still important and the zone cannot
! go through any record keeping before the HVAC system has run because there
! may be a radiant system in the building which will require iteration between
! the HVAC system (called from the Air Heat Balance) and the zone (simulated
! in the Surface Heat Balance Manager). In the future, this may be improved.
CALL ManageSurfaceHeatBalance
CALL ManageEMS(emsCallFromEndZoneTimestepBeforeZoneReporting) ! EMS calling point
CALL RecKeepHeatBalance ! Do any heat balance related record keeping
! This call has been moved to the FanSystemModule and does effect the output file
! You do get a shift in the Air Handling System Summary for the building electric loads
! IF ((.NOT.WarmupFlag).AND.(DayOfSim.GT.0)) CALL RCKEEP ! Do fan system accounting (to be moved later)
CALL ReportHeatBalance ! Manage heat balance reporting until the new reporting is in place
CALL ManageEMS(emsCallFromEndZoneTimestepAfterZoneReporting) ! EMS calling point
CALL UpdateEMSTrendVariables
IF (WarmupFlag.AND.EndDayFlag) THEN
CALL CheckWarmupConvergence
IF (.NOT.WarmupFlag) THEN
DayOfSim = 0 ! Reset DayOfSim if Warmup converged
DayOfSimChr='0'
CALL ManageEMS(emsCallFromBeginNewEvironmentAfterWarmUp) ! calling point
END IF
END IF
IF (.not. WarmupFlag .and. EndDayFlag .and. DayOfSim == 1 .and. .not. DoingSizing) THEN
CALL ReportWarmupConvergence
ENDIF
RETURN
END SUBROUTINE ManageHeatBalance