Block with overlapping window - consume_each() in regard to set_history()

[Marcin Wachowiak]

Hello,
I am having a hard time trying to correct a block that calculates
autocorrelation with overlapping.
Having read about set_history(), consume_each()  behaviour of the block
does not match my size calculations.

   - Should consume_each include the N-samples that are stored in history
   or not? (I guess history samples indices are calculated based on what is
   provided in consume_each())

The code of the block is as follows:
...
//setting parameters in constructor:
d_nonoverlap_size = d_snapshot_size-d_overlap_size;
set_history(d_overlap_size+1);

//determine input/output buffer sizes relationship (in connected blocks)
set_relative_rate(1.0/d_nonoverlap_size);
...

Then there is forecast:
...
// Setup input output relationship
for (int i=0; i out_matrix(out+d_num_inputs*d_num_inputs*i,
d_num_inputs,d_num_inputs);

// Do autocorrelation

out_matrix = (1.0/d_snapshot_size)*d_input_matrix.transpose()*d_input_matrix
.conjugate();
if (d_avg_method == 1)
out_matrix = 0.5*out_matrix+(0.5/d_snapshot_size)*d_J*out_matrix.conjugate()
*d_J;
}

// Tell runtime system how many input items we consumed on
// each input stream.
consume_each (d_nonoverlap_size*output_matrices+d_overlap_size);

// Tell runtime system how many output items we produced.
return (output_matrices);
}

When the block is simulated in comparison to no (0) overlap it returns
strange values probably due to sizing issues, some historical samples
distort the result.

[image: buffering_issue.png]
Whole code and more complex test
case(music_algo_simulation_2rx_with_noise.grc) is available here:
https://github.com/MarcinWachowiak/GNU-Radio-USRP-Beamforming
Please advise.
Kind regards,
Marcin Wachowiak

Re: First appear of the USRP blocks in GNU Radio

[isaac mario tupac davila]

Hi!

Thank you for your answers! It was great to see the email for the first
USRPs in sale.

I appreciate this information and thanks for clarifying the beginning of
USRP's with GNURadio.

Regards
Isaac T.

El vie, 18 dic 2020 a las 6:17, Marcus Müller () escribió:

> Hi Isaac,
>
> matter of fact: the "usual" distribution method for the driver for the
> USRP (1) and later even the early USRP2 were through the "usrp"
> directory within the GNU Radio source code, before the drivers were
> reimplemented as what we know as UHD.
>
> I don't know at which GNU Radio version these drivers appeared in the
> GNU Radio source tree, but honestly, feel free to check out the GNU
> Radio releases that we still have[1]: in GNU Radio 3.0.1, there was
> already a gr-usrp. Changes to "usrp/" from Eric Blossom, the GNU Radio
> maintainer of the time, reach back to 2003-07-30 (see usrp/ChangeLog and
> gr-usrp/ChangeLog in GNU Radio 3.0.1-rc1). So, basically I think it's
> pretty safe to say that together with the commercially availability of
> the USRP1, its interface was available within GNU Radio, probably even
> before. Matt Ettus was a contributor to GNU Radio before he made a USRP.
>
> Mind you, GNU Radio in 2003–2005 was quite a bit different – there was
> no GRC, to begin with; the Python bindings didn't exist until May 2003,
> and knowing SWIG, were probably sufficiently hard to build in the
> beginning, so its throroughly possible that people used the USRP within
> GNU Radio before building your flow graph with Python became the default
> thing to do.
>
> Cheers,
> Marcus
>
> [1] https://www.gnuradio.org/releases/gnuradio/
> On 18.12.20 11:10, Derek Kozel wrote:
> > Hi Isaac,
> >
> > The USRPs were originally built with the GNU Radio project in mind.
> > Here's probably the first email about the USRP1 in September 2002.
> >
> https://lists.gnu.org/archive/html/discuss-gnuradio/2002-09/msg00028.html
> >
> >
> https://lists.gnu.org/archive/html/discuss-gnuradio/2003-06/msg00010.html
> > links to:
> >
> https://web.archive.org/web/20030610161838/http://www.comsec.com/wiki?UniversalSoftwareRadioPeripheral
> >
> > Which has the line: "The Universal Software Radio Peripheral (if you
> > have an idea for a better name, let us know)"
> >
> > And the first USRPs for sale.
> >
> https://lists.gnu.org/archive/html/discuss-gnuradio/2004-12/msg00090.html
> >
> > Reading the first few years of emails on the list is a fun way to spend
> > an evening. Lots of people who are still around in the community or
> > doing SDR in different spaces like Gerald at FlexRadio.
> >
> > Cheers,
> > Derek
> >
> > On 17/12/2020 18:49, isaac mario tupac davila wrote:
> >> Hi community!
> >>
> >> I'm Isaac. I'd like to ask you a question. I'd like to add in my
> >> thesis information about the first time the USRP blocks appeared and
> >> were used. I found that the USRP1 was designed in 2004 but I'm not
> >> sure if this USRP appeared with the blocks or not.
> >>
> >> https://www.sgo.fi/~j/usrp/overview-open.pdf
> >> 
> >>
> >> If you know any information about it , I would really appreciate it.
> >>
> >> Thanks
> >> Regards
> >> Isaac T.
> >
>
>

Re: GNU Radio on Raspberry Pi 4?

[Franco VENTURI]

Gisle,
I just ran these commands here (I am on Fedora Linux version 33), and I didn't 
receive any error or warning:

git clone https://github.com/fventuri/gr-sdrplay.git
cd gr-sdrplay/
git checkout API3+RSPduo

This said, I don't think this thread called "GNU Radio on Raspberry Pi 4?" is 
the right place to further discuss build problems with the gr-sdrplay OOT 
module (besides the words 'MSVC building' make me think you are probably not 
using a Raspberry Pi), so I suggest creating a new issue about those here: 
https://github.com/fventuri/gr-sdrplay/issues

Franco


> On 12/18/2020 4:34 AM Gisle Vanem  wrote:
> 
>  
> Franco VENTURI wrote:
> 
> > if you are interested in using SDRplay API version 3.X (I think the latest 
> > version of their API is 3.07), and you are on GNU Radio 3.7, you may want 
> > to take a look at the gr-sdrplay GNU Radio OOT module I modified to work 
> > with SDRplay API version 3.X: 
> > https://github.com/fventuri/gr-sdrplay/tree/API3+RSPduo (notice the 
> > non-default branch name: 'API3+RSPduo').
> 
> I tried your 'master' branch. No problem building that.
> But I have problems with the 'API3+RSPduo' branch:
> 
> git checkout API3+RSPduo
> error: pathspec 'API3+RSPduo' did not match any file(s) known to git.
> 
> What??
> 
> Besides there are *many* warning '4250' in MSVC building
> this module:
>rsp1a_impl.h(33): warning C4250: 'gr::sdrplay3::rsp1a_impl':
>inherits 'gr::sdrplay3::rsp_impl::gr::sdrplay3::rsp_impl::start'
>via dominance
> 
> etc.

GPIo USRP E310

[Ivan Zahartchuk]

Hello. Tell me how to compile RFnoC firmware for USRP E310 so that you can
control GPIO through the Radio block?

Re: First appear of the USRP blocks in GNU Radio

[Marcus Müller]

Hi Isaac,

matter of fact: the "usual" distribution method for the driver for the
USRP (1) and later even the early USRP2 were through the "usrp"
directory within the GNU Radio source code, before the drivers were
reimplemented as what we know as UHD.

I don't know at which GNU Radio version these drivers appeared in the
GNU Radio source tree, but honestly, feel free to check out the GNU
Radio releases that we still have[1]: in GNU Radio 3.0.1, there was
already a gr-usrp. Changes to "usrp/" from Eric Blossom, the GNU Radio
maintainer of the time, reach back to 2003-07-30 (see usrp/ChangeLog and
gr-usrp/ChangeLog in GNU Radio 3.0.1-rc1). So, basically I think it's
pretty safe to say that together with the commercially availability of
the USRP1, its interface was available within GNU Radio, probably even
before. Matt Ettus was a contributor to GNU Radio before he made a USRP.

Mind you, GNU Radio in 2003–2005 was quite a bit different – there was
no GRC, to begin with; the Python bindings didn't exist until May 2003,
and knowing SWIG, were probably sufficiently hard to build in the
beginning, so its throroughly possible that people used the USRP within
GNU Radio before building your flow graph with Python became the default
thing to do.

Cheers,
Marcus

[1] https://www.gnuradio.org/releases/gnuradio/
On 18.12.20 11:10, Derek Kozel wrote:
> Hi Isaac,
> 
> The USRPs were originally built with the GNU Radio project in mind.
> Here's probably the first email about the USRP1 in September 2002.
> https://lists.gnu.org/archive/html/discuss-gnuradio/2002-09/msg00028.html
> 
> https://lists.gnu.org/archive/html/discuss-gnuradio/2003-06/msg00010.html
> links to:
> https://web.archive.org/web/20030610161838/http://www.comsec.com/wiki?UniversalSoftwareRadioPeripheral
> 
> Which has the line: "The Universal Software Radio Peripheral (if you
> have an idea for a better name, let us know)"
> 
> And the first USRPs for sale.
> https://lists.gnu.org/archive/html/discuss-gnuradio/2004-12/msg00090.html
> 
> Reading the first few years of emails on the list is a fun way to spend
> an evening. Lots of people who are still around in the community or
> doing SDR in different spaces like Gerald at FlexRadio.
> 
> Cheers,
> Derek
> 
> On 17/12/2020 18:49, isaac mario tupac davila wrote:
>> Hi community!
>>
>> I'm Isaac. I'd like to ask you a question. I'd like to add in my
>> thesis information about the first time the USRP blocks appeared and
>> were used. I found that the USRP1 was designed in 2004 but I'm not
>> sure if this USRP appeared with the blocks or not.
>>
>> https://www.sgo.fi/~j/usrp/overview-open.pdf
>> 
>>
>> If you know any information about it , I would really appreciate it.
>>
>> Thanks
>> Regards
>> Isaac T.
> 



smime.p7s
Description: S/MIME Cryptographic Signature

Re: First appear of the USRP blocks in GNU Radio

[Derek Kozel]

Hi Isaac,

The USRPs were originally built with the GNU Radio project in mind.
Here's probably the first email about the USRP1 in September 2002.
https://lists.gnu.org/archive/html/discuss-gnuradio/2002-09/msg00028.html

https://lists.gnu.org/archive/html/discuss-gnuradio/2003-06/msg00010.html
links to:
https://web.archive.org/web/20030610161838/http://www.comsec.com/wiki?UniversalSoftwareRadioPeripheral

Which has the line: "The Universal Software Radio Peripheral (if you
have an idea for a better name, let us know)"

And the first USRPs for sale.
https://lists.gnu.org/archive/html/discuss-gnuradio/2004-12/msg00090.html

Reading the first few years of emails on the list is a fun way to spend
an evening. Lots of people who are still around in the community or
doing SDR in different spaces like Gerald at FlexRadio.

Cheers,
Derek

On 17/12/2020 18:49, isaac mario tupac davila wrote:
> Hi community!
>
> I'm Isaac. I'd like to ask you a question. I'd like to add in my
> thesis information about the first time the USRP blocks appeared and
> were used. I found that the USRP1 was designed in 2004 but I'm not
> sure if this USRP appeared with the blocks or not.
>
> https://www.sgo.fi/~j/usrp/overview-open.pdf
>
> If you know any information about it , I would really appreciate it.
>
> Thanks
> Regards
> Isaac T.

Re: GNU Radio on Raspberry Pi 4?

[Gisle Vanem]

Franco VENTURI wrote:


if you are interested in using SDRplay API version 3.X (I think the latest 
version of their API is 3.07), and you are on GNU Radio 3.7, you may want to 
take a look at the gr-sdrplay GNU Radio OOT module I modified to work with 
SDRplay API version 3.X: 
https://github.com/fventuri/gr-sdrplay/tree/API3+RSPduo (notice the non-default 
branch name: 'API3+RSPduo').


I tried your 'master' branch. No problem building that.
But I have problems with the 'API3+RSPduo' branch:

git checkout API3+RSPduo
error: pathspec 'API3+RSPduo' did not match any file(s) known to git.

What??

Besides there are *many* warning '4250' in MSVC building
this module:
  rsp1a_impl.h(33): warning C4250: 'gr::sdrplay3::rsp1a_impl':
  inherits 'gr::sdrplay3::rsp_impl::gr::sdrplay3::rsp_impl::start'
  via dominance

etc.