-
Notifications
You must be signed in to change notification settings - Fork 144
New primitive - Executor (beta) #4083
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
base: main
Are you sure you want to change the base?
Changes from all commits
52c089f
f276a8f
981666d
08bee2e
f2203a3
7c38c60
127f518
9ce5e39
b98edee
b4851e0
4a3cdbf
3fe1601
5e4ab06
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,35 @@ | ||
| --- | ||
| title: Executor primitive (beta) | ||
| description: Executor is a lower-level primitive that provides more flexibility when customizing your error mitigation workflow. | ||
|
|
||
| --- | ||
|
|
||
| # Executor primitive (beta) | ||
|
|
||
| <Admonition type="note" title="Beta release"> | ||
| The Executor primitive is currently in beta and might not be stable. You are invited to test it and provide feedback. (((how?))) | ||
| </Admonition> | ||
|
|
||
| The Executor primitive is designed for quantum information scientists to run utility-scale experiments. Executor provides finer control over advanced techniques by shifting the generation of circuit variants to the server side, saving network costs and making the process explicit and customizable. With Executor, users can fine-tune error mitigation and other techniques to find the right balance of speed and quality in their utility-scale workloads. | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. A few comments on this paragraph:
This is what I came up with but probably can use some fine tuning:
|
||
|
|
||
| The Executor primitive benefits users who want to improve the reliability of computations on noisy quantum hardware, and are interested in capabilities such as noise learning, twirling, and expectation value calculations. With Executor, users will gain a clearer and more composable model for execution workflows, making it easier to experiment with new techniques, reproduce results, and share methods. | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. What does "the reliability of computations on noisy quantum hardware" mean? Regardless, I think the previous paragraph covers the benefit of using Executor. Perhaps this one can be simplified to
|
||
|
|
||
| ## Workflow | ||
|
|
||
| Important words to define: | ||
| - box | ||
| - annotation | ||
| - samplex | ||
| - dressing | ||
|
|
||
|
|
||
| ## NoiseLearnerV3 | ||
|
|
||
| ## Next steps | ||
|
|
||
| <Admonition type="tip" title="Recommendations"> | ||
| - Visit the Samplomatic documentation for [API references](https://qiskit.github.io/samplomatic/api/index.html) and guides, which include examples of the following: | ||
| - [Dressed boxes](https://qiskit.github.io/samplomatic/guides/dressed_boxes.html) | ||
| - [Transpiling with `generate_boxing_pass_manager()`](https://qiskit.github.io/samplomatic/guides/transpiler.html) | ||
| - [Working with samplex inputs and outputs](https://qiskit.github.io/samplomatic/guides/samplex_io.html) | ||
| </Admonition> | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -313,6 +313,8 @@ rpath | |
| rtol | ||
| rustc | ||
| rustworkx | ||
| samplex | ||
| samplomatic | ||
| satisfiability | ||
| saveas | ||
| sched | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's an open beta, so anyone can access it. They just need to install the preview branch.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jyu00 I mean, how do they provide feedback?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah sorry I misunderstood this. I thought it's asking how do they get invited 😄.
The best way to provide feedback is probably to open issues in samplomatic or qiskit-ibm-runtime repo.