<_whitenotifier-4>
[scopehal] azonenberg 0adcd7f - Added more doxygen comments
<d1b2>
<azonenberg> @fredzo_72653 can you also add a doc section in the manual under transports for the new HID transport? i didn't see that in your PR, only the driver
<d1b2>
<azonenberg> Doing some small code cleanup as i merge the HID PR
<d1b2>
<azonenberg> What are your thoughts on making ReadUint functions take a const vector& rather than a vector*? i think it'd make the code more readable
<d1b2>
<azonenberg> just a suggestion. i'll let you make the change if you think it's right, just let me get this cleanup done first so we don't step on each other
<_whitenotifier-4>
[scopehal-apps] fredzo 0fca62a - Moved to hid scopehal version + added hidapi to windows build.
<_whitenotifier-4>
[scopehal-apps] fredzo 271864b - Revert "Moved to hid scopehal version + added hidapi to windows build." This reverts commit 0fca62a1d48b1fd7903e4a632f7a600bfeadeb84.
<_whitenotifier-4>
[scopehal-apps] fredzo b45f3aa - Moved to hid version of scopehal
<_whitenotifier-4>
[scopehal-apps] ... and 25 more commits.
<d1b2>
<vipqualitypost> Did something change with macos build process? I did a clean build today and it was really really giving me trouble, but it could be that my build environment also somehow got messed up a bit.
<d1b2>
<vipqualitypost> Linking libomp wasn't possible without a lot of hand holding and modifications to the cmakelists
<d1b2>
<vipqualitypost> this is neat, didn't realize you can do spectrograms like this
<d1b2>
<azonenberg> there's now a dependency on hidapi
<d1b2>
<azonenberg> possible you dont have the headers for that installed?
<d1b2>
<azonenberg> but i didnt change anything to macos build in general or openmp
<d1b2>
<azonenberg> nor did i knowingly merge anything in a PR that would do s
<d1b2>
<azonenberg> do so*
<d1b2>
<azonenberg> that's not a spectrogram. a spectrogram is a 2D plot of frequency+intensity vs time
<d1b2>
<azonenberg> that's just a 1D spectrum view of amplitude vs frequency, like you'd get with a FFT
<d1b2>
<azonenberg> but with an optical input
<d1b2>
<azonenberg> the equivalent spectrogram would be with wavelength in the Y axis, time in the X, and showing basically a waterfall of the spectrometer
<d1b2>
<azonenberg> Which is not something we support as i havent yet found a reason to
<d1b2>
<vipqualitypost> sorry, yes, I think the better word would have been spectrograph 😄
<d1b2>
<vipqualitypost> libhidapi did give me a bit of trouble, it kept picking up the x86_64 version and I couldn't figure out how to change what version it picks up, so I just uninstalled it, ha.
<d1b2>
<vipqualitypost> must have been me tinkering with something else and mangling my environment