Re: [Discuss-gnuradio] new to GNUradio: AFSK and codec2 gmsk modem

[Tom Rondeau]

On Mon, Jul 29, 2013 at 7:26 PM, Kristoff Bonne <address@hidden> wrote:
> Tom,
>
>
> (inline comments)
>
>
>
> On 29-07-13 17:01, Tom Rondeau wrote:
>>
>> On Mon, Jul 29, 2013 at 5:48 AM, Kristoff Bonne<address@hidden>
>> wrote:
>>>
>>>
>>>> Just found this, it might help:
>>>> https://github.com/dl1ksv/gr-afsk
>>>
>>> Hmmm. Looks interesting. A good start. :-)
>>>
>>>
>>> However, it seams I have another problem: it does not build on my system
>>> (ubuntu 12.04 LTS).
>>> It needs gnuradio-runtime and as I currently run gnuradio 3.6.4.1 + Boost
>>> 1.49 build from source, it doesn't have that.
>>>
>>> I tried to build 3.7.1 -which seams to include gnuradio-runtime in its
>>> source- but that fails on a number of tests (qa_fir_filter,
>>> qa_freq_xlating_fir_filter, qa_constellation_receiver and
>>> qa_codec2_vocoder).
>>>
>>> Grrr! :-(
>>
>> Those QA failures are probable a Volk issue. Try running volk_profile
>> after you run 'make install'. If a given kernel fails for an
>> architecture, it will be disabled. Once volk_profile completes (it can
>> take a while), try rerunning 'make test'.
>
> Good news and bad news.
>
> First test: to run volk_profile without doing the "make install" (I did not
> want to install something where the "make tests" indicated is wasn't 100 %
> OK). Same result as before. "make test" still gives 4 errors.
>
> 2nd test:  ran "sudo make install" anyway, then volk_profile and then "make
> test":
> Good news and bad news.
> 3 tests are now OK, only the codec2 vocoder still fails.
>
>
> --- cut here --- cut here --- cut here --- cut here --- cut here ---
> The following tests FAILED:
>     168 - qa_codec2_vocoder (Failed)
> Errors while running CTest
> --- cut here --- cut here --- cut here --- cut here --- cut here ---

Yes, you need to have GNU Radio installed for volk_profile to work properly.

>
>> If it still fails, run
>> 'ctest -V -R volk' and send us the output.
>
> Is now OK:
> --- cut here --- cut here --- cut here --- cut here --- cut here ---
> 1: *** No errors detected
> 1/1 Test #1: qa_volk_test_all .................   Passed    0.92 sec
>
> The following tests passed:
>     qa_volk_test_all
>
> 100% tests passed, 0 tests failed out of 1
> --- cut here --- cut here --- cut here --- cut here --- cut here ---
>
>
> What is strange is that I do get an error when I do this test on the codec2
> vocoder block:
> --- cut here --- cut here --- cut here --- cut here --- cut here ---
>
> 168: Test command: /bin/sh
> "/home/kristoff/ham/gnuradio/gnuradio-3.7.0/build/gr-vocoder/python/vocoder/qa_codec2_vocoder_test.sh"
> 168: Test timeout computed to be: 9.99988e+06
> 168: F
> 168: ======================================================================
> 168: FAIL: test001_module_load (__main__.test_codec2_vocoder)
> 168: ----------------------------------------------------------------------
> 168: Traceback (most recent call last):
> 168:   File
> "/home/kristoff/ham/gnuradio/gnuradio-3.7.0/gr-vocoder/python/vocoder/qa_codec2_vocoder.py",
> line 54, in test001_module_load
> 168:     self.assertEqual(expected_data, actual_result)
> 168: AssertionError: Tuples differ: (0, 0, 0, 3, 2, 0, 1, 5, 6, 7,... != (0,
> 0, 0, 3, 2, 0, 1, 5, 6, 7,...
> 168:
> 168: First differing element 112:
> 168: 24
> 168: 25
> --- cut here --- cut here --- cut here --- cut here --- cut here ---
>
> Am I correct to assume that the errors means there is a difference between
> what it actually gets back from the module based on a test-pattern and what
> is expects.
> Is this related to the volt-libraries that produce a different result on my
> particular test.

The codec2 needs a bit of attention. I've not known it to fail like
this (and that's a very close result you're seeing), but we need to
update the version of codec2 that we're using. So unless you really
wanted to use codec2 with GNU Radio, just ignore this error since it's
very isolated.

> But I must say that there does is quite a difference between the test in
> gnuradio 3.6.4.1. and 3.7.0
>
> All the stuff about "data" and "expected data" are simply not present in the
> test-script in 3.6.4.1.
>
> Perhaps the thing here is that the script for 3.6.4.1. simply does not do
> this "compair with what we expect" test and it might be that this codec2
> library is just as wrong on 3.6.4.1 as in 3.7.0

Apparently, in 3.6, we weren't actually properly testing that code.


> Both versions I have are build with boost 1.49; as described in
> README.building-boost
>
> I can try with newer versions of boost; but I must say that when using Boost
> 1.54, GNUradio doesn't even compile on my box.
>
>
> What is the recommended version of boost to be used with gnuradio 3.7.0 ?

No recommended version. We just recommend not to use 1.46, 1.47, and
1.52. I haven't yet tried 1.54 and no one's reported any problems with
it, yet. I just use the default Ubuntu 13.04 version which is 1.53.

>> What's your processor?
>
> The machine is a dell laptop. The CPU is a quad-core "Intel(R) Core(TM) i5
> CPU       M 520  @ 2.40GHz"
> (which is a bit strange as the wikipedia says the 520m is supposed to be
> dual-core).

Ok, well the processor makes a bigger difference with Volk, but since
that actually seems to be working fine for you, the codec2 issue is
something else. Probably related to another version of a library.

Tom