Changeset 10187 for NEMO/trunk/INSTALL.rst
- Timestamp:
- 2018-10-09T19:08:59+02:00 (6 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
NEMO/trunk/INSTALL.rst
r9596 r10187 1 Install the modelling framework (NEMO and XIOS) 1 ===================== 2 Install the framework 3 ===================== 2 4 3 Last edition: 2018-02-14 21:32 CET by nicolasmartin 5 .. contents:: \ 6 :local: 7 8 Dependencies 9 ============ 4 10 5 Extract the NEMO code 6 Description of NEMOGCM directory tree 7 Extract and install XIOS 8 Setup your architecture configuration file 9 Compile and create NEMO executable 10 More options 11 Default behaviour 12 Tools used during the process 13 Examples 14 Running the model 15 Viewing and changing list of active CPP keys 11 | The NEMO source code is written in Fortran 95 and part of its dependencies are already included (``./ext``): 12 AGRIF preprocessing program "conv", FCM build system and IOIPSL library for outputs. 13 | And some Perl 5, Fortran compiler (ifort, gfortran, pgfortran, ...), MPI library (Open MPI or MPICH) 16 14 17 Extract the NEMO code 15 But The following dependencies should be from the official repositories of your Linux distribution but 16 you will probably have to compile them from source for enabling parallel I/O support. 18 17 19 Using your account registered here ('my_login' with password) 18 - `HDF5`_ (C library) 19 - `NetCDF`_ (C and Fortran libraries) 20 21 Extract the source code 22 ======================= 23 24 Download the source code 20 25 21 26 .. code:: console 22 svn --username 'mylogin' co http://forge.ipsl.jussieu.fr/nemo/svn/branches/2015/nemo_v3_6_STABLE/NEMOGCM23 27 24 Description of NEMOGCM directory tree 28 $ svn co http://forge.ipsl.jussieu.fr/nemo/svn/NEMO/releases/release-4.0 25 29 26 The image below shows the directory tree: 30 Description of directory tree 31 ============================= 27 32 28 simple table: 29 ARCH Compilation option files, with format arch_compiler.fcm, the compiler name has to be provided with –m option 30 CONFIG All configurations and a cpp.fcm file containing the list of CPP keys to each configuration 31 EXTERNAL Package to implement an embedded model (AGRIF) 32 NEMO FORTRAN source codes in several sub-directories 33 SETTE Package to make tests to ensure the reproducibility and restartability of the code after changes 34 TOOLS Useful softwares to different utilities 33 +-----------+---------------------------------------------------------------+ 34 | Folder | Purpose | 35 +===========+===============================================================+ 36 | ``arch`` | Settings (per architecture-compiler pair) | 37 +-----------+---------------------------------------------------------------+ 38 | ``cfgs`` | Reference configurations | 39 +-----------+---------------------------------------------------------------+ 40 | ``doc`` | - ``latex``: reference manuals for NEMO, SI\ :sup:`3`\ & TOP | 41 | | - ``rst``: quick start guide | 42 +-----------+---------------------------------------------------------------+ 43 | ``ext`` | Dependencies included (AGRIF, FCM & IOIPSL) | 44 +-----------+---------------------------------------------------------------+ 45 | ``mk`` | Building routines | 46 +-----------+---------------------------------------------------------------+ 47 | ``src`` | Modelling routines | 48 | | | 49 | | - ``ICE``: SI\ :sup:`3`\ for sea ice | 50 | | - ``NST``: AGRIF for embedded zooms | 51 | | - ``OCE``: OPA for ocean dynamics | 52 | | - ``MBG``: TOP for tracers | 53 +-----------+---------------------------------------------------------------+ 54 | ``tests`` | Test cases | 55 +-----------+---------------------------------------------------------------+ 56 | ``tools`` | Utilities to [pre|post]process data | 57 +-----------+---------------------------------------------------------------+ 35 58 36 59 Extract and install XIOS 60 ======================== 37 61 38 62 Diagnostic outputs from NEMO are handled by the third party XIOS library. … … 42 66 43 67 When you compile NEMO you will need to specify the following CPP keys: 44 68 45 69 key_iomput 46 70 key_mpp_mpi (if you want to run with multiple processes and/or use "detached mode" for the IOs system XIOS) … … 48 72 49 73 Setup your architecture configuration file 74 ========================================== 50 75 51 76 All compiler options in NEMO are controlled using files in NEMOGCM/ARCH/arch-'my_arch'.fcm where 'my_arch' is the name of the computing architecture. … … 58 83 59 84 Compile and create NEMO executable 85 ================================== 60 86 61 87 The main script to compile and create executable is called makenemo and located in the CONFIG directory, it is used to identify the routines you need from the source code, to build the makefile and run it. 62 88 As an example, compile GYRE with 'my_arch' to create a 'MY_GYRE' configuration: 63 89 64 cd NEMOGCM/CONFIG; ./makenemo –m 'my_arch' –r GYRE -n 'MY_GYRE' 90 .. code-block:: sh 91 92 ./makenemo –m 'my_arch' –r GYRE -n 'MY_GYRE' 65 93 66 94 The image below shows the structure and some content of "MY_CONFIG" directory from the launching of the configuration creation (directories and fundamental files created by makenemo). 67 95 68 96 +------------+----------------------------------------------------+ 97 | Folder | Purpose | 98 +============+====================================================+ 99 | ``BLD`` | | 100 +------------+----------------------------------------------------+ 101 | ``EXP00`` | | 102 +------------+----------------------------------------------------+ 103 | ``EXPREF`` | | 104 +------------+----------------------------------------------------+ 105 | ``MY_SRC`` | | 106 +------------+----------------------------------------------------+ 107 | ``WORK`` | | 108 +------------+----------------------------------------------------+ 69 109 70 WORK 71 72 73 74 Folder with the symbolic links to all unpreprocessed routines considered in the configuration 75 76 BLD 77 78 79 80 Compilation folder (executables, headers files, libraries, preprocessed routines, flags, …) 81 82 EXP00 83 84 85 86 Computation folder for running the model (namelists, xml, executables and inputs-outputs) 87 88 MY_SRC 89 90 91 92 Folder intended to contain your customized routines (modified from initial ones or new entire routines) 110 Folder with the symbolic links to all unpreprocessed routines considered in the configuration 111 Compilation folder (executables, headers files, libraries, preprocessed routines, flags, …) 112 Computation folder for running the model (namelists, xml, executables and inputs-outputs) 113 Folder intended to contain your customised routines (modified from initial ones or new entire routines) 93 114 94 115 After successful execution of makenemo command, the executable called opa is created in the EXP00 directory (in the example above, the executable is created in CONFIG/MY_GYRE/EXP00). 95 116 More options 96 117 97 echo "Usage : "${b_n} \ 98 " [-h] [-n name] [-m arch] [-d "dir1 dir2"] [-r conf] [-u conf] [-s Path] [-e Path] [-j No] [-v No] [-k 0/1]"; 99 echo " -h : help"; 100 echo " -h institute : specific help for consortium members"; 101 echo " -n name : config name, [-n help] to list existing configurations"; 102 echo " -m arch : choose compiler, [-m help] to list existing compilers"; 103 echo " -d dir : choose NEMO sub-directories"; 104 echo " -r conf : choose reference configuration"; 105 echo " -u conf : choose an unsupported (external) configuration"; 106 echo " -s Path : choose alternative location for NEMO main directory"; 107 echo " -e Path : choose alternative location for MY_SRC directory"; 108 echo " -j No : number of processes used to compile (0=nocompilation)"; 109 echo " -v No : set verbosity level for compilation [0-3]"; 110 echo " -k 0/1 : used cpp keys check (default = 1 -> check activated)"; 111 echo " -t dir : temporary directory for compilation" 112 echo ""; 118 .. includefile:: 113 119 120 121 122 ----------------- 114 123 Default behaviour 124 ----------------- 115 125 116 126 At the first use, you need the -m option to specify the architecture configuration file (compiler and its options, routines and libraries to include), then for next compilation, it is assumed you will be using the same compiler. 117 127 If –n option is not specified, ORCA2_LIM is the default configuration used. 118 128 129 ----------------------------- 119 130 Tools used during the process 131 ----------------------------- 120 132 121 133 functions.sh : bash functions used by makenemo, for instance to create the WORK directory … … 123 135 bld.cfg : FCM rules to compile 124 136 137 -------- 125 138 Examples 139 -------- 126 140 127 141 echo "Example to install a new configuration MY_CONFIG"; … … 148 162 echo "./makenemo -n MY_CONFIG -j0 add_key \"key_iomput key_mpp_mpi\" del_key \"key_agrif\" "; 149 163 164 ----------------- 150 165 Running the model 166 ----------------- 151 167 152 168 Once makenemo has run successfully, the opa executable is available in CONFIG/"MY_CONFIG"/EXP00 … … 156 172 mpirun -n $NPROCS ./opa # $NPROCS is the number of processes ; mpirun is your MPI wrapper 157 173 174 -------------------------------------------- 158 175 Viewing and changing list of active CPP keys 176 -------------------------------------------- 159 177 160 For a given configuration (here called MY_CONFIG), the list of active CPP keys can be found in 178 For a given configuration (here called MY_CONFIG), the list of active CPP keys can be found in:: 161 179 162 180 NEMOGCM/CONFIG/'MYCONFIG'/cpp_'MY_CONFIG'.fcm 163 181 164 182 This text file can be edited to change the list of active CPP keys. Once changed, one needs to recompile opa executable using makenemo command in order for this change to be taken in account. 183 184 .. _HDF5: http://www.hdfgroup.org/downloads/hdf5 185 .. _NetCDF: http://www.unidata.ucar.edu/downloads/netcdf
Note: See TracChangeset
for help on using the changeset viewer.