Real calls, run when this page was built. The code is the story file itself.
Which readouts can it carry at all?
Each readout in the catalogue names the feature that makes it informative. readouts.gate asks the front-end model whether that feature fits in the band, and answers before anything is recorded.
A diagram whose captions sit on top of each other is unreadable in exactly the place it matters — beside the electrode. This was found by LOOKING at a rendered head map (two labels printed over one another) rather than by any test, which is why it is a function now.
Can this front end carry this readout's informative feature? Answer BEFORE recording.
Full documentation
Returns the per-frequency verdict for the feature and both band edges, so a readout that is fine in the middle and destroyed at one edge cannot read as simply 'reachable'.
The directory holding the optional companion analysis tools: $OLIMEX_TOOLS, else the nearest parent with a REGISTRY.md. The Atlas tab and the extraction widgets come from there; without it they are switched off.