12:20 <azonenberg> So my IBC bringup scopesession has some really funky things going on with window management that i dont understand

12:21 <azonenberg> where e.g. trying to move a filter to a new area sometimes fails in completely bizarre ways

12:21 <azonenberg> That might have to be my next thing to debug

12:55 <_whitenotifier-3> [scopehal] azonenberg pushed 2 commits to master [+0/-0/±7] https://github.com/ngscopeclient/scopehal/compare/8318d30b48f6...77f8e7370b74

12:55 <_whitenotifier-3> [scopehal] azonenberg 7bfed4a - AseqSpectrometer: initial absolute irradiance support

12:55 <_whitenotifier-3> [scopehal] azonenberg 77f8e73 - Added new microamp unit

12:55 <_whitenotifier-3> [scopehal-apps] azonenberg pushed 2 commits to master [+0/-0/±9] https://github.com/ngscopeclient/scopehal-apps/compare/a5f68637cd92...b64aa4e58863

12:56 <_whitenotifier-3> [scopehal-apps] azonenberg 2d1e1c9 - Initial in-band power support

12:56 <_whitenotifier-3> [scopehal-apps] azonenberg b64aa4e - Merge branch 'master' of github.com:ngscopeclient/scopehal-apps

18:05 <d1b2> <nandly> Hi, I am trying out scopehal and ngscopeclient with Rigol DS1000z series scope. Right now, it is not possible to configure timebase due to some missing code. Sounds like something I could fix. I am confused a about interleaving feature. Scope has has one 1Gsps ADC. When there is more than one channel enabled, samplerate gets divided. This is automatic. It this that interleaving?

18:06 <d1b2> <johnsel> No, the interleaving function is for scopes that have explicit interleaving options, for he DS1k this is indeed automatic

18:07 <d1b2> <johnsel> You can thus ignore it

18:08 <d1b2> <nandly> Ok, should the GetSampleRatesNonInterleaved() take into account how many channels are enabled and return adjusted samplerates?

18:09 <d1b2> <johnsel> Looking at the Rigol driver code, what specifically can you not configure?

18:10 <d1b2> <johnsel> Oh right presumably you get no samplerates at all correct?

18:11 <d1b2> <nandly> yes, there is samplerate list only for MSO5k serises scopes

18:11 <d1b2> <johnsel> Yup makes sense, and the DS1k is m_protocol == DS_OLD I think?

18:12 <d1b2> <johnsel> The current pattern is that the samplerates are static and independent of amount of channels enabled. In theory thus you can set a value that the scope won't accept

18:12 <d1b2> <nandly> my scope is DS1kZ, and it falls into DS protocol

18:13 <d1b2> <johnsel> I would just add the samplerates as another else if

18:13 <d1b2> <johnsel> I have a task to add 10Gsa for the MSO8k series as well which I have here

18:14 <d1b2> <nandly> Yes, it's possible. I just wanted to be sure about expectations. There are no API specs I am aware of.

18:15 <d1b2> <johnsel> Well, I'm not sure how often this code is ran for one, the second is if we take into account how many channels are enabled it is confusing if some samplerates aren't available

18:16 <d1b2> <johnsel> ideally you'd have some kind of enabled parameter that you could set to false and have it show up but be impossible to select

18:16 <d1b2> <johnsel> https://github.com/ngscopeclient/scopehal/blob/77f8e7370b74501f3554e356b2c87bb664854525/scopehal/Oscilloscope.h#L524

18:17 <d1b2> <johnsel> You could implement interleaving

18:19 <d1b2> <johnsel> Thinking about it longer I don't see a reason why you can't implement 'virtual' interleaving based on the timebase selections

19:20 <d1b2> <nandly> That is gonna be interesting. You can't configure samplerate at DS1kZ copes. Instead you configure samples/div and memory depth (mine is stuck at AUTO). Samplerate is then calculated according to equation (Memory Depth = Sample Rate × Waveform Length)