Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Performance parity with Stim #34

Open
4 tasks
Krastanov opened this issue Feb 21, 2022 · 1 comment
Open
4 tasks

Performance parity with Stim #34

Krastanov opened this issue Feb 21, 2022 · 1 comment
Labels
performance bug Something is unreasonably slow

Comments

@Krastanov
Copy link
Member

Krastanov commented Feb 21, 2022 •
edited
Loading

Stim is great at:

We have similar performance on some of these topics, but a complete comparison would be useful

See comments in d3e84c1#commitcomment-67183201 for code references
@Krastanov Krastanov added the performance bug Something is unreasonably slow label Feb 21, 2022
@Fe-r-oz Fe-r-oz mentioned this issue May 6, 2024
Closed
@Fe-r-oz
Copy link
Contributor

Fe-r-oz commented Nov 25, 2024

Hi, Stefan, Please check out the following notes 👀

Examining the stim/simulators, we can draw the following comparisons as well:

  • Graph simulator (graph_simulator)
  • Detector Error Model Sampler (dem_sampler, error_analyzer, error_matcher)

Examining the stim/glue, we can draw the following comparisons:

  • SAT/SMT solvers for Lattice Surgery merges and splits. It utilizes the Kissat SAT Solver written in C and z3-solver
  • Stabilizer ZX calculus graphs via stimzx
  • sinter for monte carlo sampling of QEC circuits.
  • crumble for "exploring and inspecting 2D stabilizer circuits (in development)"

P.S. These notes are based on a quick glance and may not cover all relevant details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
performance bug Something is unreasonably slow
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Krastanov @Fe-r-oz