List view
- Overdue by 4 month(s)•Due by March 1, 2025•3/7 issues closed
- Overdue by 2 year(s)•Due by April 28, 2023•1/2 issues closed
- No due date•1/2 issues closed
The model qupulse has for AWGs is only documented via the AWG interface (https://github.com/qutech/qupulse/blob/3d6eaa68c50ac44836099c611ca6b41130868b16/qupulse/hardware/awgs/base.py#L24). It is very general (in a bad sense) and does not include more advanced device capabilities. The generality of the model currently leads to a lot of duplicated code. A more advanced and modular model of device capabilities would lead to easier to maintain code and faster implementation of drivers for new device types. Additionally, a redesign allows the addition of new features like a possible continuous mode and run-time branching if supported by the device.
No due date•5/10 issues closedPerformance: Sequencing should make use of caching mechanisms to avoid sequencing entire pulses again if only small subpulses changed (or even no change at all occured). Flexibility: It should be possible for the user to provide hints to the Sequencer (and, indirectly, hardware backends) which parameters (and thus, waveforms or sequences) are expected to change often, so that the hardware backend can set up the device such that changing these parameters is fast.
No due date•15/17 issues closed- No due date•1/1 issues closed
- No due date•2/4 issues closed
Everything concerned with the rewriting of the serialization routines for pulses (and parameters) with the goal of moving towards convenient pulses and parameter management functionality.
No due date•34/35 issues closed