🚧 Specify QPU Architecture via arch option#1687
Draft
MatthiasReumann wants to merge 2 commits into
Draft
Conversation
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
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.
Description
This is a work-in-progress pull request adding an
archoption to themqt-cctool that specifies the target QPU architecture / device. Eventually, the provided name should be used to load a dynamic device library and setup the QDMI device accordingly.If the architecture option is provided, the
mqt-cctool should perform transpilation. That is native gate-set decomposition, and if the architecture has a coupling map, the superconducting mapping pass1. Otherwise, these steps are skipped and the compilation is thus hardware-agnostic.My hope is that by doing / discussing this now, we can immediately test and benchmark multiple architectures more easily.
Resolves #1082.
Checklist
If PR contains AI-assisted content:
Assisted-by: [Model Name] via [Tool Name]footer.Footnotes
--fit-topology(or--fit-coupling-map) could potentially be a more suitable name instead of the generic--place-and-route. ↩