Changes between Version 20 and Version 21 of Users/ModelInstall
- Timestamp:
- 2017-05-12T11:07:32+02:00 (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Users/ModelInstall
v20 v21 4 4 5 5 [[PageOutline(2-3)]] 6 \\ 7 \\ 8 \\ 9 \\ 10 \\ 11 \\ 12 \\ 13 \\ 14 \\ 15 \\ 6 16 7 17 … … 14 24 svn --username "mylogin" co http://forge.ipsl.jussieu.fr/nemo/svn/branches/2015/nemo_v3_6_STABLE/NEMOGCM 15 25 }}} 26 27 === Description of directory tree 28 {{{#!comment 29 The image shows the directory tree (see * Documentation: [attachment:wiki:Users/ModelInstall:nemogcm_tree.gif]. 'TO MAKE NEW FIGURE (nemogcm_tree.gif) GELSOMINA' 30 }}} 31 32 * `ARCH` : compilation option files, with format `arch_compiler.fcm`, the compiler name has to be provided with `–m` option 33 * `CONFIG` : all configurations and a `cpp.fcm` file containing the list of CPP keys to each configuration 34 * `EXTERNAL` : package to implement an embbeded model (AGRIF) 35 * `NEMO` and sub-directories: FORTRAN source codes 36 * `SETTE` : package to make tests to ensure the reproducibility and restartability of the code after user changes 37 * `TOOLS` : useful softwares to different utilities 16 38 17 39 == 2. Extract and install XIOS … … 38 60 39 61 After sucessful 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`) 62 {{{#!comment 63 ADD here new figure with all the directories and files created by makenemo: the excutable, but also the directories and their content: WORK, BLD, etc... 64 This should be the same figure as baobe, with all new files and directories added with another color. 65 }}} 40 66 41 67 … … 60 86 * `bld.cfg` : FCM rules to compile 61 87 62 === Description of directories63 64 The image shows the directory tree (see * Documentation: [attachment:wiki:Users/ModelInstall:nemogcm_tree.gif]. 'TO MAKE NEW FIGURE (nemogcm_tree.gif) GELSOMINA'65 66 * `ARCH` : compilation option files, with format `arch_compiler.fcm`, the compiler name has to be provided with `–m` option67 * `CONFIG` : all configurations and a `cpp.fcm` file containing the list of CPP keys to each configuration68 * `EXTERNAL` : package to implement an embbeded model (AGRIF)69 * `NEMO` : source codes70 * `SETTE` : package to make tests to ensure the reproducibility and restartability of the code after user changes71 * `TOOLS` : useful softwares to different utilities. For example a tool under MPP_PREP computes the number of water processors for all possible decompositions (up to a maximum number of processors).72 * `fcm_make`: 'TO ADD description GELSOMINA '73 74 88 === Examples 75 89 76 Compiling `GYRE`, with ifort on linux to create a `MY_GYRE` configuration90 * Compiling `GYRE`, with ifort on linux to create a `MY_GYRE` configuration 77 91 {{{#!sh 78 92 makenemo –m ifort_linux –r GYRE -n MY_GYRE 79 93 }}} 80 81 Recompile it[[BR]] 94 * Create and compile `ORCA_LIM3` 82 95 {{{#!sh 83 makenemo 96 makenemo –n ORCA_LIM3 # and answer 84 97 }}} 85 86 Now, create and compile `ORCA_LIM3` 87 {{{#!sh 88 makenemo –n ORCA_LIM3 (and answer) 89 }}} 90 91 Now ORCA_LIM3_v2 based on the previous one 98 * Create your ORCA_LIM3_v2 configuration based on the previous one 92 99 {{{#!sh 93 100 makenemo –n ORCA_LIM3_v2 -r ORCA_LIM3 94 101 }}} 95 96 Now, create and compile ORCA2_LIM_2_2, add (`add_key`) and delete (`del_key`) keys, based on `ORCA2_LIM` (just un example) 102 * Create and compile ORCA2_LIM_2_2, add (`add_key`) and delete (`del_key`) keys, based on `ORCA2_LIM` 97 103 {{{#!sh 98 makenemo –n ORCA2_LIM_2_2 -r ORCA2_LIM del_key "key_iomput" (and answer)104 makenemo –n ORCA2_LIM_2_2 -r ORCA2_LIM del_key "key_iomput" # and answer 99 105 }}} 100 101 To remove a bad configuration 106 * Remove a configuration 102 107 {{{#!sh 103 makenemo –n ORCA2_LIM_2_2 clean_config (and answer) 108 makenemo –n ORCA2_LIM_2_2 clean_config # and answer 109 }}} 110 * Get help on makenemo options 111 {{{#!sh 112 makenemo –h 104 113 }}} 105 114 106 115 == 5. Running the model 107 116 108 Once makenemo has run successfully, the opa executable is available in CONFIG/"MY_CONFIG"/EXP00 117 Once makenemo has run successfully, the executable is available in `CONFIG/"MY_CONFIG"/EXP00/opa` 118 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, thos should be downloaded into the `EXP00` directory from the corresponding tarfile, see [http://forge.ipsl.jussieu.fr/nemo/wiki/Users/ReferenceConfigurations] 109 119 110 If no input file is expected, like for the simple "MY_CONFIG" configuration, 120 === Run the model 111 121 122 {{{ 112 123 cd CONFIG/"MY_CONFIG"/EXP00 113 114 {{{#!sh 115 mpirun ./opa 124 mpirun -n "NP" ./opa # NP is the number of processes ; mpirun is your MPI wrapper 116 125 }}} 117 126 118 If input file are needed, see the [http://forge.ipsl.jussieu.fr/nemo/wiki/Users/ReferenceConfigurations]119 127 120 128
