maximeandClaude Opus 5.5 8b5f8a34b9 visibility: Target obscured left to target_issue; categories no longer imports a detector
Removed: the repeated rejections of a target in visibility.py with K_TARGET, TARGET_MIN, TARGET_GAP (Obstruction found
-5, correct +3: found -14 at SNCF01, 3 instants, and -10 at WILDSTRUBEL); Target obscured now comes from target_issue
only. categories.py keeps its own JUMP_BACK so that a broken displacement.py does not block it.

Benchmark Totals (from the previous commit): Obstruction found 45 -> 40 %, correct 31 -> 34 %; the other families
unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 17:32:00 +01:00
2026-11-16 11:56:56 +01:00

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.

S
Description
Detectors for time series classification
Readme
417 KiB
0 Stars 1 Watchers 0 Forks
Languages
Python 100%