Changeset 3813


Ignore:
Timestamp:
2013-02-15T10:50:52+01:00 (9 years ago)
Author:
vichi
Message:

Updated README file for the BFM coupling

Location:
branches/2012/dev_MERGE_2012/NEMOGCM/CONFIG/GYRE_BFM
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • branches/2012/dev_MERGE_2012/NEMOGCM/CONFIG/GYRE_BFM/EXP00/runscript

    r3478 r3813  
    11#! /bin/sh  
    2  
     2### This is an example of a runscript for the LSF queueing system 
    33#BSUB -a poe 
    44#BSUB -J GYRE_BFM         # Name of the job. 
     
    88#BSUB -q poe_short    # queue 
    99#BSUB -n 4            # Number of CPUs 
    10 ##BSUB -x  
    11 ###BSUB -R "span[ptile=32]" 
    1210 
    1311set -evx 
     
    2321EXP="EXP00" 
    2422 
    25 workdir="/data/ans033/EXPERIMENTS/GYRE_BFM/${EXP}" 
     23workdir="TO_BE_SET_BY_USER" 
    2624execdir=`pwd` 
    2725 
     
    3836# Launch the model 
    3937 
    40 time mpirun.lsf opa.x  
     38mpirun.lsf opa.x  
    4139 
    42 echo " ${EXP} DONEEE!!!" 
    4340 
  • branches/2012/dev_MERGE_2012/NEMOGCM/CONFIG/GYRE_BFM/README

    r3744 r3813  
    55INFO HELPDESK: info@bfm-community.eu 
    66WEB SITE: www.bfm-community.eu 
    7 REVISION DATE: January 2013 
     7REVISION DATE: February 2013 
    88 
    99Please address any technical query to the BFM System Team  
     
    3838(ex: export NEMODIR=path/to/nemo) 
    3939 
    40 Go to the $BFMDIR/build directory and modify the script 
    41 config_GYRE_BFM.sh 
    42 adding the appropriate ARCHFILE that is used for the NEMO compilation. 
     40Go to the $BFMDIR/build/Configurations/GYRE_BFM directory and read  
     41carefully the README file. 
     42Altrenatively, execute 
     43$BFMDIR/build/bfm_config.sh -h 
     44to get information on how to add the appropriate ARCHFILE that  
     45is used for the NEMO compilation. 
    4346The script will generate the BFM code and then launch makenemo 
    4447to build the executable in this directory. 
     
    5356The distributed standard test case is GYRE_BFM, a version of GYRE 
    5457with a full-blown BFM. It is a demnstration simulation and it is not 
    55 meant to produce any published result. The namelistsfor the BFM are  
    56 not distributed with NEMO but are found in the BFM tree, in 
    57 directory $BFMDIR/run/nemo/GYRE_BFM. The user can either copy the content 
     58meant to produce any published result. The namelists for the BFM are  
     59not distributed with NEMO but are generated directly by the BFM, in 
     60directory $BFMDIR/run/GYRE_BFM. The user can either copy the content 
    5861of $NEMODIR/NEMOGCM/CONFIG/GYRE_BFM/EXP00 in this directory or the 
    5962other way around. GYRE_BFM runs with analytical input data only. 
     
    6265Other examples 
    6366----------------------------------------------------------------------- 
    64 Other couplings with NEMO are available in $BFMDIR/run/nemo/. 
     67Other couplings with NEMO are available in $BFMDIR/build/Configurations. 
    6568Please refer to the README file in each directory for more information. 
Note: See TracChangeset for help on using the changeset viewer.