|
From: | Marcus Müller |
Subject: | Re: [Discuss-gnuradio] [SOCIS '17] GRC C++ Output: Week 8 |
Date: | Tue, 19 Sep 2017 10:04:28 -0700 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 |
Hi Federico, so your idea is to use GNU Radio Companion to design blocks that internally has a loopback? That would kind of break the semantics of GRC being a tool for designing GNU Raio flow graphs, but I'd still be open to that idea, if you could explain in which way that would differ from it simply being a unified "control loop" block that only is parameterizable (in which case you wouldn't benefit from the graphical representation of it being multiple blocks with feedback, because it's not what's happening, more confusing than clarifying). So, I don't really think that we can find a sufficiently general approach here that would justify letting users do something that GNU Radio itself can't. I'd much rather fix the scheduler than spend time on emulating a fix by having restricted feedback ability that only allows a very limited set of blocks to work in the feedback branch. What do you think? Best regards, Marcus On 09/19/2017 08:29 AM, Federico
'Larroca' La Rocca wrote:
|
[Prev in Thread] | Current Thread | [Next in Thread] |