Do you enjoy improving whatever you can? Did you find a bug in preCICE or one of the adapters? Have you developed a new simulation that could serve as a tutorial? We can use your help!
You (yes, you) have already found something that can be improved in this website:
maybe an unclear part, maybe a broken link, maybe even a small typo.
Simply click the
Edit me button at the top of the respective page to see
the source file of the page. You can then click
Edit this file
and submit your changes as a Pull Request on GitHub.
Don’t worry: you cannot break anything! We will review your suggestions
and merge them as soon as possible.
We migrated our documentation from multiple different sources to this website in December 2020 and some topics may still be incomplete. This is a perfect opportunity to contribute!
We keep each issue in the repository that contains the respective code, mainly:
Please follow the issue template of each repository and provide as much information as possible, in particular the affected versions, error logs, and configuration files involved. However, it would also help if you select the files you upload and avoid sending complete simulation cases via cloud services.
In any case, you can use Markdown to format your message and in particular your code/log snippets.
Testing upcoming versions
When we try to fix an issue or to offer new functionality, we contribute and discuss in Pull Requests. You can help us test the new features by trying a pull request.
You can also use preCICE from the develop branch and report anything suspicious before we release it.
After working on your new simulation case, you may want to share it with the community to use as a starting point, or to demonstrate a new feature. We welcome contributions to our tutorials repository and we will discuss it with you over a few review iterations.
A few guidelines:
- Contribute only the files necessary for running the tutorial (no results or user-specific files).
- Provide a
README.mdfile documenting the scenario setup, the dependencies, how to run it, how to visualize the results, and an example picture or video of the results.
- Provide run scripts (
Allrun) to run your cases.
- Provide an
Allcleanscript to clean any derived files of the simulation.
- If there is already a
precice-config.xmlfor the case you are simulating, please use the same one (or contribute changes to that). We want that all solvers that can simulate a given case use the same preCICE configuation file.
- Clean-up the files: remove commented-out code, remove scripts that are not needed.
- Naming conventions:
- Directories use
-to separate words, not
_, and only use lowercase.
- Data and mesh names should start with uppercase and use
- Data names are in singular, e.g.
- Mesh names start with the participant/domain name, e.g.
- Watchpoints should be describing the point, not use a generic name.
- Directories use
We are currently working in restructuring our tutorials and we will be able to provide more guidelines soon.
You can pick up issues that you would like to work on from any repository you like. You may be particularly interested in the good first issues and we definitely need help in the help wanted issues. The same labels exist in every repository.
Helping other users
We would really appreciate it if you followed our community channels and joined us in answering questions. It is often much easier that you think!