-
Notifications
You must be signed in to change notification settings - Fork 318
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Start bounds at 1; remove references to MCT Users: take note of (1), and in particular the caveat for users noted below (in the "Notes of particular relevance for users"). (1) All global index arrays on a given processor now have a starting index of 1 - bounds_proc for each subgrid level has a starting index of 1 for each level - bounds_clump for each subgrid level has a starting index of 1 for just the first clump on the processor - but all the other clumps on the processor do not start at 1 - but rather are offset with the number of gridcells, columns, ...etc on the preceeding clumps (2) There are no longer any references to any mct data structures other than in the mct cap - All references to gsmap have been removed from decompMod.F90 and replaced with new global index arrays for the various subgrid levels - decompInitMod has been refactored to calculated these global index arrays using pure MPI rather than mct - ncdio_pio_F90.in has been refactored to use the new global index arrays rather than the gsmap data structures - the data struture ldecomp is no longer needed - the module spmdGathScatMod.F90 is no longer needed and has been removed
- Loading branch information
Showing
26 changed files
with
929 additions
and
1,501 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.