01:01 <d1b2> <hansemro> overlay average?

01:06 <azonenberg> Hmmm i'm not sure i like the term "overlay" as that implies it's drawn over the original waveform

02:48 <d1b2> <aleksorsist> Perhaps put it into an "acquisition" category of filters? Versus the x axis one which is more of a measurement

03:35 <d1b2> <azonenberg> Right now the x axis one is under "math"

03:35 <d1b2> <azonenberg> my distinction, generally speaking, is that measurements reduce a lot of data down to much less

03:36 <d1b2> <azonenberg> either waveform -> scalar or waveform -> one value per (cycle, rising edge, packet, whatever)

03:36 <d1b2> <azonenberg> while math operations are 1:1 except for resampling blocks

11:48 <_whitenotifier-b> [stm32-cpp] azonenberg pushed 1 commit to master [+0/-0/±4] https://github.com/azonenberg/stm32-cpp/compare/54baf004b014...3d7d7c713466

11:48 <_whitenotifier-b> [stm32-cpp] azonenberg 3d7d7c7 - Initial I2C support for STM32L031

15:36 <_whitenotifier-b> [scopehal-apps] hansemro opened pull request #635: ngscopeclient: handle m_metricsDialog and m_historyDialog on dialog close - https://github.com/ngscopeclient/scopehal-apps/pull/635

15:39 <_whitenotifier-b> [scopehal-apps] azonenberg closed pull request #635: ngscopeclient: handle m_metricsDialog and m_historyDialog on dialog close - https://github.com/ngscopeclient/scopehal-apps/pull/635

15:39 <_whitenotifier-b> [scopehal-apps] azonenberg pushed 2 commits to master [+0/-0/±2] https://github.com/ngscopeclient/scopehal-apps/compare/2ce02e14213f...ae614866fd4c

15:39 <_whitenotifier-b> [scopehal-apps] hansemro 86e58fa - ngscopeclient: handle m_metricsDialog and m_historyDialog on dialog close This fixes History and Performance Metrics menu items being greyed out after closing its respective dialog menu.

15:39 <_whitenotifier-b> [scopehal-apps] azonenberg ae61486 - Merge pull request #635 from hansemro/metric-history-dialog-close ngscopeclient: handle m_metricsDialog and m_historyDialog on dialog close