Use qBraid's native OriginQ provider instead of custom metriq-gym one#735
Draft
Use qBraid's native OriginQ provider instead of custom metriq-gym one#735
Conversation
- Point qbraid dependency at vprusso/qBraid@add-originq-provider which includes a native OriginQ provider (see qBraid/qBraid#1146) - Remove origin entry points from metriq-gym pyproject.toml - Update qplatform/device.py to import OriginDevice from qbraid.runtime.origin - Inline get_origin_connectivity logic (uses device.backend.chip_info() directly) - Update test constructors to match qBraid's OriginDevice API Tested end-to-end: dispatched and polled WIT benchmark on WK_C180 (180-qubit hardware).
Contributor
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tested end-to-end: dispatched and polled WIT benchmark on WK_C180 (180-qubit hardware).
Dispatch:
Poll: