From e35d9650eb375dfbbf8d3317df3e096db7417850 Mon Sep 17 00:00:00 2001 From: maxime Date: Wed, 18 Nov 2026 07:17:07 +0100 Subject: [PATCH] analyst: a missing point is not an anomaly (the station filtered it), a well compensated thermal movement is not labelled; corr_x_mm, corr_y_mm are the same curves in mm, same rule and threshold; few labels, each significant Co-Authored-By: Claude Opus 5.5 --- agents/analyst.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/agents/analyst.md b/agents/analyst.md index 66ee394..9c73f02 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 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. +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** (`corr_x_mm` and `corr_y_mm` are the same curves in mm: the same rule, the same threshold in noises; read either, or both, they complement each other, never add up): a diagnosis is wanted only when the corrected curves move beyond their ordinary noise (the threshold of `labeling/labeling-rules.md`, section 1), or when the station delivers no measurement at all (No data). They move: a spike, a jump, a drift, a wave, an agitation. **A missing point is not an anomaly**: a rejected target or reference is a measurement the station judged unreliable and filtered; only what it does to the other curves counts. The cause is then looked for everywhere (`error_value`, images, metrics), but what does not stand out on `corr_x` or `corr_y` is not labelled (an `error_value` that rises with no effect on them, a camera jump or a thermal movement well compensated). Few labels, each significant: they train the detectors. ## Your request