thresholds.md, CLAUDE.md, README.md: the simplified detectors

thresholds.md keeps only the remaining constants, with shortened history; CLAUDE.md and README.md describe the five
modules, common.py, the families each gives, the reader of the tools repository and the event fields; the benchmark
takes about 1 min.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
maximeandClaude Opus 5.5 committed 2026-11-16 17:33:43 +01:00
1 parent 8b5f8a34b9
commit 000e8bd6e4
3 files changed
+51 -78

No files matched your search

+10 -8
View File
@@ -4,21 +4,23 @@ AIMsight anomaly detectors (Python 3, standard library only) and their benchmark
## Contract (do not break)
- One detector per family, in `scripts/`: `visibility.py`, `obstruction.py`, `target_issue.py`, `thermal_displacement.py`, `no_data.py`, `displacement.py` (D-119). `categories.py` loads every `scripts/*.py` that has `detect`: never put another script with a `detect` function, or with side effects at import, directly in `scripts/`; tools go in `bench/`.
- `detect(measurements)` returns episodes with the keys `start`, `end`, `kind` (the family), `label` (the variety), `text`, `ignore`, `sensors`. A detector may also declare `temperature`, `camera`, `metrics` (`categories.CONTEXT`) or `end`; `categories.events` passes them by introspection.
- `scripts/categories.py` runs the detectors of `DETECTORS` (modules of `scripts/`: `visibility`, `target_issue`, `thermal_displacement`, `no_data`, `displacement`) and makes their episodes events. A module returns every family it finds: `visibility` also gives Brief obstruction and `target_issue` Target obscured (Obstruction). `common.py` holds the helpers they share.
- `detect(measurements)` (`no_data`: also `end`, the end of the window read) returns episodes with the keys `start`, `end`, `kind` (the family), `label` (the variety), `text` (the sentence shown), `ignore`, `sensors`; a Poor visibility also has `level`.
- The measurements are read by `scripts/data.py` of the tools repository, the sibling `~/aimsight-tools` (`categories.py` puts it on the path); a reading fix is made there.
- Label files (JSONL): `id`, `start`, `end`, `family`, `description` (and `review`, `analysis`); the project uses `labeling/auto` only.
- Two repositories use this one through a `detectors -> ~/aimsight-detectors` link (one copy on the workstation: a commit here is live for both at once); a rename here needs the matching change there:
- aimsight-app: `categories.events`, `categories.CATEGORIES` (`process`: `images`, `none`, `check`), the `--from/--to` CLIs, `bench/score.py` (the command shown in the page);
- aimsight-app: `categories.events`, `categories.CATEGORIES` (`process`: `images`, `none`, `check`), the event fields (`start`, `end`, `category`, `text`, `sensors`, `ignore`, `episodes`), the `--from/--to` CLIs, `bench/score.py` (the command shown in the page);
- Optimizer (`optimize` skill and its agents): `scripts/categories.py --from/--to`, `bench/` (`score.py`, `regression.py`, `sensors.py`); its upgrader changes `scripts/*.py` and `thresholds.md`, one commit per fix.
## Rules
- A change to improve the detectors touches `scripts/*.py` and `thresholds.md` only; never `bench/`, which is the measure. Anything is possible there: add, remove or change a constant, a rule or a whole detector; a fix that needs a new family is out of reach (one detector per family, above).
- A change to improve the detectors touches `scripts/*.py` and `thresholds.md` only; never `bench/`, which is the measure. Anything is possible there: add, remove or change a constant, a rule or a whole detector, as long as the six families remain.
- **Simple first**: a rule earns its place by its score on the benchmark, not by one case; prefer removing or widening a rule to adding a special case.
- **Everything is detected**: what is shown or not to a client is not the detectors' business. A setting chosen not to show something may be changed, saying so.
- A constant added or changed updates its line of `thresholds.md` ("Tuned on": the run that changed it) and the detector's docstring in the same change; a constant or detector removed removes its line; check with `grep -nE "^[A-Z_0-9]+ = " scripts/*.py`.
- A detector that no longer loads silently disappears: a `skipped` line in the output of `categories.py` or of the benchmark means the change is broken.
- A constant added or changed updates its line of `thresholds.md` ("Tuned on": the run that changed it) and the detector's docstring in the same change; a constant or rule removed removes its line; check with `grep -nE "^[A-Z_0-9]+ = " scripts/*.py`.
- A detector that fails is skipped: a `skipped` line in the output of `categories.py` or of the benchmark means the change is broken.
- No rule specific to a station, a sensor or a date.
- A change to a detector is checked with the benchmark: `python3 bench/regression.py --labels <labels folder> --data <data folder>` (aimsight-app and Optimizer: `labeling/auto`, `data`, links to the shared `~/aimsight-labeling` and `~/aimsight-data/data`; about 3 min). A refactoring must leave every figure unchanged.
- A change to a detector is checked with the benchmark: `python3 bench/regression.py --labels <labels folder> --data <data folder>` (aimsight-app and Optimizer: `labeling/auto`, `data`, links to the shared `~/aimsight-labeling` and `~/aimsight-data/data`; about 1 min). A refactoring must leave every figure unchanged.
- **The benchmark's scores**, per family of each station: "found", the share of the labelled instants the detectors flag; "correct", the share of the flagged instants a label puts in the family. **A regression**, on a family of a station: "found" or "correct" loses more than 2 points; it is a regression even if the `Total` rises; under 2 points it is not one; a rise is a plus, never a requirement. **Not a regression**: a drop that comes from another consistent reading of the detectors that the labels do not retain: labels contradicting each other from one station to another (the same state in two families), the gaps of a few measurements between two labels of the same phenomenon, the bounds of a label, an instant the score (per instant, without the sensors) counted as found by an event on another sensor. Labels have their ambiguities: the goal is detectors that do their best, not perfect, and not overtrained on the labels.
- History references in docstrings and `thresholds.md` ("wf-improve X, mod. 1, S2", "X, batch 01", D-xxx, E-xxx) point to past runs and to decisions recorded in aimsight-app/Support-Agent; keep them when editing a rule.
- History references in docstrings and `thresholds.md` ("wf-improve X, mod. 1, S2", "X, batch 01", D-xxx, E-xxx) point to past runs and to decisions recorded in aimsight-app/Support-Agent; keep them short when editing a rule.
- The bench tools take their paths as arguments; the architecture of the repositories: `~/aimsight-app/docs/architecture.drawio`.
+10 -12
View File
@@ -4,22 +4,20 @@ The AIMsight anomaly detectors and their benchmark. Python 3, standard library o
## The detectors
One detector per anomaly family of the displacements, in `scripts/`:
Five modules in `scripts/`, one per kind of reading; each gives episodes of one or more of the six families:
| 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` |
| Module | Reads | Families (varieties) |
|---|---|---|
| `visibility.py` | error_value of each sensor; fast noise of the curves | Visibility (Poor visibility "none" or "reduced", Heat shimmer), Obstruction (Brief obstruction) |
| `target_issue.py` | rejections day after day | Target issue (Degraded target), Obstruction (Target obscured) |
| `thermal_displacement.py` | the daily wave of the curves | Thermal displacement (Thermal expansion / contraction, Camera thermal expansion / contraction, Camera thermal movement) |
| `no_data.py` | the cadence of the measurements | No data |
| `displacement.py` | jumps and slow drift of the corrected curves | Displacement (Sudden jump, back to normal; Lasting shift; Jump, not back yet; Slow drift) |
`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`.
`common.py` holds their shared helpers. `categories.py` runs them all and classifies their episodes into events (a jump back joins the visibility loss or the obstruction that explains it; the same variety less than an hour apart, one event), one line per event. The measurements are read by `scripts/data.py` of the tools repository, the sibling `~/aimsight-tools`.
```bash
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.
@@ -40,4 +38,4 @@ A change to a detector is checked with the benchmark; a refactoring leaves every
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`.
Copied from Support-Agent on 2026-11-13 (commit 48a3092), simplified on 2026-11-16 (branch `simplify`); 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`.
+31 -58
View File
@@ -1,72 +1,45 @@
# Detector thresholds
Every threshold of the detectors (`scripts/*.py`, one per family of the families document, D-119) is **provisional**: tuned on the six data sets of events E-001 to E-005 and NORDEND of October, then adjusted by wf-improve sessions. When bulk data arrives, this is the list to review. A constant added or changed updates this file in the same change. Check: `grep -nE "^[A-Z_0-9]+ = " scripts/*.py`.
Every threshold of the detectors (`scripts/*.py`) is **provisional**: tuned on the data sets of events E-001 to E-005 and NORDEND of October, then adjusted by wf-improve sessions. A constant added or changed updates this file in the same change; check with `grep -nE "^[A-Z_0-9]+ = " scripts/*.py`.
The detectors must detect everything (the user, 2026-10-26, D-068): a setting chosen to hide something from the client is not a detection rule; the wf-improve workflow may change it. What is shown to the client is decided in a separate layer.
The detectors detect everything (the user, 2026-10-26, D-068): what is shown to the client is decided in a separate layer.
"wf-improve X, mod. 1, S2": suggestion S2 of modification 1 of the wf-improve run on X. "X, batch 01": first batch of the earlier loop on station X.
"wf-improve X, mod. 1, S2": suggestion S2 of modification 1 of the wf-improve run on X; "X, batch 01": first batch of the earlier loop on station X.
| Detector | Constant | Value | Tuned on |
|---|---|---|---|
| `visibility` | `K_MAD` | 10 | E-001 (fog 11 to 57 MAD), E-005 (10 to 70 MAD) |
| | `FACTOR` | 2 | drops sensors with a near-zero MAD (E-004, E-005); also, alone (without `K_MAD`), something passing in front of one or two targets or a reference, rejected for a single measurement (point 2): wf-improve Obstruction, mod. 1, S3 (WILDSTRUBEL: by day, heat shimmer inflates the MAD; R1 rejected at ×3.6 under 10 MAD) |
| | `RUN_MIN` | 3 | E-001, rain of E-005 |
| | `BRIEF_MIN` | 3 | trains of E-005 (5 to 17 sensors) |
| `visibility` | `K_MAD` | 10 MAD | E-001 (fog, 11 to 57 MAD), E-005 (rain, trains, 10 to 70 MAD) |
| | `FACTOR` | 2× the median | drops the sensors with a near-zero MAD (E-004, E-005); alone, something passing in front of one or two targets (wf-improve Obstruction, mod. 1, S3) |
| | `RUN_MIN` | 3 | E-001, rain of E-005; also the diffuse nuisance |
| | `GAP_STEPS` | 2.5 steps | timestamp jitter, a missing step |
| | `BRIEF_MIN` | 3 sensors | trains of E-005 (5 to 17 sensors) |
| | `SALIENCE` | 3 | trains (5 to 17) against the cobweb of E-002 (2 to 9) |
| | `FRAC` | 0.15 | tails of PR09 and CTR01 (NORDEND October) |
| | `BREAK` | 2 h | NORDEND October, night of the 13th to the 14th |
| | `K_TARGET` | 5 | leaves of E-005 (6 to 25 MAD) |
| | `TARGET_MIN` | 3 | —; 2 when `TARGET_MIN` measurement steps do not fit in `TARGET_GAP`: wf-improve Obstruction, mod. 1, S6 (BREITHORN, one measurement every 4 h: vehicles parked at night, two or three rejections) |
| | `TARGET_GAP` | 6 h | leaves of E-005 (7 rejections in 12 h); at least two measurement steps (same S6) |
| | `GAP_STEPS` | 2.5 steps | timestamp jitter |
| | `REJECT_FACTOR` | 1.2 | FLORIDA, batch 01: a rejection at 10 MAD is high without doubling (targets at level 0.6); drops C24 of E-009 (0.68, rejected at ×1.04) |
| | `HALF` | 0.5 | level "none" (point 5): NORDEND 09/10 23:00 (68 % rejected) against the rain of E-005 (24 to 33 %) |
| | `K_DIFFUSE` | 2.5 MAD | diffuse nuisance (point 8): median, over the sensors, of the error_value in MAD above each one's median, `RUN_MIN` instants in a row, rejected or not: Poor visibility "reduced"; not within heat shimmer; wf-improve Visibility, mod. 1, S2 (JUNGFRAU, FLORIDA, NORDEND: reduced visibility of the whole scene without rejection; at 2, nights labelled thermal at JUNGFRAU and jumps back of WILDSTRUBEL absorbed; at 3, half the gain) |
| | `FEW` | 3 targets | Poor visibility on at most 3 targets, no reference: an object in front of them, Target obscured (boundary "Visibility or Obstruction" of the families document); BREITHORN, batch 01 (vehicles parked in front of 2 or 3 targets out of 12) |
| `visibility` (heat shimmer) | `RATIO` | 1.5 | E-003 (×1.7 to ×3 the night) |
| | `HALF` | 0.5 | level "none": NORDEND 09.10 23:00 (68 % rejected) against the rain of E-005 (24 to 33 %) |
| | `K_DIFFUSE` | 2.5 MAD | diffuse nuisance: wf-improve Visibility, mod. 1, S2 (JUNGFRAU, FLORIDA, NORDEND) |
| `visibility` (heat shimmer) | `RATIO` | 1.5× the calm | E-003 (corr ×1.7 to ×3, error_value ×1.7 to ×3.2 the night) |
| | `SHARE` | 0.5 | — |
| | `RATIO_ERR` | 1.5 | E-003 (×1.7 to ×3.2) |
| | `REJECT_MAX` | 15 % | E-003 ≤ 7 %; cobweb and rain ≥ 18 %; rejections beyond each sensor's habit (its share of rejections over the export): wf-improve Visibility, mod. 1, S1 (WILDSTRUBEL: a reference or targets usually rejected dropped the days of heat shimmer; 4 to 14 % against 9 to 22 % raw) |
| | `STRONG` | 2× | E-003 (×2.3 to ×2.6) |
| | `MIN_DURATION` | 3 h | E-003 (10-11 h) against the morning of E-004 (2 h); the classification drops this morning too, whatever the duration |
| `displacement` (jumps) | `K` | 20 noises | E-001 (at 15, two healthy targets greyed); do not lower for the trains, seen by `visibility` |
| | `K_LASTING` | 7 noises | jump under K that stays (point 8 of `displacement.py`): NIEDERHORN, batch 01 (e09, corr_y −0.19 px at once, 8 noises, stayed 5 days) |
| | `PLATEAU` | 8 ordinary variations | same point: gap between the medians of the day after and the day before, in ordinary variations of the level from one day to the next; NIEDERHORN, batch 01 (e09: 13; E-001, healthy targets: 6 at most) |
| | `K_PEAK` | 6 noises | one-step peak common to several targets: NORDEND, batch 01 (shakes of the whole image, 6 to 11 noises) |
| | `PEAK_MIN` | 3 targets | NORDEND, batch 01 (3 to 5 targets per shake) |
| | `BASE` | 4 measurements | 1 h at 15 min; the return of a jump is judged on an hour of measurements, BASE at most, one at least (wf-improve MICHIGAN, mod. 1: at a 4 h step, a peak back at the next measurement became "Large shift") |
| | `GAP` | 1 h | — |
| `target_issue` | `SHARE` | 0.25 | regularity rather than the share of the day: wf-improve Target issue, mod. 1, S1 (WILDSTRUBEL R3, rejected by day only) |
| | `MIN_HOURS` | 3 h | as hours at the station's cadence: wf-improve NEBRASKA, batch 01 (one measurement every 4 h) |
| | `BRIDGE` | 1 day | wf-improve Obstruction, mod. 1, S1; Target issue, mod. 1, S1 (at 2, parked vehicles of BREITHORN made a week) |
| | `WEEK` | 7 days | Degraded target against Target obscured: wf-improve NEBRASKA, batch 01 (lost references, 25 days; parked vehicles, 2 to 5 days) |
| | `MIN_DAYS` | 2 days | NORDEND: isolated days on 16 sensors |
| `displacement` (jumps) | `K` | 20 noises | E-001 (at 15, two healthy targets greyed); the trains of E-005 are left to `visibility` |
| | `BASE` | 4 measurements | 1 h at 15 min; the return is judged on an hour (wf-improve MICHIGAN, mod. 1) |
| | `BACK_H` | 24 h | E-002 (plateaus up to 11.5 h) |
| | `REPEAT` | 5 jumps back | CLARIDEN, batch 01: PR_BG flips 28 times in 2.5 days, the other targets 3 at most (morning of the movement) |
| | `FLIP` | 36 h | problem target (D-074): PR_BG of CLARIDEN flips 2.5 days; C8 and C13 of E-009, 5 flips in 1 h 20 on the morning of the movement, stay brief jumps; 6 h → 36 h: wf-improve Target issue, mod. 1, S2 (NORDEND PR12, PR14, PR08, PR05, JUNGFRAU BJ_G: 12 to 28 h of flips within a loss of visibility, labelled Visibility or Obstruction, absorbed by it) |
| | `MAX_FLIPPING` | 2 targets | problem target: FLORIDA, the two stuck targets; E-002, cobweb on the references, 15 targets flip at once |
| | `LARGE` | 0.5 | large shift ("Large shift", D-074): E-004 and CLARIDEN, 18 targets on the morning of the movement; also, slow drift of the camera (LARGE of the targets in corr and of the sensors in raw x, y, on the same side: no "Slow drift" over the whole window, only the pieces of `PIECE`): wf-improve MICHIGAN, mod. 1 (BREITHORN kept); wf-improve Displacement, mod. 1, S2 (NEBRASKA reported in pieces, JUNGFRAU still silent) |
| `displacement` (slow drift) | `HOURS` | 20 h out of 24 | as the trend of the Displacements tab (D-055); as a share of the hours the station measures (wf-improve MICHIGAN, mod. 1: 5 out of 6 at one measurement every 4 h, no day counted) |
| | `DAYS` | 5 days | D-055: a trend needs at least 5 UTC days |
| | `SIZE` | 1 | D-055: drift over the period ≥ one daily amplitude; amplitude of the day: 9th and 1st deciles of `corr` |
| | `STEADY` | 0.6 | D-055: Kendall tau of the daily levels; a step from one day to the next of more than half the drift drops it (a jump) |
| | `PIECE` | 3.5 amplitudes | piecewise drift, for a target without a drift over the whole window (point 4b of `displacement.py`): wf-improve Displacement, mod. 1, S1 (rows of CLARIDEN, 3.8 to 8.3 amplitudes; JUNGFRAU, thermal cycles without a Displacement label, 3.1 at most; at 1, NORDEND and JUNGFRAU overflow) |
| | `MAX_HOLE` | 2 days | a drift piece (point 4b) does not go from one kept day to the next more than 2 days apart: wf-improve Displacement, mod. 2, S1 (CLARIDEN, hole from 10-03 to 10-05: the pieces from 09-28 to 11-01 fall; at 1, the missing days of a half-day hole cut the drifts of CLARIDEN and NEBRASKA) |
| `thermal_displacement` | `MIN_HOURS` | 20 h | —; days of the profile |
| | `PARTIAL` | 12 h | an incomplete day (fewer than `MIN_HOURS`) gets its episode if it looks like the profile on the hours it has, without entering the profile; wf-improve Thermal displacement, mod. 1, S4 (SNCF01, NORDEND, JUNGFRAU: labelled cycles of days cut by a hole; `MIN_HOURS` at 12 or 16 made NIEDERHORN go back) |
| `displacement` (slow drift) | `HOURS` | 20 h out of 24 | as the Displacements tab (D-055), as a share of the hours measured (wf-improve MICHIGAN, mod. 1) |
| | `DAYS` | 5 days | D-055 |
| | `SIZE` | 1 amplitude | D-055 |
| | `STEADY` | 0.6 | D-055 (Kendall tau) |
| | `PIECE` | 3.5 amplitudes | wf-improve Displacement, mod. 1, S1 (rows of CLARIDEN 3.8 to 8.3; thermal cycles of JUNGFRAU 3.1 at most) |
| `thermal_displacement` | `MIN_HOURS` | 20 h | — |
| | `REPRO` | 0.6 | pure noise ≈ 0 |
| | `SHARE` | 0.5 | NORDEND October just under (9/19) |
| | `WARM` | 0.3 | —; only says there is a cycle (at least `MIN_WARM_HOURS` warm hours), its bounds are at `EDGE` |
| | `EDGE` | 0.1 | start of the wave, going back from the peak (the return: `RETURN`); wf-improve Thermal displacement, mod. 1, S1 (NORDEND, JUNGFRAU, SNCF01: labelled evenings and nights, the wave stopped at the last warm hour; at 0.15 and 0.2, fewer nights found, FLORIDA overflows in the evening anyway) |
| | `RETURN` | 0.05 | return of the wave, the return after midnight if needed, at most to the next day's start: the cooling tail is slower than the warm-up; wf-improve NORDEND 2026-11-05, S1 (NORDEND, JUNGFRAU: labelled nights after the return reached `EDGE`; `EDGE` itself at 0.05, start included, made FLORIDA and SNCF01 overflow) |
| | `DAY_MATCH` | 0.5 | — |
| | `R2_MIN` | 0.3 | PS des Coudres 14 axes out of 22 above, CLARIDEN 0 out of 48 |
| | `NIGHT` | 8 h | — |
| | `R2_MIN` | 0.3 | 24 h sinusoid: PS des Coudres 14 axes out of 22 above, CLARIDEN 0 out of 48; no longer asked for the camera (raw positions) since WILDSTRUBEL, batch 01 (1 target out of 7, the wrong pointings crush the fit) |
| | `MIN_WARM_HOURS` | 2 h | WILDSTRUBEL, batch 01: a single warm hour is not a cycle (NIEDERHORN, E-005: noon, trains and holes) |
| | `SLIDE_K` | 3 noises | common camera slide without a cycle ("Camera thermal movement"): gap from the median of the day before, raw positions and corrected curves; wf-improve MICHIGAN, mod. 1 (at 2, Displacement instants of BREITHORN taken) |
| | `COLD` | 4 one-hour noises | the camera moves with the cold ("Camera thermal movement", without a cycle): the pose (tilt, rotation or scale) moves away from its median of the day before while the temperature falls under its own, the same hour; noise: variations over an hour, one step at 4 h; wf-improve Thermal displacement, mod. 1, S3 (BREITHORN, CLARIDEN, NEBRASKA: targets in opposite directions, or compensated; at 3, Displacement instants of NEBRASKA taken) |
| `no_data` | `MISSING` | 2 steps | user's rule, 2026-10-23; also applied between the last measurement and the end of the window read (CLARIDEN, batch 01); the step is at least an hour divided by the median instants per clock hour (bursts of measurements: the cycle, not the minute inside a burst; wf-improve, batch 2026-11-05, S1: SUSTENHORN) |
| `target_issue` | `CALM` | 0.25 | (detector added on 2026-10-27, see its docstring) |
| | `SHARE` | 0.5 | —; the target hidden at times ("Target obscured") |
| | `SHARE_WEEK` | 0.25 | share of the calm instants rejected that makes a degraded day of the problem target ("Degraded target", at least `WEEK` days): regularity rather than the share of the day; wf-improve Target issue, mod. 1, S1 (WILDSTRUBEL R3 rejected from 04:00 to 16:00 every day, 30 to 45 %: seen only on days without night measurements; NORDEND PR04 and CTR01, NIEDERHORN PWD_IMP_B08_024_C09, under half) |
| | `MIN_HOURS` | 3 h | hours of calm instants per day, at the station's cadence (median gap between two instants): 12 instants at 15 min; wf-improve NEBRASKA, batch 01 (one measurement every 4 h: no day counted, the lost reference REFCOLH22 was not seen) |
| | `MIN_DAYS` | 2 days | NORDEND: isolated days on 16 sensors |
| | `WEEK` | 7 days | problem target ("Degraded target") if hindered at least a week in a row, otherwise a target hidden at times ("Target obscured"): boundary "Target issue or Obstruction" of the families document; wf-improve NEBRASKA, batch 01 (BREITHORN, parked vehicles, 2 to 5 days; NEBRASKA and MICHIGAN, lost reference, 25 days; JUNGFRAU, PM_G, 63 days) |
| | `BRIDGE` | 1 day | non-degraded days in a row that do not break the run of a problem target ("Degraded target": `WEEK` days from the first to the last degraded day, `SHARE_WEEK` of rejections over the bridged run); wf-improve Obstruction, mod. 1, S1 (FLORIDA, SNCF01, NORDEND, NIEDERHORN: problem targets cut into Target obscured by a day under `SHARE`; BREITHORN, parked vehicles, unchanged); 2 → 1: wf-improve Target issue, mod. 1, S1 (at a quarter, two bridging days joined the parked vehicles of BREITHORN, POUI22, into a week) |
| | `STUCK` | 0.05 | stuck target (D-074): E-011, C2 and C3 at 0.006 and 0.016 of the others' noise; NORDEND, E-001: 0.7 at the lowest |
| `categories` (classification) | `MERGE` | 1 h | rule validated by the user: same variety less than an hour apart, a single event; two Obstruction (Target obscured, Brief obstruction) only if they share a sensor (wf-improve Obstruction, mod. 1, S1 and S3), two Target issue too (wf-improve Target issue, mod. 1, S3); a Brief obstruction only absorbs the jumps back within `MERGE` after its instant (S3) |
| | `WARM` | 0.3 | — |
| | `EDGE` | 0.1 | wf-improve Thermal displacement, mod. 1, S1 (labelled evenings and nights) |
| | `RETURN` | 0.05 | wf-improve NORDEND 2026-11-05, S1 (the cooling tail is slow) |
| | `SLIDE_K` | 3 noises | wf-improve MICHIGAN, mod. 1 (at 2, Displacement instants of BREITHORN taken) |
| `no_data` | `MISSING` | 2 steps | user's rule, 2026-10-23; also up to the end of the window (CLARIDEN, batch 01); the cadence of bursts (wf-improve, batch 2026-11-05, S1) |
| `categories` | `MERGE` | 1 h | rule validated by the user (2026-10-24); an Obstruction or a Target issue only with the same target (wf-improve Obstruction, mod. 1, S1; Target issue, mod. 1, S3) |