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.