Dépôts renommés avec le préfixe aimsight- : chemins et noms mis à jour

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
maximeandClaude Opus 5.5 committed 2026-11-16 14:56:41 +01:00
1 parent 7591488173
commit 69cba19cdc
5 files changed
+10 -10

No files matched your search

+3 -3
View File
@@ -1,8 +1,8 @@
# CLAUDE.md
labeling: the AIMsight displacement labels and the knowledge to place them, in a single copy on the workstation (`README.md`). Diagnostic-App reads and writes there, Optimizer only reads, both through a link `labeling -> ~/labeling`; commits are made here.
labeling: the AIMsight displacement labels and the knowledge to place them, in a single copy on the workstation (`README.md`). aimsight-app reads and writes there, Optimizer only reads, both through a link `labeling -> ~/aimsight-labeling`; commits are made here.
- **The labels**: `manual/<STATION>.jsonl` (the expert, for him alone), `auto/<STATION>.jsonl` (the agents, reviewed by `review`), one per line, `{"id", "start", "end", "family", "description", ...}`. The Diagnostic-App analyses: `auto/analyses/<STATION>_<start>_<end>/`.
- **The labels**: `manual/<STATION>.jsonl` (the expert, for him alone), `auto/<STATION>.jsonl` (the agents, reviewed by `review`), one per line, `{"id", "start", "end", "family", "description", ...}`. The aimsight-app analyses: `auto/analyses/<STATION>_<start>_<end>/`.
- **The knowledge**, one source per kind (`README.md`), maintained by hand: `families.md` (the families, their boundaries, the catalogue of phenomena), `labeling-rules.md` (bounds, a single event, description, stated cause), `reading-rules.md` (what the data mean), `stations.md` (the installations); the cases are the labels, through `precedents.py`; what the data are: `tools/DATA.md`. A piece of knowledge lives in one of them only.
- **The tools**, standard library: `python3 scripts/validate.py [STATION | file.jsonl]` (the rules), `python3 scripts/ids.py [STATION]` (the stable id of new labels), `python3 scripts/precedents.py "<text>" [--exclude STATION START END] [--family F] [--k N]` (the RAG; it starts the Ollama container `ollama-bge-m3` by itself if it does not answer; `--check` without it).
- **Verify**: `python3 scripts/validate.py` (today 19 expected errors: the labels submitted by the app without `review`) and `python3 scripts/precedents.py --check`.
@@ -12,5 +12,5 @@ Rules:
- A label added to `auto/` goes through `ids.py` then `validate.py`; an id never changes.
- Every time is in UTC; descriptions in words, without numeric values; written in English from now on.
- No rule specific to a station, a target or a date in the rules and the families.
- Commit by path, never `git add -A`: Diagnostic-App writes here at the same time.
- Commit by path, never `git add -A`: aimsight-app writes here at the same time.
- Language: English.
+4 -4
View File
@@ -2,8 +2,8 @@
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 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).
- `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.
- `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:
| Kind of knowledge | Source |
@@ -17,8 +17,8 @@ The AIMsight displacement labels and all the domain knowledge to place them, in
- `scripts/`: `validate.py` (the labels against the rules), `ids.py` (the stable id of each).
- `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).
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. 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.
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.
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.
History taken from Support-Agent (the `labeling/` folder, up to commit 48a3092), then the state of aimsight-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 (not built), the label map and `knowledge/`, archived on 2026-11-16.
+1 -1
View File
@@ -1,6 +1,6 @@
# The labeling rules
How to place a label: the only source of these rules for the Diagnostic-App `analyst` (before it, the Support-Agent `etiqueteur`) and for those who review their labels. The families, their boundaries and the catalogue of phenomena are in `families.md`; what the data mean, in `reading-rules.md`.
How to place a label: the only source of these rules for the aimsight-app `analyst` (before it, the Support-Agent `etiqueteur`) and for those who review their labels. The families, their boundaries and the catalogue of phenomena are in `families.md`; what the data mean, in `reading-rules.md`.
Sources in brackets: [instruction] the section "Les étiquettes" of `.claude/agents/etiqueteur.md`; [cross <family>] the cross review of 2026-11-04, `auto/revue-croisee/2026-11-04/<family>/revue.md`; [finishing <folder>] its finishing pass, `auto/revue-croisee/2026-11-04/finition/<folder>/revue.md`; [<STATION>] the station review, `auto/revue/<STATION>_<start>/revue.md`; [consistency] that of BREITHORN, MICHIGAN and NEBRASKA; [expert] a label or an answer of the expert.
+1 -1
View File
@@ -11,7 +11,7 @@ import json
import os
import sys
AUTO = os.path.join(os.path.dirname(os.path.dirname(os.path.abspath(__file__))), "auto") # ~/labeling/auto, or through the labeling/ link
AUTO = os.path.join(os.path.dirname(os.path.dirname(os.path.abspath(__file__))), "auto") # ~/aimsight-labeling/auto, or through the labeling/ link
def id_first(e):
+1 -1
View File
@@ -16,7 +16,7 @@ import os
import re
import sys
AUTO = os.path.join(os.path.dirname(os.path.dirname(os.path.abspath(__file__))), "auto") # ~/labeling/auto, or through the labeling/ link
AUTO = os.path.join(os.path.dirname(os.path.dirname(os.path.abspath(__file__))), "auto") # ~/aimsight-labeling/auto, or through the labeling/ link
FAMILIES = {"Visibility", "Obstruction", "Thermal displacement", "Displacement", "Target issue", "No data"}
DATE = re.compile(r"^\d{4}-\d\d-\d\dT\d\d:\d\dZ$")