patchwork treemap

Engine

patchwork

Command, both sides

dot -Kpatchwork -Tsvg input.gv

Input

tests/wild/gallery_patchwork_0_7dbf8c.gv · 255 bytes

Features

areaclusters

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, "patchwork", "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_patchwork_0_7dbf8c.gv

graph {
  layout=patchwork
  node [style=filled]
  "$2"  [area=200 fillcolor=gold]
  "$1"  [area=100 fillcolor=gold]
  "50c" [area= 50 fillcolor=silver]
  "20c" [area= 20 fillcolor=silver]
  "10c" [area= 10 fillcolor=silver]
  "5c"  [area=  5 fillcolor=silver]
}

Files

File	Bytes	SHA-256
input.gv	255
c.svg C	2,369	a9512cb13821cee57fe175199f0953fb2b7e89d0cda1ccbce76e9837a618b0df
rust.svg Rust	2,380	e3ad12e8c1be03ee1466d0f552a26ee1c748810ef62a44cecdab2d9fe801fe05

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

Previousosage cluster packingAll samplesNextUnix tree as treemap