<d1b2>
<246tnt> Unrelated, but I was wondering if there was an easy way to do this with scope hal : I have two captured signals and I want to count the number of pulses of ch1 between two rising edges of ch2. Is that doable ?
<gurki>
i found that raw sockets tend to be faster than hislip for my bubble of instruments
<gurki>
however, some tools will force you to use hislip
<gurki>
however, you tend to be so deeply tied to keysight tools for most of the instruments even offering hislip that im not fully certain youll gain much from integrating it with scopehal
<gurki>
apparently i like the word "however"
<gurki>
azonenberg: if you have some simple testscript i could try whether it breaks
Bird|ghosted has joined #scopehal
Bird|otherbox has quit [Ping timeout: 252 seconds]
<d1b2>
<azonenberg> off the top of my head, i dont think we have a filter for that. It'd be straightforward to write one, i imagine
<_whitenotifier-3>
[scopehal] azonenberg b42d1a9 - Merge pull request #875 from hansemro/siglent-2024-update-fixup Siglent: Replace :TRIG:MODE STOP with :TRIG:STOP; handle new SDS2000X+ version format
<_whitenotifier-3>
[scopehal] azonenberg closed pull request #875: Siglent: Replace :TRIG:MODE STOP with :TRIG:STOP; handle new SDS2000X+ version format - https://github.com/ngscopeclient/scopehal/pull/875
<_whitenotifier-3>
[scopehal-apps] azonenberg 081e091 - Update to latest scopehal
<d1b2>
<246tnt> Is there some way to write filters in python or lua or even glsl. Something you can do from the ui quickly for jobs like that ?
<d1b2>
<azonenberg> Not yet. There's an open high level wishlist item for both some way to script the GUI itself
<d1b2>
<azonenberg> and for some way to prototype filters in a scripting language
<d1b2>
<azonenberg> The bindings would be nontrivial, it can certainly be done
<d1b2>
<azonenberg> but it's something we'd want to get a couple people together and discuss how to make it reasonably efficient, forward-looking design that we wont have to change in a few months, and as capable as possible
<d1b2>
<azonenberg> Making something that only knows how to do one analog stream -> one analog stream would be striaghtforward
<d1b2>
<azonenberg> if you want to be able to work with protocol data etc it gets a lot more complex
<d1b2>
<azonenberg> honestly the main reason it doesnt exist yet, as with a lot of other features, is lack of time and dev resources 🙂