Files
aimsight-optimizer/sessions/NORDEND_2026-11-05T0600_2026-11-05T1200_20261116T1028Z/modification.md
T

10 KiB
Raw Blame History

Modification

Verdict: changed

Diagnosis

NORDEND, 2026-11-05T00:00Z → 2026-11-06T00:00Z, cadence 15 min, 19 targets and 3 references (CTR02, CTR03, CTR04; CTR01 is a local reference read as a target). Labels touching the range: NORDEND-229, 230, 231, 232, 233, 234, 235, 236, 243.

Family labelled found flagged wrongly
Displacement 1 0 3 3
Obstruction 32 28 60 32
Target issue 96 0 0 0
Thermal displacement 95 53 53 0
Visibility 0 0 43 43
  • NORDEND-229 / NORDEND-234 (Thermal displacement, camera cycle, 00:00 → 24:00): wrong bounds, too short. The detectors only had the wave from 07:00 to 20:00 (Camera thermal expansion 07:00 → 14:00, contraction 14:00 → 20:00). The return stopped as soon as the hourly gap profile fell under EDGE (0.1 of the amplitude), around 20:00. But the profile keeps a slow tail all night, which the labels count as part of the cycle ("sans repos jusqu'au départ du matin suivant"). This is the main defect, and it comes back every night. Fixed in part by S1. The early night of the 05/11 (01:00 → 06:30, the end of the 04/11 cycle) is still missed.
  • NORDEND-230 (Target issue, CTR01 rejected most of the time since 16/10): wrong family on the range. With only the 3 days of history the range command reads, CTR01 cannot reach the WEEK (7 days) a Degraded target needs. It comes out as a Target obscured (Obstruction) of CTR01 from 11-04 07:15 to 11-05 14:45. The families document allows this for a target hindered less than a week. Over the benchmark window (the whole label range), the detectors find it as a Degraded target from 10-17 to 11-07. This is a limit of the range window, not of the detector. The same accidental Target obscured gives most of the "found" Obstruction instants of the range (28/32).
  • NORDEND-231 (00:45 → 01:30) and NORDEND-233 (03:15 → 03:45), Obstruction, CTR03 rejected so the base jumps: wrong family (Visibility). The jumps back of 01:00 and 03:30 (7 and 17 targets) are absorbed into a Poor visibility "reduced" from 00:45 to 09:30. CTR03 is at 0.7 to 1.4 times its threshold, rejected 1 to 2 measurements. The families document puts a reference at its threshold, with nothing seen in front of it, in Visibility or Displacement. Only the thumbnail shows the cobweb thread: a limit (see Limits). Over the full benchmark window, 03:30 is already a Brief obstruction of CTR03.
  • Poor visibility 00:45 → 09:30 and 13:30 → 15:00 (43 instants without a Visibility label): extra. At no instant are more than 3 of the 22 sensors high: CTR02, PR01, PR09 go back and forth all day (the context says "sans effet sur les courbes"), and the side-effects of CTR03 appear on PR04 and PR11. The bounds come from CTR01, which is rejected almost all the time. Four general rules were tried; each one makes another station go back (see Not fixed).
  • NORDEND-232 (03:00 → 09:45) and NORDEND-235 (15:00), Obstruction, PR09: correct family in part. PR09 has Brief obstructions at 07:15 to 07:45 and 09:30, and its other rejections are inside the Poor visibility above. Wrong bounds, from the same cause.
  • NORDEND-236 (23:00 → 11-06 10:00), Obstruction, CTR03 comb: wrong family on the range. The first two CTR03 rejections (23:15, 23:45) come out as "Jump, not back yet" (Displacement, 19 targets), because the range ends at midnight and the return cannot be seen yet. Over the benchmark window they are Brief obstructions of CTR03, the label's family. This is an edge effect of the window.
  • NORDEND-243 (12:00, Displacement, camera jolt): absorbed into the camera thermal wave. NORDEND-234 itself describes the 12:00 jolt as part of the thermal cycle ("à 12:00 où toute la scène … fait un à-coup"). The labels disagree with each other here, and the detectors keep 234's reading: alternative reading.

What changed

  • S1 (commit 3ea6b3e), scripts/thermal_displacement.py: new constant RETURN = 0.05. The return of the wave (contraction) now goes on until the hourly gap profile falls under RETURN times the amplitude, after midnight if needed, at most to the next day's start. Before, it stopped at EDGE = 0.1. EDGE (0.1) now only bounds the start of the wave. Docstring (point 5) and thresholds.md (EDGE line reworded, RETURN line added) are updated.

Why

  • S1: a camera or structure heated during the day warms up quickly and cools slowly. The tail of its return stays a few percent of the amplitude away from the night level for hours, and labels count this tail as the thermal cycle. One threshold for both ends cut the contraction in the evening. Lowering EDGE itself also moved the start earlier and overflowed into the mornings, so only the return is read lower.

Before / after on the range

Events command, changed lines:

before: 2026-11-05T14:00Z → 2026-11-05T20:00Z Thermal displacement kept | Camera thermal contraction | 22 sensors
after:  2026-11-04T14:00Z → 2026-11-05T01:00Z Thermal displacement kept | Camera thermal contraction | 22 sensors
        2026-11-05T14:00Z → 2026-11-05T23:45Z Thermal displacement kept | Camera thermal contraction | 22 sensors

No skipped line. Range score: Thermal displacement found 53/95 (56 %) → 73/95 (77 %), correct 53/53 → 73/73 (100 %). The other families are unchanged (Displacement 0/1 and 0/3, Obstruction 28/32 and 28/60, Target issue 0/96, Visibility 0/43 correct).

Benchmark

Station Family found correct
JUNGFRAU Thermal displacement 1544/2557 (60 %) → 2300/2557 (90 %) 1544/1786 (86 %) → 2300/2654 (87 %)
NORDEND Thermal displacement 4769/7667 (62 %) → 5066/7667 (66 %) 4769/5097 (94 %) → 5066/5411 (94 %)
SNCF01 Thermal displacement 1218/1726 (71 %) → 1254/1726 (73 %) 1218/1275 (95.5 %) → 1254/1334 (94.0 %)

Total:

Family found correct
Thermal displacement 10897/16142 (68 %) → 11986/16142 (74 %) 10897/14828 (73 %) → 11986/16069 (75 %)

No other line changed. SNCF01 "correct" drops 1.5 points, under the 2-point limit. The output is in benchmark-S1.txt.

For the user to decide

  • NORDEND-243 (NORDEND, 2026-11-05 12:00, Displacement) against NORDEND-234 (Thermal displacement), whose description includes the same 12:00 jolt. The detectors absorb the one-measurement jump into the camera thermal wave, as 234 says. With this reading, the 1 Displacement instant of the range is never found.
  • NORDEND-231 and NORDEND-233 (NORDEND, 2026-11-05 01:00 to 01:15 and 03:30, Obstruction). CTR03 is rejected just above its threshold, and the families document gives Visibility or Displacement for a reference at its threshold with nothing seen in front of it. The detectors read Visibility (absorbed into the Poor visibility). The labels are right because of the thumbnail.

Not fixed

  • The false Poor visibility 00:45 → 09:30 and 13:30 → 15:00, and over the benchmark window 11-05 13:15 → 11-07 15:15. It comes from 1 to 3 sensors high at a time, one reference among them, bounded by CTR01's chronic rejections. Four rules were tried in a copy, and each makes another station go back:

    • (A) no Poor visibility when no instant has more than FEW sensors high: JUNGFRAU Visibility found 64 → 51 %, LENZSPITZE Obstruction correct 23 → 6 %;
    • (C) the rejections of a target rejected more than half the time do not bound a Poor visibility: JUNGFRAU found 64 → 51 %, CLARIDEN 3 → 0 %;
    • (T) the same, for the targets in a Target issue episode: JUNGFRAU, CLARIDEN and NORDEND Visibility found down;
    • (S) heat shimmer agitation without the steps at a reference rejection, against the night heat shimmer on the CTR03 comb: WILDSTRUBEL Visibility 79 → 13 %.

    On JUNGFRAU, nights with two references at their threshold are labelled Visibility, and the measurements alone give no general line between those and one reference hindered by a thread.

  • The early night of the 05/11 (01:00 → 06:30, end of NORDEND-229) stays without the thermal wave. The return of the 04/11 contraction reaches RETURN at about 01:00, and the gap profile is no longer monotone at night (21:00 to 23:00 rise again).

  • NORDEND-232 (PR09): bounds only in part (Brief obstructions at 07:15 to 07:45 and 09:30); the rest of its rejections are inside the Poor visibility above.

  • The CTR03 rejection at 03:30 on the range is not a Brief obstruction. PR04 and PR11 rise with it (the compensation runs on two references), so it fails the "fewer than BRIEF_MIN high sensors" guard. Over the benchmark window it already is one, so the gain would only be on the range.

Limits

  • NORDEND-231 (2026-11-05T00:45Z → 01:30Z, Obstruction), NORDEND-233 (03:15Z → 03:45Z, Obstruction), NORDEND-236 (23:00Z → 11-06 10:00Z, Obstruction): only the thumbnail shows that a cobweb thread lies on CTR03. From the measurements alone, it is a reference at its threshold that makes the base jump. Seeing the cause would take the image (a bright blurred band on the reference's spot).
  • NORDEND-232 (03:00Z → 09:45Z) and NORDEND-235 (14:45Z → 15:15Z), Obstruction: by day, PR09's thread is only deduced from the night thumbnail.
  • NORDEND-230 (Target issue, CTR01): the range command reads 3 days of history, too short for the WEEK (7 days) of a Degraded target. Over the whole label range it is found.

Tools

  • seances/NORDEND_2026-11-05T0600_2026-11-05T1200_20261116T1028Z/tools/raw_episodes.py <detectors> <station> FROM TO [detectors]: the raw episodes of each detector (before classification) on a range plus 3 days of history. Worth keeping.
  • .../tools/high_sensors.py <detectors> <station> FROM TO SHOW_FROM SHOW_TO: per instant, the sensors visibility.py calls high, the rejected ones, and the median MAD gap (point 8). Worth keeping for Visibility diagnoses.
  • .../tools/sensor_values.py <detectors> <station> SENSORS FROM TO [MEDIAN_FROM]: error_value (×median, ×threshold), corr_x and corr_y of a few sensors. Worth keeping.
  • .../tools/thermal_gaps.py <detectors> <station> FROM TO: the hourly gap profile used for the thermal bounds, on corr and on raw positions. Useful for thermal bounds.
  • .../tools/events_in_window.py <detectors> <station> FROM TO SHOW_FROM SHOW_TO: classifies a long window, as the benchmark does, and shows the events of a sub-window. Worth keeping: range runs and benchmark runs differ (history, medians).
  • .../tools/bench_diff.py BEFORE AFTER: the changed lines between two benchmark outputs, with regressions over 2 points flagged. Worth keeping as a workflow tool.