I am trying to create an io signature with multiple inputs greater than 3
using makev. in order to do this, I learned to do it according to the code
below. My issue is that I need to derive the input sizes from the input
arguments but I don't know how I would do that. I imagine using a separate
Just following up to help others in the future.
Over the years, when I try to get gnuradio on a new platform, I’ve always
wanted a “just tell me what worked”, so I can start there.
3.7.10 works well with QT blocks on OS X Sierra on MacBook Pro 15 (December,
2016)
Using Python 2.7.10
Using Xcode
Thoughts?
On Mon, Dec 5, 2016 at 4:56 PM, Dave NotTelling wrote:
> Marcus & Martin:
>
> I tried the dict_keys() method of checking, but even that can fail.
> Here is an example:
>
> [code]
>
> import pmt
>
> d = pmt.make_dict()
> d = pmt.dict_add(d, pmt.intern('a'), pmt.intern('a'))
> d = p
Adding a maximum length for a vector sink will make it easier to use for
'realtime' QA code. Minor change required.
Eugene Grayver, Ph.D.
Aerospace Corp., Sr. Eng. Spec.
Tel: 310.336.1274
___
Discuss-
Hi Bastian,
back then I tried to published it under GPL but the legal department of
my institution did not like it.. Perhaps now, after 2 years I
can give a try again :)
Anw, if some of you need more info on this I will be glad to help.
Cheers!
On 12/06/2016 01:47 PM, Bastian Bloess
Dear Johannes,
Very interesting work! I'll read it through. Many thanks.
BR, Hanwen
-- Forwarded message --
From: Johannes Demel
Date: 2016-12-07 14:17 GMT+01:00
Subject: Re: [Discuss-gnuradio] Decoding speed of the FECs in GR
To: "discuss-gnuradio@gnu.org"
Hey Hanwen,
in m
Hi Eugene,
The sensor returns a time_t value, which is based on the Unix epoch. Your
application can translate that value however it needs. You can also get
the GPRMC NMEA string by calling USRP.get_mboard_sensor('gps_gprmc') and
get the raw value from that if necessary.
Regards,
Michael
On Tu
On Wed, 2016-12-07 at 12:10 -0500, Andy Walls wrote:
> > From GDB I can see
> >
> >
> > d_filtnum = 0
> > count = -67108696
> > d_out_idx = 0
> >
>
> This is a garbage-in, garbage-out problem I've seen exactly before with
> other blocks and the PFB clock sync block.
>
> 1. Check to make sure
Typo in there count can never be less than 0.
The other thing that I think makes sense is that we might need some history
to scroll back to, but I don't think it's necessarily bounded how much
history... Are you using an upstream block that provides time_est tags?
Also, what parameters are you
> From:
> devin kelly
> Subject:
> Re: [Discuss-gnuradio] Segfault
> with
> volk_32fc_32f_dot_prod_32fc_a_avx
> Date:
> Wed, 7 Dec 2016 10:18:32 -0500
>
> ___
Some sanity appears!
>From what I can tell, count is keeping track of how many input samples have
been processed, which can never be 0. My proposed fix would be to clamp
count to 0 somewhere after line 462, but it would be nice for someone to
confirm this makes sense.
Nathan
On Wed, Dec 7, 2016
I rebuilt GR with CMAKE_BUILD_TYPE=Debug. The al and ar vairables got
optimized out, what's the compiler option to prevent that?
I think I've found part of the problem:
Looking here (on frame 2 in gdb):
https://github.com/gnuradio/gnuradio/blob/master/gr-digital/lib/pfb_clock_sync_ccf_impl.cc#L
Hey Hanwen,
in my master thesis [0] I did some benchmarks for polar codes and there
should be one benchmark for LDPC codes. All benchmarks use the GNU Radio
implementation.
[0] https://github.com/jdemel/socis-2015-gr-results
On 07.12.2016 00:52, hanwen wrote:
Dear all,
I just want to know
Hi Junxiao,
so, the tests for polar codes pass? But in GRC the examples won't run?
What does GRC report? I'm referring to the flowgraph error window.
Can you disable some blocks in GRC until it is executable? This might
point us in the correct direction. Also, which example do you try?
Cheers
Vishwesh,
And to do that the only way is to write the corresponding
"noc_block_fir.v" and put it in the lib/rfnoc folder?
Yes.
you have to create the noc_block_fir if you haven't done that yet. What I
wrote with "USE_HLS" is how you tell the noc_block_addsub.v that he should
pick the HLS IP.
Hi,
"TL;DR: You are writing your IP (module) in HLS, but you need to put it
into the Computation Engine to use the block in the RFNoC Framework"
And to do that the only way is to write the corresponding "noc_block_fir.v"
and put it in the lib/rfnoc folder?
>From what you wrote, I thought I could
Hi Vishwesh,
Please take a look at [1] which is not-that-new reference, but the idea is
still the same (this reference can be also found in the getting started
guide [2] which at the end has links to the videos of the presentation that
uses this slides). Specifically at slide 7. The noc_block_* is
Hi,
No I haven't added noc_block_fir.v file. Am I supposed to add it in
lib/rfnoc folder along with other files such as noc_block_addsub.v? Also is
there any guide on how to write this file?
I didn't get your last line
"and the way it uses to choose if the sources that it is going to use
(either
HI Vishwesh,
For the first part, yes, please only add noc_block elements into the auto
inst file.
For the second part, if you add that like into the lib/rfnoc/Makefile.srcs
you are telling the build system that you added verilog sources with that
name. Given that you are using HLS for that, that
Hi,
Thanks for the detailed reply.
>>From these I could add noc_block_digital_gain (built successfully)
>>but couldn't add chdr_fifo_large (running make X310_RFNOC_HLS_HG gave
an error)
Could you please tell us what error did it throw?
I inserted the following code in rfnoc_ce_auto_
Hello Vikesh,
Please take a look at this section of our "Getting started with RFNoC
Development" guide, specifically the "wiring CE" section [1]. As Marcus
stated, NoC blocks start with "noc_block_", and this is the way to identify
them in the sources.
On 12/06/2016 10:37 PM, Vishwesh Rege wrote:
21 matches
Mail list logo
