Struct frame_check_t¶
What frame_check found, summed across the stages it reversed.More...
#include <frame_core.h>
Public Attributes¶
| Type | Name |
|---|---|
| uint32_t | checked |
| uint32_t | corrected |
| uint32_t | ok |
| int | passed |
| uint32_t | stages |
| uint32_t | symbols |
| uint32_t | units |
Detailed Description¶
One record rather than one per stage, because a caller doing frame accounting wants a verdict and a cost. units and ok count CHECKS — one for a CRC, one per codeword for an interleaved outer code — so ok == units is the verdict and symbols is what it cost to get there.
corrected and symbols are the honest measure of how hard a link is running: ok == units with a rising symbols is margin being spent, and it is spent before it is lost. A CRC cannot report that at all, which is why an outer code is a strictly better detector and not merely a stronger one.
Public Attributes Documentation¶
variable checked¶
how many were reversed HERE (see below)
variable corrected¶
how many needed and received repair
variable ok¶
how many came out good
variable passed¶
every check good: 1 yes, 0 no. passed, not pass: the obvious name is a Python keyword
variable stages¶
stages in the description
variable symbols¶
symbol errors repaired
variable units¶
checks performed across them
The documentation for this class was generated from the following file native/inc/frame/frame_core.h