Bit String Select One Query
Select a zero-based occurrence of bit 1 in an explicit bit string; null denotes an occurrence beyond the observed count.
Description
Select a zero-based occurrence of bit 1 in an explicit bit string; null denotes an occurrence beyond the observed count.
A select-one query maps an occurrence number to a set-bit position.
When to use this tool
Select a zero-based occurrence of bit 1 in an explicit bit string; null denotes an occurrence beyond the observed count.
- Prepare the supplied bits, occurrence 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
- Enter bits, occurrence. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.position. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
List one positions in left-to-right order and return the entry at the zero-based occurrence index from 0 to 128, or null when absent.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| bits | bits. | Binary text containing only 0 and 1; at most 128 characters |
| occurrence | occurrence. | Integer from 0 to 128 inclusive |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.position | Zero-based matching position, or null when the requested match is absent. |
{
"input": {
"bits": "10100",
"occurrence": 1
},
"output": {
"result": {
"position": 2
}
}
} Limitations and assumptions
- Occurrence numbering begins at zero. No numeric low-bit-first convention is used.
- 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
Similar or alternative tools
- Bit String Rank One Query
Count 1 bits in the half-open prefix before an explicit endpoint; rank excludes the endpoint position itself.
- Bit String Select Zero Query
Select a zero-based occurrence of bit 0 in an explicit bit string; null denotes an occurrence beyond the observed count.