Support for qubit loss #2567
Open
Support for qubit loss #2567
+1,583
−147
Conversation
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
This PR adds support for qubit loss to the QDK. In particular, it adds the following features: - Simulator with configured qubit loss will probabilistically "lose" qubits during application of noise (ie: any gates, measurements, or calls to `ApplyIdleNoise`), treating futher operations on that qubit as no-op. - Qubits that are lost return neither `Zero` nor `One` during measurement but a special `Loss` value that cannot be used in comparisons, triggering a runtime failure if it is. - `Std.Diagnostics.ConfigureQubitLoss` to configure the probability of qubit loss on any operation. - `Std.Measurement.MResetZChecked` which returns a tuple of `(Result, Bool)` by checking for qubit loss as part of measurement. - Loss checks generate into QIR by emitting the `__quantum__rt__read_loss` runtime function (may not be supported on all QIR targets). TODO: - [ ] Extension setting alongside Pauli noise for configuring loss probability during histogram generation - [ ] OpenQASM support for special measurement that returns loss bit - [ ] Python API for configuring loss probability on calls to `qsharp.run` - [ ] Samples Fixes #2484, #2483
swernli
requested review from
billti,
idavis,
minestarks and
ivanbasov
as code owners
|
Change in memory usage detected by benchmark. Memory Report for e8ac9f3
|
swernli
commented
Jul 1, 2025
| @@ -633,6 +636,11 @@ operation ccz(ctrl1 : Qubit, ctrl2 : Qubit, target : Qubit) : Unit is Adj + Ctl | |||
| h(target); | |||
| } | |||
|
|
|||
| operation mresetzchecked(q : Qubit) : Result[] { | |||
There was a problem hiding this comment.
I'm not a fan of mresetzchecked as the name here, but I'm not familiar enough with the naming conventions in OpenQASM to suggest an alternative. @idavis and @orpuente-MS, any suggestions? Something like mresetz_checked or other?
There was a problem hiding this comment.
I don't think there is a real naming standard for defs
There was a problem hiding this comment.
mresetz_checked is easier to read. I would go with that instead. About the naming standard, they use both snake_case and camelCase in the official spec. So, I would just pick one (snake case is my personal preference).
|
Change in memory usage detected by benchmark. Memory Report for 1ae48a7
|
|
Change in memory usage detected by benchmark. Memory Report for 804715b
|
|
Change in memory usage detected by benchmark. Memory Report for 6d5684f
|
|
Change in memory usage detected by benchmark. Memory Report for 14cfb62
|
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.
This PR adds support for qubit loss to the QDK. In particular, it adds the following features:
ApplyIdleNoise), treating futher operations on that qubit as no-op.ZeronorOneduring measurement but a specialLossvalue that cannot be used in comparisons, triggering a runtime failure if it is.Std.Diagnostics.ConfigureQubitLossto configure the probability of qubit loss on any operation.Std.Measurement.MResetZCheckedwhich returns a tuple of(Result, Bool)by checking for qubit loss as part of measurement.__quantum__rt__read_lossruntime function (may not be supported on all QIR targets).Additional features:
qsharp.runFixes #2484, fixes #2483