Python code cleanup in v29_cleanup #17
Replies: 3 comments 1 reply
-
|
general question: I'm never quite sure when there's several branches and different states of development what should be grabbed as the "feature complete and I think it's stable but YMMV" type release. I've found using tags as one way to indicate specific release(s) are the ones to use. Or keep a Stable and Dev branch where the tip is always something that we can expect to work (and would report a bug if something doesn't)? Or even just the hash helps in staying in sync while there's a lot going on? I'm only a light Git user so there's probably even better ways I don't know about. Thanks |
Beta Was this translation helpful? Give feedback.
-
|
Yet more new features in v29_cleanup today, version 29.33: |
Beta Was this translation helpful? Give feedback.
-
|
Now using releases! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I've been hard at work on a total cleanup of the python software, which you can find in the v29_cleanup branch.
There's a nice auto generated diagram of the new structure here in the new software/README.md
More detail soon on all the new features included in this branch. But it's so easy to add things now!
There's an XY plot, Reference waveforms, Low pass filter, FFT plot features (peak hold, labels, multi-channel), etc.
Some details in this log post on Hackaday...
https://hackaday.io/project/200773-haasoscope-pro/log/243701-new-features-and-v29cleanup-software
Beta Was this translation helpful? Give feedback.
All reactions