New URL for NEMO forge!   http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
WorkingGroups/TAM/CompilationFCM – NEMO
wiki:WorkingGroups/TAM/CompilationFCM

Version 4 (modified by vigilant, 15 years ago) (diff)

--

Compilation of NEMO and NEMOVAR using FCM

Last edited Timestamp?


The recommended way of compiling the NEMO/NEMOVAR version is to use FCM. FCM stands for "Flexible Configuration Management" more information can be found here http://ncas-cms.nerc.ac.uk/html_umdocs/FCM/user_guide/

1) FCM configuration settings

FCM configuration settings are placed into the folder ~/fcmconfig/ with the following details:

Les principales rubriques à remplir avaient été définies. L'état actuel de l'arborescence est le suivant :

    ~/fcmconfig/bld/machines/nemo.cfg                                   : user specific machine configuration 
    ~/fcmconfig/nemo/machines/cppkeys.CONFIG.cfg           : default ccp keys set for CONFIG
    ~/fcmconfig/src/machines/nemo.cfg                                   : code source paths  

Usually, the user only needs to add (if not there already) his machines configuration:

    - create a 'user_machine' folder into ~/fcmconfig/bld/
    - copy paste a nemo.cfg file into his folder (for instance   ~/fcmconfig/bld/linux/nemo.cfg
    - modify nemo.cfg according to user configuration 

2) Building NEMO

? no fcmvmake.ksh file in ~/nemo/build/

3) Building NEMOVAR

In ~/nemovar/build/:

      ./fcmvmake.ksh -t path/to/build -c user_machine

FCM will create a folder 'nemofcm_build' in path/to/build. The user can also specified other compilation arguments (GRID, NPX and NPY for instance). The GRID default configuration is ORCA2 and NPX=NPY=1. The executable files model.exe and nemovar.exe are placed in ~/path/to/build/nemofcm_build/build/bin/

4) Running NEMO

In ~/nemo/script/ :

      ./runnemo.ksh -t path/to/build -A user_machine -F

The "fcmnmake.ksh" script has similar arguments as the old nemomake.ksh script. The "-F" argument for "runnemo.ksh" is needed to use the FCM generated executable.

5) Running NEMOVAR

In ~/nemovar/script/ :

      ./runnemovar.ksh -t path/to/build -A user_machine -F

The "fcmnmake.ksh" script has similar arguments as the old nemomake.ksh script. The "-F" argument for "runnemovar.ksh" is needed to use the FCM generated excutable.

Attachments (2)

Download all attachments as: .zip