Skip to content

Early RU changes and dry-run - #5869

Draft
Rebecca Dimock (beckykd) wants to merge 20 commits into
mainfrom
bd-RU-early
Draft

Rebecca Dimock (beckykd) wants to merge 20 commits into
mainfrom
bd-RU-early

Conversation

@beckykd

@beckykd Rebecca Dimock (beckykd) commented Oct 27, 2026 •

Copy link
Copy Markdown
Collaborator

For release Nov 2

@review-notebook-app

Copy link
Copy Markdown

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

Comment thread docs/guides/_toc.json Outdated
Comment thread docs/guides/local-testing-mode.ipynb Outdated
Comment thread docs/guides/local-testing-mode.ipynb Outdated
@abbycross abbycross changed the title Early RU changes Early RU changes and dry-run Oct 28, 2026
Comment thread docs/guides/dry-run-jobs.mdx Outdated
Comment thread docs/guides/dry-run-jobs.mdx Outdated
Comment thread docs/guides/dry-run-jobs.mdx Outdated
Comment thread docs/guides/dry-run-jobs.mdx Outdated
Comment thread docs/guides/dry-run-jobs.mdx Outdated

- It runs in IBM Quantum Compute Service in the cloud, not on your machine.
- It is calibrated like the real device at any given time. The calibration is live, not a snapshot.
- Its results keep the expected schema but contain randomized mock data. They are not actual or simulated measurement results, so do not use them to check physical correctness.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should mention they follow the shape expected on the result on the QPU.

Comment thread docs/guides/dry-run-jobs.mdx Outdated
Dry-run usage is not charged, does not consume your plan allocation, and does not count against any limits.

<Admonition type="caution">
Do not use `job.usage_estimation` for a dry-run usage estimate. That property exists on every job, is expressed in seconds, and on a dry-run job it describes the mock job, not a job on the real QPU. To find the number of RUs that the real QPU would charge, use `job.usage(resource_units=True)`.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't fully understand this part:

That property exists on every job, is expressed in seconds, and on a dry-run job it describes the mock job, not a job on the real QPU

We should say something like, while this property exists, the real usage estimation would be on the usage method from the dry-run job.

Comment thread docs/guides/dry-run-jobs.mdx Outdated
Comment thread docs/guides/dry-run-jobs.mdx Outdated
Comment thread docs/guides/dry-run-jobs.mdx Outdated
Comment thread docs/guides/dry-run-jobs.mdx Outdated
Comment thread docs/guides/dry-run-jobs.mdx Outdated
Comment thread docs/guides/dry-run-jobs.mdx Outdated
Comment thread docs/guides/dry-run-jobs.mdx Outdated
Comment thread docs/guides/dry-run-jobs.mdx Outdated
Comment thread docs/guides/execution-modes.mdx Outdated
Comment thread docs/guides/dry-run-jobs.mdx Outdated
Comment thread docs/guides/dry-run-jobs.mdx Outdated
Comment thread docs/guides/dry-run-jobs.mdx Outdated
Comment thread docs/guides/dry-run-jobs.mdx Outdated
Comment thread docs/guides/dry-run-jobs.mdx Outdated
Comment thread docs/guides/dry-run-jobs.mdx Outdated
Co-authored-by: Fran Cabrera <francabrera@users.noreply.github.com>
Comment thread docs/guides/dry-run-jobs.mdx Outdated

This branch was successfully deployed

1 active deployment
pr_preview — 6e733878 Deployed Oct 29, 2026 by github-actions[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

3 participants