Degi has quit [Ping timeout: 250 seconds]
Degi_ has joined #scopehal
Degi_ is now known as Degi
bvernoux has joined #scopehal
bvernoux1 has joined #scopehal
bvernoux has quit [Ping timeout: 260 seconds]
bvernoux1 is now known as bvernoux
<
azonenberg>
ok so the CNC microscope demo is leaving tonight and i will no longer be spending all of my non-working hours feeding it chips lol
<
azonenberg>
Which means back to ngscopeclient manual writing
bvernoux1 has joined #scopehal
bvernoux has quit [Ping timeout: 250 seconds]
bvernoux1 is now known as bvernoux
<
_whitenotifier-9>
[scopehal-docs] azonenberg c6a9126 - Added intro "terminology" section
bvernoux1 has joined #scopehal
bvernoux has quit [Ping timeout: 268 seconds]
<
d1b2>
<louis> azonenberg: do we have any way atm to feed a scalar value in to a PSU in the filter graph?
<
d1b2>
<louis> for the UX of that, would we prefer inputs to the power supply filter graph node, or a seperate "set PSU" filter block?
<
d1b2>
<louis> if the former, we probably have an setting under advanced for the psu that is like "[danger!] enable filter graph inputs"
<
d1b2>
<louis> that might make for weird circular graphs though, so maybe the "set PSU" filter is cleaner
<
d1b2>
<louis> A related change is, I would like to move forward with unifying statistics and filters... how do we want to go about the migration?
<
d1b2>
<louis> the actual change is easy; the question is what to do about glscope's use of the statistic construct
<
azonenberg>
@louis: there is an open feature wishlist for feeding values into the psu
<
azonenberg>
i dont think i filed a ticket
<
azonenberg>
look at how loads do it, for reference
<
azonenberg>
basically, when there is no filter graph input it just behaves like normal
<
azonenberg>
it's safe until you connect something there
<
azonenberg>
the intent is to allow this for most scalar control knobs on most instruments
<
azonenberg>
i just havent coded it up yet
<
azonenberg>
loads were the test case for this as it's what i needed that day :p
<
azonenberg>
it should not be a separate "set psu" block
<
d1b2>
<louis> sounds good. I will bang that out
<
d1b2>
<louis> thoughts on the statistic unification?
<
d1b2>
<louis> do we have an ETA on session support in ng?