Repository navigation
QFw: open the recipe's status probe through the packaged adapter - #164
Merged
Merged
Conversation
The Braket recipe's device-status snippet registered the device library by hand through mqt.core.qdmi.driver, which MQT Core 3.9 had. On the MQT Core 4.1 stack that #147 moved QFw to, that module is gone, and the packaged adapter opens the device instead, so the snippet failed with a ModuleNotFoundError on a current installation. Open the device the way QFw's Braket profile does, through amazon.braket.qdmi.qiskit.AmazonBraketBackend, and read the status from its device. Checked on the current stack: Cepheus-1-108Q reported BUSY inside its window with a queue ahead of it, SV1 IDLE. Signed-off-by: Doug Oucharek <dougso@me.com>
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.
Docs only. The Braket recipe's device-status snippet registered the device library by hand through
mqt.core.qdmi.driver, which MQT Core 3.9 had. On the MQT Core 4.1 stack that #147 moved QFw to, that module is gone and the packaged adapter opens the device instead, so the snippet failed with aModuleNotFoundErroron a current installation.The snippet now opens the device the way QFw's Braket profile does, through
amazon.braket.qdmi.qiskit.AmazonBraketBackend, and reads the status from its device. Checked on the current stack: Cepheus-1-108Q reportedBUSYinside its window with a queue ahead of it, SV1IDLE.