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
Found a potential problem with how AerBackend backend deals with different two qubit gates.
It seems if you pass a NoiseModel to AerBackend you can use any two qubit gate including {ZZPhase, CY, TK2, etc} that acts between the edges defined in the NoiseModel and get a BackendResult from the simulation.
I suppose all two qubit gates will have the same "edge error" regardless of the OpType? Would it make more sense to alter the GateSetPredicate to gates which actually work on IBM? Alternatively we could consider getting the user to define a native gateset if they pass a NoiseModel.
I find "compilation" to a backend which supports such a wide range of "native" gates to be a bit strange. It seems we have the realism of the noise model and architecture but can choose any one and two qubit gates we like for the circuit that runs.
Here's an example where I run a circuit on AerBackend with the Kyiv noise model and connectivity using a CY gate and a ZZPhase
Found a potential problem with how
AerBackend
backend deals with different two qubit gates.It seems if you pass a
NoiseModel
toAerBackend
you can use any two qubit gate including{ZZPhase, CY, TK2, etc}
that acts between the edges defined in theNoiseModel
and get aBackendResult
from the simulation.I suppose all two qubit gates will have the same "edge error" regardless of the
OpType
? Would it make more sense to alter theGateSetPredicate
to gates which actually work on IBM? Alternatively we could consider getting the user to define a native gateset if they pass aNoiseModel
.I find "compilation" to a backend which supports such a wide range of "native" gates to be a bit strange. It seems we have the realism of the noise model and architecture but can choose any one and two qubit gates we like for the circuit that runs.
Here's an example where I run a circuit on
AerBackend
with the Kyiv noise model and connectivity using a CY gate and a ZZPhaseThe text was updated successfully, but these errors were encountered: