You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -63,26 +63,18 @@ In your `.bashrc` or `.tcshrc` or other rc file add a line:
63
63
64
64
##### NCCS
65
65
66
-
NCCS currently has two different OSs. So you'll need to use different modulefiles depending on which OS you are using.
67
-
68
-
###### SLES 12
69
-
70
-
```
71
-
module use -a /discover/swdev/gmao_SIteam/modulefiles-SLES12
72
-
```
73
-
74
-
###### SLES 15
75
-
76
66
```
77
67
module use -a /discover/swdev/gmao_SIteam/modulefiles-SLES15
78
68
```
79
69
80
70
##### NAS
71
+
81
72
```
82
73
module use -a /nobackup/gmao_SIteam/modulefiles
83
74
```
84
75
85
76
##### GMAO Desktops
77
+
86
78
On the GMAO desktops, the SI Team modulefiles should automatically be
87
79
part of running `module avail` but if not, they are in:
88
80
@@ -180,16 +172,12 @@ This will set up `mepo` to use blobless clones for all future clones by adding a
180
172
181
173
### Single Step Building of the Model
182
174
183
-
If all you wish is to build the model, you can run `parallel_build.csh` from a head node. Doing so will checkout all the external repositories of the model and build it. When done, the resulting model build will be found in `build/` and the installation will be found in `install/` with setup scripts like `gcm_setup` and `fvsetup` in `install/bin`.
184
-
185
-
#### Building at NCCS (Multiple OSs)
186
-
187
-
In all the examples below, NCCS builds will act differently. Because NCCS currently has two different OSs, when you use
188
-
`parallel_build.csh` you will see that the `build` and `install` directories will be appended with `-SLES12` or `-SLES15` depending
189
-
on where you submitted to. When NCCS moves to a single OS again, this will be removed.
175
+
If all you wish is to build the model, you can run:
176
+
```
177
+
./parallel_build.csh
178
+
```
190
179
191
-
Note that if you use the `-builddir` and `-installdir` options, you can override this behavior and no OS will be automatically
192
-
appended.
180
+
from a login node. Doing so will checkout all the external repositories of the model and build it. When done, the resulting model build will be found in `build/` and the installation will be found in `install/` with setup scripts like `gcm_setup` and `fvsetup` in `install/bin`.
193
181
194
182
#### Develop Version of GEOS GCM
195
183
@@ -267,6 +255,7 @@ each sub-repository.
267
255
#### Build the Model
268
256
269
257
##### Load Compiler, MPI Stack, and Baselibs
258
+
270
259
On tcsh:
271
260
```
272
261
source @env/g5_modules
@@ -277,24 +266,39 @@ source @env/g5_modules.sh
277
266
```
278
267
279
268
##### Create Build Directory
280
-
We currently do not allow in-source builds of GEOSgcm. So we must make a directory:
281
-
```
282
-
mkdir build
283
-
```
284
-
The advantages of this is that you can build both a Debug and Release version with the same clone if desired.
285
269
286
270
##### Run CMake
287
-
CMake generates the Makefiles needed to build the model.
271
+
272
+
CMake generates the Makefiles needed to build the model. This command:
This will install to a directory parallel to your `build` directory. If you prefer to install elsewhere change the path in:
276
+
277
+
As is, this command assumes you are in the root of the GEOSgcm checkout and will create a `build/` directory in the root of the checkout and install into `install/ parallel to the `build/` directory.
278
+
279
+
This command has three options:
280
+
281
+
1.`-B` specifies the build directory.
282
+
2.`-S` specifies the source directory (root of the checkout).
283
+
3.`-DCMAKE_INSTALL_PREFIX` specifies the installation directory.
284
+
285
+
If you prefer to install elsewhere change the path in:
286
+
293
287
```
294
-
-DCMAKE_INSTALL_PREFIX=<path>
288
+
-DCMAKE_INSTALL_PREFIX=/path/to/install
295
289
```
296
290
and CMake will install there.
297
291
292
+
If you prefer your build somewhere else, you can specify that with:
293
+
```
294
+
-B /path/to/build
295
+
```
296
+
297
+
Finally, if your source is in a different directory than the current one, you can specify that with:
298
+
```
299
+
-S /path/to/source
300
+
```
301
+
298
302
###### Create and install source tarfile
299
303
300
304
Note that running with `parallel_build.csh` will create and install a tarfile of the source code at build time. But if CMake is run by hand, this is not the default action (as many who build with CMake by hand are developers and not often running experiments). In order to enable this at install time, add:
@@ -303,17 +307,20 @@ Note that running with `parallel_build.csh` will create and install a tarfile of
303
307
```
304
308
to your CMake command.
305
309
306
-
##### Build and Install with Make
310
+
##### Build and Install
311
+
307
312
```
308
-
make -jN install
313
+
cmake --build build -j N
314
+
cmake --install build
309
315
```
316
+
310
317
where `N` is the number of parallel processes. On discover head nodes, this should only be as high as 2 due to limits on the head nodes. On a compute node, you can set `N` has high as you like, though 8-12 is about the limit of parallelism in our model's make system.
311
318
312
319
### Run the GCM
313
320
314
321
Once the model has built successfully, you will have an `install/` directory in your checkout. To run `gcm_setup` go to the `install/bin/` directory and run it there:
0 commit comments