Changes between Version 28 and Version 29 of Users/ModelInstall
- Timestamp:
- 2017-05-12T17:01:51+02:00 (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Users/ModelInstall
v28 v29 4 4 5 5 [[PageOutline(2-3)]] 6 \\7 \\8 \\9 \\10 \\11 \\12 \\13 \\14 \\15 \\16 17 18 19 6 20 7 == 1. Extract the NEMO code … … 30 17 The image below shows the directory tree: 31 18 32 [[Image( Users/ModelInstall:nemogcm_tree.png,width=300)]]19 [[Image(wiki:Users/ModelInstall:nemogcm_tree.png,width=600, center)]] 33 20 34 21 … … 44 31 Diagnostic outputs from NEMO are handled by the third party XIOS library. '''Important notice: XIOS needs to be installed (dowloaded and compiled) before NEMO, since the libraries are needed to successfully create NEMO executable.''' Instructions on how to obtain and install the software see [[ModelInterfacing/InputsOutputs#ExtractingandinstallingXIOS]]. 45 32 46 When you compile NEMO you will need to specify the following cppkeys:33 When you compile NEMO you will need to specify the following CPP keys: 47 34 * key_iomput 48 35 * key_mpp_mpi (if you want to use "detached mode") … … 59 46 As an example, compile `GYRE`, with ifort on linux to create a `MY_GYRE` configuration: 60 47 {{{#!sh 61 cd NEMOGCM/CONFIG; ./makenemo –m my_arch_name–r GYRE -n MY_GYRE48 cd NEMOGCM/CONFIG; ./makenemo –m "my_arch_name" –r GYRE -n MY_GYRE 62 49 }}} 63 50 64 51 After successful execution of the makenemo command, the executable name `opa`is created in the EXP00 directory (in the example above, the executable is created in `CONFIG/MY_GYRE/EXP00/opa`) 65 52 {{{#!comment 66 The image below shows the directory tree characterized by 'MY_CONFIG'new 'branch'. All directories and fundamental files created by makenemo are highlighted in green.53 The image below shows the directory tree characterized by [[span("MY_CONFIG", style=color: #BB4444 )]] new 'branch'. All directories and fundamental files created by makenemo are highlighted in green. 67 54 In particular, even if not shown in the figure, the "WORK" folder contains links to the compiled routines. 68 55 69 56 [[Image(Users/ModelInstall:nemogcm_tree._compiled.png,width=300)]] 70 ADD here new figure with all the directories and files created by makenemo: the ex cutable, but also the directories and their content: WORK, BLD, etc...57 ADD here new figure with all the directories and files created by makenemo: the executable, but also the directories and their content: `WORK`, `BLD`, etc... 71 58 This should be the same figure as baobe, with all new files and directories added with another color. 72 59 }}} … … 107 94 makenemo –n ORCA_LIM3_v2 -r ORCA_LIM3 108 95 }}} 109 * Create and compile ORCA2_LIM_2_2, add (`add_key`) and delete (`del_key`) keys, based on `ORCA2_LIM`96 * Create and compile ORCA2_LIM_2_2, add (`add_key`) and delete (`del_key`) keys, based on ORCA2_LIM 110 97 {{{#!sh 111 98 makenemo –n ORCA2_LIM_2_2 -r ORCA2_LIM del_key "key_iomput" # and answer … … 122 109 == 5. Running the model 123 110 124 Once makenemo has run successfully, the executable is available in `CONFIG/"MY_CONFIG"/EXP00/opa`125 For the reference configurations, the `EXP00`directory also contains the small ASCII input file (namelists, *xml files for the IOs...). If the configuration also needs N ETCDF input files, this should be downloaded into the `EXP00` directory from the corresponding tarfile, see [http://forge.ipsl.jussieu.fr/nemo/wiki/Users/ReferenceConfigurations]111 Once `makenemo` has run successfully, the `opa` executable is available in `CONFIG/"MY_CONFIG"/EXP00`[[BR]] 112 For the reference configurations, the `EXP00`directory also contains the small ASCII input file (namelists, *xml files for the IOs...). If the configuration also needs NetCDF input files, this should be downloaded into the `EXP00` directory from the corresponding tarfile, see [wiki:Users/ReferenceConfigurations] 126 113 127 === Run the model 128 129 {{{ 114 {{{#!sh 130 115 cd CONFIG/"MY_CONFIG"/EXP00 131 mpirun -n "NP" ./opa # NPis the number of processes ; mpirun is your MPI wrapper116 mpirun -n $NPROCS ./opa # $NPROCS is the number of processes ; mpirun is your MPI wrapper 132 117 }}} 133 118 119 == 6. Viewing and changing list of active CPP keys 134 120 135 136 == Viewing and changing list of active cpp keys 137 138 For a given configuration (here called "MY_CONFIG", the list of active cpp keys can be found in 139 {{{ 121 For a given configuration (here called [[span("MY_CONFIG", style=color: #BB4444 )]]), the list of active CPP keys can be found in 122 {{{#!sh 140 123 NEMOGCM/CONFIG/"MYCONFIG"/cpp_"MY_CONFIG".fcm 141 124 }}} 142 125 143 This text file can be edited to change the list of active cpp keys. Once changed, one needs to recompile NEMO using the makenemocommand in order for this change to be taken in account.126 This text file can be edited to change the list of active CPP keys. Once changed, one needs to recompile NEMO using `makenemo` command in order for this change to be taken in account.