unitaryfund / mitiq

Mitiq is an open source toolkit for implementing error mitigation techniques on most current intermediate-scale quantum computers.
https://mitiq.readthedocs.io
GNU General Public License v3.0
357 stars 157 forks source link

New technique: Quantum subspace expansion #818

Closed crazy4pi314 closed 1 year ago

crazy4pi314 commented 3 years ago

New error mitigation technique: Quantum subspace expansion

Problem

Mitiq needs more error mitigation techniques.

The Quantum subspace expansion paper outlines a new error mitigation technique which involves error correcting codes. This is estimated to take ~6 months dev time.

Related papers

Rough requirements

github-actions[bot] commented 3 years ago

This issue had no activity for 2 months, and will be closed in one week unless there is new activity. Cheers!

nathanshammah commented 3 years ago

Just a note that #575 and #599 were somewhat related.

github-actions[bot] commented 2 years ago

This issue had no activity for 2 months, and will be closed in one week unless there is new activity. Cheers!

github-actions[bot] commented 2 years ago

This issue had no activity for 2 months, and will be closed in one week unless there is new activity. Cheers!

rmlarose commented 2 years ago

Colab with some prototype subspace expansion code: https://colab.research.google.com/drive/1hN8jtBK9PBVCVvT8WkcNmgHSQbBkSq00?usp=sharing

github-actions[bot] commented 2 years ago

This issue had no activity for 2 months, and will be closed in one week unless there is new activity. Cheers!

bubakazouba commented 1 year ago

Hello, We have been working on this error mitigation technique and we have an RFC ready: Request For Comments (RFC) — Error Mitigation by Subspace Expansion.

We also have a PR ready as well that I'll be sending soon.

andreamari commented 1 year ago

bubakazouba, thanks for the very good work! we'll review your RFC soon!

andreamari commented 1 year ago

The Request For Comments (RFC) — Error Mitigation by Subspace Expansion has been approved!

The current draft PR is very useful to have an idea of the overall code but it is hard to review and to merge in a single shot. So for the implementation, we suggest to sequentially focus on the following sub-issues and related sub-PRs:

andreamari commented 1 year ago

Hi @bubakazouba, thanks for all you have already done about QSE! Are you also interested in working on #1812 in the next month? No problem if you can't, I am asking just to better plan the main topics for the next milestone.

bubakazouba commented 1 year ago

Hi @bubakazouba, thanks for all you have already done about QSE! Are you also interested in working on #1812 in the next month? No problem if you can't, I am asking just to better plan the main topics for the next milestone.

Yes I plan to wrap it up early july.

natestemen commented 1 year ago

I think now that #1812 is completed we can close this out. There is still #1813, but that is an improvement that can be made down the line.

Big congratulations to @bubakazouba and team, and looking forward to getting this technique into the hands of more people, along with further testing!