Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Document that shot order is execution order in the sampler

Open Beginner friendly
  • Is something wrong?
#5,808 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Domain
documentation, quantum-computing

Research direction

Start with the guide at the linked URL and find the places where it says "shot order". Confirm the claim against the linked Stack Exchange answer, then add a sentence stating that shot order is execution order within a batch. Done when the guide states this explicitly at those points and the page still builds.

Written by the indexing model from the issue text.

Description

content 📄
URL to the relevant course

https://quantum.cloud.ibm.com/docs/en/guides/sampler-input-output

Select all that apply
  • new content request
  • typo
  • code bug
  • out-of-date content
  • broken link
  • other
Describe the fix or the content request.

In https://quantum.cloud.ibm.com/docs/en/guides/sampler-input-output, it mentions "shot order" a couple of times, but doesn't explicitly say what the order is with respect to. I think it would be worth documenting that the order is execution order, within a batch.

I am opening this issue after answering this question: https://quantumcomputing.stackexchange.com/questions/46462/is-the-per-shot-order-in-qiskit-ibm-runtime-samplerv2-results-the-hardware-execu

For new content requests - if the request is accepted, do you want to write the content?

I can help the team by providing enough information or by referring them to a specific Subject Matter Expert to write the material

Dominant language
Jupyter Notebook
Stars
108
Forks
236
Avg merge
2d 11h
Merged PRs (30d)
73

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from Qiskit/documentation

All issues in Qiskit/documentation

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.