Description
Check a low-ones thermometer code and count adjacent bit transitions.
A fixed-width bit pattern and the number it represents are different concepts. Unsigned, two's-complement, one's-complement, sign-magnitude and biased encodings use different sign and zero conventions, so a bit-preserving transformation need not preserve numerical meaning.
Check a low-ones thermometer code and count adjacent bit transitions.
When to use this tool
Use Thermometer Code Transition Validity when checking the stated fixed-width representation or encoding convention.
How to use the tool and how it works
- Enter word, width. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read valid, transitions. Inspect valid before interpreting the associated values.
Check a low-ones thermometer code and count adjacent bit transitions. Require width 1..32 and bounded word; valid means word AND (word+1) is zero, transitions counts changes between neighboring positions within width.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| word | Word | Required. Safe integer; minimum 0. |
| width | Width under the stated bit, interval or geometry convention; apply the field-specific units and bounds. | Required. Safe integer; minimum 1; maximum 32. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| valid | Whether this local input/result condition holds; inspect the limitations before treating it as full validation. | Required. Boolean. |
| transitions | Transitions | Required. Safe integer. |
{
"input": {
"word": 15,
"width": 8
},
"output": {
"valid": true,
"transitions": 1
}
}Limitations and assumptions
- Zero and all-ones words are valid; a high-ones code can have one transition yet fail this low-ones convention.
- 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
Choose an explicit representation and width, validate the complete encoded value and use the matching signed or unsigned conversion for the intended numerical interpretation.
References
Similar or alternative tools
- Unary Code Stop Bit Index
Decode one unary-prefix run and its consumed length.
- Packed Decimal Invalid Nibble Mask
Return invalid packed-decimal nibble positions.