[3pt] graph-prototype: Make more detailed automatic and non-automatic tests #110
Milestone
Comments
RalphSteinhagen
changed the title
RalphSteinhagen
added this to the CALL#4 - OP OpenDigitizer Integration/Deployment milestone
ablepharus
pushed a commit
to ablepharus/gnuradio4
that referenced
this issue
May 13, 2024
* Port of gr-digitizer to GNU Radio 4.0 Make code compile with GR 4.0, latest ROOT and latest Picoscope drivers. Some tests don't pass atm. open issues/improvements to be followed-up later: fair-acc#110 fair-acc#111 fair-acc#112 fair-acc#113 fair-acc#114 fair-acc#115 fair-acc#116 Co-authored-by: Alexander Krimm <[email protected]>
RalphSteinhagen
modified the milestones:
CALL#4 - OP OpenDigitizer Integration/Deployment,
CALL#5 - Security Hardening
RalphSteinhagen
modified the milestones:
CALL#5 - Security Hardening,
CALL#5 - UI/UX Upgrades+Backlog
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current tests for graph prototype are not sufficient to guarantee the QoI for graph prototype.
The aim of this task is two-fold:
This task should be done by somebody that does not know the inner workings of GP
to note: SP estimate is very vague and could easily be expanded to much more.
Needs discussion on prioritisation and what needs to be done explicitly before starting this.
The text was updated successfully, but these errors were encountered: