Skip to content

Conversation

@Zahrinas
Copy link
Contributor

No description provided.

@Zahrinas Zahrinas changed the title Create Z3-Owl.json Submission: Z3-Owl Jun 13, 2025
@github-actions
Copy link

github-actions bot commented Jun 13, 2025

Summary of modified submissions

Z3-Owl

Z3-4.15.2.0

@Zahrinas Zahrinas marked this pull request as ready for review June 13, 2025 17:45
@Zahrinas Zahrinas changed the title Submission: Z3-Owl Z3-Owl Submission 2025 Jun 13, 2025
@bobot bobot added the submission Submissions for SMT-COMP label Jun 14, 2025
@wintered
Copy link
Contributor

wintered commented Jun 16, 2025

@Zahrinas Thank you for submitting your derived tool! Please also submit the corresponding base solver to comply with the rules. Thanks!

martinjonas pushed a commit that referenced this pull request Jun 23, 2025
#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++
@martinjonas
Copy link
Contributor

@Zahrinas Thanks for submitting Z3-Owl to this year's SMT-COMP!

We have executed your solver on a small number of benchmarks from each logic it should compete in. 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). There are some benchmarks where the output of your tool is not valid according to the rules (and SMT-LIB specification). For example, it outputs

calling pysat
unsat

when it should reply only unsat. These results are categorized as unknown.

You can check whether all the results we have obtained are expected. If not, please let us know here.

Some notes:

  • We have used less resources than will be used in the final runs.
  • The benchmarks are scrambled by the official scrambler with seed 1.
  • The column status shows whether your solver decided the benchmark as sat (true) or unsat (false).
  • You can click on the value in the status column to see the output of your solver on that benchmark.

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!
Martin

@martinjonas
Copy link
Contributor

@Zahrinas Thanks for submitting the solver. As Dominik already wrote here earlier, according to the rules, for each derived solver also the corresponding base solver must be submitted (non-competitively). Look here for an example. Please, also create a submission for the base solver of Z3-Owl as soon as possible. In case you do not submit the base solver by the end of Thursday July 03 AoE, we will have to disqualify Z3-Owl from the competition.

@Zahrinas
Copy link
Contributor Author

Zahrinas commented Jul 2, 2025

@martinjonas Thanks for your reply. I have added the base solver submission and fixed the output issue mentioned. Please comment further if still there are problems.

@martinjonas
Copy link
Contributor

Perfect, thanks a lot for the quick fix!

@martinjonas martinjonas merged commit 1a690b8 into SMT-COMP:master Jul 2, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

submission Submissions for SMT-COMP

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants