Skip to content

Main content

Lowest Zero Bit Index Tool

Calculate lowest zero bit index from explicit caller-supplied inputs.

Loading tool…

Description

Return the least-significant zero-bit index.

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.

Return the least-significant zero-bit index.

When to use this tool

Use Lowest Zero Bit Index when checking the stated mask, field, parity or bit-index convention.

How to use the tool and how it works

  1. Enter wordDecimal, 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 found, index. Inspect found before interpreting the associated values.

Return the least-significant zero-bit index. Require width 1..256 and bounded exact wordDecimal; scan from index zero upward, return found and index or -1 when all bits are one.1

Input fieldMeaning and unitsAccepted input
wordDecimalWord DecimalRequired. Text; maximum UTF-16 length 8192. Integer syntax: optional + or - and 1-128 decimal digits; leading zeros accepted. Apply the sign restriction above.
widthWidth under the stated bit, interval or geometry convention; apply the field-specific units and bounds.Required. Safe integer; minimum 1; maximum 256.
Output fieldInterpretationReturned shape
foundFoundRequired. Boolean.
indexPosition under the explicit indexing convention; inspect any missing-value sentinel.Required. Safe integer.
json
{
  "input": {
    "wordDecimal": "11",
    "width": 4
  },
  "output": {
    "found": true,
    "index": 2
  }
}

Limitations and assumptions

  • Indexes are least-significant-first and ignore positions outside width; this is a bounded search, not complement arithmetic on an unbounded integer.
  • 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/lowest-zero-bit-index — tool.io

Similar or alternative tools