COYOTE (COmmon Yac Output Toolbox Environment)

Dependencies

YAC

• COYOTE depends on YAC. To build COYOTE please install YAC first. As coyote is build as a shared library you might want to specify -fPIC as a compile flag. The build system of COYOTE detects YAC using pkgconfig. Please set PKG_CONFIG_PATH accordingly to find YAC.
• COYOTE uses cmakes FindMPI.cmake for finding MPI. This must be the same MPI version as YAC uses.

Installation with pip

To use the python interface of COYOTE you can install COYOTE via pip with

python -m pip install git+https://gitlab.dkrz.de/nils/coyote.git

Installation with ICON on levante

/sw/spack-levante/python-3.9.9-fwvsvi/bin/python -m venv ./venv --prompt icon
. ./venv/bin/activate
git clone --recursive git@gitlab.dkrz.de:icon/icon.git icon
pushd icon
(cd externals/yac && git checkout release-3.3.0)
mkdir build
cd build
../config/dkrz/levante.gcc --enable-openmp --with-pic --prefix=$(cd ../../venv && pwd -P)
make -j32
(cd externals/yac && make install)
popd
export PKG_CONFIG_PATH=$(pwd -P)/venv/lib/pkgconfig
export MPI_ROOT=/sw/spack-levante/openmpi-4.1.2-mnmady
python -m pip install git+https://gitlab.dkrz.de/nils/coyote.git

Contributing

• Ensure the use of .clang-format and ruff configurations provided in your dev-env. The pre-commit-config would ensure that the clang-format and ruff points out to the warnings from its static code analysis before the commit gets staged. Do not over-ride it but aim to fix it.
• Try to write atleast 1 test per feature developed
• Ensure that the MR and Issues are created using appropriate templates