Ok, makes sense. Thanks for the feedback
R
From: trond...@trondeau.com [mailto:trond...@trondeau.com] On Behalf Of Tom
Rondeau
Sent: Monday, May 11, 2015 6:35 PM
To: Richard Bell
Cc: Merz Ruben, INI-INO-ECO-MXT; GNURadio Discussion List
Subject: Re: [Discuss-gnuradio] Question on control-loop blo
Hi,
iam trying to setup a grc project with 2 TCP sinks server blocks each with own TCP port but both TCP blocks with the same IP. So i want to open 2 different TCP Ports at the same host and same IP. At the other grc project iam trying to setup 2 TCP source client blocks which connect to the
Hi Andy,
oh yes, I don't like that block ;) but I'm happy it's there.
So the problem lies in the way this block is structured, and how GNU
Radio runs:
tcp_sink is just a hier block -- it's nothing but a small wrapper around
the file_descriptor_sink[1]. The cool thing about sockets is that you
ca
Hi all guys,
I have a flowgraph where I have three parallel paths for filtering signal
stored in a file. Here the picture of my flowgraph:
[image: Inline image 1]
I use gnuradio 3.6.5.1. When I run the script it uses only one processor,
and since I have 4 cores, I would like to run every of the
On 05/12/2015 12:25 PM, Nemanja Savic wrote:
Hi all guys,
I have a flowgraph where I have three parallel paths for filtering
signal stored in a file. Here the picture of my flowgraph:
Inline image 1
I use gnuradio 3.6.5.1. When I run the script it uses only one
processor, and since I have 4
What Marcus said; GNU Radio 3.6 with its default scheduler, which is
aptly named thread-per-block scheduler, automatically runs every block
in its own thread, and by default (ie. unless you explicitely specify
affinity) lets the OS handle distribution to CPUs; that's the reason GNU
Radio applicatio
You are probably right, cause that file doesn't even exist. I looked at
default gnuradio-core.conf in conf.d.
I suppose that something like that should be written in gnuradi-core.conf,
but really nothing.
Where can I find which option should be added?
On Tue, May 12, 2015 at 6:33 PM, Marcus D. Lee
@Marcus Mueller: But when I run the shown flowgraph it uses only one core.
On Tue, May 12, 2015 at 6:48 PM, Marcus Müller
wrote:
> What Marcus said; GNU Radio 3.6 with its default scheduler, which is
> aptly named thread-per-block scheduler, automatically runs every block in
> its own thread, a
On 05/12/2015 12:52 PM, Nemanja Savic wrote:
You are probably right, cause that file doesn't even exist. I looked
at default gnuradio-core.conf in conf.d.
I suppose that something like that should be written in
gnuradi-core.conf, but really nothing.
Where can I find which option should be add
You are right, cause I was looking in a process manager and only one core
was 100% busy, but since the middle filter had 37k taps it might be that
the other two were starving a little bit.
BTW, in the shown flograph, I would like to have signal in upper and down
paths synchronized, so I introduced
If that file does not exist, GNU Radio 3.6.5 would definitely use the
thread-per-block scheduler; you can try
export GR_SCHEDULER=TPB
prior to executing your flow graph from the same shell.
In fact, looking at top_block_impl.cc:59 in 3.6.5.1, it seems the
scheduler selection isn't read from a conf
Hi Nemanja,
I took the liberty of changing the subject to reflect the new topic :)
You're right, the low pass filters that the firdes tool produces should
have linear phase, meaning that their impulse response is symmetrical
and they have a constant phase delay of half the filter length.
I don't
12 matches
Mail list logo
