Compare commits
8
Commits
21a35d90aa
...
0abba2d0ed
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
0abba2d0ed | ||
|
|
b01a9116d0 | ||
|
|
3ea6b3e419 | ||
|
|
e7c03e7304 | ||
|
|
5438b0b469 | ||
|
|
7e3043d3a0 | ||
|
|
887b313ba2 | ||
|
|
c7e34b49f7 |
No files matched your search
@@ -1,4 +0,0 @@
|
||||
{
|
||||
"name": "detectors",
|
||||
"description": "AIMsight anomaly detectors and their improvement on a range of labelled data (/detectors:wf-improve)."
|
||||
}
|
||||
@@ -1,23 +1,20 @@
|
||||
# detectors
|
||||
|
||||
AIMsight anomaly detectors (Python 3, standard library only) and the Claude Code plugin that improves them (`/detectors:wf-improve`). Everything is in English: code, identifiers, docs, outputs. Layout and usage: `README.md`.
|
||||
AIMsight anomaly detectors (Python 3, standard library only) and their benchmark (`bench/`); nothing else. They are improved by Optimizer (`improve` skill) with the upgrader and validator of the agents repository. Everything is in English: code, identifiers, docs, outputs. Layout and usage: `README.md`.
|
||||
|
||||
## 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 `skills/wf-improve/scripts/`.
|
||||
- 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.
|
||||
- Label files are external data and keep their French keys: `debut`, `fin`, `categorie`, `description`.
|
||||
- Two repositories use this one as their `detectors/` submodule; a rename here needs the matching change there:
|
||||
- Diagnostic-app: `categories.events`, `categories.CATEGORIES` (`process`: `images`, `none`, `check`), the `--from/--to` CLIs, `/detectors:wf-improve`;
|
||||
- Optimizer (`batch.py`): `categories.events`, `categories.CATEGORIES`, and from `scripts/data.py` `load`, `load_temperature`, `is_reference`, `rejected`, `parse_time`, `iso`.
|
||||
|
||||
## The workflow stays generic
|
||||
|
||||
`skills/wf-improve/SKILL.md` and `agents/` describe only the workflow (range + labels → upgrader → validator → summary). Everything specific to a caller (its paths, its files, its git rules, where the summary goes) is given in the request at launch, never written here. The tools take their paths as arguments.
|
||||
- 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 -> ~/detectors` link (one copy on the workstation: a commit here is live for both at once); a rename here needs the matching change there:
|
||||
- Diagnostic-app: `categories.events`, `categories.CATEGORIES` (`process`: `images`, `none`, `check`), the `--from/--to` CLIs, `bench/score.py` (the command shown in the page);
|
||||
- Optimizer (`improve` 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 constant added or changed updates `thresholds.md` in the same change; check with `grep -nE "^[A-Z_0-9]+ = " scripts/*.py`.
|
||||
- No rule specific to a station, a sensor or a date.
|
||||
- A change to a detector is checked with the benchmark: `python3 skills/wf-improve/scripts/regression.py --labels <labels folder> --data <data folder>` (Diagnostic-app and Optimizer: `labeling/auto`, `data`, links to the shared `~/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>` (Diagnostic-app and Optimizer: `labeling/auto`, `data`, links to the shared `~/labeling` and `~/aimsight-data/data`; about 3 min). A refactoring must leave every figure unchanged.
|
||||
- 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 Diagnostic-app/Support-Agent; keep them when editing a rule.
|
||||
- The bench tools take their paths as arguments; the architecture of the repositories: `~/Diagnostic-App/docs/architecture.drawio`.
|
||||
@@ -1,6 +1,6 @@
|
||||
# detectors
|
||||
|
||||
The AIMsight anomaly detectors, and the workflow that improves them. Python 3, standard library only.
|
||||
The AIMsight anomaly detectors and their benchmark. Python 3, standard library only.
|
||||
|
||||
## The detectors
|
||||
|
||||
@@ -24,34 +24,20 @@ python3 scripts/visibility.py <station folder>
|
||||
|
||||
`thresholds.md` is the registry of the detectors' thresholds and what each was tuned on.
|
||||
|
||||
## Improving them: `/detectors:wf-improve`
|
||||
## Measuring them: `bench/`
|
||||
|
||||
The repository is also a Claude Code plugin (`.claude-plugin/plugin.json`). Its workflow improves the detectors on a range of data where they perform poorly, given labels as the truth on that range:
|
||||
|
||||
1. measures before: the score on the range, and a benchmark on a reference truth (every labelled station);
|
||||
2. the `upgrader` agent compares the detectors' events with the labels and fixes the detectors with general rules, one commit per fix;
|
||||
3. the `validator` agent, an LLM-as-judge that does not read the upgrader's diagnosis, keeps the fixes, removes some, or cancels them: no station may go back, no overfitting;
|
||||
4. a summary.
|
||||
|
||||
The result: detectors a little better on the range without going back elsewhere, or unchanged. Nothing is pushed.
|
||||
|
||||
The caller gives the context of each run: the range, the labels, the reference truth, the families document, any context documents, the output folder, and its own rules (git branch, what else to commit). For example:
|
||||
The detectors against labels (JSONL, one per line, `{"id", "start", "end", "family", "description"}`, UTC ISO times):
|
||||
|
||||
```bash
|
||||
claude --plugin-dir detectors -p "/detectors:wf-improve DETECTORS: detectors/. STATION: data/NORDEND. \
|
||||
FROM: 2026-11-04. TO: 2026-11-08. LABELS: labeling/auto/NORDEND.jsonl. \
|
||||
REFERENCE: --labels labeling/auto --data data. FAMILIES: labeling/familles.md. \
|
||||
CONTEXT: labeling/auto/analyses/NORDEND_x/rapport.md. OUT: detectors/runs/NORDEND_x/."
|
||||
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
|
||||
```
|
||||
|
||||
Labels: JSONL, one per line, `{"id", "debut", "fin", "categorie", "description"}` (UTC ISO times, `categorie` = the family).
|
||||
A change to a detector is checked with the benchmark; a refactoring leaves every figure unchanged.
|
||||
|
||||
- `skills/wf-improve/SKILL.md`: the workflow; its tools in `skills/wf-improve/scripts/`: `score.py` (the score of a range), `regression.py` (the benchmark), `sensors.py` (the sensors of each event).
|
||||
- `agents/`: `upgrader`, `validator` (called `detectors:<name>`).
|
||||
## Improving them
|
||||
|
||||
```bash
|
||||
python3 skills/wf-improve/scripts/score.py <station folder> --labels <labels.jsonl> --from YYYY-MM-DD --to YYYY-MM-DD
|
||||
python3 skills/wf-improve/scripts/regression.py --labels <folder of <STATION>.jsonl> --data <folder of <STATION>/>
|
||||
```
|
||||
The detectors are improved by Optimizer (its `improve` skill), 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 Diagnostic-app and Optimizer, where it is the `detectors/` submodule; their labels come from the `labeling` repository, their data from `aimsight-data`.
|
||||
Copied from Support-Agent on 2026-11-13 (commit 48a3092); the detectors now evolve here. Used by Diagnostic-app and Optimizer, through a `detectors -> ~/detectors` link (one copy on the workstation); their labels come from the `labeling` repository, their data from `aimsight-data`. The architecture of the repositories: `~/Diagnostic-App/docs/architecture.drawio`.
|
||||
@@ -1,111 +0,0 @@
|
||||
---
|
||||
name: upgrader
|
||||
description: Upgrader of the wf-improve workflow — on a range of data where the detectors perform poorly, compares what they find, all families, with the labels of the range (the truth), then fixes the detectors (adds, removes, changes) so that they do better there without overfitting, one commit per fix. Called by the orchestrator with the range, the labels, the families, the commands, the base commit and its output folder.
|
||||
tools: Read, Edit, Write, Bash
|
||||
model: inherit
|
||||
---
|
||||
|
||||
You are the upgrader of the wf-improve workflow: you make the detectors better on a range of data of a station where they perform poorly. The labels of the range are the truth. You compare what the detectors find with these labels, event by event, all families, say what is wrong and which detector causes it, then fix it. Afterwards, the `validator` judges your modification on the reference truth (all labelled stations, all families): a gain on the range at the cost of another station or another family is refused.
|
||||
|
||||
**Avoid overfitting**: a small step. A single range must not dictate the detectors: do better here with rules that would hold on any station, without aiming to reproduce exactly these labels. A constant tuned to make these bounds fall exactly, a rule that only recognises the exact shape of these events: no. What counts is the mechanism behind a label (a rejected reference that makes all targets jump, for example), recognisable wherever it happens. What the detectors cannot see with these measurements (a cause only an image reveals) is not a fix: say it in "Limits".
|
||||
|
||||
## Your request
|
||||
|
||||
The detectors repository (`DETECTORS`: the detectors `scripts/*.py`, their threshold registry `thresholds.md`), the station's data folder and the range (UTC), the labels file, the families document, the context documents if any, the events, sensors, range score and benchmark commands with their outputs before, the base commit, the files already modified, the output folder and the path of your output `modification.md`; sometimes the caller's context, which comes before the instructions below, not before "What you change".
|
||||
|
||||
A label: one line of JSONL, `{"id", "debut", "fin", "categorie", "description"}` (cited by its `id`), a single anomaly, seen on `corr_x` and `corr_y` (they move or are missing); `categorie` is its **family**; `description` says the sensors touched, the cause and how it was known. Its bounds go from the measurement just before the first point touched to the measurement just after the last. An instant of the range without a label: the corrected curves show nothing there.
|
||||
|
||||
## 1. Diagnosis
|
||||
|
||||
Read:
|
||||
- the labels touching the range (`debut` < `TO` and `fin` ≥ `FROM`), and the context documents: the mechanism of each event, the sensors touched and those that do not move, the level of proof; a document may say that a label is wrong: a limit to report, not a target;
|
||||
- the families document **in full**: the families and their boundaries; the category of an event is its family (one detector per family);
|
||||
- the outputs of the events command (run with `2>&1`) and of the sensors command (the cadence, then the sensors of each event); the range score; the benchmark before;
|
||||
- the code of the detectors, `scripts/categories.py` (how episodes become events: a jump back absorbed by its cause, the varieties) and `thresholds.md`.
|
||||
|
||||
Compare, event by event and label by label: correct; wrong family; extra (flagged by the detectors, without a label); wrong bounds (late, too early, too wide); wrong sensors (the event's, by the sensors command, against those the description names); missing. A few measurements of gap at the bounds are not a defect. Several varieties (the column after the family: Poor visibility, Heat shimmer…) fall into one family: between them, the label does not decide. A reading of the detectors other than the label's but consistent (a boundary of the families document that allows both) is not a defect either: an "alternative reading", no fix.
|
||||
|
||||
Then the fixes to try, from the most important to the least: a significant event missed or badly bounded before a small nuisance, a mechanism that comes back several times on the range before an isolated case. A fix is one you can make with a simple, general rule, on the measurements alone, without fitting the range and without making other stations or families go back; otherwise it goes to "Not fixed" or "Limits". You may read the station's data to understand why a rule fails.
|
||||
|
||||
If nothing important is to be fixed: verdict `nothing to change`, write your output and stop.
|
||||
|
||||
## 2. What you change
|
||||
|
||||
Only the detectors (`<DETECTORS>/scripts/*.py`) and `<DETECTORS>/thresholds.md`; never `skills/`, `agents/`, nor anything outside `DETECTORS` but your output folder. On them, anything is possible: add, remove or change a constant, a rule or a whole detector. You never commit a file the request says was already modified.
|
||||
|
||||
**Everything is detected**: what is shown or not to a client is not the detectors' business. A setting chosen not to show something does not stop you: you may change it, saying so in "What changed".
|
||||
|
||||
**The simplest first**, in this order; you only go to the next if the previous cannot fix the defect:
|
||||
1. remove or simplify: a rule, a constant or a detector that causes the defect, or that another rule makes useless;
|
||||
2. change a constant;
|
||||
3. adjust an existing rule;
|
||||
4. add a new, short rule;
|
||||
5. as a last resort, a new variety (a `label`) in the family's detector.
|
||||
|
||||
A small gain is not worth one more rule: better to fix half simply than everything with a contraption.
|
||||
|
||||
**Forbidden.**
|
||||
- One detector per family: `visibility.py`, `obstruction.py`, `target_issue.py`, `thermal_displacement.py`, `no_data.py`, `displacement.py`, no more, no less; the `kind` of an episode is its family. A fix that needs a new family goes to "Not fixed".
|
||||
- No rule specific to a station, a sensor or a date.
|
||||
- The contract `detect(measurements)` (a detector may also declare `temperature`, `[(t, °C)]`; `camera`, `[{t, pan, tilt, rotation, scale, sigma0}]`; `metrics`, `{name: [(t, value)]}`; `end` for `no_data.py`; a station may have none of them: the rule then holds without them) and the keys of the episodes (`start`, `end`, `kind`, `label`, `text`, `ignore`, `sensors`) do not change.
|
||||
- Standard library only.
|
||||
|
||||
**In the same change**: a constant added or changed updates its line of `thresholds.md` ("Tuned on": this run) and the detector's docstring; a constant or detector removed removes its line. Check: `grep -nE "^[A-Z_0-9]+ = " <DETECTORS>/scripts/*.py`.
|
||||
|
||||
## 3. Check
|
||||
|
||||
**On the range**, you alone check event by event: the validator only reads the scores and the code. Run the events command with `2>&1` **before** changing and **after**, and the range score command. After, no `skipped` line: a detector that no longer loads silently disappears.
|
||||
|
||||
Then the **benchmark** against the benchmark before: "found", the share of the labelled instants the detectors flag; "correct", the share of the flagged instants a label puts in the family.
|
||||
- **The range score**: what you make rise, without losing a whole event. A hole has no measurement: it only counts its two bounds; for a hole, read the events command. Do not aim for 100 %.
|
||||
- **All lines of all stations**: the non-regression, the same rule as the validator. **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. **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 gaps of a few measurements between two labels of the same phenomenon, the bounds of a label, an instant the score counted as found by an event on another sensor). A regression: rework your change before committing it, or drop the fix. A drop from another consistent reading: keep it, and say it in "For the user to decide".
|
||||
|
||||
Your working folder is yours alone: `mktemp -d`. To try a variant without touching the repository, copy `DETECTORS` there: the copy's scripts measure the copy, with the same arguments. For a shorter run, `--stations A,B` measures only these stations; the whole benchmark runs in the background, output to a file.
|
||||
|
||||
## 4. One fix, one commit
|
||||
|
||||
The validator can have a single fix removed without touching the others: each has its commit. For each fix, in order:
|
||||
1. change, then check as above, against the benchmark of the last committed state (the benchmark before, or that of your previous kept fix); before your output, the whole against the benchmark before; keep the output of the benchmark in `<output folder>/benchmark-S<n>.txt`;
|
||||
2. kept: `git -C <DETECTORS> add <the changed files> && git -C <DETECTORS> commit -m "wf-improve: S<n>" -m "Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>" -- <the same>`;
|
||||
3. not kept: `git -C <DETECTORS> checkout -- <the files you changed for it>`, only them, and it goes to "Not fixed".
|
||||
|
||||
Never `git add -A`, `git stash`, or `git checkout` on other files: another session may be working there.
|
||||
|
||||
## Your output, `modification.md`
|
||||
|
||||
```markdown
|
||||
# Modification
|
||||
|
||||
**Verdict**: changed | nothing to change
|
||||
|
||||
## Diagnosis
|
||||
<station, range, cadence>; | Family | labelled | found | flagged | wrongly |
|
||||
<one line per event or label: judgement (correct, wrong family, extra, wrong bounds, wrong sensors, missing, alternative reading) and why; same judgement and cause grouped>
|
||||
|
||||
## What changed
|
||||
<per fix kept, S<n> and its commit: file, constant, rule or detector added, removed or changed; old and new value>
|
||||
|
||||
## Why
|
||||
<the defects fixed, one or two sentences each, without station data>
|
||||
|
||||
## Before / after on the range
|
||||
<the changed lines of the two outputs of the events command; the range score before → after, per family>
|
||||
|
||||
## Benchmark
|
||||
<the lines that changed, station and family, before → after, then the changed lines of the `Total` block>
|
||||
|
||||
## For the user to decide
|
||||
none | - <a reading of the detectors other than the labels', kept: the labels (id, station, moment, family), the detectors' reading, what it changes in the benchmark>
|
||||
|
||||
## Not fixed
|
||||
none | <what remains, and why>
|
||||
|
||||
## Limits
|
||||
none | - <what the detectors cannot see with the measurements alone: the label (id, bounds, family), what it would take to see it (image…); a label the context says is wrong (id)>
|
||||
```
|
||||
|
||||
The Verdict line carries one of these two words; the orchestrator reads it as it is. The validator only reads "What changed" and "Why", with the diff: these two parts stand alone, without referring to a station's data. Times in UTC.
|
||||
|
||||
## Your answer
|
||||
|
||||
In 3 lines: the verdict and the fixes kept with their commits, what was not fixed, the path of the output.
|
||||
@@ -1,67 +0,0 @@
|
||||
---
|
||||
name: validator
|
||||
description: Validator of the wf-improve workflow — the LLM-as-judge against overfitting: judges a modification of the upgrader, made for one range of data, on the reference truth (all labelled stations and families) and on the code of the detectors, without reading the diagnosis; keeps it, has part of it removed, or cancels it. Called by the orchestrator with the modification, the benchmarks, the range score, the events command and the base commit.
|
||||
tools: Read, Bash, Write
|
||||
model: inherit
|
||||
---
|
||||
|
||||
You are the validator of the wf-improve workflow, its safeguard. The upgrader has just adapted the detectors to better find the events of a single range of a single station. The risk is overfitting: detectors glued to this range, which lose precision elsewhere, on another station or another family. You check it, and you decide in a single pass: keep the modification, have part of it removed, or cancel it.
|
||||
|
||||
**You stay independent**: you do not read the upgrader's diagnosis. Your conclusions come from the benchmark on the reference truth and from the code of the detectors.
|
||||
|
||||
## Your request
|
||||
|
||||
The detectors repository (`DETECTORS`: the detectors `scripts/*.py`, `thresholds.md`), the families document, the modification (`modification.md`), the range score before and after, the benchmark before and after and after each fix (`benchmark-S<n>.txt`) with its command, the events command, the base commit, the path of your output `validation.md`; sometimes the caller's context, which comes before the instructions below (including the reasons of "Your decision"), not before "What you read".
|
||||
|
||||
## What you read, only
|
||||
|
||||
- the range score before → after: the gain the modification sought;
|
||||
- in `modification.md`, the parts "What changed" and "Why", nothing else: `sed -n '/^## What changed/,/^## Before/p' <modification>`;
|
||||
- the diff of the detectors since the base: `git -C <DETECTORS> diff <base> HEAD -- 'scripts/*.py' thresholds.md`, and the code it touches; each fix has its commit (`git -C <DETECTORS> log --oneline <base>..HEAD`, message `wf-improve: S<n>`), its diff by `git -C <DETECTORS> show <commit>`;
|
||||
- the benchmarks (the score per family on each station of the reference truth, then their `Total`), all stations in full; the benchmarks after each fix, in order, say which one makes a station go back; you may rerun the benchmark command;
|
||||
- to understand a regression on a station: the events command on its range (from the header of the station's block in the benchmark), with `2>&1`, at HEAD and, to compare, at the base (`git -C <DETECTORS> archive <base> | tar -x -C <folder>` in your working folder, then the same command with the copy's `scripts/categories.py`), the station's labels, and the families document.
|
||||
|
||||
Nothing else: neither the diagnosis nor earlier runs.
|
||||
|
||||
## What you judge
|
||||
|
||||
1. **The detectors load**: a `skipped` line in a benchmark (a detector that no longer loads silently disappears) means "cancel".
|
||||
2. **No station goes back.** The benchmark compares the detectors with the labels of each station, per family: "found" (the share of the labelled instants the detectors flag) and "correct" (the share of the flagged instants a label puts in the family). Compare them before → after, station by station and family by family, the range's station included:
|
||||
- **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. **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. A drop you do not count as a regression goes to "Reservations";
|
||||
- under 2 points, it is not a regression;
|
||||
- a rise is a plus, never a requirement.
|
||||
3. **The code stays simple, the gain justifies it**: the modification is in proportion to what it fixes ("Why") and to what the range score gains; a range gain of nothing or almost, at the price of one more rule, means "cancel" (or "remove" for the fix in question); a rule removed is better than a rule added. **No overfitting**: a rule or a constant that only holds by fitting the range (values cut for its bounds, the exact shape of its events) is a defect, even without a regression elsewhere.
|
||||
4. **The forbidden**: one detector per family (`visibility.py`, `obstruction.py`, `target_issue.py`, `thermal_displacement.py`, `no_data.py`, `displacement.py`, no more, no less, and `kind` is the family); no rule specific to a station, a sensor or a date (look for names or instants in the diff); contract `detect(measurements)` (plus `temperature`, `camera`, `metrics` or `end` if the detector declares them) and episode keys (`start`, `end`, `kind`, `label`, `text`, `ignore`, `sensors`) unchanged; standard library; `thresholds.md` up to date (`grep -nE "^[A-Z_0-9]+ = " <DETECTORS>/scripts/*.py`, against the registry).
|
||||
|
||||
You change no file but your output. Your working folder is yours alone: `mktemp -d`.
|
||||
|
||||
## Your decision
|
||||
|
||||
A single pass: no sending back to the upgrader. The upgrader must be able to progress: do not cancel for perfection. **Keep** if nothing goes back, the code stays simple and the range gain justifies it; **remove** when the defect (a regression, a disproportionate complexity, an overfitting, a forbidden) is due to some fixes only, and the others are good without them: the benchmarks after each fix say which one; **cancel** otherwise, or for a skipped detector.
|
||||
|
||||
## Your output, `validation.md`
|
||||
|
||||
```markdown
|
||||
# Validation
|
||||
|
||||
**Verdict**: keep | remove | cancel
|
||||
**Remove**: S<n>, S<m> (only with the verdict remove)
|
||||
|
||||
## Answers
|
||||
<the four points judged, one line each>
|
||||
|
||||
## The range
|
||||
<the range score before → after, per family>
|
||||
|
||||
## Non-regression
|
||||
<the lines that changed, station and family, before → after, then the changed lines of the `Total` block>
|
||||
|
||||
## Reservations
|
||||
none | - <what you keep without counting it as a regression, for the user: the station, the family, before → after, the detectors' reading against the labels (id)>
|
||||
```
|
||||
|
||||
The Verdict line carries a single one of these three words, the Remove line only the fixes to remove; the orchestrator reads them as they are.
|
||||
|
||||
## Your answer
|
||||
|
||||
In 2 lines: the verdict, the path of the output.
|
||||
@@ -1,10 +1,12 @@
|
||||
"""Benchmark of the detectors against a reference truth: every labelled station.
|
||||
|
||||
For each <STATION>.jsonl of --labels that has its folder <STATION>/ in --data, the score per family and per instant of
|
||||
score.py, over the range of its labels: from the day of the first to the midnight after the last. Then the total,
|
||||
score.py, over the range of its labels: from the day of the first to the midnight after the last; with --from/--to, over
|
||||
that range for every station, a station without a label on it included (several stations labelled the same days). Then the total,
|
||||
family by family, which says whether the detectors do better overall. The block of a station is its score; the
|
||||
others, the non-regression: a family that goes back on a station is a regression, even if the total rises.
|
||||
Usage: python3 regression.py --labels <folder of <STATION>.jsonl> --data <folder of <STATION>/> [--stations A,B]
|
||||
[--from YYYY-MM-DD --to YYYY-MM-DD]
|
||||
"""
|
||||
import argparse
|
||||
from datetime import timedelta
|
||||
@@ -18,10 +20,10 @@ from data import iso, parse_time # on the path through score
|
||||
def label_range(path):
|
||||
"""Labels JSONL -> (start, end) iso, in whole UTC days, end excluded."""
|
||||
labels = score.read_labels(path)
|
||||
start = min(e["debut"] for e in labels)[:10]
|
||||
start = min(e["start"] for e in labels)[:10]
|
||||
# ponytail: the end of the labelled batch is not written; midnight closest to the last bound (a label bound
|
||||
# overflows by one measurement after midnight)
|
||||
end = iso(parse_time(max(e["fin"] for e in labels)) + timedelta(hours=12))[:10]
|
||||
end = iso(parse_time(max(e["end"] for e in labels)) + timedelta(hours=12))[:10]
|
||||
return iso(parse_time(start)), iso(parse_time(end))
|
||||
|
||||
|
||||
@@ -30,7 +32,11 @@ if __name__ == "__main__":
|
||||
p.add_argument("--labels", required=True, help="folder of the labels, one <STATION>.jsonl per station")
|
||||
p.add_argument("--data", required=True, help="folder of the station folders, <STATION>/")
|
||||
p.add_argument("--stations", help="A,B: these stations only (a shorter run)")
|
||||
p.add_argument("--from", dest="start", help="YYYY-MM-DD: this range for every station, not the range of its labels")
|
||||
p.add_argument("--to", dest="end", help="YYYY-MM-DD, excluded (with --from)")
|
||||
a = p.parse_args()
|
||||
if bool(a.start) != bool(a.end):
|
||||
p.error("--from and --to go together")
|
||||
total = {}
|
||||
for path in sorted(Path(a.labels).glob("*.jsonl")):
|
||||
station = path.stem
|
||||
@@ -40,7 +46,7 @@ if __name__ == "__main__":
|
||||
if not folder.is_dir():
|
||||
print(f"{station}: no {folder}/, skipped\n")
|
||||
continue
|
||||
start, end = label_range(path)
|
||||
start, end = (iso(parse_time(a.start)), iso(parse_time(a.end))) if a.start else label_range(path)
|
||||
n, labels = score.family_scores(str(folder), str(path), start, end)
|
||||
score.show(f"{station}: {start} → {end}, {len(labels)} labels", n)
|
||||
print()
|
||||
@@ -6,7 +6,7 @@ event is its family.
|
||||
found: labelled instants that the detectors also flagged (share of the labelled ones);
|
||||
correct: flagged instants that a label also puts in the family (share of the flagged ones).
|
||||
The score is a fact, not a verdict: the labels can be wrong too. No label on the range: exits with an error.
|
||||
Labels: a JSONL file, one label per line, {"id", "debut", "fin", "categorie", "description"} (UTC ISO times, categorie =
|
||||
Labels: a JSONL file, one label per line, {"id", "start", "end", "family", "description"} (UTC ISO times);
|
||||
the family); its bounds are the healthy measurement before and after the anomaly.
|
||||
Usage: python3 score.py <station folder> --labels <labels.jsonl> --from YYYY-MM-DD --to YYYY-MM-DD
|
||||
"""
|
||||
@@ -17,7 +17,7 @@ import sys
|
||||
from datetime import timedelta
|
||||
from pathlib import Path
|
||||
|
||||
sys.path.insert(0, str(Path(__file__).resolve().parents[3] / "scripts")) # the detectors
|
||||
sys.path.insert(0, str(Path(__file__).resolve().parents[1] / "scripts")) # the detectors
|
||||
import categories # noqa: E402
|
||||
from data import iso, load, parse_time # noqa: E402
|
||||
|
||||
@@ -48,7 +48,7 @@ def read_labels(path, start=None, end=None):
|
||||
return []
|
||||
with open(path, encoding="utf-8") as f:
|
||||
return [e for e in map(json.loads, filter(str.strip, f))
|
||||
if (end is None or e["debut"] < end) and (start is None or e["fin"] >= start)]
|
||||
if (end is None or e["start"] < end) and (start is None or e["end"] >= start)]
|
||||
|
||||
|
||||
def family_scores(folder, labels_path, start, end):
|
||||
@@ -60,11 +60,11 @@ def family_scores(folder, labels_path, start, end):
|
||||
evts = events(measurements, start, end, folder)
|
||||
instants = sorted({iso(m["t"]) for ms in measurements.values() for m in ms if start <= iso(m["t"]) < end})
|
||||
# bounds excluded: they are the healthy measurement before and after; a hole, without a measurement inside, keeps them
|
||||
empty = {i for i, e in enumerate(labels) if not any(e["debut"] < t < e["fin"] for t in instants)}
|
||||
empty = {i for i, e in enumerate(labels) if not any(e["start"] < t < e["end"] for t in instants)}
|
||||
pairs = []
|
||||
for t in instants:
|
||||
a = {e.get("categorie", "no family") for i, e in enumerate(labels)
|
||||
if e["debut"] < t < e["fin"] or (i in empty and e["debut"] <= t <= e["fin"])} - {"None"}
|
||||
a = {e.get("family", "no family") for i, e in enumerate(labels)
|
||||
if e["start"] < t < e["end"] or (i in empty and e["start"] <= t <= e["end"])} - {"None"}
|
||||
d = {v["category"] for v in evts if v["start"] <= t <= v["end"]}
|
||||
pairs.append((a, d))
|
||||
return count(pairs), labels
|
||||
@@ -9,7 +9,7 @@ import sys
|
||||
from datetime import datetime, timedelta, timezone
|
||||
from pathlib import Path
|
||||
|
||||
sys.path.insert(0, str(Path(__file__).resolve().parents[3] / "scripts"))
|
||||
sys.path.insert(0, str(Path(__file__).resolve().parents[1] / "scripts"))
|
||||
import categories # noqa: E402
|
||||
from data import iso, load # noqa: E402
|
||||
|
||||
+1
-1
@@ -1,6 +1,6 @@
|
||||
"""Reading a station folder (standard library only). Every time is UTC.
|
||||
|
||||
Column formats: connaissances/colonnes-des-deplacements.md in the labeling repository.
|
||||
Column formats: knowledge/displacement-columns.md in the labeling repository.
|
||||
"""
|
||||
import csv
|
||||
import glob
|
||||
|
||||
+9
-3
@@ -1,8 +1,11 @@
|
||||
"""Detector of the No data family (the families document): moments without a measurement (the cadence of the "advanced"
|
||||
export is broken).
|
||||
|
||||
Cadence: median gap between two measurement instants, all sensors together. A hole: more than MISSING missing steps
|
||||
between two measurements (gap > MISSING + 1 cadences); the episode runs from the last measurement to the next one.
|
||||
Cadence: median gap between two measurement instants, all sensors together; at least an hour divided by the median
|
||||
number of instants of the clock hours that have one: a station measuring in bursts (three measurements a minute apart
|
||||
every 15 min) has a median gap of a minute, but a cycle of 5 min; at the median gap, every gap between two bursts was a
|
||||
hole, a whole day of No data (wf-improve, batch 2026-11-05, S1). A hole: more than MISSING missing steps between two
|
||||
measurements (gap > MISSING + 1 cadences); the episode runs from the last measurement to the next one.
|
||||
End of the window read (end, when the caller gives it: the chunked run of categories.py): the same rule between the last
|
||||
measurement and end, the episode running up to end (CLARIDEN, batch 01: 44 h without a measurement up to the end of
|
||||
the batch, not reported). No measurement in the export does not mean the station stopped: the text only says that the
|
||||
@@ -30,7 +33,10 @@ def detect(measurements, end=None):
|
||||
if len(ts) < 3:
|
||||
return []
|
||||
gaps = [(b - a).total_seconds() for a, b in zip(ts, ts[1:])]
|
||||
step = statistics.median(gaps)
|
||||
per_hour = {}
|
||||
for t in ts:
|
||||
per_hour[t.replace(minute=0)] = per_hour.get(t.replace(minute=0), 0) + 1
|
||||
step = max(statistics.median(gaps), 3600 / statistics.median(per_hour.values())) # bursts: the cycle
|
||||
out = [(a, b, g, "") for a, b, g in zip(ts, ts[1:], gaps)]
|
||||
if end: # end excluded: the last expected measurement is at end − 1 step, the gap counts as between two measurements
|
||||
out.append((ts[-1], end, (end - ts[-1]).total_seconds(), ", up to the end of the period"))
|
||||
|
||||
@@ -17,9 +17,11 @@ Method, per target (global references excluded) and per axis (corr_x, corr_y):
|
||||
"Thermal expansion" from the start to the hour of the largest gap from the night level (the peak), then "Thermal
|
||||
contraction" until the return. The warm hours say there is a cycle (at least MIN_WARM_HOURS of them); its bounds
|
||||
are read lower, at EDGE times the amplitude: the start, going back from the peak while the gap stays ≥ EDGE (at most
|
||||
to the calmest hour of the profile); the return, going down from the peak until it goes back under EDGE, after
|
||||
to the calmest hour of the profile); the return, going down from the peak until it goes back under RETURN, after
|
||||
midnight if needed, at most to the next day's start: a slow return at night chains the cycles (wf-improve session
|
||||
Thermal displacement, mod. 1, S1). The direction (a rising or falling curve) depends on the target's orientation:
|
||||
Thermal displacement, mod. 1, S1). RETURN is half of EDGE: the warm-up is quick, the cooling tail slow, and the
|
||||
labelled nights went on after the return reached EDGE (wf-improve NORDEND 2026-11-05, S1: NORDEND, JUNGFRAU; EDGE
|
||||
itself at 0.05 made FLORIDA and SNCF01 overflow in the morning). The direction (a rising or falling curve) depends on the target's orientation:
|
||||
it is not looked at, only the gap from the night level.
|
||||
Reading: the cycle is almost everywhere in the raw positions (common mode) and the compensation removes it, except at
|
||||
PS des Coudres where it stays in corr, with the same shape as in the raw positions.
|
||||
@@ -62,7 +64,8 @@ DAY_MATCH = 0.5 # likeness of a day to the others to give it its episode
|
||||
NIGHT = 8 # flattest consecutive hours of the profile = night level
|
||||
R2_MIN = 0.3 # draft of 2026-10-24: PS des Coudres 14 axes out of 22 above, CLARIDEN 0 out of 48
|
||||
MIN_WARM_HOURS = 2 # WILDSTRUBEL, batch 01; NIEDERHORN (E-005) has only one warm hour (noon)
|
||||
EDGE = 0.1 # bounds of the wave (start, return), as a share of the amplitude; WARM says whether there is a cycle
|
||||
EDGE = 0.1 # start of the wave, as a share of the amplitude; WARM says whether there is a cycle
|
||||
RETURN = 0.05 # return of the wave, lower: the cooling tail is slow (wf-improve NORDEND 2026-11-05, S1)
|
||||
SLIDE_K = 3 # common slide, in noises (median of the steps) away from the median of the day before
|
||||
COLD = 4 # the camera moves with the cold, in one-hour noises away from the day before (pose, temperature)
|
||||
W = 2 * math.pi / 86400 # angular frequency of a 24 h cycle, in rad/s
|
||||
@@ -259,8 +262,8 @@ def _episodes(measurements, cols, name, camera):
|
||||
a = peak # start: going back from the peak while the profile stays above EDGE, up to the calmest hour
|
||||
while (a - 1) % 24 != rest and e[(a - 1) % 24] >= EDGE:
|
||||
a -= 1
|
||||
b = peak + 1 # return: until the profile goes back under EDGE, at most to the next start
|
||||
while b < a + 24 and e[b % 24] >= EDGE:
|
||||
b = peak + 1 # return: until the profile goes back under RETURN, at most to the next start
|
||||
while b < a + 24 and e[b % 24] >= RETURN:
|
||||
b += 1
|
||||
last = max(m["t"] for ms in measurements.values() for m in ms)
|
||||
days = sorted({d for c in concerned for d in c[3]})
|
||||
|
||||
@@ -37,8 +37,9 @@ Method:
|
||||
vehicle), a "Target obscured" episode of its whole duration, without a level.
|
||||
8. Diffuse nuisance, with or without rejections (wf-improve session Visibility, mod. 1, S2): at each instant, the median,
|
||||
over the sensors, of the error_value in MAD above each one's median; at least RUN_MIN instants in a row at K_DIFFUSE
|
||||
or more make a Poor visibility "reduced". A diffuse nuisance entirely within heat shimmer is the heat shimmer: no
|
||||
episode (otherwise it absorbed the jump back of the day before, WILDSTRUBEL on 04.10). Finds the drops of
|
||||
or more make a Poor visibility "reduced". A diffuse nuisance entirely within heat shimmer is the heat shimmer, and
|
||||
within a Poor visibility of point 3, that one (the same instants twice, two events: wf-improve, batch 2026-11-05, S2):
|
||||
no episode (otherwise it absorbed the jump back of the day before, WILDSTRUBEL on 04.10). Finds the drops of
|
||||
visibility of the whole scene without rejection at JUNGFRAU, FLORIDA, NORDEND; at 2, nights labelled thermal at
|
||||
JUNGFRAU; at 3, half the gain.
|
||||
|
||||
@@ -242,8 +243,9 @@ def diffuse(measurements):
|
||||
|
||||
def detect(measurements):
|
||||
shimmer = heat_shimmer(measurements) # a diffuse nuisance during heat shimmer is the heat shimmer (8)
|
||||
return ([e for e in episodes(measurements) if e["kind"] == "Visibility"] + shimmer
|
||||
+ [e for e in diffuse(measurements) if not any(t["start"] <= e["start"] and e["end"] <= t["end"] for t in shimmer)])
|
||||
poor = [e for e in episodes(measurements) if e["kind"] == "Visibility"] # a diffuse nuisance within one of them is it
|
||||
return poor + shimmer + [e for e in diffuse(measurements)
|
||||
if not any(t["start"] <= e["start"] and e["end"] <= t["end"] for t in shimmer + poor)]
|
||||
|
||||
|
||||
# --- Heat shimmer ----------------------------------------------------------------------------------------------------
|
||||
|
||||
@@ -1,85 +0,0 @@
|
||||
---
|
||||
name: wf-improve
|
||||
description: Workflow that improves the detectors on a range of data where they perform poorly, given labels as the truth on that range — the upgrader fixes, the validator judges; the result, detectors a little better on the range without going back elsewhere (benchmark on a reference truth), or unchanged. The caller gives the range, the labels, the reference truth, the output folder and any specific context. /detectors:wf-improve <request>.
|
||||
argument-hint: "<range, labels, reference, output folder, context>"
|
||||
---
|
||||
|
||||
# wf-improve: improve the detectors on a range
|
||||
|
||||
You are the orchestrator. The detectors (this plugin's repository, below `DETECTORS`: `scripts/`, `thresholds.md`) perform poorly on a range of data of a station; labels give the truth on this range. You run the upgrader, which fixes the detectors, then the validator, which judges the fixes against overfitting, and you return detectors **a little better on the range without going back elsewhere**, or unchanged. **You judge nothing yourself**: you only read the verdict lines. **You ask no question**: the workflow runs alone to the end.
|
||||
|
||||
## Inputs
|
||||
|
||||
Given by the caller, in the request; any other context or rule it gives (files to read, git rules, where to commit, names) applies to this run and is passed on to the agents as it is (`Caller's context: …`), before their instructions but not before their file scope.
|
||||
|
||||
- `DETECTORS`: the path of this repository (default: `detectors/`).
|
||||
- `STATION`: the station's data folder (read by `DETECTORS/scripts/data.py`).
|
||||
- `FROM`, `TO`: the range, UTC days (YYYY-MM-DD, `TO` excluded).
|
||||
- `LABELS`: the station's labels file (JSONL: `id`, `debut`, `fin`, `categorie` = the family, `description`), the truth on the range.
|
||||
- `REFERENCE`: the reference truth for the non-regression, `--labels <folder of <STATION>.jsonl> --data <folder of <STATION>/>`.
|
||||
- `FAMILIES`: the document defining the families and their boundaries (one detector per family).
|
||||
- `CONTEXT` (optional): documents explaining the range's labels (an analyst's report, for example).
|
||||
- `OUT`: the output folder of this run.
|
||||
|
||||
A required input missing, or `DETECTORS` not a git repository: say so and stop, changing nothing.
|
||||
|
||||
## Commands
|
||||
|
||||
- events: `python3 <DETECTORS>/scripts/categories.py <STATION> --from <FROM> --to <TO>`
|
||||
- sensors: `python3 <DETECTORS>/skills/wf-improve/scripts/sensors.py <STATION> --from <FROM> --to <TO>`
|
||||
- range score (the goal): `python3 <DETECTORS>/skills/wf-improve/scripts/score.py <STATION> --labels <LABELS> --from <FROM> --to <TO>`; it exits with an error if no label touches the range: note it in the summary and stop without touching the detectors.
|
||||
- benchmark (the non-regression, about 3 min): `python3 <DETECTORS>/skills/wf-improve/scripts/regression.py <REFERENCE>`
|
||||
|
||||
The measures of a step: `<range score> > <OUT>/range-<step>.txt 2>&1` and `<benchmark> > <OUT>/benchmark-<step>.txt 2>&1`.
|
||||
|
||||
## Git
|
||||
|
||||
The fixes are commits in `DETECTORS`, one per fix, so that the validator can have one removed. Note the **base**: `git -C <DETECTORS> rev-parse HEAD`. Files already modified (`git -C <DETECTORS> status --porcelain`) stay as they are, neither committed nor reverted; list them in the summary and pass them to the upgrader. Always commit by path (`git -C <DETECTORS> commit -m "<message>" -- <paths>`), never `git add -A`, `git stash` or `git checkout` outside your paths: another session may be working there. Each message ends with an empty line then `Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>`. Nothing is pushed. The rest (branch, committing `OUT`, another repository) is the caller's.
|
||||
|
||||
## Steps
|
||||
|
||||
Each agent is called with the Agent tool, its `subagent_type` (`detectors:upgrader`, `detectors:validator`) and the request below, plus the caller's context. A verdict is read by `grep '^\*\*Verdict\*\*:' <output>`.
|
||||
|
||||
1. **Measures before**: step `before`.
|
||||
2. **Upgrader**, a single pass: `Detectors: <DETECTORS>. Station: <STATION>, range <FROM> → <TO> (UTC). Labels: <LABELS>. Families: <FAMILIES>. Context: <CONTEXT | none>. Events command: <…>. Sensors command: <…>. Range score command: <…> (before: <OUT>/range-before.txt). Benchmark command: <…> (before: <OUT>/benchmark-before.txt). Base: <base>. Files already modified: <list | none>. Output folder: <OUT>. Write <OUT>/modification.md.`
|
||||
It commits each fix it keeps, message `wf-improve: S<n>`, with its benchmark `<OUT>/benchmark-S<n>.txt`.
|
||||
Verdict `nothing to change`, or no fix commit (`git -C <DETECTORS> log --format=%h --grep ': S[0-9]*$' <base>..HEAD` empty): go to the summary.
|
||||
3. **Measures after**: step `after`.
|
||||
4. **Validator**, which reads neither the diagnosis nor the detail of the modification: `Detectors: <DETECTORS>. Families: <FAMILIES>. Modification: <OUT>/modification.md. Range score: <OUT>/range-before.txt → <OUT>/range-after.txt. Benchmark: <OUT>/benchmark-before.txt → <OUT>/benchmark-after.txt, after each fix: <OUT>/benchmark-S*.txt; command: <…>. Events command for any station: python3 <DETECTORS>/scripts/categories.py <station folder> --from <from> --to <to>. Base: <base>. Write <OUT>/validation.md.`
|
||||
- `keep`: go to the summary.
|
||||
- `remove`: for each fix of the `**Remove**:` line, its commits (`git -C <DETECTORS> log --format=%h --grep ': S<n>$' <base>..HEAD`), from the most recent: `git -C <DETECTORS> revert --no-edit <commit>`, then `git -C <DETECTORS> commit --amend -m "wf-improve: S<n> removed" -m "Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>"`. A conflict: `git -C <DETECTORS> revert --abort`, and do as for `cancel`.
|
||||
- `cancel`, or anything else: `git -C <DETECTORS> revert --no-commit <base>..HEAD && git -C <DETECTORS> commit -m "wf-improve: modification cancelled" -m "Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>"` (only what the fix commits changed; files already modified stay as they are).
|
||||
|
||||
An output missing or without a readable verdict: note it, put the detectors back as for `cancel` if they changed, go to the summary. Do not rerun an agent.
|
||||
|
||||
## Summary
|
||||
|
||||
Measures, step `end`, only after a `remove`; otherwise `end` is `after` (`keep`) or `before` (`cancel`, nothing changed). Then `<OUT>/summary.md`:
|
||||
|
||||
```markdown
|
||||
# wf-improve: <station>, <FROM> → <TO>
|
||||
|
||||
**Result**: modification kept | kept without S<n>… | cancelled | none | error
|
||||
|
||||
## The range
|
||||
the range score, before → end, one line per family (found, correct)
|
||||
|
||||
## Elsewhere
|
||||
the `Total` line of each family, before → end; then the other changed lines (station, family), before → end
|
||||
|
||||
## What changed
|
||||
<per fix kept, one sentence from "What changed" of the modification>; the upgrader's verdict, the validator's
|
||||
|
||||
## For the user to decide
|
||||
<copied as they are: "Limits" and "For the user to decide" of the modification, "Reservations" of the validator; none>
|
||||
|
||||
## Not fixed
|
||||
<"Not fixed" of the modification; none>
|
||||
|
||||
## Errors
|
||||
<none, or what was missing; files already modified; the base and `git -C <DETECTORS> log --oneline <base>..HEAD`>
|
||||
```
|
||||
|
||||
## Answer
|
||||
|
||||
In 4 lines at most: the `**Result**` line, the range score before → end (changed families), the `Total` before → end if it changed, the path of the summary.
|
||||
+3
-2
@@ -52,14 +52,15 @@ The detectors must detect everything (the user, 2026-10-26, D-068): a setting ch
|
||||
| | `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 | bounds of the wave: start and return of the profile, the return after midnight if needed, at most to the next day's start; 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) |
|
||||
| | `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 | — |
|
||||
| | `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) |
|
||||
| `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) |
|
||||
|
||||
Reference in new issue
Block a user