Validation dashboard
A card is accepted once its output has been compared, on a real recording, against a reference computed separately in Python with MNE-Python or an equivalent library. A card that merely runs, or that agrees with an earlier version of itself, is not validated.
This table is written by the continuous integration run, not by hand. If a comparison starts failing, it turns red here before anyone tells you.
How the comparison works
For each card, the harness loads a real recording, runs the card through the application engine, then computes the same quantity from scratch with the reference library in a separate process. The two outputs are compared channel by channel.
The tolerance is set per card, because the right answer differs. A re-referencing operation is arithmetic and should agree to floating-point noise, so its tolerance is 1e-6. A FIR filter depends on how the transition band is resolved, so a correlation of 0.99 is the honest target rather than exact equality.
What this does not tell you
Agreement with a reference means the arithmetic is right. It does not mean the card is the right choice for your data, that the parameters you picked are sensible, or that the reference itself is beyond question. Those remain your judgement.
It also covers built-in cards only. Cards published by other people are reviewed before they appear in the marketplace, but they are not run through this harness.
Replaying it yourself
The harness ships with the repository. It recomputes the reference from scratch rather than comparing against a stored result, so a change in the reference library shows up as a disagreement rather than passing silently.
python3 tools/gt.py --all --report validation.json