Changes between Version 6 and Version 7 of Users/ModelInstall
- Timestamp:
- 2017-04-12T18:55:19+02:00 (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Users/ModelInstall
v6 v7 10 10 == 2. Extract and install XIOS 11 11 12 {{{#!div class="important" 13 (Nicolas) '''Will not be online after the switch!!!''' 14 12 15 [http://www.nemo-ocean.eu/Using-NEMO/User-Guides/Basics/XIOS-IO-server-installation-and-use Document here] (and come back to this page afterwards to create NEMO executable!) 16 }}} 13 17 14 18 == 3. Compile and create NEMO executable … … 22 26 === More options 23 27 24 * `–n` CONFIG: for configuration name, existant or new config to install25 * `–m` COMPILER: compiler choice (use files names in `NEMOGCM/ARCH`, see examples below)28 * `–n` [CONFIG]: for configuration name, existant or new config to install 29 * `–m` [COMPILER]: compiler choice (use files names in `NEMOGCM/ARCH`, see examples below) 26 30 * `–h`: help 27 * `–r` REFCONFIG: reference configuration as first guess when installing a new one28 * `–j` : number of processes to compile (`-j 0`:no compilation)29 * `–d` : NEMO subdirectory (not needed)30 * `–t` DIR: temporary directory to store libraries31 * `–r` [REFCONFIG]: reference configuration as first guess when installing a new one 32 * `–j`[num]: number of processes to compile (`-j 0`:no compilation) 33 * `–d` [DIR]: NEMO subdirectory (not needed) 34 * `–t` [DIR]: temporary directory to store libraries 31 35 * `-clean` [CONFIG_NAME] : remove the Makefile and all the files created afterwards 32 36 … … 37 41 38 42 * `functions.sh` : bash functions used by `makenemo`, for instance to create the `WORK` directory 39 * `cfg.txt` : text list of configurations and source directories [[BR]]43 * `cfg.txt` : text list of configurations and source directories 40 44 * `bld.cfg` : FCM rules to compile 41 45 … … 43 47 44 48 * `ARCH` : compilation option files, with format `arch_compiler.fcm`, the compiler name has to be provided with `–m` option 45 * `GYRE`, `ORCA2_LIM` or others : there is now a `cpp.fcm` file containing the list of cpp key, the `WORK` is specific to each configuration49 * `GYRE`, `ORCA2_LIM` or others : there is now a `cpp.fcm` file containing the list of CPP keys, the `WORK` is specific to each configuration 46 50 47 51 == Examples 48 52 49 Compiling GYRE, with ifort on linux to create a MY_GYRE configuration[[BR]]53 Compiling `GYRE`, with ifort on linux to create a `MY_GYRE` configuration 50 54 {{{#!sh 51 55 makenemo –m ifort_linux –r GYRE -n MY_GYRE … … 57 61 }}} 58 62 59 Now, create and compile ORCA_LIM3[[BR]]63 Now, create and compile `ORCA_LIM3` 60 64 {{{#!sh 61 65 makenemo –n ORCA_LIM3 (and answer) 62 66 }}} 63 67 64 Now ORCA_LIM3_v2 based on the previous one [[BR]]68 Now ORCA_LIM3_v2 based on the previous one 65 69 {{{#!sh 66 70 makenemo –n ORCA_LIM3_v2 -r ORCA_LIM3 67 71 }}} 68 72 69 Now, create and compile ORCA2_LIM_2_2, add ( '''add_key''') and delete ('''del_key''') keys, based on ORCA2_LIM(just un example)73 Now, create and compile ORCA2_LIM_2_2, add (`add_key`) and delete (`del_key`) keys, based on `ORCA2_LIM` (just un example) 70 74 {{{#!sh 71 75 makenemo –n ORCA2_LIM_2_2 -r ORCA2_LIM del_key "key_iomput" (and answer)
