How should we handle different hardware?

[jordandsullivan]

In #58 I have implemented a bit of a hack to get back to the basis gateset of the target_device:

ucc/ucc/transpilers/ucc_transpiler.py

Lines 45 to 48 in 17dfdee

	if isinstance(target_device, BackendV2):
	# Map the transpiled circuit to the target backend's basis gates
	# TODO: Need to implement different final mapping passes for different backends
	transpiled_circuit = transpile(circuit, optimization_level=0, backend=target_device)

This may work for Qiskit backends, but in general we need a standard way of representing the. In this case we could get them manually for Qiskit (target_device.configuration().basis_gates) and remap ourselves, but the API will be different for different devices.

qBraid has just released an early version of a QASM semantic analyzer and parser, and it appears they are working on this very problem of basis gates: qBraid/pyqasm#73

Currently for connectivity, we are using Qiskit's CouplingMap, but this also varies somewhat between devices.

We may want to standardize e.g. schema for all hardware info we want to use in compilation. e.g. fidelities, last calibration time.