Difference between revisions of "CISM simple glide flow diagram I"

From Interactive System for Ice sheet Simulation
Jump to: navigation, search
Line 1: Line 1:
Conceptual description of code linkages necessary to build the executable file '''simple_glide'''. Black ".F90" text denotes actual file names (most live in the ''libglide/'' subdirectory) where various subroutines live (shown in red) and where calls to other subroutines (shown in green) are made. Arrows denote dependency on subroutines in other modules, which are generally accessed through the Fortran "use" statement. For example, '''simple_glide.F90''' contains a call to evolve the temperature. The subroutine being called lives in '''glide.F90'''. In turn, that subroutine makes a call out to a driver subroutine that lives in '''glide_temp.F90''', which may have further dependencies in other modules.
+
Conceptual description of code linkages necessary to build the executable file '''simple_glide'''. Black ".F90" text denotes actual file names (most live in the ''libglide/'' subdirectory) where various subroutines live (shown in red) and where calls to other subroutines (shown in green) are made. Arrows denote dependency on subroutines in other modules, which are generally accessed through the Fortran "use" statement. For example, '''simple_glide.F90''' contains a call to evolve the temperature. The subroutine being called lives in '''glide.F90'''. In turn, that subroutine makes a call out to a driver subroutine that lives in '''glide_temp.F90''', which may have further dependencies in other modules. A similar figure with specific subroutine calls can be found [[CISM simple glide flow diagram II | here.]]
  
 
[[Image:simple_glide_flow_generic.png ]]
 
[[Image:simple_glide_flow_generic.png ]]

Revision as of 13:53, 16 March 2011

Conceptual description of code linkages necessary to build the executable file simple_glide. Black ".F90" text denotes actual file names (most live in the libglide/ subdirectory) where various subroutines live (shown in red) and where calls to other subroutines (shown in green) are made. Arrows denote dependency on subroutines in other modules, which are generally accessed through the Fortran "use" statement. For example, simple_glide.F90 contains a call to evolve the temperature. The subroutine being called lives in glide.F90. In turn, that subroutine makes a call out to a driver subroutine that lives in glide_temp.F90, which may have further dependencies in other modules. A similar figure with specific subroutine calls can be found here.

Simple glide flow generic.png