Skip to content

Reordering Figure Catalog

Abdullah edited this page Aug 23, 2026 · 4 revisions

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 catalog input

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 --check

Download the generated 18-page draw.io bundle.

On a narrow screen, select any figure to open the full-resolution SVG.

Baselines

0. ORIGINAL

  • CLI: 0
  • Mechanism: Identity permutation.
  • Evidence: output order captured from the shared example

ORIGINAL measured output

Figure. Topology and memory order are identical.

Editable draw.io source.

1. RANDOM

  • CLI: 1
  • Mechanism: Fixed seed-0 shuffle.
  • Evidence: output order captured from the shared example

RANDOM measured output

Figure. Only labels change; the topology is fixed.

Editable draw.io source.

Degree and bucket layouts

2. SORT

  • CLI: 2
  • Mechanism: Global degree sort.
  • Evidence: output order captured from the shared example

SORT measured output

Figure. High-degree vertices move toward the first memory region.

Editable draw.io source.

3. HUBSORT

  • CLI: 3
  • Mechanism: Sort selected hubs.
  • Evidence: output order captured from the shared example

HUBSORT measured output

Figure. Only the hub region receives a full degree sort.

Editable draw.io source.

4. HUBCLUSTER

  • CLI: 4
  • Mechanism: Stable hub clustering.
  • Evidence: output order captured from the shared example

HUBCLUSTER measured output

Figure. The hub/non-hub split changes regions without sorting every vertex.

Editable draw.io source.

5. DBG

  • CLI: 5
  • Mechanism: Degree buckets.
  • Evidence: output order captured from the shared example

DBG measured output

Figure. Bucket boundaries, not one global sort, define the output.

Editable draw.io source.

6. HUBSORTDBG

  • CLI: 6
  • Mechanism: HubSort + buckets.
  • Evidence: output order captured from the shared example

HUBSORTDBG measured output

Figure. A sorted hub bucket is followed by grouped non-hubs.

Editable draw.io source.

7. HUBCLUSTERDBG

  • CLI: 7
  • Mechanism: Stable hub/non-hub buckets.
  • Evidence: output order captured from the shared example

HUBCLUSTERDBG measured output

Figure. Both regions preserve encounter order.

Editable draw.io source.

Community and locality layouts

8. RABBITORDER

  • CLI: 8:csr
  • Mechanism: Community merge + DFS.
  • Evidence: output order captured from the shared example

RABBITORDER measured output

Figure. Community blocks become contiguous; DFS chooses hierarchy order.

Editable draw.io source.

9. GORDER

  • CLI: 9:csr
  • Mechanism: Standalone GORDER_csr.
  • Evidence: output order captured from the shared example

GORDER measured output

Figure. This is distinct from GraphBrew's relaxed local intra_gorder.

Editable draw.io source.

10. CORDER

  • CLI: 10:canonical
  • Mechanism: Canonical hot/cold.
  • Evidence: output order captured from the shared example

CORDER measured output

Figure. The workload segmentation defines the memory regions.

Editable draw.io source.

11. RCM

  • CLI: 11:bnf
  • Mechanism: BNF + RCM.
  • Evidence: output order captured from the shared example

RCM measured output

Figure. The output targets lower graph bandwidth.

Editable draw.io source.

12. GraphBrewOrder

  • 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

GraphBrewOrder measured output

Figure. GraphBrew emits one explicit composition, not a competitor fallback.

Editable draw.io source.

External and selected layouts

13. MAP

  • CLI: 13:graphbrew-running-example.lo
  • Mechanism: External label list.
  • Evidence: output order captured from the shared example

MAP measured output

Figure. MAP materializes a supplied order; it does not discover one.

Editable draw.io source.

14. AdaptiveOrder

  • CLI: 14:<policy>
  • Mechanism: Policy-selected arm.
  • Evidence: selected-arm illustration; AdaptiveOrder has no fixed permutation

AdaptiveOrder measured output

Figure. The output shown is the selected GraphBrew arm for this illustration.

Editable draw.io source.

15. LeidenOrder

  • CLI: 15
  • Mechanism: Leiden + post-layout.
  • Evidence: output order captured from the shared example

LeidenOrder measured output

Figure. Community detection alone is not an ordering.

Editable draw.io source.

Directed layout

16. GoGraphOrder

  • CLI: 16
  • Mechanism: Directed forward-edge.
  • Evidence: output order captured from the shared example

GoGraphOrder measured output

Figure. The objective is directed; the shown order is measured on this edge list.

Editable draw.io source.

Clone this wiki locally