kferjaoui d14b2c0088 docs: correct floor/peak definition, s1-vs-s4 evidence, and engine timelines ...

Resolve a terminology collision where "floor" meant both max(H2D, kernel,
D2H) and the best sustained rate. They coincide at 3x3 (16.17) and diverge
at 9x9 f64 (32.66 profiled max vs 30.01 sustained), so the deck read as
self-contradictory only at 9x9. Unify on "floor" across the deck, split A1
into separate `engine max [s4]` and `FLOOR = lower of max, sustained` rows,
and document in the report that the two numbers come from two different
runs made by two different tools -- 30.01 is unprofiled ladder wall clock,
not an nsys number.

Rebuild fig_f32_kernel as paired s1/s4 panels: the old one was hardcoded to
cap-1500 s1 values and showed the kernel binding in both arms, refuting the
D2H-handover claim on the same slide. Move that conclusion to 22/34, the end
of the Act III arc.

Redraw the opt2/opt3 timelines from a real schedule honouring one copy
engine per direction (measured overlap 1.00), with 3x3 proportions instead
of unsourced ones. Retires the "all four in flight" claim -- three are.

Redraw fig_cancellation's error floor from 42 to the documented +-3-4 ADU2;
42 was 6.5 squared, i.e. the line and the shading were each other's source.

Normalise 9x9 numbers to cap 1700 and fix eight cap-1500 residues in the
report, plus the per-instance kernel figure (43.2 us at s4, not 39.9).

2026-08-24 20:57:24 +02:00

1.6 MiB

Raw History

View Raw