=its.bldrdoc@gnu.org
[discuss-gnuradio-bounces+danderson=its.bldrdoc@gnu.org] on behalf of
Marcus Müller [marcus.muel...@ettus.com]
Sent: Tuesday, April 21, 2015 12:33 PM
To: discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] gr::buffer::allocate_buffer: warning
Hi Doug,
ok, you
-gnuradio] gr::buffer::allocate_buffer: warning
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
12:16 PM
To: discuss-gnuradio@gnu.org
Subject: [Discuss-gnuradio] gr::buffer::allocate_buffer: warning
Hello everyone,
I'm getting the following warnings when running my application, does anyone
know what this means?
gr::buffer::allocate_buffer: warning: tried to allocate
41 items of size
-gnuradio-bounces+danderson=its.bldrdoc@gnu.org] on behalf
of Ali Riaz [ariaz.1...@gmail.com]
*Sent:* Monday, April 20, 2015 12:16 PM
*To:* discuss-gnuradio@gnu.org
*Subject:* [Discuss-gnuradio] gr::buffer::allocate_buffer: warning
Hello everyone,
I'm getting the following warnings when
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
On 20.04.2015 11:16, Ali Riaz wrote:
Hello everyone,
I'm getting the following warnings when running my application, does
anyone know what this means?
gr::buffer::allocate_buffer: warning: tried to allocate
41 items of size 1592. Due to alignment requirements
512 were allocated.
Hello everyone,
I'm getting the following warnings when running my application, does anyone
know what this means?
gr::buffer::allocate_buffer: warning: tried to allocate
41 items of size 1592. Due to alignment requirements
512 were allocated. If this isn't OK, consider padding
your
On Fri, Jul 5, 2013 at 5:01 AM, Manu T S manu.t.s...@gmail.com wrote:
A block that i designed takes a vector of length 408 with numpy.int32
components. Work function just copies input to output. Work function
definition is given below.
Tom,
Yes, it is for my GSoC project. Till now I have prototyped in python
encoder, decoder and construction of LDPC codes from Reed Solomon codes.
The encoder and decoder input sizes vary based on the code block length and
dimension.
I hope to switch gears to C++ soon.
Thanks.
On Sun, Jul 7,
Hi Manu, Tracie,
I wouldn't worry about this for now. I'm assuming this is for your
GSoC project? If so, just keep going and make sure you get the math
right. You'll want to move this into a C++ block eventually,
anyways,
and do further optimizations there. We can worry about this problem
at
A block that i designed takes a vector of length 408 with numpy.int32
components. Work function just copies input to output. Work function
definition is given below.
def work(self, input_items,
11 matches
Mail list logo
