SAT-Inspired Eliminations for Superposition

Open data API in a single place

Provided by Zenodo

Get early access to SAT-Inspired Eliminations for Superposition API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2021.04.15 00:00
Created
2021.01.01
Available languages
English
Keywords
Quality scoring

Dataset description

This archive contains the problems, raw evaluation results and scripts for running the experiments described in the paper "SAT-Inspired Inprocessing for Superposition" by Petar Vukmirovic, Jasmin Blanchette, and Marijn J.H. Heule available at     https://matryoshka-project.github.io/pubs/satelimsup_paper.pdf The problems we used are stored in the "problems/" subdirectory, together with the required axioms. They are separated in two groups, "Theorems" and "SatisfiableOrOpen", as in the paper. In the "results/" directory, there are 5 files with names of the form "figD[a|b].csv", where D is a digit from 1 to 5. The digit corresponds to the figure from the paper, and the corresponding file contains experiment results for the figure labeled D. The columns give information about the results of the experiment run for a given prover configuration (e.g., CPU time, reported status, memory usage). Each row corresponds to one problem file, whose name is given in the "prob_name" column. The "i_solver" column corresponds to a prover. The "i_configuration" column corresponds to a configuration, where i is a natural number identifying a prover-configuration combination. Files named "fD[a|b]summary.csv" contain concise summaries of evaluation runs for a corresponding "fD[a|b].csv" file. Their columns are of the form "{solver}_{configuration}", and rows contain different statistics described in the "summary" column. The names of the configurations are self-explanatory and correspond to the ones used in the paper. For BCE, SPE, and PPE, if the configuration has no "inprocessing" in the name, the corresponding technique is used as preprocessing. The "zipperposition/" directory contains the scripts that execute the provided Zipperposition binary (compiled only for Linux) on a given problem using a given configuration. To run Zipperposition on a single problem using some configuration, you can use scripts with the name "run_*.sh", where * stands for the configuration used in the evaluation. The configuration names match the ones described in the files "fD[a|b].csv". The scripts take two arguments: (1) the path to the TPTP problem and (2) the CPU timeout. For example, to run problem with the path "~/puzzling.p" using the configuration "bce", execute     ./run_bce.sh ~/puzzling.p 240 A working installation of python3 and bash is required. The source code for Zipperposition can be obtained from the "wip-pred-elim-hlt-congruence" branch of the Zipperposition git repository: git@github.com:sneeuwballen/zipperposition.git. The binary stored in "scripts/" corresponds to compiled sources tagged with the commit hash c21457e0f0578a728a3779033bce28066bd85a2a. Compilation instructions are as in the "README.md" file contained in the git repository. Disclosure: Shortly before the CADE submission deadline, we noticed that there is a bug with HLBE implementation that caused Zipperposition to wrongly reach saturation on some unsatisfiable problems. This issue is now resolved in the git repository (starting with 22194f27327568fc5183ff63f70d7fb6e362f7e3). Due to lack of time, we could not redo the evaluation. For the evaluation on theorems, the issue affected Zipperposition negatively for all HLBE-enabled modes, and we expect to obtain better results with the new version. For the evaluation on satisfiable or unknown problems HLBE was disabled, so the results are not affected.  
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks