Skip to content
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

[ HIGH PRIORITY ] Add tutorial on error mitigation with Qiskit Runtime Sampler #1310

Open
2 tasks
kevinsung opened this issue May 7, 2024 · 1 comment
Open
2 tasks

Comments

@kevinsung
Copy link
Collaborator

kevinsung commented May 7, 2024

URL, if applicable

No response

Describe the new content you are requesting.

Split off from #1168

Relevant comment: #1168 (comment)

This tutorial is based on a summit demo and was refactored by Ritajit on Nate's team, please work with him on this issue.

  • move source file into this repo
  • review and refactor if needed. Address any feedback from product review in QTE repo

If this new content request is accepted, do you want to write the content?

I will write a draft of the proposed content

@kevinsung kevinsung assigned kevinsung and unassigned javabster, abbycross and beckykd May 7, 2024
@javabster javabster changed the title Add tutorial on error mitigation with Qiskit Runtime Sampler [ HIGH PRIORITY ] Add tutorial on error mitigation with Qiskit Runtime Sampler May 9, 2024
@kevinsung
Copy link
Collaborator Author

kevinsung commented May 20, 2024

The Sampler primitive only exposes two error suppression options, dynamical decoupling and pauli twirling, arguably neither of which counts as "error mitigation." So the centerpiece of this tutorial, in my opinion, is the demonstration of how to manually perform readout error mitigation using mthree (related: #843).

However, mthree has yet to move from the old backend.run interface to the new Sampler interface, though there is an open issue for it. The existing source notebook works around this by manually constructing and running calibration circuits in a simplified but suboptimal procedure (it only uses two calibration circuits), and even with this simplified procedure, the code is too complex to be suitable for a tutorial.

So in my opinion, further work on this tutorial is blocked by mthree moving to the Sampler interface, which again is tracked by this issue: Qiskit-Extensions/mthree#211

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants