-
Notifications
You must be signed in to change notification settings - Fork 2
Reordering Figure Catalog
Every strip uses the same measured 9-vertex input and the same converter binary. The shared input is shown once; each algorithm then shows only its measured output order and the mechanism that produced it.
Shared-example contract. All 17 outputs preserve the same nine vertices and twelve undirected edges. The blue-outlined cell is the vertex with the largest displacement in that measured output.
Converter SHA256: 70580d71854e222d299c488274feced6cdd8005667bc87b07fc326c3d6fc5d41.
Capture receipt with commands, mapping fingerprints, and raw stdout tails.
Re-capture and regenerate:
python3 scripts/generate_public_figures.py --capture-catalog
python3 scripts/generate_public_figures.py --checkDownload the generated 18-page draw.io bundle.
On a narrow screen, select any figure to open the full-resolution SVG.
-
CLI:
0 - Mechanism: Identity permutation.
- Evidence: output order captured from the shared example
Figure. Topology and memory order are identical.
-
CLI:
1 - Mechanism: Fixed seed-0 shuffle.
- Evidence: output order captured from the shared example
Figure. Only labels change; the topology is fixed.
-
CLI:
2 - Mechanism: Global degree sort.
- Evidence: output order captured from the shared example
Figure. High-degree vertices move toward the first memory region.
-
CLI:
3 - Mechanism: Sort selected hubs.
- Evidence: output order captured from the shared example
Figure. Only the hub region receives a full degree sort.
-
CLI:
4 - Mechanism: Stable hub clustering.
- Evidence: output order captured from the shared example
Figure. The hub/non-hub split changes regions without sorting every vertex.
-
CLI:
5 - Mechanism: Degree buckets.
- Evidence: output order captured from the shared example
Figure. Bucket boundaries, not one global sort, define the output.
-
CLI:
6 - Mechanism: HubSort + buckets.
- Evidence: output order captured from the shared example
Figure. A sorted hub bucket is followed by grouped non-hubs.
-
CLI:
7 - Mechanism: Stable hub/non-hub buckets.
- Evidence: output order captured from the shared example
Figure. Both regions preserve encounter order.
-
CLI:
8:csr - Mechanism: Community merge + DFS.
- Evidence: output order captured from the shared example
Figure. Community blocks become contiguous; DFS chooses hierarchy order.
-
CLI:
9:csr - Mechanism: Standalone GORDER_csr.
- Evidence: output order captured from the shared example
Figure. This is distinct from GraphBrew's relaxed local intra_gorder.
-
CLI:
10:canonical - Mechanism: Canonical hot/cold.
- Evidence: output order captured from the shared example
Figure. The workload segmentation defines the memory regions.
-
CLI:
11:bnf - Mechanism: BNF + RCM.
- Evidence: output order captured from the shared example
Figure. The output targets lower graph bandwidth.
-
CLI:
12:leiden:compose:sg_none:comm_size_desc:intra_gorder:gw8:gordf4:cd_serial:refine_none - Mechanism: Explicit three-axis compose.
- Evidence: output order captured from the shared example
Figure. GraphBrew emits one explicit composition, not a competitor fallback.
-
CLI:
13:graphbrew-running-example.lo - Mechanism: External label list.
- Evidence: output order captured from the shared example
Figure. MAP materializes a supplied order; it does not discover one.
-
CLI:
14:<policy> - Mechanism: Policy-selected arm.
- Evidence: selected-arm illustration; AdaptiveOrder has no fixed permutation
Figure. The output shown is the selected GraphBrew arm for this illustration.
-
CLI:
15 - Mechanism: Leiden + post-layout.
- Evidence: output order captured from the shared example
Figure. Community detection alone is not an ordering.
-
CLI:
16 - Mechanism: Directed forward-edge.
- Evidence: output order captured from the shared example
Figure. The objective is directed; the shown order is measured on this edge list.