New primitive - Executor (beta) #4083
Conversation
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
| # 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?))) |
There was a problem hiding this comment.
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.
@jyu00 I mean, how do they provide feedback?
There was a problem hiding this comment.
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.
| 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.
A few comments on this paragraph:
- Technically
Executorjust does the execution (hence the name). Circuit construction with annotation happens with samplomatic. - We should mention how Executor provides this finer control... e.g. by giving users tools to specify intents
This is what I came up with but probably can use some fine tuning:
The Executor primitive and its supporting tools are designed for quantum information scientists to run utility-scale experiments that require more control and flexibility. Executor allows you to fine-tune error mitigation and other techniques without sacrificing performance by providing the ingredients to capture design intents on the client side, and shifting the costly generation of circuit variants to the server side. 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.
|
|
||
| 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. | ||
|
|
||
| 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.
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
In this initial release, Executor support focuses mostly on Pauli-twirling, noise model learning and injection, and basis changes. More support will continue to be rolled out in the near future.
2 participants
Set up a new page for the Executor primitive, making its beta status clear, and point to it from other primitives pages
FYI @jyu00