review is now the date the user validated a label in aimsight-app; the agents' review dates removed from auto/

Quality over quantity: only the analyses discussed and validated in the app are marked. validate.py no longer
requires review; precedents.py gives the provenance as validated by the user or not.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
maximeandClaude Opus 5.5 committed 2026-11-17 10:01:22 +01:00
1 parent 542e91ccb2
commit bed0f7d09e
15 files changed
+1007 -1005

No files matched your search

+2 -2
View File
@@ -2,7 +2,7 @@
The AIMsight displacement labels and all the domain knowledge to place them, in a single copy on the workstation.
- `manual/<STATION>.jsonl`: the expert's labels, for him alone: no process and no agent uses them; `auto/<STATION>.jsonl`: those of the Support-Agent `etiqueteur`, reviewed (`review`), and those submitted by the aimsight-app `analyst`, without `review` until they are reviewed; one label per line, `{"id", "start", "end", "family", "description", ...}`, UTC times, `family` = the family.
- `manual/<STATION>.jsonl`: the expert's labels, for him alone: no process and no agent uses them; `auto/<STATION>.jsonl`: those of the Support-Agent `etiqueteur` and those submitted by the aimsight-app `analyst`; `review` is the date the user validated a label in aimsight-app (quality over quantity: only the analyses discussed and validated there), and any change removes it; the agents' reviews of 2026-11-04 and 2026-11-05 were removed on 2026-11-17 (in the history); one label per line, `{"id", "start", "end", "family", "description", ...}`, UTC times, `family` = the family.
- `auto/analyses/<STATION>_<start>_<end>/`: the analyses launched from the Data page of aimsight-app (`work/` outside git).
- The knowledge, one source per kind, maintained by hand by the user; the analyst reads the four files in full:
@@ -15,7 +15,7 @@ The AIMsight displacement labels and all the domain knowledge to place them, in
| The installation of each station | `stations.md` |
| What the data are: files, columns, image quality, images | `tools/DATA.md` (tools repository) |
- `scripts/`: `validate.py` (the labels against the rules; `check` for one label), `ids.py` (the stable id of each), `client.py` (what the client is told of a detectors' event).
- `scripts/precedents.py`: the RAG of the labels. The labels of `auto/` closest in meaning to a text, with their provenance (reviewed or not); `--exclude STATION START END` leaves out the analyzed range. bge-m3 model of the Ollama container `ollama-bge-m3` (started by the script itself if it does not answer; port 11435); the `.index/` index, outside git, updates itself at every call (only new or modified labels go through the model; ~8 min to redo everything on CPU).
- `scripts/precedents.py`: the RAG of the labels. The labels of `auto/` closest in meaning to a text, with their provenance (validated by the user or not); `--exclude STATION START END` leaves out the analyzed range. bge-m3 model of the Ollama container `ollama-bge-m3` (started by the script itself if it does not answer; port 11435); the `.index/` index, outside git, updates itself at every call (only new or modified labels go through the model; ~8 min to redo everything on CPU).
aimsight-app and Optimizer reach it through a link `labeling -> ~/aimsight-labeling`, ignored by git: aimsight-app reads and writes there (labels, analyses), Optimizer only reads; commits are made here. The scripts run from here (`python3 scripts/validate.py`) or through the link (`python3 labeling/scripts/validate.py`). Descriptions are written in English from now on.