source: branches/2013/dev_r3996_CMCC6_topbc/NEMOGCM/CONFIG/GYRE_BFM/README @ 4011

Last change on this file since 4011 was 4011, checked in by vichi, 8 years ago

Make a generic interface for trcdta when using other BGCM

This change introduces a more general trcdta structure that
is not strictly dependent on the number of tracers defined
in PISCES. The loop on the number of tracers is moved outside
trcdta and the tracer info and array is passed as an argument.
This allows to use trcdta as a library subroutine by the BFM and
other models.
NOTE: it must be tested throughly with all the PISCES configurations

This commit also updates the GYRE_BFM configuration and corrects
some minor missing cpp keys and real type definitions

File size: 3.5 KB
Line 
1-----------------------------------------------------------------------
2Coupling with the Biogeochemical Flux Model (BFM)
3-----------------------------------------------------------------------
4Author: M. Vichi, BFM system team and NEMO system team
5INFO HELPDESK: info@bfm-community.eu
6WEB SITE: www.bfm-community.eu
7REVISION DATE: February 2013
8
9Please address any technical query to the BFM System Team
10bfm_st@lists.cmcc.it
11-----------------------------------------------------------------------
12
13-----------------------------------------------------------------------
14What is the BFM?
15-----------------------------------------------------------------------
16The Biogeochemical Flux Model (BFM) is a numerical model for the
17simulation of the dynamics of major biogeochemical properties
18in marine ecosystems.  The BFM is open source software freely available
19under the GNU Public License. The model can be used in standalone mode
20to simulate a 0-D system or coupled with other OGCM.
21The coupling with NEMO is maintained by CMCC as part of the
22NEMO system team activity
23
24-----------------------------------------------------------------------
25How to get the BFM code
26-----------------------------------------------------------------------
27The code can be downloaded from http://www.bfm-community.eu after
28the registration of a new user. Follow the instructions on how to
29install the code. It is recommended to run the STANDALONE test cases
30before using the NEMO-BFM coupled system.
31
32-----------------------------------------------------------------------
33Compile NEMO with the BFM
34-----------------------------------------------------------------------
35Make sure that the BFMDIR variable is defined in your environment
36(ex: export BFMDIR=path/to/bfm)
37Define the variable NEMODIR pointing to the root of NEMO source code
38(ex: export NEMODIR=path/to/nemo)
39
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.
46The script will generate the BFM code and then launch makenemo
47to build the executable in this directory.
48
49Once the BFM code has been generated the first time, the code can be
50also rebuilt with the standard NEMO command:
51./makenemo -n GYRE_BFM -m ARCHFILE -e $BFMDIR/src/nemo
52
53-----------------------------------------------------------------------
54Standard test case
55-----------------------------------------------------------------------
56The distributed standard test case is GYRE_BFM, a version of GYRE
57with a full-blown BFM. It is a demnstration simulation and it is not
58meant to produce any published result.
59GYRE_BFM runs with analytical input data only.
60The namelists for the BFM are not distributed with NEMO but are
61generated directly by the BFM, in directory $BFMDIR/run/gyre_bfm.
62The generation of the BFM namelist also copy the required NEMO
63namelist and namelist_top files to this directory.
64This is why there are no namelist files found in the standard
65run directory $NEMODIR/NEMOGCM/CONFIG/GYRE_BFM/EXP00
66If a user prefers to work in that directory than she has to
67copy the generated namelists there
68
69-----------------------------------------------------------------------
70Other examples
71-----------------------------------------------------------------------
72Other couplings with NEMO are available in $BFMDIR/build/configurations.
73Please refer to the README file in each directory for more information.
Note: See TracBrowser for help on using the repository browser.