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

Fix typing of inserted UnitaryGates in quantum_volume (backport #13479) #13481

Merged
merged 1 commit into from
Nov 22, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Nov 22, 2024

Summary

There was a small typing issue in the quantum_volume implementation where there was a mismatch in the Python type and the rust type. The UnitaryGate were being added to the circuit as a rust space PyInstruction instead of a PyGate. This was incorrect as UnitaryGate is unitary and a gate type in python, this mismatch was causing subsequent transpilation or anything working with the unitaries in the quantum volume circuit from rust to mischaracterize the operations as non-unitary so things like getting the matrix would fail. This commit corrects the typing so the gates are added as a unitary operation in the rust typing.

This will get much simpler and less error prone when #13272 is implemented and we have a rust native UnitaryGate type.

Details and comments
This is an automatic backport of pull request #13479 done by Mergify.

There was a small typing issue in the quantum_volume implementation
where there was a mismatch in the Python type and the rust type. The
UnitaryGate were being added to the circuit as a rust space
PyInstruction instead of a PyGate. This was incorrect as UnitaryGate is
unitary and a gate type in python, this mismatch was causing subsequent
transpilation or anything working with the unitaries in the quantum
volume circuit from rust to mischaracterize the operations as
non-unitary so things like getting the matrix would fail. This commit
corrects the typing so the gates are added as a unitary operation in the
rust typing.

This will get much simpler and less error prone when #13272 is
implemented and we have a rust native UnitaryGate type.

(cherry picked from commit 4bb1432)
@mergify mergify bot requested a review from a team as a code owner November 22, 2024 18:03
@qiskit-bot
Copy link
Collaborator

Thank you for opening a new pull request.

Before your PR can be merged it will first need to pass continuous integration tests and be reviewed. Sometimes the review process can be slow, so please be patient.

While you're waiting, please feel free to review other open PRs. While only a subset of people are authorized to approve pull requests for merging, everyone is encouraged to review open pull requests. Doing reviews helps reduce the burden on the core team and helps make the project's code better for everyone.

One or more of the following people are relevant to this code:

  • @Qiskit/terra-core

@github-actions github-actions bot added this to the 1.3.0 milestone Nov 22, 2024
@coveralls
Copy link

Pull Request Test Coverage Report for Build 11977739916

Details

  • 3 of 3 (100.0%) changed or added relevant lines in 1 file are covered.
  • 8 unchanged lines in 2 files lost coverage.
  • Overall coverage increased (+0.007%) to 88.928%

Files with Coverage Reduction New Missed Lines %
crates/qasm2/src/lex.rs 2 92.98%
crates/qasm2/src/parse.rs 6 97.62%
Totals Coverage Status
Change from base Build 11939562727: 0.007%
Covered Lines: 79065
Relevant Lines: 88909

💛 - Coveralls

@mtreinish mtreinish added this pull request to the merge queue Nov 22, 2024
Merged via the queue into stable/1.3 with commit ddbb63c Nov 22, 2024
20 checks passed
@mtreinish mtreinish deleted the mergify/bp/stable/1.3/pr-13479 branch November 22, 2024 20:31
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.

3 participants