Slide 1 Running NEMO at ECMWF Slide 1 NEMO under Perforce at ECMWF Kristian S. Mogensen Last revised:

Slide 2 Running NEMO at ECMWF Slide 2 Perforce source code management system Commercial software similar to subversion and CVS. Adopted to ECMWF local use -All developers works in their own branches. -A limited set of superusers can make releases. These are typically made by merging the developers branches into a single branch. -To facilitate common tasks a command line wrapper (q2) has been developed on top of the generic Perforce client (p4). -All RD source code is store on in central repository on a server. ECMWF specific perforce documentation can be found on Perforce documentation can be found on:

Slide 3 Running NEMO at ECMWF Slide 3 Perforce at ECMWF Common tasks (using q2) : q2 help : show help message. You can also use q2 help to get detailed information about arguments to. q2 create_branch : creates a branch. q2 merge_branch : merges a branch into current branch. q2 ls_private : list private files. Private files are files not under perforce. q2 submit : submit all changes. Common tasks (using p4) : p4 edit file.F90 : open file for editing. You can now edit the file using you favourite editor. p4 add file.F90 : add a new file to the branch. p4 delete file.F90 : delete file from branch. p4 submit : submit all changes. p4 diff : show differences between current workspace and the latest commited version. p4 revert file.F90 : revert changes to a file.

Slide 4 Running NEMO at ECMWF Slide 4 NEMO under perforce NEMO managed with its own perforce project group and has its own release numbering with using the LYYEX where YY reflects the version from L’OCEAN and X reflects our changes relative to the YY version. Latest version is L10E6. To create a branch use: q2 create_branch -b mybranch -p nemo -g nemo -r L10E6

Slide 5 Running NEMO at ECMWF Slide 5 ECMWF’s make system for NEMO Important files in the make system: -Makefile.nemo is the main make file -OPA.make (and similar files) contains the rules for creating the libraries and all dependencies needed for a library -hpc_mpi.config (and similar files) contains the compiler options used -CPP_keys.ORCA2 (and similar files) contains the default CPP directives (keys) for a given configuration -CPP_keys.ORCA2_OASIS3 contains the CPP directives for running with OASIS3

Slide 6 Running NEMO at ECMWF Slide 6 ECMWF’s make system for NEMO 2 The make system is quite different from L’OCEAN’s. Domain decomposition handled by the make system based on prepIFS input Integrated into perforce Adding new routines requires a complete rebuild of the NEMO model  (but so does L’OCEAN’s make system)

Slide 7 Running NEMO at ECMWF Slide 7 Using a simplified setup to run NEMO on your workstation or ecgate. Scripts in nemo/build Compilation scripts -setupnemomake.ksh  Creates directory to run in -linknemomake.ksh  Setup the compilation environment -makenemo.ksh  Makes the nemo model. Has the arguments –x, -y to specify decomposition.

Slide 8 Running NEMO at ECMWF Slide 8 Using a simplified setup to run NEMO on your workstation or ecgate. Scripts in nemo/build 2 Scripts to get data for ec:/ne1/nemovar_testdata -gettestdata_1x1.ksh -gettestdata_1x2.ksh -gettestdata_2x1.ksh  The 3 above scripts gets restart files etc. for running NEMO with different decomposition. On ecgate only 1x1 is supported.

Slide 9 Running NEMO at ECMWF Slide 9 Using a simplified setup to run NEMO on your workstation. Scripts in nemo/build 3 Cleaning scripts: -cleannemomake.ksh  Cleans objects etc for NEMO -cleanoasis3.ksh  Cleans objects etc for OASIS3 -cleanrun.ksh  Cleans all run files (including input data) Known issues with the simplified scripts: -The path to the OASIS3 source tree is hard coded in the following files “nemo/build/lamoasis3_*.ksh”, “nemo/build/linux_oasis3.config”, “nemo/tools/pseudo_ocean/config.linux” and “nemo/tools/pseudo_atmos/config.linux”. To run with OASIS3 you need to modify this files manually. This will be fixed in the next release.

Slide 10 Running NEMO at ECMWF Slide 10 Using a simplified setup to run NEMO on your workstation or ecgate: Sample session Created a branch to work in using the q2 create_branch –b mybranch –p nemo –g nemo –r L10E6 Run the following scripts in nemo/build:./setupnemomake.ksh./linknemomake.ksh./gettestdata_1x1.ksh./runnemo.ksh This should run a 5 day ORCA2 NEMO integration forced by ERA40 fluxes