mirror of
https://github.com/harvard-edge/cs249r_book.git
synced 2026-05-08 02:28:25 -05:00
9a0d14681f
The notation-consistency scanner flags bare P as 'possible peak performance' and
bare L as 'possible latency'. In practice these occurrences across vol2 are
legitimate uses of P/L for distinct concepts (probability functions like P(X),
parameter count P, prompt-token count P, layer-count L, batch-size ratio
L/L_max). Adding each to the accept-list (matched on file + exact source line)
so the check stays useful for catching genuine convention drift.
Files affected: vol2/{compute_infrastructure, distributed_training, inference,
ops_scale, performance_engineering, responsible_ai, robust_ai}.qmd.