-
Notifications
You must be signed in to change notification settings - Fork 34
Create iProver #182
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create iProver #182
Conversation
iProver v3.9.3 initial submission
|
@konstantin-korovin Thanks for the submission! Can you please change the name of the submission file |
|
Done.
|
removed quotes in logics
after JSONLint validation
added quotes
Summary of modified submissionsiProver v3.9.3
|
added seed
updated url
updated "command"
updated "command"
|
Just to note that some tests are failed due to iProver returning "unknown" in sat cases. which is expected as it is targeted towards unsat, apart from UF. |
updated system description link
|
@wintered I updated the link, thanks! |
#189: UltimateEliminator submission 2025 #188: Z3-Siri Submission 2025 #187: OSTRICH version 2 #186: yicesQS submission to the 2025 SMT comp #185: Bitwuzla 2025 submission. #184: Yices2 Submission SMTCOMP 2025 #183: cvc5 for SMT-COMP 2025 #182: Create iProver #181: Z3-Owl Submission 2025 #179: Z3-alpha SMT-COMP 2025 #178: Z3-Noodler-Mocha Submission for SMT-COMP 2025 #177: `bv_decide` submission 2025 #176: OpenSMT (min-ucore) submission 2025 #175: Z3-Noodler submission 2025 #172: SMTS submission 2025 #171: Bitwuzla-MachBV Submission for SMT-COMP 2025 #170: Z3-Parti-Z3++ Submission for SMT-COMP 2025 #169: STP-Parti-Bitwuzla Submission for SMT-COMP 2025 #168: SMTInterpol submission 2025 #167: OpenSMT submission 2025 #165: Amaya 2025 #164: SMT-RAT submission #163: COLIBRI submission #162: [Submission] colibri2 #156: upload z3-inc-z3++
|
@konstantin-korovin Thanks for submitting iProver to this year's SMT-COMP! We have executed your solver on a small number of benchmarks from each logic it should compete in (except the parallel track). You can find the results here:
We have not seen any incorrect results returned by your solver (compared to the expected status of the benchmarks). You can check whether all the results we have obtained are expected. If not, please let us know here. Some notes:
If you upload a new version of the solver and want to have another test run, let me know. We still have some time for that. Happy rest of the competition! |
|
@konstantin-korovin I was going to run also test runs for the Parallel track, but unfortunately it seems that iProver is the only solver that participates in quantified divisions of the Parallel track. So the divisions are going to be non-competitive. If you want the results just for your information, let me know and I will run them. |
Thanks @martinjonas! it is a pity that no other system was submitted for the quantified parallel track, hopefully next time will be different. Many thanks for the offer to run iProver but let's skip it in this iteration. |
iProver v3.9.3 initial submission