Decode CCSDS 27: Difference between revisions
(Created page with "Category:Block Docs Category:Stub Docs This is the template for the "Page-per-block Docs". This first section should describe what the block...") |
No edit summary |
||
Line 1: | Line 1: | ||
[[Category:Block Docs]] | [[Category:Block Docs]] | ||
A rate 1/2, k=7 convolutional decoder for the CCSDS standard. | |||
This block performs soft-decision convolutional decoding using the Viterbi algorithm. The input is a stream of (possibly noise corrupted) floating point values nominally spanning [-1.0, 1.0], representing the encoded channel symbols 0 (-1.0) and 1 (1.0), with erased symbols at 0.0. | |||
The output is MSB first packed bytes of decoded values. | |||
As a rate 1/2 code, there will be one output byte for every 16 input symbols. | |||
This block is designed for continuous data streaming, not packetized data. The first 32 bits out will be zeroes, with the output delayed four bytes from the corresponding inputs. | |||
== Parameters == | == Parameters == | ||
None | |||
== Example Flowgraph == | == Example Flowgraph == |
Latest revision as of 00:03, 18 August 2019
A rate 1/2, k=7 convolutional decoder for the CCSDS standard.
This block performs soft-decision convolutional decoding using the Viterbi algorithm. The input is a stream of (possibly noise corrupted) floating point values nominally spanning [-1.0, 1.0], representing the encoded channel symbols 0 (-1.0) and 1 (1.0), with erased symbols at 0.0.
The output is MSB first packed bytes of decoded values. As a rate 1/2 code, there will be one output byte for every 16 input symbols. This block is designed for continuous data streaming, not packetized data. The first 32 bits out will be zeroes, with the output delayed four bytes from the corresponding inputs.
Parameters
None
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