Investigate PEC example with fewer shots
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 106
- Forks
- 223
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 72
Description
URL to the relevant guide or resource
https://qiskit.github.io/documentation/pr-5028/docs/guides/executor-examples
Select all that apply
- new content request
- typo
- code bug
- out-of-date content
- broken link
- other
Describe the fix or the content request.
The PEC example in #5028 uses 900 randomization x 1000 shots each, which seems a bit excessive. Estimator default uses 32 randomization x 128 shots each. We should do some investigate to see if we can bring these numbers down, so it doesn't take 10 minutes of QPU time (which makes it difficult for open plan users to try).
For new content requests - if the request is accepted, do you want to write the content?
I will write (or already have written) a draft of the proposed content
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the PEC example in the executor-examples guide from PR #5028 and compare its 900 randomizations × 1000 shots with the Estimator defaults of 32 × 128. Investigate whether lower values preserve the example's purpose, then verify that the guide no longer requires roughly 10 minutes of QPU time.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook
- Domain
- documentation, performance
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100