Skip to content

Main content

Masked Bit Agreement Tool

Calculate masked bit agreement from explicit caller-supplied inputs.

Loading tool…

Description

Count agreement on selected bit positions.

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.

Count agreement on selected bit positions.

When to use this tool

Use Masked Bit Agreement when checking the stated mask, field, parity or bit-index convention.

How to use the tool and how it works

  1. Enter left, right, mask, width. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read agreeingBits, comparedBits, allAgree. Inspect allAgree before interpreting the associated values.

Count agreement on selected bit positions. Require width 1..52 and bounded nonnegative integer left/right/mask; comparedBits counts mask ones, agreeingBits counts equal corresponding bits, allAgree compares counts.1

Input fieldMeaning and unitsAccepted input
leftLeftRequired. Safe integer.
rightRightRequired. Safe integer.
maskMaskRequired. Safe integer.
widthWidth under the stated bit, interval or geometry convention; apply the field-specific units and bounds.Required. Safe integer; minimum 1; maximum 52.
Output fieldInterpretationReturned shape
agreeingBitsAgreeing BitsRequired. Safe integer.
comparedBitsCompared BitsRequired. Safe integer.
allAgreeTrue for an empty selected mask, with zero compared bits.Required. Boolean.
json
{
  "input": {
    "left": 10,
    "right": 14,
    "mask": 15,
    "width": 4
  },
  "output": {
    "agreeingBits": 3,
    "comparedBits": 4,
    "allAgree": false
  }
}

Limitations and assumptions

  • An empty mask returns allAgree true with zero comparisons; no full-word or semantic equality is implied.
  • 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

  1. Calculation and input contract: bitwise/masked-bit-agreement — tool.io

Similar or alternative tools