Is there any progress on this attempt?
I can't find any fading model in python.
--
View this message in context:
http://gnuradio.4.n7.nabble.com/anyone-implement-the-Raleigh-fading-model-multi-path-tp23782p42327.html
Sent from the GnuRadio mailing list archive at Nabble.com.
__
I downloaded again and checked MD5 hash, but the same "errors" come out
during cmake. Since configurations is done as well as build files written
to appropriate folder, does that means that these errors are not serious?
io.h file is for example located in /usr/include/sys/io.h (is that like at
your
I updated the MacPorts install for GNU Radio to reflect the new 3.7.0 release
and changes to the master and next branches. Here are the new ports (and, some
related):
- gnuradio-legacy: the latest 3.6.5 release (currently 3.6.5.1).
- gnuradio: the current release (3.7.0 right now).
- gnuradio
I'm not sure its the job of a build system to clean up the broken state
left by either not running uninstall previously or an incomplete uninstall
routine - this strikes me as a bit of a hackish solution to a more general
problem
Rather than worry about this I would like to see people who build GNU
There are currently two fading model blocks that are usable in 3.7
both should show up in GRC - or from python you can use:
the flat fading model:
channels.fading_model( 8, 10.0/samp_rate, False, 4.0, 0 )
where args are {# sinusoids, fDTs, los_component, rician_factor,
prng_seed }
and a s
On Tue, Jul 2, 2013 at 5:24 AM, Nemanja Savic wrote:
> I downloaded again and checked MD5 hash, but the same "errors" come out
> during cmake. Since configurations is done as well as build files written to
> appropriate folder, does that means that these errors are not serious? io.h
> file is for
Hey guys,
I wonder whether anyone has done this before/can help me out. I'm looking
to compile GNURadio with all static libraries, so that there are zero .so
dependencies. I've been playing around with CMake, but it looks like the
linker order is wrong for compiling against static libraries:
What
Hello everyone,
Quick update on the London meetup next week. I still haven't
identified a location (had one; fell through; looking for another
spot). Please let me know (if you haven't already) if you'll be
joining me so I can find a place appropriate for the size.
What I do know is that it will
The latest simple_ra includes pulsar processing support, although very
few amateurs will have an antenna big enough to do any pulsar work, it turns
out, because of the fractional resampler, to have been relatively
easy to support.
simple_ra now relies on the gr-ra_blocks OOT module.
So, you'
> But this happens each time python does "from gnuradio import gr_unittest":
> <6>[ 390.919792] python (1771): undefined instruction: pc=42a9c328 <6>[
> 390.919822] Code: f26ee1fe e12fff1e (ee190f1d)
A "final" update, just to close my own thread.
Case 1: It happens during "cm
Hi,
I intend to transmit and receive full duplex using my USRP N200 SBX on 2
FDM basis. I have one transmit python script which could transmit m-seq
LFSR data stream which is working perfectly.
I have combined it with the uhd_rx_cfile.py by having 2 instances of the
parent class gr.top_block.
I
On Tue, Jul 2, 2013 at 3:59 PM, Monahan-Mitchell, Tim
wrote:
>> But this happens each time python does "from gnuradio import gr_unittest":
>> <6>[ 390.919792] python (1771): undefined instruction: pc=42a9c328 <6>[
>> 390.919822] Code: f26ee1fe e12fff1e (ee190f1d)
>
> A "final"
I see different use cases of this in the gnuradio tree, like:
gr::thread::scoped_lock guard(d_mutex);
gr::thread::scoped_lock l(d_mutex);
gr::thread::scoped_lock lock(d_setlock);
As well as variances of whether the mutex variable is declared in a header
file...
Could someone lend some kind wo
On Tue, Jul 2, 2013 at 4:06 PM, Monahan-Mitchell, Tim <
tmona...@qti.qualcomm.com> wrote:
> I see different use cases of this in the gnuradio tree, like:
>
> gr::thread::scoped_lock guard(d_mutex);
>
> gr::thread::scoped_lock l(d_mutex);
>
> gr::thread::scoped_lock lock(d_setlock);
>
> As well as
Ø The associated mutex is usually a (private) member variable of a class, and
is used as a synchronization object by different class methods. As a member
variable, you have a choice to name it whatever you want. If the mutex is the
only one in the class, we usually call it d_mutex. If there
15 matches
Mail list logo
