unsigned char sink that writes to a vector
Constructor Specific Documentation:
Parameters: | vlen – |
---|
gr_complex sink that writes to a vector
Constructor Specific Documentation:
Parameters: | vlen – |
---|
float sink that writes to a vector
Constructor Specific Documentation:
Parameters: | vlen – |
---|
int sink that writes to a vector
Constructor Specific Documentation:
Parameters: | vlen – |
---|
short sink that writes to a vector
Constructor Specific Documentation:
Parameters: | vlen – |
---|
1-to-1 stream annotator testing block. FOR TESTING PURPOSES ONLY.
This block creates tags to be sent downstream every 10,000 items it sees. The tags contain the name and ID of the instantiated block, use “seq” as a key, and have a counter that increments by 1 for every tag produced that is used as the tag’s value. The tags are propagated using the 1-to-1 policy.
It also stores a copy of all tags it sees flow past it. These tags can be recalled externally with the data() member.
Warning
This block is only meant for testing and showing how to use the tags.
Constructor Specific Documentation:
Parameters: |
|
---|
All-to-all stream annotator testing block. FOR TESTING PURPOSES ONLY.
This block creates tags to be sent downstream every 10,000 items it sees. The tags contain the name and ID of the instantiated block, use “seq” as a key, and have a counter that increments by 1 for every tag produced that is used as the tag’s value. The tags are propagated using the all-to-all policy.
It also stores a copy of all tags it sees flow past it. These tags can be recalled externally with the data() member.
This block is only meant for testing and showing how to use the tags.
Constructor Specific Documentation:
Parameters: |
|
---|
raw stream annotator testing block.
This block creates arbitrary tags to be sent downstream gnuradio/blocks to be sent are set manually via accessor methods and are sent only once.
This block is intended for testing of tag related gnuradio/blocks
Constructor Specific Documentation:
Parameters: | sizeof_stream_item – |
---|
Debug block for the message passing system.
The message debug block is used to capture and print or store messages as they are received. Any block that generates a message may connect that message port to one or more of the three message input ports of this debug block. The message ports are:
Constructor Specific Documentation:
Build the message debug block. It takes no parameters and has three message ports: print, store, and print_pdu.
Get a message (as a PMT) from the message vector at index .
Messages passed to the ‘store’ port will be stored in a vector. This function retrieves those messages by index. They are index in order of when they were received (all messages are just pushed onto the back of a vector). This is mostly useful in debugging message passing graphs and in QA code.
Reports the number of messages received by this block.
Sends a random PDU at intervals.
Constructor Specific Documentation:
Construct a random PDU generator.
Parameters: |
|
---|
Bit bucket that prints out any tag received.
This block collects all tags sent to it on all input ports and displays them to stdout in a formatted way. The parameter is used to identify which debug sink generated the tag, so when connecting a block to this debug sink, an appropriate name is something that identifies the input block.
This block otherwise acts as a NULL sink in that items from the input stream are ignored. It is designed to be able to attach to any block and watch all tags streaming out of that block for debugging purposes.
The tags from the last call to this work function are stored and can be retrieved using the function ‘current_tags’.
Constructor Specific Documentation:
Build a tag debug block
Parameters: |
|
---|
Returns a vector of tag_t items as of the last call to work.
Set the display of tags to stdout on/off.