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

Priority-Setting for QPU Jobs #877

Merged
merged 4 commits into from
Apr 24, 2019

Conversation

jvalery2
Copy link
Contributor

No description provided.

@jvalery2 jvalery2 requested a review from a team as a code owner April 11, 2019 17:03
pyquil/api/_qpu.py Outdated Show resolved Hide resolved
@jvalery2
Copy link
Contributor Author

Is priority something that any QPU user can configure and expect to have applied in practice? If no, then we should make that clear so as to avoid confusion.

Mark, priority IS something that any QPU user can configure and expect to have applied while they're running on a QPU. It just won't have much of an effect for them because they're already the single primary user of the chip whenever they book time. This PR is largely for internal purposes, but it will unlock the feature for users in the event there are ever multiple lab mates or students submitting jobs through the same QMI.

@jvalery2
Copy link
Contributor Author

@notmgsk Any opposition to merging this?

@notmgsk notmgsk requested review from ecpeterson and karalekas April 20, 2019 09:50
@notmgsk
Copy link
Contributor

notmgsk commented Apr 24, 2019

@karalekas @ecpeterson

Copy link
Contributor

@ecpeterson ecpeterson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no opposition, sorry for the delay

@ecpeterson ecpeterson merged commit f22a851 into rigetti:master Apr 24, 2019
@jvalery2 jvalery2 deleted the qpu-job-priority-implementation branch April 24, 2019 19:27
@karalekas karalekas added this to the v2.7.0 milestone Apr 29, 2019
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

Successfully merging this pull request may close these issues.

6 participants