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

Backends: incorporate gate errors information from Braket devices to unlock noise aware transpiling #25

Open
IceKhan13 opened this issue Apr 26, 2022 · 4 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@IceKhan13
Copy link
Member

IceKhan13 commented Apr 26, 2022

What is the expected enhancement?

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

Incorporate gate errors information from Braket devices to unlock noise aware transpiling.

Some of AWS devices has error rates. We can add them into instruction properties to make transpiling noise aware.

As a reference on how to leverage the error rates from Braket devices refer to https://github.com/aws/amazon-braket-examples/blob/main/examples/braket_features/Noise_models/Noise_models_on_Rigetti.ipynb

@IceKhan13 IceKhan13 added enhancement New feature or request help wanted Extra attention is needed labels Apr 26, 2022
@DarthRevan07
Copy link

@IceKhan13 Hi! I'd like to take a jibe at this. Could you assign it to me? Or does it work openly for everyone till a PR is accepted?

@JordanAWS JordanAWS assigned JordanAWS and DarthRevan07 and unassigned JordanAWS Jun 5, 2023
@JordanAWS
Copy link
Collaborator

You are welcome to work on it @DarthRevan07 ! The way it works that that whomever submits a successful PR first wins the bounty, or if multiple people want to work on an issue, you can choose to collaborate and split the bounty :)

@JordanAWS
Copy link
Collaborator

@DarthRevan07 Are you still working on this? One more day left in UnitaryHack!

@JordanAWS
Copy link
Collaborator

@DarthRevan07 It looks like you didn't have a chance to submit a PR before the close of UnitaryHACK (June 13), but if you are still interested in working on this problem, we we can offer AWS credits as an alternative to the bounty that was on this issue in the official hackathon :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants