Andrew Zonenberg
Andrew Zonenberg
Is this still needed now that we have memory filters? Would we ever need to be able to do math on "the past 10 waveforms of channel X" without explicitly...
Closing as I think the memory feature enables all of the relevant use cases.
Factors to consider when implementing this: * Each WaveformArea is a separate surface for rendering. Do we want to support annotations spanning more than one WaveformArea? If so, where do...
In ngscopeclient, each WaveformGroup is a single window so it's perfectly reasonable to have annotations spanning multiple WaveformArea's.
First off, the file load/save functions do not actually work in ngscopeclient yet (they show a browser dialog then a warning saying the functionality is incomplete). So a partial workaround...
Additionally, we should avoid burning GPU memory on older historical waveforms. Care may be needed to ensure that we properly recycle CPU+GPU waveforms to avoid wasting time on allocations, etc.
This is probably best implemented as a filter block (under scopehal) that turns two eye patterns into an eye-like density map but using a different shader for rendering. Leaving the...
For file storage, I think this will require a bunch of settings that are currently global in the scopesession to be moved to the per-waveform metadata (and/or duplicated there, along...
All scope settings (vertical scale, trigger configuration, etc) are displayed at their current values. Historical waveforms only store sample data, not a full snapshot of scope settings.
Yes, I think that would be useful. Go ahead and file a ticket for that.