Sink that allows a sample to be grabbed from Python.
Constructor Specific Documentation:
Sink that allows a sample to be grabbed from Python.
Constructor Specific Documentation:
Sink that allows a sample to be grabbed from Python.
Constructor Specific Documentation:
Sink that allows a sample to be grabbed from Python.
Constructor Specific Documentation:
Sink that allows a sample to be grabbed from Python.
Constructor Specific Documentation:
Sink that allows a vector of samples to be grabbed from Python.
Constructor Specific Documentation:
Parameters: | size – |
---|
Sink that allows a vector of samples to be grabbed from Python.
Constructor Specific Documentation:
Parameters: | size – |
---|
Sink that allows a vector of samples to be grabbed from Python.
Constructor Specific Documentation:
Parameters: | size – |
---|
Sink that allows a vector of samples to be grabbed from Python.
Constructor Specific Documentation:
Parameters: | size – |
---|
Sink that allows a vector of samples to be grabbed from Python.
Constructor Specific Documentation:
Parameters: | size – |
---|
A ControlPort probe to export vectors of signals.
This block acts as a sink in the flowgraph but also exports vectors of complex samples over ControlPort. This block holds the latest number of complex samples so that every query by a ControlPort client will get the same length vector.
Constructor Specific Documentation:
Make a ControlPort probe block.
Parameters: |
|
---|
A ControlPort probe to export vectors of signals.
This block acts as a sink in the flowgraph but also exports vectors of complex samples over ControlPort. This block simply sends the current vector held in the work function when the queried by a ControlPort client.
Constructor Specific Documentation:
Make a ControlPort probe block.
Parameters: |
|
---|
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.
throughput measurement
Constructor Specific Documentation:
Make a throughput measurement block.
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.