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 CheckWeatherFileValidity
! SUBROUTINE INFORMATION:
! AUTHOR Linda Lawrie
! DATE WRITTEN February 1977
! MODIFIED June 1997 (RKS)
! RE-ENGINEERED na
! PURPOSE OF THIS SUBROUTINE:
! This subroutine contains a portion of the legacy subroutine CKBLDE.
! The main purpose of this routine is to check the validity of the
! weather dates provided by the user and the attached weather file.
! These functions may eventually be pushed to an interface. This
! routine also sends the weather file header information at the
! Environment derived type.
! METHODOLOGY EMPLOYED:
! na
! REFERENCES:
! Legacy subroutine CKBLDE.
! USE STATEMENTS:
USE General, ONLY: JulianDay
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:
! na
! FLOW:
ErrorInWeatherFile=.FALSE.
IF (.not. WeatherFileExists) THEN ! No weather file exists but the user requested one--print error message
IF (DoWeathSim) THEN
CALL ShowWarningError('Weather Environment(s) requested, but no weather file found')
ErrorInWeatherFile=.TRUE.
ENDIF
END IF ! ... end of WeatherFileExists IF-THEN
RETURN
END SUBROUTINE CheckWeatherFileValidity