quantum-circuits

Is your feature request related to a use case or problem? Please describe.
Right now a lot of modules (in particular tests) are pretty free form with how they do imports. It's a good practice to import modules wherever possible.

bad:

from cirq.devices import GridQubit

good:

from cirq import devices

devices.GridQubit(whatever)

**Describe the soluti

Currently the code branches a lot on the size of the operator being generated (using ints for n<30, float for n<500, bigint ootherwise). ILog2 takes care of some of that branching. See how much you can simplify the code by using it. See Krastanov/QuantumClifford.jl#47 (comment)

At the moment, QMAP provides a default set of hard-coded architectures to map to. While we allow to specify own architectures (and, in theory, calibration data) in the form of individual input files this is rather inflexible and can be improved.

It should be possible to take an arbitrary Qiskit backend in Python, e.g., anything from https://github.com/Qiskit/qiskit-terra/tree/main/qiskit/test/m

Right now, from some benchmarks (ground state, estimated state and shor) only certain instances can be chosen using the get_one_benchmark methods. This needs clear documentation on the readme.

• Documentation which benchmarks need specific values for the benchmark_instance_name parameter
• Documentation which benchmark_instance_name refers to which instance
• Documentation that fo