Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
add multichannel extension to TablePulseTemplate and adapt tests to the
new data types, also add multichannel to TableWaveform and stubs for combining single-channel pulses into one multichannel pulse
- Loading branch information
Showing
5 changed files
with
185 additions
and
138 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
a12d7e0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While I see the need for multichannel pulse definitions, I think it would be better to realize them be aggregating several single-channel pulses. Our entire architecture currently assumes that a PulseTemplate represents a single channel and thus all pulse templates as well as the sequencer needs to be adjusted, not just the TablePulseTemplate. For the conditional pulses, this might prove to be difficult.
However, it might be worth a shot, since it will probably be easier to use.. Just keep in mind that this entails some changes to parts of the system, that might not be obvious at first.
a12d7e0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have no mechanism yet for coordinating different channels at the same time, do we? I thad a look at the sequencer and other things to make them multichannel-aware. However, a "parallel" equivalent to SequencePulseTemplate would be necessary and I have not yet finished that. This thing would enable us to combine different pulses on different channels (like a FunctionPulseTemplate and a TablePulseTemplate).
For now I need multichannel-pulses without conditions that work with an awg and dac device, including some way to extract measurement window. Therefore I hope that, for now, just making sure all parts of a pulse have the same number of channels is good enough. That does not hold in the future, of course.