azonenberg changed the topic of #scopehal to: libscopehal, libscopeprotocols, and glscopeclient development and testing |,, | Logs:
electronic_eel has quit [Ping timeout: 260 seconds]
electronic_eel_ has joined #scopehal
Degi has quit [Ping timeout: 272 seconds]
Degi has joined #scopehal
Bird|otherbox has quit [Read error: Connection reset by peer]
Bird|otherbox has joined #scopehal
electronic_eel_ has quit [Ping timeout: 240 seconds]
electronic_eel has joined #scopehal
bvernoux has joined #scopehal
juli964 has joined #scopehal
_whitelogger has joined #scopehal
electronic_eel has quit [*.net *.split]
Degi has quit [*.net *.split]
electronic_eel has joined #scopehal
Degi has joined #scopehal
<azonenberg> Hey everyone, so i'm experimenting with cleaning up the multi-repo setup a bit
<azonenberg> Step one is merging scopehal-cmake into scopehal-apps. So scopehal-apps will contain submodules for scopehal + scopehal-docs
<azonenberg> and will become the new top level repo for the project ,scopehal-cmake will be kept around with a README pointing to scopehal-apps but will no longer be active
<azonenberg> Here goes nothing
<_whitenotifier-b> [scopehal-apps] azonenberg closed issue #14: Add UI for configuring segmented capture -
<_whitenotifier-b> [scopehal-apps] azonenberg pushed 124 commits to master [+222/-201/±222]
<_whitenotifier-b> [scopehal-apps] azonenberg b39e9ba - Initial commit
<_whitenotifier-b> [scopehal-apps] azonenberg a9ee811 - Initial import of submodules. No actual build system yet.
<_whitenotifier-b> [scopehal-apps] azonenberg 1dd1859 - Added CMakeLists. Updated to latest submodules.
<_whitenotifier-b> [scopehal-apps] ... and 121 more commits.
<_whitenotifier-b> [scopehal-apps] azonenberg commented on issue #14: Add UI for configuring segmented capture -
<_whitenotifier-b> [scopehal-apps] azonenberg reopened issue #14: Add UI for configuring segmented capture -
<azonenberg> Well that's just great, "fixes #foo" commits will close the wrong issues when merging repos
<azonenberg> But that seemed to work
<azonenberg> Time for a bit more clenaup now
<_whitenotifier-b> [scopehal-apps] tdaede opened issue #139: build instructions for ffts need to produce a shared library -
<_whitenotifier-b> [scopehal-apps] tdaede opened issue #140: cmake doesn't check for presence of yaml-cpp -
<_whitenotifier-b> [scopehal-apps] azonenberg opened issue #141: Add cpack support -
<_whitenotifier-b> [scopehal-apps] azonenberg opened issue #142: Proper cmake install support -
<_whitenotifier-b> [scopehal-apps] bvernoux opened issue #143: Change .gitmodules url in order to allow clone from anonymous user -
<_whitenotifier-b> [scopehal-cmake] azonenberg pushed 1 commit to master [+0/-0/±1]
<_whitenotifier-b> [scopehal-cmake] azonenberg 1d5a0b0 - Updated README for new top level repo
<_whitenotifier-b> [scopehal-cmake] azonenberg pushed 1 commit to master [+0/-0/±1]
<_whitenotifier-b> [scopehal-cmake] azonenberg 2a8ab3d - Updated README with correct URL
<_whitenotifier-b> [scopehal-apps] azonenberg pushed 1 commit to master [+0/-0/±1]
<_whitenotifier-b> [scopehal-apps] azonenberg 852df1b - Updated README with new build directions
<_whitenotifier-b> [scopehal-docs] azonenberg pushed 1 commit to master [+0/-0/±1]
<_whitenotifier-b> [scopehal-docs] azonenberg 0d09384 - Updated "getting started" with scopehal-apps as new top level repo
<_whitenotifier-b> [scopehal-apps] azonenberg pushed 1 commit to master [+0/-0/±1]
<_whitenotifier-b> [scopehal-apps] azonenberg 4bfb393 - Updated docs
azonenberg changed the topic of #scopehal to: libscopehal, libscopeprotocols, and glscopeclient development and testing |,, | Logs:
<_whitenotifier-b> [scopehal-apps] Th3Fanbus closed pull request #138: Create -
<_whitenotifier-b> [scopehal-apps] Th3Fanbus commented on pull request #138: Create -
<_whitenotifier-b> [scopehal-apps] whitequark opened issue #144: Add ffts as a submodule -
<miek> btw, what was the reason for going with ffts?
<azonenberg> miek: fftw was GPL or another incompatible license
<azonenberg> i'm open to other suggestions of something that can be linked with proprietary tools
<miek> ah right
<azonenberg> but the intent has always been to permit scopehal to plug into vendor scope firmware etc
<azonenberg> i.e. i want to allow for tek to use a scopehal protocol decode
<azonenberg> Which means we can't use anything copyleft in the core
<_whitenotifier-b> [starshipraider] azonenberg pushed 1 commit to master [+0/-0/±3]
<_whitenotifier-b> [starshipraider] azonenberg 06af5d1 - Finished initial length matching of last DQ group
katharina has joined #scopehal
<katharina> welp, I contracted and survived Covid19
<katharina> azonenberg: did somebody else pick up the GUI issues that were assigned to me, or are they still open?
<azonenberg> katharina: ... lovely
<azonenberg> that explains why you disappeared for a while
<azonenberg> Doing OK now?
<azonenberg> AFAIK nobody's touched the issues assigned to you. However, you should probably make a new checkout of the code due to repository reorganization
<katharina> not really, but i got released from the hospital three days ago
<monochroma> D:
<azonenberg> tl;dr scopehal-cmake is dead, scopehal-apps is now the top level repo and imports scopehal and scopehal-docs as submodules
<azonenberg> i may merge them further in the future
<azonenberg> and well i guess that's an improvement over last week?
<katharina> ah i see :)
<katharina> thats good i guess, with the cmake project being dead
<azonenberg> we may eventually merge scopehal with scopehal-apps
<azonenberg> but at least this is a less stupid structure
<katharina> i definitely plan on keeping contributing. we are using the software in our lab now to test it out
<azonenberg> i didnt realize it was possible to merge git repos with full history
<azonenberg> or i would have done it a lot sooner
<katharina> i still cant use my head very well, i tried some basic webdev yesterday but no dice
<azonenberg> issues are however a giant pain to merge because any "fixes foo" comments in commit history will be applied to github issues when you unify the history
<katharina> oh that sucks
<azonenberg> because those commits end up being recreated in the other repo essentially
<azonenberg> so basically i have to go back and undo those issue closures after the flattening
<azonenberg> This is made worse by github having per project namespacing for issues
<azonenberg> vs global IDs like launchpad and some other platforms use
<azonenberg> this also means when you move issues from repo to repo you get a new ID
<azonenberg> since scopehal and scopehal-apps have so many issues unifying those repos would be a much bigger problem
<azonenberg> but at least scopehal-cmake is gone and that was the biggest thing confusing users
<miek> is the merge doing a full history rewrite?
<azonenberg> miek: i'm not quite sure how it works internally
<azonenberg> check scopehal-apps and see all of the references to submodules etc?
<azonenberg> but at least things work now
<azonenberg> katharina: well rest up and continue your UI work when you feel up to it
<azonenberg> i really like the direction you were going in
<miek> cause it may not be so bad to have a script go through and filter those keywords from the commit messages, before pushing to github?
<azonenberg> miek: we'll worry about that if/when we unify the other repos
<azonenberg> for now apps and lib separate isnt too unreasonable
<miek> yeah, fair
<azonenberg> and like i said before i wnat to give it a week or two to shake out any problems from this first flattening
<azonenberg> before i even think about doing anything more
<miek> azonenberg: on that tweet about self coupling, what do you think about this sort of thing - it worries me D:
<Degi> Wth is that
<Degi> Ugh why are vacuum components so pricy... Like the turbopump is half as pricy as the vac chamber
<Degi> Pretty nice that the repos are getting merged :D
<azonenberg> miek: honestly these days i'd say simulate it :p
<azonenberg> how fast is it, what layer is it on (internal/external), what substrate, what thickness?
<azonenberg> these all matter
<azonenberg> miek: if i you want to PM me a gerber of the layer and stackup info, i'll run a sim when i have time
<azonenberg> i may have to crop a bit of it out, but it should give you useful info
<miek> it was just something i saw posted on twitter, it's not mine, only other info i know is it's for DDR3. i've just never seen a design with such wide serpentines like that, feels risky :p
<azonenberg> ah, ok
<katharina> its interesting how smth like covid exhausts you to the core. i have problems understanding some pointer arithmetic right now which was no problem at all a few weeks ago
<katharina> i have a full month worth of sick leave, but I doubt i can rejoin the workforce then from what i heard from the earlier cases here in germany
<monochroma> katharina: :<
<azonenberg> katharina: yeah my wife had a pulmonary embolism a few years ago... When you're not getting enough air, hard to concentrate on much else
m4ssi has joined #scopehal
<katharina> azonenberg: oh god - i hope she is doing fine now?
<azonenberg> Yeah she pretty much recovered fully. We moved literally to the opposite end of the country, a week of nonstop driving
<azonenberg> That, combined with some other risk factors she had from meds/general health, resulted in DVT in one leg
<azonenberg> Which went undiagnosed due to a history of muscle cramps in the same area
<azonenberg> causing similar symptoms
<azonenberg> This thend led to the PE
<katharina> wow :c yea i heard about that
m4ssi has quit [Remote host closed the connection]
<Degi> Hmh, doesn't covid also give an increased risk of that... Kinda worried
bvernoux has quit [Quit: Leaving]
<katharina> Degi: The doctors didnt tell me anything like that, but you never know
<Degi> I mean I've read that on twitter, so not sure how reliable that is...
<katharina> I was on an ICU of an university hospital, and I generally feel that the doctors there took great care of sharing the little knowledge they had
<Degi> Oh nice
<Degi> I wish you the best for healing!
<katharina> i very much hope that my sense of smell will come back
<katharina> thanks
katharina has quit [Quit: Lost terminal]
<azonenberg> monochroma, lain, Degi: FEXT simulation of DQ48, 49, 54 on MAXWELL
<azonenberg> pretty insignificant coupling, less than -40 dB at any frequency i care about
<Degi> Huh, -35 dB to 20 GHz
<azonenberg> Yeah
<Degi> Neat
<azonenberg> So not a problem to worry about
maartenBE has quit [Ping timeout: 265 seconds]
maartenBE has joined #scopehal
juli964 has quit [Quit: Nettalk6 -]