Ooohhhh, I hadn't even thought about that.  Thank you!!  I'm still
interested in why the Python block doesn't work 'correctly' while the C++
block does, so if you do get some time I'd really be interested in your
findings.

Thanks!!

On Tue, Feb 28, 2017 at 11:38 AM, Marcus Müller <marcus.muel...@ettus.com>
wrote:

> Hi Dave,
>
> haven't gotten around to looking at your block, but I presume it uses
> message passing to emit PMTs, is that right?
>
> In that case, the "message debug" block has a "store" input.
>
> Best regards,
>
> Marcus
>
> On 02/28/2017 05:15 PM, Dave NotTelling wrote:
>
> Anyone able to help out?  Hoping it's just something dumb that I didn't
> set properly.
>
> On Feb 25, 2017 17:32, "Dave NotTelling" <dmp250...@gmail.com> wrote:
>
>> I am attempting to test a block that takes in complex samples and outputs
>> PMT objects.  In order to properly test it, I need to run a vector through
>> it and verify that the correct number of PMT objects were created.  Thus
>> far I have not run across any blocks that act like a vector sink for PMT
>> objects.  So, I created my own in Python.  When I run with the custom PMT
>> sink the graph never stops.  If I create the same PMT sink in C++ then
>> everything works as expected.  Attached is some example code.  If you build
>> gr-poopie with `cmake .. && make && sudo make install && sudo ldconfig` you
>> can then run the `test.py` script in the base directory.  It should work
>> for the first three tests and then hang on the last one.
>>
>> Thanks!
>>
>> -Dave
>>
>
>
> _______________________________________________
> Discuss-gnuradio mailing 
> listDiscuss-gnuradio@gnu.orghttps://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
>
> _______________________________________________
> 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

Reply via email to