Skip to content

We no longer have backends that use fixed rep rate #3005

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
1 of 5 tasks
jyu00 opened this issue Apr 16, 2025 · 0 comments · Fixed by #3057
Closed
1 of 5 tasks

We no longer have backends that use fixed rep rate #3005

jyu00 opened this issue Apr 16, 2025 · 0 comments · Fixed by #3057

Comments

@jyu00
Copy link
Collaborator

jyu00 commented Apr 16, 2025

URL to the relevant documentation

https://docs.quantum.ibm.com/guides/repetition-rate-execution

Select all that apply

  • typo
  • code bug
  • out-of-date content
  • broken link
  • other

Describe the fix.

In the linked page, the first sentence says Most IBM® quantum processing units (QPUs) execute circuits at a fixed rate., which is no longer true. All of our backends use dynamic rep rate now, and we should just remove the mention of fixed rep rate.

Having said that, I think there's value in keep the page to explain what rep delay is and how to set it. Although it should explain while we do circuit0_shot0 -> circuit1_shot0 etc, there is no guarantee on the order the circuits from PUBs are executed. e.g. if you submit pubs=[pub1, pub2], there is no guarantee the circuits from pub1 will run before pub2.

@jyu00 jyu00 added bug 🐛 content 📄 needs triage 🤔 this issue needs to be prioritized by the docs team labels Apr 16, 2025
@abbycross abbycross removed the needs triage 🤔 this issue needs to be prioritized by the docs team label Apr 17, 2025
github-merge-queue bot pushed a commit that referenced this issue May 1, 2025
closes #3005

---------

Co-authored-by: Frank Harkins <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants