Re: grcc and configparser
Hi Ryan, On 25/10/2021 19.07, Ryan Volz wrote: > It's possible that I backported a patch to the conda package, but I don't see > anything with a quick glance, so *shrug*. Most probably it is this PR. https://github.com/gnuradio/gnuradio/pull/3429 https://github.com/gnuradio/gnuradio/commit/ecbf67e1743 $ git tag --contains ecbf67e1743 v3.8.2.0 v3.8.3.0 v3.8.3.0-rc1 v3.8.3.1 v3.8.3.1-rc1 v3.8.4.0 v3.8.4.0-rc1 If you backport changes then it would be good to modify the version somehow to indicate that there are some changes from the upstream version. Regards, Vasil
Re: grcc and configparser
Hi Jameson, On 10/25/21 7:44 AM, Jameson Collins wrote: I have two installations of gnuradio. One is from conda, and the other is from source. Both claim to be 3.8.1.0. In the conda install when I run grcc on a certain flowgraph the python file is generated with a number of try-catch blocks around `import configparser`, I assume to catch the difference between python2 and python3. In my source install, with the exact same flowgraph, it only generates `import ConfigParser`, which doesn't work in python3. Any idea why these are different? It's possible that I backported a patch to the conda package, but I don't see anything with a quick glance, so *shrug*. Cheers, Ryan
Release Candidate v3.9.4.0-rc1
Here is a new release candidate, somewhat earlier than expected, due to a couple of regressions in v3.9.3.0 https://github.com/gnuradio/gnuradio/releases/tag/v3.9.4.0-rc1 Some other fixes and features were also backported in the process, for more details, see https://github.com/gnuradio/gnuradio/blob/v3.9.4.0-rc1/CHANGELOG.md The final v3.9.4.0 will be out next week if there are no issues, and the next set of releases (3.8.x.y and 3.9.x.y) will be out around December.
grcc and configparser
I have two installations of gnuradio. One is from conda, and the other is from source. Both claim to be 3.8.1.0. In the conda install when I run grcc on a certain flowgraph the python file is generated with a number of try-catch blocks around `import configparser`, I assume to catch the difference between python2 and python3. In my source install, with the exact same flowgraph, it only generates `import ConfigParser`, which doesn't work in python3. Any idea why these are different?
MPSK SVR SNR, Signal and Noise estimation
Hi everyone,
It seems like all estimators in MPSK_SNR_EST class, except for the SVR one
(shown below), have signal, noise, and SNR estimations. How does one get
the signal and noise components from the SVR estimate?
Regards,
Moses.
mpsk_snr_est_svr::mpsk_snr_est_svr(double alpha) : mpsk_snr_est(alpha)
{
d_y1 = 0;
d_y2 = 0;
}
int mpsk_snr_est_svr::update(int noutput_items, const gr_complex* input)
{
for (int i = 0; i < noutput_items; i++) {
double x = abs(input[i + 1]);
double x1 = abs(input[i]);
double y1 = (x * x) * (x1 * x1);
d_y1 = d_alpha * y1 + d_beta * d_y1;
double y2 = x * x * x * x;
d_y2 = d_alpha * y2 + d_beta * d_y2;
}
return noutput_items;
}
double mpsk_snr_est_svr::snr()
{
double x = d_y1 / (d_y2 - d_y1);
return 10.0 * log10(x - 1 + sqrt(x * (x - 1)));
}
Moses Browne Mwakyanjala
Founder - CEO
*Remos Space Systems AB*
m: +46 (0)70 278 2174
a: Aurorum 1C, 977 75 Luleå, Sweden
w: www.remosspace.com e: mbkit...@gmail.com
[image: image.png]
Re: ModuleNotFoundError while running unit test of the OOT
Thanks Jeff! BR niedz., 24 paź 2021 o 22:33 Jeff Long napisał(a): > That workaround doesn't make sense. The idea, though, is that some files > need to be moved/symlinked so Python can see them. Or the PYTHONPATH needs > adjustment. > > On Sun, Oct 24, 2021 at 4:23 PM Jeff Long wrote: > >> This is also true on the latest dev/master, and it was possible to do a >> "make test" before "make install" in 3.8. This has been noted in >> https://github.com/gnuradio/gnuradio/issues/4825, which also includes a >> workaround. >> >> On Sun, Oct 24, 2021 at 1:47 PM Marcin Puchlik via GNU Radio, the Free & >> Open-Source Toolkit for Software Radio wrote: >> >>> Hi, >>> While creating a squaring OOT module (just as an example), my unit test >>> failed because of *ModuleNotFoundError.* >>> This error occurs before running *make install*. After running *make >>> install* module is available and test is passing ok but it doesn't make >>> sense to do that. >>> I am using *3.9.3.0 *version of GNU Radio. I expect that after running *make >>> *there will be a python module called *square *(as I named my OOT, am I >>> correct?) >>> Below is the output after running *ctest -VV *command: >>> >>> Note: below output is obtained after running *make install *and then *make >>> uninstall *(after make install, module is available and the is no error) >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> *UpdateCTestConfiguration from >>> :/home/ubuntu/prefixes/gnuradio39/OOTs/gr-square/build/DartConfiguration.tclUpdateCTestConfiguration >>> from >>> :/home/ubuntu/prefixes/gnuradio39/OOTs/gr-square/build/DartConfiguration.tclTest >>> project /home/ubuntu/prefixes/gnuradio39/OOTs/gr-square/buildConstructing a >>> list of testsDone constructing a list of testsUpdating test list for >>> fixturesAdded 0 tests to meet fixture requirementsChecking test dependency >>> graph...Checking test dependency graph endtest 1Start 1: qa_square_ff1: >>> Test command: /usr/bin/sh >>> "/home/ubuntu/prefixes/gnuradio39/OOTs/gr-square/build/python/qa_square_ff_test.sh"1: >>> Test timeout computed to be: 10001: Traceback (most recent call >>> last):1: File >>> "/home/ubuntu/prefixes/gnuradio39/OOTs/gr-square/python/qa_square_ff.py", >>> line 12, in 1: from square import square_ff1: ImportError: >>> cannot import name 'square_ff' from 'square' (unknown location)1: 1: During >>> handling of the above exception, another exception occurred:1: 1: Traceback >>> (most recent call last):1: File >>> "/home/ubuntu/prefixes/gnuradio39/OOTs/gr-square/python/qa_square_ff.py", >>> line 18, in 1: from square import square_ff1: ImportError: >>> cannot import name 'square_ff' from 'square' (unknown location)1/1 Test #1: >>> qa_square_ff .***Failed0.26 sec0% tests passed, 1 >>> tests failed out of 1Total Test time (real) = 0.27 secThe following tests >>> FAILED: 1 - qa_square_ff (Failed)Errors while running CTest* >>> >>
