|
From: | Kostis Triantafyllakis |
Subject: | Re: [Discuss-gnuradio] [GSOC17 - Draft proposal] Implement SigMF functionality for GNU Radio |
Date: | Sat, 25 Mar 2017 02:20:39 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 |
Bastian, Ben, Seth, Nathan and Paul, Thank you all for your useful feedback! On 03/24/2017 06:01 PM, Ben Hilburn
wrote:
I was actually referring to normal streams with tags. I should fix that in my proposal. Furthermore, I will examine the case of Tagged Streams in order to be able to safely reject them. Messy was a word I've chosen to describe that the produced code is not so easy to read and understand. Python wrappers were not in my initial intentions, but as long as the timeline permits it I would be interested on implementing them. I think Ben's answer covered the concept I had in my mind. For sure I have to rephrase/clarify this in the proposal. It is true that in my mind I was thinking the proposed SigMF GUI app as an integrated GRC tool, just like filter design. Nevertheless, I totally understand the philosophy behind reusing/extending instead of re-inventing the wheel. I should give a careful look on gr-pyqt and QT sinks though. Maybe I could let the destructor of the block in combination with fseekm handle the finalization of the metafile. The case of segfault is actually a question that needs more attention. I have already started looking at the open issues. Do you think it would be meaningful to move the discussion there, in a dedicated issue? According to the description in the main page, RapidJSON "is self-
|
[Prev in Thread] | Current Thread | [Next in Thread] |