qibolab
qibolab copied to clipboard
qiboteam
Quantum hardware module and drivers for Qibo.
Currently it is used internally in the QM driver, we could consider lifting to the `Platform` if it is used in a similar manner on all drivers.
Ok, I perfectly agree with this implementation, but I'd say that it is not specific to QM. I would have liked to have it in the `Platform`. But this is...
`Circuit` has its own mechanism to convey qubits' names, and we're supporting `str` names in the `Platform` in Qibolab. So, we should make use of them in the compiler. This...
The delays that QM can play should be a multiple of 4ns (=1 clock cycle) and should be longer than 16ns, due to limitations in the [`qua.wait`](https://docs.quantum-machines.co/1.2.0/docs/API_references/qua/dsl_main/#qm.qua._dsl.wait) command. It should...
Most likely not very relevant in practice, just logging it here as an interesting observation in case it pops up in the future: https://github.com/qiboteam/qibolab/pull/979#discussion_r1729255498
https://github.com/qiboteam/qibolab/pull/994#discussion_r1723546739 This can be done with [`pytest.importorskip()`](https://docs.pytest.org/en/stable/reference/reference.html#pytest-importorskip) in the modules explicitly importing it, and by manually catching `ModuleNotFoundError` in the `platform` and `connected_platform` fixtures https://github.com/qiboteam/qibolab/blob/f310266553c2c4789e10d5c226b92a66de96e242/tests/conftest.py#L99-L127 by manually invoking [`pytest.skip()`](https://docs.pytest.org/en/stable/reference/reference.html#pytest.skip).