European GNU Radio Days/2025: Difference between revisions
(→Topics: CI infra) |
|||
Line 112: | Line 112: | ||
: Intermediate to Expert | : Intermediate to Expert | ||
; Scope | ; Scope | ||
: 0.5 | : 1h to 0.5 days | ||
=== Description === | === Description === |
Revision as of 08:02, 22 May 2025
The EU GR days 2025 are taking place in Lyon, July 16–18 (incl.)
Invitation
Dear GNU Radio Community, After the previous years' European GNU Radio Days, and following popular demand, we announce a lighter version for 2025 that will take place July 16-18 in Lyon, France, in Inria/INSA Lyon's CITI laboratory. This time, to reduce the organization load while still providing a venue to meet and chat around GNU Radio in Europe, there won't be dedicated tutorial and presentation talk tracks. The goal is to get together in a room to develop/design, on/with GNU Radio, brainstorming together on possible features and improvements. It is also an opportunity for those interested to visit and start playing with the SLICES/CorteXlab SDR testbed that we have in the lab, for reproducible and remote radio experiments. Beginners are, of course, welcome for those who want to work on their own project, on the wiki's tutorials,... in an stimulating environment with other GNU Radio enthusiasts. As mentioned above, this will take place in France, in the Doua Campus of Lyon's metropolitan area: 6 avenue des Arts, 69100 Villeurbanne, France. It's easily accessible by public transport from the city center (mostly tram T1 and T4) Registration will be free as this is an informal meeting, but please tell us if you plan to come so that we can book the right number of rooms. See you in Lyon, -- Cyrille MORIN Ingénieur SED Équipe MARACAS
Topics
As announced, the organizers will not try to set up a talk track or something; it's a hackathon thing, and everyone is encouraged to coordinate topics with others. Thus, let's collect topics here:
Topic Template
- Champion
- Sarah D. Topicbringer
- Level
- Intermediate (or entry-level, or expert)
- Scope
- 0.5 days
Description
Let's talk about topic, which happens a lot in turboencabulators.
Desired Outcome
Code to turboencabulate to effectively prevent sinusoidal deplanaration.
Q&A
Will we talk about longitudinal error amplification codes? ~Carl
- not my area of expertise, but if you want to, that'd be cool! ~Sarah
- Sure, I'll bring a 20 min slideset! ~Carl
Managing Latency
- Champion
- Marcus Müller (might try to convince Derek to come)
- Level
- Expert to Intermediate
- Scope
- 1.0 to 1.5 days
Description
There's a transmit-token based approach to managing latency that Derek together with Matt designed a few years back.
It would be nice to integrate it into GNU Radio, such that it becomes universally available.
A first step might be something like a message listener in gr::block on the system port, which can be "programmed" to ensure nitems_written(x) <= last_value_received + max_nr_of_samples_in_flight
. This warrants discussion.
Desired outcome
Prototype, and a champion to drive the change.
Q&A
None yet.
The GNU Radio 3 runtime locking clustershamble
- Champion
- Marcus Müller
- Level
- Expert++
- Scope
- 1.5+ days
Description
Changes like adding functionality to get one, and exactly one, tag from this input based on this tag filter function passed in, which would mean a large reduction of memcopy & CPU load in tag handling blocks, are blocked.
This is due to locking of buffers, tag structures, the Python GIL and other parts of GNU Radio not being well-designed.
Especially, everything related to block_detail does one large "mega-lock", regardless of whether it's reading or modifying access.
This needs to be overhauled.
Desired outcome
Plan for granular locking that allows multiple concurrent read accesses to tag structures, doesn't conflate tag structure locking with ring buffer locking
Q&A
None yet.
Improving CI infrastructure brainstorm
- Champion
- Marcus Müller + X
- Level
- Intermediate to Expert
- Scope
- 1h to 0.5 days
Description
Currently, we have pretty slow CI running on github actions on free github runners.
How do we approach getting things faster?
Desired outcome
Direction to go
Q&A
None yet.