Add detailed output metadata field to cut-finder output #620
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ibrahim-shehzad
requested review from
caleb-johnson
and removed request for
caleb-johnson
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@caleb-johnson , when looking over the tutorial on automatic cut finding, I realized that under some circumstances, the user may wish to see more details of which cuts were actually found and where (in particular, what were the names and qubits associated with the gates that were involved). I added a metadata field to this effect and I wonder if an a priori commented line that lets the user see more of these details of the cut scheme is worth adding to the tutorial.