No comment on the patch, but in general, it helps us a lot if you do
this via github & pull request.
M
On 24.09.2014 12:21, Zhe Feng wrote:
Dear all,
I checked the keep_m_in_n block and found a possible bug in it. In the
work function, the code wrote:
consume_each(d_n);
return d_m;
which I
Dear all,
I checked the keep_m_in_n block and found a possible bug in it. In the work
function, the code wrote:
consume_each(d_n);
return d_m;
which I think it should be
consume_each(blks*d_n);
return blks*d_m.
while blks=std::min(noutput_items/d_m, ninput_items[0]/d_n).
Since both m and n of
On 24.09.2014 09:52, Michael Berman wrote:
Sagar,
Taking a look in the git history for the v3.3.0 tag, this was authored
on June 2, 2010. Your best bet would probably be to install an OS
version that corresponds to this date. Ubuntu 10.04 would probably be
my suggestion.
Also (and sorry to b
On Wed, Sep 17, 2014 at 2:06 PM, Sam mite wrote:
> Hi, I am trying the CMA equalizer of gnuradio and for understanding I am
> studying the reference paper mentioned in the doc as well. I have a
> question after going through the code- Why the real and imag part of the
> error signals are being c
The documentation for qam_demod is the documentation for qam_mod.
/\/\ark.
--
Aim for brevity while avoiding jargon.
~ Edsger Dijkstra
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
modulation_utils is a registry for modulations implemented in other
modules. A grep in the same directory as modulation_utils turns up
bpsk.py, cpm.py, gfsk.py, gmsk.py, psk.py, qam.py, qpsk.py.
On 09/24/2014 04:26 PM, Medhat Hamdy wrote:
Hi all,
I am really confused. I opened the modula
Sagar,
Taking a look in the git history for the v3.3.0 tag, this was authored on
June 2, 2010. Your best bet would probably be to install an OS version
that corresponds to this date. Ubuntu 10.04 would probably be my
suggestion.
As far as documentation, I know there have been a lot of updates r
Hello all,
I have a gr module that was built using GNURadio 3.3.0. I have to run it
and experiment with it. I am facing the following problems.
*PS : GNURadio 3.3.0 had a different architecture, which was gnuradio-core,
but now with the latest versions, the architecture of GNURadio is changed
and
Hi all,
I am really confused. I opened the modulation_utils and I cannot figure out
how the modulation part is performed, it is just an empty curly braces.
_type_1_modulators = {}
def type_1_mods():
return _type_1_modulators
def add_type_1_mod(name, mod_class):
_type_1_modulator
On 09/24/2014 04:14 PM, Jean-Baptiste Truffault wrote:
Sorry for the time, I had some trouble with the 3.7.3 install, finally I
installed the 3.7.5 thanks to the script
http://www.sbrac.org/files/build-gnuradio.
First, I recorded a DSRC signal thanks to Gnu Radio and my USRP N210
(with a CBX dau
On 24.09.2014 01:47, ruben.m...@swisscom.com wrote:
Hey,
Thanks a lot!
I’m away from hardware until Tuesday. Will test it then.
I still think that for your application, you don't actually need it. A
test would still be appreciated.
M
Ruben
*From:*trond...@trondeau.com [mailto:trond...@
Hi Achilleas,
Can you issue a pull request for this against gnuradio/gnuradio.git? That
will help us track it better for merging.
Thanks!
Tom
On Wed, Sep 24, 2014 at 9:08 AM, Achilleas Anastasopoulos wrote:
> Hi all,
>
> I have made several updates to the gr-trellis examples (adding options
How is that Makefile executed? GRC generates the top_block.py then executes
it. The Makefile would have to edit it before execution right?
Ryan
On Wed, Sep 24, 2014 at 10:25 AM, wrote:
> Just as a follow-up, I have a flow-graph, simple_ra, that originates in
> GRC, but the Makefile that I use e
Just as a follow-up, I have a flow-graph, simple_ra, that originates in
GRC, but the Makefile that I use edits the generated code post-facto,
in an automated way, so that it's reproducible. My use-case is
trivial--I'm just editing-in a version number into a title string, but
the
general ap
Hey All,
Thanks for the leads and advice.
Ryan
> Vanush,
>
> GRC will overwrite any changes you make to the generated Python file, so
> you would want to do any custom programming outside that file. The
> '__main__' code is only hit if you execute the file as the top level
> program.
>
> - Jeff
>
Hi all,
I have made several updates to the gr-trellis examples (adding options etc).
They are here:
https://github.com/anastas/gnuradio.git
under branch "trelllisupdates"
I hope they'll get merged to the master branch soon.
Please let me know if there are any issues to be resolved.
best,
Achile
Hey,
Thanks a lot!
I’m away from hardware until Tuesday. Will test it then.
Ruben
From: trond...@trondeau.com [mailto:trond...@trondeau.com] On Behalf Of Tom
Rondeau
Sent: Tuesday, September 23, 2014 7:55 PM
To: Martin Braun
Cc: Merz Ruben, INI-INO-ECO-MXT; GNURadio Discussion List
Subject: Re: [
I have following flowgraph:
usrp_source--->>probe_mag_squared_block>block2--->block3
What I want to do is that I want to bypass the "work" function of block2
when the threshold level of probe_mag_squared reaches. I do not want to
stop(), lock(), disconnect the flow graph. Is this possible u
18 matches
Mail list logo
