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