<_whitenotifier-e>
[scopehal] mandl ce649a6 - Fix SetChannelCoupling for MODEL_SIGLENT_SDS1000 Fix SetChannelOffset for MODEL_SIGLENT_SDS1000
<_whitenotifier-e>
[scopehal] mandl 591511e - Merge branch 'azonenberg:master' into master
<_whitenotifier-e>
[scopehal] mandl 4f3f410 - Fix SetSampleDepth restart trigger if active Fix GetSampleRatesInterleaved checked with handbook and datasheet
<_whitenotifier-e>
[scopehal] azonenberg 5bdac7e - Merge pull request #543 from mandl/master Fix SetChannelCoupling for MODEL_SIGLENT_SDS1000
<azonenberg>
mubes: just added you to the scopehal repo as a committer since you've been the main siglent driver maintainer for a while
<azonenberg>
So now you can merge PRs against the siglent driver to master without having to go through me
<azonenberg>
Please still file a PR or otherwise check with me prior to making any changes elsewhere in the code, but for siglent stuff i'll trust your judgment
<azonenberg>
same deal, you can make edits to the siglent driver documentation at your discretion but check with me for other edits
<d1b2>
<mubes> Thats just a hint to update my documentation 😁 @mandl / @dannas A few words for the SDS1000 driver in the docs would be handy if you can find the time...
<azonenberg>
Lol. I really need to do a lot more work on docs
<azonenberg>
that's one of the biggest things i want to improve upon before calling it ready for v0.1
<azonenberg>
the other thing i want to at least start by v0.1 is export capability
<azonenberg>
being able to get data out of glscopeclient into other tools
<azonenberg>
I have the early skeleton of that developing now
<azonenberg>
CSV and Touchstone will probably be the initial formats then we can add others as we see fit in the future
<azonenberg>
At least initially exports will be very gui driven
<azonenberg>
we can think about how to make it more headless-friendly later
<azonenberg>
but there is a lot of configuration that has to be made in order to specify mappings of channels etc
<d1b2>
<mubes> You're right through, a UI fairy would be a really nice thing to have....there is so much functionality in here, but it could do with being more visible - some of it is well hidden
<azonenberg>
Exactly
<azonenberg>
we need a lot of UI development, and we need a lot of documentation
<azonenberg>
and right now i'm the only one doing that on the core (not counting driver specific docs)
<azonenberg>
And there's just more work than one person can do in those departments
<azonenberg>
miek: so i fixed the doc bug causing the CI error, but i still do want doc build logs recorded for tracking down future issues of this sort
<azonenberg>
this is slightly less critical than it was a few hours ago though