microsoft / microsoft/qdk-ec

Tool for checking basic fault tolerance

Open
#82 0 comments 0 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

Sometimes user sees logical error rate always higher than physical error rate but not sure why this is happening. It's often a question about whether this is a decoder problem or encoder problem (how the fault-tolerant circuit is designed). Generally, user would also like to check if a constant number of combination of the physical errors would cause a logical error. None of these functionalities are easy to build from user's perspective because the simulation happens inside deq-runtime. However, if we could provide such a functionality pointing to which gadget's which error (line number), and show the syndrome information, and show which set of errors that the decoder infers, this would be pretty helpful for users.

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 investigating how the simulation runs inside deq-runtime and how fault-tolerant circuits expose gadgets and errors. The finished tool should identify the gadget and error line causing a logical error, show syndrome information, and report which physical-error sets the decoder infers.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
devtools, testing-qa
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.