Multiset Count Table Expander
Expand normalized typed multiplicity rows into a bounded occurrence list, preserving first key appearance order.
Description
Expand normalized typed multiplicity rows into a bounded occurrence list, preserving first key appearance order.
Expanding a count table produces repeated scalar values but cannot recover their original interleaving.
When to use this tool
Expand normalized typed multiplicity rows into a bounded occurrence list, preserving first key appearance order.
- Prepare the supplied countsJson 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 countsJson. 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.values. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Normalize countsJson, require total count at most 128 and emit each value repeated its aggregated count, grouped in normalized key order.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| countsJson | JSON text, entered as one text field. The decoded structure is illustrated below; it is not a separate file. | Text |
For the JSON text fields, the following decoded structures show the example records before they are serialized into input strings. Keep field names, list nesting and value types as shown.
[
{
"field": "countsJson",
"decoded": [
{
"value": 1,
"count": 2
},
{
"value": "a",
"count": 1
}
]
}
]| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.values | The values list in the ordering and representation described above. |
{
"input": {
"countsJson": "[{\"value\":1,\"count\":2},{\"value\":\"a\",\"count\":1}]"
},
"output": {
"result": {
"values": [
1,
1,
"a"
]
}
}
}Limitations and assumptions
- Inputs exceeding the expansion budget are rejected. The resulting sequence is grouped by value, not reconstructed source order.
- Count records contain a scalar JSON value and an integer count from zero to one million. Duplicate typed values aggregate up to one million per input key and zero aggregates are omitted.
- 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.
- Lists are limited to 128 entries. JSON text must meet bounded size and depth checks, and numeric outputs beyond the safe finite magnitude are rejected. Exact large integers use decimal strings.
- 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
Keep count-table arithmetic separate from occurrence ordering and persistent inventory changes. Choose minimum intersection, maximum union or additive sum explicitly, and retain scalar types when matching values.
References
Similar or alternative tools
- Multiset Count Table Normalizer
Normalize typed scalar count rows by exact identity, summing duplicates and dropping zeros; counts must be nonnegative integers.
- Multiset Absolute Multiplicity Difference
Compute typed multiset absolute multiplicity difference from exact scalar identities and nonnegative integer counts; duplicate count rows are summed.