Re: [Discuss-gnuradio] File sink Recording Issue
Hello Jahnavendra Mattipa:
Unfortunately, I am having a trouble opening your GRC file. If you are
reading it from GNU Radio, you can simply use a file source. If you are
using Matlab/Octave, you can do something like this:
read = fread(fopen('sam.dat'),2048,'single');
IQ = read(1:2:end) + read(2:2:end)*i;
Where 'sam.dat' is the file path, 2048 is the length to read, and 'single'
is the datatype (ieee754 single precssion). (Assuming complex datatype; if
float, data is not interleaved so you should skip the second line).
The data is in pure binary format, so text editors won't open it properly
(as explained in the GNURadio wiki).
Regards,
Kyeong Su Shin
On Sun, Apr 2, 2017 at 10:14 PM, Jahnavendra Mattipa <
jahna.mattipa2...@gmail.com> wrote:
> Hello all,
>
> 1st.py
>
>
> array
>
>
> fm_record.txt
>
>
> lpf.grc
>
>
> sam.dat
>
>
> sam.doc
>
> I am jahnavendra. I am facing some difficulty while recording the data
> in the gnuradio 'grc' file. I recorded data using fil sink but it is
> looking like some special characters are showing while opening the recorded
> file. Can anyone please tell me how to identify the recorded data and which
> which format best suites to open the file. While recording the data using
> signal generator it is creating in the order of GB range files and i
> attached some recorded files, using these you may get an idea about my
> problem.
> Thank you in advance.
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] log4cpp library not found
Hi, Ok, there's something wrong with your ldconfig. Since we're actively talking about linkage of stuff, you would probably do good if you fixed that. Anyway, did you also install log4cpp-devel? Best regards, Marcus On 03.04.2017 08:12, li...@lazygranch.com wrote: > sudo yum search all log4cpp > == Matched: log4cpp > == > log4cpp-devel.x86_64 : Development tools for Log for C++ > liblog4cpp5.x86_64 : Logging for C++ > > ldconfig -v | grep liblog4cpp > ldconfig: Can't stat /usr/lib64/graphviz/sharp: No such file or directory > ldconfig: Can't stat /usr/lib64/graphviz/java: No such file or directory > ldconfig: Can't stat /usr/lib64/graphviz/perl: No such file or directory > ldconfig: Can't stat /usr/lib64/graphviz/php: No such file or directory > ldconfig: Can't stat /usr/lib64/graphviz/ocaml: No such file or directory > ldconfig: Can't stat /usr/lib64/graphviz/python: No such file or directory > ldconfig: Can't stat /usr/lib64/graphviz/lua: No such file or directory > ldconfig: Can't stat /usr/lib64/graphviz/tcl: No such file or directory > ldconfig: Can't stat /usr/lib64/graphviz/guile: No such file or directory > ldconfig: Can't stat /usr/lib64/graphviz/ruby: No such file or directory > ldconfig: Path `/opt/kde3/lib64' given more than once > ldconfig: Path `/opt/kde3/lib' given more than once > ldconfig: Can't stat /libx32: No such file or directory > ldconfig: Can't stat /usr/libx32: No such file or directory > ldconfig: Cannot stat /opt/kde3/lib64/libgmcop.so: No such file or directory > liblog4cpp.so.5 -> liblog4cpp.so.5.0.6 > liblog4cpp.so.6.0 -> liblog4cpp.so.6.0.0 > liblog4cpp.so.5 -> liblog4cpp.so.5.0.6 > > > > On Sun, 2 Apr 2017 20:27:03 -0700 > Cinaed Simson wrote: > >> On 04/02/2017 04:17 PM, li...@lazygranch.com wrote: >>> Regarding the Marcus cmake, I guessed that src would copy to lib, >>> but that didn't happen. (Easy to check by file dates.) I ended up >>> copying the new FindLog4cpp.cmake to both locations myself. I did a >>> diff with the -s option and they are the same. >>> >>> diff >>> -s /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake >>> /usr/local/lib/cmake/gnuradio/FindLog4cpp.cmake >>> Files /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake >>> and /usr/local/lib/cmake/gnuradio/FindLog4cpp.cmake are identical >>> >>> >>> The problem is still there. I downloaded the log4cpp from the >>> opensuse repo, which of course would use the "normal" library >>> (/usr/lib64) rather than the local library, but that didn't work >>> either. >>> >>> So in summary, the problem is still there. >> Correct me if I'm wrong, but it appears the system installed version >> of liblog4cpp is in /usr/lib64 and the source version you built is in >> /usr/local/lib64. >> >> Please post the output of >> >>yum search log4cpp >> >> and >> >> ldconfig -v | grep liblog4cpp >> >> -- Cinaed >>> >>> On Sun, 2 Apr 2017 14:16:07 -0700 >>> Cinaed Simson wrote: >>> On 04/01/2017 03:40 PM, li...@lazygranch.com wrote: > find / -name "FindLog4cpp.cmake" > /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake > /usr/local/lib/cmake/gnuradio/FindLog4cpp.cmake > > That file is found twice. Is that the problem? If not, which do I > replace? Or perhaps both. Or does one file cause the other file to > be updated? No, one file is the source file and the other file is the installed in your gnuradio installation directory. Try diff /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake /usr/local/lib/cmake/gnuradio/FindLog4cpp.cmake That is, diff on the two files and make sure they're the same. If they're different, I'm not sure which one it would be reading - my guess would be the one /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake. In any case, I'm not sure where you stand with this problem. Did you receive a file from Marcus? -- Cinaed > > On Sat, 1 Apr 2017 19:03:52 +0200 > Marcus Müller wrote: > >> That's very interesting, considering that I believe the CMake >> script that looks for log4cpp uses the same pkg-command to look >> for it... >> >> Ok. So there's something strange going on with that >> cmake/Modules/FindLog4cpp.cmake, probably. >> >> Can you replace that Find...cmake with the one I've attached and >> give it a try? >> >> Cheers, >> >> Marcus >> >> >> On 01.04.2017 18:27, li...@lazygranch.com wrote: >>> Hyphen instead of underscore. >>> >>> pkg-config --libs log4cpp >>> -L/usr/local/lib64 -llog4cpp >>> >>> So pkg-config finds the library. Note I got the same problem >>> regarding not finding log4cpp when I used the opensuse package >>> manager version instead of making my own in /usr/src. >>> >>> >>> >>> >>
Re: [Discuss-gnuradio] log4cpp library not found
Yes to the dev install. I'm not exactly sure what I can do about ldconfig. Apologies in advance for an advert laden website link, but should I add /usr/local/lib64 as shown below: https://codeyarns.com/2014/01/14/how-to-add-library-directory-to-ldconfig-cache/ The odd thing is log4cpp is the only library with this problem, yet many other libraries are found in /usr/local by gnuradio. The libraries for the sdrs for example. I also built my own iqbalance (forgot the exact name) in /use/local. There was some issue with what opensuse provided. Original Message From: Marcus Müller Sent: Monday, April 3, 2017 3:02 AM To: discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] log4cpp library not found Hi, Ok, there's something wrong with your ldconfig. Since we're actively talking about linkage of stuff, you would probably do good if you fixed that. Anyway, did you also install log4cpp-devel? Best regards, Marcus On 03.04.2017 08:12, li...@lazygranch.com wrote: > sudo yum search all log4cpp > == Matched: log4cpp > == > log4cpp-devel.x86_64 : Development tools for Log for C++ > liblog4cpp5.x86_64 : Logging for C++ > > ldconfig -v | grep liblog4cpp > ldconfig: Can't stat /usr/lib64/graphviz/sharp: No such file or directory > ldconfig: Can't stat /usr/lib64/graphviz/java: No such file or directory > ldconfig: Can't stat /usr/lib64/graphviz/perl: No such file or directory > ldconfig: Can't stat /usr/lib64/graphviz/php: No such file or directory > ldconfig: Can't stat /usr/lib64/graphviz/ocaml: No such file or directory > ldconfig: Can't stat /usr/lib64/graphviz/python: No such file or directory > ldconfig: Can't stat /usr/lib64/graphviz/lua: No such file or directory > ldconfig: Can't stat /usr/lib64/graphviz/tcl: No such file or directory > ldconfig: Can't stat /usr/lib64/graphviz/guile: No such file or directory > ldconfig: Can't stat /usr/lib64/graphviz/ruby: No such file or directory > ldconfig: Path `/opt/kde3/lib64' given more than once > ldconfig: Path `/opt/kde3/lib' given more than once > ldconfig: Can't stat /libx32: No such file or directory > ldconfig: Can't stat /usr/libx32: No such file or directory > ldconfig: Cannot stat /opt/kde3/lib64/libgmcop.so: No such file or directory > liblog4cpp.so.5 -> liblog4cpp.so.5.0.6 > liblog4cpp.so.6.0 -> liblog4cpp.so.6.0.0 > liblog4cpp.so.5 -> liblog4cpp.so.5.0.6 > > > > On Sun, 2 Apr 2017 20:27:03 -0700 > Cinaed Simson wrote: > >> On 04/02/2017 04:17 PM, li...@lazygranch.com wrote: >>> Regarding the Marcus cmake, I guessed that src would copy to lib, >>> but that didn't happen. (Easy to check by file dates.) I ended up >>> copying the new FindLog4cpp.cmake to both locations myself. I did a >>> diff with the -s option and they are the same. >>> >>> diff >>> -s /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake >>> /usr/local/lib/cmake/gnuradio/FindLog4cpp.cmake >>> Files /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake >>> and /usr/local/lib/cmake/gnuradio/FindLog4cpp.cmake are identical >>> >>> >>> The problem is still there. I downloaded the log4cpp from the >>> opensuse repo, which of course would use the "normal" library >>> (/usr/lib64) rather than the local library, but that didn't work >>> either. >>> >>> So in summary, the problem is still there. >> Correct me if I'm wrong, but it appears the system installed version >> of liblog4cpp is in /usr/lib64 and the source version you built is in >> /usr/local/lib64. >> >> Please post the output of >> >> yum search log4cpp >> >> and >> >> ldconfig -v | grep liblog4cpp >> >> -- Cinaed >>> >>> On Sun, 2 Apr 2017 14:16:07 -0700 >>> Cinaed Simson wrote: >>> On 04/01/2017 03:40 PM, li...@lazygranch.com wrote: > find / -name "FindLog4cpp.cmake" > /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake > /usr/local/lib/cmake/gnuradio/FindLog4cpp.cmake > > That file is found twice. Is that the problem? If not, which do I > replace? Or perhaps both. Or does one file cause the other file to > be updated? No, one file is the source file and the other file is the installed in your gnuradio installation directory. Try diff /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake /usr/local/lib/cmake/gnuradio/FindLog4cpp.cmake That is, diff on the two files and make sure they're the same. If they're different, I'm not sure which one it would be reading - my guess would be the one /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake. In any case, I'm not sure where you stand with this problem. Did you receive a file from Marcus? -- Cinaed > > On Sat, 1 Apr 2017 19:03:52 +0200 > Marcus Müller wrote: > >> That's very interesting, considering that I believe the CMake >> script that looks for log4cpp uses the same pkg-command to look >> for it... >> >
Re: [Discuss-gnuradio] log4cpp library not found
No, you probably shouldn't fiddle manually. You should rather figure out what went wrong there. I'm getting the slight feeling that your system might be pretty special; can you try this whole dance on a clean Suse installation? Not quite sure we're not chasing ghosts here, due to something else on your system breaking things and making it wrong to make common assumptions about how things work on modern distros... Best regards, Marcus On 03.04.2017 12:17, li...@lazygranch.com wrote: > Yes to the dev install. > > I'm not exactly sure what I can do about ldconfig. > > Apologies in advance for an advert laden website link, but should I add > /usr/local/lib64 as shown below: > https://codeyarns.com/2014/01/14/how-to-add-library-directory-to-ldconfig-cache/ > > The odd thing is log4cpp is the only library with this problem, yet many > other libraries are found in /usr/local by gnuradio. The libraries for the > sdrs for example. I also built my own iqbalance (forgot the exact name) in > /use/local. There was some issue with what opensuse provided. > > > > > Original Message > From: Marcus Müller > Sent: Monday, April 3, 2017 3:02 AM > To: discuss-gnuradio@gnu.org > Subject: Re: [Discuss-gnuradio] log4cpp library not found > > Hi, > > Ok, there's something wrong with your ldconfig. Since we're actively > talking about linkage of stuff, you would probably do good if you fixed > that. > > Anyway, did you also install log4cpp-devel? > > Best regards, > Marcus > > On 03.04.2017 08:12, li...@lazygranch.com wrote: >> sudo yum search all log4cpp >> == Matched: log4cpp >> == >> log4cpp-devel.x86_64 : Development tools for Log for C++ >> liblog4cpp5.x86_64 : Logging for C++ >> >> ldconfig -v | grep liblog4cpp >> ldconfig: Can't stat /usr/lib64/graphviz/sharp: No such file or directory >> ldconfig: Can't stat /usr/lib64/graphviz/java: No such file or directory >> ldconfig: Can't stat /usr/lib64/graphviz/perl: No such file or directory >> ldconfig: Can't stat /usr/lib64/graphviz/php: No such file or directory >> ldconfig: Can't stat /usr/lib64/graphviz/ocaml: No such file or directory >> ldconfig: Can't stat /usr/lib64/graphviz/python: No such file or directory >> ldconfig: Can't stat /usr/lib64/graphviz/lua: No such file or directory >> ldconfig: Can't stat /usr/lib64/graphviz/tcl: No such file or directory >> ldconfig: Can't stat /usr/lib64/graphviz/guile: No such file or directory >> ldconfig: Can't stat /usr/lib64/graphviz/ruby: No such file or directory >> ldconfig: Path `/opt/kde3/lib64' given more than once >> ldconfig: Path `/opt/kde3/lib' given more than once >> ldconfig: Can't stat /libx32: No such file or directory >> ldconfig: Can't stat /usr/libx32: No such file or directory >> ldconfig: Cannot stat /opt/kde3/lib64/libgmcop.so: No such file or directory >> liblog4cpp.so.5 -> liblog4cpp.so.5.0.6 >> liblog4cpp.so.6.0 -> liblog4cpp.so.6.0.0 >> liblog4cpp.so.5 -> liblog4cpp.so.5.0.6 >> >> >> >> On Sun, 2 Apr 2017 20:27:03 -0700 >> Cinaed Simson wrote: >> >>> On 04/02/2017 04:17 PM, li...@lazygranch.com wrote: Regarding the Marcus cmake, I guessed that src would copy to lib, but that didn't happen. (Easy to check by file dates.) I ended up copying the new FindLog4cpp.cmake to both locations myself. I did a diff with the -s option and they are the same. diff -s /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake /usr/local/lib/cmake/gnuradio/FindLog4cpp.cmake Files /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake and /usr/local/lib/cmake/gnuradio/FindLog4cpp.cmake are identical The problem is still there. I downloaded the log4cpp from the opensuse repo, which of course would use the "normal" library (/usr/lib64) rather than the local library, but that didn't work either. So in summary, the problem is still there. >>> Correct me if I'm wrong, but it appears the system installed version >>> of liblog4cpp is in /usr/lib64 and the source version you built is in >>> /usr/local/lib64. >>> >>> Please post the output of >>> >>> yum search log4cpp >>> >>> and >>> >>> ldconfig -v | grep liblog4cpp >>> >>> -- Cinaed On Sun, 2 Apr 2017 14:16:07 -0700 Cinaed Simson wrote: > On 04/01/2017 03:40 PM, li...@lazygranch.com wrote: >> find / -name "FindLog4cpp.cmake" >> /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake >> /usr/local/lib/cmake/gnuradio/FindLog4cpp.cmake >> >> That file is found twice. Is that the problem? If not, which do I >> replace? Or perhaps both. Or does one file cause the other file to >> be updated? > No, one file is the source file and the other file is the > installed in your gnuradio installation directory. > > Try > > diff /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake > /usr/local/lib/cmake/gnuradio/FindLog4cpp.cmake > > That i
Re: [Discuss-gnuradio] log4cpp library not found
Funny thing you mention a clean installation. I found btrfs to be a disaster on opensuse. It turns out on some machines this is a known problem. It turned out the snapshots provided by btrfs were worthless, and it would lock up my machine. So I did a fresh install of opensuse on ext4 for the OS just last week. I didn't mirror /usr/local, so everything there is fresh off of mostly git source. So I would say the installation is as clean as can be expected. I had to add the ham and science repositories. Original Message From: Marcus Müller Sent: Monday, April 3, 2017 3:19 AM To: li...@lazygranch.com; discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] log4cpp library not found No, you probably shouldn't fiddle manually. You should rather figure out what went wrong there. I'm getting the slight feeling that your system might be pretty special; can you try this whole dance on a clean Suse installation? Not quite sure we're not chasing ghosts here, due to something else on your system breaking things and making it wrong to make common assumptions about how things work on modern distros... Best regards, Marcus On 03.04.2017 12:17, li...@lazygranch.com wrote: > Yes to the dev install. > > I'm not exactly sure what I can do about ldconfig. > > Apologies in advance for an advert laden website link, but should I add > /usr/local/lib64 as shown below: > https://codeyarns.com/2014/01/14/how-to-add-library-directory-to-ldconfig-cache/ > > The odd thing is log4cpp is the only library with this problem, yet many > other libraries are found in /usr/local by gnuradio. The libraries for the > sdrs for example. I also built my own iqbalance (forgot the exact name) in > /use/local. There was some issue with what opensuse provided. > > > > > Original Message > From: Marcus Müller > Sent: Monday, April 3, 2017 3:02 AM > To: discuss-gnuradio@gnu.org > Subject: Re: [Discuss-gnuradio] log4cpp library not found > > Hi, > > Ok, there's something wrong with your ldconfig. Since we're actively > talking about linkage of stuff, you would probably do good if you fixed > that. > > Anyway, did you also install log4cpp-devel? > > Best regards, > Marcus > > On 03.04.2017 08:12, li...@lazygranch.com wrote: >> sudo yum search all log4cpp >> == Matched: log4cpp >> == >> log4cpp-devel.x86_64 : Development tools for Log for C++ >> liblog4cpp5.x86_64 : Logging for C++ >> >> ldconfig -v | grep liblog4cpp >> ldconfig: Can't stat /usr/lib64/graphviz/sharp: No such file or directory >> ldconfig: Can't stat /usr/lib64/graphviz/java: No such file or directory >> ldconfig: Can't stat /usr/lib64/graphviz/perl: No such file or directory >> ldconfig: Can't stat /usr/lib64/graphviz/php: No such file or directory >> ldconfig: Can't stat /usr/lib64/graphviz/ocaml: No such file or directory >> ldconfig: Can't stat /usr/lib64/graphviz/python: No such file or directory >> ldconfig: Can't stat /usr/lib64/graphviz/lua: No such file or directory >> ldconfig: Can't stat /usr/lib64/graphviz/tcl: No such file or directory >> ldconfig: Can't stat /usr/lib64/graphviz/guile: No such file or directory >> ldconfig: Can't stat /usr/lib64/graphviz/ruby: No such file or directory >> ldconfig: Path `/opt/kde3/lib64' given more than once >> ldconfig: Path `/opt/kde3/lib' given more than once >> ldconfig: Can't stat /libx32: No such file or directory >> ldconfig: Can't stat /usr/libx32: No such file or directory >> ldconfig: Cannot stat /opt/kde3/lib64/libgmcop.so: No such file or directory >> liblog4cpp.so.5 -> liblog4cpp.so.5.0.6 >> liblog4cpp.so.6.0 -> liblog4cpp.so.6.0.0 >> liblog4cpp.so.5 -> liblog4cpp.so.5.0.6 >> >> >> >> On Sun, 2 Apr 2017 20:27:03 -0700 >> Cinaed Simson wrote: >> >>> On 04/02/2017 04:17 PM, li...@lazygranch.com wrote: Regarding the Marcus cmake, I guessed that src would copy to lib, but that didn't happen. (Easy to check by file dates.) I ended up copying the new FindLog4cpp.cmake to both locations myself. I did a diff with the -s option and they are the same. diff -s /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake /usr/local/lib/cmake/gnuradio/FindLog4cpp.cmake Files /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake and /usr/local/lib/cmake/gnuradio/FindLog4cpp.cmake are identical The problem is still there. I downloaded the log4cpp from the opensuse repo, which of course would use the "normal" library (/usr/lib64) rather than the local library, but that didn't work either. So in summary, the problem is still there. >>> Correct me if I'm wrong, but it appears the system installed version >>> of liblog4cpp is in /usr/lib64 and the source version you built is in >>> /usr/local/lib64. >>> >>> Please post the output of >>> >>> yum search log4cpp >>> >>> and >>> >>> ldconfig -v | grep liblog4cpp >>> >>> -- Cinaed On Sun, 2 Apr 2017 14:16:07 -0700 Cin
Re: [Discuss-gnuradio] log4cpp library not found
You said you didn't mirror /usr/local, does that imply you copied over other things? Best regards, Marcus On 03.04.2017 12:32, li...@lazygranch.com wrote: > Funny thing you mention a clean installation. I found btrfs to be a disaster > on opensuse. It turns out on some machines this is a known problem. It turned > out the snapshots provided by btrfs were worthless, and it would lock up my > machine. So I did a fresh install of opensuse on ext4 for the OS just last > week. I didn't mirror /usr/local, so everything there is fresh off of mostly > git source. So I would say the installation is as clean as can be expected. I > had to add the ham and science repositories. > > Original Message > From: Marcus Müller > Sent: Monday, April 3, 2017 3:19 AM > To: li...@lazygranch.com; discuss-gnuradio@gnu.org > Subject: Re: [Discuss-gnuradio] log4cpp library not found > > No, you probably shouldn't fiddle manually. You should rather figure out > what went wrong there. I'm getting the slight feeling that your system > might be pretty special; can you try this whole dance on a clean Suse > installation? Not quite sure we're not chasing ghosts here, due to > something else on your system breaking things and making it wrong to > make common assumptions about how things work on modern distros... > > Best regards, > > Marcus > > > On 03.04.2017 12:17, li...@lazygranch.com wrote: >> Yes to the dev install. >> >> I'm not exactly sure what I can do about ldconfig. >> >> Apologies in advance for an advert laden website link, but should I add >> /usr/local/lib64 as shown below: >> https://codeyarns.com/2014/01/14/how-to-add-library-directory-to-ldconfig-cache/ >> >> The odd thing is log4cpp is the only library with this problem, yet many >> other libraries are found in /usr/local by gnuradio. The libraries for the >> sdrs for example. I also built my own iqbalance (forgot the exact name) in >> /use/local. There was some issue with what opensuse provided. >> >> >> >> >> Original Message >> From: Marcus Müller >> Sent: Monday, April 3, 2017 3:02 AM >> To: discuss-gnuradio@gnu.org >> Subject: Re: [Discuss-gnuradio] log4cpp library not found >> >> Hi, >> >> Ok, there's something wrong with your ldconfig. Since we're actively >> talking about linkage of stuff, you would probably do good if you fixed >> that. >> >> Anyway, did you also install log4cpp-devel? >> >> Best regards, >> Marcus >> >> On 03.04.2017 08:12, li...@lazygranch.com wrote: >>> sudo yum search all log4cpp >>> == Matched: log4cpp >>> == >>> log4cpp-devel.x86_64 : Development tools for Log for C++ >>> liblog4cpp5.x86_64 : Logging for C++ >>> >>> ldconfig -v | grep liblog4cpp >>> ldconfig: Can't stat /usr/lib64/graphviz/sharp: No such file or directory >>> ldconfig: Can't stat /usr/lib64/graphviz/java: No such file or directory >>> ldconfig: Can't stat /usr/lib64/graphviz/perl: No such file or directory >>> ldconfig: Can't stat /usr/lib64/graphviz/php: No such file or directory >>> ldconfig: Can't stat /usr/lib64/graphviz/ocaml: No such file or directory >>> ldconfig: Can't stat /usr/lib64/graphviz/python: No such file or directory >>> ldconfig: Can't stat /usr/lib64/graphviz/lua: No such file or directory >>> ldconfig: Can't stat /usr/lib64/graphviz/tcl: No such file or directory >>> ldconfig: Can't stat /usr/lib64/graphviz/guile: No such file or directory >>> ldconfig: Can't stat /usr/lib64/graphviz/ruby: No such file or directory >>> ldconfig: Path `/opt/kde3/lib64' given more than once >>> ldconfig: Path `/opt/kde3/lib' given more than once >>> ldconfig: Can't stat /libx32: No such file or directory >>> ldconfig: Can't stat /usr/libx32: No such file or directory >>> ldconfig: Cannot stat /opt/kde3/lib64/libgmcop.so: No such file or directory >>> liblog4cpp.so.5 -> liblog4cpp.so.5.0.6 >>> liblog4cpp.so.6.0 -> liblog4cpp.so.6.0.0 >>> liblog4cpp.so.5 -> liblog4cpp.so.5.0.6 >>> >>> >>> >>> On Sun, 2 Apr 2017 20:27:03 -0700 >>> Cinaed Simson wrote: >>> On 04/02/2017 04:17 PM, li...@lazygranch.com wrote: > Regarding the Marcus cmake, I guessed that src would copy to lib, > but that didn't happen. (Easy to check by file dates.) I ended up > copying the new FindLog4cpp.cmake to both locations myself. I did a > diff with the -s option and they are the same. > > diff > -s /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake > /usr/local/lib/cmake/gnuradio/FindLog4cpp.cmake > Files /usr/local/src/gnuradio/cmake/Modules/FindLog4cpp.cmake > and /usr/local/lib/cmake/gnuradio/FindLog4cpp.cmake are identical > > > The problem is still there. I downloaded the log4cpp from the > opensuse repo, which of course would use the "normal" library > (/usr/lib64) rather than the local library, but that didn't work > either. > > So in summary, the problem is still there. Correct me if I'm wrong, but it appears the system
Re: [Discuss-gnuradio] log4cpp library not found
Only /home was saved , but there was no code there. I kind of wished I had mirrored /usr/local because it was a lot of work to build some of the code again, but that wouldn't be a clean installation. How is this for an idea? Log4cpp isn't unique to gnuradio. I will dig around for some program that also uses log4cpp and see if the installation works. It would have to be code using cmake. I did a google on log4cpp dependency and found this: https://github.com/avxsynth/avxsynth/wiki I don't have to install it, just try to build it and see if it finds my log4cpp. Original Message From: Marcus Müller Sent: Monday, April 3, 2017 3:36 AM To: li...@lazygranch.com; discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] log4cpp library not found You said you didn't mirror /usr/local, does that imply you copied over other things? Best regards, Marcus On 03.04.2017 12:32, li...@lazygranch.com wrote: > Funny thing you mention a clean installation. I found btrfs to be a disaster > on opensuse. It turns out on some machines this is a known problem. It turned > out the snapshots provided by btrfs were worthless, and it would lock up my > machine. So I did a fresh install of opensuse on ext4 for the OS just last > week. I didn't mirror /usr/local, so everything there is fresh off of mostly > git source. So I would say the installation is as clean as can be expected. I > had to add the ham and science repositories. > > Original Message > From: Marcus Müller > Sent: Monday, April 3, 2017 3:19 AM > To: li...@lazygranch.com; discuss-gnuradio@gnu.org > Subject: Re: [Discuss-gnuradio] log4cpp library not found > > No, you probably shouldn't fiddle manually. You should rather figure out > what went wrong there. I'm getting the slight feeling that your system > might be pretty special; can you try this whole dance on a clean Suse > installation? Not quite sure we're not chasing ghosts here, due to > something else on your system breaking things and making it wrong to > make common assumptions about how things work on modern distros... > > Best regards, > > Marcus > > > On 03.04.2017 12:17, li...@lazygranch.com wrote: >> Yes to the dev install. >> >> I'm not exactly sure what I can do about ldconfig. >> >> Apologies in advance for an advert laden website link, but should I add >> /usr/local/lib64 as shown below: >> https://codeyarns.com/2014/01/14/how-to-add-library-directory-to-ldconfig-cache/ >> >> The odd thing is log4cpp is the only library with this problem, yet many >> other libraries are found in /usr/local by gnuradio. The libraries for the >> sdrs for example. I also built my own iqbalance (forgot the exact name) in >> /use/local. There was some issue with what opensuse provided. >> >> >> >> >> Original Message >> From: Marcus Müller >> Sent: Monday, April 3, 2017 3:02 AM >> To: discuss-gnuradio@gnu.org >> Subject: Re: [Discuss-gnuradio] log4cpp library not found >> >> Hi, >> >> Ok, there's something wrong with your ldconfig. Since we're actively >> talking about linkage of stuff, you would probably do good if you fixed >> that. >> >> Anyway, did you also install log4cpp-devel? >> >> Best regards, >> Marcus >> >> On 03.04.2017 08:12, li...@lazygranch.com wrote: >>> sudo yum search all log4cpp >>> == Matched: log4cpp >>> == >>> log4cpp-devel.x86_64 : Development tools for Log for C++ >>> liblog4cpp5.x86_64 : Logging for C++ >>> >>> ldconfig -v | grep liblog4cpp >>> ldconfig: Can't stat /usr/lib64/graphviz/sharp: No such file or directory >>> ldconfig: Can't stat /usr/lib64/graphviz/java: No such file or directory >>> ldconfig: Can't stat /usr/lib64/graphviz/perl: No such file or directory >>> ldconfig: Can't stat /usr/lib64/graphviz/php: No such file or directory >>> ldconfig: Can't stat /usr/lib64/graphviz/ocaml: No such file or directory >>> ldconfig: Can't stat /usr/lib64/graphviz/python: No such file or directory >>> ldconfig: Can't stat /usr/lib64/graphviz/lua: No such file or directory >>> ldconfig: Can't stat /usr/lib64/graphviz/tcl: No such file or directory >>> ldconfig: Can't stat /usr/lib64/graphviz/guile: No such file or directory >>> ldconfig: Can't stat /usr/lib64/graphviz/ruby: No such file or directory >>> ldconfig: Path `/opt/kde3/lib64' given more than once >>> ldconfig: Path `/opt/kde3/lib' given more than once >>> ldconfig: Can't stat /libx32: No such file or directory >>> ldconfig: Can't stat /usr/libx32: No such file or directory >>> ldconfig: Cannot stat /opt/kde3/lib64/libgmcop.so: No such file or directory >>> liblog4cpp.so.5 -> liblog4cpp.so.5.0.6 >>> liblog4cpp.so.6.0 -> liblog4cpp.so.6.0.0 >>> liblog4cpp.so.5 -> liblog4cpp.so.5.0.6 >>> >>> >>> >>> On Sun, 2 Apr 2017 20:27:03 -0700 >>> Cinaed Simson wrote: >>> On 04/02/2017 04:17 PM, li...@lazygranch.com wrote: > Regarding the Marcus cmake, I guessed that src would copy to lib, > but that didn't happen. (Easy to check by file dates
Re: [Discuss-gnuradio] log4cpp library not found
I really do believe it's something about GNU Radio's build system and your system not harmonizing very well, and we won't learn much about that, no matter whether something else builds or not. In any case, I'm a bit worried that on a fresh Suse system, ldconfig should be broken already, so there's something up with your /home/ if that isn't usually the case. On 03.04.2017 13:04, li...@lazygranch.com wrote: > Only /home was saved , but there was no code there. I kind of wished I had > mirrored /usr/local because it was a lot of work to build some of the code > again, but that wouldn't be a clean installation. > > How is this for an idea? Log4cpp isn't unique to gnuradio. I will dig around > for some program that also uses log4cpp and see if the installation works. It > would have to be code using cmake. > > I did a google on log4cpp dependency and found this: > https://github.com/avxsynth/avxsynth/wiki > > I don't have to install it, just try to build it and see if it finds my > log4cpp. > > Original Message > From: Marcus Müller > Sent: Monday, April 3, 2017 3:36 AM > To: li...@lazygranch.com; discuss-gnuradio@gnu.org > Subject: Re: [Discuss-gnuradio] log4cpp library not found > > You said you didn't mirror /usr/local, does that imply you copied over > other things? > > Best regards, > Marcus > > > On 03.04.2017 12:32, li...@lazygranch.com wrote: >> Funny thing you mention a clean installation. I found btrfs to be a disaster >> on opensuse. It turns out on some machines this is a known problem. It >> turned out the snapshots provided by btrfs were worthless, and it would lock >> up my machine. So I did a fresh install of opensuse on ext4 for the OS just >> last week. I didn't mirror /usr/local, so everything there is fresh off of >> mostly git source. So I would say the installation is as clean as can be >> expected. I had to add the ham and science repositories. >> >> Original Message >> From: Marcus Müller >> Sent: Monday, April 3, 2017 3:19 AM >> To: li...@lazygranch.com; discuss-gnuradio@gnu.org >> Subject: Re: [Discuss-gnuradio] log4cpp library not found >> >> No, you probably shouldn't fiddle manually. You should rather figure out >> what went wrong there. I'm getting the slight feeling that your system >> might be pretty special; can you try this whole dance on a clean Suse >> installation? Not quite sure we're not chasing ghosts here, due to >> something else on your system breaking things and making it wrong to >> make common assumptions about how things work on modern distros... >> >> Best regards, >> >> Marcus >> >> >> On 03.04.2017 12:17, li...@lazygranch.com wrote: >>> Yes to the dev install. >>> >>> I'm not exactly sure what I can do about ldconfig. >>> >>> Apologies in advance for an advert laden website link, but should I add >>> /usr/local/lib64 as shown below: >>> https://codeyarns.com/2014/01/14/how-to-add-library-directory-to-ldconfig-cache/ >>> >>> The odd thing is log4cpp is the only library with this problem, yet many >>> other libraries are found in /usr/local by gnuradio. The libraries for the >>> sdrs for example. I also built my own iqbalance (forgot the exact name) in >>> /use/local. There was some issue with what opensuse provided. >>> >>> >>> >>> >>> Original Message >>> From: Marcus Müller >>> Sent: Monday, April 3, 2017 3:02 AM >>> To: discuss-gnuradio@gnu.org >>> Subject: Re: [Discuss-gnuradio] log4cpp library not found >>> >>> Hi, >>> >>> Ok, there's something wrong with your ldconfig. Since we're actively >>> talking about linkage of stuff, you would probably do good if you fixed >>> that. >>> >>> Anyway, did you also install log4cpp-devel? >>> >>> Best regards, >>> Marcus >>> >>> On 03.04.2017 08:12, li...@lazygranch.com wrote: sudo yum search all log4cpp == Matched: log4cpp == log4cpp-devel.x86_64 : Development tools for Log for C++ liblog4cpp5.x86_64 : Logging for C++ ldconfig -v | grep liblog4cpp ldconfig: Can't stat /usr/lib64/graphviz/sharp: No such file or directory ldconfig: Can't stat /usr/lib64/graphviz/java: No such file or directory ldconfig: Can't stat /usr/lib64/graphviz/perl: No such file or directory ldconfig: Can't stat /usr/lib64/graphviz/php: No such file or directory ldconfig: Can't stat /usr/lib64/graphviz/ocaml: No such file or directory ldconfig: Can't stat /usr/lib64/graphviz/python: No such file or directory ldconfig: Can't stat /usr/lib64/graphviz/lua: No such file or directory ldconfig: Can't stat /usr/lib64/graphviz/tcl: No such file or directory ldconfig: Can't stat /usr/lib64/graphviz/guile: No such file or directory ldconfig: Can't stat /usr/lib64/graphviz/ruby: No such file or directory ldconfig: Path `/opt/kde3/lib64' given more than once ldconfig: Path `/opt/kde3/lib' given more than once ldconfig: Can't stat /libx32: No such file or directory >
Re: [Discuss-gnuradio] gr-trellis test_cpm.py question
Here is what needs to be done (simple). N is the dimensionality of the signal space (found earlier in the code). Now we need to set up a filter bank to project the incoming signal to all its dimensions. These filters are held on the MF[] array. Now (due to laziness) i didn't write a for loop that instantiates N filter blocks, but I just instantiated them manually for the case of N=2 in filter_fir_filter_xxx_0_0 = filter.fir_filter_ccc(Q, MF[0].conjugate()) filter_fir_filter_xxx_0_0_0 = filter.fir_filter_ccc(Q, MF[1].conjugate()) So what needs to be done is (through a for loop) instantiate these N filter blocks and appropriately modify the code (in the "connections" part) to make the right connections to and from these blocks. best, Achilleas On Sun, Apr 2, 2017 at 6:58 PM, Andy Walls wrote: > Hi Achilleas: > > In the test_cpm.py example under gr-trellis, there is a comment: > > "# only works for N=2, do it manually for N>2..." > https://github.com/gnuradio/gnuradio/blob/master/gr- > trellis/examples/python/test_cpm.py#L108 > > Could you, or anyone else, elaborate on what need to be done manually for > N>2? > > Thanks, > Andy > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] gr-trellis test_cpm.py question
Ah, OK. Thank you. I don't need anything that adaptive or automatic myself. I plan to play around with viterbi demodulation of GMSK and maybe SOQPSK this week. As I dig into the gr-trellis implementation I may have more questions. Regards, Andy On Mon, 2017-04-03 at 08:50 -0400, Achilleas Anastasopoulos wrote: > Here is what needs to be done (simple). > > > N is the dimensionality of the signal space (found earlier in the > code). > Now we need to set up a filter bank to project the incoming signal to > all its dimensions. These filters are held on the MF[] array. > Now (due to laziness) i didn't write a for loop that instantiates N > filter blocks, but I just instantiated them manually for the case of > N=2 in > > > filter_fir_filter_xxx_0_0 = filter.fir_filter_ccc(Q, > MF[0].conjugate()) > > filter_fir_filter_xxx_0_0_0 = filter.fir_filter_ccc(Q, > MF[1].conjugate()) > > > > So what needs to be done is (through a for loop) instantiate these N > filter blocks > and appropriately modify the code (in the "connections" part) to make > the right > connections to and from these blocks. > > > best, > Achilleas > > > > On Sun, Apr 2, 2017 at 6:58 PM, Andy Walls > wrote: > Hi Achilleas: > > In the test_cpm.py example under gr-trellis, there is a > comment: > > "# only works for N=2, do it manually for N>2..." > > https://github.com/gnuradio/gnuradio/blob/master/gr-trellis/examples/python/test_cpm.py#L108 > > Could you, or anyone else, elaborate on what need to be done > manually for N>2? > > Thanks, > Andy > > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] gr-trellis test_cpm.py question
sure, feel free to look into the gr-trellis documentation and provide some feedback. If you have further questions please let us know. best, Achilleas On Mon, Apr 3, 2017 at 9:02 AM, Andy Walls wrote: > Ah, OK. Thank you. > I don't need anything that adaptive or automatic myself. > > I plan to play around with viterbi demodulation of GMSK and maybe SOQPSK > this week. > > As I dig into the gr-trellis implementation I may have more questions. > > Regards, > Andy > > On Mon, 2017-04-03 at 08:50 -0400, Achilleas Anastasopoulos wrote: > > Here is what needs to be done (simple). > > > > > > N is the dimensionality of the signal space (found earlier in the > > code). > > Now we need to set up a filter bank to project the incoming signal to > > all its dimensions. These filters are held on the MF[] array. > > Now (due to laziness) i didn't write a for loop that instantiates N > > filter blocks, but I just instantiated them manually for the case of > > N=2 in > > > > > > filter_fir_filter_xxx_0_0 = filter.fir_filter_ccc(Q, > > MF[0].conjugate()) > > > > filter_fir_filter_xxx_0_0_0 = filter.fir_filter_ccc(Q, > > MF[1].conjugate()) > > > > > > > > So what needs to be done is (through a for loop) instantiate these N > > filter blocks > > and appropriately modify the code (in the "connections" part) to make > > the right > > connections to and from these blocks. > > > > > > best, > > Achilleas > > > > > > > > On Sun, Apr 2, 2017 at 6:58 PM, Andy Walls > > wrote: > > Hi Achilleas: > > > > In the test_cpm.py example under gr-trellis, there is a > > comment: > > > > "# only works for N=2, do it manually for N>2..." > > https://github.com/gnuradio/gnuradio/blob/master/gr- > trellis/examples/python/test_cpm.py#L108 > > > > Could you, or anyone else, elaborate on what need to be done > > manually for N>2? > > > > Thanks, > > Andy > > > > > > > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] OS X Fuzzy Text in GRC
Michael helped me out yesterday, but the fuzziness didn't go away by changing the Python info.plist file per https://trac.macports.org/ticket/36410. I'm just going to accept it as a slightly annoying 'feature' since it's not something that kills functionality. If anyone has success in making the text inside the blocks as clean as the text in the menus then I'd love to hear how. I also tried changing the gr-qtgui conf file to raster, opengl, and native with no change between them. On Sun, Apr 2, 2017 at 2:10 PM, Michael Dickens wrote: > Can you send me (off list) a screen snapshot or the like so that I can see > what you mean by "fuzzy"? I see nothing out of the ordinary in GRC when > running, but then maybe I'm not looking at the correct text... Cheers! - MLD > > On Sun, Apr 2, 2017, at 10:12 AM, Dave NotTelling wrote: > > I just installed GNU Radio via macports and the text in the blocks is > really fuzzy. I ran across https://trac.macports.org/ticket/36410 but I > don't quite understand how to make it work for my issue. Is there > something in /Applications/MacPorts/Qt4 that I should be changing? I'm > running OS X 10.11.6. > > > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] FG probe generation of thread.start() race conditions (python tutorials)
James,
thanks for pointing that out!
On 03/29/2017 10:22 AM, James Shimer wrote:
> Sorry if this is a duplicate/newbie question (didn't find anything
> searching). When going thru the python examples. I came across a race
> condition where the thread would start to run prior to object's
> constructor completing. The fix is to manually move the code generated
> for starting the probe thread to the very end of the constructor.
>
>
> If this "bug" is open already thanks for your time, if not here are some
> more details:
>
>
> Tutorial 3, section 3.1.5, you're asked to modify the probe thread to
> reference members of the class to set_ampl and set_freq, those functions
> in-turn access members of the object, which may not have been
> initialized yet because the thread runs while the constructor is still
> running.
>
> https://wiki.gnuradio.org/index.php/Guided_Tutorial_GNU_Radio_in_Python
>
> The symptom:
>
> Exception in thread Thread-1:
>
> Traceback (most recent call last):
>
> File
> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py",
> line 801, in __bootstrap_inner
>
> self.run()
>
> File
> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py",
> line 754, in run
>
> self.__target(*self.__args, **self.__kwargs)
>
> File "power.py", line 95, in _variable_function_probe_0_probe
>
> self.set_ampl(0.3)
>
> File "power.py", line 174, in set_ampl
>
> self.analog_sig_source_x_0.set_amplitude(self.ampl)
>
> File
> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/gnuradio/gr/hier_block2.py",
> line 92, in __getattr__
>
> return getattr(self._impl, name)
>
> AttributeError: 'top_block_sptr' object has no attribute
> 'analog_sig_source_x_0'
>
>
> The resolution:
>
> diff -rupN if_else.py if_else2.py
>
> --- if_else.py2017-03-29 13:20:32.0 -0400
>
> +++ if_else2.py2017-03-29 13:19:37.0 -0400
>
> @@ -101,7 +101,6 @@ class if_else(gr.top_block, Qt.QWidget):
>
> time.sleep(1.0 / (10))
>
> _variable_function_probe_0_thread =
> threading.Thread(target=_variable_function_probe_0_probe)
>
> _variable_function_probe_0_thread.daemon = True
>
> -_variable_function_probe_0_thread.start()
>
>
>
> self.qtgui_time_sink_x_0 = qtgui.time_sink_f(
>
> 1024, #size
>
> @@ -160,6 +159,7 @@ class if_else(gr.top_block, Qt.QWidget):
>
> self.connect((self.analog_sig_source_x_0, 0),
> (self.blocks_throttle_0, 0))
>
> self.connect((self.analog_sig_source_x_1, 0),
> (self.qtgui_time_sink_x_0, 0))
>
> self.connect((self.blocks_throttle_0, 0), (self.probe, 0))
>
> +_variable_function_probe_0_thread.start()
>
>
>
> def closeEvent(self, event):
>
> self.settings = Qt.QSettings("GNU Radio", "if_else")
>
>
>
> Thanks
>
>
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] gr-ieee 802.11 and commercial AP (late ACK packets)
Hello Bastian, How much the delay between sensing the channel and sending the ACK should be. With X300 I was able to achieve a minm of 80 microsecs round trip time. Not less than that. I am now sure that it cant be done on GPP, just wondering how fast it should be. If you can direct me to some link, that would be great :) Regards Sumit -- View this message in context: http://gnuradio.4.n7.nabble.com/gr-ieee-802-11-and-commercial-AP-late-ACK-packets-tp63339p63445.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] gr-ieee 802.11 and commercial AP (late ACK packets)
Hi, On 04/03/2017 09:44 PM, sumitstop wrote: > Hello Bastian, > > How much the delay between sensing the channel and sending the ACK should > be. With X300 I was able to achieve a minm of 80 microsecs round trip time. > Not less than that. Interesting. What exactly did you measure? I assume you used PCIe? > > I am now sure that it cant be done on GPP, just wondering how fast it should > be. If you can direct me to some link, that would be great :) The timing constraints are given in the standard (They depend on the mode, but they are below 80us). Best, Bastian ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] gr-ieee 802.11 and commercial AP (late ACK packets)
Hello Bastian, Yes I used PCIe(X300). I measured two things. One "rtt" with latency_test.cpp which gave 80 microsecs and another receiver latency where I set the GPIO HIGH as soon as the receive power exceeds a threshold. I made a custom C++ script for this. This gave 52 microsecs. Regards Sumit -- View this message in context: http://gnuradio.4.n7.nabble.com/gr-ieee-802-11-and-commercial-AP-late-ACK-packets-tp63339p63447.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
