11 |
was a convenient method for both segregating and rapidly including or |
was a convenient method for both segregating and rapidly including or |
12 |
excluding parameterizations during the software build process. |
excluding parameterizations during the software build process. |
13 |
|
|
14 |
Over time, package use increased. The number of packages has grown |
Over time, package use has increased. The number of packages has |
15 |
and they have evolved to contain much of the model functionality |
grown and they have evolved to contain much of the model functionality |
16 |
including momentum schemes, I/O utilities, diagnostics, ``exchange'' |
including momentum schemes, I/O utilities, diagnostics, ``exchange'' |
17 |
algorithms, and numerous other processes that have no direct |
algorithms for domain decomposition, and numerous physical |
18 |
connection to any specific physical parameterizations. The following |
parameterizations. The following sections describe how to use the |
19 |
sections describe how to use the existing packages and how to modify |
existing packages and how to modify them and create new ones. |
|
them or create new ones. |
|
20 |
|
|
21 |
%% In this chapter the schemes for parameterizing processes that are not |
%% In this chapter the schemes for parameterizing processes that are not |
22 |
%% represented explicitly in MITgcm are described. Some of these |
%% represented explicitly in MITgcm are described. Some of these |