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 optional endpoint_id job argument #250

Open
jselig-rigetti opened this issue Feb 9, 2023 · 2 comments
Open

Support optional endpoint_id job argument #250

jselig-rigetti opened this issue Feb 9, 2023 · 2 comments

Comments

@jselig-rigetti
Copy link
Contributor

Both ExecuteControllerJobRequest and GetControllerJobResultsRequest accept either of these arguments to specify the job target:

  • quantum_processor_id, which is resolved to an endpoint using get_default_endpoint
  • endpoint_id, which is used directly

However, currently qcs::qpu::runner::{submit, retrieve_results} only support quantum_processor_id.

@jselig-rigetti
Copy link
Contributor Author

Target should be an enum, crate should redefine.

If endpoint, use directly - otherwise, continue with gateway routing decision making

@jselig-rigetti
Copy link
Contributor Author

Executable::submit_to_qpu calls translate and execute in series, which would require modifying it to accept both quantum_processor_id and endpoint_id as parameters in some situations, or duplicate QPU ids - splitting these into separate steps for the user can help maintain the distinction between the two and keep the API more straightforward.

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

No branches or pull requests

1 participant