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:

    ~/NEMOVAR/UTIL/build/fcmconfig/bld/machines/nemo.cfg                                   : user specific machine configuration 
    ~/NEMOVAR/UTIL/build/fcmconfig/nemo/machines/cppkeys.CONFIG.cfg           : default ccp keys set for CONFIG
    ~/NEMOVAR/UTIL/build/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 / NEMOTAM / NEMOVAR

In ~/NEMOVAR/UTIL/build/:

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

The option -B is either NEMO, NEMOTAM, NEMOVAR or NEMOALL (lower case is ok).
FCM will create a folder 'nemofcm_build' in path/to/build. The user can also specify other compilation arguments (GRID, NPX and NPY for instance). The GRID default configuration is ORCA2 and NPX=NPY=1. The executable files opa.exe is placed in ~/path/to/build/nemofcm_build/build/bin/

3) Running NEMO

In ~/NEMOVAR/UTIL/scripts/ :

      ./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.

4) Running NEMOTAM

In ~/NEMOVAR/UTIL/scripts/ :

      ./runnemotam.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. As default, the will use the setup file: my_setup_generic.

5) Running NEMOVAR

In ~/NEMOVAR/UTIL/scripts/ :

      ./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. As default, the will use the setup file: my_setup_tam_var.

Last modified 11 years ago Last modified on 2009-09-16T16:33:54+02:00