Files
aimsight-labeling/families.md
T

7.0 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 (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.

Key Detector What happens For the client Label-map phenomena
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 Rain at night; Visibility drops over the whole scene; Atmospheric turbulence
Obstruction obstruction.py 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 A passage hides the targets; A plant in front of a target; An obstacle covers part of the spot
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 The structure expands and contracts; The camera moves through a thermal effect; A rise over several days with the temperature drop
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 A real movement of the structure
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 —

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 (map: "A reference dropped: the base changes", "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 Displacement without a cause. 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: 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.
  • Target issue or Displacement: a changed configuration (moved sensors, changed starting position, setting) is Target issue; the jump that results is not a Displacement.

What is not labeled

  • What touches neither corr_x nor corr_y: 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 (if some remains, the label bounds the step and concludes "the camera moves"). Thermal movement, on the other hand, is always labeled (D-117).
  • The station's intended configuration (map: "Targets that are twins of their references").
  • The expert can say so with the key None (labeling tool: "None (curves untouched)"): such a label is not counted.