05:26 <_whitenotifier-9> [scopehal-docs] azonenberg pushed 1 commit to master [+0/-0/±1] https://github.com/glscopeclient/scopehal-docs/compare/198e1f2ae3f0...eeca84af84a8

05:26 <_whitenotifier-9> [scopehal-docs] azonenberg eeca84a - Initial skeleton documentation of scalar stairstep filter

05:27 <_whitenotifier-9> [scopehal] azonenberg pushed 2 commits to master [+2/-0/±5] https://github.com/glscopeclient/scopehal/compare/8f8f3f0ad05b...d4b5c6bfda5f

05:27 <_whitenotifier-9> [scopehal] azonenberg df5af45 - Added UnitSelector helper to FilterParameter

05:27 <_whitenotifier-9> [scopehal] azonenberg d4b5c6b - Initial implementation of ScalarStairstepFilter

06:05 <_whitenotifier-9> [scopehal-apps] azonenberg pushed 1 commit to master [+0/-0/±3] https://github.com/glscopeclient/scopehal-apps/compare/d37e1ef3e6bf...9f8b478b5430

06:05 <_whitenotifier-9> [scopehal-apps] azonenberg 9f8b478 - Changed mutex acquisition order to avoid another deadlock (when naming a texture while the waveform data mutex is already locked)

06:41 <_whitenotifier-9> [scopehal] azonenberg pushed 1 commit to master [+0/-0/±6] https://github.com/glscopeclient/scopehal/compare/d4b5c6bfda5f...3921256089b7

06:41 <_whitenotifier-9> [scopehal] azonenberg 3921256 - Refactoring: moved Refresh() to FlowGraphNode out of Filter, so that we can now refresh instrument channels that may take data streams as inputs

06:41 <_whitenotifier-9> [scopehal-apps] azonenberg pushed 1 commit to master [+0/-0/±5] https://github.com/glscopeclient/scopehal-apps/compare/9f8b478b5430...b38e05544d92

06:41 <_whitenotifier-9> [scopehal-apps] azonenberg b38e055 - Refactoring: now refresh all flow graph nodes in filter graph, even those which are not filters

08:58 <_whitenotifier-9> [scopehal] azonenberg pushed 3 commits to master [+0/-0/±7] https://github.com/glscopeclient/scopehal/compare/3921256089b7...8902a56b269a

08:58 <_whitenotifier-9> [scopehal] azonenberg b7e21b2 - Fixed bug causing filter refreshes using legacy signature to not be executed

08:58 <_whitenotifier-9> [scopehal] azonenberg 1ad9fd1 - ScalarStairstepFilter: update unit of parameters when changed

08:58 <_whitenotifier-9> [scopehal] azonenberg 8902a56 - Loads now support scalar inputs to update the set point

08:59 <_whitenotifier-9> [scopehal-apps] azonenberg pushed 1 commit to master [+0/-0/±5] https://github.com/glscopeclient/scopehal-apps/compare/b38e05544d92...cb90f82f1383

08:59 <_whitenotifier-9> [scopehal-apps] azonenberg cb90f82 - Various imrpovements to enable filter graph based control of loads

09:11 <d1b2> <azonenberg> Controlling my Siglent load using a time-varying waveform (stairstep ramp) generated from the filter graph

09:11 <d1b2> <azonenberg> https://cdn.discordapp.com/attachments/776941750291267595/1085490459226415125/power-stairstep.png

09:11 <azonenberg> Eventual plan is to add filter graph control to most things you'd twiddle with front panel knobs

09:12 <azonenberg> so you can implement feedback networks or scripted test patterns entirely in the filter graph

09:12 <azonenberg> While nothing currently implements this, the architecture allows for channels to have vector inputs too

09:13 <azonenberg> so you can in theory synthesize a waveform in a scopehal filter graph then push it to an AWG and play it back to your DUT

09:13 <azonenberg> this isnt possible yet because while we have a function generator API, we don't have full arb support in the API yet

09:13 <azonenberg> but this is the intended manner for that to be exposed

11:44 <_whitenotifier-9> [scopehal] bvernoux commented on issue #755: SPIRV linking missing for non-WIN32? - https://github.com/glscopeclient/scopehal/issues/755#issuecomment-1469854337

22:28 <_whitenotifier-9> [scopehal] azonenberg pushed 1 commit to master [+2/-0/±2] https://github.com/glscopeclient/scopehal/compare/8902a56b269a...49c04cfc7a4f

22:28 <_whitenotifier-9> [scopehal] azonenberg 49c04cf - Initial skeleton of RigolFunctionGenerator

22:31 <azonenberg> Starting work on a Rigol DG4000 series function generator driver

22:31 <azonenberg> initially just canned functions but full arb eventually

22:32 <azonenberg> Have some refactoring before that bit lands

22:38 <monochroma> any idea what the status of the siglent driver is? (specifically for the sds1104x-e)

22:40 <azonenberg> I do not know about sds1000 series

22:40 <azonenberg> some folks i think have played with it

22:40 <azonenberg> its a different software platfomr than the 2000/5000/6000 which, while slow, is pretty stable

22:40 <azonenberg> we do support the older platform but i dont know how well it's being maintained

22:41 <monochroma> ahh

22:43 <azonenberg> why? thinking of getting one?

22:43 <azonenberg> I know we have a lot of users on the newer siglent platform so while its slow and there's some quirks, it generally works well

22:53 <monochroma> i have access to one already

23:00 <azonenberg> ah ok

23:00 <azonenberg> well by all means play with it and let me know how it works