The control station of the AIMsight diagnostic: see, analyze, launch. The Data page shows the curves, the camera images, the labels and the detectors' events; its Analysis tab launches, by `claude -p`, processes whose code lives in the other repositories:
- **"Analyze the range"**: the `analyst` of the agents repository, on a chosen range, with the app's instructions (`instructions/analyst.md`) and without the detectors (`DETECTORS: no`): labels, submitted to `labeling/auto/`, and a diagnostic report;
- **"Optimize the detectors"**, on a finished analysis: `/improve` in Optimizer improves the detectors on the range of the analysis, its labels as truth, without overfitting; then the `tool-builder` of the agents repository brings the analyst's scripts into the reading harness (tools repository).
Each thing is committed in its own repository: the labels in `~/labeling`, the detectors in `~/detectors` (the optimization session does it, without pushing), the tools in `~/tools` (the tool-builder does it).
The pumping is in the `~/aimsight-data` repository (`extraction/`, VS Code tasks **pump** and **pump a range**); user guide `~/aimsight-data/extraction/README.md`.
- the labels: `python3 labeling/scripts/validate.py` (the labels submitted by the app do not have `review` yet, which it requires: as many expected errors);