Vector Sink: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
ThomasHabets (talk | contribs) m (correct syntax for Python 3) |
||
Line 7: | Line 7: | ||
time.sleep(10) | time.sleep(10) | ||
my_data = tb.my_vec_snk.data() | my_data = tb.my_vec_snk.data() | ||
print "data: ",my_data | print("data: ",my_data) | ||
To extract data from a running flow graph use the probe blocks. | To extract data from a running flow graph use the probe blocks. | ||
Line 13: | Line 13: | ||
time.sleep(10) | time.sleep(10) | ||
my_data = tb.my_probe_signal.level() | my_data = tb.my_probe_signal.level() | ||
print "data: ",my_data | print("data: ",my_data) | ||
== Parameters == | == Parameters == |
Latest revision as of 12:13, 26 October 2022
Stores stream to a vector, useful if you’re running for a short time, for example in a test. You can access that data using snk.data() after tb.run() has completed.
So something like:
tb.run() time.sleep(10) my_data = tb.my_vec_snk.data() print("data: ",my_data)
To extract data from a running flow graph use the probe blocks.
tb.start() time.sleep(10) my_data = tb.my_probe_signal.level() print("data: ",my_data)
Parameters
- Reserve Memory for Items
- Reserve space in the internal storage for this many items; the internal storage will still grow to accommodate more item if necessary, but setting this to a realistic value can avoid memory allocations during runtime, especially if you know a priori how many items you're going to store.
Example Flowgraph
Insert description of flowgraph here, then show a screenshot of the flowgraph and the output if there is an interesting GUI. Currently we have no standard method of uploading the actual flowgraph to the wiki or git repo, unfortunately. The plan is to have an example flowgraph showing how the block might be used, for every block, and the flowgraphs will live in the git repo.
Source Files
- C++ files
- TODO
- Header files
- TODO
- Public header files
- TODO
- Block definition
- TODO