GNU Radio 3.6.5 C++ API

gr::blocks::tagged_stream_mux_impl Class Reference

#include <tagged_stream_mux_impl.h>

Inheritance diagram for gr::blocks::tagged_stream_mux_impl:
gr::blocks::tagged_stream_mux gr_tagged_stream_block gr_block gr_basic_block gr_msg_accepter gruel::msg_accepter

List of all members.

Public Member Functions

 tagged_stream_mux_impl (size_t itemsize, const std::string &lengthtagname)
 ~tagged_stream_mux_impl ()
int work (int noutput_items, gr_vector_int &ninput_items, gr_vector_const_void_star &input_items, gr_vector_void_star &output_items)
 Just like gr_block::general_work, but makes sure the input is valid.

Protected Member Functions

int calculate_output_stream_length (const std::vector< int > &ninput_items)
 Calculate the number of output items.

Constructor & Destructor Documentation

gr::blocks::tagged_stream_mux_impl::tagged_stream_mux_impl ( size_t  itemsize,
const std::string &  lengthtagname 
)
gr::blocks::tagged_stream_mux_impl::~tagged_stream_mux_impl ( )

Member Function Documentation

int gr::blocks::tagged_stream_mux_impl::calculate_output_stream_length ( const std::vector< int > &  ninput_items) [protected, virtual]

Calculate the number of output items.

This is basically the inverse function to forecast(): Given a number of input items, it returns the maximum number of output items.

You most likely need to override this function, unless your block is a sync block or integer interpolator/decimator.

Reimplemented from gr_tagged_stream_block.

int gr::blocks::tagged_stream_mux_impl::work ( int  noutput_items,
gr_vector_int ninput_items,
gr_vector_const_void_star input_items,
gr_vector_void_star output_items 
) [virtual]

Just like gr_block::general_work, but makes sure the input is valid.

The user must override work to define the signal processing code. Check the documentation for general_work() to see what happens here.

Like gr_sync_block, this calls consume() for you (it consumes ninput_items[i] items from the i-th port).

A note on tag propagation: The PDU length tags are handled by other functions, but all other tags are handled just as in any other gr_block. So, most likely, you either set the tag propagation policy to TPP_DONT and handle the tag propagation manually, or you propagate tags through the scheduler and don't do anything here.

Parameters:
noutput_itemsThe size of the writable output buffer
ninput_itemsThe exact size of the items on every input for this particular PDU. These will be consumed if a length tag key is provided!
input_itemsSee gr_block
output_itemsSee gr_block

Implements gr_tagged_stream_block.


The documentation for this class was generated from the following file: