Changes between Version 20 and Version 21 of Users/Model Install


Ignore:
Timestamp:
2017-05-12T11:07:32+02:00 (3 years ago)
Author:
clevy
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Users/Model Install

    v20 v21  
    44 
    55[[PageOutline(2-3)]] 
     6\\ 
     7\\ 
     8\\ 
     9\\ 
     10\\ 
     11\\ 
     12\\ 
     13\\ 
     14\\ 
     15\\ 
    616 
    717 
     
    1424svn --username "mylogin" co http://forge.ipsl.jussieu.fr/nemo/svn/branches/2015/nemo_v3_6_STABLE/NEMOGCM 
    1525}}} 
     26 
     27=== Description of directory tree 
     28{{{#!comment 
     29The 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 
    1638 
    1739== 2. Extract and install XIOS 
     
    3860 
    3961After 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 
     63ADD here new figure with all the directories and files created by makenemo: the excutable, but also the directories and their content: WORK, BLD, etc... 
     64This should be the same figure as baobe, with all new files and directories added with another color. 
     65}}} 
    4066 
    4167 
     
    6086* `bld.cfg` : FCM rules to compile 
    6187 
    62 === Description of directories 
    63  
    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` option 
    67 * `CONFIG` : all configurations and a `cpp.fcm` file containing the list of CPP keys to each configuration 
    68 * `EXTERNAL` : package to implement an embbeded model (AGRIF) 
    69 * `NEMO` : source codes 
    70 * `SETTE` : package to make tests to ensure the reproducibility and restartability of the code after user changes 
    71 * `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  
    7488=== Examples 
    7589 
    76 Compiling `GYRE`, with ifort on linux to create a `MY_GYRE` configuration 
     90* Compiling `GYRE`, with ifort on linux to create a `MY_GYRE` configuration 
    7791{{{#!sh 
    7892makenemo –m ifort_linux –r GYRE -n MY_GYRE 
    7993}}} 
    80  
    81 Recompile it[[BR]] 
     94* Create and compile `ORCA_LIM3` 
    8295{{{#!sh 
    83 makenemo 
     96makenemo –n ORCA_LIM3 # and answer 
    8497}}} 
    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 
    9299{{{#!sh 
    93100makenemo –n ORCA_LIM3_v2 -r ORCA_LIM3 
    94101}}} 
    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` 
    97103{{{#!sh 
    98 makenemo –n ORCA2_LIM_2_2 -r ORCA2_LIM del_key "key_iomput" (and answer) 
     104makenemo –n ORCA2_LIM_2_2 -r ORCA2_LIM del_key "key_iomput" # and answer 
    99105}}} 
    100  
    101 To remove a bad configuration 
     106* Remove a configuration 
    102107{{{#!sh 
    103 makenemo –n ORCA2_LIM_2_2 clean_config (and answer) 
     108makenemo –n ORCA2_LIM_2_2 clean_config # and answer 
     109}}} 
     110* Get help on makenemo options 
     111{{{#!sh 
     112makenemo –h 
    104113}}} 
    105114 
    106115== 5. Running the model 
    107116 
    108 Once makenemo has run successfully, the opa executable is available in CONFIG/"MY_CONFIG"/EXP00 
     117Once makenemo has run successfully, the executable is available in `CONFIG/"MY_CONFIG"/EXP00/opa` 
     118For 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] 
    109119 
    110 If no input file is expected, like for the simple "MY_CONFIG" configuration, 
     120=== Run the model 
    111121 
     122{{{ 
    112123cd CONFIG/"MY_CONFIG"/EXP00 
    113  
    114 {{{#!sh 
    115 mpirun ./opa 
     124mpirun -n "NP" ./opa    # NP is the number of processes ; mpirun is your MPI wrapper 
    116125}}} 
    117126 
    118 If input file are needed, see the  [http://forge.ipsl.jussieu.fr/nemo/wiki/Users/ReferenceConfigurations]  
    119127 
    120128