Fix DD documentation inconsistency for reset qubits - #5511
Open
t-imamichi wants to merge 1 commit into
Open
Conversation
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
Contributor
|
One or more of the following people are relevant to this code:
|
Member
Author
|
The CI error does not appear to be related to my fix.
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The DD option and the figure shown below are inconsistent.
Because
dynamical_decoupling.skip_reset_qubitsdefaults to False, the XX sequence is also applied to q2.To match the figure,
dynamical_decoupling.skip_reset_qubits=Trueshould be specified.In general, setting
dynamical_decoupling.skip_reset_qubits=Trueprovides better accuracy because it avoids applying DD sequences to reset (clean) qubits, as illustrated in the figure. However, the default value remains False for backward compatibility.Reference: https://quantum.cloud.ibm.com/docs/en/guides/estimator-options#available-options