Analyst knowledge: reading-rules.md, stations.md, a phenomenon catalogue in families.md; the label map and knowledge/ archived
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
1c8479d962
commit
4688d8ab9e
16 files changed
+201
-17
No files matched your search
@@ -4,12 +4,21 @@ The AIMsight displacement labels and all the domain knowledge to place them, in
|
||||
|
||||
- `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 Diagnostic-App `analyst`, without `review` until they are reviewed; 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 Diagnostic-App (`work/` outside git).
|
||||
- `families.md`, `labeling-rules.md`, `label-map.md`, `knowledge/`: how to label, what the labels have taught.
|
||||
- The knowledge, one source per kind, maintained by hand by the user; the analyst reads the four files in full:
|
||||
|
||||
| Kind of knowledge | Source |
|
||||
|---|---|
|
||||
| The cases | the labels of `auto/`, through `precedents.py` |
|
||||
| The families, their boundaries, the catalogue of phenomena | `families.md` |
|
||||
| How to place a label | `labeling-rules.md` |
|
||||
| What the data mean: measurement chain, gaps, reading rules, false friends | `reading-rules.md` |
|
||||
| The installation of each station | `stations.md` |
|
||||
| What the data are: files, columns, image quality, images | `tools/DATA.md` (tools repository) |
|
||||
- `validate.py` (the labels against the rules), `ids.py` (the stable id of each).
|
||||
- `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).
|
||||
|
||||
Diagnostic-App and Optimizer reach it through a link `labeling -> ~/labeling`, ignored by git: Diagnostic-App reads and writes there (labels, analyses), Optimizer only reads; commits are made here. `validate.py` and `ids.py` run from here or through the link (`python3 labeling/validate.py`). Descriptions are written in English from now on.
|
||||
|
||||
History taken from Support-Agent (the `labeling/` folder, up to commit 48a3092), then the state of Diagnostic-App on 2026-11-13 (462ba9e): the archives of the etiqueteur and of the reviews (`auto/etiqueteur/`, `auto/revue/`, `auto/revue-croisee/`) and the old `labeling.py` tool remain in the history. The notes cite their sources as they were in Support-Agent (`docs/…`, `events/`, `run.md`, `agent-diagnostic/`, the skills `/labels-map`, `/review-auto-labels`, `/review-event`…): paths of that repository, obsolete, kept read-only.
|
||||
History taken from Support-Agent (the `labeling/` folder, up to commit 48a3092), then the state of Diagnostic-App on 2026-11-13 (462ba9e): the archives of the etiqueteur and of the reviews (`auto/etiqueteur/`, `auto/revue/`, `auto/revue-croisee/`) and the old `labeling.py` tool remain in the history.
|
||||
|
||||
`docs/archive/`: the design and plan of the labeler, archived on 2026-11-16 (not built).
|
||||
`docs/archive/`: the design and plan of the labeler (not built), the label map and `knowledge/`, archived on 2026-11-16.
|
||||
Reference in new issue
Block a user