analyst, support: the cases (labeling/auto/cases/, scripts/cases.py) replace the catalogue of phenomena and the false friends
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
4cd56ac172
commit
59da8532ab
2 files changed
+10
-9
No files matched your search
+9
-8
@@ -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.
|
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** (`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.
|
The expert labels in free text: what is seen, the cause and how it was known, what follows from it. The phenomena, false friends and lessons learnt so far are the cases (`labeling/auto/cases/`), drawn from the labels; the labels themselves 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
|
## Your request
|
||||||
|
|
||||||
@@ -25,12 +25,13 @@ The repository you are called from carries the links `data/` (the stations), `la
|
|||||||
|
|
||||||
- `tools/GUIDE.md` (read it first): your tools; and `tools/DATA.md` (**in full**): the files of a station and what each column means;
|
- `tools/GUIDE.md` (read it first): your tools; and `tools/DATA.md` (**in full**): the files of a station and what each column means;
|
||||||
- the station folder, through these tools or your scripts, and its images with Read;
|
- the station folder, through these tools or your scripts, and its images with Read;
|
||||||
- `labeling/families.md` (**in full**): the families of the labels, their boundaries, the catalogue of phenomena, what is not labelled;
|
- `labeling/families.md` (**in full**): the families of the labels, their boundaries, what is not labelled;
|
||||||
- `labeling/labeling-rules.md` (**in full**): how to write a label, bounds, a single event, description, stated cause;
|
- `labeling/labeling-rules.md` (**in full**): how to write a label, bounds, a single event, description, stated cause;
|
||||||
- `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/reading-rules.md` (**in full**): what the data mean: the measurement chain, the thermal effects, the gaps, the reading rules;
|
||||||
- `labeling/stations.md` (**in full**): the structure, camera, references and neighbours of each station;
|
- `labeling/stations.md` (**in full**): the structure, camera, references and neighbours of each station;
|
||||||
- `labeling/auto/<STATION>.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;
|
- `labeling/auto/<STATION>.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/scripts/precedents.py "<what you see>" --exclude <STATION> <start> <end>` (`--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 **cases**: `python3 labeling/scripts/cases.py --list` (every case, one line each), then `python3 labeling/scripts/cases.py "<what you see>"` (`--family`, `--k` as needed): each with its signature, its checks, its neighbours and how to tell them apart, its sources, and whether the user validated it; a label source inside your own range is not an independent confirmation;
|
||||||
|
- the **precedents**, with `python3 labeling/scripts/precedents.py "<what you see>" --exclude <STATION> <start> <end>` (`--family`, `--k` as needed): the labels already written in `labeling/auto/`, all stations, closest in meaning to your description; each with its provenance (`auto, validated by the user on …`, `auto, not validated`). Use the cases, the precedents, or both: the cases for what generalizes, the precedents for how a similar case was bounded, classified and worded;
|
||||||
- what your instructions add.
|
- 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".
|
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".
|
||||||
@@ -42,7 +43,7 @@ Those of the guide, with `--start`, `--end` of the range (a margin before or aft
|
|||||||
## Steps
|
## Steps
|
||||||
|
|
||||||
1. **Read the range** as the guide says, in full: everything that makes the curves not flat, and what the expert looks at (`labeling/reading-rules.md`, section 5); the hints first.
|
1. **Read the range** as the guide says, in full: everything that makes the curves not flat, and what the expert looks at (`labeling/reading-rules.md`, section 5); the hints first.
|
||||||
2. **For each moment**, look in the catalogue of phenomena (`labeling/families.md`) for those that could fit, and check on the data and the images what each says should be seen there; beware of the false friends (`labeling/reading-rules.md`, section 6). Then look for its **precedents**: describe what you see as a label description (the sensors affected, what they do, what the images show), without naming a cause you did not see, and read how these cases were bounded, classified and explained. A precedent is a case, not a truth: a reviewed label weighs more than an unreviewed one, and any may be wrong; check what it says on your data, and a precedent your data contradict, say so in your analysis (section 3). A phenomenon the catalogue does not know is labelled too, without forcing a cause; its precedents may know it. A phenomenon found once is looked for over **the whole range** and treated the same way every time: cold mornings, for example, are all listed by `days.py --bounds` (pose and `corr`) against the temperature (`metrics.py`). Before writing that the targets do not move and that it is the camera, check it **target by target** with `overview.py --rigid`: a target whose raw position departs alone from the overall movement moves in the image; it is not the compensation.
|
2. **For each moment**, look among the cases for those that could fit: `cases.py --list` shows them all (phenomena, false friends, lessons), `cases.py "<what you see>"` the closest, with what you see written as a label description (the sensors affected, what they do, what the images show), without naming a cause you did not see. Check on the data and the images what the signature and the checks of each say should be seen there, and rule out its neighbours as each says. A case is a generalization, not a truth: a case the user validated weighs more than one not validated, and any may be wrong; a case your data contradict, say so in your analysis (section 3). The precedents, if you search them, show how similar labels were bounded, classified and explained; a precedent is a case, not a truth: check it on your data. A phenomenon no case knows is labelled too, without forcing a cause; its precedents may know it. A phenomenon found once is looked for over **the whole range** and treated the same way every time: cold mornings, for example, are all listed by `days.py --bounds` (pose and `corr`) against the temperature (`metrics.py`). Before writing that the targets do not move and that it is the camera, check it **target by target** with `overview.py --rigid`: a target whose raw position departs alone from the overall movement moves in the image; it is not the compensation.
|
||||||
3. **Write your labels**, your analysis, then what your instructions ask for.
|
3. **Write your labels**, your analysis, then what your instructions ask for.
|
||||||
|
|
||||||
## The labels
|
## The labels
|
||||||
@@ -68,8 +69,8 @@ Before answering, `python3 labeling/scripts/validate.py <output folder>/labels.j
|
|||||||
|
|
||||||
## 1. My labels
|
## 1. My labels
|
||||||
### <start> → <end>
|
### <start> → <end>
|
||||||
- **Phenomenon of the catalogue**: <its name> | none
|
- **Case**: <id>, how it fits and what differs | none
|
||||||
- **Precedents**: <id, or station and dates, of those that helped you, and how> | none useful
|
- **Precedents**: <id, or station and dates, of those that helped you, and how> | none useful | not searched
|
||||||
- **Family**: <key>, and why it rather than a neighbour
|
- **Family**: <key>, and why it rather than a neighbour
|
||||||
- **Measured**: <columns, sensors, values, times, what does not move>
|
- **Measured**: <columns, sensors, values, times, what does not move>
|
||||||
- **Images**: <times looked at, what they show> | none
|
- **Images**: <times looked at, what they show> | none
|
||||||
@@ -79,7 +80,7 @@ Before answering, `python3 labeling/scripts/validate.py <output folder>/labels.j
|
|||||||
<what moves without crossing the threshold of a label: when, which targets, its deviation in noises>
|
<what moves without crossing the threshold of a label: when, which targets, its deviation in noises>
|
||||||
|
|
||||||
## 3. The documentation
|
## 3. The documentation
|
||||||
<what helped you in the labeling knowledge (`families.md`, `labeling-rules.md`, `reading-rules.md`, `stations.md`, `tools/DATA.md`) and the precedents (and the detectors with DETECTORS: yes), what was missing, what misled you or seemed contradicted by the data>
|
<what helped you in the labeling knowledge (`families.md`, `labeling-rules.md`, `reading-rules.md`, `stations.md`, `tools/DATA.md`) the cases and the precedents (and the detectors with DETECTORS: yes), what was missing, what misled you or seemed contradicted by the data>
|
||||||
|
|
||||||
## Difficulties
|
## Difficulties
|
||||||
none | - <what hindered your work: unclear instruction, path, command>
|
none | - <what hindered your work: unclear instruction, path, command>
|
||||||
|
|||||||
+1
-1
@@ -34,7 +34,7 @@ One copy of each repository on the workstation:
|
|||||||
|---|---|
|
|---|---|
|
||||||
| `~/aimsight-data/data/<STATION>/` | the data of the stations: measurements, camera images, metrics, weather; read through the tools |
|
| `~/aimsight-data/data/<STATION>/` | the data of the stations: measurements, camera images, metrics, weather; read through the tools |
|
||||||
| `~/aimsight-tools/` | the reading harness: `GUIDE.md` (the tools; read it before reading any data), `DATA.md` (each file and column) |
|
| `~/aimsight-tools/` | the reading harness: `GUIDE.md` (the tools; read it before reading any data), `DATA.md` (each file and column) |
|
||||||
| `~/aimsight-labeling/` | the labeling knowledge (`families.md`, with what the client is told of each family; `reading-rules.md`; `stations.md`; `labeling-rules.md`), the labels of `auto/<STATION>.jsonl`, the analyses (`auto/analyses/`) and the earlier support folders (`auto/support/`); never `manual/`, the user's own labels |
|
| `~/aimsight-labeling/` | the labeling knowledge (`families.md`, with what the client is told of each family; `reading-rules.md`; `stations.md`; `labeling-rules.md`; the cases, `auto/cases/`, through `scripts/cases.py`), the labels of `auto/<STATION>.jsonl`, the analyses (`auto/analyses/`) and the earlier support folders (`auto/support/`); never `manual/`, the user's own labels |
|
||||||
| `~/aimsight-detectors/` | the detectors; their events on a range: `python3 detectors/scripts/categories.py data/<STATION>/ --from <day> --to <day>`, from the root |
|
| `~/aimsight-detectors/` | the detectors; their events on a range: `python3 detectors/scripts/categories.py data/<STATION>/ --from <day> --to <day>`, from the root |
|
||||||
| `~/aimsight-libredesk/snippets/textes/` | the product knowledge base: FAQ, station manual, trade knowledge, one extract per file |
|
| `~/aimsight-libredesk/snippets/textes/` | the product knowledge base: FAQ, station manual, trade knowledge, one extract per file |
|
||||||
|
|
||||||
|
|||||||
Reference in new issue
Block a user