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.

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

Add functionalities to debug a stim circuit #37

Open
7 of 10 tasks
MarcSerraPeralta opened this issue Sep 23, 2024 · 2 comments · Fixed by #40
Open
7 of 10 tasks

Add functionalities to debug a stim circuit #37

MarcSerraPeralta opened this issue Sep 23, 2024 · 2 comments · Fixed by #40
Labels
enhancement New feature or request

Comments

@MarcSerraPeralta
Copy link
Owner

MarcSerraPeralta commented Sep 23, 2024

  • Isolate individual detectors from of a circuit to be plotted individually and see if they look as expected
  • Convert logicals to detectors and plot them
  • Compute the max weight hyperedge in a DEM to see if it makes sense
  • Remove gauge detectors from dems and circuits
  • A way to plot some error in the circuit to see its location
  • Check if a DEM instruction (decomposed and undecomposed) is in a DEM
  • Get the DEM instructions present in one DEM but not in another one
  • Check if a decoding graph has disconnected subgraphs
  • A way to get the qubit label from the qubit ind (maybe this should be in the Layout class?)
  • All faults in a stim DEM trigger max two detectors
@MarcSerraPeralta MarcSerraPeralta added the enhancement New feature or request label Sep 23, 2024
@MarcSerraPeralta
Copy link
Owner Author

Instead of adding this set of tools into a debugging module, I believe that it is better to divide them into some more specific modules (because they can be used not only for debugging but for other purposes).
I propose the following: detectors, dems, and plotting (?). For the latter, I am still unsure because the performance module contains a plots.py file inside it, to it does not make sense to have a both a general and specific plotting, becayse then one does not know where to find the tools.

@MarcSerraPeralta
Copy link
Owner Author

Maybe a better classification of the modules it is regarding the inputs of the functions. For example, in a dems module, the inputs of the functions are dems (with other arguments). I believe this simplifies the problem because it is easier to access the functions as one only needs to know what is the input/object it wants to transform/operate on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant