A jump back joins an overlapping Visibility episode, or an Obstruction or Target issue episode holding all its targets; a slow drift, a Target issue episode holding its targets. Removed (their benchmark contribution, each alone): heat shimmer dropped next to a shift of several targets (Visibility found +1), HOSTS with the thermal wave (none), the special cases of a Brief obstruction, of heat shimmer and of the thermal wave as hosts (one jump back at WILDSTRUBEL, already lost), SHIFTS, variety() reduced to (label, level). sentence() removed: each detector writes the text of its episodes; the event adds one sentence for the jumps it absorbed. events() no longer takes anything from the folder. Benchmark Totals (from the previous commit): Visibility found 54 -> 55 %, correct 71 -> 72 %; the other families unchanged. regression.py now runs in about 1 min (was 3.5). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
detectors
The AIMsight anomaly detectors and their benchmark. Python 3, standard library only.
The detectors
One detector per anomaly family of the displacements, in scripts/:
| Family | Detector |
|---|---|
| Visibility | visibility.py |
| Obstruction | obstruction.py |
| Target issue | target_issue.py |
| Thermal displacement | thermal_displacement.py |
| No data | no_data.py |
| Displacement | displacement.py |
categories.py runs them all and classifies their episodes into events, one line per event; they read a station folder through scripts/data.py of the tools repository, the sibling ~/aimsight-tools.
python3 scripts/categories.py <station folder> --from YYYY-MM-DD --to YYYY-MM-DD # --chunk N, --history N
thresholds.md is the registry of the detectors' thresholds and what each was tuned on.
Measuring them: bench/
The detectors against labels (JSONL, one per line, {"id", "start", "end", "family", "description"}, UTC ISO times):
python3 bench/score.py <station folder> --labels <labels.jsonl> --from YYYY-MM-DD --to YYYY-MM-DD # the score of a range
python3 bench/regression.py --labels <folder of <STATION>.jsonl> --data <folder of <STATION>/> # the benchmark; --from/--to: one range for all
python3 bench/sensors.py <station folder> --from YYYY-MM-DD --to YYYY-MM-DD # the sensors of each event
A change to a detector is checked with the benchmark; a refactoring leaves every figure unchanged.
Improving them
The detectors are improved by Optimizer (its optimize skill, from one analysis), with the upgrader and validator agents of the agents repository: on the range of an analysis, its labels as the truth, the upgrader fixes the detectors (one commit per fix here) and the validator keeps, removes or cancels the fixes against overfitting, judged by this benchmark. Nothing is pushed.
Copied from Support-Agent on 2026-11-13 (commit 48a3092); the detectors now evolve here. Used by aimsight-app and Optimizer, through a detectors -> ~/aimsight-detectors link (one copy on the workstation); their labels come from the labeling repository, their data from aimsight-data. The architecture of the repositories: ~/aimsight-app/docs/architecture.drawio.