Changeset 4176 for branches/2013/dev_CMCC_2013/NEMOGCM/CONFIG/GYRE_BFM
- Timestamp:
- 2013-11-11T12:13:04+01:00 (11 years ago)
- Location:
- branches/2013/dev_CMCC_2013/NEMOGCM/CONFIG/GYRE_BFM
- Files:
-
- 3 deleted
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/2013/dev_CMCC_2013/NEMOGCM/CONFIG/GYRE_BFM/README
r3813 r4176 5 5 INFO HELPDESK: info@bfm-community.eu 6 6 WEB SITE: www.bfm-community.eu 7 REVISION DATE: February20137 REVISION DATE: October 2013 8 8 9 9 Please address any technical query to the BFM System Team … … 33 33 Compile NEMO with the BFM 34 34 ----------------------------------------------------------------------- 35 NEMO-BFM is compiled from the BFM configuration script relying on the 36 NEMO FCM compilation environment. This is done to allow BFM users to 37 use new configurations in NEMO that are not part of the NEMO 38 standard distribution code. 39 The BFM configuration shipped with NEMO is GYRE_BFM (see next section) 40 35 41 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) 42 and define the variable NEMODIR pointing to the root of NEMO source code 43 It is assumed here that you have expanded the bfm in /home/user/bfm 44 and the root of this NEMO directory in /home/user/nemo then 45 and that you have already adjusted the appropriate ARCHFILE that 46 is used for the NEMO compilation with makenemo in ../../ARCH 39 47 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 Execute 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 48 53 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 54 The script will generate (-g) the BFM code, then launch 55 makenemo for compilation (-c) and create the run directory 56 (-d) in $BFMDIR/run. 57 58 to get information on how to use the BFM configuration script run 59 >> ./bfm_config.sh -h 52 60 53 61 ----------------------------------------------------------------------- … … 56 64 The distributed standard test case is GYRE_BFM, a version of GYRE 57 65 with 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. 66 meant to produce any published result. 67 GYRE_BFM runs with analytical input data only. 68 The namelists for the BFM are not distributed with NEMO but are 69 generated directly by the BFM, in directory $BFMDIR/run/gyre_bfm. 70 The generation of the BFM namelist also copy the required NEMO 71 namelist and namelist_top files to this directory. 72 This is why there are no namelist files found in the standard 73 run directory $NEMODIR/NEMOGCM/CONFIG/GYRE_BFM/EXP00 74 75 Note for expert users: 76 If a user prefers to work in the NEMO directory than she has to 77 copy the generated namelists there 78 >> cp $BFMDIR/run/gyre_bfm/* $NEMODIR/NEMOGCM/CONFIG/GYRE_BFM/EXP00 79 Once the BFM code has been generated the first time, the code can be 80 also rebuilt with the standard NEMO command: 81 >> ./makenemo -n GYRE_BFM -m ARCHFILE -e $BFMDIR/src/nemo 63 82 64 83 ----------------------------------------------------------------------- 65 84 Other examples 66 85 ----------------------------------------------------------------------- 67 Other couplings with NEMO are available in $BFMDIR/build/Configurations. 86 Other couplings with NEMO are available in $BFMDIR/build/configurations. 87 Run the command 88 >> ./bfm_config.sh -P 89 to get a list of available presets 68 90 Please refer to the README file in each directory for more information. -
branches/2013/dev_CMCC_2013/NEMOGCM/CONFIG/GYRE_BFM/cpp_GYRE_BFM.fcm
r3695 r4176 1 bld::tool::fppkeys key_gyre key_dynspg_flt key_ldfslp key_zdftke key_vectopt_loop key_top key_my_trc key_mpp_mpi key_iomput 1 bld::tool::fppkeys key_gyre key_dynspg_flt key_ldfslp key_zdftke key_vectopt_loop key_top key_my_trc key_mpp_mpi key_iomput key_nosignedzero 2 2 inc $BFMDIR/src/nemo/bfm.fcm
Note: See TracChangeset
for help on using the changeset viewer.