discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: how to auto detect peak frequency in QT FFT sink


From: Cinaed Simson
Subject: Re: how to auto detect peak frequency in QT FFT sink
Date: Wed, 2 Dec 2020 18:43:29 -0800
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0

Actually, it's the opposite - maint-3.8 is the default and the master is 3.7.

Would you post your results of

   make test

in the build directory of

  gr-fhss_utils

for gnuradio-3.8?

-- Cinaed


On 12/2/20 5:20 PM, Kyle A Logue wrote:
FYI all gr-fhss_utils tests pass on a properly configured machine.

I highly recommend you use `pybombs` in the future.

Is it possible you have the `maint-3.7` branch of fhss_utils? I think the master branch is for 3.8.

Kyle



From: Cinaed Simson <cinaed.simson@gmail.com>
Sent: Wednesday, December 2, 2020 13:32
To: Kyle A Logue <kyle.a.logue@aero.org>; discuss-gnuradio@gnu.org <discuss-gnuradio@gnu.org>
Subject: Re: how to auto detect peak frequency in QT FFT sink
 
I was just curious - and the only reason I choose FFT peak was because you did.

I built gnuradio and the OOT modules from source. And it doesn't matter where you hang the gnuradio root.

And it's highly unlikely that I could compile, link to gnuradio, and run make test with missing dependencies.

On the machine I first tested it which was an old 64 bit Dell Optiplex desktop running Debian 10 (buster), and it logs the following error in dmesg:

  [1233081.177466] traps: python3[22326] trap invalid opcode ip:7feef013fc5c sp:7ffed724b720 error:0 in libgnuradio-fhss_utils.so.42c85270[7feef0133000+1d000]

- where I believe error:0 implies division by zero.

Then I installed it on a new i5 laptop and it passes the first test - which I presume is the division by 0 error above - but fails the other 2 tests - and doesn't log any errors in dmesg.

Then I downloaded and installed gr-pdu_utils and gr-sandia_utils and both of those packages are riddled with make test errors.

I'm presuming these are work in progress - and I don't the time right now to explore those errors further.

-- Cinaed


On 12/1/20 2:17 PM, Kyle A Logue wrote:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]