You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
not essential, since it is a feature present mostly for user's simplicity (instead, while generating the assembly, we can also use Python variables, which will be simpler for us)
it may be useful to validate further scripts, or to accept users' provided snippets
however, the stride required to reset the bin counter can be computed ahead of time, and it should be possible to add the reset inside and outside the shots loop without any conditional (or, at least, without any extra register - since the stride is fixed)
probe and acquisition may use a single sequencer, in io mode
especially for the QRM-RF (the only one we use for acquisition), there is a single input and a single output, so we can just connect any sequencer to both, instead of using one for each of them (and multiplexed channel)
the hook used by the mocking mechanism has to be replaced, because unreliable
it is only working because the module is imported dynamically after the hook has already replaced the Qcodes module attribute
if, by any chance, the qblox.cluster module gets loaded before the hook is installed, the original function is captured, and it's not replaced by changing the module attribute
sweep readout duration
this is not currently happening in Qibolab, but it would generate an error while resolving the integration length
An accumulator for some items which will exceed #868 and #1088
.DEF
directivesshots
bin counter resetio
modeqblox.cluster
module gets loaded before the hook is installed, the original function is captured, and it's not replaced by changing the module attributeqibolab/src/qibolab/_core/instruments/qblox/config.py
Lines 116 to 121 in 1614166
The text was updated successfully, but these errors were encountered: