Description
Calculate channel-symbol rate from a supplied source rate and expansion factor.
Information quantities depend on the logarithm base, event model and symbol accounting. Bits, nats and hartleys are logarithmic units, while source symbols, channel symbols and header bits describe different counting bases. A local mass residual or expansion factor does not estimate entropy, independence or channel capacity from data.
Calculate channel-symbol rate from a supplied source rate and expansion factor.
When to use this tool
Use Source Channel Symbol Rate when you already have sourceSymbolsPerSecond, channelSymbolsPerSourceSymbol and need to calculate channel-symbol rate from a supplied source rate and expansion factor.
How to use the tool and how it works
- Enter sourceSymbolsPerSecond, channelSymbolsPerSourceSymbol. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read channelSymbolsPerSecond. Use the output convention below.
Require both inputs>=0; return sourceSymbolsPerSecond*channelSymbolsPerSourceSymbol.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| sourceSymbolsPerSecond | Source-symbol rate, not bits/s unless each source symbol is explicitly one bit. | Required. Finite number; minimum 0. |
| channelSymbolsPerSourceSymbol | Channel Symbols Per Source Symbol | Required. Finite number; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| channelSymbolsPerSecond | Channel Symbols Per Second | Required. Finite number. |
{
"input": {
"sourceSymbolsPerSecond": 100,
"channelSymbolsPerSourceSymbol": 2.5
},
"output": {
"channelSymbolsPerSecond": 250
}
} Limitations and assumptions
- The multiplier is channel symbols per source symbol, not bits per symbol; no code, entropy, capacity, reliability or actual channel is modeled.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Evaluate the full probability model, code and payload/header format when studying information or efficiency. Keep symbol and logarithm bases explicit; a unit conversion or one joint-mass reference term is only a local calculation.
References
Similar or alternative tools
- Information Unit One Bit Reference
Convert a supplied bit quantity to nats and hartleys.
- Coding Overhead Fixed Header Share
Calculate fixed-header share of supplied payload-plus-header bits.