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.
Changeset 4230 for branches/2013/dev_LOCEAN_CMCC_INGV_2013/NEMOGCM/CONFIG/GYRE_BFM/README – NEMO

Ignore:
Timestamp:
2013-11-18T12:57:11+01:00 (10 years ago)
Author:
cetlod
Message:

dev_LOCEAN_CMCC_INGV_2013 : merge LOCEAN & CMCC_INGV branches, see ticket #1182

File:
1 edited

Legend:

Unmodified
Added
Removed
  • branches/2013/dev_LOCEAN_CMCC_INGV_2013/NEMOGCM/CONFIG/GYRE_BFM/README

    r3813 r4230  
    55INFO HELPDESK: info@bfm-community.eu 
    66WEB SITE: www.bfm-community.eu 
    7 REVISION DATE: February 2013 
     7REVISION DATE: October 2013 
    88 
    99Please address any technical query to the BFM System Team  
     
    3333Compile NEMO with the BFM  
    3434----------------------------------------------------------------------- 
     35NEMO-BFM is compiled from the BFM configuration script relying on the 
     36NEMO FCM compilation environment. This is done to allow BFM users to 
     37use new configurations in NEMO that are not part of the NEMO 
     38standard distribution code. 
     39The BFM configuration shipped with NEMO is GYRE_BFM (see next section) 
     40 
    3541Make sure that the BFMDIR variable is defined in your environment 
    36 (ex: export BFMDIR=path/to/bfm) 
    37 Define the variable NEMODIR pointing to the root of NEMO source code 
    38 (ex: export NEMODIR=path/to/nemo) 
     42and define the variable NEMODIR pointing to the root of NEMO source code 
     43It is assumed here that you have expanded the bfm in /home/user/bfm 
     44and the root of this NEMO directory in /home/user/nemo then 
     45and that you have already adjusted the appropriate ARCHFILE that 
     46is used for the NEMO compilation with makenemo in ../../ARCH 
    3947 
    40 Go to the $BFMDIR/build/Configurations/GYRE_BFM directory and read  
    41 carefully the README file. 
    42 Altrenatively, execute 
    43 $BFMDIR/build/bfm_config.sh -h 
    44 to get information on how to add the appropriate ARCHFILE that  
    45 is used for the NEMO compilation. 
    46 The script will generate the BFM code and then launch makenemo 
    47 to build the executable in this directory. 
     48Execute the following commands: 
     49>> export BFMDIR=/home/user/bfm 
     50>> export NEMODIR=/home/user/nemo 
     51>> cd $BFMDIR/build 
     52>> ./bfm_config.sh -gcd -p GYRE_BFM 
    4853 
    49 Once the BFM code has been generated the first time, the code can be  
    50 rebuilt with the following command: 
    51 ./makenemo -n GYRE_BFM -m ARCHFILE -e $BFMDIR/src/nemo  
     54The script will generate (-g) the BFM code, then launch  
     55makenemo for compilation (-c) and create the run directory 
     56(-d) in $BFMDIR/run. 
     57 
     58to get information on how to use the BFM configuration script run 
     59>> ./bfm_config.sh -h 
    5260 
    5361----------------------------------------------------------------------- 
     
    5664The distributed standard test case is GYRE_BFM, a version of GYRE 
    5765with a full-blown BFM. It is a demnstration simulation and it is not 
    58 meant to produce any published result. The namelists for the BFM are  
    59 not distributed with NEMO but are generated directly by the BFM, in 
    60 directory $BFMDIR/run/GYRE_BFM. The user can either copy the content 
    61 of $NEMODIR/NEMOGCM/CONFIG/GYRE_BFM/EXP00 in this directory or the 
    62 other way around. GYRE_BFM runs with analytical input data only. 
     66meant to produce any published result.  
     67GYRE_BFM runs with analytical input data only. 
     68The namelists for the BFM are not distributed with NEMO but are  
     69generated directly by the BFM, in directory $BFMDIR/run/gyre_bfm.  
     70The generation of the BFM namelist also copy the required NEMO 
     71namelist and namelist_top files to this directory.  
     72This is why there are no namelist files found in the standard  
     73run directory $NEMODIR/NEMOGCM/CONFIG/GYRE_BFM/EXP00  
     74 
     75Note for expert users: 
     76If a user prefers to work in the NEMO directory than she has to 
     77copy the generated namelists there  
     78>> cp $BFMDIR/run/gyre_bfm/* $NEMODIR/NEMOGCM/CONFIG/GYRE_BFM/EXP00 
     79Once the BFM code has been generated the first time, the code can be  
     80also rebuilt with the standard NEMO command: 
     81>> ./makenemo -n GYRE_BFM -m ARCHFILE -e $BFMDIR/src/nemo  
    6382 
    6483----------------------------------------------------------------------- 
    6584Other examples 
    6685----------------------------------------------------------------------- 
    67 Other couplings with NEMO are available in $BFMDIR/build/Configurations. 
     86Other couplings with NEMO are available in $BFMDIR/build/configurations. 
     87Run the command  
     88>> ./bfm_config.sh -P 
     89to get a list of available presets 
    6890Please refer to the README file in each directory for more information. 
Note: See TracChangeset for help on using the changeset viewer.