Bus connectivity #347
Replies: 2 comments 2 replies
-
I think we should do what you mentioned but on the sequencer level, not the output. Each line is connected to a sequencer that always has two ports. In case of mw gate we are using both pulses and we activate hw modulation on the sequencer, for the flux pulses we do a trick on this general formulation and we map two sequencers to the same port and we swap the waveforms for one of them, but we are still talking about two different sequencers for two different buses. I see two problems with mapping to an output:
|
Beta Was this translation helpful? Give feedback.
-
I like that implementation, nothing agains it. |
Beta Was this translation helpful? Give feedback.
-
Currently the bus contains the following information (ignoring all the
id_
andcategory
values):But this information is not complete. Ideally we would like to map a
Bus
to an output of an instrument, such that we could call:and the
Bus
knows which sequencer to update (because it knows the output of the instrument, and internally the instruments knows the sequencer-output mapping).In the runcard, we could do something like:
However we have the following problem: what if more than one sequencer is mapped to an output / pair of outputs? Should we update both sequencers when doing:
???
Beta Was this translation helpful? Give feedback.
All reactions