The waveformWrap/partialWaveformBuffer mechanism is used for stim-triggered waveform mode & could be useful for spike-triggered waveform mode.
My last review (@ a86807abc1f16d90e07770a034dcabd9809196ae) raised these questions:
What does this mechanism provide that augment/contract rawDataBuffer mechanism does not? Presumed answer: extending further than horizontalRange(2) into subsequent timer period if needed.
Reason for storing a list of waveformWrap and partialWaveformBufffer values per channel? How is this essential/enhancing to the waveform wrap capabilities?
Could this mechanism be applied to spike-triggered waveform mode? If so, would this obviate need for the augment/contract rawDataBuffer machinery?
The waveformWrap/partialWaveformBuffer mechanism is used for stim-triggered waveform mode & could be useful for spike-triggered waveform mode.
My last review (@ a86807abc1f16d90e07770a034dcabd9809196ae) raised these questions:
What does this mechanism provide that augment/contract rawDataBuffer mechanism does not? Presumed answer: extending further than horizontalRange(2) into subsequent timer period if needed.
Reason for storing a list of waveformWrap and partialWaveformBufffer values per channel? How is this essential/enhancing to the waveform wrap capabilities?
Could this mechanism be applied to spike-triggered waveform mode? If so, would this obviate need for the augment/contract rawDataBuffer machinery?