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

Support Q-CTRL #964

Closed
3 tasks
kt474 opened this issue Jul 19, 2023 · 1 comment · Fixed by #1017
Closed
3 tasks

Support Q-CTRL #964

kt474 opened this issue Jul 19, 2023 · 1 comment · Fixed by #1017
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@kt474
Copy link
Member

kt474 commented Jul 19, 2023

Once the server side updates are ready we'll have to support Q-CTRL from the client side. Users will need to be able to indicate (and also save in their account options) they want to use Q-CTRL's primitives:

service = QiskitRuntimeService(channel="ibm_cloud", instance="...", channel_strategy="q-ctrl")

Requirements

  • An option for users to select Q-Ctrl as the error mitigation strategy. This selection can also be saved as part of save_account().
  • Raise an error if Q-Ctrl is selected but channel is not IBM Cloud.
  • Q-Ctrl only support resilience_level=1, so the provider should issue a warning if a different level is used. A warning instead of an error to allow users to switch between Q-Ctrl and regular without code change.
@kt474 kt474 added the enhancement New feature or request label Jul 19, 2023
@kt474 kt474 self-assigned this Jul 19, 2023
@kt474 kt474 added this to the 0.11.4 milestone Aug 6, 2023
@jyu00
Copy link
Collaborator

jyu00 commented Aug 14, 2023

Q-Ctrl only support resilience_level=1, so the provider should issue a warning if a different level is used. A warning instead of an error to allow users to switch between Q-Ctrl and regular without code change.

Let's hold off on this. There's discussion on whether Q-Ctrl should handle this.

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

Successfully merging a pull request may close this issue.

2 participants