Monday, March 30, 2026

Potential GSoC Contributor: GNU Radio 4 signal processing server for MaiaSDR Project

Hi everyone,

This is Hamza, a final year bachelor's engineering student from Egypt. I have been interested in GNU Radio since 2025, and have previously contributed to GNU Radio through Google Summer of Code 2026.

I have taken my time to draft this proposal discussing a possible design for building a GR4 server for the maia-wasm client. Please let me know your thoughts — any feedback is much appreciated.

Check it out here: https://drive.google.com/file/d/1jcgWEr7wwUagQwuczW42UjEXnSgE4WGi/view?

Best regards,
Hamza Hassan

Re: Feedback on GSoC Proposal Submission: GRC Sub-flowgraphs and Minimap Navigation

Hi,

I have updated the proposal by Adding another feature called as Runtime Perfomance Overlay. This feature would colormap the GRC blocks based on the blocks execution delay. It acts like a heatmap in the node graph this becomes useful to people who needs to identify where exactly they are having bottlenecks in their flowgraph design and update it accordingly.

Regards,
Suryasaradhi 



On Thu, 26 Mar, 2026, 12:31 pm B Suryasaradhi, <suryasaradhi3@gmail.com> wrote:
Dear GNU Radio Community,

I hope you are doing well.

My name is Suryasaradhi, and I am currently pursuing an MSc in Electronics Design and Technology at the University of Siegen. I am writing to share my GSoC 2026 proposal titled:

"Enhancing GRC: Built-in Sub-flowgraphs and Minimap Navigation"

This proposal focuses on improving the usability and scalability of GNU Radio Companion (GRC), especially for large and complex flowgraphs. The key contributions include:

- A built-in sub-flowgraph system to enable modular design without requiring external Python bindings or recompilation
- A minimap navigation system for intuitive visualization and navigation of large flowgraphs
- Improvements to workflow efficiency, design scalability, and overall user experience

I have already developed working prototypes for both the sub-flowgraph system and the minimap (GTK), and I am currently extending support to Qt. The proposal also includes detailed system design, implementation strategy, and a structured timeline.

I would greatly appreciate your feedback and suggestions to further refine the proposal. I am particularly interested in aligning the design with the current GRC architecture and community expectations.

Please find the detailed proposal attached as a PDF.

Thank you for your time and consideration.

Best regards,
Suryasaradhi
MSc Electronics Design and Technology
University of Siegen

Re: BokehGUI in GNU Radio 4 (GSOC)

Thanks for the feedback this clears up quite a bit

3,1) Ill explicitly state that the library is undecided and try to keep discussion on the core architecture library neutral, i'll add it as a deliverable to be done hopefully by the the first week of gsoc, it'll contain compiling a list of options, testing and final selection of the library.

2) I'll incorporate more testing throughout the timeline instead of keeping all of it to the end

ill try to expand a bit on risks/risk mitigation & prioritization in the proposal
Virus-free.www.avast.com

On Mon, Mar 30, 2026 at 11:46 AM Cyrille Morin <cyrille.morin@inria.fr> wrote:

Hi Ziad,

To give you some feedback, I'll go out of order:

3) I believe deciding on the exact library to use is an important first step, and is part of the work to be done as it requires time to try out the different options. So having that decision as part of the gsoc itself is a good thing. It could even be thought of as a deliverable

1) The discussion of pros and cons is good, but the exact choice might be dependent on the specificities of the chosen library. For instance, ImGUI might be easier to integrate directly into C++ blocks than Bokeh's Python

2) In general, it's good practice to test as you go. Making all the sinks and widgets before starting to test them might leave you with nothing working, or having to rewrite everything if you find systemic bugs in your code or architecture.

Expanding on the topic of risks. It could be good to think about, and detail where you could have some wriggle room to tackle unexpected issues and/or plan B, prioritization in case time runs short.

Cyrille MORIN
Ingénieur SED
Équipe MARACAS


Centre Inria de Lyon

Laboratoire CITI
Campus La Doua - Villeurbanne
6 avenue des Arts
F-69621 Villeurbanne

Le 27/03/2026 à 18:52, Ziad Haithem 202201027 a écrit :
Sorry for the delay in my reply, things took a bit longer than i expected

Thanks for the answers 

I went ahead and looked up some developer tutorials for GR4 and i think i have a good enough of an understanding now to be able to write a good proposal,

Here is the google doc fo my proposal with the technical aspects complete and that's mainly what i would like to get feedback on

Specifically what i would like feedback on is the following
1) My main design choice on the core infrastructure and if my rationalization behind it is sufficient (I detail 3 approaches in my proposal and compare them)
2) I lack quite a bit of experience with QA & documentation and so those parts of the proposal may be a bit lackluster any feedback on that would definitely help 
3) I have essentially pushed back the question of what library for browser plotting will be used (Bokeh, imgui, etc) to being part of the first week of work, as i feel i wont have enough time to do an actual good assessment before the proposal deadline, is that okay or do i need to specify the library which will be used ?

Obviously any feedback on anything else is welcome, I am sure I have so much to learn ! 

Since its a google doc, feedback via comments within the document would be easier than email i think, however whatever is preferable for you is fine


On Wed, Mar 25, 2026 at 5:34 PM Cyrille Morin <cyrille.morin@inria.fr> wrote:

Hi Ziad,

Having a running GR 4.0 with a custom OOT is certainly a good start, well done!

I'm definitely not in the best position to give advice on GR4 code philosophy as I still need to start playing with it before GSoc starts.
But I believe you'll find the best and most up to date info in the gnuradio4 repo itself, including the readmes in the /docs folder, and also the 4.0.0-RC1 tag description which covers a lot of the current state

I mention Bokeh in the project description because it's the dependency we use for the current (GR3) version of the remote monitoring system, so we know it can cover the main use case.
But it is far from perfect so we are open to using an other library providing that same core use case of remote monitoring with plots and interaction with widgets, with the added bonus of not requiring anything installed on the remote computer.
So ImGUI, with its many flavours could be an interesting option with better performance, nice plots... as long as it shows an efficient way for remote operation outside of the local browser.

I hope it helps with some of your questions,

Best

Cyrille MORIN
Ingénieur SED
Équipe MARACAS


Centre Inria de Lyon

Laboratoire CITI
Campus La Doua - Villeurbanne
6 avenue des Arts
F-69621 Villeurbanne

Le 24/03/2026 à 04:40, Ziad Haithem 202201027 a écrit :

Dear GNU Radio Community,

I have decided that my gsoc proposal/project will be on the "BokehGUI in GNU radio 4.0" idea

1. Proof of Concept & Progress

To get comfortable with the GR 4.0 , I've developed a small PoC . It uses a signal generator block into a custom OOT module that publishes data to a socket via ZMQ. A Python script then subscribes to that socket and plots the sine wave in the browser in real-time using Bokeh.

Main goal is to just show i was able to take something generated by GR4 and get it displayed in the browser 

I've also worked through the GR3 beginner and OOT tutorials, and spent time playing with ZMQ/Bokeh to ensure I can handle plotting and the data flow between processes.

2. Seeking Guidance on GR 4.0 

While I'm thrilled I got the PoC running, this is my first time working with a codebase of this scale. My main concern is moving from "making it work" to "making it right." What are some resources that'll help me design and write code that "fits" with the design philosophy behind OOT modules for GR4. I feel like this will be very important for my proposal 

3. Use of bokeh  

I wrote the POC in bokeh and focused on it when experimenting because its what was mentioned in the project description and there are plenty of resources for it. However while researching I found that in European GNU Radio Days in the next generation remote GUI section. "Imgui"  was considered a good candidate to be used for wireless plotting for GNU Radio 4.0. Has the community moved away from this opinion ? is it still present ? Should I write my proposal with only one library in mind or be flexible and have this been decided later on in development ?  

4. Why This Project?

I initially looked for something with a bit more DSP and communications concepts. However this project feels important, and I decided to go with something which would have an impact instead of wasting time thinking of a custom project to propose that had me playing with some of the concepts i was most interested in. 

I am really looking forward to the possibility of contributing to GNU Radio this summer as part of GSOC. Thank you for your time and for any pointers you can provide!

cyberspectrum is best spectrum (I think the code word is for the proposal only but one can never be too safe lol)

Sincerely,

Ziad 
--
Ziad Haithem Fahmy
ID:202201027
 
Communications and Information Engineering Student

Zewail City of Science, Technology and Innovation  

Ahmed Zewail Road, October Gardens, Giza 12578, Egypt

www.zewailcity.edu.eg


0120 205 7175

Whatsapp number - 0109 479 1824



Re: BokehGUI in GNU Radio 4 (GSOC)

Hi Ziad,

To give you some feedback, I'll go out of order:

3) I believe deciding on the exact library to use is an important first step, and is part of the work to be done as it requires time to try out the different options. So having that decision as part of the gsoc itself is a good thing. It could even be thought of as a deliverable

1) The discussion of pros and cons is good, but the exact choice might be dependent on the specificities of the chosen library. For instance, ImGUI might be easier to integrate directly into C++ blocks than Bokeh's Python

2) In general, it's good practice to test as you go. Making all the sinks and widgets before starting to test them might leave you with nothing working, or having to rewrite everything if you find systemic bugs in your code or architecture.

Expanding on the topic of risks. It could be good to think about, and detail where you could have some wriggle room to tackle unexpected issues and/or plan B, prioritization in case time runs short.

Cyrille MORIN
Ingénieur SED
Équipe MARACAS


Centre Inria de Lyon

Laboratoire CITI
Campus La Doua - Villeurbanne
6 avenue des Arts
F-69621 Villeurbanne

Le 27/03/2026 à 18:52, Ziad Haithem 202201027 a écrit :
Sorry for the delay in my reply, things took a bit longer than i expected

Thanks for the answers 

I went ahead and looked up some developer tutorials for GR4 and i think i have a good enough of an understanding now to be able to write a good proposal,

Here is the google doc fo my proposal with the technical aspects complete and that's mainly what i would like to get feedback on

Specifically what i would like feedback on is the following
1) My main design choice on the core infrastructure and if my rationalization behind it is sufficient (I detail 3 approaches in my proposal and compare them)
2) I lack quite a bit of experience with QA & documentation and so those parts of the proposal may be a bit lackluster any feedback on that would definitely help 
3) I have essentially pushed back the question of what library for browser plotting will be used (Bokeh, imgui, etc) to being part of the first week of work, as i feel i wont have enough time to do an actual good assessment before the proposal deadline, is that okay or do i need to specify the library which will be used ?

Obviously any feedback on anything else is welcome, I am sure I have so much to learn ! 

Since its a google doc, feedback via comments within the document would be easier than email i think, however whatever is preferable for you is fine


On Wed, Mar 25, 2026 at 5:34 PM Cyrille Morin <cyrille.morin@inria.fr> wrote:

Hi Ziad,

Having a running GR 4.0 with a custom OOT is certainly a good start, well done!

I'm definitely not in the best position to give advice on GR4 code philosophy as I still need to start playing with it before GSoc starts.
But I believe you'll find the best and most up to date info in the gnuradio4 repo itself, including the readmes in the /docs folder, and also the 4.0.0-RC1 tag description which covers a lot of the current state

I mention Bokeh in the project description because it's the dependency we use for the current (GR3) version of the remote monitoring system, so we know it can cover the main use case.
But it is far from perfect so we are open to using an other library providing that same core use case of remote monitoring with plots and interaction with widgets, with the added bonus of not requiring anything installed on the remote computer.
So ImGUI, with its many flavours could be an interesting option with better performance, nice plots... as long as it shows an efficient way for remote operation outside of the local browser.

I hope it helps with some of your questions,

Best

Cyrille MORIN
Ingénieur SED
Équipe MARACAS


Centre Inria de Lyon

Laboratoire CITI
Campus La Doua - Villeurbanne
6 avenue des Arts
F-69621 Villeurbanne

Le 24/03/2026 à 04:40, Ziad Haithem 202201027 a écrit :

Dear GNU Radio Community,

I have decided that my gsoc proposal/project will be on the "BokehGUI in GNU radio 4.0" idea

1. Proof of Concept & Progress

To get comfortable with the GR 4.0 , I've developed a small PoC . It uses a signal generator block into a custom OOT module that publishes data to a socket via ZMQ. A Python script then subscribes to that socket and plots the sine wave in the browser in real-time using Bokeh.

Main goal is to just show i was able to take something generated by GR4 and get it displayed in the browser 

I've also worked through the GR3 beginner and OOT tutorials, and spent time playing with ZMQ/Bokeh to ensure I can handle plotting and the data flow between processes.

2. Seeking Guidance on GR 4.0 

While I'm thrilled I got the PoC running, this is my first time working with a codebase of this scale. My main concern is moving from "making it work" to "making it right." What are some resources that'll help me design and write code that "fits" with the design philosophy behind OOT modules for GR4. I feel like this will be very important for my proposal 

3. Use of bokeh  

I wrote the POC in bokeh and focused on it when experimenting because its what was mentioned in the project description and there are plenty of resources for it. However while researching I found that in European GNU Radio Days in the next generation remote GUI section. "Imgui"  was considered a good candidate to be used for wireless plotting for GNU Radio 4.0. Has the community moved away from this opinion ? is it still present ? Should I write my proposal with only one library in mind or be flexible and have this been decided later on in development ?  

4. Why This Project?

I initially looked for something with a bit more DSP and communications concepts. However this project feels important, and I decided to go with something which would have an impact instead of wasting time thinking of a custom project to propose that had me playing with some of the concepts i was most interested in. 

I am really looking forward to the possibility of contributing to GNU Radio this summer as part of GSOC. Thank you for your time and for any pointers you can provide!

cyberspectrum is best spectrum (I think the code word is for the proposal only but one can never be too safe lol)

Sincerely,

Ziad 
--
Ziad Haithem Fahmy
ID:202201027
 
Communications and Information Engineering Student

Zewail City of Science, Technology and Innovation  

Ahmed Zewail Road, October Gardens, Giza 12578, Egypt

www.zewailcity.edu.eg


0120 205 7175

Whatsapp number - 0109 479 1824



GSoC26 Proposal: Graphical interoperability between CyberEther and GNU Radio

Hello,
This is Youssef. I have been on Matrix for a while now, but this is my first time posting to the mailing list :)
I'm sharing my GSoC proposal for "Graphical interoperability between CyberEther and GNU Radio".

I know I'm a bit late to the proposal discussion, but I would especially appreciate comments on:
- the feasibility of implementing a custom buffer, similar to `cuda_buffer` in `gr-cuda`, to achieve a minimal dataflow.
- the clarity and realism of the deliverables


Re: GSoC 2026 Proposal - Hardware in the loop CI

Hello Joseph,

I read trough your document.
Overall, it looks good, it appears to have everything required of the proposal document.

A couple of thoughts: 

The proposed integrated tests look good and feel like what we would like to head towards, but being integration tests, they involve a lot of moving parts, so they might require a lot of tweaking and debugging time to work reliably, which might push back the integration into the CI pipeline.

I've never used Labgrid so I don't know much about what it can or cannot help with. But it does sound in your proposal to perform many task already done by the platform's systems (booking, health check, ...) You might want to detail where specifically Labgrid would offer new and required capabilities

Best

Cyrille MORIN
Ingénieur SED
Équipe MARACAS


Centre Inria de Lyon

Laboratoire CITI
Campus La Doua - Villeurbanne
6 avenue des Arts
F-69621 Villeurbanne

Le 28/03/2026 à 14:49, Joseph George a écrit :

Hi Cyrille,

I have completed the first draft of my GSoC 2026 proposal for the "Hardware in the Loop CI" project.

Draft : Hardware in the Loop CI

A huge thank you to Larry and Philip for the insights. I have explicitly integrated the LBNL Node Health Check paradigm to isolate hardware failures from software regressions, and I've adopted Labgrid as the core hardware orchestration layer to manage the CorteXlab USRPs.

I would greatly appreciate any feedback from the community,

Thanks for your time and guidance!

Best, Joseph George


On Thu, 26 Mar 2026 at 22:23, Cyrille Morin <cyrille.morin@inria.fr> wrote:

Hi Joseph,

Welcome!

Feel free to share your draft here on the mailing list, for feedback by members of the community, that's the right place

I don't have a specific format for the tests scenarios, choose what you think is best/more readable/most relevant.
But do look at the GSoC Student info on the wiki if you haven't already: https://wiki.gnuradio.org/index.php?title=GSoCStudentInfo

Cyrille MORIN
Le 26/03/2026 à 15:56, Joseph George a écrit :
Hi Cyrille, 
I'm Joseph, an ECE student and the Chair of the IEEE Signal Processing Society at my college. I'm putting together a GSoC proposal for the "Hardware in the loop CI" project and wanted to quickly say hello. 

I have a strong background in bridging DSP theory with physical hardware. I recently placed 7th globally in the ICASSP 2026 ALS challenge by building domain-driven acoustic biomarker pipelines, and I regularly build hardware projects (like ESP32 navigation systems using Kalman filtering for sensor fusion). I'd love to help bring GNU Radio's CI tests out of software only simulation and onto the physical CorteXlab hardware. 

I am drafting my 12-week timeline right now. Is there a specific format you prefer for the test scenarios, or a good place to drop a link to my draft for a quick sanity check before Tuesday's deadline?

Re:

Hi Sayantan,

It took me a while, but I read through your document.
It looks good, I see you've integrated the feedback given to you earlier :)

The proposed approach is leaning more towards "unit" block tests that full integration flowgraph, but that does reduce risks of not having anything working.

I don't see much to point out, except maybe the fact that we might not want to have fully automatic pipeline trigger on every PR since there might be quite a lot of them and we might not want to fill up the testbed's time. But that's mostly something to define with the maintenance team.

Best

Cyrille MORIN
Ingénieur SED
Équipe MARACAS


Centre Inria de Lyon

Laboratoire CITI
Campus La Doua - Villeurbanne
6 avenue des Arts
F-69621 Villeurbanne

Le 27/03/2026 à 05:59, Sayantan Maity a écrit :

Hi Cyrille,

I hope you're doing well.

I have completed a draft of my GSoC proposal titled "Hardware-in-the-Loop Continuous Integration for GNU Radio using CorteXlab." I have attached the proposal as a PDF for your review.

I would really appreciate it if you could take some time to review it and share your feedback, especially regarding the overall approach, feasibility, and any areas for improvement.

Thank you for your time and guidance.

Best regards,
Sayantan Maity
B.S. Electronics Systems, IIT Madras