5. Config file dedicated to CROCO :**croco_config.cfg** 
########################################################

These part only describe the user input config file


It allows to the user to give some parameters to configure the different sloop tasks

* Compile model :parameters related to the compilation of CROCO
* run model   : parameters to run CROCO 
* IBC forcing : Collect and build IBC forcing files
* Atm forcing : Collect and build atmospheric forcing file
* Extract module for IBC interpolation
* Postprod configuration : Split model output file by area and step by step in multiples netcdf files


.. list-table:: Compile commands
   :header-rows: 1

   * - Section 
     - Sub-section
     - Field 
     - Description
   * - compile_model 
     -
     - *croco_config_dir*
     - Directory where to find the templates for your configuration
   * - 
     - **tpl_files**
     - *croco_param_file*
     - The preproc parameters template file for CROCO **param.h** (name must be param.h.tpl)
   * - 
     - 
     - *croco_compile_file*
     - The jobcomp script template to compile the code (name must be jobcomp.tpl)
   * - 
     - 
     - *croco_preproc_file*
     - The file containing the CPP keys that defines your configuration  (name must be cppdefs.h.tpl)
   * - 
     - **Source** 
     - *croco_src_dir* 
     - The directory containing the references sources of the croco code (**OCEAN**) 
   * - 
     - **MPI** 
     - np_xi,np_eta 
     - The number of procs along x and y dimension you want to user (nb_procs=np_xi*np_eta) 
   * - 
     -
     - nnodes  
     - In case of MPI_NOLAND feature this is the real number of cpus used (without land cpus) given by the preprocessing programm
   * - **Run model**
     - **croco_inputs** 
     - *freq_rst* 
     - Output frequency of your restart file in hours
   * -
     -
     - *freq_output* 
     - Output frequency of your main history file in hours
   * -
     -
     - *croco_forcing_dir* 
     - Directory containing the inputs files 
   * -
     -
     - *croco_frc_grid* 
     - Croco grid in netcdf format  
   * -
     -
     - *croco_frc_atm* 
     - Atm forcing file if not build by sloop-croco-run-atmfrc 
   * -
     -
     - *croco_frc_rivers* 
     - Croco runoff netcdf file if not build by sloop-croco-run-rivers 
   * -
     -
     - *croco_frc_tides* 
     - Croco tidal file in netcdf : Mandatory ! 
   * -
     -
     - *croco_frc_ini* 
     - Croco initial file in netcdf if not provided by sloop-croco-run-ibc-1-init
   * -
     -
     - *croco_frc_obc* 
     - Croco obc file in netcdf if not provided by sloop-croco-run-ibc-2-obc
   * -
     - **tpl_files** 
     - *croco_config_dir* 
     - Directory containing the user config of Croco 
   * -
     - 
     - *croco_input_file* 
     - Croco input parameters file read by croco executable (name must be croco.in.tpl)
   * - **obc_frc**
     - 
     - *model* 
     - Choice of OGCM model from which to build the IBC conditions (for now only "glorys12v1") 
   * - 
     - 
     - *out_name*
     - name of the Netcdf file collected by the script sloop-croco-run-ibc-0-collect 
   * - **atm_frc**
     - 
     - *model* 
     - Choice of atmospheric model from which to build the forcing (for now only "arpege-hr") 
   * - **extract**
     - **namelist** 
     - *file_coarse* 
     - OGCM file provided by the user if not build by sloop-croco-run-ibc-0-collect 
   * -
     -
     - *bathy_fine*
     - The croco grid file in netcdf 
   * -
     -
     - *l_zgrid*
     - Is your OGCM file on vertical Z-GRID ? 
   * -
     -
     - *b_sig,theta_sig,hc_sig*
     - Sigma parameters to define the vertical grid : Must be the same as in *croco.in* file
   * -
     -
     - *kmax*
     - Number of sigma layers : must be the same as in *param.h* file 
   * - **postprod**
     - 
     - *write_whole_domain* 
     - True if you want the sloop-croco-run-postprod-0-format-data to store the whole grid 
   * - 
     - 
     - *postprod_data_dir* 
     - path of the directory where to store the results
   * -
     - **zone1** 
     - activate 
     - True if the user want to store this sub-domain
   * -
     - 
     - lon_bnds 
     - longitudes boundaries of the sub-domain 
   * -
     - 
     - lat_bnds 
     - latitudes boundaries of the sub-domain 


     

Here is a template of the **croco_conf.cfg**

.. literalinclude:: ../templates/cfg_croco/croco_conf.cfg
            :language: ini