Bridges
A bridge does not invent instances: it encodes artefacts that another competition distributes, a circuit of a hardware verification competition for example, with a pinned toolchain. The parameter of the encoding, the depth of an unrolling, is what lets the family scale beyond the handful of instances a SAT competition kept.
Your own files work too
A bridge reads whatever file of its format you give it: mount your directory on /data and it
encodes your circuit, not only the ones a competition kept. See your problem.
What we never do
We do not redistribute the benchmarks of another competition. The repository keeps a manifest per collection, with its address, its checksum and its terms, and the files are fetched into a local cache when a bridge runs. The sizes below are what a download costs, not what this project stores.
| Bridge | Collection | Upstream distribution | Archive | Exact / checked | Terms |
|---|---|---|---|---|---|
| AIGER bridge | hwmcc10 | Hardware Model Checking Competition 2010 benchmarks | 3 MB | 30 / 31 | distributed by the competition; the Intel models are excluded from this archive for licence reasons |
| AIGER bridge | smtqfbv | AIGs of the SMT-LIB quantifier-free bit-vector benchmarks | 272 MB | 30 / 31 | published by the FMV group next to the AIGER tools, derived from the SMT-LIB benchmarks |
| freeLunch bridge | — | — | — | 0 / 0 |