azonenberg changed the topic of #scopehal to: ngscopeclient, libscopehal, and libscopeprotocols development and testing | https://github.com/ngscopeclient/scopehal-apps | Logs: https://libera.irclog.whitequark.org/scopehal
Degi_ has joined #scopehal
Degi has quit [Ping timeout: 260 seconds]
Degi_ is now known as Degi
juri_ has quit [Ping timeout: 256 seconds]
juri_ has joined #scopehal
juri_ has quit [Ping timeout: 245 seconds]
juri_ has joined #scopehal
juri_ has quit [Ping timeout: 264 seconds]
juri_ has joined #scopehal
juri_ has quit [Ping timeout: 245 seconds]
juri_ has joined #scopehal
juri_ has quit [Ping timeout: 255 seconds]
juri_ has joined #scopehal
juri_ has quit [Ping timeout: 240 seconds]
juri_ has joined #scopehal
juri_ has quit [Ping timeout: 268 seconds]
juri_ has joined #scopehal
juri__ has joined #scopehal
juri_ has quit [Ping timeout: 276 seconds]
juri__ has quit [Read error: Connection reset by peer]
juri_ has joined #scopehal
<_whitenotifier-3> [scopehal] azonenberg opened issue #835: ASEQ: don't output any data on absolute irradiance stream if the unit doesn't have absolute cal data - https://github.com/ngscopeclient/scopehal/issues/835
juri_ has quit [Ping timeout: 255 seconds]
juri_ has joined #scopehal
juri_ has quit [Ping timeout: 268 seconds]
juri_ has joined #scopehal
juri_ has quit [Read error: Connection reset by peer]
juri_ has joined #scopehal
juri_ has quit [Ping timeout: 252 seconds]
juri_ has joined #scopehal
juri_ has quit [Read error: Connection reset by peer]
juri_ has joined #scopehal
juri_ has quit [Read error: Connection reset by peer]
juri_ has joined #scopehal
juri__ has joined #scopehal
juri_ has quit [Ping timeout: 264 seconds]
juri__ has quit [Ping timeout: 264 seconds]
juri_ has joined #scopehal
juri_ has quit [Ping timeout: 256 seconds]
juri_ has joined #scopehal
juri_ has quit [Read error: Connection reset by peer]
juri_ has joined #scopehal
juri_ has quit [Read error: Connection reset by peer]
juri_ has joined #scopehal
bvernoux has joined #scopehal
bvernoux has quit [Client Quit]
juri_ has quit [Ping timeout: 255 seconds]
juri_ has joined #scopehal
juri_ has quit [Ping timeout: 260 seconds]
juri_ has joined #scopehal
<d1b2> <azonenberg> Anyone have thoughts on this 8b/10b decode icon?
<d1b2> <azonenberg> oops wrong draft
<d1b2> <azonenberg> this one
juri_ has quit [Ping timeout: 268 seconds]
<d1b2> <azonenberg> Also considering two possible styles for 64/66 decoding
<d1b2> <azonenberg> I like the second version better
juri_ has joined #scopehal
juri_ has quit [Ping timeout: 256 seconds]
juri_ has joined #scopehal
juri_ has quit [Ping timeout: 255 seconds]
juri_ has joined #scopehal
juri_ has quit [Ping timeout: 268 seconds]
juri_ has joined #scopehal
juri_ has quit [Ping timeout: 256 seconds]
juri_ has joined #scopehal
juri_ has quit [Ping timeout: 252 seconds]
balrog has quit [Quit: Bye]
balrog has joined #scopehal
juri_ has joined #scopehal
juri_ has quit [Ping timeout: 260 seconds]
juri_ has joined #scopehal
juri_ has quit [Ping timeout: 246 seconds]
juri_ has joined #scopehal
juri_ has quit [Read error: Connection reset by peer]
juri_ has joined #scopehal
<d1b2> <johnsel> I'm not a huge fan
<d1b2> <johnsel> The ratio is a little off
<d1b2> <johnsel> as well as leading bits for one and trailing bits for the other
<d1b2> <johnsel> it's a little visually confusing
juri__ has joined #scopehal
<d1b2> <johnsel> I understand you can't put 64 lines marking individual bits but the fact one has it and the other doesn't is also a little weird
<d1b2> <johnsel> you might fill the bar with the actual amount of bits instead
<d1b2> <johnsel> so in text "10B" and "8B" is what I mean
juri_ has quit [Ping timeout: 264 seconds]
<d1b2> <azonenberg> So we might center 8b10b or something
<d1b2> <azonenberg> the right justification ws intended to highlight that 64/66 has the two header bits and then the 64 scrambled data bits
<d1b2> <azonenberg> while 8b10b is a 8:10 codebook code
<d1b2> <azonenberg> this might not be as relevant to people who arent familiar with the nitty gritty of the line codes :p
juri__ has quit [Read error: Connection reset by peer]
<d1b2> <azonenberg> these icons are going to be small, i don't think text is going to work well unless it's enormous
<d1b2> <johnsel> I understand that but it's still confusing to look at because it seems as if there are 2x10% chunks instead of 2 single bits
<d1b2> <johnsel> I disagree, you have zoom on the graph editor anyway
<d1b2> <azonenberg> I'll sit on it a bit. I expect a lot of these icons are going to get redone a bit
<d1b2> <azonenberg> my current thoguht is to get first draft icons for every filter block done, then make a list of complaints
<d1b2> <azonenberg> then go back and revamp the ones we don't like
<d1b2> <johnsel> I mean either is good enough for sure compared to having nothing
<d1b2> <azonenberg> I don't want to get buried in details on one or two filters and not get to the others
<d1b2> <azonenberg> Yeah exactly
<d1b2> <azonenberg> But i certainly want a list of ones where I can say "this one could use work" and these are on that list
<d1b2> <johnsel> Agreed
<d1b2> <azonenberg> other recent additions not yet merged: memory (the "freeze" imagery i'm still on the fence about)
<d1b2> <azonenberg> CSV import and export
<d1b2> <azonenberg> burst width
<d1b2> <azonenberg> FWHM
<d1b2> <azonenberg> histogram
<d1b2> <azonenberg> envelope
<d1b2> <azonenberg> we have a concept for FFT that i really didnt like and probably won't even merge, its just a spectrum with two peaks, but i'm not sure what i would change yet
<d1b2> <azonenberg> @johnsel any feedback on these? (or any of the ones we've already upstreamed?)
<d1b2> <azonenberg> there's one for uart protocol decode but i cant find the pic in scrollback, its just a 9-pin d-sub connector
<d1b2> <azonenberg> (in more true color, gray and gold)
<d1b2> <azonenberg> ethernet is in progress
<d1b2> <johnsel> I like these so far
<d1b2> <johnsel> They're pretty clear to me
juri_ has joined #scopehal
<d1b2> <azonenberg> only another hundred-some to go lol
<d1b2> <azonenberg> And i've done the ones with the most obvious graphical depictions first
<d1b2> <azonenberg> it'll get trickier when we start moving on to protocols especially without using trademarked logos
<d1b2> <azonenberg> e.g. for usb i'll have to use a usb connector most likely not the trident
<d1b2> <azonenberg> and when we get to stuff like "PCIE gen 2 TLP layer" forget it lol
<d1b2> <azonenberg> i'll probably have one generic pcie card icon for the entire pcie protocol stack i just reuse for every layer, possibly with a text overlay for the layer
<d1b2> <johnsel> that makes sense
juri_ has quit [Ping timeout: 256 seconds]
juri__ has joined #scopehal
<d1b2> <azonenberg> anyway i think it adds a lot to the graph editor and is definitely worth continuing with
<d1b2> <azonenberg> makes graphs both easier to follow and a lot more professional looking
juri__ has quit [Ping timeout: 256 seconds]
juri_ has joined #scopehal
juri_ has quit [Ping timeout: 256 seconds]
juri_ has joined #scopehal
juri_ has quit [Read error: Connection reset by peer]
juri_ has joined #scopehal
juri_ has quit [Read error: Connection reset by peer]
juri_ has joined #scopehal
juri_ has quit [Ping timeout: 276 seconds]
juri_ has joined #scopehal
<_whitenotifier-3> [scopehal-apps] hgl10 starred scopehal-apps - https://github.com/hgl10