microsoft / microsoft/qdk-ec

Loss support (better version: Pauli envelop)

Open
#90 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
64
Forks
16
Avg merge
1d 5h
Merged PRs (30d)
5

Description

An upgrade from naive random imputation (#75 ): https://arxiv.org/pdf/2603.04156

Is your feature request related to a problem? Please describe.
Qubit loss is a critical feature for atom/ion platforms, but currently deq can only handle Pauli noises. Although in principle deq provides the flexibility of changing probabilities at runtime, there is no such tool that can easily do it. Ideally, user would want to declare loss noise in the gadgets (as an extension to stim), and then deq should absorbs all the complexity inside, instead of requiring user to provide probability modifiers.

Describe the solution you'd like
Adopt the state of the art loss decoding technique: Pauli envelop. Need more in-depth analysis under the context of dynamic logical circuits for a systematic implementation.

Describe alternatives you've considered
Alternative would be to treat loss as erasure and simply set weight to 0 of some edges. This would be suboptimal but should be an alternative approach that's available for benchmarking.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the linked Pauli-envelop paper and issue #75, then analyze how loss should work with dynamic logical circuits. Compare the proposed Pauli-envelop approach with the erasure alternative and define what a systematic implementation and benchmarking path would require.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.