Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
M MEDUSA_4.2.x
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Packages & Registries
    • Packages & Registries
    • Package Registry
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Commits
Collapse sidebar
  • acc
  • MEDUSA_4.2.x
  • Wiki
  • How to SETTE test MEDUSA.

Last edited by julpal Oct 06, 2023
Page history
This is an old version of this page. You can view the most recent version or browse the history.

How to SETTE test MEDUSA.

SETTE tests

The SETTE tests are a group of validation tests made on a regular basis onto NEMO to make sure that a bug-fix or development branch won't break the model. It enables to test that different configuration of the code will compile, run, are restartable and reproducible. It also enable to compare the code performances to a previously-tested-reference version of the code.

NEMO now uses SETTE on a regular basis using the git "continuous-integration".

We will continue to do it by hand with MEDUSA, at least for now, but of course, we want to benefit from all these tests to check MEDUSA the same way!

MEDUSA on SETTE

Clone repository
  • Compile MEDUSA from scratch
  • Developing on MEDUSA git Best practice
  • How to SETTE test MEDUSA.
  • How to run MEDUSA 1D on ARCHER2 and ANEMONE
  • How to run on ANEMONE
  • How to run on ARCHER2
  • MEDUSA DOCU : Chl light
  • MEDUSA DOCU : Rivers
  • MEDUSA Guide some useful explanations
  • MEDUSA NEMO4.2
  • MEDUSA Training How to run MEDUSA 1D ( on NOC linux system)
  • Home
  • todo_list