qref
qref copied to clipboard
PsiQ
Quantum Resource Estimate Format
As we discussed, it would be good to have a section of the docs discussing the design choices we made, in particular why do we have `Schema` and `Routine` objects...
We should have an example how to use `rendering` module somewhere in our docs. I'm thinking about a bit more polished version of the following: ``` import yaml from qref...
It would be great to have some more advanced examples of routines written in QART. Two that come to mind are: - Alias Sampling – add it to the documentation...
Currently defining connections is pretty verbose: ``` connections = [{"source": "a.out", "target": "b.in"}] ``` This makes some bigger Routines unnecessarily big and hard to read, which is a problem especially...
It would be great to add Qualtran -> QREF conversion. The conversion itself shouldn't live here, but we should get on one of the Qualtran weekly calls and ask where...
Currently QREF objects can come in different forms: 1. Saved to a file 2. Represented as a dictionary 3. Instances of pydantic models (`SchemaV1`) This introduces some ambiguity, as when...
Currently schema has some fields with confusing names: - `input_params` - `local_variables` - `linked_params` This naming is not very consistent, as "params" and "variables" are used interchangeably here. According to...
## Describe the bug When there's a routine with multiple through ports, it renders very badly, see below:
As @dexter2206 mentioned in https://github.com/PsiQ/bartiq/pull/136#pullrequestreview-2419346221: > After reviewing this and the QREF's counterpart of this PR I'm more and more convinced that it would be better if we had a...