Skip to content

Various tutorial cases for the coupling library preCICE with real solvers. These files are meant to be rendered on precice.org, so don't look at the README files here.

License

Notifications You must be signed in to change notification settings

precice/tutorials

Folders and files

NameName
Last commit message
Last commit date

Latest commit

a0071c3 · Mar 31, 2025
Mar 27, 2025
May 13, 2024
Feb 20, 2025
Mar 27, 2025
Feb 20, 2025
Feb 20, 2025
Mar 24, 2025
Feb 20, 2025
Feb 20, 2025
Mar 31, 2025
Feb 20, 2025
Feb 20, 2025
Feb 20, 2025
Mar 31, 2025
Feb 20, 2025
Mar 19, 2025
Feb 20, 2025
Feb 20, 2025
Feb 20, 2025
Feb 20, 2025
Feb 20, 2025
Feb 20, 2025
Feb 20, 2025
Feb 20, 2025
Feb 20, 2025
Feb 20, 2025
Feb 20, 2025
Mar 24, 2025
Mar 31, 2025
Jan 13, 2025
Mar 27, 2025
Feb 20, 2025
Feb 20, 2025
Feb 20, 2025
Feb 20, 2025
Mar 5, 2024
Aug 14, 2023
Dec 10, 2024
Dec 11, 2023
Jul 29, 2021
May 19, 2023
Jun 27, 2024
Apr 16, 2024
Apr 23, 2021
Apr 23, 2021
Feb 2, 2018
Mar 21, 2025
May 13, 2024

Repository files navigation

preCICE tutorials

System tests (latest components)

Important

This repository is aimed for development purposes and the default branch is develop. If you want to use the tutorials, switch to the master branch or download the latest release.

This repository contains ready-to-run tutorial cases for the coupling library preCICE. The purpose of these cases is not to teach you how to use preCICE from scratch, but to serve as starting points for setting up similar simulation cases, as well as test cases. Read more on our preCICE tutorials documentation section.

As a general rule, you can start each participant from inside their <tutorial>/<participant>-<solver> using ./run.sh. Look into these short scripts and copy the parts you need for your new case. Before running again, execute the cleaning scripts you can find at each level, to clean from this point and deeper.

Contributions to this repository are very welcome. Please refer to the page Contribute to preCICE for a few guidelines and hints to help you in this direction.

Note that we use Git LFS to version reference results. These will appear as seemingly empty files containing URLs if you don't have Git LFS installed (optional, mainly useful for our system tests).