You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I built a small deterministic CPU reference around ChartGPU’s parallel-LTTB path to make bucket-level decisions inspectable - every candidate, the neighboring bucket averages, and the winner/runner-up margin.
It focuses on ordinary full-scan interior buckets up to 512 points and lives as a separate JS reference, rather than making a GPU parity claim.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I built a small deterministic CPU reference around ChartGPU’s parallel-LTTB path to make bucket-level decisions inspectable - every candidate, the neighboring bucket averages, and the winner/runner-up margin.
It focuses on ordinary full-scan interior buckets up to 512 points and lives as a separate JS reference, rather than making a GPU parity claim.
https://github.com/notferdon/decimation-decision-microscope
From the library side, where could something like this actually be useful - debugging, regression testing, correctness checks, or somewhere else?
And if you were going to test one invariant first, which would matter most: bucket/index behavior, numerical precision, or something I’m missing?
All reactions