4. Summary of essential steps¶
CROCO needs to be compiled for each configuration (grid, MPI decomposition, paramterizations…). The files that need to be edited are (available in croco/OCEAN directory):
cppdefs.hCPP-keys* allowing to select configuration, numerical schemes, parameterizations,forcing and boundary conditions* CROCO extensively uses the C preprocessor (cpp) during compilation toreplace code statements, insert files into the code, and select relevantparts of the code depending on its directives.
param.hGrid settings: the values of the model grid size are:LLm0 points in the X directionMMm0 points in the Y directionN vertical levelsFor realistic regional cases, LLm0 and MMm0 are given by running
make_grid.m,and N is defined in
param.halso contains: Parallelisation settingsTides, Wetting-Drying, Point sources, Floats, Stations specifications
the compilation script (including settings for paths, compilers, libraries, etc)
CROCO namelist input file
croco.incontains several configurations settings such as: the time stepping, the vertical coordinate settings, the I/O settings and paths, some parameters for the model, … It has to be edited before running. It is available in croco/OCEAN directory for regional configurations, and in croco/TEST_CASES directory for test cases.
- Input files
CROCO needs the following input files to run:
CROCO grid file:
CROCO surface forcing file:
CROCO vertical boundary conditions:
CROCO initial conditions:
They can be created using the Preprocessing croco_tools, see dedicated tutorial. These files are eventually not mandatory in test cases for which the useful settings are defined analytically within the CROCO code.
CROCO can be run in serial or parallel mode. See the run tutorial.
CROCO usual outputs are:
CROCO restart file:
CROCO instantaneous output file:
CROCO averaged output file:
CROCO log file:
croco.logif you have defined the LOGFILE key in cppdefs.h : # define LOGFILE
Other output files can be generated depending on the settings provided in