On Thu, Feb 20, 2014 at 11:25 PM, Kelly Boswell wrote:
> After the make test failed for this module, I decided to poke around to see
> if there is an easy fix. I made a script that simply executes the test over
> and over until it seg faults and exits after the core file is created.
>
> x@
After the make test failed for this module, I decided to poke around to see
if there is an easy fix. I made a script that simply executes the test over
and over until it seg faults and exits after the core file is created.
x@:~/src/gnuradio/build/gr-digital/python/digital$ ./runtests.sh
Us
Where did you find that particular install?
Bruce
Sent from my iPad
On Feb 20, 2014, at 3:37 PM, Ed Criscuolo wrote:
> I just upgraded my ports-installed version of GR 3.6.3 to
> GR 3.7.2.1 with a simple "port upgrade gnuradio".
> The install went smoothly without errors and installed
> a worki
GnuRadio 3.7.2.1
OSX 10.8.5
I was setting up a flowgraph in GRC using the
mpsk_receiver_cc block and encountered a problem.
Don't know if it is a bug in the GRC xml or a
missing method in the block code.
In GRC, the mpsk_receiver's "loop_bandwidth" parameter
is underlined in the properties popup
On Thu, Feb 20, 2014 at 11:10 PM, Michael Dickens wrote:
> Hi Zhou - I think it would be great to see how far GNU Radio can be pushed
> with respect to MIMO processing. With advances in both algorithms and
> multi-core CPU raw processing capabilities, the added computational
> requirements for M
Dear Martin,
Thanks for the hints.
I think this function helps: set_min_noutput_items()
Problem:
Says, the instantaneous interpolation_factor is 3.
As inherited from gr::block, the scheduler may call the general_work() with
noutput_items=2 (any number is possible).
When this happen, there is not
I just upgraded my ports-installed version of GR 3.6.3 to
GR 3.7.2.1 with a simple "port upgrade gnuradio".
The install went smoothly without errors and installed
a working copy of 3.7.2.1 with only a few operational
issues.
Hats off to Michael Dickens for his superb job of supporting
GnuRadio on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
mt19937 refers to the standard mersenne twister random number
generator used in boost; so this is your compiler complaining about
boost::random not having that. Which version of boost does your centos
machine have?
Greetings
Marcus
On 20.02.2014 22:5
Hello GR,
While building GR 3.7 (clone it from https://github.com/gnuradio/gnuradio)
on a Centos machine I got this error.
In file included from
/raid/nae/gnuradio-3.7/gr-blocks/lib/message_strobe_random_impl.cc:27:
/raid/nae/gnuradio-3.7/gr-blocks/lib/message_strobe_random_impl.h:48: error:
‘mt1
On 02/20/2014 01:49 PM, Jonathan Fox wrote:
> I know the I/O signature would control that part. So noutput_items is
> set in the IO signature, the size of it increases when a vector output
> is set. So if I call set_output_multiple in my constructor and have it
> set the size of my modulated wavefo
On Thu, Feb 20, 2014 at 2:33 PM, Martin Braun wrote:
> On 02/20/2014 01:49 PM, Jonathan Fox wrote:
> > I know the I/O signature would control that part. So noutput_items is
> > set in the IO signature, the size of it increases when a vector output
> > is set. So if I call set_output_multiple in my
On 02/20/2014 01:46 PM, Activecat wrote:
> I need to create a interpolator block which has a callback function to
> change its interpolation factor on the fly.
>
> If this block is inherited from gr::sync_interpolator, its interpolation
> factor cannot be changed on the fly because the interpolati
Hi Tom, thanks for your replay.
In fact, I'm not sure which are the sample rates of the example files
I'm using:
capture_941.8M_112.cfile
vf_call6_a725_d174_g5_Kc1EF00BAB3BAC7002.cfile
However, I've tried with different decimation rates, including typical
112, and nothing happens.
Gabriel
Hi Zhou - I think it would be great to see how far GNU Radio can be pushed with
respect to MIMO processing. With advances in both algorithms and multi-core
CPU raw processing capabilities, the added computational requirements for MIMO
might be realizable at some reasonable level (IIRC, they wer
On Thu, Feb 20, 2014 at 9:15 PM, Michael Dickens
wrote:
> Hi Zhou - Can you post some links to relevant papers / research, for folks
> like me to do a quick look at? I studied MIMO just a little bit, mostly
> from an IT perspective, not a practical one. But, I've read through a lot
> of papers (
Hi Zhou - Can you post some links to relevant papers / research, for folks like
me to do a quick look at? I studied MIMO just a little bit, mostly from an IT
perspective, not a practical one. But, I've read through a lot of papers (on
many subjects) and would be interested in knowing more abou
On Thu, Feb 20, 2014 at 3:24 PM, Martin Braun wrote:
> On 02/20/2014 04:01 AM, YiZiRui Zhou wrote:
> > Hi Martin,
> >
> > Thanks for your advice.
> >
> > Although it is not so clear, I have some elementary ideas on this
> > project and I'm on it now. On the other hand, I will keep an eye on the
>
Forgot to hit reply all.
On Wed, Feb 19, 2014 at 3:30 AM, Martin Braun wrote:
> On 02/19/2014 12:23 AM, Jonathan Fox wrote:
> > Thank you for the response, I apologize, I wasn't very clear at all in
> > explaining my problem and I can see that I came across confusing. Let me
> > quickly re-explai
Dear Sir,
I need to create a interpolator block which has a callback function to
change its interpolation factor on the fly.
If this block is inherited from gr::sync_interpolator, its interpolation
factor cannot be changed on the fly because the interpolation factor is an
argument of its construc
19 matches
Mail list logo
