COOM Suite
The COOM language is a domain-specific language for modelling product configuration problems. While currently geared towards ASP, the COOM Suite is intended to serve as a general workbench for experimentation with industrial-scale product configuration problems. It includes a (customizable) ANTLR v4 parser to convert COOM specifications into facts, and currently contains two ASP encodings for solving: one for clingo and one for hybrid solver flingo.
In addition, a prototypical UI, a range of examples and a benchmark collection with four scalable benchmark sets is provided.
If you want to cite the COOM Suite, please use the following reference
J. Baumeister, S. Hahn, K. Herud, M. Ostrowski, J. Reutelshöfer, N. Rühling, T. Schaub, P. Wanko. Towards Industrial-scale Product Configuration. CoRR, abs/2504.00013, 2025. doi: 10.48550/arXiv.2504.00013. URL https://arxiv.org/abs/2504.00013.
Usage
Look at our documentation page to see how to use the COOM Suite.
Solving
The main functionality the COOM Suite offers is converting a COOM configuration model and solving it using ASP. To do this, run
coomsuite solve examples/coom/kids-bike.coom
This will convert the given COOM file to a set of (serialized) facts, refine these facts, and finally solve them with the clingo encoding.
- Note that the direct conversion of COOM into facts is a mere serialization of
the COOM model. We make use of a preprocessing encoding to translate the
"serialized" facts into a set of "refined" facts, capturing the essence of
the configuration problem. To show the "refined" facts, run the
solvemode with option--show-facts.
Convert COOM to facts
To convert a COOM instance into a set of (serialized) facts run
coomsuite convert examples/coom/kids-bike.coom
By default, the facts are printed to the console. Optionally, an output
directory can be provided using option --output dir.
Examples
The COOM Suite contains a range of (product) configuration examples encoded in
the COOM language. They can be found in the examples/coom
directory. We highlight here only the Bike collection, containing three
examples in increasing complexity that correspond to the three COOM language
fragments defined above: the Kids,
City, and
Travel Bike.
We also provide the corresponding (serialized and refined) facts to these
examples under examples/asp.
Installation
For instructions on how to install from source or pip see our
documentation page.
1 maintainer
Metadata
1 maintainer
Release files for coomsuite 1.1.2
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 |
|---|---|---|---|---|
| coomsuite-1.1.2.tar.gz | 383.7 kB | With provenance | Details for coomsuite-1.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| coomsuite-1.1.2-py3-none-any.whl | Python 3 | none | any | Details for coomsuite-1.1.2-py3-none-any.whl |
Total release size: 501.2 kB
Release files / coomsuite-1.1.2.tar.gz
| Download URL | coomsuite-1.1.2.tar.gz |
|---|---|
| Size | 383.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8a026acca53e26677c4baaeb2803ea54202f58ab267892f46c55ef752332d58c
|
|
BLAKE2b-256 checksum How to use checksums |
ef0fd6ebc32b5fa171d8c61496f59ec2ca3e9b30588810a3cdd0978d8490ba0d
|
| 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 Apr 20, 2026.
Transparency logRelease files / coomsuite-1.1.2-py3-none-any.whl
| Download URL | coomsuite-1.1.2-py3-none-any.whl |
|---|---|
| Size | 117.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
687d93614c779748ab9764b9f20be6b77a2170095052981cf7e3e0e64ec0e158
|
|
BLAKE2b-256 checksum How to use checksums |
e9dfe66667f34c149b9e52bca7ef6443669042ce55120901401663314b05af04
|
| 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 Apr 20, 2026.
Transparency logSecurity for coomsuite 1.1.2
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for coomsuite-1.1.2.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 Apr 20, 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.
