[Discuss-gnuradio] attach pre existing blocks

2017-07-17 Thread Alex Homero Rivadeneira Erazo
Hi everybody,

Do you know, if it is possible to attach blocks that are available in a
recent version of gnuradio (such as 3.7.12) and include them in an older
version of gnuradio (such as 3.7.9).

The blocks that I am interested are Protocol formatter (Async) and Multiply
by Tag Value blocks.


Regards,

Alex
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] Debugging polar code crashes

2017-07-13 Thread Alex Homero Rivadeneira Erazo
Hi Johannes

The GNU radio program turns dark and is unresponsive, and there is not
anything printed on the command line.

Best regards,

Alex



On Thu, Jul 13, 2017 at 3:03 AM, Johannes Demel <de...@ant.uni-bremen.de>
wrote:

> Hi Alex,
>
> could you be more specific about
> 'When I drop the POLAR code configurator block on the canvas, the gnuradio
> program turns down.'?
> Does GRC quit with an error? Does it turn dark and is unresponsive? Is
> there anything printed on the commandline?
>
> Cheers
> Johannes
>
>
> On 12.07.2017 18:04, Marcus Müller wrote:
>
>> Those test failures aren't great, but I think they might be bugs in the
>> tests.
>>
>> So, OK, can't remember what you need to do under Ubuntu to get the full
>> Python debugging capability in GDB, but I wrote a (slightly dated, since
>> the python commands have improved) tutorial on debugging crashing Python
>> applications [1].
>> The idea is to simply execute your minimal crashing example using
>>
>> gdb --args python2 /path/to/flowgraph.py
>> (gdb) run
>> 
>> (gdb) backtrace
>>
>> and figure out why where how things crash. If you got a backtrace, and
>> don't immediately see how to proceed (hint: print a few local variables,
>> if possible, using gdb's "print" command), share it with the mailing list
>>
>> Best regards,
>> Marcus
>>
>> [1]https://wiki.gnuradio.org/index.php/TutorialsGDB
>> On 07/12/2017 05:50 PM, Alex Homero Rivadeneira Erazo wrote:
>>
>>> I am using ubuntu 16.04 LTS.
>>>
>>> At the end of the make test, I have obtained some failures:
>>>
>>> 97% tests passed, 6 tests failed out of 218
>>>
>>> Total Test time (real) = 142.49 sec
>>>
>>> The following tests FAILED:
>>> 48 - qa_ctrlport_probes (Failed)
>>> 59 - qa_cpp_py_binding (Failed)
>>> 76 - qa_cpp_py_binding_set (Failed)
>>> 124 - qa_filterbank (Failed)
>>> 154 - qa_ofdm_txrx (Failed)
>>> 197 - qa_fading_model (Failed)
>>> Errors while running CTest
>>> Makefile:61: recipe for target 'test' failed
>>> make: *** [test] Error 8
>>>
>>> Best regards,
>>>
>>> Alex
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Wed, Jul 12, 2017 at 11:46 AM, Marcus Müller
>>> <marcus.muel...@ettus.com <mailto:marcus.muel...@ettus.com>> wrote:
>>>
>>> That might still give us enough debug info. Which Linux distro are
>>> we talking about (or, is it Linux at all?)
>>>
>>> Best regards,
>>>
>>> Marcus
>>>
>>>
>>> On 07/12/2017 05:30 PM, Alex Homero Rivadeneira Erazo wrote:
>>>
>>>> Hi Marcus
>>>>
>>>> At this moment, I am installing the
>>>> gnuradio 3.7.12git-171-get72c77bc from source, which is the same
>>>> that I installed with pybombs . Unfortunately, I just already
>>>> built the gnuradio with "make && make test". The gnuradio that I
>>>> had with the standard installation was gnuradio 3.7.9
>>>>
>>>> Thanks
>>>>
>>>> Best regards,
>>>>
>>>> Alex
>>>>
>>>>
>>>>
>>>>
>>>> On Wed, Jul 12, 2017 at 11:13 AM, Marcus Müller
>>>> <marcus.muel...@ettus.com <mailto:marcus.muel...@ettus.com>> wrote:
>>>>
>>>> Hi Alex,
>>>>
>>>> that does indeed sound like a bug. Things shouldn't be crashing!
>>>>
>>>> So, what's the distribution you're working with? Maybe I can
>>>> help you a bit with the debugging. If you're, at the moment,
>>>> building GNU Radio, make sure that the CMake parameters
>>>> contain -DCMAKE_BUILD_TYPE=RelWithDebInfo , so that we get
>>>> debugging symbols :)
>>>>
>>>> Best regards,
>>>>
>>>> Marcus
>>>>
>>>>
>>>> On 07/12/2017 05:11 PM, Alex Homero Rivadeneira Erazo wrote:
>>>>
>>>>> Hi Marcus
>>>>>
>>>>> Based on your suggestion I have deleted my Nabbles account.
>>>>>
>>>>> Respect to my problem with the POLAR code
>>>>> configurator block, I checked the discussion threads, but
>

Re: [Discuss-gnuradio] polar code example

2017-07-12 Thread Alex Homero Rivadeneira Erazo
I am using ubuntu 16.04 LTS.

At the end of the make test, I have obtained some failures:

97% tests passed, 6 tests failed out of 218

Total Test time (real) = 142.49 sec

The following tests FAILED:
 48 - qa_ctrlport_probes (Failed)
 59 - qa_cpp_py_binding (Failed)
 76 - qa_cpp_py_binding_set (Failed)
124 - qa_filterbank (Failed)
154 - qa_ofdm_txrx (Failed)
197 - qa_fading_model (Failed)
Errors while running CTest
Makefile:61: recipe for target 'test' failed
make: *** [test] Error 8

Best regards,

Alex

On Wed, Jul 12, 2017 at 11:46 AM, Marcus Müller <marcus.muel...@ettus.com>
wrote:

> That might still give us enough debug info. Which Linux distro are we
> talking about (or, is it Linux at all?)
>
> Best regards,
>
> Marcus
>
> On 07/12/2017 05:30 PM, Alex Homero Rivadeneira Erazo wrote:
>
> Hi Marcus
>
> At this moment, I am installing the gnuradio 3.7.12git-171-get72c77bc
> from source, which is the same that I installed with pybombs .
> Unfortunately, I just already built the gnuradio with "make && make test".
> The gnuradio that I had with the standard installation was gnuradio 3.7.9
>
> Thanks
>
> Best regards,
>
> Alex
>
>
>
>
> On Wed, Jul 12, 2017 at 11:13 AM, Marcus Müller <marcus.muel...@ettus.com>
> wrote:
>
>> Hi Alex,
>>
>> that does indeed sound like a bug. Things shouldn't be crashing!
>>
>> So, what's the distribution you're working with? Maybe I can help you a
>> bit with the debugging. If you're, at the moment, building GNU Radio, make
>> sure that the CMake parameters contain -DCMAKE_BUILD_TYPE=RelWithDebInfo
>> , so that we get debugging symbols :)
>>
>> Best regards,
>>
>> Marcus
>>
>> On 07/12/2017 05:11 PM, Alex Homero Rivadeneira Erazo wrote:
>>
>> Hi Marcus
>>
>> Based on your suggestion I have deleted my Nabbles account.
>>
>> Respect to my problem with the POLAR code configurator block, I checked
>> the discussion threads, but anyone gave a solution.
>>
>> Note that this problem does not happen with a gnuradio installed with the
>> distribution's package manager (standard installation). However, the
>> problem with this installation method is that gnuradio is not up to date
>> and it does not have all the blocks that I need in my work. That is why I
>> used pybombs to install gnuradio which has the blocks that I need. Now the
>> problem is that gnuradio with pybombs does work with the POLAR code
>> configurator block. When I drop the POLAR code configurator block on the
>> canvas, the gnuradio program turns down.
>>
>> At this moment, I am installing gnuradio from source. If you have other
>> ideas please tell me.
>>
>> Thanks
>>
>> Best regards,
>>
>> Alex
>>
>>
>>
>> On Wed, Jul 12, 2017 at 9:43 AM, Marcus Müller <marcus.muel...@ettus.com>
>> wrote:
>>
>>> Hi Alex,
>>>
>>> I hope you do get an answer, but that mail from Jose is from the
>>> beginning of 2016 – not extremely likely.
>>>
>>> Anyway, have you seen the other answers that Jose got?
>>> If not: That's Nabble's fault. I never tire to repeat:
>>> Nabble is just a terrible, terrible web frontend to use the official GNU
>>> Radio Mailing list.
>>>
>>> It's not the official mailing list archive. It never was, and it never
>>> will be. The official way to sign up for the mailing list is
>>>
>>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>>
>>> and there's a link to the official mailing list archive, too.
>>>
>>> I'd recommend deleting your Nabble account, and directly signing up
>>> under the above address with your email account. It's really easier to
>>> use a proper email client (eg. GMail's web frontend) and simply the
>>> mails than Nabble. Nabble breaks discussion threads, it makes answers
>>> invisible, and it has cost us hours and hours of unnecessary work so
>>> far. PLEASE, don't use Nabble.
>>>
>>> Best regards,
>>>
>>> Marcus
>>>
>>>
>>> On 07/12/2017 01:52 PM, Alex Rivadeneira wrote:
>>> > Dear Jose
>>> >
>>> > Can you tell me if you solved the problem with the POLAR code
>>> configurator
>>> > block? because I have the same problem in the gnuradio installed with
>>> > pybombs.
>>> >
>>> > Thanks
>>> >
>>> > Alex
>>> >
>>> >
>>> >
>>> > --

Re: [Discuss-gnuradio] polar code example

2017-07-12 Thread Alex Homero Rivadeneira Erazo
Hi Marcus

At this moment, I am installing the gnuradio 3.7.12git-171-get72c77bc from
source, which is the same that I installed with pybombs . Unfortunately, I
just already built the gnuradio with "make && make test". The gnuradio that
I had with the standard installation was gnuradio 3.7.9

Thanks

Best regards,

Alex




On Wed, Jul 12, 2017 at 11:13 AM, Marcus Müller <marcus.muel...@ettus.com>
wrote:

> Hi Alex,
>
> that does indeed sound like a bug. Things shouldn't be crashing!
>
> So, what's the distribution you're working with? Maybe I can help you a
> bit with the debugging. If you're, at the moment, building GNU Radio, make
> sure that the CMake parameters contain -DCMAKE_BUILD_TYPE=RelWithDebInfo
> , so that we get debugging symbols :)
>
> Best regards,
>
> Marcus
>
> On 07/12/2017 05:11 PM, Alex Homero Rivadeneira Erazo wrote:
>
> Hi Marcus
>
> Based on your suggestion I have deleted my Nabbles account.
>
> Respect to my problem with the POLAR code configurator block, I checked
> the discussion threads, but anyone gave a solution.
>
> Note that this problem does not happen with a gnuradio installed with the
> distribution's package manager (standard installation). However, the
> problem with this installation method is that gnuradio is not up to date
> and it does not have all the blocks that I need in my work. That is why I
> used pybombs to install gnuradio which has the blocks that I need. Now the
> problem is that gnuradio with pybombs does work with the POLAR code
> configurator block. When I drop the POLAR code configurator block on the
> canvas, the gnuradio program turns down.
>
> At this moment, I am installing gnuradio from source. If you have other
> ideas please tell me.
>
> Thanks
>
> Best regards,
>
> Alex
>
>
>
> On Wed, Jul 12, 2017 at 9:43 AM, Marcus Müller <marcus.muel...@ettus.com>
> wrote:
>
>> Hi Alex,
>>
>> I hope you do get an answer, but that mail from Jose is from the
>> beginning of 2016 – not extremely likely.
>>
>> Anyway, have you seen the other answers that Jose got?
>> If not: That's Nabble's fault. I never tire to repeat:
>> Nabble is just a terrible, terrible web frontend to use the official GNU
>> Radio Mailing list.
>>
>> It's not the official mailing list archive. It never was, and it never
>> will be. The official way to sign up for the mailing list is
>>
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
>> and there's a link to the official mailing list archive, too.
>>
>> I'd recommend deleting your Nabble account, and directly signing up
>> under the above address with your email account. It's really easier to
>> use a proper email client (eg. GMail's web frontend) and simply the
>> mails than Nabble. Nabble breaks discussion threads, it makes answers
>> invisible, and it has cost us hours and hours of unnecessary work so
>> far. PLEASE, don't use Nabble.
>>
>> Best regards,
>>
>> Marcus
>>
>>
>> On 07/12/2017 01:52 PM, Alex Rivadeneira wrote:
>> > Dear Jose
>> >
>> > Can you tell me if you solved the problem with the POLAR code
>> configurator
>> > block? because I have the same problem in the gnuradio installed with
>> > pybombs.
>> >
>> > Thanks
>> >
>> > Alex
>> >
>> >
>> >
>> > --
>> > View this message in context: http://gnuradio.4.n7.nabble.co
>> m/polar-code-example-tp58407p64520.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
>>
>>
>> ___
>> Discuss-gnuradio mailing list
>> Discuss-gnuradio@gnu.org
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
>
>
>
> --
> Regards,
>
> Alex Homero Rivadeneira E.
> Cell: 438 397-8330 <(438)%20397-8330>
>
>
>


-- 
Regards,

Alex Homero Rivadeneira E.
Cell: 438 397-8330
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] polar code example

2017-07-12 Thread Alex Homero Rivadeneira Erazo
Hi Marcus

Based on your suggestion I have deleted my Nabbles account.

Respect to my problem with the POLAR code configurator block, I checked the
discussion threads, but anyone gave a solution.

Note that this problem does not happen with a gnuradio installed with the
distribution's package manager (standard installation). However, the
problem with this installation method is that gnuradio is not up to date
and it does not have all the blocks that I need in my work. That is why I
used pybombs to install gnuradio which has the blocks that I need. Now the
problem is that gnuradio with pybombs does work with the POLAR code
configurator block. When I drop the POLAR code configurator block on the
canvas, the gnuradio program turns down.

At this moment, I am installing gnuradio from source. If you have other
ideas please tell me.

Thanks

Best regards,

Alex



On Wed, Jul 12, 2017 at 9:43 AM, Marcus Müller 
wrote:

> Hi Alex,
>
> I hope you do get an answer, but that mail from Jose is from the
> beginning of 2016 – not extremely likely.
>
> Anyway, have you seen the other answers that Jose got?
> If not: That's Nabble's fault. I never tire to repeat:
> Nabble is just a terrible, terrible web frontend to use the official GNU
> Radio Mailing list.
>
> It's not the official mailing list archive. It never was, and it never
> will be. The official way to sign up for the mailing list is
>
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
> and there's a link to the official mailing list archive, too.
>
> I'd recommend deleting your Nabble account, and directly signing up
> under the above address with your email account. It's really easier to
> use a proper email client (eg. GMail's web frontend) and simply the
> mails than Nabble. Nabble breaks discussion threads, it makes answers
> invisible, and it has cost us hours and hours of unnecessary work so
> far. PLEASE, don't use Nabble.
>
> Best regards,
>
> Marcus
>
>
> On 07/12/2017 01:52 PM, Alex Rivadeneira wrote:
> > Dear Jose
> >
> > Can you tell me if you solved the problem with the POLAR code
> configurator
> > block? because I have the same problem in the gnuradio installed with
> > pybombs.
> >
> > Thanks
> >
> > Alex
> >
> >
> >
> > --
> > View this message in context: http://gnuradio.4.n7.nabble.
> com/polar-code-example-tp58407p64520.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
>
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>



-- 
Regards,

Alex Homero Rivadeneira E.
Cell: 438 397-8330
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio