Description
Check whether two words differ in exactly one bit.
Bit positions are usually counted from the least-significant bit, while a displayed binary string has its own left-to-right indexing convention. Masks, fields and parity predicates describe a selected region or pattern; local agreement does not validate a complete encoded record.
Check whether two words differ in exactly one bit.
When to use this tool
Use Gray Code Single Transition Bit Index when checking the stated mask, field, parity or bit-index convention.
How to use the tool and how it works
- Enter left, right, width. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read singleTransition, bitIndex. Inspect singleTransition before interpreting the associated values.
Check whether two words differ in exactly one bit. Require width 1..128 and bounded exact operands; XOR nonzero with a single set bit gives singleTransition true and its least-significant-based bitIndex, otherwise -1.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| left | Left | Required. Text; maximum UTF-16 length 8192. Integer syntax: optional + or - and 1-128 decimal digits; leading zeros accepted. Apply the sign restriction above. |
| right | Right | Required. Text; maximum UTF-16 length 8192. Integer syntax: optional + or - and 1-128 decimal digits; leading zeros accepted. Apply the sign restriction above. |
| width | Width under the stated bit, interval or geometry convention; apply the field-specific units and bounds. | Required. Safe integer; minimum 1; maximum 128. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| singleTransition | Single Transition | Required. Boolean. |
| bitIndex | Bit Index | Required. Safe integer. |
{
"input": {
"left": "3",
"right": "2",
"width": 4
},
"output": {
"singleTransition": true,
"bitIndex": 0
}
}Limitations and assumptions
- Equal words are not a single transition; this tests one pair, not a valid ordered Gray-code sequence.
- 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 bit order, word width and missing-position policy; use the complete record format and appropriate parsing or checksum methods for full validation.
References
Similar or alternative tools
- Lowest Zero Bit Index
Return the least-significant zero-bit index.
- Bit Word Leading Transition Position
Locate the first transition in written binary text.