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

add QEM schema to repo #2586

Open
natestemen opened this issue Nov 27, 2024 · 2 comments · May be fixed by #2597
Open

add QEM schema to repo #2586

natestemen opened this issue Nov 27, 2024 · 2 comments · May be fixed by #2597
Assignees
Milestone

Comments

@natestemen
Copy link
Member

The development of a schema for quantum error mitigation techniques has been undergoing through an RFC, as well as a private repository. They are now at a point where they should be added, so we can start integrating them into the Calibrator and other tools.

I suggest creating a new directory mitiq/schema to add the files for the schema and work with them from there. More issues to come, but lets start simple.

cc @ecarlander @ruheenirodi comment here if you have any questions about getting these added, and let me know who I should assign to the issue.

@natestemen
Copy link
Member Author

Oh also, please add a link to the repo if you're okay with making it public. If you'd like to keep it private that's okay, but I know others want to see!

@ecarlander ecarlander linked a pull request Dec 7, 2024 that will close this issue
6 tasks
@ecarlander
Copy link
Contributor

We copied the contents out our working repo into the mitiq/schema directory, but if we should instead reserve that for more developed work we can switch back to that and I'll share the link! I also mentioned this in the PR I opened

@natestemen natestemen linked a pull request Dec 7, 2024 that will close this issue
6 tasks
@purva-thakre purva-thakre added this to the 0.43.0 milestone Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants