Streams and Vectors: Difference between revisions

From GNU Radio
Jump to navigation Jump to search
m (fixed tense)
 
(38 intermediate revisions by 2 users not shown)
Line 1: Line 1:
This tutorial will describe the difference between a ''Stream'' and a ''Vector''. You can find the previous tutorial here: [[Converting_Data_Types|Converting Data Types]]
<div style="float:right">
{{Template:BeginnerTutorials}}
</div>
This tutorial describes the differences between a ''Stream'' and a ''Vector''.
 
The previous tutorial, [[Packing_Bits|Packing Bits]], describes how to pack a stream of bits into the ''byte'' or ''char'' data type, and then unpack them back into a stream of bits. The next tutorial, [[Hier_Blocks_and_Parameters|Hier Blocks and Parameters]], demonstrates how to create a ''Hierarchical Block'' and using ''Parameters''.


== Streams ==
== Streams ==


''Streams'' in GNU Radio are what convey the information between blocks and are represented by the arrows connecting blocks in a flowgraph. A ''stream'' must have a data type, such as ''Float 32'' or ''Byte''. A ''stream'' carries 1 sample for each time instance and are used to represent and process serial data.
Blocks in GNU Radio can be connected using either ''streams'' or ''vectors''. A ''stream'' carries 1 sample for each time instance. A ''stream'' produces serialized data. A ''stream'' must have a data type, such as ''Float 32'' or ''Byte''.  


The ''Signal Source'' block produces a ''Complex Float 32'' stream. The output of the block at each time instance contains 1 complex sample:
The ''Signal Source'' block produces a ''Complex Float 32'' stream. The output of the block at each time instance contains 1 complex sample:
Line 9: Line 14:
[[File:SignalSourceStreamExample.png|700px]]
[[File:SignalSourceStreamExample.png|700px]]


The figure shows there is a single complex sample at each time instance.


== Vectors ==
== Vectors ==


''Vectors'' carry multiple samples per time instance, representing data in parallel. By analogy, a ''stream'' represents a scalar at each time instance whereas a vector represents an array at each time instance.
''Vectors'' carry multiple samples per time instance. ''Vectors'' represent data in parallel. A ''stream'' represents a scalar at each time instance. A ''vector'' represents an array at each time instance.


GRC uses lighter colors to represent ''streams'' and darker colors to represent ''vector'' outputs:
GRC uses lighter colors to represent ''streams'' and darker colors to represent ''vector'' outputs:


[[File:StreamVectorDarkerColors.png|600px]]
[[File:StreamVectorDarkerColors.png|600px]]


== Streams to Vector Flowgraph Example ==
== Streams to Vector Flowgraph Example ==


The following example will describe how to convert a stream to a vector and back to a stream. Two complex sinusoid streams will be converted to a 2-element vector, displayed, and then converted back to their independent streams.
The following example describes how to convert a stream to a vector and back to a stream. Two complex sinusoid streams are converted to a 2-element vector, displayed, and then converted back to their two independent streams.


Add two ''Signal Source'' blocks to the workspace:
Add two ''Signal Source'' blocks to the workspace:
Line 38: Line 43:
[[File:ConnectStreamsToVector.png|700px]]
[[File:ConnectStreamsToVector.png|700px]]


The ''Streams to Vector'' block acts as an interleaver, taking the two serial ''stream'' inputs and converting them to a two-dimensional ''vector'' output. The block takes the sample from the ''in0'' port and places it into the first element in the output ''vector'', and then takes the a sample from the ''in1'' port and places into the second element in the ''vector''.
The ''Streams to Vector'' block acts as an interleaver. The ''Streams to Vector'' block takes a sample from the ''in0'' port and places it into the first element in the output ''vector''. The ''Streams to Vector'' block takes a sample from the ''in1'' port and places it into the second element in the output ''vector''. The ''Streams to Vector'' block combines two serial ''stream'' inputs into a two-dimensional ''vector'' output.


Search for the ''Vector to Stream'' block which will serialize the vector data, and then add three ''QT GUI Time Sink'' blocks:
Search for the ''Vector to Stream'' block and add three ''QT GUI Time Sink'' blocks to the flowgraph:


[[File:InterleavedSignalSourceWithTimeSinks.png|700px]]
[[File:InterleavedSignalSourceWithTimeSinks.png|700px]]
The ''Vector to Stream'' block will serialize the vector into a stream. The samples at the output of ''Vector to Stream'' will be interleaved.




Line 66: Line 73:




Running the flowgraph will now display three time sinks, ''Signal Source A'', ''Signal Source B'', and ''Interleaved Signal Sources''. Note that the ''Interleaved Signal Sources'' time sink displays interleaved samples from ''Signal Source A'' and ''Signal Source B'':
Running the flowgraph displays three time sinks, ''Signal Source A'', ''Signal Source B'', and ''Interleaved Signal Sources''. The ''Interleaved Signal Sources'' time sink displays interleaved samples from ''Signal Source A'' and ''Signal Source B'':


[[File:TimeSinkSignalSources.png|700px]]
[[File:TimeSinkSignalSources.png|700px]]


== Vector to Streams Flowgraph Example ==
The following example deinterleaves (or serializes) the vectorized data, converting it back into two streams.
Search for the ''Vector to Streams'' block, add it to the workspace, and connect it to the ''Streams to Vector'' block:
[[File:AddVectorToStreamsBlock.png|700px]]
The ''Vector to Streams'' block deserializes vector samples and converts them into streams, performing the inverse operation to the ''Streams to Vector'' block.
Right-click and delete the arrows connecting the two ''Signal Source'' blocks to the ''QT GUI Time Sink'' blocks:
[[File:DeleteTimeSinks.png|700px]]
Move and reconnect the two ''QT GUI Time Sink'' blocks to the ''Vector to Streams'' outputs:
[[File:ReconnectedTimeSinks.png|700px]]


== Vector to Streams Flowgraph Example ==


The following example will now deinterleave the vectorized data and convert it back into two streams. First, delete the two ''QT GUI Time Sink'' blocks connected to the ''Signal Sources'':
Run the flowgraph. The vectorized samples have been separated back into two streams:


[[File:DeleteTimeSinks.png|500px]]
[[File:DeserializedTimeSink.png|700px]]


The flowgraph is now simplified:


[[File:SimplifiedFlowgraphVectorToStreams.png|700px]]
The next tutorial, [[Hier_Blocks_and_Parameters|Hier Blocks and Parameters]], demonstrates how to create a ''Hierarchical Block'' and use ''Parameters''.

Latest revision as of 10:18, 17 January 2023

Beginner Tutorials

Introducing GNU Radio

  1. What is GNU Radio?
  2. Installing GNU Radio
  3. Your First Flowgraph

Flowgraph Fundamentals

  1. Python Variables in GRC
  2. Variables in Flowgraphs
  3. Runtime Updating Variables
  4. Signal Data Types
  5. Converting Data Types
  6. Packing Bits
  7. Streams and Vectors
  8. Hier Blocks and Parameters

Creating and Modifying Python Blocks

  1. Creating Your First Block
  2. Python Block With Vectors
  3. Python Block Message Passing
  4. Python Block Tags

DSP Blocks

  1. Low Pass Filter Example
  2. Designing Filter Taps
  3. Sample Rate Change
  4. Frequency Shifting
  5. Reading and Writing Binary Files

SDR Hardware

  1. RTL-SDR FM Receiver
  2. B200-B205mini FM Receiver

This tutorial describes the differences between a Stream and a Vector.

The previous tutorial, Packing Bits, describes how to pack a stream of bits into the byte or char data type, and then unpack them back into a stream of bits. The next tutorial, Hier Blocks and Parameters, demonstrates how to create a Hierarchical Block and using Parameters.

Streams

Blocks in GNU Radio can be connected using either streams or vectors. A stream carries 1 sample for each time instance. A stream produces serialized data. A stream must have a data type, such as Float 32 or Byte.

The Signal Source block produces a Complex Float 32 stream. The output of the block at each time instance contains 1 complex sample:

SignalSourceStreamExample.png

The figure shows there is a single complex sample at each time instance.

Vectors

Vectors carry multiple samples per time instance. Vectors represent data in parallel. A stream represents a scalar at each time instance. A vector represents an array at each time instance.

GRC uses lighter colors to represent streams and darker colors to represent vector outputs:

StreamVectorDarkerColors.png

Streams to Vector Flowgraph Example

The following example describes how to convert a stream to a vector and back to a stream. Two complex sinusoid streams are converted to a 2-element vector, displayed, and then converted back to their two independent streams.

Add two Signal Source blocks to the workspace:

TwoSignalSourceBlocks.png


Edit the parameters of the second Signal Source to have a frequency of 100 and amplitude of 0.1 to distinguish it visually from the first Signal Source:

ChangeFrequencyAmplitudeSignalSource.png

Click OK to accept the parameters.

Search for the Streams to Vector block, drag it into the workspace and connect it to the Signal Source blocks:

ConnectStreamsToVector.png

The Streams to Vector block acts as an interleaver. The Streams to Vector block takes a sample from the in0 port and places it into the first element in the output vector. The Streams to Vector block takes a sample from the in1 port and places it into the second element in the output vector. The Streams to Vector block combines two serial stream inputs into a two-dimensional vector output.

Search for the Vector to Stream block and add three QT GUI Time Sink blocks to the flowgraph:

InterleavedSignalSourceWithTimeSinks.png

The Vector to Stream block will serialize the vector into a stream. The samples at the output of Vector to Stream will be interleaved.


Edit the titles for the three QT GUI Time Sink blocks so the can be distinguished from one another. First, edit the block connected to the Signal Source with frequency 1000 and amplitude 1 to have the title Signal Source A:

TimeSinkAProperty.png

SignalSourceATimeSink.png


Now edit the QT GUI Time Sink connected to the second Signal Source with frequency 100 and Amplitude 0.1 to have the title Signal Source B:

TimeSinkBProperty.png

SignalSourceBTimeSink.png


Finally, edit the QT GUI Time Sink connected to the Vector to Stream block to have the title Interleaved Signal Sources:

TimeSinkInterleavedProperty.png

InterleavedSignalSourceTimeSink.png


Running the flowgraph displays three time sinks, Signal Source A, Signal Source B, and Interleaved Signal Sources. The Interleaved Signal Sources time sink displays interleaved samples from Signal Source A and Signal Source B:

TimeSinkSignalSources.png

Vector to Streams Flowgraph Example

The following example deinterleaves (or serializes) the vectorized data, converting it back into two streams.

Search for the Vector to Streams block, add it to the workspace, and connect it to the Streams to Vector block:

AddVectorToStreamsBlock.png


The Vector to Streams block deserializes vector samples and converts them into streams, performing the inverse operation to the Streams to Vector block.

Right-click and delete the arrows connecting the two Signal Source blocks to the QT GUI Time Sink blocks:

DeleteTimeSinks.png


Move and reconnect the two QT GUI Time Sink blocks to the Vector to Streams outputs:

ReconnectedTimeSinks.png


Run the flowgraph. The vectorized samples have been separated back into two streams:

DeserializedTimeSink.png


The next tutorial, Hier Blocks and Parameters, demonstrates how to create a Hierarchical Block and use Parameters.

Retrieved from "https://wiki.gnuradio.org/index.php?title=Streams_and_Vectors&oldid=12854"