-
Notifications
You must be signed in to change notification settings - Fork 11
remove SLES12 from readme #797
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -18,12 +18,11 @@ module use -a (path) | |
| module load GEOSenv | ||
| ``` | ||
|
|
||
| where `(path)` depends on the computing system; at NCCS, `(path)` also depends on the operating system (SLES12 on Skylake and Cascade Lake nodes; SLES15 on Milan nodes, as of Jan. 2024): | ||
| where `(path)` depends on the computing system: | ||
|
|
||
| | System | Path | | ||
| | ------------- |---------------------------------------------------| | ||
| | NCCS Discover | `/discover/swdev/gmao_SIteam/modulefiles-SLES12` | | ||
| | | `/discover/swdev/gmao_SIteam/modulefiles-SLES15` | | ||
| | NCCS Discover | `/discover/swdev/gmao_SIteam/modulefiles-SLES15` | | ||
| | NAS | `/nobackup/gmao_SIteam/modulefiles` | | ||
| | GMAO desktops | `/ford1/share/gmao_SIteam/modulefiles` | | ||
|
|
||
|
|
@@ -46,15 +45,13 @@ git clone -b v17.9.1 --single-branch git@github.com:GEOS-ESM/GEOSldas.git | |
| To build the model in a single step, do the following from a head node: | ||
| ``` | ||
| cd ./GEOSldas | ||
| parallel_build.csh | ||
| ./parallel_build.csh -mil | ||
| ``` | ||
| This checks out all the external repositories of the model (albeit only on the first run, [see subsection on mepo below](#mepo)!) and then builds and installs the model. | ||
|
|
||
| At **NCCS**, the default is to build GEOSldas on SLES12 (Skylake or Cascade Lake nodes); to build GEOSldas on SLES15 (Milan nodes), use `parallel_build.csh -mil`. | ||
| The resulting model build is found in `build-SLES15/`, and the installation is found in `install-SLES15/`, with setup scripts like `ldas_setup` in `install-SLES15/bin`. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm a bit confused by the build and install directory names, which may be outdated. When I look at the build of the LDAS nightly tests, there's not "-SLES15" in the directory names: |
||
|
|
||
| The resulting model build is found in `build[-SLESxx]/`, and the installation is found in `install[-SLESxx]/`, with setup scripts like `ldas_setup` in `install[-SLESxx]/bin`. | ||
|
|
||
| To obtain a build that is suitable for debugging, use `parallel_build.csh -debug`, which builds in `build-Debug[-SLESxx]/` and installs in `install-Debug[-SLESxx]/`. There is also an option for aggressive optimization. For details, see the [GEOSldas Wiki](https://github.com/GEOS-ESM/GEOSldas/wiki). | ||
| To obtain a build that is suitable for debugging, use `./parallel_build.csh -debug -mil`, which builds in `build-Debug-SLES15/` and installs in `install-Debug-SLES15/`. There is also an option for aggressive optimization. For details, see the [GEOSldas Wiki](https://github.com/GEOS-ESM/GEOSldas/wiki). | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. see comments above re. the |
||
|
|
||
| Instructions for building the model in multiple steps are provided below. | ||
|
|
||
|
|
@@ -63,12 +60,12 @@ Instructions for building the model in multiple steps are provided below. | |
| ## How to Set Up (Configure) and Run GEOSldas | ||
|
|
||
|
|
||
| a) At **NCCS**, GEOSldas must be built, configured, and run on the same operating system. To run GEOSldas on Milan nodes (SLES15), start with `ssh discover-mil`. | ||
| a) To run GEOSldas on Milan nodes (SLES15), start with `ssh discover-mil`. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do we need the |
||
|
|
||
| b) Set up the job as follows: | ||
|
|
||
| ``` | ||
| cd (build_path)/GEOSldas/install[-SLESxx]/bin | ||
| cd (build_path)/GEOSldas/install-SLES15/bin | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. see comment above re. |
||
| source g5_modules [for bash or zsh: source g5_modules.[z]sh] | ||
| ./ldas_setup setup [-v] (exp_path) ("exe"_input_filename) ("bat"_input_filename) | ||
| ``` | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess initially we will keep using
-mil, but looking ahead, do we really need to have the-milflag for parallel_build.csh if there's only SLES15?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we will see how build.csh handle the default. @mathomp4