[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Problem with Log Power FFT block
From: |
Marcus Müller |
Subject: |
Re: Problem with Log Power FFT block |
Date: |
Fri, 15 Jan 2021 17:09:46 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 |
That's peculiar, but as a side note:
The logarithm is a strictly monotonous function.
Therefore, you can just omit the logarithm operation altogether; the
thing with the maximum logarithm is always the thing with the maximum
amplitude, anyway. If you still need the logarithm of that value, you
can do that *after* the maximum and calculate one logarithm per FFT,
instead of one logarithm for every single sample.
On 15.01.21 13:49, Wojciech Kazubski wrote:
> Hello,
> Some time ago I used Log Power FFT block to detect a weak carrier in a
> noise.
> The output vector was passed through a Max block set to vector length 1024
> to
> determine the highest value, which was the signal power. This worked fine in
> GR-3.7, but after upgrade to GR-3.8 (release 3.8.2) I get this error in Log
> Power FFT block:
>
> Failed to eval ''part' if vlen == 1 else 'none'': name 'vlen' is not defined
>
> Is this a bug or I am doing something wrong?
>
> --
> Wojciech Kazubski
>
>
>
smime.p7s
Description: S/MIME Cryptographic Signature
- Problem with Log Power FFT block, Wojciech Kazubski, 2021/01/15
- Re: Problem with Log Power FFT block, Jeff Long, 2021/01/15
- Re: Problem with Log Power FFT block, Christophe Seguinot, 2021/01/15
- Re: Problem with Log Power FFT block, wk, 2021/01/16
- Re: Problem with Log Power FFT block, wk, 2021/01/16
- Re: Problem with Log Power FFT block, Jeff Long, 2021/01/16
- Re: Problem with Log Power FFT block, wk, 2021/01/16
Re: Problem with Log Power FFT block,
Marcus Müller <=