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 CostInfoOut
! SUBROUTINE INFORMATION:
! AUTHOR Brent Griffith
! DATE WRITTEN April 2003
! MODIFIED na
! RE-ENGINEERED na
! PURPOSE OF THIS SUBROUTINE:
! This subroutine produces a file with information about surfaces.
! for the purpose of producing first cost estimates to include in objective value functions
! for design optimization
! METHODOLOGY EMPLOYED:
! Access data in DataSurfaces and report
! REFERENCES:
! na
! USE STATEMENTS:
USE DataPrecisionGlobals
USE DataHeatBalance
USE DataSurfaces
USE DataInterfaces, ONLY: ShowFatalError
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:
integer unit ! Unit number on which to write file
integer surf ! Loop variable for surfaces
integer, external :: getnewunitnumber ! External function for a new unit number
Logical,ALLOCATABLE, DIMENSION(:) :: uniqueSurf
integer write_stat
if (totsurfaces > 0 .and. .not. allocated(surface)) then
! no error needed, probably in end processing, just return
return
endif
! need to determine unique surfacs... some surfaces are shared by zones and hence doubled
Allocate(uniqueSurf(TotSurfaces))
uniqueSurf = .true.
do surf=1, TotSurfaces
If (surface(surf)%ExtBoundCond > 0) then
If (surface(surf)%ExtBoundCond < surf) then !already cycled through
uniqueSurf(surf) = .false.
endif
endif
If ( surface(surf)%Construction == 0) then !throw out others for now
uniqueSurf(surf) = .false.
endif
enddo
unit=getnewunitnumber()
! .sci = surface cost info
open(unit,file='eplusout.sci', Action='write', iostat=write_stat)
if (write_stat /= 0) then
CALL ShowFatalError('CostInfoOut: Could not open file "eplusout.sci" for output (write).')
endif
write(unit, *) totsurfaces , count(uniqueSurf)
write(unit, *) 'data for surfaces useful for cost information'
write(unit, *) 'Number, Name, Construction, class, area, grossarea'
do surf=1,TotSurfaces
!if (surface(surf)%class .eq. SurfaceClass_IntMass) CYCLE
If (.not. uniqueSurf(surf)) cycle
! why the heck are constructions == 0 ?
If ( surface(surf)%Construction /= 0) then
write(unit, 801) surf, trim(surface(surf)%name), trim(Construct(surface(surf)%Construction)%name), &
trim(cSurfaceClass(surface(surf)%class)), surface(surf)%Area, surface(surf)%GrossArea
endif
enddo
801 format(I5,',',A,',',A,',',A, ',',f14.5,',',f14.5 )
close(unit)
deallocate(uniqueSurf)
return
END SUBROUTINE CostInfoOut