wf-improve: several stations on the same range (DATA, STATIONS, a labels folder); regression.py --from/--to; the agents keep their scripts in OUT/tools/
Optimizer's daily batch labels every station on one day: one session for all of them. The single-station request (Diagnostic-app) is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
c7e34b49f7
commit
887b313ba2
5 files changed
+32
-11
No files matched your search
+4
-1
@@ -33,7 +33,7 @@ Nothing else: neither the diagnosis nor earlier runs.
|
||||
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`.
|
||||
You change no file but your output and your scripts. Your working folder is yours alone: `mktemp -d`. A script you write to read the data or to check a rule (anything longer than a one-line command) is a file in `<the folder of your output>/tools/`, its first line saying what it does, and runs from there, never inline (heredoc, `python3 -c`): the caller keeps these scripts to reuse them; your output lists them (`## Tools`).
|
||||
|
||||
## Your decision
|
||||
|
||||
@@ -58,6 +58,9 @@ A single pass: no sending back to the upgrader. The upgrader must be able to pro
|
||||
|
||||
## 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)>
|
||||
|
||||
## Tools
|
||||
none | - <`tools/<script>`: what it does, its arguments; worth keeping as a workflow tool or not>
|
||||
```
|
||||
|
||||
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.
|
||||
|
||||
Reference in new issue
Block a user