osage cluster packing

Engine

osage

Command, both sides

dot -Kosage -Tsvg input.gv

Input

tests/wild/gallery_osage_0_f6bd9e.gv · 294 bytes

Features

clusterspack

Result

identical on macOSidentical under portable math

OverprintSide by sideBlinkPixel diffSource diff

Comparing…

Magenta plate

100%

C onlyport onlyboth: in register

Live check, in this browserRun again

Waiting to load the WASM build (1.7 MB, about 700 KB compressed)

The browser runs renderAllBytes(input, "osage", "svg") on the same bytes the C reference read. WASM uses the portable math library, not Apple's libm, so a layout that depends on the last bit of sin or pow can legitimately differ (why).

Input

gallery_osage_0_f6bd9e.gv

graph {
  layout=osage
    subgraph cluster_0 {
      label="composite cluster";
      subgraph cluster_1 {
          label="the first cluster";
        C
        L
        U
        S
        T
        E
        R
      }
      subgraph cluster_2 {
          label="the second\ncluster";
        a
        b
        c
        d
      }
      1
      2
    }
  3
  4
  5
}

Files

File	Bytes	SHA-256
input.gv	294
c.svg C	5,587	3f4731a24ef6669a9e1494792d069b305ff0d20aa5c1d0148979f03014edb973
rust.svg Rust	5,598	57569817ad31c53520f87fdced11801a450a3d04a61bb4787cb138ebacdcb7d6

The two hashes differ even when the outputs are identical, because each file keeps its own generator comment. Made by scripts/site-samples.sh.

PreviousRadial Unix treeAll samplesNextpatchwork treemap