Edge List Parallel Edge Buckets
Inventory parallel edge occurrences with exact directed or undirected endpoint equivalence; retain multiplicities rather than normalize away duplicates.
Description
Inventory parallel edge occurrences with exact directed or undirected endpoint equivalence; retain multiplicities rather than normalize away duplicates.
Parallel-edge buckets depend on whether direction matters. Edge identity and weight are separate from that grouping.
When to use this tool
Inventory parallel edge occurrences with exact directed or undirected endpoint equivalence; retain multiplicities rather than normalize away duplicates.
- Prepare the supplied edgesJson, directed 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 edgesJson, directed. 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.
Group by ordered source/target strings when directed, otherwise by the lexically sorted endpoint pair. Return groups with more than one record, including their indexes.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| edgesJson | JSON text, entered as one text field. The decoded structure is illustrated below; it is not a separate file. | Text |
| directed | Explicit choice for directed; supply a boolean rather than a text label. | true or false |
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": "edgesJson",
"decoded": [
{
"id": "a",
"source": "u",
"target": "v",
"weight": 2
},
{
"id": "b",
"source": "v",
"target": "u",
"weight": 4
},
{
"id": "c",
"source": "u",
"target": "u",
"weight": 1
}
]
}
]| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.buckets | The buckets list in the ordering and representation described above. |
{
"input": {
"edgesJson": "[{\"id\":\"a\",\"source\":\"u\",\"target\":\"v\",\"weight\":2},{\"id\":\"b\",\"source\":\"v\",\"target\":\"u\",\"weight\":4},{\"id\":\"c\",\"source\":\"u\",\"target\":\"u\",\"weight\":1}]",
"directed": false
},
"output": {
"result": {
"buckets": [
{
"key": "[\"u\",\"v\"]",
"indexes": [
0,
1
]
}
]
}
}
}Limitations and assumptions
- Loops can form parallel buckets too. No records are merged and different weights do not separate a bucket.
- Every edge record requires unique string id, string source/target and finite numeric weight, even when this operation does not use the weight. Parallel endpoints and loops are retained unless explicitly filtered.
- 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
Choose edge identities, directedness and vertex coverage explicitly. Local edge-list audits and transformations do not replace a graph algorithm with the required connectivity, path or ordering guarantees.
References
Similar or alternative tools
- Edge ID Trail Validity Check
Verify an edge-ID trail with no repeated edge occurrences from an explicit start; directed or undirected traversal, with failure indexes retained.
- Edge List Boundary Cut Selector
Select edges crossing an explicit vertex-set boundary using endpoint exclusive membership; direction and occurrence IDs remain intact.