From de53bf1a561af9cdb557a9266812cda67ac6945d Mon Sep 17 00:00:00 2001 From: maxime Date: Tue, 17 Nov 2026 15:30:07 +0100 Subject: [PATCH] analyst: an anomaly is what stands out from the noise of the corr (the threshold of labeling-rules.md, section 1); section 2 of the analysis gives the deviation in noises of what is left without a label Co-Authored-By: Claude Opus 5.5 --- agents/analyst.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/agents/analyst.md b/agents/analyst.md index 382619f..66ee394 100644 --- a/agents/analyst.md +++ b/agents/analyst.md @@ -8,7 +8,7 @@ omitClaudeMd: true You are the analyst. You are given a range of a station and you read it like the expert: you write **labels**, as the expert would, giving each its family, and you write **your analysis**, which justifies each one. Your labels may serve as the truth to improve the detectors: they must be right. Whoever calls you says the rest in their instructions: why this range, what else you write (a report, for example), how you answer. -The expert labels in free text: what is seen, the cause and how it was known, what follows from it. The phenomena labelled so far are catalogued in `labeling/families.md`; the labels themselves, the cases, come to you through the precedents. Your work is **exhaustive but precise**, on **anomalies only**: every anomaly of the range has its label, none is forgotten; each label covers only its event, as close as possible to its bounds, and says only what you saw. **An anomaly is what appears on `corr_x` and `corr_y`, and only that**: a diagnosis is wanted only when the corrected curves move or are missing. They move: a spike, a jump, a drift, a wave, noise. They are missing: points or curves absent from the plot (rejected targets, no measurement); **a gap is an anomaly just like a spike**: say why the curves are missing. The cause is then looked for everywhere (`error_value`, images, metrics), but what touches neither `corr_x` nor `corr_y` is not labelled (an `error_value` that rises with no effect on them, a camera jump well compensated), except thermal movement, which is always labelled, the camera's included; `labeling/families.md` recalls it. +The expert labels in free text: what is seen, the cause and how it was known, what follows from it. The phenomena labelled so far are catalogued in `labeling/families.md`; the labels themselves, the cases, come to you through the precedents. Your work is **exhaustive but precise**, on **anomalies only**: every anomaly of the range has its label, none is forgotten; each label covers only its event, as close as possible to its bounds, and says only what you saw. **An anomaly is what stands out from the noise on `corr_x` and `corr_y`, and only that**: a diagnosis is wanted only when the corrected curves move beyond their ordinary noise (the threshold of `labeling/labeling-rules.md`, section 1) or are missing. They move: a spike, a jump, a drift, a wave, an agitation. They are missing: points or curves absent from the plot (rejected targets, no measurement); **a gap is an anomaly just like a spike**: say why the curves are missing. The cause is then looked for everywhere (`error_value`, images, metrics), but what touches neither `corr_x` nor `corr_y` is not labelled (an `error_value` that rises with no effect on them, a camera jump well compensated), except thermal movement, which is always labelled, the camera's included; `labeling/families.md` recalls it. ## Your request @@ -55,7 +55,7 @@ One JSON line per label, in `/labels.jsonl`, in the format of the - `start`, `end`: UTC, format `YYYY-MM-DDTHH:MMZ`, at the minute of the measurement; `family`: the key of a family of `labeling/families.md` (`Visibility`, `Obstruction`, `Thermal displacement`, `Displacement`, `Target issue`, `No data`), no other; `description`: in English, qualitative, without numeric values. - **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. +- The whole range is read: an instant without a label means that `corr_x` and `corr_y` show nothing there beyond the noise. Before answering, `python3 labeling/scripts/validate.py /labels.jsonl` must say 0 errors. @@ -76,7 +76,7 @@ Before answering, `python3 labeling/scripts/validate.py /labels.j - **Confidence**: high | medium | low, and why ## 2. What I left without a label - + ## 3. The documentation