CORAL - simulation manager for NEMO - is a collaborative job submission script manager for NEMO

Pierre-Yves Barriat d16a8913b6 Merge templates 7 роки тому
archive 6a8837f120 Initial commit 8 роки тому
nemo c68f763adc New GNU ELIC template + bugFix's 7 роки тому
templates d16a8913b6 Merge templates 7 роки тому
utils 6a8837f120 Initial commit 8 роки тому
zone 6a8837f120 Initial commit 8 роки тому
.gitignore 6a8837f120 Initial commit 8 роки тому
AUTHORS 6a8837f120 Initial commit 8 роки тому
BUGS 6a8837f120 Initial commit 8 роки тому
LICENSE 6fb1416ef8 Initial commit 8 роки тому
NEWS 6a8837f120 Initial commit 8 роки тому
README.md a955998b8d Update 'README.md' 7 роки тому
TODO 6a8837f120 Initial commit 8 роки тому
coral 6a8837f120 Initial commit 8 роки тому
setup-coral.sh 6a8837f120 Initial commit 8 роки тому

README.md

Coral - simulation manager for NEMO

Purpose

Coral is a collaborative job submission script manager for the NEMO (Nucleus for European Modelling of the Ocean) modeling framework Documentation. With Coral, you can use and re-use job submission scripts designed and tested by your colleagues. You can ammend them in an easy way, and generate a submission script tailored to your needs. Then, you can share your script with your colleages.

Overview

  • Run 'coral -h' to get a list of Coral commands, and 'coral <command> -h' to get help for a specific <command>
  • Please see the Documentation for common usages and change log.
  • Having trouble? Get help with Troubleshooting

Features

Once Nemo and Coral are properly installed, you can create a working submission script in three commands:

  • coral init: initiate a set of configuration files (with working default values on the cluster) for the experiment features, data location, restart options, etc.
  • coral build: create a submission script from the configuration files
  • coral submit: submit the job, with options to run tests locally, ignore automatic job resubmission, restart from scratch, etc.

At each stage, you can act manually to adapt the workflow to your liking.

Once the job is submitted, you can simply run 'coral status' in the run directory to get an overview of what is happening. No need to look for job ids, or output files.

Requirements

NEMO & XIOS source code: see How to get NEMO from scratch

Install

Clone the Coral repository (for instance in the EXTERNAL directory of your NEMO install)

cd $HOME/modeles/nemo/3.6/EXTERNAL
git clone ssh://egit/TECLIM/Coral.git coral

and update your shell startup script to source the 'setup-coral.sh' file to add 'coral' to your PATH variable.

configure_nemo()
{
  [...]
  source $HOME/modeles/nemo/3.6/EXTERNAL/coral/setup-coral.sh
}

Getting started

NEMO & XIOS must be compiled: see How to compile NEMO

Create a NEMO config experiment

cd $HOME/modeles/nemo/3.6/CONFIG
# Create new experiment
./makenemo -n ORCA1_LIM3_REF -d "OPA_SRC LIM_SRC_3" -m myARCHfile -j0
# Check your CPP keys
vi ORCA1_LIM3_REF/cpp_ORCA1_LIM3_REF.fcm
# Compile
./makenemo -n ORCA1_LIM3_REF -m myARCHfile -j4

Create a Coral instance

cd ORCA1_LIM3_REF
mkdir CORAL00
cd CORAL00
coral -h
coral init -h
coral list
coral init elic_gnu

Acknowledgments

  • Thanks @dfr for initializing this project.

Contributors

License

This project is under the Creative Commons CC0 1.0 Universal License. See the LICENSE file for the full license text.