proposal to improve "job estimation" comprehension
@beckykd is already working on this.
Since Jan 21, 2025.
- Dominant language
- Jupyter Notebook
- Stars
- 106
- Forks
- 223
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 72
Description
URL, if applicable
https://docs.quantum.ibm.com/guides/estimate-job-run-time
Describe the new content you are requesting.
Hi,
I suggest we clarify the goal of estimation and when it can be useful.
My first though using the provided example was to question the fact that to obtain an estimation I had to submit my job. Since the example is straightforward the estimation was even very different relatively from the execution time.
Several aspects weren't clear.
When you "estimate" on a simple circuit, it might not be very useful. But if you have a complex one, the classical computation part can take long and during this time, the estimation can help you decide whether :
- you continue
- you cancel
- or if you can afford to run a longer test on more shots, or if you need to split your circuit, etc ...
Thanks
If this new content request is accepted, do you want to write the content?
I only want to review the material when it's finished
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.