Re: Does GRAS support setting max noutput items?

alcina · July 15, 2013, 11:36pm

Hi Josh,

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

Regards, Devin

----- Reply message -----
From: “Josh B.” [email protected]
To: [email protected]
Cc: [email protected]
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:

“/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.

github.com

guruofquality/gras/blob/master/include/gras/block_config.hpp

// Copyright (C) by Josh Blum. See LICENSE.txt for licensing information.

#ifndef INCLUDED_GRAS_BLOCK_CONFIG_HPP
#define INCLUDED_GRAS_BLOCK_CONFIG_HPP

#include <gras/gras.hpp>
#include <gras/thread_pool.hpp>
#include <cstddef>

namespace gras
{

//! Configuration parameters for a block
struct GRAS_API GlobalBlockConfig
{
    GlobalBlockConfig(void);

    /*!
     * Merge the settings from another config.
     * Non-defaults on this config stay,

This file has been truncated. show original

github.com

guruofquality/gras/blob/master/include/gras/top_block.hpp#L24


      
          
          
TopBlock(const std::string &name);
          
          
virtual ~TopBlock(void);
          
          
/*!
           * Commit changes to the global configuration.
           * Call this after modifying the global config.
           * Commit config is called automatically by start/stop/run.
           */
          void commit_config(void);
          
          
/*!
           * Commit changes to the overall flow graph.
           * Call this after modifying connections.
           * Commit is called automatically by start/stop/run.
           */
          void commit(void);
          
          
/*!
           * Run is for finite flow graph executions.

github.com

guruofquality/gras/blob/master/include/gras/block.hpp#L42


      
           ******************************************************************/
          
          
//! Get the configuration rules of an input port
          const InputPortConfig &input_config(const size_t which_input) const;
          
          
//! Get the configuration rules of an input port
          InputPortConfig &input_config(const size_t which_input);
          
          
//! Get the configuration rules of an output port
          const OutputPortConfig &output_config(const size_t which_output) const;
          
          
//! Get the configuration rules of an output port
          OutputPortConfig &output_config(const size_t which_output);
          
          
/*!
           * Commit changes to the port configuration.
           * Changes are commited automatically when the block becomes active.
           * However, once active, changes may not effect until commit_config().
           */
          void commit_config(void);

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

Re: Does GRAS support setting max noutput items?

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

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