Rules: a missing point is not labeled for itself (the station filtered it), No data only when the station delivers nothing, thermal movement only when the corrected curves keep it (replaces D-117), Target issue only for a target rejected almost always; the mm curves follow the same rule and threshold

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
maximeandClaude Opus 5.5 committed 2026-11-18 07:16:59 +01:00
1 parent 764af7d8ec
commit c89c1b9976
2 files changed
+16 -16

No files matched your search

+7 -6
View File
@@ -1,12 +1,12 @@
# The label families
One label, one anomaly, one family (D-109 to D-111, D-119). An anomaly is what shows up on `corr_x` and `corr_y`: the curves move (a peak, a jump, a drift, noise) or are missing (a gap). The family says the **cause** of what is seen on the corrected curves, or of what is missing from them, and what the client should conclude. Its key, its very name, goes in the `family` field of the label; the labeling tool offers it in its Category menu. Each family has its detector, in `detectors/scripts/` (D-119): the category of a detector event is its family.
One label, one anomaly, one family (D-109 to D-111, D-119). An anomaly is what shows up on `corr_x` and `corr_y`: the curves move beyond their noise (a peak, a jump, a drift, an agitation) or are all missing (No data); a missing point alone, filtered by the station, is not one. The family says the **cause** of what is seen on the corrected curves, or of what is missing from them, and what the client should conclude. Its key, its very name, goes in the `family` field of the label; the labeling tool offers it in its Category menu. Each family has its detector, in `detectors/scripts/` (D-119): the category of a detector event is its family.
| Key | Detector | What happens | For the client |
|---|---|---|---|
| `Visibility` | `visibility.py` | things are harder to see: a diffuse nuisance between the camera and the scene. The image is faint or blurred (rain, fog, condensation, light, dirty lens: the spots are fainter or blurrier), or it shakes (turbulence: hot air, above a road or in the sun, makes the spots shake, a fast noise on the curves). The description says which is seen | do not trust the curves over the range; it is not a movement |
| `Obstruction` | `visibility.py` (brief), `target_issue.py` (target obscured) | an object hides one or a few targets, for a moment or for a long time (train, vehicle, plant, snow on the target) | ignore the curve of the hidden targets over the range |
| `Thermal displacement` | `thermal_displacement.py` | a component (the structure, the camera and its mount) moves with temperature; it is always labeled, whether the corrected curves show it or the camera compensates it (D-117); the direction does not matter | normal, nothing to do |
| `Thermal displacement` | `thermal_displacement.py` | a component (the structure, the camera and its mount) moves with temperature; it is labeled only when the corrected curves keep it, not when the camera compensates it (`labeling-rules.md`, section 1); the direction does not matter | normal, nothing to do |
| `Displacement` | `displacement.py` | a lasting jump, a slow drift, and anything that changes the corrected curves without an established cause (rule D-074: do not alarm the client, hide nothing) | to check: look at the images, monitor |
| `Target issue` | `target_issue.py` | a constantly problematic target: rejected almost always, badly oriented, badly installed, badly configured, dirty | act on the target; ignore its curve |
| `No data` | `no_data.py` | no measurement for any sensor, all curves missing (acquisition, power, transmission); the cause, if the metrics or the images show it, otherwise not established | the curves are missing over the range; the cause says whether to act |
@@ -32,8 +32,8 @@ For the client, some varieties of a family (the `label` of the detectors' episod
- **A jump then the return**: the family of its cause, seen on the images. A passing vehicle, and its reflection, are Obstruction (a reflection on the roadway lasting only one measurement is a vehicle: read the measurement before and the one after); the reflection of the sun on the fixed scene is Visibility. Without an established cause: Displacement.
- **Thermal displacement or Displacement**: what follows the temperature of the housing **and comes back with it** (same position at equal temperature), even over several days, or whose thermal cause the expert gives, is Thermal displacement; what follows it only as a trend, without coming back at equal temperature, and what the temperature does not explain, are Displacement.
- **Thermal displacement or Visibility**: curves that follow the scale and rotation of the camera with the housing temperature, the `error_value` at its level or rising only a little, nothing on the images, several targets moving apart in opposite directions through the rest of the compensation, are Thermal displacement. References moving apart from each other and from the targets, an `error_value` rising on most sensors, an episode with sharp edges, or a nuisance seen on the images, are Visibility, even at the temperature trough. The two can coexist: two labels. A daytime agitation, the pose shaking without the `error_value` rising, is not turbulence.
- **A gap**: curves missing because targets are rejected are in the family of the cause of the rejection (Visibility, Obstruction, Target issue); all curves missing, no measurement: No data. The cause of a No data can be outside the station: a gap at the same minutes on several stations is a common cause (transmission or reception), not an outage. The station is running if a synchronization falls at the missing instant, if the image of that instant exists, or if `DB_not_uploaded` rises then falls.
- **Target issue or episode of another family**: a Target issue requires rejections specific to the target (outside the episodes shared with its neighbors) almost every day of the range, also on covered or rainy days, under the station's normal regime (the floodlight at night, daylight). A reference rejected like this every day is one, even if its entries and exits do not make the targets jump: the compensation loses it every day. Rejections that come only with a condition seen on the images (sun, rain, night of poor visibility) are episodes of the family of that condition, one label each time. An `error_value` right at the threshold, with few own rejections, is not a Target issue: first count the own rejections of each target and each reference, day by day.
- **A gap**: curves missing because targets are rejected are not labeled for themselves, the station filtered them; the episode that rejects them is labeled only if it moves the other curves beyond the noise, in the family of its cause (Visibility, Obstruction); a target rejected almost always is a Target issue; all curves missing, no measurement: No data. The cause of a No data can be outside the station: a gap at the same minutes on several stations is a common cause (transmission or reception), not an outage. The station is running if a synchronization falls at the missing instant, if the image of that instant exists, or if `DB_not_uploaded` rises then falls.
- **Target issue or episode of another family**: a Target issue requires rejections specific to the target (outside the episodes shared with its neighbors) almost every day of the range, also on covered or rainy days, under the station's normal regime (the floodlight at night, daylight). A reference rejected like this every day is one, even if its entries and exits do not make the targets jump: the compensation loses it every day. Rejections that come only with a condition seen on the images (sun, rain, night of poor visibility) are not a Target issue: missing points, labeled only when the curves move beyond the noise, in the family of that condition. An `error_value` right at the threshold, with few own rejections, is not a Target issue: first count the own rejections of each target and each reference, day by day.
- **Target issue or Displacement**: a changed configuration (moved sensors, changed starting position, setting) is Target issue; the jump that results is not a Displacement.
## The phenomena
@@ -73,7 +73,7 @@ What has been labelled so far, one line each: **name**: what is seen; how to tel
- **The configuration of a sensor has changed**: a sensor moved or reset: its curve changes with nothing moving in the image; the jump is not a Displacement.
### Thermal displacement
- **The camera moves through a thermal effect**: the pose follows the housing temperature, every day, the compensation erasing more or less of it; labelled even when fully compensated.
- **The camera moves through a thermal effect**: the pose follows the housing temperature, every day, the compensation erasing more or less of it; labelled only when the curves keep it beyond the noise.
- **The camera drifts away when the temperature of its housing drops, without a daily cycle**: sheltered (a building, a tunnel), it drifts in jerks with the housing temperature and comes back when it warms.
- **The structure expands and contracts with the temperature**: a structure that can move (a bridge) moves with its own slow rhythm, each target its amplitude, the references stable; two labels a day, expansion and contraction.
- **A rise over several days with the drop in temperature**: the temperature keeps falling for days and the structure keeps rising; it comes back at equal temperature (else Displacement).
@@ -95,6 +95,7 @@ What has been labelled so far, one line each: **name**: what is seen; how to tel
## What is not labeled
- What does not stand out from the noise of `corr_x` and `corr_y` (the threshold of `labeling-rules.md`, section 1): an `error_value` that rises without effect on them; a camera step well compensated, even on two references, as long as the `corr` keep nothing of it beyond the noise (if some remains, the label bounds the step and concludes "the camera moves"). Thermal movement, on the other hand, is always labeled (D-117).
- What does not stand out from the noise of `corr_x` and `corr_y` (the threshold of `labeling-rules.md`, section 1): an `error_value` that rises without effect on them; a camera step well compensated, even on two references, as long as the `corr` keep nothing of it beyond the noise (if some remains, the label bounds the step and concludes "the camera moves"); a thermal movement that the compensation absorbs.
- A missing point: a target or a reference rejected, a curve partly missing, filtered by the station as unreliable, even when its cause is known (a pass-by, the sun, a faint spot at dawn); only what it does to the other curves is labeled.
- The station's intended configuration (targets that are twins of their references: the same prism serves as target and reference; they are named with their reference in its labels).
- The expert can say so with the key `None` (labeling tool: "None (curves untouched)"): such a label is not counted.
+9 -10
View File
@@ -6,14 +6,13 @@ Sources in brackets: [instruction] the section "Les étiquettes" of `.claude/age
## 1. What is labeled
- **Everything that stands out from the noise on `corr_x` or `corr_y`, over the whole batch**: a movement (a spike, a jump, a drift, a wave, an agitation) is labeled when at least one target deviates from its level by more than 5 of its own noises, the threshold of the thermal cycle below (`tools/scripts/ranges.py` at its default `--k 5`, with `--rolling` under a drift or a thermal cycle); a missing point is labeled at any amplitude (the gaps and the rejections below). Under the threshold, it is the ordinary noise of the station: it goes in the analysis, with its deviation in noises, not in a label. An instant without a label means the curves show nothing beyond the noise. [instruction; WYOMING: an agitation under the threshold, labeled then removed according to the expert; the user, 2026-11-17]
- **A gap of a single measurement is labeled No data, at any rate**: otherwise, the label of one and the same common gap would depend on the station's rate. [cross No data, CLARIDEN, FLORIDA, LENZSPITZE]
- **A target rejected for one instant is labeled**: it is a missing point; the isolated rejections of a target right at the threshold each have their one-measurement label. [LENZSPITZE, SNCF01, cross Target issue]
- **Thermal movement is always labeled, even compensated**: the camera pose that follows the temperature gets its label every time, even when the corrected curves are back, even without a daily cycle (tunnel, building: the pose against brief drops of the housing temperature), even on an overcast day (D-117). [NORDEND, WILDSTRUBEL, MICHIGAN, CLARIDEN, cross Thermal displacement]
- **No thermal label on a day when neither the pose nor the `corr` deviate by more than 5 noises from the night level**: there is no cycle to label. [cross Thermal displacement, NIEDERHORN]
- **"No effect on the curves" is checked before labeling nothing**: on the residuals of the `corr` at those instants, and on the number of targets jumping together against a calm moment of the same day; an agitation under the rejection threshold that makes targets flip is labeled. [JUNGFRAU, NORDEND]
- **Everything that stands out from the noise on `corr_x` or `corr_y`, over the whole batch** (or on `corr_x_mm`, `corr_y_mm`: the same curves in mm, the same rule; the noise is the sensor's own, in its unit, so the threshold in noises is the same): a movement (a spike, a jump, a drift, a wave, an agitation) is labeled when at least one target deviates from its level by more than 5 of its own noises, the threshold of the thermal cycle below (`tools/scripts/ranges.py` at its default `--k 5`, with `--rolling` under a drift or a thermal cycle); a missing point is not labeled for itself (below). Under the threshold, it is the ordinary noise of the station: it goes in the analysis, with its deviation in noises, not in a label. An instant without a label means the curves show nothing beyond the noise. [instruction; WYOMING: an agitation under the threshold, labeled then removed according to the expert; the user, 2026-11-17]
- **No data only when the station delivers nothing**: no measurement of any sensor, all curves missing; then at any rate, even for a single measurement, otherwise the label of one and the same common gap would depend on the station's rate. [cross No data, CLARIDEN, FLORIDA, LENZSPITZE; the user, 2026-11-17]
- **A missing point is not labeled for itself**: a target or a reference rejected, a curve partly missing, is a measurement the station itself judged unreliable and filtered; the client sees no false value there. Only what it does to the other curves is labeled (a lost reference makes the targets jump), beyond the noise, in the family of its cause. [the user, 2026-11-17]
- **Thermal movement is labeled only when the corrected curves keep it**: at least one target deviates by more than 5 noises from the night level, the threshold above; a camera movement that the compensation absorbs is not labeled, nor a pose that moves alone, whatever the day. [the user, 2026-11-17, replaces D-117; cross Thermal displacement, NIEDERHORN]
- **"No effect on the curves" is checked before labeling nothing**: on the residuals of the `corr` at those instants, and on the number of targets jumping together against a calm moment of the same day. [JUNGFRAU, NORDEND]
- **A signature found once is searched over the whole batch**: every cold night, every sunny afternoon, every step of the same shape, with the image of the same day; this is how the forgotten ones were found. [BREITHORN, FLORIDA, JUNGFRAU, NEBRASKA]
- **What falls under a long label is labeled apart**: pose steps, isolated rejections, a passage within a day of turbulence have their own label. [SNCF01, LENZSPITZE, cross Obstruction]
- **What falls under a long label is labeled apart**: pose steps, a passage within a day of turbulence have their own label, when they stand out from the noise. [SNCF01, LENZSPITZE, cross Obstruction]
- **Targets twinned with their references are not labeled for themselves**: they are named with their reference in the labels that touch it. [cross Target issue]
## 2. The bounds
@@ -55,7 +54,7 @@ Sources in brackets: [instruction] the section "Les étiquettes" of `.claude/age
- **Two nuisance episodes separated by a few hours where targets stay shifted make only one**: the shifted targets are still touched. [NORDEND]
- **An obstacle that stays makes one label per parking or per episode**: an intermittent episode (a plant shaken by the wind) is cut at a pause of several measurements. [cross Obstruction]
- **A Target issue: one label per target and per batch, from the start to the end of its regime**: the defect is the target's, the night is not an event. [cross Target issue, JUNGFRAU]
- **The isolated rejections of a target before its Target issue regime each have their label, in the family of their cause**: the Target issue starts with the regime, not at the first rejection separated from the regime by clean days. [finishing divers]
- **The Target issue starts with the regime**: not at the first rejection separated from the regime by clean days; those isolated rejections are missing points, not labeled. [finishing divers]
- **A target whose `error_value` goes above its threshold at a jump and stays there has its Target issue, in addition to the Displacement of the jump**: the two labels overlap. [finishing niederhorn]
- **A deviation specific to targets, mixed with a camera movement, is the same event if it follows it in both directions, on the same dates**: it rises, stops and comes back with it; with its own dates (start, stop or return without the camera), it is a second event; it is read on the residual (`overview.py --rigid`), day by day, at equal tilt or temperature. [finishing divers]
@@ -82,7 +81,7 @@ Sources in brackets: [instruction] the section "Les étiquettes" of `.claude/age
- **A thermal cycle label is described on its own day, never by copying the day before**: the direction and magnitude, in words, of each axis of the pose and the hour of its return; the rise of the housing temperature; the targets that dip and those that rise that day, without those that a Target issue makes unreadable; the `corr_y`; the hour when the curves come back; "in the sun", "the references stay calm", "some days" only if that day shows it. [finishing niederhorn, finishing nordend, finishing wildstrubel, NORDEND]
- **"Mostly pan", an axis that moves "with" another, a pose that "comes back at once" are checked axis by axis**: in degrees, at the hour of each extreme. [finishing niederhorn, finishing wildstrubel]
- **The agitation from one measurement to the next is written in the thermal label**: when the pose step exceeds several times that of the night and the `error_value` does not rise; it does not make a Visibility. [finishing niederhorn]
- **A compensated thermal movement is stated as such**: the description says the pose moves and the compensation absorbs it. [cross Thermal displacement]
- **A thermal movement partly compensated is stated as such**: the description says the pose moves, what the compensation absorbs and what remains on the curves. [cross Thermal displacement]
- **A touched reference is stated, with what remains**: the targets move together; two remaining references, "a very bad sign"; none, "the points make no sense". [cross Obstruction]
- **A Displacement says what moves in the image, checked target by target on the raw position, and concludes accordingly**: the camera moves and the targets do not: "it is not a movement of the structure; the camera is to be monitored"; targets move alone: "a movement of these targets is not excluded: to check (what to look at), monitor"; nothing moves in the image, the base or the configuration changes: "it is not a movement of the structure; points to ignore if there is a return, to check with the operator otherwise"; the whole scene deforms while the camera moves: "movement of the structure not established: to monitor". [cross Displacement, NEBRASKA]
- **A drift of several days says whether it follows the housing temperature and whether it comes back with it, at equal temperature**: otherwise, "the temperature does not explain it alone, link not established". [cross Displacement]
@@ -102,7 +101,7 @@ Sources in brackets: [instruction] the section "Les étiquettes" of `.claude/age
- **"Image not looked at" is not an end when an image exists**: it is looked at, or the cause is stated deduced; a signature that returns about twenty times is looked at on a thumbnail sheet, one measurement per episode. [cross Obstruction, NIEDERHORN]
- **Do not say more than what was seen**: never "nothing to fear" nor "probably not a movement" when the cause is not established: they reassure without proof; with an established cause (seen, or given by the expert), "nothing to fear for the structure" is right. A nuance on a cause not established ("probably", "likely", "possible") remains allowed, next to "not established" or "deduced": it states the degree of the hypothesis, as with the expert. [instruction, cross Displacement, WILDSTRUBEL; the user, 2026-11-05]
- **A gap at the same minutes on several stations is stated the same on each**: "a common cause outside the station (transmission or reception of the data), not a station failure; it is not established", with the other stations, then "nothing to do on the station"; with two stations only, the common cause is "possible"; the word "outage" is not written. [cross No data]
- **Each rejection of a measurement of a small group of targets, each loss of a reference, is looked at on the thumbnail, even in a day of turbulence**: it is often a passage. [WILDSTRUBEL]
- **Each loss of a reference, each rejection inside a labeled moment, is looked at on the thumbnail, even in a day of turbulence**: it is often a passage. [WILDSTRUBEL]
- **A gap specific to a station keeps its own cause**: energy, mains or silent station, read on its metrics; without a signature, "cause not established". [cross No data]
The boundaries between families, and what is not labeled: `families.md`.