Occurrence Index Buckets
Bucket occurrence indexes by exact string value in first-occurrence order without losing duplicates.
Description
Bucket occurrence indexes by exact string value in first-occurrence order without losing duplicates.
Occurrence buckets collect every source position for each repeated value. They retain ordering evidence that a simple frequency count would lose.
When to use this tool
Bucket occurrence indexes by exact string value in first-occurrence order without losing duplicates.
- Prepare the supplied values 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 values. 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.buckets. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Scan values in input order using a Map. Return one bucket per distinct value in first-seen order, with its complete ascending index list.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| values | values. | At most 128 strings, each at most 128 UTF-16 code units |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.buckets | The buckets list in the ordering and representation described above. |
{
"input": {
"values": [
"a",
"b",
"a"
]
},
"output": {
"result": {
"buckets": [
{
"value": "a",
"indexes": [
0,
2
]
},
{
"value": "b",
"indexes": [
1
]
}
]
}
}
}Limitations and assumptions
- Comparison follows the supplied scalar/string list representation and exact key equality. Buckets do not reorder the source list or merge similar spellings.
- Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
- Ordinary string lists have at most 128 entries of at most 128 code units each; numeric lists and matrices have separate bounded size checks. Nonfinite results and excessively large serialized outputs are rejected.
- Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.
Alternative or Complementary methods
Use explicit source-index maps when rearranging data or planning missing-value fills. Keep row-major coordinates, cyclic indexes and one-based occurrence numbers distinct, and inspect null donor positions before copying values.
References
Similar or alternative tools
- Stable Occurrence Numbering
Assign stable one-based occurrence numbers independently for each exact supplied string.
- Adjacent Change Indexes
Return indexes whose value differs from the previous supplied string, not CSS change hints or a value transform.