Replaces the rebase pass in the tk_to_qiskit conversion with AutoRebase. It doesn't require a tk1_replacement function and so it better from the point of view of serialization. Its also a bit cleaner syntatically and allows us to delete some unecessary lines which define variables for RebaseCustom.
This PR supercedes CQCL/pytket-qiskit#386 as I don't see a reason for this to wait until the refactor of tk_to_qiskit and qiskit_to_tk is done.
As mentioned in the related issue, I'm a little puzzled that this shows up in the dict of the default_compilation_pass for IBM backends. I think it would be worth checking to see if the passes are serilaized correctly.
(please see the issue discussion CQCL/tket#1573)
Related issues
CQCL/tket#1573
Checklist
[x] I have performed a self-review of my code.
[ ] I have commented hard-to-understand parts of my code.
[ ] I have made corresponding changes to the public API documentation.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I have updated the changelog with any user-facing changes.
Description
Replaces the rebase pass in the
tk_to_qiskitconversion withAutoRebase. It doesn't require atk1_replacementfunction and so it better from the point of view of serialization. Its also a bit cleaner syntatically and allows us to delete some unecessary lines which define variables forRebaseCustom.This PR supercedes CQCL/pytket-qiskit#386 as I don't see a reason for this to wait until the refactor of
tk_to_qiskitandqiskit_to_tkis done.As mentioned in the related issue, I'm a little puzzled that this shows up in the dict of the
default_compilation_passfor IBM backends. I think it would be worth checking to see if the passes are serilaized correctly.(please see the issue discussion CQCL/tket#1573)
Related issues
CQCL/tket#1573
Checklist