Files
aimsight-labeling/families.md
T
2026-11-18 10:51:31 +01:00

9.5 KiB

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 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 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 (lasting shift, jump not back yet, slow drift) something moved, by a jump or a drift, and has not come back by the end of the range: one or more targets, a reference, or the camera outside a thermal effect; the description says what moved check what moved: the structure (look at the images, check on site) or the camera (check its mount)
Perturbation displacement.py (jump back to normal) the corrected curves move beyond their noise and come back, and no other family explains it: a jolt of the camera, a reference or the base shifted for a while, a single point, targets that wander and come back; the cause is not established or several factors mix nothing to do: the curves came back; ignore these points
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

For the client, some varieties of a family (the label of the detectors' episode, and its level when it has one) say more than their family; the others take the family's:

Variety For the client
Poor visibility reduced use the data over the range with care: they are less precise
Heat shimmer nothing to do: the small fast wiggles are not movement
Camera thermal movement nothing to do: this is not a movement of the structure
Brief obstruction ignore this single point on the curves
Sudden jump, back to normal nothing to do: it came back; ignore these points
Lasting shift check what moved: look at the images
Jump, not back yet check what moved: look at the images
Slow drift keep watching it

The boundaries

  • Visibility or Obstruction: the nuisance is judged by its extent, not by the light. The whole scene hindered (rain, fog, underexposed image, milky dawn, sun in the field) is Visibility; a few targets hidden by an object, the rest intact, are Obstruction, even if the object is lit (machine, headlights, light of a parked vehicle). A spider web goes by what it does: a thread that hides a target, Obstruction; the web that veils the image, Visibility.
  • Obstruction, whatever the duration: an obstacle that stays (parked vehicle, machine, plant, animal or insects against the lens, mark on the glass in front of a single spot) is Obstruction.
  • A hindered reference (phenomena: "A reference dropped", "Two references lost"): the family of its cause. A passage in front of a reference that makes the base jump is Obstruction when the object is seen, or deduced from a passage signature; a reference right at its threshold, with nothing in front of it, is not a passage: Visibility, or Perturbation without a cause; Displacement if the base stays changed. The description says it is a reference, and that the targets move together because of it.
  • 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: Perturbation.
  • 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 and does not come back, are Displacement. What does not follow it and comes back is Perturbation.
  • Displacement or Perturbation: decided by the return, not by the cause. What moved and has not come back by the end of the range (a target, a reference, the camera outside a thermal effect) is Displacement; what comes back, even after days, is Perturbation. A camera that moves and stays is Displacement even when the compensation absorbs it afterwards; the description says it is the camera. A partial return is not a return.
  • 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 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

They are the cases: auto/cases/ (kind phenomenon), listed by python3 scripts/cases.py --list, searched by python3 scripts/cases.py "<what you see>". A phenomenon not among them is labelled too, without forcing a cause.

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"); 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.