Re: [Discuss-gnuradio] Does GRAS support setting max noutpu t_items?

[devin . butterfield]

Hi Josh, 

Thanks for the quick work on this. Setting max noutputitems from grc works fine now. 
--
Regards, Devin 

----- Reply message -----
From: "Josh Blum" <address@hidden>
To: <address@hidden>
Cc: <address@hidden>
Subject: [Discuss-gnuradio] Does GRAS support setting max noutput_items?
Date: Sun, Jul 14, 2013 12:27 pm




On 07/14/2013 02:43 PM, Devin Butterfield wrote:
> Hi folks,
> 
> I just started experimenting with GRAS and ran into this:
> 
>>>> GRAS: The debug asserts are enabled. <<<
> Created default thread pool with 4 threads.
> Traceback (most recent call last):
>   File "top_block.py", line 80, in <module>
>     tb.Run(True, 10)
>   File
> "/opt/gnuradio/lib/python2.7/dist-packages/grc_gnuradio/wxgui/top_block_gui.py",
> line 76, in Run
>     self.start(max_nouts)
> TypeError: start() takes exactly 1 argument (2 given)
> 
> Is this feature broken?
> 

Yea, Its in the block config that can be set at the global config level
or the block level, or the port level.

https://github.com/guruofquality/gras/blob/master/include/gras/block_config.hpp

https://github.com/guruofquality/gras/blob/master/include/gras/top_block.hpp#L24

https://github.com/guruofquality/gras/blob/master/include/gras/block.hpp#L42

Its also available in the wrapper set set_max_noutput_items on the
blocks, it just didnt get into the second parameter for the run/start
API calls. I can add it...

Just curious... What are you trying to do at a high level? Constrain the
available buffer that a block can produce (without upstream consuming)?
Constrain the maximum number of items in a single call to work? etc..

-josh

> Thanks.
> --
> Regards, Devin
> 
> 
> 
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>