|
From: | Marcus D. Leech |
Subject: | Re: [Discuss-gnuradio] GRC programming problem--anyone with any bright ideas? (fwd) |
Date: | Sat, 21 Apr 2012 20:28:03 -0400 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111108 Fedora/3.1.16-1.fc14 Thunderbird/3.1.16 |
On 04/21/2012 08:20 PM, Vladimir Dergachev wrote:
The flow-graph writes to 3 FIFOs. I fire off 3 reader threads that read the FIFOs, and only dump data when the other part of the program determines that it's in a "triggered" situation, since I'm both reading and writing, I refer to that as "reflexive".On Fri, 20 Apr 2012, Marcus D. Leech wrote:On 04/20/2012 03:45 PM, Vladimir Dergachev wrote:I actually worked out a different solution, involving reflexive FIFOs seems to work.I am not familiar with those - could you comment in more detail ? Thanks !Vladimir Dergachev
It maintains the existing semantic for the gr_file_sink, and since I already have some "helper" Python code to deal with trigger detection,
it was a natural place to put it. Works just fine. -- Marcus Leech Principal Investigator Shirleys Bay Radio Astronomy Consortium http://www.sbrac.org
[Prev in Thread] | Current Thread | [Next in Thread] |