I appreciate everyones work. It's making my job easier.
v/r,
Rich
On Tue, Apr 21, 2015 at 11:50 AM, Johnathan Corgan wrote:
> On Tue, Apr 21, 2015 at 11:19 AM, Richard Bell
> wrote:
>
>> Was the Correlation Estimator block recently added? If so, thank you
>> whoever wrote it. If not, thanks an
On Tue, Apr 21, 2015, at 03:12 PM, Marcus Müller wrote:
> By the way: This currently *is* getting more interesting: Because you
> typically don't want to copy memory needlessly in a
> performance-critical application, it's bad that blocks that wrap some
> kind of accelerator (GPU, FPGA card, DSP co
Doug,
you're welcome!
Yeah, my simple "two buffers back to back" example is a bit on the
simplistic side. Actually, we have multiple implementations on how to
get mem-mappable pages, and how much copies/"abort if someone
accidentially ends up in this memory region" pages we have, and of
course Win
On Tue, Apr 21, 2015 at 11:19 AM, Richard Bell
wrote:
> Was the Correlation Estimator block recently added? If so, thank you
> whoever wrote it. If not, thanks anyway. It seems to be an alternative to
> the infamous Corr_and_Sync block.
>
> I also like the testbench that goes with it in gr-digita
Marcus,
Awesome! I'm working my way through the scheduler slides linked earlier today,
and I get to where it's describing buffers on linux like "attach shmid1 to
first half of shmid2 with shmat, attach shmid1 to second half of shmid2 with
shmat, memory in both halves of shmid2 are mapped to the
Hi Doug,
ok, you asked for this :D
So, GNU Radio's buffers look a lot like real circular buffers to the
blocks using them:
For example, assume your buffer between source block A and sink block B
is large enough to store exactly 1 of your items:
A-->B
Now, A has produced 9000 items, of which B
Thanks for your response, Tom. So basically, the documentation needs to be
updated to better reflect the desired behavior of the block. My interpretation
of the behavior would be something like “The look_ahead value creates a minimum
search window. The peak is first searched within this windo
Was the Correlation Estimator block recently added? If so, thank you
whoever wrote it. If not, thanks anyway. It seems to be an alternative to
the infamous Corr_and_Sync block.
I also like the testbench that goes with it in gr-digital/examples/demod. I
did not know I could use Modulate Vector (or
Would it be possible to dive into this a bit deeper? I'm trying to get more
familiar with the the scheduler and how the buffer is laid out.
So using "tried to allocate 41 items of size 1592. Due to alignment
requirements 512 were allocated" as an example, the scheduler looked at the
requirement
Understood.
Most of my tuits are still all rectilinear as well
On 2015-04-21 10:40, Tom Rondeau wrote:
> On Sun, Apr 19, 2015 at 11:39 AM, Marcus D. Leech wrote:
> On 04/19/2015 11:32 AM, Martin Braun wrote:
> Yeah: Use the QT widgets.
>
> As we keep mentioning, the WX widgets will b
On Sun, Apr 19, 2015 at 11:39 AM, Marcus D. Leech wrote:
> On 04/19/2015 11:32 AM, Martin Braun wrote:
>
>> Yeah: Use the QT widgets.
>>
>> As we keep mentioning, the WX widgets will be going away in the future,
>> and no one wants to maintain them. Of course, if someone has a bug fix
>> for this
On Mon, Apr 20, 2015 at 1:42 PM, marco Ribero
wrote:
> I try to give more details.
> In order to create blocks using the standard way(cmake/make/install) with
> Cuda,I've modified the CMakeList in /lib as shown before. My block is
> created using gr_modtool and the language is c++.
> The fact is
On Mon, Apr 20, 2015 at 12:47 PM, Frank Fu wrote:
> I’ve also been looking for an appropriate fix for peak_detector2. When I
> review this thread and the issue tracker, I’m uncertain how the block is
> supposed to behave. I think most of the developers have looked at the
> documentation in the
On 04/21/2015 09:43 AM, Murray Thomson wrote:
> On 20 April 2015 at 15:13, Philip Balister wrote:
>
>>
>>
>> On 04/19/2015 11:07 AM, Murray Thomson wrote:
>>> Hello,
>>>
>>> I have built the gnuradio-dev-image for an arm machine and I wanted to
>>> share a couple of small issues that I found in t
On Tue, Apr 21, 2015 at 3:21 AM, Marcus Müller
wrote:
> Dear LTP,
>
> your top_block [1] is a msg_accepter, just like every other block in your
> system, and a basic_block. Hence, it has a a post()[3] method, it has a
> message_port_register_in()[4] etc.
>
> You should be able to follow what's d
On 20 April 2015 at 15:13, Philip Balister wrote:
>
>
> On 04/19/2015 11:07 AM, Murray Thomson wrote:
> > Hello,
> >
> > I have built the gnuradio-dev-image for an arm machine and I wanted to
> > share a couple of small issues that I found in the process.
> >
> > - The meta-sdr/conf/bblayers.conf
Hi Trek,
the scheduler and all the core components holding GNU Radio together are
in gnuradio/gnuradio-runtime. The scheduler is mainly composed of the
files starting with tpb (==thread per block), block_executor, and
block/buffer.
There's
http://www.trondeau.com/blog/2013/9/15/explaining-the-gnu
Is there a sample routine, document or youtube video explaining the GNUradio
scheduler? hard to fully understand Gnuradio without it. What are the files in
the Gnuradio that are the core of the scheduler?
thanks,___
Discuss-gnuradio mailing list
Disc
Dear LTP,
your top_block [1] is a msg_accepter, just like every other block in
your system, and a basic_block. Hence, it has a a post()[3] method, it
has a message_port_register_in()[4] etc.
You should be able to follow what's described in the Guided tutorials,
Part 5, section 5. [2] If you haven
19 matches
Mail list logo
