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 (diff) – NEMO

Changes between Version 3 and Version 4 of WorkingGroups/TAM/CompilationFCM


Ignore:
Timestamp:
2009-09-15T12:38:55+02:00 (15 years ago)
Author:
vigilant
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WorkingGroups/TAM/CompilationFCM

    v3 v4  
    3333 
    3434== 3) Building NEMOVAR == 
     35 
    3536In ~/nemovar/build/: 
    3637{{{ 
    37       ./fcmvmake -t path/to/build -c user_machine 
     38      ./fcmvmake.ksh -t path/to/build -c user_machine 
    3839}}} 
    3940FCM will create a folder 'nemofcm_build' in path/to/build.  
    4041The 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/ 
    4142 
     43== 4) Running NEMO == 
    4244 
     45In ~/nemo/script/ : 
     46{{{ 
     47      ./runnemo.ksh -t path/to/build -A user_machine -F 
     48}}} 
     49The "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. 
     50 
     51== 5) Running NEMOVAR == 
     52In ~/nemovar/script/ : 
     53{{{ 
     54      ./runnemovar.ksh -t path/to/build -A user_machine -F 
     55}}} 
     56The "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.