You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
thread '' panicked at crates/circuit/src/interner.rs:147:14:
the caller is responsible for only using interner keys from the correct interner
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
PanicException: the caller is responsible for only using interner keys from the correct interner
How can we reproduce the issue?
run above
What should happen?
it should work. It does if I first compile against no backend, and then use those circuits as input to the backend transpile
Any suggestions?
No clue
The text was updated successfully, but these errors were encountered:
This is caused by an issue in the UnitarySynthesis for 3+ qubit blocks (when calling op.power you convert the PauliEvo gate into a UnitaryGate), which is fixed by #13591.
Out of interest: Are you using power to repeat the circuit here or are you interested in the unitary of that power? I'm asking because power converts the gate to a matrix and then computes the matrix power. To repeat the gate object, you can use op.repeat(N).
I am interested in applying the gate multiple times, which is what I expect the power op to do. There is no mention of any implementation difference between power and repeat, so an user is most likely unaware of the points you mention.
Perhaps explicitly mention the power method is numerical and thus only works for small numbers of qubits, and then point users to the repeat method in the docstring for power?
Could also do a similar cross-reference for the repeat docstrings.
Environment
What is happening?
gives
thread '' panicked at crates/circuit/src/interner.rs:147:14:
the caller is responsible for only using interner keys from the correct interner
note: run with
RUST_BACKTRACE=1
environment variable to display a backtracePanicException: the caller is responsible for only using interner keys from the correct interner
How can we reproduce the issue?
run above
What should happen?
it should work. It does if I first compile against no backend, and then use those circuits as input to the backend transpile
Any suggestions?
No clue
The text was updated successfully, but these errors were encountered: