preCICE Config Checker
A library that checks a preCICE configuration file for logical errors.
How does this differ from precice-tools check? This checker only checks the configuration for logical errors.
Requirements
- Python 3.10
- Pip
- Git for cloning the repository
- precice-config-graph Library. This will be installed during the Installation step below.
Installation
- Clone this repository:
git clone https://github.com/precice/config-check
cd config-check
- Create a new Python Virtual Environment (optional, but recommended):
python -m venv venv
source venv/bin/activate # On Windows, use `venv\Scripts\activate`
- Install required dependencies:
pip install .
You need to force re-install the precice_config_graph-dependency on new versions, since it is downloaded directly from GitHub. To do so, run:
pip install --ignore-installed .
Project Structure
config-check
├── .github, .idea, etc…
│
├── docs # Documentation on rules and the inner workings of this checker
│ └── ...
│
├── preciceconfigcheck # Main library files
│ ├── rules # All rules that are checked by this utility
│ │ ├── ...
│ │ └── examples # Exemplary implementations of rules to test output format
│ │ └── ...
│ │
│ ├── tests # Configuration files to test rules
│ │ └── ...
│ │
│ ├── cli.py # Main entrypoint for this checker
│ ├── color.py # Definition of colors for CLI output
│ ├── rule.py # Class of a rule and logic to check all rules
│ ├── rules_processing.py # Processes rules and handles output
│ ├── rules_utils.py # Utility functions for rules
│ ├── severity.py # Enum for specifying severity of output
│ └── violation.py # Class of a violation
│
│
├── .gitignore, LICENSE, README.md
│
├── pyproject.toml # Project configuration (dependencies etc.)
└── shell.nix # Dependencies for anyone using NixOS / the nix-package manager. Should be replaced by a flake in the future.
Checking a preCICE config
To check a preCICE configuration file for logical errors, run the following within the root of this repository:
python -m preciceconfigcheck.cli "path/to/precice-config.xml"
If you want more information about the checks that were performed and their results, use
python -m preciceconfigcheck.cli "path/to/precice-config.xml" --debug
Suggesting new Rules
We are always open to suggestions for new rules. When encountering a logical error that does not already get reviewed by our checker, please create a new issue on our GitHub repository and:
- Check that the problem is not already under development (marked with
TODOin docs/Rules.md) - Explain the problem:
- What exactly is the problem?
- Why is it a problem?
- Are there cases when this setup is valid?
- Please also provide a
precice-config.xmlfile with the error you described and one with a fix of how it should be
Metadata
Release files for precice-config-check 1.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| precice_config_check-1.0.4.tar.gz | 27.1 kB | With provenance | Details for precice_config_check-1.0.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| precice_config_check-1.0.4-py3-none-any.whl | Python 3 | none | any | Details for precice_config_check-1.0.4-py3-none-any.whl |
Total release size: 60.9 kB
Release files / precice_config_check-1.0.4.tar.gz
| Download URL | precice_config_check-1.0.4.tar.gz |
|---|---|
| Size | 27.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fecddc0291093ba4a3955ef24a08c821fd1276e4c3a1e148a28b6b40986b5c90
|
|
BLAKE2b-256 checksum How to use checksums |
9cc4abe8e977e4648899c684a8d0dcea7202e81df4d0a70f94568a65598e086e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 8, 2026.
Transparency logRelease files / precice_config_check-1.0.4-py3-none-any.whl
| Download URL | precice_config_check-1.0.4-py3-none-any.whl |
|---|---|
| Size | 33.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7a087f1d659cd0b7ea92ced5500a52391905ac1455ef819c79c61226fd7da55b
|
|
BLAKE2b-256 checksum How to use checksums |
9ac298dca4dff8fb637c71d54ada284841e59f8fadbdeee3761894c0086aee36
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 8, 2026.
Transparency logSecurity for precice-config-check 1.0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for precice_config_check-1.0.4.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 8, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.