The NECCTON-algo organization hosts the algorithms developed in the framework of the NECCTON project.

Requirements to add a repository to the organization https://github.com/neccton-algo:

• Be a member of the NECCTON project
• Put the mandatory files in the respository as described here.
• Follow the recommendations as much as possible
• Complete the table here :

| Work Package 6| | Benthic-Habitat-Models | | @damianobaldan | 6.2.2 | Benthic habitat mapping markdown | | ERSEM-NECCTON | benthic-fauna | @r-millington | 5.2.1 | Benthic predators added to ERSEM for NECCTON| | Benthic_Process_models | | @QMudde | 6.2.4 | Process models for keystone benthic species | | Work Package 7&8| | FEISTY | | @KenHasteAndersen | 7.3 | Fortran and R implementation of the FEISTY fish community model | | OGSTM-BFM-Hg | neccton_WP8|@ginRosati|8.2| Marine biogeochemical mercury model| | plasticparcels | | @michaeldenes | 8.2.1 | Microplastic transport and dispersion simulation tool based on the parcels Lagrangian framework | | Plastic_Poseidon | | @tamvas3712 | 8.2.2 | Marine plastic pollution module | | MEDSLIK_II_NECCTON | | @SLiubartseva | 8.2.3 | MEDSLIK-II code for NECCTON project | | CanMETOP | | Zhiyong Xie | 8.2.5 | POPs’ Global atmospheric transport model | | ECOSMO-MERCY | | @jbieser | 8.2.5 | Marine Mercury Cycling and Bioaccumulation module | | Bfiat | | @karlines | 8.2.6 | Bottom Fishing Impact Assessment Tools | | CC Indices | | @ledm | 8.4 | Climate Change Stressor Indices |

A GitHub repository of the NECCTON GitHub organization contains the following file:

• A LICENCE file: NECCTON encourages the use of open-source licences.
• A CODEOWNERSfile: indicate the main contacts for the repository. See here for more details.
• A README file: see the minimum requirement for the README file here
• One or several Jupyter notebooks to demonstrate the algorithm and the baseline. The baseline corresponds to an existing algorithm or a minimal solution (e.g. linear regression) that the algorithm is expected to outperform.

The README file must contain a description for:

• the data source
• the baseline (or a link to the jupyter notebook of the baseline)
• the metrics used to validate the output(s) of the algorithm
• the list of dependencies (name of the dependency and full version number used) needed to use the code, and use language-specific tools to install the dependencies (recommended)
• the documentation (e.g., via a link). It should allow a potential user to understand the code and reuse it. The documentation will be available at the M36 of the NECCTON project.
• Citations and links for NECCTON publications using or introducing the code, when applicable.

In addition to the points mentionned above, it is strongly suggested to:

• Use a data API for easy access to the data when testing the code
• Make use of GitHub actions to run unit tests when pushing the code on the repository (or when merging with the main branch). See here for a documentation of GitHub actions.
• Use language specific tools (e.g. conda, pipenv) to define the running environment.
• Use the latest best coding practices. For more details, see here
• Upload code to the organization code that is specific to the NECCTON project. Other generic tools can be hosted elsewhere.