From 4e119cb1b0fc0cebf94e397d58ed859ad3942af1 Mon Sep 17 00:00:00 2001 From: maxime Date: Mon, 16 Nov 2026 13:20:31 +0100 Subject: [PATCH] Analyst: the labeling scripts are in labeling/scripts/ Co-Authored-By: Claude Opus 5.5 --- agents/analyst.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/agents/analyst.md b/agents/analyst.md index 25e7ea4..382619f 100644 --- a/agents/analyst.md +++ b/agents/analyst.md @@ -30,7 +30,7 @@ The repository you are called from carries the links `data/` (the stations), `la - `labeling/reading-rules.md` (**in full**): what the data mean: the measurement chain, the thermal effects, the gaps, the reading rules, the false friends, the lessons of cases; - `labeling/stations.md` (**in full**): the structure, camera, references and neighbours of each station; - `labeling/auto/.jsonl`, for the labels already written on the range and at its edges: those already there stay; do not redo a right label; a label you believe wrong, say so in your analysis. An event already labelled just before the range is extended, not redone; -- the **precedents**, with `python3 labeling/precedents.py "" --exclude ` (`--family`, `--k` as needed): the labels already written in `labeling/auto/`, all stations, closest in meaning to your description; each with its provenance (`auto, reviewed on …`, `auto, not reviewed`); +- the **precedents**, with `python3 labeling/scripts/precedents.py "" --exclude ` (`--family`, `--k` as needed): the labels already written in `labeling/auto/`, all stations, closest in meaning to your description; each with its provenance (`auto, reviewed on …`, `auto, not reviewed`); - what your instructions add. All the labeling knowledge is in `labeling/`: nothing else, neither `labeling/manual/` (the user's own labels, for him alone: no process uses them), nor `CLAUDE.md`, nor the other analyses; the detectors only with `DETECTORS: yes`. What is measured is what you draw from the data with the documentation. You list what you read in "Sources read". @@ -57,7 +57,7 @@ One JSON line per label, in `/labels.jsonl`, in the format of the - **The rules of a label are those of `labeling/labeling-rules.md`**: what is labelled, the bounds, a single event, the family, the description, the stated cause. They prevail over your intuition. - The whole range is read: an instant without a label means that `corr_x` and `corr_y` show nothing there. -Before answering, `python3 labeling/validate.py /labels.jsonl` must say 0 errors. +Before answering, `python3 labeling/scripts/validate.py /labels.jsonl` must say 0 errors. ## Your analysis