Bit String Hamming Position List

Return every differing position between equal-width bit strings, preserving Hamming witnesses rather than just a count.

Description

Return every differing position between equal-width bit strings, preserving Hamming witnesses rather than just a count.

A Hamming comparison can expose every differing position rather than only a distance count.

When to use this tool

Return every differing position between equal-width bit strings, preserving Hamming witnesses rather than just a count.

  • Prepare the supplied left, right fields for this operation.
  • Compare the complete example with the representation used by your own input before carrying the result into another step.

How to use the tool and how it works

  1. Enter left, right. Use the exact text syntax, units and index conventions explained below.
  2. Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
  3. Read result.positions. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.

Require equal-length binary strings and collect each zero-based index where left and right differ.1

Input fieldMeaning and representationAccepted input
leftleft.Binary text containing only 0 and 1; at most 128 characters
rightright.Binary text containing only 0 and 1; at most 128 characters
Output fieldInterpretation
resultObject containing the named outputs below.
result.positionsThe positions list in the ordering and representation described above.
json
{
  "input": {
    "left": "101",
    "right": "001"
  },
  "output": {
    "result": {
      "positions": [
        0
      ]
    }
  }
}

Limitations and assumptions

  • No alignment, insertion or deletion is attempted. Different input lengths are errors rather than compared with padding.
  • Every bitstring is at most 128 characters and contains only literal zero and one.
  • All declared input fields are required and unexpected top-level fields are rejected. Numbers must be finite; lists are limited to 128 entries and ordinary text fields to 8,192 UTF-16 code units, with tighter limits where stated.
  • JSON text inputs must parse within bounded nesting and size limits. Numeric outputs outside the safe finite range are rejected; large exact integer results use decimal strings. Indexes and half-open spans are zero-based unless a rank is explicitly described as one-based.

Alternative or Complementary methods

Choose a packed-integer or textual-bit representation deliberately before combining operations. Preserve the documented index direction, width and exclusive boundaries; do not substitute a rank query for select.

References

  1. Tool behavior and example: Bit String Hamming Position List — tool.io

Similar or alternative tools

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies