diff --git a/auto/BREITHORN.jsonl b/auto/BREITHORN.jsonl
index 4f9176d..a78b242 100644
--- a/auto/BREITHORN.jsonl
+++ b/auto/BREITHORN.jsonl
@@ -1,5 +1,5 @@
-{"id": "BREITHORN-2", "start": "2026-10-03T00:00Z", "end": "2026-10-13T04:00Z", "family": "Displacement", "description": "From the start of the data to 13 October, six targets drift slowly and steadily, all in the same direction, mostly in corr_x, in corr_y too except POUI19: COLH20, COLI20, COLI21, COLJ19, POUI19 and POUI20; COLI24 drifts in the opposite direction in corr_y. Their drift follows the camera pose step by step, as the camera gradually tilts (tilt increasing, pan and rotation decreasing), while their position in the image hardly moves and their error_value stays stable; the other targets, such as POUH21, do not drift. Cause given by the expert: the camera is gradually nodding forward and the compensation of its movement is not complete, correcting some targets better than others. According to the expert, COLJ19 and POUI19, which drift the most, are much closer to the camera than the other targets; for the other drifting targets, the reason for their poorer compensation (position, angle) is not established. The temperature of the camera housing drops slightly over the range, link not established. According to the expert, BREITHORN, MICHIGAN and NEBRASKA are in the same building: the cameras of the three stations tilt together, in the same direction and on the same dates (advance until 12 October, stop and slight backward movement from 13 to 16, resumption from the 17th to the end of the month), which points to a cause common to the building rather than a fault of this camera alone; at equal housing temperature, the cameras are more tilted at the end of the month than in the middle: temperature does not explain it alone, link not established. For the customer: the targets do not move relative to each other, this is not a movement of the structure; the camera tilt is to be monitored.", "review": "2026-11-17"}
-{"id": "BREITHORN-13", "start": "2026-10-16T20:00Z", "end": "2026-11-01T00:00Z", "family": "Displacement", "description": "From 17 October to the end of the batch, the drift resumes, faster than at the beginning of the month until the 25th, then clearly slower without stopping: the camera tilts again (tilt increasing, pan and rotation decreasing), and COLH20, COLI20, COLI21, COLJ19, POUI19 and POUI20 drift with it, mostly in corr_x and also in corr_y, POUI19 the most; COLI24 drifts in the opposite direction in corr_y. COLI22, COLH20''', POUI22 and POUI24 drift too, more noisily, between their own rejections. Their position in the image hardly moves, their error_value stays stable, POUH21 does not drift. Cause given by the expert: the camera is nodding forward and the compensation of its movement is not complete, correcting some targets better than others. According to the expert, COLJ19 and POUI19, which drift the most, are much closer to the camera than the other targets; for the other drifting targets, the reason for their poorer compensation (position, angle) is not established. The resumption coincides with the drop in the camera housing temperature, but the drift does not come back when it rises: link not established. According to the expert, BREITHORN, MICHIGAN and NEBRASKA are in the same building: the cameras of the three stations tilt together, in the same direction and on the same dates (advance until 12 October, stop and slight backward movement from 13 to 16, resumption from the 17th to the end of the month), which points to a cause common to the building rather than a fault of this camera alone; at equal housing temperature, the cameras are more tilted at the end of the month than in the middle: temperature does not explain it alone, link not established. For the customer: the targets do not move relative to each other, this is not a movement of the structure; the camera tilt is to be monitored."}
+{"id": "BREITHORN-2", "start": "2026-10-03T00:00Z", "end": "2026-10-13T04:00Z", "family": "Displacement", "description": "From the start of the data to 13 October, six targets drift slowly and steadily, all in the same direction, mostly in corr_x, in corr_y too except POUI19: COLH20, COLI20, COLI21, COLJ19, POUI19 and POUI20; COLI24 drifts in the opposite direction in corr_y. Their drift follows the camera pose step by step, as the camera gradually tilts (tilt increasing, pan and rotation decreasing), while their position in the image hardly moves and their error_value stays stable; the other targets, such as POUH21, do not drift. Cause given by the expert: the camera is gradually nodding forward and the compensation of its movement is not complete, correcting some targets better than others. According to the expert, COLJ19 and POUI19, which drift the most, are much closer to the camera than the other targets; for the other drifting targets, the reason for their poorer compensation (position, angle) is not established. The temperature of the camera housing drops slightly over the range, link not established. According to the expert, BREITHORN, MICHIGAN and NEBRASKA are in the same building: the cameras of the three stations tilt together, in the same direction and on the same dates (advance until 12 October, stop and slight backward movement from 13 to 16, resumption from the 17th to the end of the month), which points to a cause common to the building rather than a fault of this camera alone; at equal housing temperature, the cameras are more tilted at the end of the month than in the middle: temperature does not explain it alone, link not established. For the customer: the targets do not move relative to each other, this is not a movement of the structure; the camera tilt is to be monitored.", "review": "2026-11-17", "analysis": "BREITHORN_2026-10-03T0000_2026-11-01T0000"}
+{"id": "BREITHORN-13", "start": "2026-10-16T20:00Z", "end": "2026-11-01T00:00Z", "family": "Displacement", "description": "From 17 October to the end of the batch, the drift resumes, faster than at the beginning of the month until the 25th, then clearly slower without stopping: the camera tilts again (tilt increasing, pan and rotation decreasing), and COLH20, COLI20, COLI21, COLJ19, POUI19 and POUI20 drift with it, mostly in corr_x and also in corr_y, POUI19 the most; COLI24 drifts in the opposite direction in corr_y. COLI22, COLH20''', POUI22 and POUI24 drift too, more noisily, between their own rejections. Their position in the image hardly moves, their error_value stays stable, POUH21 does not drift. Cause given by the expert: the camera is nodding forward and the compensation of its movement is not complete, correcting some targets better than others. According to the expert, COLJ19 and POUI19, which drift the most, are much closer to the camera than the other targets; for the other drifting targets, the reason for their poorer compensation (position, angle) is not established. The resumption coincides with the drop in the camera housing temperature, but the drift does not come back when it rises: link not established. According to the expert, BREITHORN, MICHIGAN and NEBRASKA are in the same building: the cameras of the three stations tilt together, in the same direction and on the same dates (advance until 12 October, stop and slight backward movement from 13 to 16, resumption from the 17th to the end of the month), which points to a cause common to the building rather than a fault of this camera alone; at equal housing temperature, the cameras are more tilted at the end of the month than in the middle: temperature does not explain it alone, link not established. For the customer: the targets do not move relative to each other, this is not a movement of the structure; the camera tilt is to be monitored.", "analysis": "BREITHORN_2026-10-03T0000_2026-11-01T0000"}
{"id": "BREITHORN-10", "start": "2026-10-13T00:00Z", "end": "2026-10-13T08:00Z", "family": "Obstruction", "description": "For the duration of one measurement, on 13 October in the morning, COLH20''' and COLI24 are rejected (curves absent) and POUI24, POUI22 and COLI22, partly hidden, jump in corr_x or in corr_y; everything returns at the next measurement. On the image of that hour, a car with its headlights on is in front of the bottom of the scene. The references hold. Point to ignore, the structure does not move.", "review": "2026-11-17", "analysis": "BREITHORN_2026-10-13T0000_2026-10-22T1600"}
{"id": "BREITHORN-39", "start": "2026-10-13T04:00Z", "end": "2026-10-16T20:00Z", "family": "Displacement", "description": "From 13 to 16 October, the slow drift stops and goes back a little: the camera straightens slightly (tilt decreasing, rotation rising), and the same targets, COLJ19, POUI19, COLI20, COLI21, POUI20 and COLH20, partly come back in corr_x, POUI19 most of all; it turns on the afternoon of 16 October, when the drift resumes (labelled apart). Cause according to the expert: parallax. Some targets are a few metres from the camera, others and the references several times farther; when the camera nods, its optical centre moves a little and the near targets shift more in the image than the far ones, while the compensation, a single image transformation fitted on the far references, treats all points as if they were at the same distance: the near targets are not fully corrected and seem to drift, the nearest the most. This is seen on the image: COLJ19 and POUI19, which drift the most, have very large blurred spots, COLI20, COLI21 and POUI20 large spots with a halo, the mark of targets close to the camera, out of focus; the references, POUH21, which does not drift, and the bottom targets have small sharp spots. COLH20 drifts although its spot is small: for it, the reason is not established. Their position in the image relative to each other hardly moves, their error_value stays stable. According to the expert, BREITHORN, MICHIGAN and NEBRASKA are in the same building: the cameras of MICHIGAN and NEBRASKA stop and move back on the same days; the return falls on days when the camera housing temperature no longer drops, link not established. For the customer: this is not a movement of the structure but an artifact of the compensation on the near targets; the camera tilt is to be monitored.", "analysis": "BREITHORN_2026-10-13T0000_2026-10-22T1600"}
{"id": "BREITHORN-12", "start": "2026-10-15T20:00Z", "end": "2026-10-16T12:00Z", "family": "No data", "description": "No measurement for any sensor during three acquisitions, in the night of 15 to 16 October, and no image; the curves then resume at the level they had before. The station was powered: full battery and normal voltage in the metrics until the early morning; the metrics are then missing for a few hours, then everything returns. The same gap affects the two other stations of the building (MICHIGAN, NEBRASKA, in the same building according to the expert), but also all the other stations. The gap starts at the same time, around 23:00, on the nine stations that were measuring then (LENZSPITZE only has its first measurements in the middle of that night, WILDSTRUBEL is already stopped), and their metrics stop at the same time on most of them; measurements and metrics resume at different times depending on the station, most of them in late morning. JUNGFRAU, whose metrics continue, accumulates unsent entries all night, sent in late morning, and yet its measurements for the night are missing from the data: a common cause outside the stations (transmission or reception of the data), not a shutdown of the stations; it is not established. The cause is therefore not specific to the building. The curves are missing over the range; nothing to do on the station if it does not repeat.", "review": "2026-11-17", "analysis": "BREITHORN_2026-10-13T0000_2026-10-22T1600"}
diff --git a/auto/CLARIDEN.jsonl b/auto/CLARIDEN.jsonl
index 39832a8..48c0e81 100644
--- a/auto/CLARIDEN.jsonl
+++ b/auto/CLARIDEN.jsonl
@@ -1,5 +1,5 @@
-{"id": "CLARIDEN-1", "start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The target P-300-B is rejected at every measurement of the batch: its recognition error stays almost at 1, its corrected curve is missing over the whole month. This has lasted since 29 September in the late afternoon, the time when the recognition error of other targets, including its neighbor P-301-B, also changes level all at once: a station setting changed that day. On the thumbnails (the 1st, the 15th and the 31st), the prism spot is sharp and bright, but next to the position where the system looks for it: the target seems badly configured or badly positioned, not hidden. Curve to ignore; correct the position of the target in the configuration or check the prism.", "review": "2026-11-17"}
-{"id": "CLARIDEN-14", "start": "2026-10-06T22:00Z", "end": "2026-10-11T06:00Z", "family": "Displacement", "description": "Slow drift of several targets over four days, made of small steps, then stabilization: D-303-B rises vertically, D-303-C and D-304-C rise vertically, D-301-C rises horizontally, D-306-B goes down horizontally. The camera moves: its tilt drifts slowly over the same days, with a small step on the 8th, and these targets follow it closely in the directions of their curves; the compensation does not absorb this tilt equally on every target. Ordinary recognition error, nothing on the images. The camera housing temperature stays almost constant over these days: no link with it. Slow return from the 11th to the 19th, labeled separately. Deduced from the curves and the camera pose: mostly a remainder of the camera tilt, not established as a movement of the structure; the camera is to be monitored, and these targets checked against the other measurements of the site."}
+{"id": "CLARIDEN-1", "start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The target P-300-B is rejected at every measurement of the batch: its recognition error stays almost at 1, its corrected curve is missing over the whole month. This has lasted since 29 September in the late afternoon, the time when the recognition error of other targets, including its neighbor P-301-B, also changes level all at once: a station setting changed that day. On the thumbnails (the 1st, the 15th and the 31st), the prism spot is sharp and bright, but next to the position where the system looks for it: the target seems badly configured or badly positioned, not hidden. Curve to ignore; correct the position of the target in the configuration or check the prism.", "review": "2026-11-17", "analysis": "CLARIDEN_2026-10-01T0000_2026-11-01T0000"}
+{"id": "CLARIDEN-14", "start": "2026-10-06T22:00Z", "end": "2026-10-11T06:00Z", "family": "Displacement", "description": "Slow drift of several targets over four days, made of small steps, then stabilization: D-303-B rises vertically, D-303-C and D-304-C rise vertically, D-301-C rises horizontally, D-306-B goes down horizontally. The camera moves: its tilt drifts slowly over the same days, with a small step on the 8th, and these targets follow it closely in the directions of their curves; the compensation does not absorb this tilt equally on every target. Ordinary recognition error, nothing on the images. The camera housing temperature stays almost constant over these days: no link with it. Slow return from the 11th to the 19th, labeled separately. Deduced from the curves and the camera pose: mostly a remainder of the camera tilt, not established as a movement of the structure; the camera is to be monitored, and these targets checked against the other measurements of the site.", "analysis": "CLARIDEN_2026-10-01T0000_2026-11-01T0000"}
{"id": "CLARIDEN-72", "start": "2026-10-11T06:00Z", "end": "2026-10-16T12:00Z", "family": "Displacement", "description": "The targets of row C slowly come back after their drift of the 6th to the 11th: D-301-C goes back down horizontally from the 11th to the 15th, D-304-C and D-303-C go back down vertically from the 12th until the first measurements after the gap of the night of the 15th to the 16th, then stay at that level until the 17th: the return is over. Their later movements are not part of it: the dip of the 18th and 19th follows the slow tilting of the camera and comes back at its jump of the 20th (both labeled separately). These movements do not follow the slight straightening of the camera of the 11th to the 13th either, which leaves only a remainder within the noise on the curves: they continue while the camera is still. Nothing in front of the targets on the image of the 13th. The housing temperature stays almost constant over these days: no link with it. This is the return of the drift of the 6th to the 11th, labeled separately. Cause not established, in a tunnel under construction: a movement of these targets is not excluded. To be checked against the other measurements of the site; monitor this row.", "analysis": "CLARIDEN_2026-10-11T0000_2026-10-20T0400"}
{"id": "CLARIDEN-50", "start": "2026-10-11T08:50Z", "end": "2026-10-11T09:10Z", "family": "Displacement", "description": "For one measurement, the corrected vertical curves of many targets drop together, then come back at the next one. D-304-A, D-301-A, D-303-A and D-302_A drop the most; D-301-C, D-302-B and PR_BG (same prism), P-299-B, P-301-B and P-299-A drop less. At that measurement, the whole scene shifts slightly in the image and the camera pose jumps (rotation, tilt), but the reference D-302-C does not follow the other references: the compensation is skewed for one measurement. The recognition error does not move. The image of that instant shows nothing in front of the targets. Cause not established; points to ignore, not a movement of the structure.", "analysis": "CLARIDEN_2026-10-11T0000_2026-10-20T0400"}
{"id": "CLARIDEN-52", "start": "2026-10-15T22:50Z", "end": "2026-10-16T10:30Z", "family": "No data", "description": "No measurement or image for almost twelve hours, on the night of 15 to 16, and no station metric. The gap starts at the same time, around 23:00, on the nine stations that were measuring then (LENZSPITZE only has its first measurements in the middle of that night, WILDSTRUBEL is already stopped), and their metrics stop at the same time on most of them; measurements and metrics resume at different times depending on the station, most of them in late morning. JUNGFRAU, whose metrics continue, accumulates unsent entries all night, sent in late morning, and yet its measurements for the night are missing from the data: a common cause outside the stations (transmission or reception of the data), not a shutdown of the stations; it is not established. In addition, at CLARIDEN, the station restarts on its battery: the voltage stays well below its usual level, without charge, until early afternoon, then charging resumes; its power supply was also missing that night. The curves are missing over the range; check the site power supply if it repeats.", "analysis": "CLARIDEN_2026-10-11T0000_2026-10-20T0400"}
diff --git a/auto/FLORIDA.jsonl b/auto/FLORIDA.jsonl
index 04ff218..16d8c9f 100644
--- a/auto/FLORIDA.jsonl
+++ b/auto/FLORIDA.jsonl
@@ -1,5 +1,5 @@
-{"id": "FLORIDA-1", "start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "Sellette 6 is a constantly problematic target: its error_value stays just above the threshold, a large part of its measurements are rejected all month, day and night, whatever the weather: its curve has gaps every day and its kept measurements jump. Seen on the thumbnails: a very small spot, almost invisible by day, very close to the halo of Sellette 5, which is much brighter; on the morning of the 20th, the measurement of Sellette 5 even latched onto the spot of Sellette 6. Ignore its curve; check the orientation or cleanliness of the prism.", "review": "2026-11-17"}
-{"id": "FLORIDA-14", "start": "2026-10-06T10:15Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "Massif 2 becomes a problematic target: by day, its spot is only a point (noon thumbnails of the 3rd and the 6th), and from the 6th its error_value goes above the threshold at times, measurements rejected by day; from the rain episode of the 8th, its spot also weakens at night and does not come back, the majority of its measurements are rejected day and night until the 29th, and its kept measurements change level (corr_y clearly going downward, corr_x going down at the end of the month). On the 30th and 31st, it is kept again, but just under the threshold and with a corr_y much lower than at the start of the month. Seen on the thumbnails: wide and bright spot at night in early October, small and weak afterwards, invisible by day on the 12th, 30th and 31st. Cause not established (prism tarnished, dirty or veiled). Ignore its curve; check the prism.", "review": "2026-11-17"}
+{"id": "FLORIDA-1", "start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "Sellette 6 is a constantly problematic target: its error_value stays just above the threshold, a large part of its measurements are rejected all month, day and night, whatever the weather: its curve has gaps every day and its kept measurements jump. Seen on the thumbnails: a very small spot, almost invisible by day, very close to the halo of Sellette 5, which is much brighter; on the morning of the 20th, the measurement of Sellette 5 even latched onto the spot of Sellette 6. Ignore its curve; check the orientation or cleanliness of the prism.", "review": "2026-11-17", "analysis": "FLORIDA_2026-10-01T0000_2026-11-01T0000"}
+{"id": "FLORIDA-14", "start": "2026-10-06T10:15Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "Massif 2 becomes a problematic target: by day, its spot is only a point (noon thumbnails of the 3rd and the 6th), and from the 6th its error_value goes above the threshold at times, measurements rejected by day; from the rain episode of the 8th, its spot also weakens at night and does not come back, the majority of its measurements are rejected day and night until the 29th, and its kept measurements change level (corr_y clearly going downward, corr_x going down at the end of the month). On the 30th and 31st, it is kept again, but just under the threshold and with a corr_y much lower than at the start of the month. Seen on the thumbnails: wide and bright spot at night in early October, small and weak afterwards, invisible by day on the 12th, 30th and 31st. Cause not established (prism tarnished, dirty or veiled). Ignore its curve; check the prism.", "review": "2026-11-17", "analysis": "FLORIDA_2026-10-01T0000_2026-11-01T0000"}
{"id": "FLORIDA-3", "start": "2026-10-01T09:45Z", "end": "2026-10-01T19:00Z", "family": "Thermal displacement", "description": "Thermal cycle of the day: with the rise of the housing temperature, the camera pose drifts (mostly the pan) until the middle of the afternoon, then returns at the end of the day; the corr_x of Sellette 6, Massif 2 and Sellette 4 rises a little during the day, the corr_y of Sellette 6 too, and returns in the evening. Deduced: the camera movement follows the housing temperature, ordinary error_value outside the other episodes. Thermal movement of the camera (and perhaps of the pipe carrying the targets): normal, nothing to do.", "review": "2026-11-17", "analysis": "FLORIDA_2026-10-01T0000_2026-10-11T0945"}
{"id": "FLORIDA-65", "start": "2026-10-01T20:30Z", "end": "2026-10-02T08:45Z", "family": "Visibility", "description": "Night of rain or mist: from 20:45 the error_value of all the targets and of both references rises together and the corrected curves of Sellette 4 and Sellette 5 already shift a little; from 21:00 p1_r (and its twin Sellette 3), Sellette 4 and Sellette 5 are rejected all night and the camera is no longer registered until the morning. From 21:00 to 22:30 the kept measurements of Massif 2 and Sellette 6 jump strongly downward in corr_y (compensation on r1_r alone); from 22:45 to about 02:00 almost all the sensors are rejected, then only rare points remain, still shifted. Seen on the 00:00 image: very weak spots, drops on the leaves in the foreground. Everything comes back in the morning, Sellette 4 last. The structure does not move: nothing to do, curves of the range to ignore.", "analysis": "FLORIDA_2026-10-01T0000_2026-10-11T0945"}
{"id": "FLORIDA-5", "start": "2026-10-02T01:45Z", "end": "2026-10-02T02:15Z", "family": "No data", "description": "One measurement absent for all sensors, although the image of that moment exists; the station synchronizes at that moment and its voltage is normal: it is running, the measurement is missing; measurements resume at the next one. SNCF01 has no data yet that day. This one-measurement gap in the night, around 02:00 UTC, falls on the same measurement at FLORIDA and SNCF01 on 09, 14 and 15/10, and only on them; other stations have the same night gap around the same hour in other weeks (JUNGFRAU and NORDEND in early September): a common cause outside the station, at night, is probable; it is not established. Nothing to do on the station if it does not get worse.", "review": "2026-11-17", "analysis": "FLORIDA_2026-10-01T0000_2026-10-11T0945"}
diff --git a/auto/JUNGFRAU.jsonl b/auto/JUNGFRAU.jsonl
index a62139f..5321e1d 100644
--- a/auto/JUNGFRAU.jsonl
+++ b/auto/JUNGFRAU.jsonl
@@ -1,4 +1,4 @@
-{"id": "JUNGFRAU-2", "start": "2026-09-30T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "PM_G is rejected at every measurement of the month, as almost always over the period of the data: its corrected curve is entirely missing, whatever the weather. Its error_value stays at the level of its neighbors PM_C and PM_D and follows the same variations; it is its threshold, lower than that of all the other targets, that it permanently exceeds. Images: its spot is sharp and round, like those of PM_C and PM_D, day and night. Cause not established: a badly set threshold rather than a damaged target, according to the images. Check the configuration of PM_G; ignore its curve.", "review": "2026-11-17"}
+{"id": "JUNGFRAU-2", "start": "2026-09-30T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "PM_G is rejected at every measurement of the month, as almost always over the period of the data: its corrected curve is entirely missing, whatever the weather. Its error_value stays at the level of its neighbors PM_C and PM_D and follows the same variations; it is its threshold, lower than that of all the other targets, that it permanently exceeds. Images: its spot is sharp and round, like those of PM_C and PM_D, day and night. Cause not established: a badly set threshold rather than a damaged target, according to the images. Check the configuration of PM_G; ignore its curve.", "review": "2026-11-17", "analysis": "JUNGFRAU_2026-09-30T0000_2026-11-01T0000"}
{"id": "JUNGFRAU-33", "start": "2026-10-10T16:15Z", "end": "2026-10-11T07:30Z", "family": "Thermal displacement", "description": "Cooling of the night: the corr_y of the bridge targets rises steadily until morning, the camera tilt follows. Deduced from the curves and the camera housing temperature, which drops: the bridge rises as it cools. Normal, nothing to do.", "review": "2026-11-17", "analysis": "JUNGFRAU_2026-10-10T1615_2026-10-21T1030"}
{"id": "JUNGFRAU-34", "start": "2026-10-11T07:30Z", "end": "2026-10-11T16:15Z", "family": "Thermal displacement", "description": "Warming of the day: the corr_y of the bridge targets sinks until the middle of the afternoon, then stays flat until nightfall; the camera pose follows. Deduced from the curves and the camera housing temperature. Normal, nothing to do.", "review": "2026-11-17", "analysis": "JUNGFRAU_2026-10-10T1615_2026-10-21T1030"}
{"id": "JUNGFRAU-100", "start": "2026-10-11T16:15Z", "end": "2026-10-12T07:30Z", "family": "Thermal displacement", "description": "Cooling of the evening and the night: from late afternoon the camera tilt rises again while the corr_y of the bridge targets stays at its trough, then from nightfall the corr_y of the bridge targets rises until morning, the camera tilt too; references stable, very stable error_value. Deduced from the curves and the camera housing temperature, which drops from late afternoon: the bridge rises as it cools, and the camera fixed to it compensates it poorly. Normal, nothing to do.", "analysis": "JUNGFRAU_2026-10-10T1615_2026-10-21T1030"}
diff --git a/auto/MICHIGAN.jsonl b/auto/MICHIGAN.jsonl
index 3b01a06..3333766 100644
--- a/auto/MICHIGAN.jsonl
+++ b/auto/MICHIGAN.jsonl
@@ -1,4 +1,4 @@
-{"id": "MICHIGAN-3", "start": "2026-10-09T08:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The reference REFPOU22 is lost on 9 October between the 08:00 measurement and the 12:00 one, and does not come back until the end of the month: its error_value rises almost to the maximum, it is rejected at every measurement and its raw positions wander far from its place. On the thumbnails, its spot, sharp at 04:00 and 08:00 on 9 October, has disappeared at 12:00 and does not come back (also seen on 12 October, 20 October and 31 October), while the neighboring spots and REF42, REFG43N are intact; no obstacle is visible. At 12:00 on 9 October, corr_x and corr_y of all the targets jump together and stay shifted, without a step in the raw positions: the compensation now only runs on REF42 and REFG43N, its reprojection error drops to zero and the basis changes. With these two references only, close to each other and far from the targets, the compensation is fragile: the curves of all the targets are more agitated than before, and the slightest deviation of these two references relative to the targets passes, amplified, into all the targets. At the same measurement, NEBRASKA, in the same building as MICHIGAN according to the expert, also loses one of its references (REFCOLH22), whose spot disappears in the same way with no visible obstacle: a cause common to both, in the building, is to be looked for; it is not established. The reference of the same name seen by BREITHORN stays sharp on its images. Cause of the loss not established (prism masked, turned or removed). For the customer: the jump is not a movement, and the corrected curves since 9 October are not very reliable; check the prism of REFPOU22 on site and restore it.", "review": "2026-11-17"}
+{"id": "MICHIGAN-3", "start": "2026-10-09T08:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The reference REFPOU22 is lost on 9 October between the 08:00 measurement and the 12:00 one, and does not come back until the end of the month: its error_value rises almost to the maximum, it is rejected at every measurement and its raw positions wander far from its place. On the thumbnails, its spot, sharp at 04:00 and 08:00 on 9 October, has disappeared at 12:00 and does not come back (also seen on 12 October, 20 October and 31 October), while the neighboring spots and REF42, REFG43N are intact; no obstacle is visible. At 12:00 on 9 October, corr_x and corr_y of all the targets jump together and stay shifted, without a step in the raw positions: the compensation now only runs on REF42 and REFG43N, its reprojection error drops to zero and the basis changes. With these two references only, close to each other and far from the targets, the compensation is fragile: the curves of all the targets are more agitated than before, and the slightest deviation of these two references relative to the targets passes, amplified, into all the targets. At the same measurement, NEBRASKA, in the same building as MICHIGAN according to the expert, also loses one of its references (REFCOLH22), whose spot disappears in the same way with no visible obstacle: a cause common to both, in the building, is to be looked for; it is not established. The reference of the same name seen by BREITHORN stays sharp on its images. Cause of the loss not established (prism masked, turned or removed). For the customer: the jump is not a movement, and the corrected curves since 9 October are not very reliable; check the prism of REFPOU22 on site and restore it.", "review": "2026-11-17", "analysis": "MICHIGAN_2026-10-09T0800_2026-11-01T0000"}
{"id": "MICHIGAN-1", "start": "2026-10-03T00:00Z", "end": "2026-10-05T16:00Z", "family": "Target issue", "description": "From the start of the data to 5 October at noon, COLH21' and REFH22' give exactly the same positions, the same error_value and the same corrected curves: the two sensors are placed on the same point of a group of spots, and their corr_y is clearly lower than that of their neighbors. At the 16:00 measurement on 5 October, they separate: on the 12:00 and 16:00 thumbnails, the scene is the same, but COLH21' is now centered on the top of the group and REFH22' on the bottom; their corr_y jumps toward that of their neighbors and stays there, their error_value drops. At the same moment, the raw positions of several other targets, including COLH18', change a little without their corrected curves moving, and the camera does not move. Cause deduced, not established: the sensors were reconfigured, and COLH21' and REFH22' were badly configured before, placed on the same point; the jump at 16:00 is the return to normal. For the customer: this is not a movement of the structure; the curves of COLH21' and REFH22' from before 5 October at 16:00 are not to be trusted and cannot be compared with those after; check that the current configuration of these two targets is the right one.", "review": "2026-11-17", "analysis": "MICHIGAN_2026-10-03T0000_2026-10-12T1600"}
{"id": "MICHIGAN-17", "start": "2026-10-04T20:00Z", "end": "2026-10-05T12:00Z", "family": "Thermal displacement", "description": "On 5 October, at the 00:00 measurement, the corr_y of all the targets rises together, a little, most clearly for COLH19N', POUH19N', COLH21'', COLH18S''' and COLH19N''; it partly comes back at 04:00, when the corr_x of several targets (COLH20'', POUH21'', COLH21' and REFH22') rises a little in turn; the corr_y of COLH19N', POUH19N' and COLH19N'' rises a little again at 08:00, then everything is back at 12:00. At the same time, the camera housing temperature drops at once and stays low until it rises again at 12:00, and the camera moves with it: at 00:00 its rotation turns and its tilt goes back a little, at 04:00 and 08:00 it nods forward and its scale drops, at 12:00 it comes back. The raw positions of all the sensors, references included, slide together, the targets without moving relative to each other; the reference REFPOU22 slides a little differently from the targets, and the compensation, still on three references, does not erase all of this movement. COLH21' and REFH22', still placed on the same point (labelled apart), move like the others. Same signature as the night of 6 October (labelled apart). Cause deduced from the curves, the camera pose and the camera housing temperature; nothing in front of the targets on the 00:00 and 08:00 images. Small deviation. For the customer: this is not a movement of the structure, nothing to do.", "analysis": "MICHIGAN_2026-10-03T0000_2026-10-12T1600"}
{"id": "MICHIGAN-18", "start": "2026-10-06T00:00Z", "end": "2026-10-06T20:00Z", "family": "Thermal displacement", "description": "On 6 October, at the 04:00 measurement, the corr_y of most targets goes down together, a little, COLH20', COLH21', REFH22', COLH21'', POUH21'' and COLH18S''' the most, and the corr_x of COLH21' and COLH20' rises a little; most come back at 08:00, but the corr_y of COLH18S''' stays low, and a little that of POUH18' and COLH18', until 16:00, and comes back at 20:00. At the same moment, the camera housing temperature makes a brief drop, lowest at 04:00, then rises again until 16:00; the camera nods forward (tilt rising, scale dropping) at 04:00, then comes back gradually until 16:00, and the raw positions of all the sensors, references included, slide together: it is the camera that moves, not the targets; the compensation, still on three references, does not erase all of this movement. The error_value of COLH18', POUH18' and COLH19N' rises a little at 04:00 and returns at 16:00. Same signature as the night of 5 October (labelled apart). Cause deduced from the curves, the camera pose and the camera housing temperature; nothing in front of the targets on the 04:00 image. Small deviation. For the customer: this is not a movement of the structure, nothing to do.", "analysis": "MICHIGAN_2026-10-03T0000_2026-10-12T1600"}
diff --git a/auto/NEBRASKA.jsonl b/auto/NEBRASKA.jsonl
index d184221..5d779d0 100644
--- a/auto/NEBRASKA.jsonl
+++ b/auto/NEBRASKA.jsonl
@@ -1,5 +1,5 @@
-{"id": "NEBRASKA-2", "start": "2026-10-09T08:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The reference REFCOLH22 is lost at the 9 October noon measurement and does not come back until the end of the month: its error_value jumps almost to the maximum and all its measurements are rejected. On the thumbnails, its spot, sharp and round until the morning of 9 October, has disappeared from its place at the next measurement, while the neighboring spot and the other references are intact; what made it disappear (prism fallen, removed, hidden) is not visible on the whole image. At the same measurement, MICHIGAN, in the same building as NEBRASKA according to the expert, also loses one of its references (REFPOU22), whose spot disappears in the same way with no visible obstacle: a cause common to both, in the building, is to be looked for; it is not established. At the loss, all the targets jump together in one step: corr_x upward, most on COLJ20, POUJ19, POUJ20 and POUH19, and corr_y upward on COLH19, COLH20, COLJ23 and COLJ24; the jump does not return, it is not a movement. The compensation then runs on the two only references REFH22 and REFP''21 (the corrections of these two references cancel): a more fragile basis, which no longer compensates the camera movement well and makes all the targets move at the slightest deviation of a reference. Very bad sign for the measurement: check the prism of REFCOLH22 on site and restore it.", "review": "2026-11-17"}
-{"id": "NEBRASKA-6", "start": "2026-10-16T20:00Z", "end": "2026-11-01T00:00Z", "family": "Displacement", "description": "Long upward drift of the corr_x of all the targets, strongest on the targets at the top and the right of the image (COLJ20, POUJ20, POUJ19, COLJ19, then COLH19, POUH19, COLH20) and weak in the image on those close to the references (COLH21, COLJ23, COLJ24), although COLJ24, far from the camera, drifts as much as the others in mm; the corr_y of COLH19, POUH19, POUJ20, COLJ19 and COLH20 goes down, that of POUH20 and COLH21 rises; no return at the end of the month. The camera keeps nodding forward as in the first half of the month (tilt rising, pan and rotation turning, scale dropping), and the compensation on two references only renders it poorly, so that the targets drift with it. The camera housing temperature drops from 16 October and the drift follows its jolts: fast rise until 19 October, slower until 24 October, stop and slight backward movement when the temperature rises again from 25 to 28 October, new rise with the cold of 28 and 29 October, slight backward movement when it rises again on 31 October. But the camera was already nodding forward from 3 to 12 October when the temperature was hardly dropping, and it stays more tilted at the end of the month than in the middle at equal temperature: temperature does not explain it alone, link not established. According to the expert, BREITHORN, MICHIGAN and NEBRASKA are in the same building: the cameras of the three stations tilt together, in the same direction and on the same dates (advance until 12 October, stop and slight backward movement from 13 to 16, resumption from the 17th to the end of the month), which points to a cause common to the building rather than a fault of this camera alone. Checked target by target (the raw positions against the overall movement of the targets, and a camera transformation fitted on the other targets): the scene does not move quite as a block, it deforms while the camera tilts. POUH20 moves away the most from the other targets, its neighbor POUH21 hardly at all; then COLH21, and the targets at the edges of the image (COLJ19, COLJ20, COLH19); hence the rise of the corr_y of POUH20 and COLH21. These deviations follow the camera tilt in both directions: POUH20 rises with it on 11 and 12 October, goes back down when it straightens from 13 to 16 October, rises fast with it from 17 to 19 October, then slowly until the end of the month; COLH21 only moves away from 18 October, when the camera exceeds its tilt of the 12th. It is the same movement as that of the camera, not a separate event; at equal tilt, POUH20 stays slightly higher after 17 October than before. Cause not established (the camera moving slightly as it tilts, targets at different distances, or a movement of the structure with the building). Deduced from the curves, the raw positions, the pose and the temperatures; images with nothing clear. For the customer: the camera tilts and the scene deforms with it: a movement of the structure is not established; to be monitored, the camera tilt and the curves of POUH20 and COLH21, which move away the most; restoring a third reference will make the curves reliable again."}
+{"id": "NEBRASKA-2", "start": "2026-10-09T08:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The reference REFCOLH22 is lost at the 9 October noon measurement and does not come back until the end of the month: its error_value jumps almost to the maximum and all its measurements are rejected. On the thumbnails, its spot, sharp and round until the morning of 9 October, has disappeared from its place at the next measurement, while the neighboring spot and the other references are intact; what made it disappear (prism fallen, removed, hidden) is not visible on the whole image. At the same measurement, MICHIGAN, in the same building as NEBRASKA according to the expert, also loses one of its references (REFPOU22), whose spot disappears in the same way with no visible obstacle: a cause common to both, in the building, is to be looked for; it is not established. At the loss, all the targets jump together in one step: corr_x upward, most on COLJ20, POUJ19, POUJ20 and POUH19, and corr_y upward on COLH19, COLH20, COLJ23 and COLJ24; the jump does not return, it is not a movement. The compensation then runs on the two only references REFH22 and REFP''21 (the corrections of these two references cancel): a more fragile basis, which no longer compensates the camera movement well and makes all the targets move at the slightest deviation of a reference. Very bad sign for the measurement: check the prism of REFCOLH22 on site and restore it.", "review": "2026-11-17", "analysis": "NEBRASKA_2026-10-09T0800_2026-11-01T0000"}
+{"id": "NEBRASKA-6", "start": "2026-10-16T20:00Z", "end": "2026-11-01T00:00Z", "family": "Displacement", "description": "Long upward drift of the corr_x of all the targets, strongest on the targets at the top and the right of the image (COLJ20, POUJ20, POUJ19, COLJ19, then COLH19, POUH19, COLH20) and weak in the image on those close to the references (COLH21, COLJ23, COLJ24), although COLJ24, far from the camera, drifts as much as the others in mm; the corr_y of COLH19, POUH19, POUJ20, COLJ19 and COLH20 goes down, that of POUH20 and COLH21 rises; no return at the end of the month. The camera keeps nodding forward as in the first half of the month (tilt rising, pan and rotation turning, scale dropping), and the compensation on two references only renders it poorly, so that the targets drift with it. The camera housing temperature drops from 16 October and the drift follows its jolts: fast rise until 19 October, slower until 24 October, stop and slight backward movement when the temperature rises again from 25 to 28 October, new rise with the cold of 28 and 29 October, slight backward movement when it rises again on 31 October. But the camera was already nodding forward from 3 to 12 October when the temperature was hardly dropping, and it stays more tilted at the end of the month than in the middle at equal temperature: temperature does not explain it alone, link not established. According to the expert, BREITHORN, MICHIGAN and NEBRASKA are in the same building: the cameras of the three stations tilt together, in the same direction and on the same dates (advance until 12 October, stop and slight backward movement from 13 to 16, resumption from the 17th to the end of the month), which points to a cause common to the building rather than a fault of this camera alone. Checked target by target (the raw positions against the overall movement of the targets, and a camera transformation fitted on the other targets): the scene does not move quite as a block, it deforms while the camera tilts. POUH20 moves away the most from the other targets, its neighbor POUH21 hardly at all; then COLH21, and the targets at the edges of the image (COLJ19, COLJ20, COLH19); hence the rise of the corr_y of POUH20 and COLH21. These deviations follow the camera tilt in both directions: POUH20 rises with it on 11 and 12 October, goes back down when it straightens from 13 to 16 October, rises fast with it from 17 to 19 October, then slowly until the end of the month; COLH21 only moves away from 18 October, when the camera exceeds its tilt of the 12th. It is the same movement as that of the camera, not a separate event; at equal tilt, POUH20 stays slightly higher after 17 October than before. Cause not established (the camera moving slightly as it tilts, targets at different distances, or a movement of the structure with the building). Deduced from the curves, the raw positions, the pose and the temperatures; images with nothing clear. For the customer: the camera tilts and the scene deforms with it: a movement of the structure is not established; to be monitored, the camera tilt and the curves of POUH20 and COLH21, which move away the most; restoring a third reference will make the curves reliable again.", "analysis": "NEBRASKA_2026-10-09T0800_2026-11-01T0000"}
{"id": "NEBRASKA-3", "start": "2026-10-13T04:00Z", "end": "2026-10-17T04:00Z", "family": "Displacement", "description": "Slow bump of the corr_y of the top targets (COLJ20, POUJ20, POUJ19, COLJ19, and a little COLH19 and POUH19): it rises by a notch on 13 October in the morning, stays high, then goes back down on 17 October in the morning; the corr_x of COLJ20 and POUJ20 recedes a little at the same time. At the same moment the camera goes back: its tilt goes back down from its peak of 12 October and its pan goes to its lowest of the month, then goes up again on 17 October. The camera housing temperature rises a little at the start then stays stable: link not established. According to the expert, BREITHORN, MICHIGAN and NEBRASKA are in the same building: the cameras of BREITHORN and MICHIGAN stop and move back on the same days. Deduced from the curves and the pose: it is the camera that moves, poorly compensated with two references, and the scene deforms with it: POUH20 goes back down with it. For the customer: the camera straightens and the scene deforms with it: a movement of the structure is not established; the camera tilt is to be monitored, and restoring a third reference will make the curves reliable again.", "review": "2026-11-17", "analysis": "NEBRASKA_2026-10-13T0000_2026-10-22T0000"}
{"id": "NEBRASKA-4", "start": "2026-10-15T20:00Z", "end": "2026-10-16T12:00Z", "family": "No data", "description": "No measurement for any sensor for three measurements, in the night of 15 to 16 October: all the curves are missing, then resume at the same level as before the gap. The station metrics (voltage, temperatures) are also missing over the same range; the voltage is normal just before and just after, so it is not a lack of energy. The same gap affects the two other stations of the building (BREITHORN, MICHIGAN, in the same building according to the expert), but also all the other stations. The gap starts at the same time, around 23:00, on the nine stations that were measuring then (LENZSPITZE only has its first measurements in the middle of that night, WILDSTRUBEL is already stopped), and their metrics stop at the same time on most of them; measurements and metrics resume at different times depending on the station, most of them in late morning. JUNGFRAU, whose metrics continue, accumulates unsent entries all night, sent in late morning, and yet its measurements for the night are missing from the data: a common cause outside the stations (transmission or reception of the data), not a shutdown of the stations; it is not established. The cause is therefore not specific to the building. The curves are missing over the range; nothing to do on the station if it does not repeat.", "review": "2026-11-17", "analysis": "NEBRASKA_2026-10-13T0000_2026-10-22T0000"}
{"id": "NEBRASKA-5", "start": "2026-10-16T20:00Z", "end": "2026-10-17T20:00Z", "family": "Displacement", "description": "The corr_x of COLJ19 alone jumps upward at the midnight measurement on 17 October, stays high all day, then partly returns in the evening; its neighbors do not jump. Its raw position in the image shifts by as much relative to the other targets, without the camera moving at that moment or its error_value changing; nothing on the thumbnails. It is not an effect of the compensation; cause not established, deduced from the curves and the raw positions. To be checked: look at the target and monitor its curve.", "review": "2026-11-17", "analysis": "NEBRASKA_2026-10-13T0000_2026-10-22T0000"}
diff --git a/auto/NIEDERHORN.jsonl b/auto/NIEDERHORN.jsonl
index 8935da3..7d88834 100644
--- a/auto/NIEDERHORN.jsonl
+++ b/auto/NIEDERHORN.jsonl
@@ -1,10 +1,10 @@
-{"id": "NIEDERHORN-2", "start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The target e03 is rejected at almost every measurement of the batch: its corrected curve does not exist (a few isolated points at most). Seen on the thumbnails: no spot is visible at its position on the thumbnails, day and night. It is not the weather: it is permanent, day and night. Act on the target or its configuration; ignore its curve.", "review": "2026-11-17"}
-{"id": "NIEDERHORN-3", "start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The target e04 is rejected at almost every measurement of the batch: its corrected curve does not exist (a few isolated points at most). Seen on the thumbnails: no sharp spot is visible at its position on the thumbnails, only a small glow by day. It is not the weather: it is permanent, day and night. Act on the target or its configuration; ignore its curve.", "review": "2026-11-17"}
-{"id": "NIEDERHORN-4", "start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The target e05 is rejected at almost every measurement of the batch: its corrected curve does not exist (a few isolated points at most). Seen on the thumbnails: no spot is visible at its position on the thumbnails, day and night. It is not the weather: it is permanent, day and night. Act on the target or its configuration; ignore its curve.", "review": "2026-11-17"}
-{"id": "NIEDERHORN-5", "start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The target e07 is rejected at almost every measurement of the batch: its corrected curve does not exist (a few isolated points at most). Seen on the thumbnails: its spot is visible but between two very close neighbors; its recognition error stays above the threshold. It is not the weather: it is permanent, day and night. Act on the target or its configuration; ignore its curve.", "review": "2026-11-17"}
-{"id": "NIEDERHORN-6", "start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The target e08 is rejected at almost every measurement of the batch: its corrected curve does not exist (a few isolated points at most). Seen on the thumbnails: its spot is visible but between two very close neighbors; its recognition error stays above the threshold. It is not the weather: it is permanent, day and night. Act on the target or its configuration; ignore its curve.", "review": "2026-11-17"}
-{"id": "NIEDERHORN-7", "start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The target e11 is rejected at almost every measurement of the batch: its corrected curve does not exist (a few isolated points at most). Seen on the thumbnails: its spot is very large and dazzled at night, stuck to a small neighbor; its error stays above the threshold. It is not the weather: it is permanent, day and night. Act on the target or its configuration; ignore its curve.", "review": "2026-11-17"}
-{"id": "NIEDERHORN-8", "start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The target e12 is rejected at almost every measurement of the batch: its corrected curve does not exist (a few isolated points at most). Seen on the thumbnails: its spot is very large and dazzled at night, stuck to a small neighbor; its error stays above the threshold. It is not the weather: it is permanent, day and night. Act on the target or its configuration; ignore its curve.", "review": "2026-11-17"}
+{"id": "NIEDERHORN-2", "start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The target e03 is rejected at almost every measurement of the batch: its corrected curve does not exist (a few isolated points at most). Seen on the thumbnails: no spot is visible at its position on the thumbnails, day and night. It is not the weather: it is permanent, day and night. Act on the target or its configuration; ignore its curve.", "review": "2026-11-17", "analysis": "NIEDERHORN_2026-10-01T0000_2026-11-01T0000"}
+{"id": "NIEDERHORN-3", "start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The target e04 is rejected at almost every measurement of the batch: its corrected curve does not exist (a few isolated points at most). Seen on the thumbnails: no sharp spot is visible at its position on the thumbnails, only a small glow by day. It is not the weather: it is permanent, day and night. Act on the target or its configuration; ignore its curve.", "review": "2026-11-17", "analysis": "NIEDERHORN_2026-10-01T0000_2026-11-01T0000"}
+{"id": "NIEDERHORN-4", "start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The target e05 is rejected at almost every measurement of the batch: its corrected curve does not exist (a few isolated points at most). Seen on the thumbnails: no spot is visible at its position on the thumbnails, day and night. It is not the weather: it is permanent, day and night. Act on the target or its configuration; ignore its curve.", "review": "2026-11-17", "analysis": "NIEDERHORN_2026-10-01T0000_2026-11-01T0000"}
+{"id": "NIEDERHORN-5", "start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The target e07 is rejected at almost every measurement of the batch: its corrected curve does not exist (a few isolated points at most). Seen on the thumbnails: its spot is visible but between two very close neighbors; its recognition error stays above the threshold. It is not the weather: it is permanent, day and night. Act on the target or its configuration; ignore its curve.", "review": "2026-11-17", "analysis": "NIEDERHORN_2026-10-01T0000_2026-11-01T0000"}
+{"id": "NIEDERHORN-6", "start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The target e08 is rejected at almost every measurement of the batch: its corrected curve does not exist (a few isolated points at most). Seen on the thumbnails: its spot is visible but between two very close neighbors; its recognition error stays above the threshold. It is not the weather: it is permanent, day and night. Act on the target or its configuration; ignore its curve.", "review": "2026-11-17", "analysis": "NIEDERHORN_2026-10-01T0000_2026-11-01T0000"}
+{"id": "NIEDERHORN-7", "start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The target e11 is rejected at almost every measurement of the batch: its corrected curve does not exist (a few isolated points at most). Seen on the thumbnails: its spot is very large and dazzled at night, stuck to a small neighbor; its error stays above the threshold. It is not the weather: it is permanent, day and night. Act on the target or its configuration; ignore its curve.", "review": "2026-11-17", "analysis": "NIEDERHORN_2026-10-01T0000_2026-11-01T0000"}
+{"id": "NIEDERHORN-8", "start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The target e12 is rejected at almost every measurement of the batch: its corrected curve does not exist (a few isolated points at most). Seen on the thumbnails: its spot is very large and dazzled at night, stuck to a small neighbor; its error stays above the threshold. It is not the weather: it is permanent, day and night. Act on the target or its configuration; ignore its curve.", "review": "2026-11-17", "analysis": "NIEDERHORN_2026-10-01T0000_2026-11-01T0000"}
{"id": "NIEDERHORN-1", "start": "2026-10-01T00:00Z", "end": "2026-10-01T02:00Z", "family": "No data", "description": "One measurement is missing for all sensors, references and targets: one point absent on all the curves. The station is running (metrics present at that hour, normal voltage before and after); the cause of the gap is not established (measurement not made or not transmitted). The curves resume at the next measurement without a jump: nothing to do.", "review": "2026-11-17", "analysis": "NIEDERHORN_2026-10-01T0000_2026-10-11T0500"}
{"id": "NIEDERHORN-140", "start": "2026-10-01T02:00Z", "end": "2026-10-01T03:00Z", "family": "Obstruction", "description": "PWD_IMP_B07_016_C09 alone, at the first measurement after the missing one, in the night: its corr_x and corr_y jump clearly for one measurement, without rejection, its recognition error a little lower, then come back; its neighbours and the references do not move. Cause seen on the 02:00 thumbnail: the tip of a leaf touches the spot; it is the foreground plant, shaken by the wind, which, according to the expert, passes in front of this target. The structure does not move: ignore this target's curve over the range.", "analysis": "NIEDERHORN_2026-10-01T0000_2026-10-11T0500"}
{"id": "NIEDERHORN-141", "start": "2026-10-01T04:00Z", "end": "2026-10-01T17:00Z", "family": "Visibility", "description": "At night and in the morning, for several hours: the recognition error of many targets rises, many are rejected at times (mostly PWD_IMP_B07_018_C09, PWD_RMP_B15_019_C09, PWD_RMP_B12_018_C09, e09, PWD_IMP_B07_017_C09 and PWD_RMP_B12_017_C09, once or twice PWD_RMP_B12_019_C09, PWD_RMP_B15_018_C09, e02, e06, e10 and PWD_RMP_B16_026_C09) and the corr_x of the targets on the left dips clearly (PWD_RMP_B15_020_C09, e15, e10, e14, e13, PWD_RMP_B16_026_C09, PWD_IMP_B08_025_C09); the references hold, higher up on the road. Gradual return in late morning: PWD_IMP_B07_018_C09, rejected until 15:00, PWD_RMP_B17_026_C09 and e09 still stand away from their level at 16:00, then come back. Cause seen on the 07:00 image: a noisy background, faint out-of-focus drops on the glass, weaker spots, nothing in front (according to the expert, a rainy night at this station). The structure does not move: do not trust the curves over the range. PWD_IMP_B07_016_C09, moved by the foreground plant during the same hours, is labelled apart.", "analysis": "NIEDERHORN_2026-10-01T0000_2026-10-11T0500"}
diff --git a/auto/NORDEND.jsonl b/auto/NORDEND.jsonl
index 28993c1..de6f36d 100644
--- a/auto/NORDEND.jsonl
+++ b/auto/NORDEND.jsonl
@@ -1,7 +1,7 @@
-{"id": "NORDEND-24", "start": "2026-08-17T05:15Z", "end": "2026-10-01T00:00Z", "family": "Target issue", "description": "PR04: its spot is much weaker than that of its neighbours PR03 and PR05, by day as by night (thumbnails of 14, 22, 26/08, 07, 12 and 23/09), and its error_value, already several times that of its neighbours, rises over the weeks. It is rejected almost every day, by day as by night, a good part of the time from 21 to 25/08 and from 06 to 08/09, almost without interruption from 18 to 28/09; the rejections become rare on 30/09. Between the rejections, its corr_x and corr_y curves are much noisier than those of its neighbours and change level, without the neighbours following. At night, lit cobweb threads pass over its area (23/09 image at 00:00), without explaining the whole range. The disturbance continues in October, weaker (next label, from 01/10). Cause not established (dirt, orientation, cobweb). This is not a movement: ignore its curve; check the target on site.", "review": "2026-11-17"}
-{"id": "NORDEND-152", "start": "2026-10-01T00:00Z", "end": "2026-10-26T20:45Z", "family": "Target issue", "description": "PR04: usual error_value several times higher than that of its neighbours, scattered rejections almost every day, by day as by night, and corrected curves twice as noisy; the target is not hidden on the images. This is the continuation of a stronger disturbance in September, when it was almost always rejected. After the rain of 24 to 25, its error_value falls back to the level of the others during 26, after a last departure in early evening, and the rejections stop: the target (or whatever was soiling it) has probably been cleaned. Afterwards its curves, calm, stay lower than at the beginning of the month, in corr_x and in corr_y, until the end of the batch: the level measured during the disturbance is not a reference. Cause not established beyond that. Do not trust its curve over the range; check the target if it comes back.", "review": "2026-11-17"}
-{"id": "NORDEND-169", "start": "2026-10-08T02:15Z", "end": "2026-11-07T14:00Z", "family": "Obstruction", "description": "PR17: a blurred pale disc (mark on the window lit by the infrared) sharpens just under its spot at 02:30 and covers part of it (thumbnails of 08/10 at 02:00 and 02:45, then of the following nights; still visible, weaker, on 26, 29 and 31/10, and as a pale area under the spot on 04/11). In one step, its corr_y drops and its corr_x rises markedly, only PR17 moves, its neighbours do not, and its error_value doubles and stays high. This step brings the corr_y of PR17 back to roughly its level from before its jump of 05/09 (separate label, Displacement, plateau until that day); but the September jump had only touched its corr_y, without raising its error_value, and no disc was visible then: the step comes from the mark, and that it also undoes the September plateau is not established. Its curves still change level in steps: a partial return at 23:00 on the 12th, in the middle of a back-and-forth of the camera from 22:30 to 00:15 (labelled separately, Displacement) that moves the other targets too; they come back after it, PR17 keeps its new level, so its step is its own and not the camera; then new offsets from 21 to 24. After the rain of 24 to 25, its error_value falls back to its earlier level, but its curves come back neither to their level of the beginning of the month (the September plateau) nor to that from before the jump of 05/09, and stay so until the end of the range, the disc still visible. Cause seen on the images; the exact nature of the mark is not established. This is not a movement of PR17; ignore its curve over the range, clean the window."}
-{"id": "NORDEND-195", "start": "2026-10-16T19:00Z", "end": "2026-11-07T14:00Z", "family": "Target issue", "description": "CTR01 (local reference, read as a target): from the evening of the 16th, its error_value no longer falls back to its level of the beginning of the month and keeps rising until the end of the month, very close to the threshold then above it; the measurement is rejected a large part of the time, by night as by day, every day, almost without stopping from the end of October to the afternoon of 02/11, then still about half of the time until the end of the range; its curve is missing or stays very noisy. Before the 16th, it was only rejected on sunny afternoons and during the nights when the left-edge spots fade out (separate labels). On the images, its spot is weak; at the end of the month, blurred marks left on the window after the rain pass near it (26/10 image at 03:00), then a pale blurred band covers it (31/10 image at 03:00). Cause not established: state of the prism, or of the window in front of it, to be checked. Ignore its curve; intervene on the target."}
+{"id": "NORDEND-24", "start": "2026-08-17T05:15Z", "end": "2026-10-01T00:00Z", "family": "Target issue", "description": "PR04: its spot is much weaker than that of its neighbours PR03 and PR05, by day as by night (thumbnails of 14, 22, 26/08, 07, 12 and 23/09), and its error_value, already several times that of its neighbours, rises over the weeks. It is rejected almost every day, by day as by night, a good part of the time from 21 to 25/08 and from 06 to 08/09, almost without interruption from 18 to 28/09; the rejections become rare on 30/09. Between the rejections, its corr_x and corr_y curves are much noisier than those of its neighbours and change level, without the neighbours following. At night, lit cobweb threads pass over its area (23/09 image at 00:00), without explaining the whole range. The disturbance continues in October, weaker (next label, from 01/10). Cause not established (dirt, orientation, cobweb). This is not a movement: ignore its curve; check the target on site.", "review": "2026-11-17", "analysis": "NORDEND_2026-08-17T0515_2026-11-07T1400"}
+{"id": "NORDEND-152", "start": "2026-10-01T00:00Z", "end": "2026-10-26T20:45Z", "family": "Target issue", "description": "PR04: usual error_value several times higher than that of its neighbours, scattered rejections almost every day, by day as by night, and corrected curves twice as noisy; the target is not hidden on the images. This is the continuation of a stronger disturbance in September, when it was almost always rejected. After the rain of 24 to 25, its error_value falls back to the level of the others during 26, after a last departure in early evening, and the rejections stop: the target (or whatever was soiling it) has probably been cleaned. Afterwards its curves, calm, stay lower than at the beginning of the month, in corr_x and in corr_y, until the end of the batch: the level measured during the disturbance is not a reference. Cause not established beyond that. Do not trust its curve over the range; check the target if it comes back.", "review": "2026-11-17", "analysis": "NORDEND_2026-08-17T0515_2026-11-07T1400"}
+{"id": "NORDEND-169", "start": "2026-10-08T02:15Z", "end": "2026-11-07T14:00Z", "family": "Obstruction", "description": "PR17: a blurred pale disc (mark on the window lit by the infrared) sharpens just under its spot at 02:30 and covers part of it (thumbnails of 08/10 at 02:00 and 02:45, then of the following nights; still visible, weaker, on 26, 29 and 31/10, and as a pale area under the spot on 04/11). In one step, its corr_y drops and its corr_x rises markedly, only PR17 moves, its neighbours do not, and its error_value doubles and stays high. This step brings the corr_y of PR17 back to roughly its level from before its jump of 05/09 (separate label, Displacement, plateau until that day); but the September jump had only touched its corr_y, without raising its error_value, and no disc was visible then: the step comes from the mark, and that it also undoes the September plateau is not established. Its curves still change level in steps: a partial return at 23:00 on the 12th, in the middle of a back-and-forth of the camera from 22:30 to 00:15 (labelled separately, Displacement) that moves the other targets too; they come back after it, PR17 keeps its new level, so its step is its own and not the camera; then new offsets from 21 to 24. After the rain of 24 to 25, its error_value falls back to its earlier level, but its curves come back neither to their level of the beginning of the month (the September plateau) nor to that from before the jump of 05/09, and stay so until the end of the range, the disc still visible. Cause seen on the images; the exact nature of the mark is not established. This is not a movement of PR17; ignore its curve over the range, clean the window.", "analysis": "NORDEND_2026-08-17T0515_2026-11-07T1400"}
+{"id": "NORDEND-195", "start": "2026-10-16T19:00Z", "end": "2026-11-07T14:00Z", "family": "Target issue", "description": "CTR01 (local reference, read as a target): from the evening of the 16th, its error_value no longer falls back to its level of the beginning of the month and keeps rising until the end of the month, very close to the threshold then above it; the measurement is rejected a large part of the time, by night as by day, every day, almost without stopping from the end of October to the afternoon of 02/11, then still about half of the time until the end of the range; its curve is missing or stays very noisy. Before the 16th, it was only rejected on sunny afternoons and during the nights when the left-edge spots fade out (separate labels). On the images, its spot is weak; at the end of the month, blurred marks left on the window after the rain pass near it (26/10 image at 03:00), then a pale blurred band covers it (31/10 image at 03:00). Cause not established: state of the prism, or of the window in front of it, to be checked. Ignore its curve; intervene on the target.", "analysis": "NORDEND_2026-08-17T0515_2026-11-07T1400"}
{"id": "NORDEND-181", "start": "2026-10-13T07:45Z", "end": "2026-10-14T05:00Z", "family": "Thermal displacement", "description": "Weak thermal cycle of the camera: overcast day, the housing temperature only rises a little (highest around 15:00); the pan drops a little, the tilt barely rises; the camera comes back in the evening and at night, until the dawn mist of the 14th (separate label). The compensation absorbs it poorly, and for a long time: the corr_x of PR18 drops strongly in early afternoon and only comes back in the night (still strongly at 19:00), that of PR16 and PR14 as much; the corr_y of most of the other targets drops a little to markedly all day and evening, and the references depart a little (CTR02, CTR03, CTR04). Deduced cause: the pose follows the housing temperature, and the rock face of the quarry does not move with the temperature. The structure does not move, nothing to do.", "review": "2026-11-17", "analysis": "NORDEND_2026-10-13T0745_2026-10-24T1630"}
{"id": "NORDEND-182", "start": "2026-10-13T09:15Z", "end": "2026-10-13T11:00Z", "family": "Visibility", "description": "In mid-morning, the error_value of the reference CTR04 and of several targets rises markedly, without getting CTR04 discarded; PR07 then PR04 are rejected and their curves are missing, and the corrections of most of the targets (PR06, PR08, PR14, PR15, PR16 above all) fluctuate and jump together at times; everything calms down when the error_value of CTR04 falls back. On the 10:00 image, overcast sky, veiled sun at the top of the image, nothing in front of the targets. Cause not established: a poorer visibility, which disturbs a reference without getting it discarded. Not a movement; do not trust the curves over the range.", "review": "2026-11-17", "analysis": "NORDEND_2026-10-13T0745_2026-10-24T1630"}
{"id": "NORDEND-265", "start": "2026-10-13T12:15Z", "end": "2026-10-13T12:45Z", "family": "Visibility", "description": "Around midday, for one measurement, the spots shrink and weaken over the group (12:30 thumbnails of PR07, PR14 and PR16, against 12:15 and 12:45), under an overcast sky, with nothing in front: PR07 is rejected and its curve is missing, and the corr_x of most of the targets drops clearly together (PR16, PR15, PR14, PR13, PR05, PR06, PR08 the most), the references not moving; everything comes back at the next measurement. Cause seen on the thumbnails: a passing drop of the light on the scene. Not a movement; ignore this point.", "analysis": "NORDEND_2026-10-13T0745_2026-10-24T1630"}
diff --git a/auto/SNCF01.jsonl b/auto/SNCF01.jsonl
index ac5c91d..8329444 100644
--- a/auto/SNCF01.jsonl
+++ b/auto/SNCF01.jsonl
@@ -1,8 +1,8 @@
-{"id": "SNCF01-1", "start": "2026-10-04T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "BG.1: all its measurements are rejected, from the start of the data to the end of the batch; its curve is missing entirely. Its recognition error stays above the threshold, by day and by night, whatever the weather; on the night image its spot appears doubled. Target permanently poorly seen (orientation, installation or configuration to be checked): act on the target; no curve to read.", "review": "2026-11-17"}
-{"id": "SNCF01-2", "start": "2026-10-04T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "F4.1: all its measurements are rejected over the batch; its curve is missing entirely. Its recognition error stays above the threshold permanently; on the images its spot is small and faint. Target permanently poorly seen: act on the target; no curve to read.", "review": "2026-11-17"}
-{"id": "SNCF01-3", "start": "2026-10-04T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "CV.7: most of its measurements are rejected over the whole batch, its recognition error oscillating around the threshold; its curve has only scattered points, and the last ones accepted, at the end of the batch, move strongly away from its level without anything else moving. Target permanently poorly seen (by day, its spot touches the edge of a bright structure on the image): act on the target; ignore its curve.", "review": "2026-11-17"}
-{"id": "SNCF01-4", "start": "2026-10-04T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "F4.4: most of its measurements are rejected over the whole batch, its recognition error staying stuck to the threshold; its curve has only scattered, noisy points. Faint, doubled spot on the night image. Target permanently poorly seen: act on the target; ignore its curve.", "review": "2026-11-17"}
-{"id": "SNCF01-7", "start": "2026-10-04T00:00Z", "end": "2026-11-01T00:00Z", "family": "Displacement", "description": "Over the whole batch, as one single episode, the corrected curves of many targets drift slowly, with no return: corr_y rises on BG.2, F4.5, F4.6, P4, CV.8, F4.3, P5, and drops on P1, P7, CV.1; corr_x drops on P2, P3, P4, F4.6; the drift flattens at the end of the month; part of the drop of P7, CV.1 comes from the jump of 15/10 in the morning, labelled separately. At the same time, the camera rotation drops and its tilt rises slowly, the reprojection error of the references increases and, relative to the overall movement of the targets, the positions of the targets relative to one another change more and more over the month (P1, P7, F4.5, BG.2 especially), like those of the references: the whole scene slowly deforms in the image, while the camera tilts. No temperature is available for this station (empty metrics); the cause is not established (seasonal cooling, incomplete compensation of the camera tilt, a reference that moves, or a movement of the wall). The movement of the structure is not established: to be watched.", "review": "2026-11-17"}
+{"id": "SNCF01-1", "start": "2026-10-04T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "BG.1: all its measurements are rejected, from the start of the data to the end of the batch; its curve is missing entirely. Its recognition error stays above the threshold, by day and by night, whatever the weather; on the night image its spot appears doubled. Target permanently poorly seen (orientation, installation or configuration to be checked): act on the target; no curve to read.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-04T0000_2026-11-01T0000"}
+{"id": "SNCF01-2", "start": "2026-10-04T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "F4.1: all its measurements are rejected over the batch; its curve is missing entirely. Its recognition error stays above the threshold permanently; on the images its spot is small and faint. Target permanently poorly seen: act on the target; no curve to read.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-04T0000_2026-11-01T0000"}
+{"id": "SNCF01-3", "start": "2026-10-04T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "CV.7: most of its measurements are rejected over the whole batch, its recognition error oscillating around the threshold; its curve has only scattered points, and the last ones accepted, at the end of the batch, move strongly away from its level without anything else moving. Target permanently poorly seen (by day, its spot touches the edge of a bright structure on the image): act on the target; ignore its curve.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-04T0000_2026-11-01T0000"}
+{"id": "SNCF01-4", "start": "2026-10-04T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "F4.4: most of its measurements are rejected over the whole batch, its recognition error staying stuck to the threshold; its curve has only scattered, noisy points. Faint, doubled spot on the night image. Target permanently poorly seen: act on the target; ignore its curve.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-04T0000_2026-11-01T0000"}
+{"id": "SNCF01-7", "start": "2026-10-04T00:00Z", "end": "2026-11-01T00:00Z", "family": "Displacement", "description": "Over the whole batch, as one single episode, the corrected curves of many targets drift slowly, with no return: corr_y rises on BG.2, F4.5, F4.6, P4, CV.8, F4.3, P5, and drops on P1, P7, CV.1; corr_x drops on P2, P3, P4, F4.6; the drift flattens at the end of the month; part of the drop of P7, CV.1 comes from the jump of 15/10 in the morning, labelled separately. At the same time, the camera rotation drops and its tilt rises slowly, the reprojection error of the references increases and, relative to the overall movement of the targets, the positions of the targets relative to one another change more and more over the month (P1, P7, F4.5, BG.2 especially), like those of the references: the whole scene slowly deforms in the image, while the camera tilts. No temperature is available for this station (empty metrics); the cause is not established (seasonal cooling, incomplete compensation of the camera tilt, a reference that moves, or a movement of the wall). The movement of the structure is not established: to be watched.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-04T0000_2026-11-01T0000"}
{"id": "SNCF01-39", "start": "2026-10-14T07:15Z", "end": "2026-10-15T01:15Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (14/10): from the morning, the pan and the tilt of the camera drop and its scale rises, then they slowly come back in the afternoon, the evening and the night, until the camera comes to rest around one in the morning; the two-in-the-morning gap and the camera jump of the early morning, labelled separately, come after this rest. The corrected curves follow the same cycle, poorly compensated: corr_x of P7, P5, P6 and corr_y of P5, P6, P7, P4 move away from their night level during the day then come back, partly all at once at nightfall, when the recognition error also comes back (the lighting plays a part). Deduced cause: the camera and its mount move with the heat of the day (camera pose); the structure, a masonry wall, is not supposed to move like that. No temperature is available to confirm it. Normal, nothing to do.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-14T0645_2026-10-22T1030"}
{"id": "SNCF01-98", "start": "2026-10-14T09:30Z", "end": "2026-10-14T16:30Z", "family": "Visibility", "description": "By day (14/10), in the sun (hard shadows on the wall on the image of 13:00): the corrected curves of the low targets fluctuate much more than at night, from one measurement to the next, with one-measurement jumps that come back at once, mostly CV.4, CV.2, F4.3, CV.6, F4.2, BG.2, F4.5 and F4.6, and CV.2 and CV.4 are rejected at times; the night before and the evening after are calm. Deduced cause: heat shimmer from the air heated above the tracks (a fast noise over the scene, by sunny day only), not visible as such on the images; some rejections of CV.2 and CV.4, low targets, may also come from passages, not seen. Do not trust the small movements of these curves by day; this is not a movement of the structure.", "analysis": "SNCF01_2026-10-14T0645_2026-10-22T1030"}
{"id": "SNCF01-99", "start": "2026-10-14T10:30Z", "end": "2026-10-14T11:00Z", "family": "Obstruction", "description": "One single measurement: CV.2, CV.4 and CV.8 are rejected, their curves are missing, the recognition error of the reference BG.3.1 jumps strongly while staying under its threshold, and CV.6, F4.2 and F4.6 make a corr jump that comes back at the next measurement. Cause: a passage in front of the bottom of the scene and of BG.3.1, deduced from the signature (several low targets and a reference hit together for one measurement; no image at that minute, the station takes one per hour). The structure is not moving: point to ignore, nothing to do.", "analysis": "SNCF01_2026-10-14T0645_2026-10-22T1030"}
diff --git a/auto/WILDSTRUBEL.jsonl b/auto/WILDSTRUBEL.jsonl
index b78f4e7..492e18a 100644
--- a/auto/WILDSTRUBEL.jsonl
+++ b/auto/WILDSTRUBEL.jsonl
@@ -1,8 +1,8 @@
-{"id": "WILDSTRUBEL-46", "start": "2026-09-07T00:00Z", "end": "2026-10-01T00:00Z", "family": "Target issue", "description": "The reference R3 is rejected on every measured day of the batch (from 07 to 09/09, then from 22 to 30/09), from sunrise until mid-afternoon, and almost never at night: by day, its error_value stays above its threshold at almost every measurement, a little less often in the last days of September; at night, it is well below. On its daytime thumbnail (30/09 at 10:00), its spot cannot be seen, while those of R1 and R2 can; at night, under the infrared, it is sharp, smaller than theirs (03/09 at 02:00 thumbnail). It is rejected as much before as after the outage from 09/09 to 22/09, when the other reflectors are better seen: it is the target, not the daytime sun. The compensation therefore runs every day on five references, and on three or fewer as soon as two others are lost (PA_8 poorly seen before the outage, passages in front of R1 and R2, sunrise, separate labels); its entries and exits do not make the targets jump. Cause not established: a reflector too weak for daytime (small, dirty or poorly oriented). Ignore the curve of R3 by day; act on the target (clean it, reorient it or replace it) to give a sixth reference back to the daytime compensation.", "review": "2026-11-17"}
-{"id": "WILDSTRUBEL-69", "start": "2026-09-09T21:45Z", "end": "2026-09-22T08:45Z", "family": "No data", "description": "No measurement for any sensor for nearly two weeks; the metrics and the images stop with the measurements. Just before, the battery empties and the voltage falls well below its level of the other nights (metrics): the station shuts down for lack of energy. It restarts on 22/09 in the morning, the battery full and a voltage much higher than usual, as on an external power supply; on return, the tilt of the camera is no longer at the same night level as before the outage. The curves are missing: the station ran out of energy, to be checked (battery, panel, possible intervention).", "review": "2026-11-17"}
-{"id": "WILDSTRUBEL-70", "start": "2026-09-09T21:45Z", "end": "2026-09-22T09:00Z", "family": "Displacement", "description": "During the outage from 09/09 to 22/09, the corrected curves change level and do not resume the one from before: corr_y of PB1_2 markedly lower, corr_y of PB2_2 lower, corr_x of PB_5, PA2_2, PA3_2 and PB4 lower, corr_y of PA_9 higher, from the first measurement. The jump is hidden in the outage; the step lasts until the end of the batch, except for PB_5, back near its level from before on 30/09 (labelled separately), and PB1_2 keeps going down from 25 to 29/09 (labelled separately). The camera is no longer at the same night level (tilt and rotation shifted). Relative to the overall movement of the targets, the raw position of PB1_2 has shifted alone, and the references PA_8 and PA1_2 a little relative to each other, which changes the basis of the other targets. After the restart, the reflectors are seen better, by day and by night, and the error_value of all sensors is lower; the housing temperature has the same cycle before and after. Cause not established: an intervention on the station during the outage (adjustment, cleaning), or, for PB1_2, a movement of the kerb. For the targets that follow the basis, this is not a movement of the structure: do not compare the levels from before and after the outage, to be checked with the operator; for PB1_2, a movement is not excluded: look at the target, keep watching.", "review": "2026-11-17"}
-{"id": "WILDSTRUBEL-130", "start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The reference R3 is rejected every measured day, from the first measurement of the morning (04:30 to 05:45) until 13:30-16:30, and almost never at night: most of the measurements from 05:00 to 15:00, often all of them, from 01/10 to 09/10, and at the only daytime measurement of 15/10 (08:00); almost none at night. Its median error_value is markedly above the threshold by day, and a little below it at night. It is as much so on the days when the housing heats up least (on 08/10, almost all its daytime measurements): it is not the daytime sun, it is the target. On its daytime thumbnails, its spot cannot be seen (30/09 at 10:00), while those of R1 and R2 can. The compensation therefore runs every day on five references, and on three or fewer when two others are lost (passages, PA_8 and PA1_2 poorly seen in the sun, separate labels); its entries and exits do not make the targets jump (median jump of the corr no more than a little above the noise, like the other steps of the day, apart from the moments already labelled). No daytime measurement after 15/10: no return seen, until the end of the batch. Cause not established: a reflector too weak for daytime (small, dirty or poorly oriented). Ignore the curve of R3 by day; act on the target (clean it, reorient it or replace it).", "review": "2026-11-17"}
-{"id": "WILDSTRUBEL-199", "start": "2026-10-15T08:00Z", "end": "2026-10-31T20:15Z", "family": "No data", "description": "No measurement for any sensor for more than two weeks; the metrics and the images are also missing almost all that time (two isolated values on 25/10), and come back only on 30/10 in the evening, the battery well charged but not full; it is full only on 31/10 in the morning, with daytime images on 31/10, still without a displacement measurement until that evening. Cause not established (station stopped). The curves are missing: to be checked with the operator."}
+{"id": "WILDSTRUBEL-46", "start": "2026-09-07T00:00Z", "end": "2026-10-01T00:00Z", "family": "Target issue", "description": "The reference R3 is rejected on every measured day of the batch (from 07 to 09/09, then from 22 to 30/09), from sunrise until mid-afternoon, and almost never at night: by day, its error_value stays above its threshold at almost every measurement, a little less often in the last days of September; at night, it is well below. On its daytime thumbnail (30/09 at 10:00), its spot cannot be seen, while those of R1 and R2 can; at night, under the infrared, it is sharp, smaller than theirs (03/09 at 02:00 thumbnail). It is rejected as much before as after the outage from 09/09 to 22/09, when the other reflectors are better seen: it is the target, not the daytime sun. The compensation therefore runs every day on five references, and on three or fewer as soon as two others are lost (PA_8 poorly seen before the outage, passages in front of R1 and R2, sunrise, separate labels); its entries and exits do not make the targets jump. Cause not established: a reflector too weak for daytime (small, dirty or poorly oriented). Ignore the curve of R3 by day; act on the target (clean it, reorient it or replace it) to give a sixth reference back to the daytime compensation.", "review": "2026-11-17", "analysis": "WILDSTRUBEL_2026-09-07T0000_2026-11-01T0000"}
+{"id": "WILDSTRUBEL-69", "start": "2026-09-09T21:45Z", "end": "2026-09-22T08:45Z", "family": "No data", "description": "No measurement for any sensor for nearly two weeks; the metrics and the images stop with the measurements. Just before, the battery empties and the voltage falls well below its level of the other nights (metrics): the station shuts down for lack of energy. It restarts on 22/09 in the morning, the battery full and a voltage much higher than usual, as on an external power supply; on return, the tilt of the camera is no longer at the same night level as before the outage. The curves are missing: the station ran out of energy, to be checked (battery, panel, possible intervention).", "review": "2026-11-17", "analysis": "WILDSTRUBEL_2026-09-07T0000_2026-11-01T0000"}
+{"id": "WILDSTRUBEL-70", "start": "2026-09-09T21:45Z", "end": "2026-09-22T09:00Z", "family": "Displacement", "description": "During the outage from 09/09 to 22/09, the corrected curves change level and do not resume the one from before: corr_y of PB1_2 markedly lower, corr_y of PB2_2 lower, corr_x of PB_5, PA2_2, PA3_2 and PB4 lower, corr_y of PA_9 higher, from the first measurement. The jump is hidden in the outage; the step lasts until the end of the batch, except for PB_5, back near its level from before on 30/09 (labelled separately), and PB1_2 keeps going down from 25 to 29/09 (labelled separately). The camera is no longer at the same night level (tilt and rotation shifted). Relative to the overall movement of the targets, the raw position of PB1_2 has shifted alone, and the references PA_8 and PA1_2 a little relative to each other, which changes the basis of the other targets. After the restart, the reflectors are seen better, by day and by night, and the error_value of all sensors is lower; the housing temperature has the same cycle before and after. Cause not established: an intervention on the station during the outage (adjustment, cleaning), or, for PB1_2, a movement of the kerb. For the targets that follow the basis, this is not a movement of the structure: do not compare the levels from before and after the outage, to be checked with the operator; for PB1_2, a movement is not excluded: look at the target, keep watching.", "review": "2026-11-17", "analysis": "WILDSTRUBEL_2026-09-07T0000_2026-11-01T0000"}
+{"id": "WILDSTRUBEL-130", "start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The reference R3 is rejected every measured day, from the first measurement of the morning (04:30 to 05:45) until 13:30-16:30, and almost never at night: most of the measurements from 05:00 to 15:00, often all of them, from 01/10 to 09/10, and at the only daytime measurement of 15/10 (08:00); almost none at night. Its median error_value is markedly above the threshold by day, and a little below it at night. It is as much so on the days when the housing heats up least (on 08/10, almost all its daytime measurements): it is not the daytime sun, it is the target. On its daytime thumbnails, its spot cannot be seen (30/09 at 10:00), while those of R1 and R2 can. The compensation therefore runs every day on five references, and on three or fewer when two others are lost (passages, PA_8 and PA1_2 poorly seen in the sun, separate labels); its entries and exits do not make the targets jump (median jump of the corr no more than a little above the noise, like the other steps of the day, apart from the moments already labelled). No daytime measurement after 15/10: no return seen, until the end of the batch. Cause not established: a reflector too weak for daytime (small, dirty or poorly oriented). Ignore the curve of R3 by day; act on the target (clean it, reorient it or replace it).", "review": "2026-11-17", "analysis": "WILDSTRUBEL_2026-09-07T0000_2026-11-01T0000"}
+{"id": "WILDSTRUBEL-199", "start": "2026-10-15T08:00Z", "end": "2026-10-31T20:15Z", "family": "No data", "description": "No measurement for any sensor for more than two weeks; the metrics and the images are also missing almost all that time (two isolated values on 25/10), and come back only on 30/10 in the evening, the battery well charged but not full; it is full only on 31/10 in the morning, with daytime images on 31/10, still without a displacement measurement until that evening. Cause not established (station stopped). The curves are missing: to be checked with the operator.", "analysis": "WILDSTRUBEL_2026-09-07T0000_2026-11-01T0000"}
{"id": "WILDSTRUBEL-200", "start": "2026-10-31T20:00Z", "end": "2026-10-31T20:30Z", "family": "Displacement", "description": "A single measurement after three weeks without measurement: the camera has nodded down a lot since 09/10 (its tilt well above that of early October, already slowly rising from 03/10 to 09/10), all the raw positions have risen in the image. The compensation runs on five references (R2 rejected), but almost all targets have their corrected curves shifted upward on corr_y, PB1_2 and PB2_2 the most, PA_9 on corr_x, and the reprojection errors of the references are higher than usual. No image at that hour. Cause not established: the camera has tilted, and the compensation does not quite catch up with it; a single point does not say whether it is lasting. To be checked: look at the mount of the camera, keep watching the next measurements.", "review": "2026-11-17", "analysis": "WILDSTRUBEL_2026-10-20T0000_2026-11-01T0000"}
{"id": "WILDSTRUBEL-201", "start": "2026-10-31T20:15Z", "end": "2026-11-01T00:00Z", "family": "No data", "description": "No measurement for any sensor until the end of the batch; the metrics stop at the same moment, although the battery was full and the voltage normal. This is not an end-of-file delay: nothing arrives on the following days either, when the other stations have their data. Cause not established (station stopped again). The curves are missing: to be checked with the operator.", "review": "2026-11-17", "analysis": "WILDSTRUBEL_2026-10-20T0000_2026-11-01T0000"}
{"id": "WILDSTRUBEL-176", "start": "2026-10-06T19:45Z", "end": "2026-10-07T07:00Z", "family": "No data", "description": "No measurement for any sensor during the night, except three isolated measurements at 05:00, 06:00 and 06:30, where several targets are rejected. The station shuts down for lack of energy: just before the outage, the battery is at its lowest and the voltage below its usual night level, and the metrics stop with the measurements; it restarts at sunrise with the solar charge, the compute board still cold (metrics). The curves are missing; nothing moves on the structure, but the station does not have enough energy to last the night: to be checked (battery, panel).", "review": "2026-11-17", "analysis": "WILDSTRUBEL_2026-10-06T1945_2026-10-20T0000"}
diff --git a/auto/analyses/long-labels/BREITHORN/analysis.md b/auto/analyses/BREITHORN_2026-10-03T0000_2026-11-01T0000/analysis.md
similarity index 100%
rename from auto/analyses/long-labels/BREITHORN/analysis.md
rename to auto/analyses/BREITHORN_2026-10-03T0000_2026-11-01T0000/analysis.md
diff --git a/auto/analyses/BREITHORN_2026-10-03T0000_2026-11-01T0000/labels.jsonl b/auto/analyses/BREITHORN_2026-10-03T0000_2026-11-01T0000/labels.jsonl
new file mode 100644
index 0000000..7fd622d
--- /dev/null
+++ b/auto/analyses/BREITHORN_2026-10-03T0000_2026-11-01T0000/labels.jsonl
@@ -0,0 +1,2 @@
+{"start": "2026-10-03T00:00Z", "end": "2026-10-13T04:00Z", "family": "Displacement", "description": "From the start of the data to 13 October, six targets drift slowly and steadily, all in the same direction, mostly in corr_x, in corr_y too except POUI19: COLH20, COLI20, COLI21, COLJ19, POUI19 and POUI20; COLI24 drifts in the opposite direction in corr_y. Their drift follows the camera pose step by step, as the camera gradually tilts (tilt increasing, pan and rotation decreasing), while their position in the image hardly moves and their error_value stays stable; the other targets, such as POUH21, do not drift. Cause given by the expert: the camera is gradually nodding forward and the compensation of its movement is not complete, correcting some targets better than others. According to the expert, COLJ19 and POUI19, which drift the most, are much closer to the camera than the other targets; for the other drifting targets, the reason for their poorer compensation (position, angle) is not established. The temperature of the camera housing drops slightly over the range, link not established. According to the expert, BREITHORN, MICHIGAN and NEBRASKA are in the same building: the cameras of the three stations tilt together, in the same direction and on the same dates (advance until 12 October, stop and slight backward movement from 13 to 16, resumption from the 17th to the end of the month), which points to a cause common to the building rather than a fault of this camera alone; at equal housing temperature, the cameras are more tilted at the end of the month than in the middle: temperature does not explain it alone, link not established. For the customer: the targets do not move relative to each other, this is not a movement of the structure; the camera tilt is to be monitored.", "review": "2026-11-17"}
+{"start": "2026-10-16T20:00Z", "end": "2026-11-01T00:00Z", "family": "Displacement", "description": "From 17 October to the end of the batch, the drift resumes, faster than at the beginning of the month until the 25th, then clearly slower without stopping: the camera tilts again (tilt increasing, pan and rotation decreasing), and COLH20, COLI20, COLI21, COLJ19, POUI19 and POUI20 drift with it, mostly in corr_x and also in corr_y, POUI19 the most; COLI24 drifts in the opposite direction in corr_y. COLI22, COLH20''', POUI22 and POUI24 drift too, more noisily, between their own rejections. Their position in the image hardly moves, their error_value stays stable, POUH21 does not drift. Cause given by the expert: the camera is nodding forward and the compensation of its movement is not complete, correcting some targets better than others. According to the expert, COLJ19 and POUI19, which drift the most, are much closer to the camera than the other targets; for the other drifting targets, the reason for their poorer compensation (position, angle) is not established. The resumption coincides with the drop in the camera housing temperature, but the drift does not come back when it rises: link not established. According to the expert, BREITHORN, MICHIGAN and NEBRASKA are in the same building: the cameras of the three stations tilt together, in the same direction and on the same dates (advance until 12 October, stop and slight backward movement from 13 to 16, resumption from the 17th to the end of the month), which points to a cause common to the building rather than a fault of this camera alone; at equal housing temperature, the cameras are more tilted at the end of the month than in the middle: temperature does not explain it alone, link not established. For the customer: the targets do not move relative to each other, this is not a movement of the structure; the camera tilt is to be monitored."}
diff --git a/auto/analyses/long-labels/BREITHORN/report.md b/auto/analyses/BREITHORN_2026-10-03T0000_2026-11-01T0000/report.md
similarity index 100%
rename from auto/analyses/long-labels/BREITHORN/report.md
rename to auto/analyses/BREITHORN_2026-10-03T0000_2026-11-01T0000/report.md
diff --git a/auto/analyses/BREITHORN_2026-10-03T0000_2026-11-01T0000/request.json b/auto/analyses/BREITHORN_2026-10-03T0000_2026-11-01T0000/request.json
new file mode 100644
index 0000000..af0cf5c
--- /dev/null
+++ b/auto/analyses/BREITHORN_2026-10-03T0000_2026-11-01T0000/request.json
@@ -0,0 +1,6 @@
+{
+ "station": "BREITHORN",
+ "start": "2026-10-03T00:00Z",
+ "end": "2026-11-01T00:00Z",
+ "hints": "Requalify the long labels of the station (work/existing.jsonl: those that no period analysis owns) under the new rules: keep, correct, remove."
+}
\ No newline at end of file
diff --git a/auto/analyses/long-labels/CLARIDEN/analysis.md b/auto/analyses/CLARIDEN_2026-10-01T0000_2026-11-01T0000/analysis.md
similarity index 100%
rename from auto/analyses/long-labels/CLARIDEN/analysis.md
rename to auto/analyses/CLARIDEN_2026-10-01T0000_2026-11-01T0000/analysis.md
diff --git a/auto/analyses/CLARIDEN_2026-10-01T0000_2026-11-01T0000/labels.jsonl b/auto/analyses/CLARIDEN_2026-10-01T0000_2026-11-01T0000/labels.jsonl
new file mode 100644
index 0000000..c9dea6b
--- /dev/null
+++ b/auto/analyses/CLARIDEN_2026-10-01T0000_2026-11-01T0000/labels.jsonl
@@ -0,0 +1,2 @@
+{"start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The target P-300-B is rejected at every measurement of the batch: its recognition error stays almost at 1, its corrected curve is missing over the whole month. This has lasted since 29 September in the late afternoon, the time when the recognition error of other targets, including its neighbor P-301-B, also changes level all at once: a station setting changed that day. On the thumbnails (the 1st, the 15th and the 31st), the prism spot is sharp and bright, but next to the position where the system looks for it: the target seems badly configured or badly positioned, not hidden. Curve to ignore; correct the position of the target in the configuration or check the prism.", "review": "2026-11-17"}
+{"start": "2026-10-06T22:00Z", "end": "2026-10-11T06:00Z", "family": "Displacement", "description": "Slow drift of several targets over four days, made of small steps, then stabilization: D-303-B rises vertically, D-303-C and D-304-C rise vertically, D-301-C rises horizontally, D-306-B goes down horizontally. The camera moves: its tilt drifts slowly over the same days, with a small step on the 8th, and these targets follow it closely in the directions of their curves; the compensation does not absorb this tilt equally on every target. Ordinary recognition error, nothing on the images. The camera housing temperature stays almost constant over these days: no link with it. Slow return from the 11th to the 19th, labeled separately. Deduced from the curves and the camera pose: mostly a remainder of the camera tilt, not established as a movement of the structure; the camera is to be monitored, and these targets checked against the other measurements of the site."}
diff --git a/auto/analyses/long-labels/CLARIDEN/report.md b/auto/analyses/CLARIDEN_2026-10-01T0000_2026-11-01T0000/report.md
similarity index 100%
rename from auto/analyses/long-labels/CLARIDEN/report.md
rename to auto/analyses/CLARIDEN_2026-10-01T0000_2026-11-01T0000/report.md
diff --git a/auto/analyses/CLARIDEN_2026-10-01T0000_2026-11-01T0000/request.json b/auto/analyses/CLARIDEN_2026-10-01T0000_2026-11-01T0000/request.json
new file mode 100644
index 0000000..da46d84
--- /dev/null
+++ b/auto/analyses/CLARIDEN_2026-10-01T0000_2026-11-01T0000/request.json
@@ -0,0 +1,6 @@
+{
+ "station": "CLARIDEN",
+ "start": "2026-10-01T00:00Z",
+ "end": "2026-11-01T00:00Z",
+ "hints": "Requalify the long labels of the station (work/existing.jsonl: those that no period analysis owns) under the new rules: keep, correct, remove."
+}
\ No newline at end of file
diff --git a/auto/analyses/long-labels/FLORIDA/analysis.md b/auto/analyses/FLORIDA_2026-10-01T0000_2026-11-01T0000/analysis.md
similarity index 100%
rename from auto/analyses/long-labels/FLORIDA/analysis.md
rename to auto/analyses/FLORIDA_2026-10-01T0000_2026-11-01T0000/analysis.md
diff --git a/auto/analyses/FLORIDA_2026-10-01T0000_2026-11-01T0000/labels.jsonl b/auto/analyses/FLORIDA_2026-10-01T0000_2026-11-01T0000/labels.jsonl
new file mode 100644
index 0000000..cb31f8e
--- /dev/null
+++ b/auto/analyses/FLORIDA_2026-10-01T0000_2026-11-01T0000/labels.jsonl
@@ -0,0 +1,2 @@
+{"start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "Sellette 6 is a constantly problematic target: its error_value stays just above the threshold, a large part of its measurements are rejected all month, day and night, whatever the weather: its curve has gaps every day and its kept measurements jump. Seen on the thumbnails: a very small spot, almost invisible by day, very close to the halo of Sellette 5, which is much brighter; on the morning of the 20th, the measurement of Sellette 5 even latched onto the spot of Sellette 6. Ignore its curve; check the orientation or cleanliness of the prism.", "review": "2026-11-17"}
+{"start": "2026-10-06T10:15Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "Massif 2 becomes a problematic target: by day, its spot is only a point (noon thumbnails of the 3rd and the 6th), and from the 6th its error_value goes above the threshold at times, measurements rejected by day; from the rain episode of the 8th, its spot also weakens at night and does not come back, the majority of its measurements are rejected day and night until the 29th, and its kept measurements change level (corr_y clearly going downward, corr_x going down at the end of the month). On the 30th and 31st, it is kept again, but just under the threshold and with a corr_y much lower than at the start of the month. Seen on the thumbnails: wide and bright spot at night in early October, small and weak afterwards, invisible by day on the 12th, 30th and 31st. Cause not established (prism tarnished, dirty or veiled). Ignore its curve; check the prism.", "review": "2026-11-17"}
diff --git a/auto/analyses/long-labels/FLORIDA/report.md b/auto/analyses/FLORIDA_2026-10-01T0000_2026-11-01T0000/report.md
similarity index 100%
rename from auto/analyses/long-labels/FLORIDA/report.md
rename to auto/analyses/FLORIDA_2026-10-01T0000_2026-11-01T0000/report.md
diff --git a/auto/analyses/FLORIDA_2026-10-01T0000_2026-11-01T0000/request.json b/auto/analyses/FLORIDA_2026-10-01T0000_2026-11-01T0000/request.json
new file mode 100644
index 0000000..addd760
--- /dev/null
+++ b/auto/analyses/FLORIDA_2026-10-01T0000_2026-11-01T0000/request.json
@@ -0,0 +1,6 @@
+{
+ "station": "FLORIDA",
+ "start": "2026-10-01T00:00Z",
+ "end": "2026-11-01T00:00Z",
+ "hints": "Requalify the long labels of the station (work/existing.jsonl: those that no period analysis owns) under the new rules: keep, correct, remove."
+}
\ No newline at end of file
diff --git a/auto/analyses/long-labels/JUNGFRAU/analysis.md b/auto/analyses/JUNGFRAU_2026-09-30T0000_2026-11-01T0000/analysis.md
similarity index 100%
rename from auto/analyses/long-labels/JUNGFRAU/analysis.md
rename to auto/analyses/JUNGFRAU_2026-09-30T0000_2026-11-01T0000/analysis.md
diff --git a/auto/analyses/JUNGFRAU_2026-09-30T0000_2026-11-01T0000/labels.jsonl b/auto/analyses/JUNGFRAU_2026-09-30T0000_2026-11-01T0000/labels.jsonl
new file mode 100644
index 0000000..49a2e31
--- /dev/null
+++ b/auto/analyses/JUNGFRAU_2026-09-30T0000_2026-11-01T0000/labels.jsonl
@@ -0,0 +1 @@
+{"start": "2026-09-30T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "PM_G is rejected at every measurement of the month, as almost always over the period of the data: its corrected curve is entirely missing, whatever the weather. Its error_value stays at the level of its neighbors PM_C and PM_D and follows the same variations; it is its threshold, lower than that of all the other targets, that it permanently exceeds. Images: its spot is sharp and round, like those of PM_C and PM_D, day and night. Cause not established: a badly set threshold rather than a damaged target, according to the images. Check the configuration of PM_G; ignore its curve.", "review": "2026-11-17"}
diff --git a/auto/analyses/long-labels/JUNGFRAU/report.md b/auto/analyses/JUNGFRAU_2026-09-30T0000_2026-11-01T0000/report.md
similarity index 100%
rename from auto/analyses/long-labels/JUNGFRAU/report.md
rename to auto/analyses/JUNGFRAU_2026-09-30T0000_2026-11-01T0000/report.md
diff --git a/auto/analyses/JUNGFRAU_2026-09-30T0000_2026-11-01T0000/request.json b/auto/analyses/JUNGFRAU_2026-09-30T0000_2026-11-01T0000/request.json
new file mode 100644
index 0000000..cf7985f
--- /dev/null
+++ b/auto/analyses/JUNGFRAU_2026-09-30T0000_2026-11-01T0000/request.json
@@ -0,0 +1,6 @@
+{
+ "station": "JUNGFRAU",
+ "start": "2026-09-30T00:00Z",
+ "end": "2026-11-01T00:00Z",
+ "hints": "Requalify the long labels of the station (work/existing.jsonl: those that no period analysis owns) under the new rules: keep, correct, remove."
+}
\ No newline at end of file
diff --git a/auto/analyses/long-labels/MICHIGAN/analysis.md b/auto/analyses/MICHIGAN_2026-10-09T0800_2026-11-01T0000/analysis.md
similarity index 100%
rename from auto/analyses/long-labels/MICHIGAN/analysis.md
rename to auto/analyses/MICHIGAN_2026-10-09T0800_2026-11-01T0000/analysis.md
diff --git a/auto/analyses/MICHIGAN_2026-10-09T0800_2026-11-01T0000/labels.jsonl b/auto/analyses/MICHIGAN_2026-10-09T0800_2026-11-01T0000/labels.jsonl
new file mode 100644
index 0000000..66cf3bc
--- /dev/null
+++ b/auto/analyses/MICHIGAN_2026-10-09T0800_2026-11-01T0000/labels.jsonl
@@ -0,0 +1 @@
+{"start": "2026-10-09T08:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The reference REFPOU22 is lost on 9 October between the 08:00 measurement and the 12:00 one, and does not come back until the end of the month: its error_value rises almost to the maximum, it is rejected at every measurement and its raw positions wander far from its place. On the thumbnails, its spot, sharp at 04:00 and 08:00 on 9 October, has disappeared at 12:00 and does not come back (also seen on 12 October, 20 October and 31 October), while the neighboring spots and REF42, REFG43N are intact; no obstacle is visible. At 12:00 on 9 October, corr_x and corr_y of all the targets jump together and stay shifted, without a step in the raw positions: the compensation now only runs on REF42 and REFG43N, its reprojection error drops to zero and the basis changes. With these two references only, close to each other and far from the targets, the compensation is fragile: the curves of all the targets are more agitated than before, and the slightest deviation of these two references relative to the targets passes, amplified, into all the targets. At the same measurement, NEBRASKA, in the same building as MICHIGAN according to the expert, also loses one of its references (REFCOLH22), whose spot disappears in the same way with no visible obstacle: a cause common to both, in the building, is to be looked for; it is not established. The reference of the same name seen by BREITHORN stays sharp on its images. Cause of the loss not established (prism masked, turned or removed). For the customer: the jump is not a movement, and the corrected curves since 9 October are not very reliable; check the prism of REFPOU22 on site and restore it.", "review": "2026-11-17"}
diff --git a/auto/analyses/long-labels/MICHIGAN/report.md b/auto/analyses/MICHIGAN_2026-10-09T0800_2026-11-01T0000/report.md
similarity index 100%
rename from auto/analyses/long-labels/MICHIGAN/report.md
rename to auto/analyses/MICHIGAN_2026-10-09T0800_2026-11-01T0000/report.md
diff --git a/auto/analyses/MICHIGAN_2026-10-09T0800_2026-11-01T0000/request.json b/auto/analyses/MICHIGAN_2026-10-09T0800_2026-11-01T0000/request.json
new file mode 100644
index 0000000..a27b09a
--- /dev/null
+++ b/auto/analyses/MICHIGAN_2026-10-09T0800_2026-11-01T0000/request.json
@@ -0,0 +1,6 @@
+{
+ "station": "MICHIGAN",
+ "start": "2026-10-09T08:00Z",
+ "end": "2026-11-01T00:00Z",
+ "hints": "Requalify the long labels of the station (work/existing.jsonl: those that no period analysis owns) under the new rules: keep, correct, remove."
+}
\ No newline at end of file
diff --git a/auto/analyses/long-labels/NEBRASKA/analysis.md b/auto/analyses/NEBRASKA_2026-10-09T0800_2026-11-01T0000/analysis.md
similarity index 100%
rename from auto/analyses/long-labels/NEBRASKA/analysis.md
rename to auto/analyses/NEBRASKA_2026-10-09T0800_2026-11-01T0000/analysis.md
diff --git a/auto/analyses/NEBRASKA_2026-10-09T0800_2026-11-01T0000/labels.jsonl b/auto/analyses/NEBRASKA_2026-10-09T0800_2026-11-01T0000/labels.jsonl
new file mode 100644
index 0000000..2ad75ea
--- /dev/null
+++ b/auto/analyses/NEBRASKA_2026-10-09T0800_2026-11-01T0000/labels.jsonl
@@ -0,0 +1,2 @@
+{"start": "2026-10-09T08:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The reference REFCOLH22 is lost at the 9 October noon measurement and does not come back until the end of the month: its error_value jumps almost to the maximum and all its measurements are rejected. On the thumbnails, its spot, sharp and round until the morning of 9 October, has disappeared from its place at the next measurement, while the neighboring spot and the other references are intact; what made it disappear (prism fallen, removed, hidden) is not visible on the whole image. At the same measurement, MICHIGAN, in the same building as NEBRASKA according to the expert, also loses one of its references (REFPOU22), whose spot disappears in the same way with no visible obstacle: a cause common to both, in the building, is to be looked for; it is not established. At the loss, all the targets jump together in one step: corr_x upward, most on COLJ20, POUJ19, POUJ20 and POUH19, and corr_y upward on COLH19, COLH20, COLJ23 and COLJ24; the jump does not return, it is not a movement. The compensation then runs on the two only references REFH22 and REFP''21 (the corrections of these two references cancel): a more fragile basis, which no longer compensates the camera movement well and makes all the targets move at the slightest deviation of a reference. Very bad sign for the measurement: check the prism of REFCOLH22 on site and restore it.", "review": "2026-11-17"}
+{"start": "2026-10-16T20:00Z", "end": "2026-11-01T00:00Z", "family": "Displacement", "description": "Long upward drift of the corr_x of all the targets, strongest on the targets at the top and the right of the image (COLJ20, POUJ20, POUJ19, COLJ19, then COLH19, POUH19, COLH20) and weak in the image on those close to the references (COLH21, COLJ23, COLJ24), although COLJ24, far from the camera, drifts as much as the others in mm; the corr_y of COLH19, POUH19, POUJ20, COLJ19 and COLH20 goes down, that of POUH20 and COLH21 rises; no return at the end of the month. The camera keeps nodding forward as in the first half of the month (tilt rising, pan and rotation turning, scale dropping), and the compensation on two references only renders it poorly, so that the targets drift with it. The camera housing temperature drops from 16 October and the drift follows its jolts: fast rise until 19 October, slower until 24 October, stop and slight backward movement when the temperature rises again from 25 to 28 October, new rise with the cold of 28 and 29 October, slight backward movement when it rises again on 31 October. But the camera was already nodding forward from 3 to 12 October when the temperature was hardly dropping, and it stays more tilted at the end of the month than in the middle at equal temperature: temperature does not explain it alone, link not established. According to the expert, BREITHORN, MICHIGAN and NEBRASKA are in the same building: the cameras of the three stations tilt together, in the same direction and on the same dates (advance until 12 October, stop and slight backward movement from 13 to 16, resumption from the 17th to the end of the month), which points to a cause common to the building rather than a fault of this camera alone. Checked target by target (the raw positions against the overall movement of the targets, and a camera transformation fitted on the other targets): the scene does not move quite as a block, it deforms while the camera tilts. POUH20 moves away the most from the other targets, its neighbor POUH21 hardly at all; then COLH21, and the targets at the edges of the image (COLJ19, COLJ20, COLH19); hence the rise of the corr_y of POUH20 and COLH21. These deviations follow the camera tilt in both directions: POUH20 rises with it on 11 and 12 October, goes back down when it straightens from 13 to 16 October, rises fast with it from 17 to 19 October, then slowly until the end of the month; COLH21 only moves away from 18 October, when the camera exceeds its tilt of the 12th. It is the same movement as that of the camera, not a separate event; at equal tilt, POUH20 stays slightly higher after 17 October than before. Cause not established (the camera moving slightly as it tilts, targets at different distances, or a movement of the structure with the building). Deduced from the curves, the raw positions, the pose and the temperatures; images with nothing clear. For the customer: the camera tilts and the scene deforms with it: a movement of the structure is not established; to be monitored, the camera tilt and the curves of POUH20 and COLH21, which move away the most; restoring a third reference will make the curves reliable again."}
diff --git a/auto/analyses/long-labels/NEBRASKA/report.md b/auto/analyses/NEBRASKA_2026-10-09T0800_2026-11-01T0000/report.md
similarity index 100%
rename from auto/analyses/long-labels/NEBRASKA/report.md
rename to auto/analyses/NEBRASKA_2026-10-09T0800_2026-11-01T0000/report.md
diff --git a/auto/analyses/NEBRASKA_2026-10-09T0800_2026-11-01T0000/request.json b/auto/analyses/NEBRASKA_2026-10-09T0800_2026-11-01T0000/request.json
new file mode 100644
index 0000000..5fabce3
--- /dev/null
+++ b/auto/analyses/NEBRASKA_2026-10-09T0800_2026-11-01T0000/request.json
@@ -0,0 +1,6 @@
+{
+ "station": "NEBRASKA",
+ "start": "2026-10-09T08:00Z",
+ "end": "2026-11-01T00:00Z",
+ "hints": "Requalify the long labels of the station (work/existing.jsonl: those that no period analysis owns) under the new rules: keep, correct, remove."
+}
\ No newline at end of file
diff --git a/auto/analyses/long-labels/NIEDERHORN/analysis.md b/auto/analyses/NIEDERHORN_2026-10-01T0000_2026-11-01T0000/analysis.md
similarity index 100%
rename from auto/analyses/long-labels/NIEDERHORN/analysis.md
rename to auto/analyses/NIEDERHORN_2026-10-01T0000_2026-11-01T0000/analysis.md
diff --git a/auto/analyses/NIEDERHORN_2026-10-01T0000_2026-11-01T0000/labels.jsonl b/auto/analyses/NIEDERHORN_2026-10-01T0000_2026-11-01T0000/labels.jsonl
new file mode 100644
index 0000000..0c49a8a
--- /dev/null
+++ b/auto/analyses/NIEDERHORN_2026-10-01T0000_2026-11-01T0000/labels.jsonl
@@ -0,0 +1,7 @@
+{"start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The target e03 is rejected at almost every measurement of the batch: its corrected curve does not exist (a few isolated points at most). Seen on the thumbnails: no spot is visible at its position on the thumbnails, day and night. It is not the weather: it is permanent, day and night. Act on the target or its configuration; ignore its curve.", "review": "2026-11-17"}
+{"start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The target e04 is rejected at almost every measurement of the batch: its corrected curve does not exist (a few isolated points at most). Seen on the thumbnails: no sharp spot is visible at its position on the thumbnails, only a small glow by day. It is not the weather: it is permanent, day and night. Act on the target or its configuration; ignore its curve.", "review": "2026-11-17"}
+{"start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The target e05 is rejected at almost every measurement of the batch: its corrected curve does not exist (a few isolated points at most). Seen on the thumbnails: no spot is visible at its position on the thumbnails, day and night. It is not the weather: it is permanent, day and night. Act on the target or its configuration; ignore its curve.", "review": "2026-11-17"}
+{"start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The target e07 is rejected at almost every measurement of the batch: its corrected curve does not exist (a few isolated points at most). Seen on the thumbnails: its spot is visible but between two very close neighbors; its recognition error stays above the threshold. It is not the weather: it is permanent, day and night. Act on the target or its configuration; ignore its curve.", "review": "2026-11-17"}
+{"start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The target e08 is rejected at almost every measurement of the batch: its corrected curve does not exist (a few isolated points at most). Seen on the thumbnails: its spot is visible but between two very close neighbors; its recognition error stays above the threshold. It is not the weather: it is permanent, day and night. Act on the target or its configuration; ignore its curve.", "review": "2026-11-17"}
+{"start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The target e11 is rejected at almost every measurement of the batch: its corrected curve does not exist (a few isolated points at most). Seen on the thumbnails: its spot is very large and dazzled at night, stuck to a small neighbor; its error stays above the threshold. It is not the weather: it is permanent, day and night. Act on the target or its configuration; ignore its curve.", "review": "2026-11-17"}
+{"start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The target e12 is rejected at almost every measurement of the batch: its corrected curve does not exist (a few isolated points at most). Seen on the thumbnails: its spot is very large and dazzled at night, stuck to a small neighbor; its error stays above the threshold. It is not the weather: it is permanent, day and night. Act on the target or its configuration; ignore its curve.", "review": "2026-11-17"}
diff --git a/auto/analyses/long-labels/NIEDERHORN/report.md b/auto/analyses/NIEDERHORN_2026-10-01T0000_2026-11-01T0000/report.md
similarity index 100%
rename from auto/analyses/long-labels/NIEDERHORN/report.md
rename to auto/analyses/NIEDERHORN_2026-10-01T0000_2026-11-01T0000/report.md
diff --git a/auto/analyses/NIEDERHORN_2026-10-01T0000_2026-11-01T0000/request.json b/auto/analyses/NIEDERHORN_2026-10-01T0000_2026-11-01T0000/request.json
new file mode 100644
index 0000000..a73e7e2
--- /dev/null
+++ b/auto/analyses/NIEDERHORN_2026-10-01T0000_2026-11-01T0000/request.json
@@ -0,0 +1,6 @@
+{
+ "station": "NIEDERHORN",
+ "start": "2026-10-01T00:00Z",
+ "end": "2026-11-01T00:00Z",
+ "hints": "Requalify the long labels of the station (work/existing.jsonl: those that no period analysis owns) under the new rules: keep, correct, remove."
+}
\ No newline at end of file
diff --git a/auto/analyses/long-labels/NIEDERHORN/scripts/count.py b/auto/analyses/NIEDERHORN_2026-10-01T0000_2026-11-01T0000/scripts/count.py
similarity index 100%
rename from auto/analyses/long-labels/NIEDERHORN/scripts/count.py
rename to auto/analyses/NIEDERHORN_2026-10-01T0000_2026-11-01T0000/scripts/count.py
diff --git a/auto/analyses/long-labels/NIEDERHORN/scripts/daynight.py b/auto/analyses/NIEDERHORN_2026-10-01T0000_2026-11-01T0000/scripts/daynight.py
similarity index 100%
rename from auto/analyses/long-labels/NIEDERHORN/scripts/daynight.py
rename to auto/analyses/NIEDERHORN_2026-10-01T0000_2026-11-01T0000/scripts/daynight.py
diff --git a/auto/analyses/long-labels/NIEDERHORN/scripts/specific.py b/auto/analyses/NIEDERHORN_2026-10-01T0000_2026-11-01T0000/scripts/specific.py
similarity index 100%
rename from auto/analyses/long-labels/NIEDERHORN/scripts/specific.py
rename to auto/analyses/NIEDERHORN_2026-10-01T0000_2026-11-01T0000/scripts/specific.py
diff --git a/auto/analyses/long-labels/NORDEND/analysis.md b/auto/analyses/NORDEND_2026-08-17T0515_2026-11-07T1400/analysis.md
similarity index 100%
rename from auto/analyses/long-labels/NORDEND/analysis.md
rename to auto/analyses/NORDEND_2026-08-17T0515_2026-11-07T1400/analysis.md
diff --git a/auto/analyses/NORDEND_2026-08-17T0515_2026-11-07T1400/labels.jsonl b/auto/analyses/NORDEND_2026-08-17T0515_2026-11-07T1400/labels.jsonl
new file mode 100644
index 0000000..836e7e0
--- /dev/null
+++ b/auto/analyses/NORDEND_2026-08-17T0515_2026-11-07T1400/labels.jsonl
@@ -0,0 +1,4 @@
+{"start": "2026-08-17T05:15Z", "end": "2026-10-01T00:00Z", "family": "Target issue", "description": "PR04: its spot is much weaker than that of its neighbours PR03 and PR05, by day as by night (thumbnails of 14, 22, 26/08, 07, 12 and 23/09), and its error_value, already several times that of its neighbours, rises over the weeks. It is rejected almost every day, by day as by night, a good part of the time from 21 to 25/08 and from 06 to 08/09, almost without interruption from 18 to 28/09; the rejections become rare on 30/09. Between the rejections, its corr_x and corr_y curves are much noisier than those of its neighbours and change level, without the neighbours following. At night, lit cobweb threads pass over its area (23/09 image at 00:00), without explaining the whole range. The disturbance continues in October, weaker (next label, from 01/10). Cause not established (dirt, orientation, cobweb). This is not a movement: ignore its curve; check the target on site.", "review": "2026-11-17"}
+{"start": "2026-10-01T00:00Z", "end": "2026-10-26T20:45Z", "family": "Target issue", "description": "PR04: usual error_value several times higher than that of its neighbours, scattered rejections almost every day, by day as by night, and corrected curves twice as noisy; the target is not hidden on the images. This is the continuation of a stronger disturbance in September, when it was almost always rejected. After the rain of 24 to 25, its error_value falls back to the level of the others during 26, after a last departure in early evening, and the rejections stop: the target (or whatever was soiling it) has probably been cleaned. Afterwards its curves, calm, stay lower than at the beginning of the month, in corr_x and in corr_y, until the end of the batch: the level measured during the disturbance is not a reference. Cause not established beyond that. Do not trust its curve over the range; check the target if it comes back.", "review": "2026-11-17"}
+{"start": "2026-10-08T02:15Z", "end": "2026-11-07T14:00Z", "family": "Obstruction", "description": "PR17: a blurred pale disc (mark on the window lit by the infrared) sharpens just under its spot at 02:30 and covers part of it (thumbnails of 08/10 at 02:00 and 02:45, then of the following nights; still visible, weaker, on 26, 29 and 31/10, and as a pale area under the spot on 04/11). In one step, its corr_y drops and its corr_x rises markedly, only PR17 moves, its neighbours do not, and its error_value doubles and stays high. This step brings the corr_y of PR17 back to roughly its level from before its jump of 05/09 (separate label, Displacement, plateau until that day); but the September jump had only touched its corr_y, without raising its error_value, and no disc was visible then: the step comes from the mark, and that it also undoes the September plateau is not established. Its curves still change level in steps: a partial return at 23:00 on the 12th, in the middle of a back-and-forth of the camera from 22:30 to 00:15 (labelled separately, Displacement) that moves the other targets too; they come back after it, PR17 keeps its new level, so its step is its own and not the camera; then new offsets from 21 to 24. After the rain of 24 to 25, its error_value falls back to its earlier level, but its curves come back neither to their level of the beginning of the month (the September plateau) nor to that from before the jump of 05/09, and stay so until the end of the range, the disc still visible. Cause seen on the images; the exact nature of the mark is not established. This is not a movement of PR17; ignore its curve over the range, clean the window."}
+{"start": "2026-10-16T19:00Z", "end": "2026-11-07T14:00Z", "family": "Target issue", "description": "CTR01 (local reference, read as a target): from the evening of the 16th, its error_value no longer falls back to its level of the beginning of the month and keeps rising until the end of the month, very close to the threshold then above it; the measurement is rejected a large part of the time, by night as by day, every day, almost without stopping from the end of October to the afternoon of 02/11, then still about half of the time until the end of the range; its curve is missing or stays very noisy. Before the 16th, it was only rejected on sunny afternoons and during the nights when the left-edge spots fade out (separate labels). On the images, its spot is weak; at the end of the month, blurred marks left on the window after the rain pass near it (26/10 image at 03:00), then a pale blurred band covers it (31/10 image at 03:00). Cause not established: state of the prism, or of the window in front of it, to be checked. Ignore its curve; intervene on the target."}
diff --git a/auto/analyses/long-labels/NORDEND/report.md b/auto/analyses/NORDEND_2026-08-17T0515_2026-11-07T1400/report.md
similarity index 100%
rename from auto/analyses/long-labels/NORDEND/report.md
rename to auto/analyses/NORDEND_2026-08-17T0515_2026-11-07T1400/report.md
diff --git a/auto/analyses/NORDEND_2026-08-17T0515_2026-11-07T1400/request.json b/auto/analyses/NORDEND_2026-08-17T0515_2026-11-07T1400/request.json
new file mode 100644
index 0000000..398882b
--- /dev/null
+++ b/auto/analyses/NORDEND_2026-08-17T0515_2026-11-07T1400/request.json
@@ -0,0 +1,6 @@
+{
+ "station": "NORDEND",
+ "start": "2026-08-17T05:15Z",
+ "end": "2026-11-07T14:00Z",
+ "hints": "Requalify the long labels of the station (work/existing.jsonl: those that no period analysis owns) under the new rules: keep, correct, remove."
+}
\ No newline at end of file
diff --git a/auto/analyses/long-labels/NORDEND/scripts/rejections.py b/auto/analyses/NORDEND_2026-08-17T0515_2026-11-07T1400/scripts/rejections.py
similarity index 100%
rename from auto/analyses/long-labels/NORDEND/scripts/rejections.py
rename to auto/analyses/NORDEND_2026-08-17T0515_2026-11-07T1400/scripts/rejections.py
diff --git a/auto/analyses/long-labels/NORDEND/scripts/write_labels.py b/auto/analyses/NORDEND_2026-08-17T0515_2026-11-07T1400/scripts/write_labels.py
similarity index 100%
rename from auto/analyses/long-labels/NORDEND/scripts/write_labels.py
rename to auto/analyses/NORDEND_2026-08-17T0515_2026-11-07T1400/scripts/write_labels.py
diff --git a/auto/analyses/NORDEND_2026-10-24T1630_2026-11-07T1400/analysis.md b/auto/analyses/NORDEND_2026-10-24T1630_2026-11-07T1400/analysis.md
index 4e3f4f8..6cfd348 100644
--- a/auto/analyses/NORDEND_2026-10-24T1630_2026-11-07T1400/analysis.md
+++ b/auto/analyses/NORDEND_2026-10-24T1630_2026-11-07T1400/analysis.md
@@ -192,4 +192,4 @@ Values, label by label (largest deviation in noises; a thermal label against the
## After the requalification of the long labels
-NORDEND-283 (CTR01) and NORDEND-284 (PR17), 01/11 → 07/11, removed: NORDEND-195 and NORDEND-169 now run to 07/11 14:00 and carry these episodes (labeling/auto/analyses/long-labels/NORDEND/).
+NORDEND-283 (CTR01) and NORDEND-284 (PR17), 01/11 → 07/11, removed: NORDEND-195 and NORDEND-169 now run to 07/11 14:00 and carry these episodes (labeling/auto/analyses/NORDEND_2026-08-17T0515_2026-11-07T1400/).
diff --git a/auto/analyses/long-labels/SNCF01/analysis.md b/auto/analyses/SNCF01_2026-10-04T0000_2026-11-01T0000/analysis.md
similarity index 95%
rename from auto/analyses/long-labels/SNCF01/analysis.md
rename to auto/analyses/SNCF01_2026-10-04T0000_2026-11-01T0000/analysis.md
index 535acb2..9ab3008 100644
--- a/auto/analyses/long-labels/SNCF01/analysis.md
+++ b/auto/analyses/SNCF01_2026-10-04T0000_2026-11-01T0000/analysis.md
@@ -15,4 +15,4 @@ Window: 2114 measurement instants (15 min). Rejection counts from `tools/scripts
Note: the rule of the catalogue "a target right at the threshold, the whole batch, with many own rejections" (`families.md`, Target issue) would have kept SNCF01-5 and SNCF01-6; the instruction of this requalification (and `labeling-rules.md` section 1: a missing point is not labeled for itself) prevails: only targets rejected almost always keep their Target issue.
## Sources read
-`tools/GUIDE.md`, `tools/DATA.md`, `labeling/families.md`, `labeling/labeling-rules.md`, `labeling/reading-rules.md`, `labeling/stations.md`, `labeling/auto/analyses/long-labels/SNCF01/input.jsonl`, the station data through `inventory.py`, `ranges.py`, `summary.py`.
+`tools/GUIDE.md`, `tools/DATA.md`, `labeling/families.md`, `labeling/labeling-rules.md`, `labeling/reading-rules.md`, `labeling/stations.md`, `work/existing.jsonl`, the station data through `inventory.py`, `ranges.py`, `summary.py`.
diff --git a/auto/analyses/SNCF01_2026-10-04T0000_2026-11-01T0000/labels.jsonl b/auto/analyses/SNCF01_2026-10-04T0000_2026-11-01T0000/labels.jsonl
new file mode 100644
index 0000000..7be5755
--- /dev/null
+++ b/auto/analyses/SNCF01_2026-10-04T0000_2026-11-01T0000/labels.jsonl
@@ -0,0 +1,5 @@
+{"start": "2026-10-04T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "BG.1: all its measurements are rejected, from the start of the data to the end of the batch; its curve is missing entirely. Its recognition error stays above the threshold, by day and by night, whatever the weather; on the night image its spot appears doubled. Target permanently poorly seen (orientation, installation or configuration to be checked): act on the target; no curve to read.", "review": "2026-11-17"}
+{"start": "2026-10-04T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "F4.1: all its measurements are rejected over the batch; its curve is missing entirely. Its recognition error stays above the threshold permanently; on the images its spot is small and faint. Target permanently poorly seen: act on the target; no curve to read.", "review": "2026-11-17"}
+{"start": "2026-10-04T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "CV.7: most of its measurements are rejected over the whole batch, its recognition error oscillating around the threshold; its curve has only scattered points, and the last ones accepted, at the end of the batch, move strongly away from its level without anything else moving. Target permanently poorly seen (by day, its spot touches the edge of a bright structure on the image): act on the target; ignore its curve.", "review": "2026-11-17"}
+{"start": "2026-10-04T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "F4.4: most of its measurements are rejected over the whole batch, its recognition error staying stuck to the threshold; its curve has only scattered, noisy points. Faint, doubled spot on the night image. Target permanently poorly seen: act on the target; ignore its curve.", "review": "2026-11-17"}
+{"start": "2026-10-04T00:00Z", "end": "2026-11-01T00:00Z", "family": "Displacement", "description": "Over the whole batch, as one single episode, the corrected curves of many targets drift slowly, with no return: corr_y rises on BG.2, F4.5, F4.6, P4, CV.8, F4.3, P5, and drops on P1, P7, CV.1; corr_x drops on P2, P3, P4, F4.6; the drift flattens at the end of the month; part of the drop of P7, CV.1 comes from the jump of 15/10 in the morning, labelled separately. At the same time, the camera rotation drops and its tilt rises slowly, the reprojection error of the references increases and, relative to the overall movement of the targets, the positions of the targets relative to one another change more and more over the month (P1, P7, F4.5, BG.2 especially), like those of the references: the whole scene slowly deforms in the image, while the camera tilts. No temperature is available for this station (empty metrics); the cause is not established (seasonal cooling, incomplete compensation of the camera tilt, a reference that moves, or a movement of the wall). The movement of the structure is not established: to be watched.", "review": "2026-11-17"}
diff --git a/auto/analyses/long-labels/SNCF01/report.md b/auto/analyses/SNCF01_2026-10-04T0000_2026-11-01T0000/report.md
similarity index 100%
rename from auto/analyses/long-labels/SNCF01/report.md
rename to auto/analyses/SNCF01_2026-10-04T0000_2026-11-01T0000/report.md
diff --git a/auto/analyses/SNCF01_2026-10-04T0000_2026-11-01T0000/request.json b/auto/analyses/SNCF01_2026-10-04T0000_2026-11-01T0000/request.json
new file mode 100644
index 0000000..1f2e918
--- /dev/null
+++ b/auto/analyses/SNCF01_2026-10-04T0000_2026-11-01T0000/request.json
@@ -0,0 +1,6 @@
+{
+ "station": "SNCF01",
+ "start": "2026-10-04T00:00Z",
+ "end": "2026-11-01T00:00Z",
+ "hints": "Requalify the long labels of the station (work/existing.jsonl: those that no period analysis owns) under the new rules: keep, correct, remove."
+}
\ No newline at end of file
diff --git a/auto/analyses/long-labels/WILDSTRUBEL/analysis.md b/auto/analyses/WILDSTRUBEL_2026-09-07T0000_2026-11-01T0000/analysis.md
similarity index 85%
rename from auto/analyses/long-labels/WILDSTRUBEL/analysis.md
rename to auto/analyses/WILDSTRUBEL_2026-09-07T0000_2026-11-01T0000/analysis.md
index 6f975b6..6d8b227 100644
--- a/auto/analyses/long-labels/WILDSTRUBEL/analysis.md
+++ b/auto/analyses/WILDSTRUBEL_2026-09-07T0000_2026-11-01T0000/analysis.md
@@ -6,4 +6,4 @@
- **WILDSTRUBEL-130** (Target issue, reference R3, 01/10 00:00 → 01/11 00:00): **kept** as is. 325 of 432 measurements rejected (75 %): by day 29–40 of 31–43 per day from 01 to 09/10 (31/31 on 07/10, 29/31 on 09/10), the only daytime measurement of 15/10 rejected; at night 0–2 per night (1 of 38 on 01/10). The other references over the range: PA1_2 90, PA_8 86, R2 40, R1 25, PB3_2 13. Its own rejections every measured day: Target issue kept. No measurement after 15/10 08:00 except one on 31/10 20:15 (night, accepted), as the text says.
- **WILDSTRUBEL-199** (No data, 15/10 08:00 → 31/10 20:15): **corrected** (description), review removed. Bounds hold: last measurement 15/10 08:00, next 31/10 20:15, no measurement in between. Metrics: two isolated hours on 25/10 (01:00, 03:00), then back on 30/10 18:00; BatteryPercent 78 % at 30/10 18:00, 80–84 % all night, 94 % at 31/10 05:00, 100 % from 31/10 06:00 to 15:00 (BusVoltage 13.1–13.2 V then 14.0–14.2 V). Correction applied (found by the period analyst): "the battery full" at the 30/10 return becomes "well charged but not full; full only on 31/10 in the morning"; images on 31/10 04:00–13:00 hourly, first displacement measurement 31/10 20:15 ("until that evening" added).
-Sources read: `tools/GUIDE.md`, `tools/DATA.md`, `labeling/families.md`, `labeling/labeling-rules.md`, `labeling/reading-rules.md`, `labeling/stations.md`, `input.jsonl`, the NORDEND long-labels outputs (format). Commands: `scripts/r3_rates.py` (rejections per reference and per day/night, through `tools/scripts/data.py`), `inventory.py` (missing steps, image gaps), `metrics.py --names BusVoltage,BatteryPercent(,BatteryState) --metrics-only` on 08–23/09 and 24/10–01/11, `days.py` night levels 05–26/09 (`work/days_70.txt`), `ranges.py --k 5 --outside` 01–25/09 with the mm columns (`work/ranges_70.txt`). Labels written by `scripts/write_labels.py`; `validate.py`: 0 errors, 0 overlaps.
+Sources read: `tools/GUIDE.md`, `tools/DATA.md`, `labeling/families.md`, `labeling/labeling-rules.md`, `labeling/reading-rules.md`, `labeling/stations.md`, `work/existing.jsonl`, the outputs of the NORDEND long labels (format). Commands: `scripts/r3_rates.py` (rejections per reference and per day/night, through `tools/scripts/data.py`), `inventory.py` (missing steps, image gaps), `metrics.py --names BusVoltage,BatteryPercent(,BatteryState) --metrics-only` on 08–23/09 and 24/10–01/11, `days.py` night levels 05–26/09 (`work/days_70.txt`), `ranges.py --k 5 --outside` 01–25/09 with the mm columns (`work/ranges_70.txt`). Labels written by `scripts/write_labels.py`; `validate.py`: 0 errors, 0 overlaps.
diff --git a/auto/analyses/WILDSTRUBEL_2026-09-07T0000_2026-11-01T0000/labels.jsonl b/auto/analyses/WILDSTRUBEL_2026-09-07T0000_2026-11-01T0000/labels.jsonl
new file mode 100644
index 0000000..59ec34a
--- /dev/null
+++ b/auto/analyses/WILDSTRUBEL_2026-09-07T0000_2026-11-01T0000/labels.jsonl
@@ -0,0 +1,5 @@
+{"start": "2026-09-07T00:00Z", "end": "2026-10-01T00:00Z", "family": "Target issue", "description": "The reference R3 is rejected on every measured day of the batch (from 07 to 09/09, then from 22 to 30/09), from sunrise until mid-afternoon, and almost never at night: by day, its error_value stays above its threshold at almost every measurement, a little less often in the last days of September; at night, it is well below. On its daytime thumbnail (30/09 at 10:00), its spot cannot be seen, while those of R1 and R2 can; at night, under the infrared, it is sharp, smaller than theirs (03/09 at 02:00 thumbnail). It is rejected as much before as after the outage from 09/09 to 22/09, when the other reflectors are better seen: it is the target, not the daytime sun. The compensation therefore runs every day on five references, and on three or fewer as soon as two others are lost (PA_8 poorly seen before the outage, passages in front of R1 and R2, sunrise, separate labels); its entries and exits do not make the targets jump. Cause not established: a reflector too weak for daytime (small, dirty or poorly oriented). Ignore the curve of R3 by day; act on the target (clean it, reorient it or replace it) to give a sixth reference back to the daytime compensation.", "review": "2026-11-17"}
+{"start": "2026-09-09T21:45Z", "end": "2026-09-22T08:45Z", "family": "No data", "description": "No measurement for any sensor for nearly two weeks; the metrics and the images stop with the measurements. Just before, the battery empties and the voltage falls well below its level of the other nights (metrics): the station shuts down for lack of energy. It restarts on 22/09 in the morning, the battery full and a voltage much higher than usual, as on an external power supply; on return, the tilt of the camera is no longer at the same night level as before the outage. The curves are missing: the station ran out of energy, to be checked (battery, panel, possible intervention).", "review": "2026-11-17"}
+{"start": "2026-09-09T21:45Z", "end": "2026-09-22T09:00Z", "family": "Displacement", "description": "During the outage from 09/09 to 22/09, the corrected curves change level and do not resume the one from before: corr_y of PB1_2 markedly lower, corr_y of PB2_2 lower, corr_x of PB_5, PA2_2, PA3_2 and PB4 lower, corr_y of PA_9 higher, from the first measurement. The jump is hidden in the outage; the step lasts until the end of the batch, except for PB_5, back near its level from before on 30/09 (labelled separately), and PB1_2 keeps going down from 25 to 29/09 (labelled separately). The camera is no longer at the same night level (tilt and rotation shifted). Relative to the overall movement of the targets, the raw position of PB1_2 has shifted alone, and the references PA_8 and PA1_2 a little relative to each other, which changes the basis of the other targets. After the restart, the reflectors are seen better, by day and by night, and the error_value of all sensors is lower; the housing temperature has the same cycle before and after. Cause not established: an intervention on the station during the outage (adjustment, cleaning), or, for PB1_2, a movement of the kerb. For the targets that follow the basis, this is not a movement of the structure: do not compare the levels from before and after the outage, to be checked with the operator; for PB1_2, a movement is not excluded: look at the target, keep watching.", "review": "2026-11-17"}
+{"start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The reference R3 is rejected every measured day, from the first measurement of the morning (04:30 to 05:45) until 13:30-16:30, and almost never at night: most of the measurements from 05:00 to 15:00, often all of them, from 01/10 to 09/10, and at the only daytime measurement of 15/10 (08:00); almost none at night. Its median error_value is markedly above the threshold by day, and a little below it at night. It is as much so on the days when the housing heats up least (on 08/10, almost all its daytime measurements): it is not the daytime sun, it is the target. On its daytime thumbnails, its spot cannot be seen (30/09 at 10:00), while those of R1 and R2 can. The compensation therefore runs every day on five references, and on three or fewer when two others are lost (passages, PA_8 and PA1_2 poorly seen in the sun, separate labels); its entries and exits do not make the targets jump (median jump of the corr no more than a little above the noise, like the other steps of the day, apart from the moments already labelled). No daytime measurement after 15/10: no return seen, until the end of the batch. Cause not established: a reflector too weak for daytime (small, dirty or poorly oriented). Ignore the curve of R3 by day; act on the target (clean it, reorient it or replace it).", "review": "2026-11-17"}
+{"start": "2026-10-15T08:00Z", "end": "2026-10-31T20:15Z", "family": "No data", "description": "No measurement for any sensor for more than two weeks; the metrics and the images are also missing almost all that time (two isolated values on 25/10), and come back only on 30/10 in the evening, the battery well charged but not full; it is full only on 31/10 in the morning, with daytime images on 31/10, still without a displacement measurement until that evening. Cause not established (station stopped). The curves are missing: to be checked with the operator."}
diff --git a/auto/analyses/long-labels/WILDSTRUBEL/report.md b/auto/analyses/WILDSTRUBEL_2026-09-07T0000_2026-11-01T0000/report.md
similarity index 100%
rename from auto/analyses/long-labels/WILDSTRUBEL/report.md
rename to auto/analyses/WILDSTRUBEL_2026-09-07T0000_2026-11-01T0000/report.md
diff --git a/auto/analyses/WILDSTRUBEL_2026-09-07T0000_2026-11-01T0000/request.json b/auto/analyses/WILDSTRUBEL_2026-09-07T0000_2026-11-01T0000/request.json
new file mode 100644
index 0000000..b4b90b1
--- /dev/null
+++ b/auto/analyses/WILDSTRUBEL_2026-09-07T0000_2026-11-01T0000/request.json
@@ -0,0 +1,6 @@
+{
+ "station": "WILDSTRUBEL",
+ "start": "2026-09-07T00:00Z",
+ "end": "2026-11-01T00:00Z",
+ "hints": "Requalify the long labels of the station (work/existing.jsonl: those that no period analysis owns) under the new rules: keep, correct, remove."
+}
\ No newline at end of file
diff --git a/auto/analyses/long-labels/WILDSTRUBEL/scripts/r3_rates.py b/auto/analyses/WILDSTRUBEL_2026-09-07T0000_2026-11-01T0000/scripts/r3_rates.py
similarity index 100%
rename from auto/analyses/long-labels/WILDSTRUBEL/scripts/r3_rates.py
rename to auto/analyses/WILDSTRUBEL_2026-09-07T0000_2026-11-01T0000/scripts/r3_rates.py
diff --git a/auto/analyses/long-labels/WILDSTRUBEL/scripts/write_labels.py b/auto/analyses/WILDSTRUBEL_2026-09-07T0000_2026-11-01T0000/scripts/write_labels.py
similarity index 100%
rename from auto/analyses/long-labels/WILDSTRUBEL/scripts/write_labels.py
rename to auto/analyses/WILDSTRUBEL_2026-09-07T0000_2026-11-01T0000/scripts/write_labels.py
diff --git a/auto/analyses/long-labels/BREITHORN/input.jsonl b/auto/analyses/long-labels/BREITHORN/input.jsonl
deleted file mode 100644
index cc44e42..0000000
--- a/auto/analyses/long-labels/BREITHORN/input.jsonl
+++ /dev/null
@@ -1,2 +0,0 @@
-{"id": "BREITHORN-2", "start": "2026-10-03T00:00Z", "end": "2026-10-13T04:00Z", "family": "Displacement", "description": "From the start of the data to 13 October, six targets drift slowly and steadily, all in the same direction, mostly in corr_x, in corr_y too except POUI19: COLH20, COLI20, COLI21, COLJ19, POUI19 and POUI20; COLI24 drifts in the opposite direction in corr_y. Their drift follows the camera pose step by step, as the camera gradually tilts (tilt increasing, pan and rotation decreasing), while their position in the image hardly moves and their error_value stays stable; the other targets, such as POUH21, do not drift. Cause given by the expert: the camera is gradually nodding forward and the compensation of its movement is not complete, correcting some targets better than others. According to the expert, COLJ19 and POUI19, which drift the most, are much closer to the camera than the other targets; for the other drifting targets, the reason for their poorer compensation (position, angle) is not established. The temperature of the camera housing drops slightly over the range, link not established. According to the expert, BREITHORN, MICHIGAN and NEBRASKA are in the same building: the cameras of the three stations tilt together, in the same direction and on the same dates (advance until 12 October, stop and slight backward movement from 13 to 16, resumption from the 17th to the end of the month), which points to a cause common to the building rather than a fault of this camera alone; at equal housing temperature, the cameras are more tilted at the end of the month than in the middle: temperature does not explain it alone, link not established. For the customer: the targets do not move relative to each other, this is not a movement of the structure; the camera tilt is to be monitored.", "review": "2026-11-17"}
-{"id": "BREITHORN-13", "start": "2026-10-16T20:00Z", "end": "2026-11-01T00:00Z", "family": "Displacement", "description": "From 17 October to the end of the batch, the drift resumes, faster than at the beginning of the month until the 25th, then clearly slower without stopping: the camera tilts again (tilt increasing, pan and rotation decreasing), and COLH20, COLI20, COLI21, COLJ19, POUI19 and POUI20 drift with it, mostly in corr_x and also in corr_y, POUI19 the most; COLI24 drifts in the opposite direction in corr_y. Their position in the image hardly moves, their error_value stays stable, POUH21 does not drift. Cause given by the expert: the camera is nodding forward and the compensation of its movement is not complete, correcting some targets better than others. According to the expert, COLJ19 and POUI19, which drift the most, are much closer to the camera than the other targets; for the other drifting targets, the reason for their poorer compensation (position, angle) is not established. The resumption coincides with the drop in the camera housing temperature, but the drift does not come back when it rises: link not established. According to the expert, BREITHORN, MICHIGAN and NEBRASKA are in the same building: the cameras of the three stations tilt together, in the same direction and on the same dates (advance until 12 October, stop and slight backward movement from 13 to 16, resumption from the 17th to the end of the month), which points to a cause common to the building rather than a fault of this camera alone; at equal housing temperature, the cameras are more tilted at the end of the month than in the middle: temperature does not explain it alone, link not established. For the customer: the targets do not move relative to each other, this is not a movement of the structure; the camera tilt is to be monitored.", "review": "2026-11-17"}
diff --git a/auto/analyses/long-labels/BREITHORN/labels.jsonl b/auto/analyses/long-labels/BREITHORN/labels.jsonl
deleted file mode 100644
index 77d940d..0000000
--- a/auto/analyses/long-labels/BREITHORN/labels.jsonl
+++ /dev/null
@@ -1,2 +0,0 @@
-{"id": "BREITHORN-2", "start": "2026-10-03T00:00Z", "end": "2026-10-13T04:00Z", "family": "Displacement", "description": "From the start of the data to 13 October, six targets drift slowly and steadily, all in the same direction, mostly in corr_x, in corr_y too except POUI19: COLH20, COLI20, COLI21, COLJ19, POUI19 and POUI20; COLI24 drifts in the opposite direction in corr_y. Their drift follows the camera pose step by step, as the camera gradually tilts (tilt increasing, pan and rotation decreasing), while their position in the image hardly moves and their error_value stays stable; the other targets, such as POUH21, do not drift. Cause given by the expert: the camera is gradually nodding forward and the compensation of its movement is not complete, correcting some targets better than others. According to the expert, COLJ19 and POUI19, which drift the most, are much closer to the camera than the other targets; for the other drifting targets, the reason for their poorer compensation (position, angle) is not established. The temperature of the camera housing drops slightly over the range, link not established. According to the expert, BREITHORN, MICHIGAN and NEBRASKA are in the same building: the cameras of the three stations tilt together, in the same direction and on the same dates (advance until 12 October, stop and slight backward movement from 13 to 16, resumption from the 17th to the end of the month), which points to a cause common to the building rather than a fault of this camera alone; at equal housing temperature, the cameras are more tilted at the end of the month than in the middle: temperature does not explain it alone, link not established. For the customer: the targets do not move relative to each other, this is not a movement of the structure; the camera tilt is to be monitored.", "review": "2026-11-17"}
-{"id": "BREITHORN-13", "start": "2026-10-16T20:00Z", "end": "2026-11-01T00:00Z", "family": "Displacement", "description": "From 17 October to the end of the batch, the drift resumes, faster than at the beginning of the month until the 25th, then clearly slower without stopping: the camera tilts again (tilt increasing, pan and rotation decreasing), and COLH20, COLI20, COLI21, COLJ19, POUI19 and POUI20 drift with it, mostly in corr_x and also in corr_y, POUI19 the most; COLI24 drifts in the opposite direction in corr_y. COLI22, COLH20''', POUI22 and POUI24 drift too, more noisily, between their own rejections. Their position in the image hardly moves, their error_value stays stable, POUH21 does not drift. Cause given by the expert: the camera is nodding forward and the compensation of its movement is not complete, correcting some targets better than others. According to the expert, COLJ19 and POUI19, which drift the most, are much closer to the camera than the other targets; for the other drifting targets, the reason for their poorer compensation (position, angle) is not established. The resumption coincides with the drop in the camera housing temperature, but the drift does not come back when it rises: link not established. According to the expert, BREITHORN, MICHIGAN and NEBRASKA are in the same building: the cameras of the three stations tilt together, in the same direction and on the same dates (advance until 12 October, stop and slight backward movement from 13 to 16, resumption from the 17th to the end of the month), which points to a cause common to the building rather than a fault of this camera alone; at equal housing temperature, the cameras are more tilted at the end of the month than in the middle: temperature does not explain it alone, link not established. For the customer: the targets do not move relative to each other, this is not a movement of the structure; the camera tilt is to be monitored."}
diff --git a/auto/analyses/long-labels/BREITHORN/work/inventory.txt b/auto/analyses/long-labels/BREITHORN/work/inventory.txt
deleted file mode 100644
index 1bb81ca..0000000
--- a/auto/analyses/long-labels/BREITHORN/work/inventory.txt
+++ /dev/null
@@ -1,84 +0,0 @@
-Folder: data/BREITHORN
-"advanced" exports (source of the measurements): 78
- 78 files, first and last (--files for the full list):
- data/BREITHORN/displacement/BREITHORN_advanced_20260901.csv
- data/BREITHORN/displacement/BREITHORN_advanced_20261117.csv
-Hourly exports: 0 (not read by the tools: hourly averages, local time without a zone; see tools/DATA.md)
-Camera movements (pose at each registration): 78
- 78 files, first and last (--files for the full list):
- data/BREITHORN/camera/BREITHORN_camera_20260901.csv
- data/BREITHORN/camera/BREITHORN_camera_20261117.csv
-Other files: 2965
- 2965 files, first and last (--files for the full list):
- data/BREITHORN/metrics/BREITHORN_BatteryPercent_2026_09_01_00_00 to 2026_09_01_23_00.csv
- data/BREITHORN/targets.csv
-
-What the data contain, over the window (per column, the rows that have a value; "empty": none):
- "advanced" export: 2752 rows; x 2752, y 2752, error_value 2752, error_threshold 2752, relative_x 2752, relative_y 2752, corr_x 2651, corr_y 2651, reproj_err 667 (4 sensors of 16), inlier 663 (4 sensors of 16), sigma0 2720, pattern_type 2752, peak empty, flux empty, sharpness empty, fwhm empty, dominance empty, snr empty, corr_x_mm 1963 (12 sensors of 16), corr_y_mm 1963 (12 sensors of 16)
- Export image quality (peak to snr): empty
- Camera pose (camera/): 172 rows; median_pan 172, min_pan 172, max_pan 172, median_tilt 172, min_tilt 172, max_tilt 172, median_scale 172, min_scale 172, max_scale 172, median_rotation 172, min_rotation 172, max_rotation 172, median_sigma0 170, min_sigma0 170, max_sigma0 170
- System metrics (metrics/, one CSV per metric and per day; read by metrics.py): 38: BatteryPercent (30 d), BatteryState (30 d), BusCurrent (30 d), BusVoltage (30 d), BusVoltageOCV (30 d), BusVoltageTrend (30 d), DB_file_size (30 d), DB_not_uploaded (30 d), DB_total_entries (30 d), DB_uploaded (30 d), Power (30 d), SIM_CCID (30 d), ShuntVoltage (30 d), avail_disk_1k-blk (30 d), ber_percent (30 d), data_storage_free_gb (30 d), data_storage_total_gb (30 d), data_storage_used_gb (30 d), ip (30 d), ip_eth0 (30 d), ip_modem (30 d), ip_nebula1 (30 d), last_sync (30 d), link (30 d), mode (30 d), network_operator (30 d), network_technology (30 d), registration (30 d), rsrp_dBm (30 d), rsrq_dB (30 d), rssi_dbm (30 d), sensor_A0_deg_c (30 d), sensor_CPU_deg_c (30 d), sensor_GPU_deg_c (30 d), sensor_PLL_deg_c (30 d), sensor_thermal_deg_c (30 d), total_disk_1k-blk (30 d), used_disk_1k-blk (30 d)
- Camera images: 172
- Others: targets.csv (1)
-Images: 464, from 2026-09-01T00:00Z to 2026-11-17T16:00Z
- gap between two images over the window, per run of equal gaps (within 5 min):
- 2026-10-03T00:00Z → 2026-10-15T20:00Z: 78 images, every 240 min
- 2026-10-15T20:00Z → 2026-10-16T12:00Z: one gap of 960 min
- 2026-10-16T12:00Z → 2026-11-01T00:00Z: 94 images, every 240 min
-
-Measurement period: 2026-09-01T00:00Z → 2026-11-17T08:00Z, 446 instants
-Cadence (median step): 240 min
-Missing measurements (instants absent from the cadence): 20
- between 2026-10-15T20:00Z and 2026-10-16T12:00Z: 3
- between 2026-11-08T00:00Z and 2026-11-09T12:00Z: 8
- between 2026-11-11T00:00Z and 2026-11-12T12:00Z: 8
- between 2026-11-16T16:00Z and 2026-11-17T00:00Z: 1
-
-Sensors: 16 (4 references, 12 targets)
- distance (m) and mm/px: targets.csv (data.load_targets); "-": not in it, or not filled in (distance 1000 mm); "?": its lines (n) disagree, no corr_x_mm / corr_y_mm
-sensor type pattern threshold measurements rejected distance mm/px
-REFG44N reference global_ref 0.7 446 16 - -
-REFH22 reference global_ref 0.7 446 10 - -
-REFI'21 reference global_ref 0.7 446 57 - -
-REFPOU22 reference global_ref 0.7 446 61 - -
-COLH20 target target 0.7 446 0 21.6 8.116
-COLH20''' target target 0.7 446 38 22.6 8.560
-COLI20 target target 0.7 446 0 20.2 7.571
-COLI21 target target 0.7 446 0 30.3 11.351
-COLI22 target target 0.7 446 23 40.2 15.004
-COLI24 target target 0.7 446 67 60.3 22.539
-COLJ19 target target 0.7 446 0 8.9 3.272
-POUH21 target target 0.7 446 0 29.8 11.347
-POUI19 target target 0.7 446 0 9.4 3.546
-POUI20 target target 0.7 446 0 20.5 7.798
-POUI22 target target 0.7 446 45 40.4 15.220
-POUI24 target target 0.7 446 11 60.5 22.835
-
-Camera pose over the whole period: 436 registrations, 2026-09-01T00:00Z → 2026-11-16T00:00Z
-Measurement instants without a pose (no registration): 10 of 446
-
-Window 2026-10-03T00:00Z → 2026-11-01T00:00Z: 172 instants present
-Steps absent for all sensors, between two present instants (cadence of 240 min):
- between 2026-10-15T20:00Z and 2026-10-16T12:00Z: 3
-Present instants where sensors have no measurement:
- (none)
-Rejected measurements in the window, per sensor (start → end of each run of consecutive steps, count):
- REFH22 (6): 2026-10-09T00:00Z → 04:00Z (2); 2026-10-26T00:00Z → 04:00Z (2); 2026-10-26T16:00Z → 20:00Z (2)
- REFI'21 (1): 2026-10-07T12:00Z
- REFPOU22 (14): 2026-10-03T04:00Z → 2026-10-04T16:00Z (10); 2026-10-26T00:00Z → 04:00Z (2); 2026-10-27T00:00Z → 04:00Z (2)
- COLH20''' (15): 2026-10-03T04:00Z → 2026-10-04T16:00Z (10); 2026-10-13T04:00Z; 2026-10-26T00:00Z → 04:00Z (2); 2026-10-27T00:00Z → 04:00Z (2)
- COLI22 (13): 2026-10-06T20:00Z → 2026-10-07T04:00Z (3); 2026-10-08T00:00Z; 2026-10-09T00:00Z → 04:00Z (2); 2026-10-09T20:00Z; 2026-10-10T04:00Z; 2026-10-24T04:00Z → 12:00Z (3); 2026-10-26T00:00Z → 04:00Z (2)
- COLI24 (33): 2026-10-06T20:00Z → 2026-10-07T04:00Z (3); 2026-10-07T20:00Z → 2026-10-08T00:00Z (2); 2026-10-09T00:00Z → 04:00Z (2); 2026-10-09T20:00Z; 2026-10-10T04:00Z; 2026-10-13T04:00Z; 2026-10-21T20:00Z → 2026-10-22T04:00Z (3); 2026-10-22T20:00Z → 2026-10-23T04:00Z (3); 2026-10-23T20:00Z → 2026-10-25T20:00Z (13); 2026-10-26T16:00Z → 20:00Z (2); 2026-10-29T20:00Z → 2026-10-30T00:00Z (2)
- POUI22 (32): 2026-10-03T04:00Z → 2026-10-04T16:00Z (10); 2026-10-06T20:00Z → 2026-10-07T04:00Z (3); 2026-10-08T00:00Z; 2026-10-09T00:00Z → 04:00Z (2); 2026-10-09T20:00Z; 2026-10-10T04:00Z; 2026-10-24T04:00Z → 2026-10-25T20:00Z (11); 2026-10-26T20:00Z → 2026-10-27T04:00Z (3)
- POUI24 (8): 2026-10-04T16:00Z; 2026-10-10T04:00Z; 2026-10-24T04:00Z → 12:00Z (3); 2026-10-26T00:00Z → 04:00Z (2); 2026-10-26T16:00Z
-Retained references by the compensation (inlier = 1) out of 4, number of instants: 4: 153, 3: 17, 0: 2
-Instants where references are not retained (runs of consecutive steps with the same references out; r = rejected, empty = inlier empty, otherwise the inlier value):
- 2026-10-03T04:00Z → 2026-10-04T16:00Z (10): 3 retained; out: REFPOU22 (r)
- 2026-10-07T12:00Z: 3 retained; out: REFI'21 (r)
- 2026-10-09T00:00Z → 04:00Z (2): 3 retained; out: REFH22 (r)
- 2026-10-26T00:00Z → 04:00Z (2): 0 retained; out: REFG44N (empty), REFH22 (r), REFI'21 (empty), REFPOU22 (r)
- 2026-10-26T16:00Z → 20:00Z (2): 3 retained; out: REFH22 (r)
- 2026-10-27T00:00Z → 04:00Z (2): 3 retained; out: REFPOU22 (r)
-
-Camera pose in the window: 172 registrations, 2026-10-03T00:00Z → 2026-11-01T00:00Z
-Measurement instants without a pose (no registration): 0 of 172
diff --git a/auto/analyses/long-labels/BREITHORN/work/log.jsonl b/auto/analyses/long-labels/BREITHORN/work/log.jsonl
deleted file mode 100644
index ae0ee29..0000000
--- a/auto/analyses/long-labels/BREITHORN/work/log.jsonl
+++ /dev/null
@@ -1,57 +0,0 @@
-{"type":"system","subtype":"init","cwd":"/home/maxime/aimsight-app","session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","tools":["Read","Bash","Write"],"mcp_servers":[],"model":"claude-opus-5-5","permissionMode":"acceptEdits","slash_commands":["deep-research","design","slides","design-sync","dataviz","artifact-diagramming","whiteboard","artifact-capabilities","update-config","verify","debug","code-review","simplify","batch","fewer-permission-prompts","doctor","loop","schedule","claude-api","workflow-authoring","run","run-skill-generator","plugin-authoring","advisor","agents","auto-mode-setup","autocompact","clear","color","compact","config","output-style","context","effort","fast","focus","heapdump","init","mcp","import","model","__remote-workflow","workflow-launch-exec","reload-plugins","reload-skills","rename","ultrareview","security-review","usage-credits","extra-usage","usage","insights","recap","skill-doctor","goal","design-consent","design-revoke","list-agents","team-onboarding"],"terminal_slash_commands":["doctor","color","focus","reload-plugins"],"apiKeySource":"none","claude_code_version":"2.1.326","output_style":"default","agents":["agents:analyst","agents:support","agents:upgrader","agents:validator","claude","claude-code-guide","Explore","general-purpose","Plan","statusline-setup"],"skills":["deep-research","design","slides","design-sync","dataviz","artifact-diagramming","whiteboard","artifact-capabilities","update-config","verify","debug","code-review","simplify","batch","fewer-permission-prompts","doctor","loop","schedule","claude-api","workflow-authoring","run","run-skill-generator","plugin-authoring"],"plugins":[{"name":"agents","path":"/home/maxime/aimsight-app/agents","source":"agents@inline"},{"name":"cc-plugin-agents-md","path":"builtin","source":"cc-plugin-agents-md@builtin"},{"name":"cc-plugin-telemetry","path":"builtin","source":"cc-plugin-telemetry@builtin"},{"name":"cc-plugin-privacy","path":"builtin","source":"cc-plugin-privacy@builtin"},{"name":"cc-plugin-plugin-authoring","path":"builtin","source":"cc-plugin-plugin-authoring@builtin"}],"capabilities":["interrupt_receipt_v1","interrupt_cancel_queued_v1","interrupt_send_now_v1","interrupt_requeue_taken_v1","msg_lifecycle_v1","request_marker_lists_v1","ask_user_question_unanswered_v1","lifecycle_wakeup_source_v1","sdk_mcp_tools_list_changed","sdk_mcp_manifests","mcp_read_resource_v1","mcp_tool_ui_meta_v1","ui_surface_v1","mcp_call_result_not_for_model_v1","mcp_call_check_permissions_v1","voice_call_talk_line_v1","withdrawn_files_note_v2","ui_pane_widget_v1","reload_plugins_refuse_if_busy_v1","silent_resend_files_v1"],"analytics_disabled":false,"product_feedback_disabled":false,"uuid":"68026e32-e0ab-4a9b-9cc8-27a9c890cb23","memory_paths":{"auto":"/home/maxime/.claude/projects/-home-maxime-aimsight-app/memory/"},"scratchpad_path":"/tmp/claude-1000/-home-maxime-aimsight-app/b1dece15-7ed2-440e-993c-de42f2e6a4bf/scratchpad","original_cwd":"/home/maxime/aimsight-app","additional_directories":["/home/maxime/aimsight-data/data","/home/maxime/aimsight-labeling","/home/maxime/aimsight-tools"],"messaging_socket_path":"/run/user/1000/cc-socks/41405.sock","fast_mode_state":"off","fast_mode_disabled_reason":"sdk_opt_in_required","per_turn_effort_active":true,"ultrathink_available":false,"ultrathink_typed_raises":false,"view_mode":"default","startup_timing":{"entrypoint":"claude-desktop","warm_spare_claimed":false,"plugin_full_loads":0,"user_context_builds":1,"sdk_mcp_dial_runs":0,"sdk_mcp_servers_dialed":0,"flag_fetch_kick":"not_eligible","flag_fetch_kick_judged_at_ms":656,"hooks_init_source":"startup","phases":{"node_boot_ms":366,"settings_load_ms":1,"pre_action_mdm_keychain_ms":7,"pre_action_init_ms":260,"pre_action_client_data_url_ms":0,"pre_action_migrations_ms":0,"pre_action_managed_settings_ms":5,"pre_action_ms":299,"permission_context_ms":222,"setup_import_ms":1,"setup_uds_dir_ms":28,"setup_uds_listen_ms":30,"setup_uds_publish_ms":3,"setup_uds_messaging_ms":64,"setup_hooks_snapshot_ms":0,"setup_file_watcher_ms":0,"setup_release_notes_ms":40,"setup_ms":106,"skills_load_ms":186,"tools_commands_load_ms":88,"model_catalog_decision_ms":23,"mcp_config_wait_ms":16,"mcp_config_load_ms":2,"mcp_connect_ms":3,"hooks_init_ms":25,"print_import_ms":45,"grove_check_ms":20,"headless_prologue_ms":24,"initial_messages_load_ms":1,"headless_post_load_ms":5,"input_ready_ms":1395,"first_message_read_ms":1407,"sdk_mcp_update_ms":2,"first_message_handle_ms":2,"first_message_handle_cpu_ms":3,"first_message_handle_loop_lag_ms":0,"mcp_prewait_ms":2,"qe_system_prompt_ms":279,"prompt_submit_hooks_ms":6,"qe_plugin_skills_load_ms":14,"init_emit_ms":9},"time_origin_ms":1794947454991.6929,"phase_start_ms":{"node_boot_ms":0,"settings_load_ms":379,"pre_action_mdm_keychain_ms":387,"pre_action_init_ms":394,"pre_action_client_data_url_ms":654,"pre_action_migrations_ms":658,"pre_action_managed_settings_ms":658,"pre_action_ms":387,"permission_context_ms":696,"setup_import_ms":922,"setup_uds_dir_ms":931,"setup_uds_listen_ms":959,"setup_uds_publish_ms":988,"setup_uds_messaging_ms":928,"setup_hooks_snapshot_ms":994,"setup_file_watcher_ms":994,"setup_release_notes_ms":996,"setup_ms":930,"skills_load_ms":928,"tools_commands_load_ms":1071,"model_catalog_decision_ms":1193,"mcp_config_wait_ms":1227,"mcp_connect_ms":1275,"hooks_init_ms":1258,"print_import_ms":1282,"grove_check_ms":1330,"headless_prologue_ms":1328,"initial_messages_load_ms":1352,"headless_post_load_ms":1353,"input_ready_ms":0,"first_message_read_ms":0,"sdk_mcp_update_ms":1407,"first_message_handle_ms":1407,"mcp_prewait_ms":1413,"qe_system_prompt_ms":1430,"prompt_submit_hooks_ms":1858,"qe_plugin_skills_load_ms":1987,"init_emit_ms":2001}}}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98mXGZHTwkpyqp1x5rZ","type":"message","role":"assistant","content":[{"type":"thinking","thinking":"","signature":"CAQSwQUKEAgTGAI4AUIIdGhpbmtpbmcSDEIS40hIIIUzPeUJOhoMzz7UFAVI3QuHzaXWIjCJImr+KY0VZGloiXPa4Mu2oIOzQWLDD4AY0KxP4d274uijfJrwEoj8TjLVWH0GgSsq3gQffJIcZ8iBqq1wPm8RlWXrJV+XLafPNrk/ny9qr4NieZoZj0/hXhQxiV94VgicsFzCxerDBhK6uPV2PEopGLEH9PueY15aUkpvouUhpeIzbsaZcRLwhL6e5FB6w3bMfTmQFIJ2JLpJ/5ihP6goVgEEVyWF0WR/NxZuSxmSBDTcbh1WFzUHSiVpRc4NL7dtiAuCqbmPDAfbZmceiq4r46fU2+/vHp6N05QnCYF9y6FNMqTFla1FdVJ/5uExrtL28cKbtUBS6qq1lZF0wqGJDZW2Gxn3ywyqfOmyja7hIvs4CfGEfw7RpR5R9oevTPQVrzcrt60FBtItgK5uSNbt2DXC0sOY17GQtS/uAow+MTPM2G1gPbGGGbRmviL4pzYz0ymfXHuSjNphcw4kQImP3Xms1nQrnjNwgdb0guJd/Fv9DhPhm7ibP/l3wFp3lfonqr8f0nT26/d/sm89Sy8vUt27hR+ZXulCPMiWMv71Y3t+ktQqFAV3a0wapjpPVQRmdNMijVmtxwVYvZViz2Nyuwev2FFaU4zdnV1c1B+LFaUTxkMJbg8PhxNS2tPu/2VhpPg67g3yoF/UcNr4ISHkUn3Rt14d5bk2NGKqtwQuxaB1XR/0nACedva60O98xPN69+geO9y2sdd+XDxELT+EISkdiESdyqwyazZtYK+nWxy/TVlnzsWrgZ/Aw0i5Q6p5jIq2C8UEo8kvLHE+SpD5cIZtI3wvc7e6XIVWnlxU5FExwyroExGbErKXpMEPfM7JjcOCJEIAPa2a4cfgc1t5xwo3KBNKkgLFgu93TTJRWJIYAQ=="}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":3962,"cache_read_input_tokens":5976,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":3962},"output_tokens":8,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"2655a29f-3a45-48fa-8d80-95c490a30584","timestamp":"2026-11-17T20:30:59.484Z","request_id":"req_011Ch98mX4PwgEq9bx8fQqJb","thinking_duration_ms":559,"thinking_display":"updates"}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98mXGZHTwkpyqp1x5rZ","type":"message","role":"assistant","content":[{"type":"tool_use","id":"toolu_01VrKN2xwmZsx3Gcjm13QD6e","name":"Bash","input":{"command":"cd /home/maxime/aimsight-app; cat labeling/auto/analyses/long-labels/BREITHORN/input.jsonl; ls labeling/auto/analyses/long-labels/BREITHORN/; ls -d labeling/auto/analyses/BREITHORN_*; wc -l tools/GUIDE.md tools/DATA.md labeling/families.md labeling/labeling-rules.md labeling/reading-rules.md labeling/stations.md","description":"List input labels and docs"},"caller":{"type":"direct"}}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":3962,"cache_read_input_tokens":5976,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":3962},"output_tokens":8,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"ae063987-952b-4ffd-b411-f78f49022f45","timestamp":"2026-11-17T20:31:00.810Z","request_id":"req_011Ch98mX4PwgEq9bx8fQqJb","wire_tool_inputs":{"toolu_01VrKN2xwmZsx3Gcjm13QD6e":{"command":"cd /home/maxime/aimsight-app; cat labeling/auto/analyses/long-labels/BREITHORN/input.jsonl; ls labeling/auto/analyses/long-labels/BREITHORN/; ls -d labeling/auto/analyses/BREITHORN_*; wc -l tools/GUIDE.md tools/DATA.md labeling/families.md labeling/labeling-rules.md labeling/reading-rules.md labeling/stations.md","description":"List input labels and docs"}}}
-{"type":"rate_limit_event","rate_limit_info":{"status":"allowed_warning","resetsAt":1794954600,"rateLimitType":"five_hour","utilization":0.99,"overageStatus":"rejected","overageDisabledReason":"org_level_disabled","isUsingOverage":false,"surpassedThreshold":0.9,"unifiedWindows":{"five_hour":{"utilization":0.99,"resetsAt":1794954600,"status":"allowed_warning","surpassedThreshold":0.9},"seven_day":{"utilization":0.72,"resetsAt":1795302000,"status":"allowed"}},"overageEnabled":false},"uuid":"a15f7ea0-7556-40dc-9412-0d04cffa20f4","session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf"}
-{"type":"system","subtype":"task_summary","detail":"Listing input labels and docs","uuid":"6d3d67d5-2ae4-4ac6-a99f-e86dc878729d","session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf"}
-{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_01VrKN2xwmZsx3Gcjm13QD6e","type":"tool_result","content":"{\"id\": \"BREITHORN-2\", \"start\": \"2026-10-03T00:00Z\", \"end\": \"2026-10-13T04:00Z\", \"family\": \"Displacement\", \"description\": \"From the start of the data to 13 October, six targets drift slowly and steadily, all in the same direction, mostly in corr_x, in corr_y too except POUI19: COLH20, COLI20, COLI21, COLJ19, POUI19 and POUI20; COLI24 drifts in the opposite direction in corr_y. Their drift follows the camera pose step by step, as the camera gradually tilts (tilt increasing, pan and rotation decreasing), while their position in the image hardly moves and their error_value stays stable; the other targets, such as POUH21, do not drift. Cause given by the expert: the camera is gradually nodding forward and the compensation of its movement is not complete, correcting some targets better than others. According to the expert, COLJ19 and POUI19, which drift the most, are much closer to the camera than the other targets; for the other drifting targets, the reason for their poorer compensation (position, angle) is not established. The temperature of the camera housing drops slightly over the range, link not established. According to the expert, BREITHORN, MICHIGAN and NEBRASKA are in the same building: the cameras of the three stations tilt together, in the same direction and on the same dates (advance until 12 October, stop and slight backward movement from 13 to 16, resumption from the 17th to the end of the month), which points to a cause common to the building rather than a fault of this camera alone; at equal housing temperature, the cameras are more tilted at the end of the month than in the middle: temperature does not explain it alone, link not established. For the customer: the targets do not move relative to each other, this is not a movement of the structure; the camera tilt is to be monitored.\", \"review\": \"2026-11-17\"}\n{\"id\": \"BREITHORN-13\", \"start\": \"2026-10-16T20:00Z\", \"end\": \"2026-11-01T00:00Z\", \"family\": \"Displacement\", \"description\": \"From 17 October to the end of the batch, the drift resumes, faster than at the beginning of the month until the 25th, then clearly slower without stopping: the camera tilts again (tilt increasing, pan and rotation decreasing), and COLH20, COLI20, COLI21, COLJ19, POUI19 and POUI20 drift with it, mostly in corr_x and also in corr_y, POUI19 the most; COLI24 drifts in the opposite direction in corr_y. Their position in the image hardly moves, their error_value stays stable, POUH21 does not drift. Cause given by the expert: the camera is nodding forward and the compensation of its movement is not complete, correcting some targets better than others. According to the expert, COLJ19 and POUI19, which drift the most, are much closer to the camera than the other targets; for the other drifting targets, the reason for their poorer compensation (position, angle) is not established. The resumption coincides with the drop in the camera housing temperature, but the drift does not come back when it rises: link not established. According to the expert, BREITHORN, MICHIGAN and NEBRASKA are in the same building: the cameras of the three stations tilt together, in the same direction and on the same dates (advance until 12 October, stop and slight backward movement from 13 to 16, resumption from the 17th to the end of the month), which points to a cause common to the building rather than a fault of this camera alone; at equal housing temperature, the cameras are more tilted at the end of the month than in the middle: temperature does not explain it alone, link not established. For the customer: the targets do not move relative to each other, this is not a movement of the structure; the camera tilt is to be monitored.\", \"review\": \"2026-11-17\"}\ninput.jsonl\nwork\nlabeling/auto/analyses/BREITHORN_2026-10-03T0000_2026-10-13T0000\nlabeling/auto/analyses/BREITHORN_2026-10-13T0000_2026-10-22T1600\nlabeling/auto/analyses/BREITHORN_2026-10-22T1600_2026-11-01T0000\n 240 tools/GUIDE.md\n 74 tools/DATA.md\n 101 labeling/families.md\n 107 labeling/labeling-rules.md\n 100 labeling/reading-rules.md\n 17 labeling/stations.md\n 639 total","is_error":false}]},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"9bd20347-e84b-40b1-969c-4673f78ac3b6","timestamp":"2026-11-17T20:31:01.095Z","tool_use_result":{"stdout":"{\"id\": \"BREITHORN-2\", \"start\": \"2026-10-03T00:00Z\", \"end\": \"2026-10-13T04:00Z\", \"family\": \"Displacement\", \"description\": \"From the start of the data to 13 October, six targets drift slowly and steadily, all in the same direction, mostly in corr_x, in corr_y too except POUI19: COLH20, COLI20, COLI21, COLJ19, POUI19 and POUI20; COLI24 drifts in the opposite direction in corr_y. Their drift follows the camera pose step by step, as the camera gradually tilts (tilt increasing, pan and rotation decreasing), while their position in the image hardly moves and their error_value stays stable; the other targets, such as POUH21, do not drift. Cause given by the expert: the camera is gradually nodding forward and the compensation of its movement is not complete, correcting some targets better than others. According to the expert, COLJ19 and POUI19, which drift the most, are much closer to the camera than the other targets; for the other drifting targets, the reason for their poorer compensation (position, angle) is not established. The temperature of the camera housing drops slightly over the range, link not established. According to the expert, BREITHORN, MICHIGAN and NEBRASKA are in the same building: the cameras of the three stations tilt together, in the same direction and on the same dates (advance until 12 October, stop and slight backward movement from 13 to 16, resumption from the 17th to the end of the month), which points to a cause common to the building rather than a fault of this camera alone; at equal housing temperature, the cameras are more tilted at the end of the month than in the middle: temperature does not explain it alone, link not established. For the customer: the targets do not move relative to each other, this is not a movement of the structure; the camera tilt is to be monitored.\", \"review\": \"2026-11-17\"}\n{\"id\": \"BREITHORN-13\", \"start\": \"2026-10-16T20:00Z\", \"end\": \"2026-11-01T00:00Z\", \"family\": \"Displacement\", \"description\": \"From 17 October to the end of the batch, the drift resumes, faster than at the beginning of the month until the 25th, then clearly slower without stopping: the camera tilts again (tilt increasing, pan and rotation decreasing), and COLH20, COLI20, COLI21, COLJ19, POUI19 and POUI20 drift with it, mostly in corr_x and also in corr_y, POUI19 the most; COLI24 drifts in the opposite direction in corr_y. Their position in the image hardly moves, their error_value stays stable, POUH21 does not drift. Cause given by the expert: the camera is nodding forward and the compensation of its movement is not complete, correcting some targets better than others. According to the expert, COLJ19 and POUI19, which drift the most, are much closer to the camera than the other targets; for the other drifting targets, the reason for their poorer compensation (position, angle) is not established. The resumption coincides with the drop in the camera housing temperature, but the drift does not come back when it rises: link not established. According to the expert, BREITHORN, MICHIGAN and NEBRASKA are in the same building: the cameras of the three stations tilt together, in the same direction and on the same dates (advance until 12 October, stop and slight backward movement from 13 to 16, resumption from the 17th to the end of the month), which points to a cause common to the building rather than a fault of this camera alone; at equal housing temperature, the cameras are more tilted at the end of the month than in the middle: temperature does not explain it alone, link not established. For the customer: the targets do not move relative to each other, this is not a movement of the structure; the camera tilt is to be monitored.\", \"review\": \"2026-11-17\"}\ninput.jsonl\nwork\nlabeling/auto/analyses/BREITHORN_2026-10-03T0000_2026-10-13T0000\nlabeling/auto/analyses/BREITHORN_2026-10-13T0000_2026-10-22T1600\nlabeling/auto/analyses/BREITHORN_2026-10-22T1600_2026-11-01T0000\n 240 tools/GUIDE.md\n 74 tools/DATA.md\n 101 labeling/families.md\n 107 labeling/labeling-rules.md\n 100 labeling/reading-rules.md\n 17 labeling/stations.md\n 639 total","stderr":"","interrupted":false,"isImage":false,"noOutputExpected":false},"tool_result_meta":[{"id":"toolu_01VrKN2xwmZsx3Gcjm13QD6e","permission_decision":{"decision":"accept","source":"config","reason_type":"rule"}}]}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98moiGVLeyFXtHKAJ8f","type":"message","role":"assistant","content":[{"type":"tool_use","id":"toolu_013TnQF76LTA6ACbWGHsBgqa","name":"Bash","input":{"command":"cd /home/maxime/aimsight-app; cat tools/GUIDE.md tools/DATA.md labeling/labeling-rules.md","description":"Read guide, data doc, labeling rules"},"caller":{"type":"direct"}}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":1698,"cache_read_input_tokens":9938,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":1698},"output_tokens":21,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"61f46e03-496d-44b3-bcd7-e5c1a11ba181","timestamp":"2026-11-17T20:31:03.189Z","request_id":"req_011Ch98moXrDRw3CYGGV9ZtA","wire_tool_inputs":{"toolu_013TnQF76LTA6ACbWGHsBgqa":{"command":"cd /home/maxime/aimsight-app; cat tools/GUIDE.md tools/DATA.md labeling/labeling-rules.md","description":"Read guide, data doc, labeling rules"}}}
-{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_013TnQF76LTA6ACbWGHsBgqa","type":"tool_result","content":"\nOutput too large (70KB). Full output saved to: /home/maxime/.claude/projects/-home-maxime-aimsight-app/b1dece15-7ed2-440e-993c-de42f2e6a4bf/tool-results/bbi9zey7i.txt\n\nPreview (first 2KB):\n# Reading the data\n\nThe guide to the reading harness: followed by the analyst; improved by the upgrader (agents repository), run by Optimizer's `optimize` skill, the only one that writes here.\n\nA camera tracks targets (reflectors) fixed on a structure; its own movement is compensated thanks to reference targets, assumed fixed. This movement, the **camera pose** (`pan`, `tilt`, `rotation` in degrees, `scale`, `sigma0` of the registration, in `camera/`), is read before the sensors: it explains a large part of what moves on the curves (D-073). This guide says how to read a station's data: what the curves and the images show, moment by moment. It does not say what they mean: family, known event, hypothesis and verdict are the business of whoever calls you.\n\n## Read first\n\n- `tools/DATA.md`: the files of a station and the meaning of each column, the image quality metrics, the camera images (**first**);\n- `labeling/reading-rules.md`: what the data mean (the measurement chain, gaps, reading rules, false friends).\n\n## The tools\n\nRun them from the root of the calling repository, where `tools/`, `data/` and `labeling/` are links. They return values, never verdicts: you judge. `--out `: where whoever calls you stores your figures; they give it to you. The method (below) says in which order to run them; each section says what a tool returns and how to read it.\n\n| Tool | The question it answers |\n|---|---|\n| [`inventory.py`](#inventory) | What is there, what is missing: files, contents of each source, images, poses, cadence, sensors, rejections |\n| [`summary.py`](#summary) | The usual level of each sensor, then one column by time step |\n| [`plot.py`](#plot) | The series of chosen sensors and columns, as a PNG |\n| [`overview.py`](#overview) | All the sensors together, against the camera pose: common movement, single sensors, residuals, rigid movement |\n| [`ranges.py`](#ranges) | Dated ranges where each sensor leaves its level, at the native step |\n...\n","is_error":false}]},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"bd6a4ee4-9d17-4c09-a609-e3518378e7c5","timestamp":"2026-11-17T20:31:03.256Z","tool_use_result":{"stdout":"# Reading the data\n\nThe guide to the reading harness: followed by the analyst; improved by the upgrader (agents repository), run by Optimizer's `optimize` skill, the only one that writes here.\n\nA camera tracks targets (reflectors) fixed on a structure; its own movement is compensated thanks to reference targets, assumed fixed. This movement, the **camera pose** (`pan`, `tilt`, `rotation` in degrees, `scale`, `sigma0` of the registration, in `camera/`), is read before the sensors: it explains a large part of what moves on the curves (D-073). This guide says how to read a station's data: what the curves and the images show, moment by moment. It does not say what they mean: family, known event, hypothesis and verdict are the business of whoever calls you.\n\n## Read first\n\n- `tools/DATA.md`: the files of a station and the meaning of each column, the image quality metrics, the camera images (**first**);\n- `labeling/reading-rules.md`: what the data mean (the measurement chain, gaps, reading rules, false friends).\n\n## The tools\n\nRun them from the root of the calling repository, where `tools/`, `data/` and `labeling/` are links. They return values, never verdicts: you judge. `--out `: where whoever calls you stores your figures; they give it to you. The method (below) says in which order to run them; each section says what a tool returns and how to read it.\n\n| Tool | The question it answers |\n|---|---|\n| [`inventory.py`](#inventory) | What is there, what is missing: files, contents of each source, images, poses, cadence, sensors, rejections |\n| [`summary.py`](#summary) | The usual level of each sensor, then one column by time step |\n| [`plot.py`](#plot) | The series of chosen sensors and columns, as a PNG |\n| [`overview.py`](#overview) | All the sensors together, against the camera pose: common movement, single sensors, residuals, rigid movement |\n| [`ranges.py`](#ranges) | Dated ranges where each sensor leaves its level, at the native step |\n| [`days.py`](#days) | What comes back from one day to the next: night levels, days superimposed by hour, bounds of each day |\n| [`metrics.py`](#metrics) | The system metrics (temperature, voltage…) against the targets and the pose |\n| [`stations.py`](#stations) | Several stations on the same timeline |\n| [`quality.py`](#quality) | The six image quality metrics against a calm reference; labels; degraded instants no label covers |\n| [`thumbnails.py`](#thumbnails) | Full-resolution thumbnails of the camera images, around sensors or of a zone |\n| [`gif.py`](#gif) | A GIF of the camera images over a range, for a reply to the customer |\n| [`ls … \\| grep`](#whole-image) | The whole camera image at a time |\n\n### inventory\n\n```\npython3 tools/scripts/inventory.py [--start T] [--end T] [--files]\n```\n\nNames and counts, never values. Over the **whole period**:\n- files by type: beyond 5 per type, the count, the first and the last (`--files`: the full list, only to look for a specific file);\n- **what each source contains** over the window: the columns of the export, of the pose, of `quality/` and of `weather/` (the MeteoSwiss weather, hourly; a station without a Swiss position has none), with the number of rows that have a value (\"empty\" otherwise; an export column that not all sensors carry says how many carry it); the names of the system metrics of `metrics/`; the images and the difference images. The \"Export image quality (peak to snr)\" line says whether the six quality metrics are filled (then `quality.py`) or empty;\n- images by runs of equal gaps between two images (within 5 min, over the window if given): one line per change of gap, a hole is dated by its two images;\n- camera poses (count, period, measurement instants without registration), period, cadence, missing measurements, sensors (reference or target, error threshold, rejected measurements, distance from the camera and mm per px of `targets.csv`). When `pattern_type` is empty, a sensor is a reference if it carries `reproj_err` or `inlier` (the \"pattern_type empty for N sensors\" line says so);\n- \"Duplicate readings\": an export (often named after the customer's project) whose readings are already in the others; with 0 different values, it changes nothing to the reading, otherwise the tools keep the one of the last file in name order.\n\nWith `--start`/`--end` (on a batch: those of the batch), a section for the window: the missing steps, dated (for all the sensors, or which ones are missing); by sensor, the rejected measurements, dated (runs of consecutive steps; rejected: `error_value` above the sensor's threshold, **references included**); then the **number of references retained by the compensation** (`inlier` = 1) at each instant and the dated runs where some are not, which ones and why (`r` rejected, `0` discarded by the compensation, `empty`; another mark is the value of `inlier`, e.g. `-1`). When `inlier` is empty over the window, the retained references are read from the filled `reproj_err` (the title says so).\n\nA run that ends the same day writes only the time of its end. Over a month, the output with `--start`/`--end` exceeds what a call displays: read each section through `grep` (`| grep -A40 '^Retained references'`, `| grep '^ PR04 '`).\n\n### summary\n\n```\npython3 tools/scripts/summary.py [--column C] [--stat median|min|max] [--step 1h] [--level period|window] [--sensors A,B] [--start T] [--end T] [--instants T1,T2] [--mark]\n```\n\nThe usual level of each sensor (median, MAD, min, max) over the whole period, or over the `--start`/`--end` window with `--level window` (for a batch: a level change within the batch is not compared with weeks of other measurements); then a table by time step, the sensor header repeated every 24 lines.\n- Columns: `error_value`, `corr_x`, `corr_y`, `relative_x`, `relative_y`, `x`, `y`, `sigma0`, `reproj_err`, `corr_x_mm`, `corr_y_mm` (the `corr` in mm, empty without a sure factor: `tools/DATA.md`, \"The targets\"), and the six image quality metrics `peak`, `flux`, `sharpness`, `fwhm`, `dominance`, `snr` (raw values; against a calm reference, `quality.py`).\n- `--mark`: `*` after the value when a measurement of the step is rejected (`x`, `y`, `error_value` of a rejected measurement stay filled), `o` when one has inlier = 0.\n- `--instants T1,T2`: only the steps that contain these instants (the values of all the sensors at a few chosen times).\n- With `--step` equal to the cadence, `--level window --mark`: the per-instant, per-sensor table of one column, one column per run.\n\n### plot\n\n```\n.venv/bin/python tools/scripts/plot.py [--sensors A,B] [--columns C1,C2] [--start T] [--end T] [--zone T1/T2 ...] [--out D]\n```\n\nA PNG of the series, each `--zone` greyed; prints its path. Columns: those of `summary.py`, quality metrics included (raw values).\n\n### overview\n\n```\n.venv/bin/python tools/scripts/overview.py [--columns x,y,sigma0] [--column error_value] [--step 15min] [--k 5] [--min 5] [--residuals corr_x,corr_y,error_value|no] [--outside T1/T2] [--others] [--rigid BASE [--without A,B] [--follow A,B]] [--table T1/T2|no] [--sensors A,B] [--start T] [--end T] [--out D]\n```\n\nAll the sensors together, each against its median and its MAD over the window.\n\nPNGs:\n- **common**: at the top, if the folder has `camera/`, the **camera pose** (raw values, one point per registration, the line cut at measurement instants without registration); the median across sensors of `x`, `y`, `sigma0`, the dispersion across sensors as a grey band; on the `x`, `y` panels, also **each global reference separately** (one line each) and the **median of the targets alone** (black line); at each step, the number of sensors whose `--column` exceeds its median by more than `--k` MAD. Ticks every 1 to 12 h depending on the window, every n days beyond 20 days.\n- **multiples**: a small chart per sensor, one scale each: a step of a single sensor shows there.\n- **residuals-corr_x**, **-corr_y**, **-error_value** (`--residuals`; `no`: none of these PNGs nor their tables): a small chart per sensor of the column minus the sensor's own level (its median over the window; with `--outside T1/T2`, that of the rest of the window, outside the moment read), one scale each, zero dotted: a deviation of a few hundredths on `corr`, hidden in the parallel bands of `plot.py`, shows there.\n- **residuals-…-others** (`--others`): each sensor minus its own median **and minus the median of the other sensors at the same instant**: what all share (the remainder of the compensation of a common movement) cancels, what is specific remains.\n- **rigid** (`--rigid BASE`): at each measurement, the overall movement of the targets since the instant `BASE` (translation, rotation, scale, estimated by medians: a target that jumps alone does not pull it; `--without A,B` removes targets from it) and, for each sensor, the **residual** `dx`, `dy` (raw position minus its position at `BASE` carried by this movement, in px). Panels: `dx`, `dy` of each global reference against the median and the 10th-90th percentile of the targets, `|residual|` of the targets (median, 90th percentile), fitted rotation and scale, `reproj_err` of the references; a rejected reference is a cross (the scale is that of the accepted measurements, a far cross is out of frame).\n\nPrinted:\n- the **common median table**, one line per `--step`: the time, the deviation from the window median of `x`, `y`, `sigma0`, then `x_targets`, `y_targets` (median of the targets alone), then the raw camera pose `cam_pan`, `cam_tilt`, `cam_rotation`, `cam_scale`, `cam_sigma0` (empty without registration); the minimum and the maximum of each column with their instant; then those of `x`, `y` of each global reference (`(rejected)` when the measurement is, with the reference's number of rejected measurements); the measurement instants without pose (dated runs); the instants where at least `--min` sensors exceed together, with their names (`--min 1`: also a single sensor that leaves its level, absent from the default list of 5 sensors);\n- `--residuals`: per sensor, the level, the own noise (median of the differences between two measurements), the min/max deviation per step with their instant, in units and in noises;\n- `--others`: per sensor, the slope and the correlation r of the residual on the common median of `x`, `y`, `sigma0`;\n- `--rigid`: the table by step (`rot_deg`, `scale`, `tx`, `ty`, `tgt_med`, `tgt_max`, `dx`, `dy` of each reference and of each sensor of `--follow A,B`: the step-by-step sequence of a target) and, per sensor, min, max and value at the last instant of `dx`, `dy`. Rejected measurements enter neither the fit, nor the band of the targets, `tgt_med`, `tgt_max`, nor the columns of the table (over several days, parked cars or night rejections no longer drown the rest); the per-sensor summary gives them separately (`; N rejected: min …, max …`, and `(rejected)` after a last value that is rejected).\n\nThe tables by step (common median, `--rigid`) repeat their header every 24 lines; `--table T1/T2` prints them only between T1 and T2 (`no`: not at all), levels, min, max, PNGs and the rest remaining over the whole window: over a one-month batch, first `--table no`, then `--table` on the day of a moment (same levels, which a shorter `--start`/`--end` window would not give). The default step is 15 min, the cadence of the measurements: a one-hour step flattens a peak of one to four steps, dates to the hour and erases an agitation of `x`, `y`; do not widen it to read a batch.\n\nReading, in this order:\n1. **The camera pose first** (top panels, `cam_` columns), dated at the native step: when it rotates (`pan`, `tilt`, `rotation`), changes scale, when its registration degrades (`sigma0`) or is absent (line cut, instants without pose). Each moment of the sensors is read against it: during a movement or a registration gap, or camera still.\n2. **Who moves in the image.** The pose is computed from the global references: a change of pose (or a rise of `sigma0`) is a camera movement only if **the targets also move in the image** (on the `x`, `y` panels, the lines of the references against the black line of the targets alone; `x_targets`, `y_targets`). Only references move, targets still: these references moved, and the pose and the `corr` of all the targets are skewed without raw movement of the targets; say which references and by how much. References and targets together: the camera or the scene; then look whether the `corr` come back.\n3. **Rotation or scale: `--rigid`.** Then the deviation from the median no longer says who moves alone (each sensor deviates according to its place in the image; the rigid residual does not). Before writing \"everything moves together\", rerun with `--rigid BASE`, `BASE` a calm instant before the first movement: a reference whose residual stays far from the 10th-90th percentile of the targets, or a `reproj_err` of the references that does not come back, means the compensation remains skewed by these references and the steps of `corr` partly come from it (say which, by how much, until when); a rising `|residual|` of the targets says they do not move as a block.\n4. **Then `x`, `y`, `sigma0`, before `corr`**: the median of `x`, `y` (raw position, references included), the references one by one, the targets alone and `sigma0` say what moves in the image. Date the start, the end, the return of a movement, or a level that does not come back, on the printed table (time, value), not on the PNG axis. A dip of `corr` after a movement of the raw median is the remainder of the compensation, not a movement of these sensors. The multiples of `error_value` show a lasting step of a sensor, the count the instants where many rise together.\n5. **The residuals, on every batch, without waiting for a suspicion**: a single sensor that rises or falls, a `corr` that drifts by a few hundredths, a step specific to one sensor under a common movement show there; the table says by how much (in noises) and when. On a target whose `corr` goes down under a strong common movement, `--others` separates a remainder of the compensation from a movement of its own: a dip that remains is not a remainder shared by all; a high slope with r close to ±1 on common `y` says it is proportional to the common movement (gain specific to the sensor); without r or slope, it is independent of the movement.\n\n### ranges\n\n```\npython3 tools/scripts/ranges.py [--columns error_value,corr_x,corr_y] [--k 5] [--merge 1h] [--min-measurements 1] [--outside T1/T2] [--rolling N|DURATION] [--instants N] [--sensors A,B] [--start T] [--end T]\n```\n\nDates the start and the end of a sensor's moment without rerunning ten tables. By column and by sensor, at the measurements (native step, never averaged): level (median of the window), own noise, **largest jump** from one measurement to the next (value, in noises, the two instants; `(rejected: …)` when one end is); then the **ranges** where the sensor deviates from its level by more than `--k` noises: start, end, number of measurements, extreme (signed, in units and in noises) and its instant. Two ranges of the same sign less than `--merge` apart make one; rejected measurements do not cut a range; column `rejected`: how many of the range's measurements are (and `rejected extreme`). A range that touches the edge of the window is dated at the edge.\n- `--outside T1/T2`: level and noise computed outside an episode that skews the window median (the sensor spends half the batch there). Rerun with it around a long episode to date its return to the level: do not conclude \"does not come back\" without having read it.\n- `--min-measurements N`: only the ranges of at least N measurements (and how many out of the total). Over several days, the one-step ranges number in the hundreds and drown the long steps: first `--min-measurements 6`, then without.\n- `--rolling N` (N measurements on each side) or `--rolling 1d` (the measurements within a duration): the level of each measurement is the median of its neighbours, without it; a long drift or a step follows this local level, only the deviations shorter than the window remain (the level column and the noise do not change; with `--outside`, only the noise is computed outside the episode).\n- `--instants N`: at the end, the instants where at least N sensors are out of level on one of the columns, with each sensor and its signed deviation in noises (`cx` corr_x, `cy` corr_y, `ev` error_value), the sensors rejected at that instant (among `--sensors`: removing the always-rejected sensors lightens the list), and each reference: `error_value` (`r` if rejected) / inlier.\n- When the batch has a long drift or several steps (the ranges number in the hundreds, or one half of the batch is \"out of level\"), rerun with `--rolling` (a few measurements, or a few hours to a day depending on the cadence) and `--instants 2`: the brief deviations under the drift come out alone, and the list per instant says which sensors deviate together, which are rejected and what the references do; a deviation of all the targets with the references at the same instant is read against the camera pose.\n\nA noise of `0` (and \"-\" in noises, no range): the values are constant to rounding (deviations below 1e-9), like the `corr` of the references when the compensation retains only two (see Conventions); the same in `overview.py --residuals` and `days.py`.\n\n### days\n\n```\n.venv/bin/python tools/scripts/days.py [--columns corr_x,corr_y,error_value] [--night 20-3] [--k 5] [--days 2] [--step 15min] [--sensors A,B] [--bounds [--smoothing N] [--fraction F]] [--start T] [--end T] [--out D]\n```\n\nWhat comes back from one day to the next, on accepted measurements only. A night: the hours `--night` H1-H2 UTC, straddling midnight, dated from the day it starts; choose hours where the day cycle (`error_value`, camera pose) has subsided (**byhour** figure).\n\n1. **Level of each night**, by sensor and by column: median, MAD, number of measurements, own noise; from one night to the next, the **step** (difference of the medians, in units and in noises) and **where it falls** (\"between A and B\": where the night measurements of the two nights split best between the two levels; B at the start of the following night: the cut falls by day). Read it for any sensor that has already made a step or for which `--outside` is not enough (several levels in the batch): a step of a few noises is dated by its \"between A and B\", a step of `error_value` and one of `corr` at the same instant are linked, a slow drift reads from one night to the next.\n2. **Superimposed days**: PNG **byhour-**, a small chart per sensor, hour of the day on the x axis, one curve per day, each measurement minus the level of the last night started (night greyed, frame from the 1st to the 99th percentile, the title says how many measurements fall outside it). Table: per `--step` slot of the hour of the day, the sensors whose deviation exceeds `--k` noises on the same side at least `--days` days, with the number of days and the median of these deviations. What comes back every day at the same hour, on one or several sensors, groups there, even when it lasts one to three measurements: one moment per hour of the day (say which sensors, how many days out of how many, the amplitude, what the camera pose does at that hour), not one moment per day, nor nothing because each step is short.\n3. **Bounds of each day** (`--bounds`), for what comes back every day and is labelled day by day (thermal cycle, warming and cooling), rather than fixing the same hours for all the days: for the median of the targets of each column (with `--sensors`, the median of these sensors; with one, its own) and for the camera pose (`pan`, `tilt`, `rotation`, `scale`, `sigma0`, if `camera/` exists), the deviation from the level of the night that precedes each day (a day goes from the end of one night to the end of the next). Per day: number of measurements, the first and the last; first and last instant beyond `--k` noises, with the measurement just before and just after, at the native step; signed max and min with their instant; the sequence of measurements beyond `--k` noises around the larger of the two; the following night minus the reference night. A day without measurement says so; a reference night that is not the previous one is named. Each day line starts with the short name of its series (`corr_x`, `pose_tilt`…): `| grep '^pose_tilt '` reads one, `| grep ' 12/10 '` one day. PNG **bounds**: the deviation over the batch, first → last exceedance light grey, sequence around the extreme dark grey, max and min marked.\n - `--smoothing N`: the deviation of each measurement is the median of the N measurements of the day centred on it (noise and `--k` unchanged; PNG: smoothed in blue, raw in grey): an isolated point no longer cuts the sequence around the extreme nor makes a first or a last exceedance.\n - `--fraction F`: the threshold of each day is F times its largest |deviation| (printed on its line, `threshold …`), instead of `--k` noises: when the noise at the native step is unrelated to the amplitude of the cycle (very noisy or very smooth pose).\n - Reading: the sequence around the extreme dates the cycle, the max and the min a go and a return (morning and afternoon); \"before\" and \"after\" give the bounds at the native step (at a cadence of 1 h or 4 h, an event goes from the measurement before to the one after). First exceedance at the start of the day (\"before -\") and last at its end every day: the night is not calm; change `--night`, or `--sensors` the targets that carry the cycle. Camera drifting all night: a short night just before the morning (`--night 3-5`: the level of the rest that precedes the start). Noisy series or isolated points: `--smoothing 5`. Threshold in noises that does not bite (never exceeded, or exceeded all day): `--fraction 0.3`, then read the sequence around the extreme, not the first and the last exceedance. A \"1 measurements\" line is a peak, not a cycle.\n\n### metrics\n\n```\n.venv/bin/python tools/scripts/metrics.py [--names A,B] [--step 1h] [--stat median|min|max] [--against temperature] [--smoothing 24h] [--metrics-only] [--start T] [--end T] [--out D]\n```\n\nThe system metrics of `metrics/` (one value per hour), never the identifiers (`SIM_CCID`, `ip*`):\n- the available metrics with their number of values over the window (\"empty\": none; all empty is an absent datum, not a stable temperature);\n- a table per `--step`: `temperature` (median of the `sensor_*_deg_c` components, the one the detectors read), each metric of `--names` (default: the `*_deg_c` and `BusVoltage`), then, unless `--metrics-only`, `tgt_corr_x`, `tgt_corr_y` (median over the targets of `corr` minus each target's own level, accepted measurements) and the raw camera pose (`cam_pan` … `cam_sigma0`); an empty cell is skipped, a text metric (`link`, `BatteryState`, `last_sync`) is returned as it is. `--step 1d --stat min` (or `max`): the minimum or the maximum of each day;\n- per column: filled steps, min and max with their instant; the correlation r and the slope of each column on `--against` (with `--smoothing 24h`, on its rolling mean, column `_smooth`: for a station where the temperature varies little and fast, indoors); the dated runs of steps without any metric;\n- a PNG: temperatures on one panel (median in black), each other metric on its own, then `tgt_corr_x`, `tgt_corr_y` and the pose, line cut on a gap.\n\nAn r does not say a cause: say it as a value, with the window where it is computed.\n\n### stations\n\n```\n.venv/bin/python tools/scripts/stations.py [...] [--columns temperature,cam_tilt,cam_rotation,cam_scale,tgt_corr_x,tgt_corr_y] [--step 1h] [--stat median|min|max] [--table T1/T2|no] [--start T] [--end T] [--out D]\n```\n\n**Several stations on the same timeline** (neighbouring stations, same building). Columns: `temperature` (as in `metrics.py`), `cam_pan` … `cam_sigma0` (raw pose), `tgt_corr_x`, `tgt_corr_y` (as in `metrics.py`), `rej_targets`, `rej_refs` (number of rejected targets, of rejected references, the largest of the step).\n- Prints per station the period, the cadence and the number of instants; the **gaps**: the runs of steps without measurement or without temperature, with the stations where they are missing (a gap common to several stations on a single line); the table by step (one `STATION:column` column each, tabs; `--table` as in `overview.py`); per column and per pair of stations, r of the values and r of the steps from one value to the next (a common movement shows on the steps, a common trend on the values), with n.\n- PNG **stations**: a panel per column, a line per station (raw temperature, the rest minus its median), and a band per station of the steps without measurement.\n- Take `--step` equal to the slowest cadence of the stations; over a month at `1h`, first `--table no`.\n\n### quality\n\n```\npython3 tools/scripts/quality.py [--calm T1/T2,T3/T4] [--common] [--table M] [--step 15min] [--threshold 0.5] [--sensors A,B] [--start T] [--end T]\n... --labels F [--numbers 3,7] [--margin 60] [--edges]\n... --labels F --outside [--min 1] [--except \"Thermal displacement\"]\n.venv/bin/python tools/scripts/quality.py --figure [--metrics flux,snr,dominance] [--labels F] [--zone T1/T2 ...] [--out D]\npython3 tools/scripts/quality.py --self-test\n```\n\nThe six **image quality metrics** (`peak`, `flux`, `sharpness`, `fwhm`, `dominance`, `snr`; definitions: `tools/DATA.md`), on the stations that have them (otherwise: \"No quality metrics\", and nothing else). Each measurement becomes a **ratio** to the **calm reference** of its sensor: the median of the metric over its measurements in the `--calm` windows, at the same UTC hour of the day (without `--calm`: the whole folder); 1 = like the reference, < 1 lower, > 1 higher; for `fwhm` and `dominance`, the rise says a degraded image; rejected measurements included.\n- Without options: the folder's maximal `peak`, then per sensor (`r` = reference) the rejected measurements, `pk/max` (median peak over the window divided by this maximum: at 1, the spot touches the image ceiling, its `peak` no longer moves and its `sharpness` follows the exposure: read `flux`, `snr` instead), and for each metric the median ratio and the extreme with its instant; then the median of the targets and of the references.\n- `--common`: per step, the median of the ratios of the targets / of the references for each metric (what affects the whole scene, visibility or turbulence; `--step 1d` shows on one screen on which days the reference holds).\n- `--table M`: per step, the ratio of `M` of each sensor (`*`: a rejected measurement), their median and how many pass `--threshold` (below, or above 1/`--threshold` for `fwhm`, `dominance`): a target that goes out and comes back; on a moment, `--table flux --sensors …` says which targets are hidden (flux cut) or veiled, from which instant to which instant: write them by their name.\n- `--labels F` (one JSON per line, `start`, `end`, `family`): per numbered label, the median ratio of the targets and of the references over the hour before, the range and the hour after (`tgt 0.96|0.26|0.79`, `--margin` minutes), then the sensors **affected** over the range (flux or snr below `--threshold`, or dominance above 1/`--threshold`), with their worst flux, from lowest to highest. `--edges`: per instant of the widened range, the number of affected sensors and the median of the targets of flux, snr, dominance (`<` within the range), to date the first and the last degraded instant.\n- `--outside`: the runs of instants that no label covers (outside `--except` families) where at least `--min` sensors are affected, with the sensors and their worst flux: candidates for forgotten labels, to check on `corr_x`, `corr_y`.\n- `--figure` (instead of the tables): PNG **quality-common** (a panel per metric, log scale: median of the targets in black, of the references in red, grey band from the 10th to the 90th percentile of the targets: a disturbance of the whole scene moves the median, an occultation of a few targets only the bottom of the band) and a PNG **quality-** per `--metrics` (a small chart per sensor, references in red); `--labels` greys each label in one colour per family, `--zone` ranges.\n\nReading: the metrics say **why** a measurement degrades, where `error_value` says only that it degrades; they prove a cause and name the affected targets. What they showed on LENZSPITZE (to be confirmed on each station): `flux` cut (close to 0) on a group of targets, the others intact, for one to a few measurements: these targets are hidden (the list is read on the flux each time, not on the usual list; a hidden target can stay under its error threshold, and its point is wrong); `flux` down over the whole scene, stronger on the distant targets: reduced visibility; `sharpness` down and `dominance` up, `flux` whole: the image shakes (turbulence); nothing moves: neither the image nor the view, to be looked for in the movement. A whole flux refutes an occultation. `fwhm`, truncated to the disc, moves little; on a spot at the ceiling (`pk/max` at 1), it goes down when the spot darkens.\n\n**The calm reference decides everything**: take `--calm` on calm hours of the **same image regime** as the range read. When the lighting or the exposure changes (after a gap, an intervention), a reference on the other side skews the ratios by a factor of two or three: `--common --step 1d` over the batch shows this change (medians of the targets and of the references far from 1 for whole days, then at 1); then take a reference on each side and read each side with its own. Calm days are often days of thermal cycle: a reading of the thermal against them is circular.\n\n### thumbnails\n\n```\n.venv/bin/python tools/scripts/thumbnails.py --sensors A,B --times T1,T2 [--radius 100] [--contrast [MIN,","stderr":"","interrupted":false,"isImage":false,"noOutputExpected":false,"persistedOutputPath":"/home/maxime/.claude/projects/-home-maxime-aimsight-app/b1dece15-7ed2-440e-993c-de42f2e6a4bf/tool-results/bbi9zey7i.txt","persistedOutputSize":71645},"tool_result_meta":[{"id":"toolu_013TnQF76LTA6ACbWGHsBgqa","permission_decision":{"decision":"accept","source":"config","reason_type":"rule"}}]}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98moiGVLeyFXtHKAJ8f","type":"message","role":"assistant","content":[{"type":"tool_use","id":"toolu_0191FceTDQJ7KggDrXEiXodt","name":"Bash","input":{"command":"cd /home/maxime/aimsight-app; cat labeling/families.md labeling/reading-rules.md labeling/stations.md","description":"Read families, reading rules, stations"},"caller":{"type":"direct"}}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":1698,"cache_read_input_tokens":9938,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":1698},"output_tokens":21,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"b7c8dfd6-87b2-47b6-a0d2-7f15800443ba","timestamp":"2026-11-17T20:31:03.854Z","request_id":"req_011Ch98moXrDRw3CYGGV9ZtA","wire_tool_inputs":{"toolu_0191FceTDQJ7KggDrXEiXodt":{"command":"cd /home/maxime/aimsight-app; cat labeling/families.md labeling/reading-rules.md labeling/stations.md","description":"Read families, reading rules, stations"}}}
-{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_0191FceTDQJ7KggDrXEiXodt","type":"tool_result","content":"\nOutput too large (30.5KB). Full output saved to: /home/maxime/.claude/projects/-home-maxime-aimsight-app/b1dece15-7ed2-440e-993c-de42f2e6a4bf/tool-results/bi79iapup.txt\n\nPreview (first 2KB):\n# The label families\n\nOne 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.\n\n| Key | Detector | What happens | For the client |\n|---|---|---|---|\n| `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 |\n| `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 |\n| `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 |\n| `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 |\n...\n","is_error":false}]},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"f598dcfc-639e-49a5-92a7-67e99562f2fa","timestamp":"2026-11-17T20:31:03.917Z","tool_use_result":{"stdout":"# The label families\n\nOne 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.\n\n| Key | Detector | What happens | For the client |\n|---|---|---|---|\n| `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 |\n| `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 |\n| `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 |\n| `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 |\n| `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 |\n| `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 |\n\nFor 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:\n\n| Variety | For the client |\n|---|---|\n| `Poor visibility reduced` | use the data over the range with care: they are less precise |\n| `Heat shimmer` | nothing to do: the small fast wiggles are not movement |\n| `Camera thermal movement` | nothing to do: this is not a movement of the structure |\n| `Brief obstruction` | ignore this single point on the curves |\n| `Sudden jump, back to normal` | look at the images: the cause is not established |\n| `Lasting shift` | check whether the structure moved: look at the images |\n| `Jump, not back yet` | check whether the structure moved: look at the images |\n| `Slow drift` | keep watching it |\n\n## The boundaries\n\n- **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.\n- **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.\n- **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 Displacement without a cause. The description says it is a reference, and that the targets move together because of it.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **Target issue or Displacement**: a changed configuration (moved sensors, changed starting position, setting) is Target issue; the jump that results is not a Displacement.\n\n## The phenomena\n\nWhat has been labelled so far, one line each: **name**: what is seen; how to tell it from its neighbours. The hypotheses to weigh for a moment of a range; the cases, their bounds and descriptions come from the labels, through `precedents.py`. A phenomenon not in this list is labelled too, without forcing a cause.\n\n### No data\n- **A gap common to several stations**: the measurements missing at the same minutes on every station measuring then; a cause outside the stations, not established. Read the other stations before the station's metrics.\n- **The station runs, the measurement is missing**: one station, powered and communicating (synchronization, image or `DB_not_uploaded` at the missing instant), misses a measurement.\n- **The station goes silent on its own, for a long time**: no measurements, no images, no metrics, for hours or days, without the signature of a lack of energy.\n- **The station shuts down for lack of energy**: the battery does not last the night; voltage below the knee before the gap, a restart with the solar charge.\n- **Mains cut: the station runs on its battery**: a station on mains stops, or comes back on a drawn-down battery, until the mains return.\n\n### Obstruction\n- **A pass-by hides the targets for the length of one measurement**: a train, a vehicle, passers-by: the hidden targets rejected for one acquisition, back at the next; a reference behind it makes the whole base jump. Insects give the same signature: only the image tells.\n- **A target left under the threshold latches onto a headlight, a reflection or another spot**: during a pass-by, one false point kept in the curve, without rejection; `dominance` rises on a recent camera.\n- **A vehicle or machine that stays in front of the targets**: the same sensors hidden for hours or days, sometimes a reference; one label per parking.\n- **An animal very close to the lens**: lit at night, it hides part or all of the scene for one or two measurements; a spider is not its web.\n- **A plant shaken by the wind in front of a target**: one target, at times, on windy days; it grows over weeks.\n- **An obstacle covers part of the spot**: an obstacle, or a mark on the glass in front of one spot, hides part of it for hours or weeks: the measured centre slides; the sliding is the artifact, the jump back is the return to normal.\n\n### Visibility\n- **Rain**: drops in front of the lens veil the spots during the hours of rain, at night above all; the references, higher up, may suffer less.\n- **The soiled glass**: after rain, drop marks veil part of the scene durably; under a single spot, it is an obstacle (Obstruction).\n- **Visibility drops over the whole scene, without an obstacle**: fog, condensation, a milky dawn: flux down on all sensors, `error_value` up, rejections; raw positions without a step.\n- **Part of the scene goes dark at night**: the distant spots, or a few neighbours at the edge of the group, lose their light, nothing in front.\n- **A reference loses its brightness, without an obstacle**: one or two references weaken and shrink, most often at night, then come back on their own; the centre does not move.\n- **Atmospheric turbulence**: by day, air heated above a road, ballast or rails makes the spots tremble: a fast noise, `error_value` up. Without the `error_value` rising, an agitation of the pose is the camera heating (Thermal displacement).\n- **The sun in the field or behind a spot**: the sun enters the field, or lights the background of a target or a reference as bright as it: rejections at the same hours on sunny days only.\n- **A faint spot lost when the light is missing**: a faint target crosses its threshold at the change from night to day, under an overcast sky or in a noisy night image; its rejections come with the light, not every day (else Target issue).\n\n### Target issue\n- **A target rejected at all its measurements**: never accepted, whatever the weather.\n- **A target right at the threshold, the whole batch**: its `error_value` keeps crossing the threshold, with many own rejections.\n- **A target rejected every night or every day**: under the station's ordinary regime (floodlight, daylight), at the same hours, whatever the weather.\n- **A target that degrades, and sometimes recovers**: seen worse and worse from a date on; back only after weeks, if ever, often at another level.\n- **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.\n\n### Thermal displacement\n- **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.\n- **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.\n- **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.\n- **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).\n\n### Displacement\n- **A step of the camera that the compensation does not erase**: the camera moves at once and a remainder passes into the curves; a step that leaves nothing beyond the noise is not labelled.\n- **The camera tilts little by little**: over weeks, the tilt rises and the compensation corrects some targets better than others; the targets do not move relative to each other.\n- **The base changes without a reference lost**: all references kept, the distance between them changes a little; all targets shift together without moving in the image.\n- **A real movement of the structure**: targets shift and stay, with references and pose stable and a good image; if the camera and references moved too, the amplitude is not established.\n- **Targets move slowly, alone, then come back**: one or a few targets, hours or days, without a camera movement or an obstructed view.\n- **A target or a small group jumps and stays shifted**: at once, to another level, without the camera moving or a visible cause.\n- **A step taken during a measurement outage**: on resumption, targets do not find their previous level.\n\n### Family of the cause\n- **A reference dropped: the base changes**: one reference above its threshold, dropped: all targets jump together, the reprojection error at zero; the family is that of what hindered the reference.\n- **Two references lost: the camera is blind**: two of three references dropped one after the other: every point of the range is invalid; the family of the cause.\n- **A compensation on two references**: a station built with two, or having lost one for good: the slightest difference between them passes into all the targets; the family of what disturbs them.\n- **A spider web in front of the lens**: Visibility when it veils the image, Obstruction when a thread hides a few spots; no signal at all is possible, only the images show it.\n\n## What is not labeled\n\n- 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.\n- 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.\n- 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).\n- The expert can say so with the key `None` (labeling tool: \"None (curves untouched)\"): such a label is not counted.\n# Reading rules\n\nWhat the data of a station mean: where each cause enters the measurement, what it touches, and the rules and false friends that the expert and the reviewed labels have established. What the files and columns are: `tools/DATA.md`. How to place a label: `labeling-rules.md`; the families and their boundaries: `families.md`, whose rules are not repeated here.\n\nCases are cited by label id (`NORDEND-80`, in `auto/.jsonl`; `precedents.py` finds others); `[expert]`: the expert's word, from a label that is not in `auto/`. Maintained by hand.\n\n## 1. How a measurement is made\n\n1. **The scene**: targets on the structure, references around it, assumed fixed.\n2. **The view**: the air between the camera and the targets, and what can pass or settle in front.\n3. **The image**: the lens, then the capture (IRON, or DIFF which combines several captures).\n4. **The pattern measurement**: each sensor is found in the image: `x`, `y`, `error_value`; on recent cameras, the image quality. Above `error_threshold`, the measurement is rejected.\n5. **The compensation**: a 2D similarity (translation, rotation, scale) fitted on the references (`global_ref`) gives the camera pose (`pan`, `tilt`, `rotation`, `scale`, `sigma0`) and, per reference, `reproj_err` and `inlier`.\n6. **The corrected curve**: `corr_x`, `corr_y`, the position of the target once the estimated camera movement is removed.\n\nA displayed value is the end of this chain: find the stage that gave way.\n\n## 2. Where each cause enters, and what it touches\n\n| Stage | Cause | What it touches | Time | Witnesses |\n|---|---|---|---|---|\n| View (air) | fog, rain, condensation: **reduced visibility** | a homogeneous drop in flux; `error_value` rises, rejections; raw positions without a step | hours | quality (`flux`), images |\n| View (air) | **heat haze** (turbulence) | a fast noise; only when the structure really heats up; not under a bridge | the hot hours | temperature, `error_value` by day versus night |\n| View (obstacle) | object, leaves, snow on a target: **occultation**; a passage | one or a few targets; on a recent camera, their flux cut, the neighbours intact (LENZSPITZE-9); a passage: one measurement | from one measurement to weeks | quality, images |\n| Target | problem target (badly oriented, dirty, glued) | one target, lastingly | days and more | `error_value` of the target alone |\n| Lens | **thermal deformation of the optics** (sun on the station) | the whole image deforms, which a similarity cannot represent | short: follows the sun on the station | housing temperature |\n| Camera and mount | **expansion of the mount**; wind, jolt, shock | raw positions of all sensors, references included, together; the compensation absorbs it (`corr` flat) or badly: `corr` follows the inflections of the camera movement | specific to the mount | camera pose, housing temperature |\n| References | **reference hidden or less well seen** | the transformation is redone without it: points shifted at once, often grouped in one part of the image, the shift growing with the distance to the references; back when it returns: reversible | the time of the nuisance | `error_value`, `reproj_err` of the references, `sigma0`, camera pose |\n| References | a reference moved | the `corr` of the targets shifted lastingly | lasting | `reproj_err` of the reference |\n| Structure | **thermal expansion of the structure** | `corr`, an amplitude specific to each target, references stable | the longest: slow heating, late cooling | no air temperature (section 3) |\n| Structure | real movement | `corr` of one or several targets, which lasts; references and pose stable, good image quality | lasting | all of the above, at calm |\n\n**A jump that returns** to normal is not serious: the return is what makes it benign. Saying \"jump\" is not enough; the question is its cause, quite often a reference hidden or less well seen.\n\n## 3. Thermal effects\n\n- **Three movement effects**: the lens, the mount, the structure, told apart by their heating and cooling times; the structure is the slowest. Heat haze is apart: a noise, not a movement.\n- **The cases cross**: a camera on a bridge has two structures, the one that carries it (the mount) and the one it monitors.\n- **In waves**: expansion, then contraction; often stronger in Y than in X, depending on the orientation.\n- **The kind of structure says whether a thermal movement is possible**: a bridge yes; a rock face, too massive, or a road, no: the movement is then that of the camera (`stations.md`). [expert, WILDSTRUBEL-102]\n- **The camera can move through a thermal effect at a different rhythm from the structure**, not having the same heating time. [expert]\n- **The temperature that counts is that of the camera housing, not that of the air around**, even sheltered. The temperatures available are those of the compute board (`sensor_*_deg_c`), inside the housing, heated by the sun and by the computing, as hourly means: a witness for the lens and the mount, not for the structure nor the air. `temperature_deg_c`, on a few stations: unknown sensor. [expert, BREITHORN-14]\n- **A change of regime is understood through the temperature**: look at it. [expert]\n- **The direction of a thermal movement is read on the housing temperature, not on the hour**; when the scale of the camera follows it, the effect is on the camera. [NORDEND-155, CLARIDEN-13]\n\n## 4. Gaps\n\n- **A gap is not necessarily an outage**: acquisition, transmission, ingestion and display are distinct layers.\n - At the end of a file, empty values can be only a synchronization delay (`last_sync`): a delay only if the other stations do not have their data yet either.\n - At the start of a file, empty values precede the first measurement: not an outage.\n - A gap surrounded by a normal voltage is not an energy problem.\n- **A gap is read with the other stations and the metrics** (the boundary \"A gap\" of `families.md`). [JUNGFRAU-52, NORDEND-50, WILDSTRUBEL-201, CLARIDEN-19]\n- **A power cut leaves a signature**: the voltage below the knee (about 12.8 V) just before or just after the gap; the temperature drops during the gap more than at the same hours on nights without a gap, which alone does not settle it (a common gap can do the same, an outage that comes back after sunrise shows nothing).\n- **A station on mains that comes back with its battery drawn down has lost the mains.**\n- **A `NaN` or `inf` value** in an export is an absence of measurement.\n\n## 5. Reading rules\n\n- **What moves in the image is read before the cause, on the raw positions against the overall movement** (`overview.py --rigid`): the targets do not move relative to each other, it is the camera [BREITHORN-2]; targets move alone, a movement is not excluded [CLARIDEN-14]; nothing moves and the curves jump, it is the base or the configuration [WILDSTRUBEL-136, CLARIDEN-38].\n- **A jump is judged against the neighbours**: if it brings the target back toward them, it is a return to normal, and the artifact was before; if it takes it away from them, it is to be treated quite differently. [expert]\n- **A level is also judged against the past of the target, over weeks**: a jump that brings it back to an old level is a return. [NORDEND-94, NORDEND-169]\n- **A high `error_value` is not a problem in itself: its variations count.** [expert]\n- **A very stable `error_value` says the targets stay well visible**: while they move, it rather suggests a poor compensation than an obstruction of the view. [expert]\n- **A rejected measurement is removed from the display, not a measurement just under the threshold**: a target left under the threshold keeps its jump. [expert, NIEDERHORN-13]\n- **At least three references are needed; dropping a single one is enough to distort everything**: a kind of triangulation. **The position of the targets rests on the network of references**: references badly seen, targets badly anchored. [expert]\n- **The reprojection error says how many references hold**: at zero, only two remain, a very bad sign, not a perfect measurement; absent, only one, and no measurement is possible. Except on a station built with two references, where it is always at zero. [JUNGFRAU-22, FLORIDA-4, expert]\n- **The pose of the camera is reliable only if the references hold**: a reference rejected, dropped or sliding against the targets distorts it; a single hindered target does not. [FLORIDA-58]\n- **A drift specific to a few targets that follows the camera, on the same dates, is the scene deforming with it**, not a second movement; it is separate only if it has its own dates. [NEBRASKA-6, NEBRASKA-5]\n- **Neighbouring cameras are read together**: the same movement, the same loss or the same gap on the cameras of one building have a common cause; what touches only one is on its line of sight. [MICHIGAN-3, BREITHORN-20]\n\n## 6. False friends\n\n- **Jumps of many targets, all in the same direction, are not a movement** when they fall at the reference switches: raw positions without a step, daily cycle that continues. [expert]\n- **A target that slides slowly away from its neighbours is not moving** when its `error_value` rises with the sliding and a step brings it back toward them. [expert]\n- **A rise over several days is not necessarily a real movement**: it may follow a lasting drop in temperature. [expert]\n- **Corrections stuck at zero are not a failure**: a twin of a reference. [expert]\n- **No signal does not mean no obstruction**: only the images show the web. [expert]\n- **A web is not the spider**: the web veils in part for hours or days; the spider hides everything for the length of one measurement. [expert]\n- **References that do not move in the rain do not contradict the rain**: higher up, they suffer it less. [NIEDERHORN-12]\n- **The step of a real movement is not its amplitude** when the camera and the references have moved too. [expert]\n- **A swarm of insects is not a train**: same signature; only the image tells them apart. [NIEDERHORN-66]\n- **In a tunnel, a temperature drop at the same moment does not make a thermal effect**: the bump of a group comes with the `error_value` and returns before the scale of the camera. [CLARIDEN-12, CLARIDEN-13]\n- **The return of the `error_value` is not the end of an obstruction**: after a mark on the glass, the curves stay shifted. [NORDEND-169]\n- **A spot on a thumbnail that follows the measurement is not necessarily there**: the frame follows a measurement perhaps latched onto the neighbour; only a fixed frame shows it. [FLORIDA-43]\n\n## 7. Non-negotiable rules\n\n- Judge nothing on a binary `inlier`: use continuous weights, residuals, influence.\n- Neither `sigma0` alone nor the number of references is ever a sufficient criterion.\n- The image quality of a target is not the quality of the reference network; a small residual is not a well-constrained transformation.\n- A common-mode movement is not a structural movement; coherent references are not physically fixed references: the camera cannot prove that a network moving as a block is fixed.\n\n## 8. Lessons from cases outside the labels\n\n- **When everything moves together, the measurements alone do not separate the structure from the camera** (Barcelona, a bridge whose vault subsided: the references, the camera and the structure moved; the expert called it a real movement, confirmed by other monitoring systems of the site). An unstable compensation then distorts the amplitude of a real movement: the movement is reported, its amplitude is not established. [expert]\n- **Two prisms too close interfere**: a 24 h cycle correlated between the two, or isolated peaks on one target at a time, too large for the structure, with no obstruction on the images; a neighbour much brighter than the others. On a recent camera, `dominance` shows it. [client report]\n- **Vegetation grows over days and weeks**: a partial, progressive occultation, not reversible from one measurement to the next like a passage; the hardest obstruction according to the expert. [client report]\n- **References masked (two of four, by vegetation)**: a 24 h cycle on pan, roll and tilt, badly compensated, is then not a movement of the camera but a base too weak for the transformation. [client report]\n- **A target of low contrast**: by day, square waves on one axis, back at night, `error_value` rising by day without reaching the threshold. [client report]\n- **Snow**: noise and apparent movements on all sensors and the camera, a brief loss of data, the signal quickly back. [client report]\n# The stations\n\nWhat each station is: its structure, its camera, its references, its neighbours. Context for reading a station's data, not a rule: what happens at a station is in its labels (`auto/.jsonl`, `precedents.py`). The kind of structure says whether a thermal movement of the structure is possible (`reading-rules.md`, section 3). Cases are cited by label id; `[expert]`: the expert's word. Maintained by hand: a new station gets its row when its first range is analysed.\n\n| Station | Structure | Camera | References | Neighbouring cameras |\n|---|---|---|---|---|\n| BREITHORN | in a building (a factory, indoors) [expert] | one measurement every four hours; COLJ19 and POUI19 much closer to the camera than the other targets [expert]; the camera nods forward over October, compensation incomplete [expert] | REFH22, REFPOU22 among the sensors at the bottom of the image | MICHIGAN and NEBRASKA, in the same building: a drift common to the three [BREITHORN-2] |\n| CLARIDEN | a tunnel under construction, with other measurement systems [expert] | images always dark; on mains | four references, D-302-C, PR-291, PR-293, PR-295; PR-284 is a local reference, read as a target; D-302-B and PR_BG on the same prism [CLARIDEN-38] | — |\n| FLORIDA | — | — | two references only, p1_r and r1_r, each with its twin target (Sellette 3, Pont Ernen) [expert] | its one-measurement gaps at night fall at the same instants as SNCF01's |\n| JUNGFRAU | a bridge, which rises as it cools [expert] | under the deck, fixed to the bridge | three references off the bridge, REF_D, REF_G, REF_CT | — |\n| LENZSPITZE | a railway seen from under a bridge, a work site and machines next to it | recent camera, with image quality; `x`, `y` relative in the export (`tools/DATA.md`); only `temperature_deg_c` is filled | nine references, i","stderr":"","interrupted":false,"isImage":false,"noOutputExpected":false,"persistedOutputPath":"/home/maxime/.claude/projects/-home-maxime-aimsight-app/b1dece15-7ed2-440e-993c-de42f2e6a4bf/tool-results/bi79iapup.txt","persistedOutputSize":31201},"tool_result_meta":[{"id":"toolu_0191FceTDQJ7KggDrXEiXodt","permission_decision":{"decision":"accept","source":"config","reason_type":"rule"}}]}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98n1nnueGR4pjfB2gt2","type":"message","role":"assistant","content":[{"type":"tool_use","id":"toolu_017RJJ3rkQYvkbaXq518356P","name":"Read","input":{"file_path":"/home/maxime/.claude/projects/-home-maxime-aimsight-app/b1dece15-7ed2-440e-993c-de42f2e6a4bf/tool-results/bbi9zey7i.txt"},"caller":{"type":"direct"}}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":1886,"cache_read_input_tokens":11636,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":1886},"output_tokens":16,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"d2062a24-4141-4cd2-869a-d474b4bce071","timestamp":"2026-11-17T20:31:06.300Z","request_id":"req_011Ch98n1ZuGw3Ugyh4DMV2R","wire_tool_inputs":{"toolu_017RJJ3rkQYvkbaXq518356P":{"file_path":"/home/maxime/.claude/projects/-home-maxime-aimsight-app/b1dece15-7ed2-440e-993c-de42f2e6a4bf/tool-results/bbi9zey7i.txt"}}}
-{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_017RJJ3rkQYvkbaXq518356P","type":"tool_result","content":"1\t# Reading the data\n2\t\n3\tThe guide to the reading harness: followed by the analyst; improved by the upgrader (agents repository), run by Optimizer's `optimize` skill, the only one that writes here.\n4\t\n5\tA camera tracks targets (reflectors) fixed on a structure; its own movement is compensated thanks to reference targets, assumed fixed. This movement, the **camera pose** (`pan`, `tilt`, `rotation` in degrees, `scale`, `sigma0` of the registration, in `camera/`), is read before the sensors: it explains a large part of what moves on the curves (D-073). This guide says how to read a station's data: what the curves and the images show, moment by moment. It does not say what they mean: family, known event, hypothesis and verdict are the business of whoever calls you.\n6\t\n7\t## Read first\n8\t\n9\t- `tools/DATA.md`: the files of a station and the meaning of each column, the image quality metrics, the camera images (**first**);\n10\t- `labeling/reading-rules.md`: what the data mean (the measurement chain, gaps, reading rules, false friends).\n11\t\n12\t## The tools\n13\t\n14\tRun them from the root of the calling repository, where `tools/`, `data/` and `labeling/` are links. They return values, never verdicts: you judge. `--out `: where whoever calls you stores your figures; they give it to you. The method (below) says in which order to run them; each section says what a tool returns and how to read it.\n15\t\n16\t| Tool | The question it answers |\n17\t|---|---|\n18\t| [`inventory.py`](#inventory) | What is there, what is missing: files, contents of each source, images, poses, cadence, sensors, rejections |\n19\t| [`summary.py`](#summary) | The usual level of each sensor, then one column by time step |\n20\t| [`plot.py`](#plot) | The series of chosen sensors and columns, as a PNG |\n21\t| [`overview.py`](#overview) | All the sensors together, against the camera pose: common movement, single sensors, residuals, rigid movement |\n22\t| [`ranges.py`](#ranges) | Dated ranges where each sensor leaves its level, at the native step |\n23\t| [`days.py`](#days) | What comes back from one day to the next: night levels, days superimposed by hour, bounds of each day |\n24\t| [`metrics.py`](#metrics) | The system metrics (temperature, voltage…) against the targets and the pose |\n25\t| [`stations.py`](#stations) | Several stations on the same timeline |\n26\t| [`quality.py`](#quality) | The six image quality metrics against a calm reference; labels; degraded instants no label covers |\n27\t| [`thumbnails.py`](#thumbnails) | Full-resolution thumbnails of the camera images, around sensors or of a zone |\n28\t| [`gif.py`](#gif) | A GIF of the camera images over a range, for a reply to the customer |\n29\t| [`ls … \\| grep`](#whole-image) | The whole camera image at a time |\n30\t\n31\t### inventory\n32\t\n33\t```\n34\tpython3 tools/scripts/inventory.py [--start T] [--end T] [--files]\n35\t```\n36\t\n37\tNames and counts, never values. Over the **whole period**:\n38\t- files by type: beyond 5 per type, the count, the first and the last (`--files`: the full list, only to look for a specific file);\n39\t- **what each source contains** over the window: the columns of the export, of the pose, of `quality/` and of `weather/` (the MeteoSwiss weather, hourly; a station without a Swiss position has none), with the number of rows that have a value (\"empty\" otherwise; an export column that not all sensors carry says how many carry it); the names of the system metrics of `metrics/`; the images and the difference images. The \"Export image quality (peak to snr)\" line says whether the six quality metrics are filled (then `quality.py`) or empty;\n40\t- images by runs of equal gaps between two images (within 5 min, over the window if given): one line per change of gap, a hole is dated by its two images;\n41\t- camera poses (count, period, measurement instants without registration), period, cadence, missing measurements, sensors (reference or target, error threshold, rejected measurements, distance from the camera and mm per px of `targets.csv`). When `pattern_type` is empty, a sensor is a reference if it carries `reproj_err` or `inlier` (the \"pattern_type empty for N sensors\" line says so);\n42\t- \"Duplicate readings\": an export (often named after the customer's project) whose readings are already in the others; with 0 different values, it changes nothing to the reading, otherwise the tools keep the one of the last file in name order.\n43\t\n44\tWith `--start`/`--end` (on a batch: those of the batch), a section for the window: the missing steps, dated (for all the sensors, or which ones are missing); by sensor, the rejected measurements, dated (runs of consecutive steps; rejected: `error_value` above the sensor's threshold, **references included**); then the **number of references retained by the compensation** (`inlier` = 1) at each instant and the dated runs where some are not, which ones and why (`r` rejected, `0` discarded by the compensation, `empty`; another mark is the value of `inlier`, e.g. `-1`). When `inlier` is empty over the window, the retained references are read from the filled `reproj_err` (the title says so).\n45\t\n46\tA run that ends the same day writes only the time of its end. Over a month, the output with `--start`/`--end` exceeds what a call displays: read each section through `grep` (`| grep -A40 '^Retained references'`, `| grep '^ PR04 '`).\n47\t\n48\t### summary\n49\t\n50\t```\n51\tpython3 tools/scripts/summary.py [--column C] [--stat median|min|max] [--step 1h] [--level period|window] [--sensors A,B] [--start T] [--end T] [--instants T1,T2] [--mark]\n52\t```\n53\t\n54\tThe usual level of each sensor (median, MAD, min, max) over the whole period, or over the `--start`/`--end` window with `--level window` (for a batch: a level change within the batch is not compared with weeks of other measurements); then a table by time step, the sensor header repeated every 24 lines.\n55\t- Columns: `error_value`, `corr_x`, `corr_y`, `relative_x`, `relative_y`, `x`, `y`, `sigma0`, `reproj_err`, `corr_x_mm`, `corr_y_mm` (the `corr` in mm, empty without a sure factor: `tools/DATA.md`, \"The targets\"), and the six image quality metrics `peak`, `flux`, `sharpness`, `fwhm`, `dominance`, `snr` (raw values; against a calm reference, `quality.py`).\n56\t- `--mark`: `*` after the value when a measurement of the step is rejected (`x`, `y`, `error_value` of a rejected measurement stay filled), `o` when one has inlier = 0.\n57\t- `--instants T1,T2`: only the steps that contain these instants (the values of all the sensors at a few chosen times).\n58\t- With `--step` equal to the cadence, `--level window --mark`: the per-instant, per-sensor table of one column, one column per run.\n59\t\n60\t### plot\n61\t\n62\t```\n63\t.venv/bin/python tools/scripts/plot.py [--sensors A,B] [--columns C1,C2] [--start T] [--end T] [--zone T1/T2 ...] [--out D]\n64\t```\n65\t\n66\tA PNG of the series, each `--zone` greyed; prints its path. Columns: those of `summary.py`, quality metrics included (raw values).\n67\t\n68\t### overview\n69\t\n70\t```\n71\t.venv/bin/python tools/scripts/overview.py [--columns x,y,sigma0] [--column error_value] [--step 15min] [--k 5] [--min 5] [--residuals corr_x,corr_y,error_value|no] [--outside T1/T2] [--others] [--rigid BASE [--without A,B] [--follow A,B]] [--table T1/T2|no] [--sensors A,B] [--start T] [--end T] [--out D]\n72\t```\n73\t\n74\tAll the sensors together, each against its median and its MAD over the window.\n75\t\n76\tPNGs:\n77\t- **common**: at the top, if the folder has `camera/`, the **camera pose** (raw values, one point per registration, the line cut at measurement instants without registration); the median across sensors of `x`, `y`, `sigma0`, the dispersion across sensors as a grey band; on the `x`, `y` panels, also **each global reference separately** (one line each) and the **median of the targets alone** (black line); at each step, the number of sensors whose `--column` exceeds its median by more than `--k` MAD. Ticks every 1 to 12 h depending on the window, every n days beyond 20 days.\n78\t- **multiples**: a small chart per sensor, one scale each: a step of a single sensor shows there.\n79\t- **residuals-corr_x**, **-corr_y**, **-error_value** (`--residuals`; `no`: none of these PNGs nor their tables): a small chart per sensor of the column minus the sensor's own level (its median over the window; with `--outside T1/T2`, that of the rest of the window, outside the moment read), one scale each, zero dotted: a deviation of a few hundredths on `corr`, hidden in the parallel bands of `plot.py`, shows there.\n80\t- **residuals-…-others** (`--others`): each sensor minus its own median **and minus the median of the other sensors at the same instant**: what all share (the remainder of the compensation of a common movement) cancels, what is specific remains.\n81\t- **rigid** (`--rigid BASE`): at each measurement, the overall movement of the targets since the instant `BASE` (translation, rotation, scale, estimated by medians: a target that jumps alone does not pull it; `--without A,B` removes targets from it) and, for each sensor, the **residual** `dx`, `dy` (raw position minus its position at `BASE` carried by this movement, in px). Panels: `dx`, `dy` of each global reference against the median and the 10th-90th percentile of the targets, `|residual|` of the targets (median, 90th percentile), fitted rotation and scale, `reproj_err` of the references; a rejected reference is a cross (the scale is that of the accepted measurements, a far cross is out of frame).\n82\t\n83\tPrinted:\n84\t- the **common median table**, one line per `--step`: the time, the deviation from the window median of `x`, `y`, `sigma0`, then `x_targets`, `y_targets` (median of the targets alone), then the raw camera pose `cam_pan`, `cam_tilt`, `cam_rotation`, `cam_scale`, `cam_sigma0` (empty without registration); the minimum and the maximum of each column with their instant; then those of `x`, `y` of each global reference (`(rejected)` when the measurement is, with the reference's number of rejected measurements); the measurement instants without pose (dated runs); the instants where at least `--min` sensors exceed together, with their names (`--min 1`: also a single sensor that leaves its level, absent from the default list of 5 sensors);\n85\t- `--residuals`: per sensor, the level, the own noise (median of the differences between two measurements), the min/max deviation per step with their instant, in units and in noises;\n86\t- `--others`: per sensor, the slope and the correlation r of the residual on the common median of `x`, `y`, `sigma0`;\n87\t- `--rigid`: the table by step (`rot_deg`, `scale`, `tx`, `ty`, `tgt_med`, `tgt_max`, `dx`, `dy` of each reference and of each sensor of `--follow A,B`: the step-by-step sequence of a target) and, per sensor, min, max and value at the last instant of `dx`, `dy`. Rejected measurements enter neither the fit, nor the band of the targets, `tgt_med`, `tgt_max`, nor the columns of the table (over several days, parked cars or night rejections no longer drown the rest); the per-sensor summary gives them separately (`; N rejected: min …, max …`, and `(rejected)` after a last value that is rejected).\n88\t\n89\tThe tables by step (common median, `--rigid`) repeat their header every 24 lines; `--table T1/T2` prints them only between T1 and T2 (`no`: not at all), levels, min, max, PNGs and the rest remaining over the whole window: over a one-month batch, first `--table no`, then `--table` on the day of a moment (same levels, which a shorter `--start`/`--end` window would not give). The default step is 15 min, the cadence of the measurements: a one-hour step flattens a peak of one to four steps, dates to the hour and erases an agitation of `x`, `y`; do not widen it to read a batch.\n90\t\n91\tReading, in this order:\n92\t1. **The camera pose first** (top panels, `cam_` columns), dated at the native step: when it rotates (`pan`, `tilt`, `rotation`), changes scale, when its registration degrades (`sigma0`) or is absent (line cut, instants without pose). Each moment of the sensors is read against it: during a movement or a registration gap, or camera still.\n93\t2. **Who moves in the image.** The pose is computed from the global references: a change of pose (or a rise of `sigma0`) is a camera movement only if **the targets also move in the image** (on the `x`, `y` panels, the lines of the references against the black line of the targets alone; `x_targets`, `y_targets`). Only references move, targets still: these references moved, and the pose and the `corr` of all the targets are skewed without raw movement of the targets; say which references and by how much. References and targets together: the camera or the scene; then look whether the `corr` come back.\n94\t3. **Rotation or scale: `--rigid`.** Then the deviation from the median no longer says who moves alone (each sensor deviates according to its place in the image; the rigid residual does not). Before writing \"everything moves together\", rerun with `--rigid BASE`, `BASE` a calm instant before the first movement: a reference whose residual stays far from the 10th-90th percentile of the targets, or a `reproj_err` of the references that does not come back, means the compensation remains skewed by these references and the steps of `corr` partly come from it (say which, by how much, until when); a rising `|residual|` of the targets says they do not move as a block.\n95\t4. **Then `x`, `y`, `sigma0`, before `corr`**: the median of `x`, `y` (raw position, references included), the references one by one, the targets alone and `sigma0` say what moves in the image. Date the start, the end, the return of a movement, or a level that does not come back, on the printed table (time, value), not on the PNG axis. A dip of `corr` after a movement of the raw median is the remainder of the compensation, not a movement of these sensors. The multiples of `error_value` show a lasting step of a sensor, the count the instants where many rise together.\n96\t5. **The residuals, on every batch, without waiting for a suspicion**: a single sensor that rises or falls, a `corr` that drifts by a few hundredths, a step specific to one sensor under a common movement show there; the table says by how much (in noises) and when. On a target whose `corr` goes down under a strong common movement, `--others` separates a remainder of the compensation from a movement of its own: a dip that remains is not a remainder shared by all; a high slope with r close to ±1 on common `y` says it is proportional to the common movement (gain specific to the sensor); without r or slope, it is independent of the movement.\n97\t\n98\t### ranges\n99\t\n100\t```\n101\tpython3 tools/scripts/ranges.py [--columns error_value,corr_x,corr_y] [--k 5] [--merge 1h] [--min-measurements 1] [--outside T1/T2] [--rolling N|DURATION] [--instants N] [--sensors A,B] [--start T] [--end T]\n102\t```\n103\t\n104\tDates the start and the end of a sensor's moment without rerunning ten tables. By column and by sensor, at the measurements (native step, never averaged): level (median of the window), own noise, **largest jump** from one measurement to the next (value, in noises, the two instants; `(rejected: …)` when one end is); then the **ranges** where the sensor deviates from its level by more than `--k` noises: start, end, number of measurements, extreme (signed, in units and in noises) and its instant. Two ranges of the same sign less than `--merge` apart make one; rejected measurements do not cut a range; column `rejected`: how many of the range's measurements are (and `rejected extreme`). A range that touches the edge of the window is dated at the edge.\n105\t- `--outside T1/T2`: level and noise computed outside an episode that skews the window median (the sensor spends half the batch there). Rerun with it around a long episode to date its return to the level: do not conclude \"does not come back\" without having read it.\n106\t- `--min-measurements N`: only the ranges of at least N measurements (and how many out of the total). Over several days, the one-step ranges number in the hundreds and drown the long steps: first `--min-measurements 6`, then without.\n107\t- `--rolling N` (N measurements on each side) or `--rolling 1d` (the measurements within a duration): the level of each measurement is the median of its neighbours, without it; a long drift or a step follows this local level, only the deviations shorter than the window remain (the level column and the noise do not change; with `--outside`, only the noise is computed outside the episode).\n108\t- `--instants N`: at the end, the instants where at least N sensors are out of level on one of the columns, with each sensor and its signed deviation in noises (`cx` corr_x, `cy` corr_y, `ev` error_value), the sensors rejected at that instant (among `--sensors`: removing the always-rejected sensors lightens the list), and each reference: `error_value` (`r` if rejected) / inlier.\n109\t- When the batch has a long drift or several steps (the ranges number in the hundreds, or one half of the batch is \"out of level\"), rerun with `--rolling` (a few measurements, or a few hours to a day depending on the cadence) and `--instants 2`: the brief deviations under the drift come out alone, and the list per instant says which sensors deviate together, which are rejected and what the references do; a deviation of all the targets with the references at the same instant is read against the camera pose.\n110\t\n111\tA noise of `0` (and \"-\" in noises, no range): the values are constant to rounding (deviations below 1e-9), like the `corr` of the references when the compensation retains only two (see Conventions); the same in `overview.py --residuals` and `days.py`.\n112\t\n113\t### days\n114\t\n115\t```\n116\t.venv/bin/python tools/scripts/days.py [--columns corr_x,corr_y,error_value] [--night 20-3] [--k 5] [--days 2] [--step 15min] [--sensors A,B] [--bounds [--smoothing N] [--fraction F]] [--start T] [--end T] [--out D]\n117\t```\n118\t\n119\tWhat comes back from one day to the next, on accepted measurements only. A night: the hours `--night` H1-H2 UTC, straddling midnight, dated from the day it starts; choose hours where the day cycle (`error_value`, camera pose) has subsided (**byhour** figure).\n120\t\n121\t1. **Level of each night**, by sensor and by column: median, MAD, number of measurements, own noise; from one night to the next, the **step** (difference of the medians, in units and in noises) and **where it falls** (\"between A and B\": where the night measurements of the two nights split best between the two levels; B at the start of the following night: the cut falls by day). Read it for any sensor that has already made a step or for which `--outside` is not enough (several levels in the batch): a step of a few noises is dated by its \"between A and B\", a step of `error_value` and one of `corr` at the same instant are linked, a slow drift reads from one night to the next.\n122\t2. **Superimposed days**: PNG **byhour-**, a small chart per sensor, hour of the day on the x axis, one curve per day, each measurement minus the level of the last night started (night greyed, frame from the 1st to the 99th percentile, the title says how many measurements fall outside it). Table: per `--step` slot of the hour of the day, the sensors whose deviation exceeds `--k` noises on the same side at least `--days` days, with the number of days and the median of these deviations. What comes back every day at the same hour, on one or several sensors, groups there, even when it lasts one to three measurements: one moment per hour of the day (say which sensors, how many days out of how many, the amplitude, what the camera pose does at that hour), not one moment per day, nor nothing because each step is short.\n123\t3. **Bounds of each day** (`--bounds`), for what comes back every day and is labelled day by day (thermal cycle, warming and cooling), rather than fixing the same hours for all the days: for the median of the targets of each column (with `--sensors`, the median of these sensors; with one, its own) and for the camera pose (`pan`, `tilt`, `rotation`, `scale`, `sigma0`, if `camera/` exists), the deviation from the level of the night that precedes each day (a day goes from the end of one night to the end of the next). Per day: number of measurements, the first and the last; first and last instant beyond `--k` noises, with the measurement just before and just after, at the native step; signed max and min with their instant; the sequence of measurements beyond `--k` noises around the larger of the two; the following night minus the reference night. A day without measurement says so; a reference night that is not the previous one is named. Each day line starts with the short name of its series (`corr_x`, `pose_tilt`…): `| grep '^pose_tilt '` reads one, `| grep ' 12/10 '` one day. PNG **bounds**: the deviation over the batch, first → last exceedance light grey, sequence around the extreme dark grey, max and min marked.\n124\t - `--smoothing N`: the deviation of each measurement is the median of the N measurements of the day centred on it (noise and `--k` unchanged; PNG: smoothed in blue, raw in grey): an isolated point no longer cuts the sequence around the extreme nor makes a first or a last exceedance.\n125\t - `--fraction F`: the threshold of each day is F times its largest |deviation| (printed on its line, `threshold …`), instead of `--k` noises: when the noise at the native step is unrelated to the amplitude of the cycle (very noisy or very smooth pose).\n126\t - Reading: the sequence around the extreme dates the cycle, the max and the min a go and a return (morning and afternoon); \"before\" and \"after\" give the bounds at the native step (at a cadence of 1 h or 4 h, an event goes from the measurement before to the one after). First exceedance at the start of the day (\"before -\") and last at its end every day: the night is not calm; change `--night`, or `--sensors` the targets that carry the cycle. Camera drifting all night: a short night just before the morning (`--night 3-5`: the level of the rest that precedes the start). Noisy series or isolated points: `--smoothing 5`. Threshold in noises that does not bite (never exceeded, or exceeded all day): `--fraction 0.3`, then read the sequence around the extreme, not the first and the last exceedance. A \"1 measurements\" line is a peak, not a cycle.\n127\t\n128\t### metrics\n129\t\n130\t```\n131\t.venv/bin/python tools/scripts/metrics.py [--names A,B] [--step 1h] [--stat median|min|max] [--against temperature] [--smoothing 24h] [--metrics-only] [--start T] [--end T] [--out D]\n132\t```\n133\t\n134\tThe system metrics of `metrics/` (one value per hour), never the identifiers (`SIM_CCID`, `ip*`):\n135\t- the available metrics with their number of values over the window (\"empty\": none; all empty is an absent datum, not a stable temperature);\n136\t- a table per `--step`: `temperature` (median of the `sensor_*_deg_c` components, the one the detectors read), each metric of `--names` (default: the `*_deg_c` and `BusVoltage`), then, unless `--metrics-only`, `tgt_corr_x`, `tgt_corr_y` (median over the targets of `corr` minus each target's own level, accepted measurements) and the raw camera pose (`cam_pan` … `cam_sigma0`); an empty cell is skipped, a text metric (`link`, `BatteryState`, `last_sync`) is returned as it is. `--step 1d --stat min` (or `max`): the minimum or the maximum of each day;\n137\t- per column: filled steps, min and max with their instant; the correlation r and the slope of each column on `--against` (with `--smoothing 24h`, on its rolling mean, column `_smooth`: for a station where the temperature varies little and fast, indoors); the dated runs of steps without any metric;\n138\t- a PNG: temperatures on one panel (median in black), each other metric on its own, then `tgt_corr_x`, `tgt_corr_y` and the pose, line cut on a gap.\n139\t\n140\tAn r does not say a cause: say it as a value, with the window where it is computed.\n141\t\n142\t### stations\n143\t\n144\t```\n145\t.venv/bin/python tools/scripts/stations.py [...] [--columns temperature,cam_tilt,cam_rotation,cam_scale,tgt_corr_x,tgt_corr_y] [--step 1h] [--stat median|min|max] [--table T1/T2|no] [--start T] [--end T] [--out D]\n146\t```\n147\t\n148\t**Several stations on the same timeline** (neighbouring stations, same building). Columns: `temperature` (as in `metrics.py`), `cam_pan` … `cam_sigma0` (raw pose), `tgt_corr_x`, `tgt_corr_y` (as in `metrics.py`), `rej_targets`, `rej_refs` (number of rejected targets, of rejected references, the largest of the step).\n149\t- Prints per station the period, the cadence and the number of instants; the **gaps**: the runs of steps without measurement or without temperature, with the stations where they are missing (a gap common to several stations on a single line); the table by step (one `STATION:column` column each, tabs; `--table` as in `overview.py`); per column and per pair of stations, r of the values and r of the steps from one value to the next (a common movement shows on the steps, a common trend on the values), with n.\n150\t- PNG **stations**: a panel per column, a line per station (raw temperature, the rest minus its median), and a band per station of the steps without measurement.\n151\t- Take `--step` equal to the slowest cadence of the stations; over a month at `1h`, first `--table no`.\n152\t\n153\t### quality\n154\t\n155\t```\n156\tpython3 tools/scripts/quality.py [--calm T1/T2,T3/T4] [--common] [--table M] [--step 15min] [--threshold 0.5] [--sensors A,B] [--start T] [--end T]\n157\t... --labels F [--numbers 3,7] [--margin 60] [--edges]\n158\t... --labels F --outside [--min 1] [--except \"Thermal displacement\"]\n159\t.venv/bin/python tools/scripts/quality.py --figure [--metrics flux,snr,dominance] [--labels F] [--zone T1/T2 ...] [--out D]\n160\tpython3 tools/scripts/quality.py --self-test\n161\t```\n162\t\n163\tThe six **image quality metrics** (`peak`, `flux`, `sharpness`, `fwhm`, `dominance`, `snr`; definitions: `tools/DATA.md`), on the stations that have them (otherwise: \"No quality metrics\", and nothing else). Each measurement becomes a **ratio** to the **calm reference** of its sensor: the median of the metric over its measurements in the `--calm` windows, at the same UTC hour of the day (without `--calm`: the whole folder); 1 = like the reference, < 1 lower, > 1 higher; for `fwhm` and `dominance`, the rise says a degraded image; rejected measurements included.\n164\t- Without options: the folder's maximal `peak`, then per sensor (`r` = reference) the rejected measurements, `pk/max` (median peak over the window divided by this maximum: at 1, the spot touches the image ceiling, its `peak` no longer moves and its `sharpness` follows the exposure: read `flux`, `snr` instead), and for each metric the median ratio and the extreme with its instant; then the median of the targets and of the references.\n165\t- `--common`: per step, the median of the ratios of the targets / of the references for each metric (what affects the whole scene, visibility or turbulence; `--step 1d` shows on one screen on which days the reference holds).\n166\t- `--table M`: per step, the ratio of `M` of each sensor (`*`: a rejected measurement), their median and how many pass `--threshold` (below, or above 1/`--threshold` for `fwhm`, `dominance`): a target that goes out and comes back; on a moment, `--table flux --sensors …` says which targets are hidden (flux cut) or veiled, from which instant to which instant: write them by their name.\n167\t- `--labels F` (one JSON per line, `start`, `end`, `family`): per numbered label, the median ratio of the targets and of the references over the hour before, the range and the hour after (`tgt 0.96|0.26|0.79`, `--margin` minutes), then the sensors **affected** over the range (flux or snr below `--threshold`, or dominance above 1/`--threshold`), with their worst flux, from lowest to highest. `--edges`: per instant of the widened range, the number of affected sensors and the median of the targets of flux, snr, dominance (`<` within the range), to date the first and the last degraded instant.\n168\t- `--outside`: the runs of instants that no label covers (outside `--except` families) where at least `--min` sensors are affected, with the sensors and their worst flux: candidates for forgotten labels, to check on `corr_x`, `corr_y`.\n169\t- `--figure` (instead of the tables): PNG **quality-common** (a panel per metric, log scale: median of the targets in black, of the references in red, grey band from the 10th to the 90th percentile of the targets: a disturbance of the whole scene moves the median, an occultation of a few targets only the bottom of the band) and a PNG **quality-** per `--metrics` (a small chart per sensor, references in red); `--labels` greys each label in one colour per family, `--zone` ranges.\n170\t\n171\tReading: the metrics say **why** a measurement degrades, where `error_value` says only that it degrades; they prove a cause and name the affected targets. What they showed on LENZSPITZE (to be confirmed on each station): `flux` cut (close to 0) on a group of targets, the others intact, for one to a few measurements: these targets are hidden (the list is read on the flux each time, not on the usual list; a hidden target can stay under its error threshold, and its point is wrong); `flux` down over the whole scene, stronger on the distant targets: reduced visibility; `sharpness` down and `dominance` up, `flux` whole: the image shakes (turbulence); nothing moves: neither the image nor the view, to be looked for in the movement. A whole flux refutes an occultation. `fwhm`, truncated to the disc, moves little; on a spot at the ceiling (`pk/max` at 1), it goes down when the spot darkens.\n172\t\n173\t**The calm reference decides everything**: take `--calm` on calm hours of the **same image regime** as the range read. When the lighting or the exposure changes (after a gap, an intervention), a reference on the other side skews the ratios by a factor of two or three: `--common --step 1d` over the batch shows this change (medians of the targets and of the references far from 1 for whole days, then at 1); then take a reference on each side and read each side with its own. Calm days are often days of thermal cycle: a reading of the thermal against them is circular.\n174\t\n175\t### thumbnails\n176\t\n177\t```\n178\t.venv/bin/python tools/scripts/thumbnails.py --sensors A,B --times T1,T2 [--radius 100] [--contrast [MIN,MAX]] [--fixed] [--zone X,Y,W,H] [--out D]\n179\t```\n180\t\n181\tA sheet of full-resolution thumbnails: one row per sensor, one column per time, centred on the sensor's raw position (`x`, `y`) at each time. Look at it with Read: a whole image read by Read is reduced, a small reflector becomes illegible in it.\n182\t- The centre of the frame is written under each thumbnail: when `x`, `y` jump, the frame moves by as much, and a spot that enters the frame seems to appear; `--fixed` keeps for each sensor the frame of the first time and marks with a red cross the `x`, `y` of each time.\n183\t- Unretouched pixels: the brightness compares from one thumbnail to the next; prints for each thumbnail the background (median), the 99th percentile and the peak (grey levels 0 to 255). Without an image at the requested time, takes the nearest and prints the gap (the actual time is in the title).\n184\t- A faint or deformed spot is invisible as it is: `--contrast MIN,MAX` puts all the thumbnails in grey with the same stretch (without value: from the 1st percentile to the sheet's maximum, crushed by a saturated pixel; then choose MIN,MAX from the printed background and peak, e.g. `10,40`); `--radius 30` to `50` magnifies. Compare the shape and the peak before, during and after an episode, at the same hour of the day.\n185\t- A frame that the image edge cuts is flagged (\"frame cut by the image edge (W × H px)\"): on some stations, `x`, `y` are not pixels (values close to 0) and the frame falls in the corner; then look at the scene through `--zone`.\n186\t- `--zone X,Y,W,H` (pixels of the original image: top left corner, width, height, as in `gif.py`): the same zone at each time, side by side (up to 4 per row), same stretch with `--contrast`; `--sensors` becomes optional, those given are marked with a cross and their name. For the scene around the targets (foreground object, headlights, lighting), prefer it to a large `--radius`.\n187\t- Each thumbnail is rendered pixel for pixel up to 1000 px a side, but Read reduces a wide PNG: with a large `--radius` or a large `--zone`, three or four times per sheet.\n188\t\n189\t### gif\n190\t\n191\t```\n192\t.venv/bin/python tools/scripts/gif.py --start T --end T [--width 720] [--duration 700] [--max 150] [--zone X,Y,W,H] [--out D]\n193\t```\n194\t\n195\tA GIF of the camera images between `--start` and `--end` inclusive, cropped to `--zone` if needed, set to `--width` px, UTC date and time at the bottom right; beyond `--max` images, `--max` at regular intervals; prints the time of each image, then the path and the size of the GIF. To attach the scene to a reply to the customer; Read does not read a GIF: to look, `thumbnails.py --zone`.\n196\t\n197\t### whole image\n198\t\n199\t```\n200\tls /images/ | grep TZ\n201\t```\n202\t\n203\tThen Read on the file found (Read takes no pattern): the whole camera image at that time (UTC), for the scene (occultation, lighting, weather).\n204\t\n205\t## Conventions\n206\t\n207\t- Instants: `2026-01-01T00:00Z`; a time without time zone is read as UTC; `--end` includes the minute given. On a batch, `--start` and `--end` of the batch.\n208\t- Bash is used only to run these tools, `ls`, `grep` and `date`, one command per call, without a `for` loop (a pipe to `grep` is allowed): permissions are granted command by command. If the current directory is not the root of the calling repository, `cd && ` counts as one command. Write no other script. Whoever calls you may add commands to this list.\n209\t- **An output too long for one call** (beyond a few hundred lines, cut at display): shorten it first with the tool's options (`--table no` then `--table T1/T2`, `--min-measurements`, `--sensors`, `--columns`, a shorter window), or read a section of it through a pipe to `grep` (`| grep -A40 '^Title'`, `| grep '^pose_tilt '`). If you have to reread it several times, store it in the output folder in the same call (` > /.txt`) and read that file with Read (`offset`, `limit`) or with `grep`: no `head`, `tail`, `sed`, `cut`. The tools create their output folder themselves: no `mkdir`.\n210\t- A sensor name that carries an apostrophe (`COLH20'''`, `REFP''21`) goes in double quotes in the shell: `--sensors \"COLH20'''\",COLI22`.\n211\t- **Each PNG is looked at with Read**: you read a chart better than a table, and a PNG you have not looked at has shown nothing.\n212\t- A rejected measurement (`error_value` above the threshold) is not a measurement: the station empties the `corr` of a rejected target, but leaves those of a rejected **reference**, often absurd; the tools empty them (`corr`, ranges, residuals, jumps cover only accepted measurements). When the compensation retains only **two references**, their `corr` is 0 (to 1e-13): it passes exactly through them; their noise prints as `0` and their deviations in noises as \"-\"; read nothing into these values, read the references through `x`, `y` (`overview.py --rigid`) and `error_value`. Its `x`, `y` remain: before citing a jump of `x`, `y`, check whether it is marked `(rejected)`; a rejected measurement is not cited as a movement.\n213\t\n214\t## The method\n215\t\n216\t1. **Inventory** (`inventory.py`): what is available, what is missing. A filled column that the tools do not show or a source that no tool reads (`images_diff/`) remains data: know that it exists. The image quality columns (`peak` to `snr`, recent cameras) are read through `quality.py`; `metrics/` through `metrics.py`: a cut of the measurements is read against the steps without metric and the voltage (`--names BusVoltage,BusCurrent,Power,BatteryPercent --metrics-only` on the cut). On a batch, rerun it with the batch's `--start`/`--end`: the absent steps and the rejections of the batch, dated; those of the whole period say nothing about the batch. Read the rejections of the **references** as much as those of the targets: a sensor rejected at the same hours every day makes a moment on its own (say its share of rejected measurements and its hours, day by day); when it is a reference, say with how many references the compensation then runs (the list of retained references). When several targets jump together by one step, or the compensation drops (no pose), look first in that list at which references were lost at that instant.\n217\t2. **Wide first**:\n218\t - `overview.py` on the batch, first (on a batch of more than a few days, `--table no`, then `--table T1/T2` on the days to read), read in the order of its Reading section: the pose, who moves in the image (`--rigid` as soon as the pose rotates or changes scale), `x`, `y`, `sigma0` before `corr`, the residuals on every batch.\n219\t - On a batch of more than two days, then `days.py`, before reading the isolated steps of `ranges.py`: first its **byhour** PNGs and table by slot, then its **night levels**; `days.py --bounds` for what comes back every day and is labelled day by day.\n220\t - Several neighbouring stations given by whoever calls you: `stations.py` (temperatures, poses, `corr` of the targets, common rejections and gaps, at the same hours) before comparing their moments.\n221\t - When the pose or the `corr` of the targets drift over several days, or move without day/night cycle: `metrics.py` on the batch, the temperature against `tgt_corr_x`, `tgt_corr_y` and the pose, on the PNG, then r and the slope.\n222\t - On a station that has the image quality metrics: `quality.py --common --step 1d` on the batch (choice of the calm reference), then `quality.py --figure` with this reference: the median `flux` of the targets and of the references dates the hours of reduced visibility, the grey band that dives alone the occultations; with a labels file, `--labels F --outside`.\n223\t - Then `plot.py` on all the sensors, `error_value` then `corr_x`, `corr_y` (or `relative_x`, `relative_y`), references and targets; `summary.py` on these columns with a wide step (6h or 1d).\n224\t3. **Then zoom**: `summary.py` at 15min (`--stat max` for the real peak of a sensor), and `plot.py` on the windows and the sensors that move.\n225\t4. **Each sensor against its own usual level** (its median and its MAD), never against an absolute threshold; on a batch, the level is computed on the batch (`--level window`, `overview.py`), not on the whole period.\n226\t5. **Each retained moment is dated and measured at the native 15 min step**: start, end and maximum read on the 15 min table (`overview.py` by default, `summary.py --step 15min`), never on an hourly table; also `overview.py --min 1` for single sensors; `ranges.py` on the batch (first `--min-measurements 6`) for, per sensor, start, end, extreme and largest jump at the native step (`--outside` around a long episode, `--rolling` and `--instants 2` under a long drift or several steps); the tables of `x`, `y` on the windows where they stir. On a station that has the quality metrics, for each moment: `quality.py --table flux --sensors …` (or `--labels F --numbers N --edges` on a label): which targets are hidden or veiled, from which instant to which instant.\n227\t6. **The images**: thumbnails (with `--contrast` for a faint target) spaced, one every 2 to 3 h, tighter where the curves move, always with an unaffected witness sensor, at a time before, during and after (at the same hour of the day if possible); when `x`, `y` of a sensor jump between two thumbnails (centre of the frame written under each), rerun with `--fixed` before saying that a spot appears or disappears; the whole image for the scene (occultation, lighting, weather).\n228\t\n229\t## What the reading returns\n230\t\n231\tOne line per moment. A moment: a sensor or a group of sensors that leaves its usual level during a window you can date.\n232\t\n233\t| Start | End | Sensors | Columns | What I see | Images |\n234\t|---|---|---|---|---|---|\n235\t\n236\t- **Sensors**: references or targets, how many, which ones.\n237\t- **What I see**: the shape (one-step peak, step, slow rise, agitation), the amplitude against the usual level (in MAD or in times the median), the return to normal or not, what the other sensors do, **what the camera does** at the same moment (pose moving, by how much, or still; registration absent; \"no `camera/`\" if the folder has none).\n238\t- **Images**: what the thumbnails and the whole image show at that moment, or \"no image\".\n239\t\n240\tTimes in UTC.\n241\t# The data of a station\n242\t\n243\tWhat the files of a station folder are, and what each column means. How to read them with the tools: `GUIDE.md`. What they mean for a label (causes, reading rules, false friends): `labeling/reading-rules.md`. Maintained by hand; `GUIDE.md` is the tool-builder's.\n244\t\n245\t## The displacements: the \"advanced\" export\n246\t\n247\t`displacement/_advanced__.csv`, the source of the analyses: one row per sensor and per measurement, at the native rate of the station (10 or 15 min), `time_utc` in explicit UTC.\n248\t\n249\t| Column | Meaning |\n250\t|---|---|\n251\t| `sensor_name` | the sensor (target or reference) |\n252\t| `pattern_type` | `global_ref`: a reference of the compensation; `ref`: a *local reference*, treated as a target, outside the compensation, without `reproj_err`; empty: a target |\n253\t| `x`, `y` | raw position in the image [px]. Not the centroid of the spot: the offset centroid − (`x`, `y`) is constant per sensor by day and differs between sensors; it changes at night, when the spot is saturated. Probably the position of the reference pattern |\n254\t| `relative_x`, `relative_y` | relative displacement before the camera compensation [px]; not `x − x0` |\n255\t| `corr_x`, `corr_y` | the position of the target once the estimated camera movement is removed: **the curves that are labelled**. In px, not mm (below) |\n256\t| `corr_x_mm`, `corr_y_mm` | `corr_x`, `corr_y` in mm: × the sensor's `mm_per_px` (`targets.csv`, below), computed by `data.load`; empty without a sure factor. The same curves in another unit: the noise threshold of a label is read in noises, whatever the unit; mm say how far a target moves, for the reader |\n257\t| `error_value` | recognition error of the pattern, not an uncertainty |\n258\t| `error_threshold` | specific to each sensor (0.3 to 0.7). Above it, the measurement is rejected: the row and its `error_value` stay, `corr_x` and `corr_y` are empty, not interpolated |\n259\t| `reproj_err`, `inlier` | references only: residual and contribution of each reference in the compensation |\n260\t| `sigma0` | residual of the fit on the references: one value per measurement, repeated on every row |\n261\t| `peak`, `flux`, `sharpness`, `fwhm`, `dominance`, `snr` | image quality of each sensor, recent cameras only (below) |\n262\t\n263\t- \"Rejected\" is a judgment of the AIMsight platform, not of the camera: the camera delivers all its measurements, and a client's platform that integrates the data receives them all.\n264\t- **Unit of `corr_x`, `corr_y`**: px. The hourly export's `horizontal_displacement` (mm) is a factor × the hourly mean of `corr_x` + a constant (likewise `vertical` and `corr_y`, correlation ≥ 0.99); the factor (mm per px) depends on the pattern and on the station.\n265\t- **LENZSPITZE**: its export gives `x`, `y` relative to the pattern; the extraction rewrites them in image px and fills `pattern_type`. Sensors 1023 and 8019 have no pattern: their `x`, `y` are empty. The tools' crosses may sit slightly off the spots there.\n266\t- `inventory.py` says, on a batch, which columns carry values.\n267\t\n268\t## The targets\n269\t\n270\t`targets.csv`, from the pumping: one line per sensor of the platform, `sensor_name`, `pattern_type`, `distance_mm` (from the camera) and `mm_per_px` (`distance_convertion_factor`, the factor of the dashboard's exports in mm), their current values. Read by `data.load_targets`, shown by `inventory.py` (sensor table).\n271\t- The references are not in it yet (pumped from the next pumping on): no distance, no mm for them. They are assumed fixed.\n272\t- `distance_mm` 1000: not filled in on the platform; the line is ignored.\n273\t- A name may have several lines (a target counted twice, an older configuration of the unit, another lens): when they disagree, `data.load_targets` keeps no value (`inventory.py`: `?(n)`) and that target has no mm; the distance stays when the lines agree on it.\n274\t- The distance says which targets are near and far. A far target moves few px for many mm: targets are compared with each other in mm, or in px with their distance. A camera that turns shifts every target by about the same px (the mm grow with the distance); a movement of the structure of the same mm gives px that shrink with the distance; a parallax shows between targets at different distances.\n275\t\n276\t## The camera pose\n277\t\n278\t`camera/_camera_.csv`, from the pumping only: the pose at each registration, `time_utc` in UTC, `median_|min_|max_` of `pan`, `tilt`, `rotation` [deg], `scale`, `sigma0`, one row per measurement (min = max). A measurement instant without a row: the camera was not registered.\n279\t\n280\t- Orders of magnitude: `pan`, `tilt` of a few hundredths of a degree, `scale` within 10⁻³ of 1; some stations show several degrees, not explained.\n281\t- **A positive `tilt` means the camera is nosing down** (the expert).\n282\t- Read by `overview.py` and `inventory.py`.\n283\t\n284\t## The weather\n285\t\n286\t`weather/_weather_.csv`, from the pumping, for a station with a Swiss position only: the hourly measurements of the nearest MeteoSwiss station, `time_utc` in UTC (start of the hour); `position`, `place`, `station`, `station_name`, `distance_km`, `height_m` say where; then `precipitation_mm`, `temperature_c`, `humidity_pct`, `wind_speed_kmh`, `wind_gust_kmh`, `wind_direction_deg`, `pressure_hpa`, `sunshine_min`, `global_radiation_wm2`, `snow_depth_cm` (empty: not measured there). The weather a few km away, not at the camera: what the images show prevails. Read by `data.load_weather`.\n287\t\n288\t## The hourly export\n289\t\n290\t`__to__1hour.csv`: one row per hour, targets only; per target `horizontal_displacement`, `vertical_displacement`, their `_min` / `_max`, `_error` (mean `error_value` of the hour), `_count_val` (measurements of the hour, rejected ones included).\n291\t\n292\t- **`timestamp` has no time zone: Swiss local time** (UTC+2 in summer), at the start of the hour.\n293\t\n294\t## Image quality of a target\n295\t\n296\tSix columns of the advanced export, computed by the GPU of recent cameras on the sensor's window in the DIFF image, in units of that image. Filled only where `inventory.py` says so (\"Export image quality\"); for older cameras, `~/optical_emulator` can recompute them from the DIFF images. \"Disc\": the neighbourhood of the peak, radius `min(H, W)/6` (at least 3 px); \"background\": the rest of the window.\n297\t\n298\t| Metric | Definition | What it measures | Reading |\n299\t|---|---|---|---|\n300\t| `peak` | `max(I)` | the brightness of the return | high, saturation; low, underexposure or missed flash. All targets dropping: the lighting; a single one: that target (fouling, misalignment) |\n301\t| `flux` | flux of the disc minus the background | the light of the target, background removed | reflectivity of the target (fouling, ageing, flash), not ambient light; drops well before `error_value` exceeds its threshold |\n302\t| `sharpness` | `Σ(I²) / (ΣI)²` | concentration of the energy (higher = sharper) | drops: drifting focus, turbulence, degrading target. Independent of the gain, not of the background: follow it over time on one target, do not compare cameras |\n303\t| `fwhm` | width at half height around the peak, background removed [px] | width of the spot | rises: defocus, turbulence, motion blur. Truncated to the disc: under strong defocus it flattens instead of rising |\n304\t| `dominance` | `(second peak − background) / (peak − background)`, 0 (clean) toward 1 (ambiguous) | does a single spot dominate the window? | high: a comparable second reflection, a stray bright point, or the target has gone and something else is the brightest: the correlation can latch onto the wrong pattern, which `error_value` does not see. One hot pixel outside the disc is enough |\n305\t| `snr` | `(peak − background) / bg_sigma` | the signal above the background noise | low: marginal return, even when `peak` looks normal. Independent of exposure and gain. The emulator marks `empty` below 8 |\n306\t\n307\t`peak` and `flux` give the brightness, `sharpness` and `fwhm` the sharpness, `dominance` and `snr` the validity: together they say **why** a measurement degrades, where `error_value` only says that it does. They describe the image of **one target**, not the health of the reference network.\n308\t\n309\t## Camera images: IRON and DIFF\n310\t\n311\t- **IRON** (`images/`): the ordinary image of the scene, JPG. The cause of an event is seen on it (condensation, rain, train, snow).\n312\t- **DIFF** (`images_diff/`): several captures combined to raise the contrast of the reflectors; **the image the displacement algorithms measure**, by default. Not a difference between two instants. 16-bit PNG.\n313\t- Acquisition modes (station manual): \"Single with infrared light\", one image per measurement; \"Differential\", several combined (`Stacking` 20 to 40 when light is difficult); option \"Work on IRON images\", to follow a texture without reflector.\n314\t- Not every station has DIFF images; the pumping keeps about one image per hour. The tools look only at IRON images; `inventory.py` counts the DIFF ones, which your own scripts may read. What is very close to the lens (a web) may stand out better on DIFF.\n315\t# The labeling rules\n316\t\n317\tHow to place a label: the only source of these rules for the aimsight-app `analyst` (before it, the Support-Agent `etiqueteur`) and for those who review their labels. The families, their boundaries and the catalogue of phenomena are in `families.md`; what the data mean, in `reading-rules.md`.\n318\t\n319\tSources in brackets: [instruction] the section \"Les étiquettes\" of `.claude/agents/etiqueteur.md`; [cross ] the cross review of 2026-11-04, `auto/revue-croisee/2026-11-04//revue.md`; [finishing ] its finishing pass, `auto/revue-croisee/2026-11-04/finition//revue.md`; [] the station review, `auto/revue/_/revue.md`; [consistency] that of BREITHORN, MICHIGAN and NEBRASKA; [expert] a label or an answer of the expert.\n320\t\n321\t## 1. What is labeled\n322\t\n323\t- **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]\n324\t- **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]\n325\t- **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]\n326\t- **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]\n327\t- **\"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]\n328\t- **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]\n329\t- **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]\n330\t- **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]\n331\t\n332\t## 2. The bounds\n333\t\n334\t- **`start` is the measurement just before the first touched point, `end` the measurement just after the last, never `start` = `end`**: a touched point moves or is missing; an anomaly of a single measurement goes from the point before to the point after (a passage at 11:00, 15 min rate: 10:45 → 11:15). [instruction, WILDSTRUBEL]\n335\t- **The bounds are measurement instants, at the minute of the measurement**: at a 15 min rate, it is the quarter hour; at 10 min or 5 min, the minute of the measurement, like the expert's label. [cross Obstruction, CLARIDEN, expert]\n336\t- **The bounds are read on the curves, not on the rejections**: a reference that drifts before being rejected, a target that comes back after the last rejection are touched; read the two or three measurements before the first rejection (the `error_value` of a reference and the pose often already move there), and, for a loss of references at night, the `corr_x` of the targets and of the neighboring references. [cross Visibility, FLORIDA, LENZSPITZE]\n337\t- **Each edge is checked sensor by sensor, in both columns, not on the median**: all sensors, not only those named; a `corr_x` peak can touch `corr_y` longer. [instruction, NORDEND, NEBRASKA, MICHIGAN]\n338\t- **A measurement that has come back halfway is still touched; one more measurement, already back, is too many**: read the value of the next step before closing, without rounding inward or outward. [instruction, BREITHORN, JUNGFRAU, CLARIDEN]\n339\t- **A range of rejections ends at the measurement following the last rejection of all touched targets**: the first rejected measurement is not the start either. [instruction, BREITHORN, NIEDERHORN, SNCF01]\n340\t- **A reference rejected at a bound counts as a touched point, unless it is rejected there as usual**: its usual rejections (by day, in the morning, a Target issue target) do not move the bound. [cross Obstruction, CLARIDEN]\n341\t- **At the edge of a gap, the bound is the first measurement after the gap, or the last before**: an event that starts at the resumption starts at that measurement, which is also the `end` of the No data; a single measurement inside an outage is bounded one rate step on either side. [cross Obstruction, WILDSTRUBEL, JUNGFRAU]\n342\t- **Before writing, a script checks the bounds**: `start` < `end`, they are measurement instants, and no sensor is touched there outside its usual rejections, references included. [cross Obstruction, WILDSTRUBEL]\n343\t- **The end of a nuisance specific to a target is read on its `corr_x` and `corr_y`, against its level before, over several nights**: not on the return of its `error_value`; without a return, the label runs to the end of the batch; without a level before, it ends where the curves stop changing. [cross Target issue, NORDEND]\n344\t- **A return ends where the curve stops coming back**: not at midnight; a plateau is not a return. [LENZSPITZE]\n345\t- **A label goes to the end of the batch only if points are still missing or moving there**: otherwise it ends at the return. [cross Displacement]\n346\t- **A lasting jump is bounded on the jump**: from the measurement before to the measurement after the one where the new level is reached; hidden in an outage, on the outage and the first measurement after; hidden under another label, at the first measurements where it is seen. [cross Displacement, expert]\n347\t- **The bounds of a thermal cycle are read day by day, on the turning points of the pose and of the `corr`**: never at midnight or at a fixed hour, except at the start and the end of the batch; when the pose is noisy, on its hourly median. [cross Thermal displacement, FLORIDA, SNCF01]\n348\t- **The camera cycle starts at the morning turning point**: the first instant when the tilt and the pan leave their end-of-night level without coming back, the later of the two; not the fast part of the movement, nor the first deviation of `days.py --bounds`; a deviation of a single rate step from the bound placed stays within the uncertainty. [cross Thermal displacement, NORDEND, finishing nordend]\n349\t- **It ends at the later of the two returns, the pose on its main axes and the curves at their night level**: an axis returns to the level where it then stays, not under a threshold set on the night, which may differ; the slow relaxation of a secondary axis (often the scale) does not push the end back, as in the expert's labels; without rest, the cycle ends at the next start and the labels follow one another. [cross Thermal displacement, NORDEND, WILDSTRUBEL, expert, finishing niederhorn, finishing wildstrubel]\n350\t- **A nuisance at night stops the cycle only if it distorts the pose**: a reference rejected, discarded, or that drifts against the targets (`overview.py --rigid`); a target bothered alone does not stop it. [finishing divers, finishing nordend]\n351\t- **A gap does not cut a cycle visible on both sides** (so the gaps of one or two measurements); otherwise, a gap or a jump at night stops it: the cycle ends at the rest of the pose if it comes before, otherwise at the last measurement before the gap or at the measurement before the jump. [finishing divers, finishing nordend]\n352\t- **Before extending a cycle over a night that moves, read the housing temperature and the references**: it must still drop there, or the pose follow its usual profile; a pose that moves at flat temperature, with a reference that drifts, is the nuisance of that reference, not the thermal return. [finishing divers]\n353\t- **The reference night of a cycle is chosen calm, not by civil day**: when the pose comes back all night, a start is dated at the turning point, not at the first deviation from that night. [SNCF01, cross Thermal displacement]\n354\t- **The phases of the structure are cut at the turning points**: when the trough is flat for several hours, the cut is placed in the flat and the two phases touch. [JUNGFRAU, cross Thermal displacement]\n355\t- **An event that touches the edge of the batch extends the label of the neighboring batch, if there is one**: it is not redone; otherwise, it starts or ends at the batch edge. [JUNGFRAU, cross Target issue]\n356\t\n357\t## 3. A single event"}]},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"e6043069-317f-497b-be27-4c405b3cac50","timestamp":"2026-11-17T20:31:06.575Z","tool_use_result":{"type":"text","file":{"filePath":"/home/maxime/.claude/projects/-home-maxime-aimsight-app/b1dece15-7ed2-440e-993c-de42f2e6a4bf/tool-results/bbi9zey7i.txt","content":"# Reading the data\n\nThe guide to the reading harness: followed by the analyst; improved by the upgrader (agents repository), run by Optimizer's `optimize` skill, the only one that writes here.\n\nA camera tracks targets (reflectors) fixed on a structure; its own movement is compensated thanks to reference targets, assumed fixed. This movement, the **camera pose** (`pan`, `tilt`, `rotation` in degrees, `scale`, `sigma0` of the registration, in `camera/`), is read before the sensors: it explains a large part of what moves on the curves (D-073). This guide says how to read a station's data: what the curves and the images show, moment by moment. It does not say what they mean: family, known event, hypothesis and verdict are the business of whoever calls you.\n\n## Read first\n\n- `tools/DATA.md`: the files of a station and the meaning of each column, the image quality metrics, the camera images (**first**);\n- `labeling/reading-rules.md`: what the data mean (the measurement chain, gaps, reading rules, false friends).\n\n## The tools\n\nRun them from the root of the calling repository, where `tools/`, `data/` and `labeling/` are links. They return values, never verdicts: you judge. `--out `: where whoever calls you stores your figures; they give it to you. The method (below) says in which order to run them; each section says what a tool returns and how to read it.\n\n| Tool | The question it answers |\n|---|---|\n| [`inventory.py`](#inventory) | What is there, what is missing: files, contents of each source, images, poses, cadence, sensors, rejections |\n| [`summary.py`](#summary) | The usual level of each sensor, then one column by time step |\n| [`plot.py`](#plot) | The series of chosen sensors and columns, as a PNG |\n| [`overview.py`](#overview) | All the sensors together, against the camera pose: common movement, single sensors, residuals, rigid movement |\n| [`ranges.py`](#ranges) | Dated ranges where each sensor leaves its level, at the native step |\n| [`days.py`](#days) | What comes back from one day to the next: night levels, days superimposed by hour, bounds of each day |\n| [`metrics.py`](#metrics) | The system metrics (temperature, voltage…) against the targets and the pose |\n| [`stations.py`](#stations) | Several stations on the same timeline |\n| [`quality.py`](#quality) | The six image quality metrics against a calm reference; labels; degraded instants no label covers |\n| [`thumbnails.py`](#thumbnails) | Full-resolution thumbnails of the camera images, around sensors or of a zone |\n| [`gif.py`](#gif) | A GIF of the camera images over a range, for a reply to the customer |\n| [`ls … \\| grep`](#whole-image) | The whole camera image at a time |\n\n### inventory\n\n```\npython3 tools/scripts/inventory.py [--start T] [--end T] [--files]\n```\n\nNames and counts, never values. Over the **whole period**:\n- files by type: beyond 5 per type, the count, the first and the last (`--files`: the full list, only to look for a specific file);\n- **what each source contains** over the window: the columns of the export, of the pose, of `quality/` and of `weather/` (the MeteoSwiss weather, hourly; a station without a Swiss position has none), with the number of rows that have a value (\"empty\" otherwise; an export column that not all sensors carry says how many carry it); the names of the system metrics of `metrics/`; the images and the difference images. The \"Export image quality (peak to snr)\" line says whether the six quality metrics are filled (then `quality.py`) or empty;\n- images by runs of equal gaps between two images (within 5 min, over the window if given): one line per change of gap, a hole is dated by its two images;\n- camera poses (count, period, measurement instants without registration), period, cadence, missing measurements, sensors (reference or target, error threshold, rejected measurements, distance from the camera and mm per px of `targets.csv`). When `pattern_type` is empty, a sensor is a reference if it carries `reproj_err` or `inlier` (the \"pattern_type empty for N sensors\" line says so);\n- \"Duplicate readings\": an export (often named after the customer's project) whose readings are already in the others; with 0 different values, it changes nothing to the reading, otherwise the tools keep the one of the last file in name order.\n\nWith `--start`/`--end` (on a batch: those of the batch), a section for the window: the missing steps, dated (for all the sensors, or which ones are missing); by sensor, the rejected measurements, dated (runs of consecutive steps; rejected: `error_value` above the sensor's threshold, **references included**); then the **number of references retained by the compensation** (`inlier` = 1) at each instant and the dated runs where some are not, which ones and why (`r` rejected, `0` discarded by the compensation, `empty`; another mark is the value of `inlier`, e.g. `-1`). When `inlier` is empty over the window, the retained references are read from the filled `reproj_err` (the title says so).\n\nA run that ends the same day writes only the time of its end. Over a month, the output with `--start`/`--end` exceeds what a call displays: read each section through `grep` (`| grep -A40 '^Retained references'`, `| grep '^ PR04 '`).\n\n### summary\n\n```\npython3 tools/scripts/summary.py [--column C] [--stat median|min|max] [--step 1h] [--level period|window] [--sensors A,B] [--start T] [--end T] [--instants T1,T2] [--mark]\n```\n\nThe usual level of each sensor (median, MAD, min, max) over the whole period, or over the `--start`/`--end` window with `--level window` (for a batch: a level change within the batch is not compared with weeks of other measurements); then a table by time step, the sensor header repeated every 24 lines.\n- Columns: `error_value`, `corr_x`, `corr_y`, `relative_x`, `relative_y`, `x`, `y`, `sigma0`, `reproj_err`, `corr_x_mm`, `corr_y_mm` (the `corr` in mm, empty without a sure factor: `tools/DATA.md`, \"The targets\"), and the six image quality metrics `peak`, `flux`, `sharpness`, `fwhm`, `dominance`, `snr` (raw values; against a calm reference, `quality.py`).\n- `--mark`: `*` after the value when a measurement of the step is rejected (`x`, `y`, `error_value` of a rejected measurement stay filled), `o` when one has inlier = 0.\n- `--instants T1,T2`: only the steps that contain these instants (the values of all the sensors at a few chosen times).\n- With `--step` equal to the cadence, `--level window --mark`: the per-instant, per-sensor table of one column, one column per run.\n\n### plot\n\n```\n.venv/bin/python tools/scripts/plot.py [--sensors A,B] [--columns C1,C2] [--start T] [--end T] [--zone T1/T2 ...] [--out D]\n```\n\nA PNG of the series, each `--zone` greyed; prints its path. Columns: those of `summary.py`, quality metrics included (raw values).\n\n### overview\n\n```\n.venv/bin/python tools/scripts/overview.py [--columns x,y,sigma0] [--column error_value] [--step 15min] [--k 5] [--min 5] [--residuals corr_x,corr_y,error_value|no] [--outside T1/T2] [--others] [--rigid BASE [--without A,B] [--follow A,B]] [--table T1/T2|no] [--sensors A,B] [--start T] [--end T] [--out D]\n```\n\nAll the sensors together, each against its median and its MAD over the window.\n\nPNGs:\n- **common**: at the top, if the folder has `camera/`, the **camera pose** (raw values, one point per registration, the line cut at measurement instants without registration); the median across sensors of `x`, `y`, `sigma0`, the dispersion across sensors as a grey band; on the `x`, `y` panels, also **each global reference separately** (one line each) and the **median of the targets alone** (black line); at each step, the number of sensors whose `--column` exceeds its median by more than `--k` MAD. Ticks every 1 to 12 h depending on the window, every n days beyond 20 days.\n- **multiples**: a small chart per sensor, one scale each: a step of a single sensor shows there.\n- **residuals-corr_x**, **-corr_y**, **-error_value** (`--residuals`; `no`: none of these PNGs nor their tables): a small chart per sensor of the column minus the sensor's own level (its median over the window; with `--outside T1/T2`, that of the rest of the window, outside the moment read), one scale each, zero dotted: a deviation of a few hundredths on `corr`, hidden in the parallel bands of `plot.py`, shows there.\n- **residuals-…-others** (`--others`): each sensor minus its own median **and minus the median of the other sensors at the same instant**: what all share (the remainder of the compensation of a common movement) cancels, what is specific remains.\n- **rigid** (`--rigid BASE`): at each measurement, the overall movement of the targets since the instant `BASE` (translation, rotation, scale, estimated by medians: a target that jumps alone does not pull it; `--without A,B` removes targets from it) and, for each sensor, the **residual** `dx`, `dy` (raw position minus its position at `BASE` carried by this movement, in px). Panels: `dx`, `dy` of each global reference against the median and the 10th-90th percentile of the targets, `|residual|` of the targets (median, 90th percentile), fitted rotation and scale, `reproj_err` of the references; a rejected reference is a cross (the scale is that of the accepted measurements, a far cross is out of frame).\n\nPrinted:\n- the **common median table**, one line per `--step`: the time, the deviation from the window median of `x`, `y`, `sigma0`, then `x_targets`, `y_targets` (median of the targets alone), then the raw camera pose `cam_pan`, `cam_tilt`, `cam_rotation`, `cam_scale`, `cam_sigma0` (empty without registration); the minimum and the maximum of each column with their instant; then those of `x`, `y` of each global reference (`(rejected)` when the measurement is, with the reference's number of rejected measurements); the measurement instants without pose (dated runs); the instants where at least `--min` sensors exceed together, with their names (`--min 1`: also a single sensor that leaves its level, absent from the default list of 5 sensors);\n- `--residuals`: per sensor, the level, the own noise (median of the differences between two measurements), the min/max deviation per step with their instant, in units and in noises;\n- `--others`: per sensor, the slope and the correlation r of the residual on the common median of `x`, `y`, `sigma0`;\n- `--rigid`: the table by step (`rot_deg`, `scale`, `tx`, `ty`, `tgt_med`, `tgt_max`, `dx`, `dy` of each reference and of each sensor of `--follow A,B`: the step-by-step sequence of a target) and, per sensor, min, max and value at the last instant of `dx`, `dy`. Rejected measurements enter neither the fit, nor the band of the targets, `tgt_med`, `tgt_max`, nor the columns of the table (over several days, parked cars or night rejections no longer drown the rest); the per-sensor summary gives them separately (`; N rejected: min …, max …`, and `(rejected)` after a last value that is rejected).\n\nThe tables by step (common median, `--rigid`) repeat their header every 24 lines; `--table T1/T2` prints them only between T1 and T2 (`no`: not at all), levels, min, max, PNGs and the rest remaining over the whole window: over a one-month batch, first `--table no`, then `--table` on the day of a moment (same levels, which a shorter `--start`/`--end` window would not give). The default step is 15 min, the cadence of the measurements: a one-hour step flattens a peak of one to four steps, dates to the hour and erases an agitation of `x`, `y`; do not widen it to read a batch.\n\nReading, in this order:\n1. **The camera pose first** (top panels, `cam_` columns), dated at the native step: when it rotates (`pan`, `tilt`, `rotation`), changes scale, when its registration degrades (`sigma0`) or is absent (line cut, instants without pose). Each moment of the sensors is read against it: during a movement or a registration gap, or camera still.\n2. **Who moves in the image.** The pose is computed from the global references: a change of pose (or a rise of `sigma0`) is a camera movement only if **the targets also move in the image** (on the `x`, `y` panels, the lines of the references against the black line of the targets alone; `x_targets`, `y_targets`). Only references move, targets still: these references moved, and the pose and the `corr` of all the targets are skewed without raw movement of the targets; say which references and by how much. References and targets together: the camera or the scene; then look whether the `corr` come back.\n3. **Rotation or scale: `--rigid`.** Then the deviation from the median no longer says who moves alone (each sensor deviates according to its place in the image; the rigid residual does not). Before writing \"everything moves together\", rerun with `--rigid BASE`, `BASE` a calm instant before the first movement: a reference whose residual stays far from the 10th-90th percentile of the targets, or a `reproj_err` of the references that does not come back, means the compensation remains skewed by these references and the steps of `corr` partly come from it (say which, by how much, until when); a rising `|residual|` of the targets says they do not move as a block.\n4. **Then `x`, `y`, `sigma0`, before `corr`**: the median of `x`, `y` (raw position, references included), the references one by one, the targets alone and `sigma0` say what moves in the image. Date the start, the end, the return of a movement, or a level that does not come back, on the printed table (time, value), not on the PNG axis. A dip of `corr` after a movement of the raw median is the remainder of the compensation, not a movement of these sensors. The multiples of `error_value` show a lasting step of a sensor, the count the instants where many rise together.\n5. **The residuals, on every batch, without waiting for a suspicion**: a single sensor that rises or falls, a `corr` that drifts by a few hundredths, a step specific to one sensor under a common movement show there; the table says by how much (in noises) and when. On a target whose `corr` goes down under a strong common movement, `--others` separates a remainder of the compensation from a movement of its own: a dip that remains is not a remainder shared by all; a high slope with r close to ±1 on common `y` says it is proportional to the common movement (gain specific to the sensor); without r or slope, it is independent of the movement.\n\n### ranges\n\n```\npython3 tools/scripts/ranges.py [--columns error_value,corr_x,corr_y] [--k 5] [--merge 1h] [--min-measurements 1] [--outside T1/T2] [--rolling N|DURATION] [--instants N] [--sensors A,B] [--start T] [--end T]\n```\n\nDates the start and the end of a sensor's moment without rerunning ten tables. By column and by sensor, at the measurements (native step, never averaged): level (median of the window), own noise, **largest jump** from one measurement to the next (value, in noises, the two instants; `(rejected: …)` when one end is); then the **ranges** where the sensor deviates from its level by more than `--k` noises: start, end, number of measurements, extreme (signed, in units and in noises) and its instant. Two ranges of the same sign less than `--merge` apart make one; rejected measurements do not cut a range; column `rejected`: how many of the range's measurements are (and `rejected extreme`). A range that touches the edge of the window is dated at the edge.\n- `--outside T1/T2`: level and noise computed outside an episode that skews the window median (the sensor spends half the batch there). Rerun with it around a long episode to date its return to the level: do not conclude \"does not come back\" without having read it.\n- `--min-measurements N`: only the ranges of at least N measurements (and how many out of the total). Over several days, the one-step ranges number in the hundreds and drown the long steps: first `--min-measurements 6`, then without.\n- `--rolling N` (N measurements on each side) or `--rolling 1d` (the measurements within a duration): the level of each measurement is the median of its neighbours, without it; a long drift or a step follows this local level, only the deviations shorter than the window remain (the level column and the noise do not change; with `--outside`, only the noise is computed outside the episode).\n- `--instants N`: at the end, the instants where at least N sensors are out of level on one of the columns, with each sensor and its signed deviation in noises (`cx` corr_x, `cy` corr_y, `ev` error_value), the sensors rejected at that instant (among `--sensors`: removing the always-rejected sensors lightens the list), and each reference: `error_value` (`r` if rejected) / inlier.\n- When the batch has a long drift or several steps (the ranges number in the hundreds, or one half of the batch is \"out of level\"), rerun with `--rolling` (a few measurements, or a few hours to a day depending on the cadence) and `--instants 2`: the brief deviations under the drift come out alone, and the list per instant says which sensors deviate together, which are rejected and what the references do; a deviation of all the targets with the references at the same instant is read against the camera pose.\n\nA noise of `0` (and \"-\" in noises, no range): the values are constant to rounding (deviations below 1e-9), like the `corr` of the references when the compensation retains only two (see Conventions); the same in `overview.py --residuals` and `days.py`.\n\n### days\n\n```\n.venv/bin/python tools/scripts/days.py [--columns corr_x,corr_y,error_value] [--night 20-3] [--k 5] [--days 2] [--step 15min] [--sensors A,B] [--bounds [--smoothing N] [--fraction F]] [--start T] [--end T] [--out D]\n```\n\nWhat comes back from one day to the next, on accepted measurements only. A night: the hours `--night` H1-H2 UTC, straddling midnight, dated from the day it starts; choose hours where the day cycle (`error_value`, camera pose) has subsided (**byhour** figure).\n\n1. **Level of each night**, by sensor and by column: median, MAD, number of measurements, own noise; from one night to the next, the **step** (difference of the medians, in units and in noises) and **where it falls** (\"between A and B\": where the night measurements of the two nights split best between the two levels; B at the start of the following night: the cut falls by day). Read it for any sensor that has already made a step or for which `--outside` is not enough (several levels in the batch): a step of a few noises is dated by its \"between A and B\", a step of `error_value` and one of `corr` at the same instant are linked, a slow drift reads from one night to the next.\n2. **Superimposed days**: PNG **byhour-**, a small chart per sensor, hour of the day on the x axis, one curve per day, each measurement minus the level of the last night started (night greyed, frame from the 1st to the 99th percentile, the title says how many measurements fall outside it). Table: per `--step` slot of the hour of the day, the sensors whose deviation exceeds `--k` noises on the same side at least `--days` days, with the number of days and the median of these deviations. What comes back every day at the same hour, on one or several sensors, groups there, even when it lasts one to three measurements: one moment per hour of the day (say which sensors, how many days out of how many, the amplitude, what the camera pose does at that hour), not one moment per day, nor nothing because each step is short.\n3. **Bounds of each day** (`--bounds`), for what comes back every day and is labelled day by day (thermal cycle, warming and cooling), rather than fixing the same hours for all the days: for the median of the targets of each column (with `--sensors`, the median of these sensors; with one, its own) and for the camera pose (`pan`, `tilt`, `rotation`, `scale`, `sigma0`, if `camera/` exists), the deviation from the level of the night that precedes each day (a day goes from the end of one night to the end of the next). Per day: number of measurements, the first and the last; first and last instant beyond `--k` noises, with the measurement just before and just after, at the native step; signed max and min with their instant; the sequence of measurements beyond `--k` noises around the larger of the two; the following night minus the reference night. A day without measurement says so; a reference night that is not the previous one is named. Each day line starts with the short name of its series (`corr_x`, `pose_tilt`…): `| grep '^pose_tilt '` reads one, `| grep ' 12/10 '` one day. PNG **bounds**: the deviation over the batch, first → last exceedance light grey, sequence around the extreme dark grey, max and min marked.\n - `--smoothing N`: the deviation of each measurement is the median of the N measurements of the day centred on it (noise and `--k` unchanged; PNG: smoothed in blue, raw in grey): an isolated point no longer cuts the sequence around the extreme nor makes a first or a last exceedance.\n - `--fraction F`: the threshold of each day is F times its largest |deviation| (printed on its line, `threshold …`), instead of `--k` noises: when the noise at the native step is unrelated to the amplitude of the cycle (very noisy or very smooth pose).\n - Reading: the sequence around the extreme dates the cycle, the max and the min a go and a return (morning and afternoon); \"before\" and \"after\" give the bounds at the native step (at a cadence of 1 h or 4 h, an event goes from the measurement before to the one after). First exceedance at the start of the day (\"before -\") and last at its end every day: the night is not calm; change `--night`, or `--sensors` the targets that carry the cycle. Camera drifting all night: a short night just before the morning (`--night 3-5`: the level of the rest that precedes the start). Noisy series or isolated points: `--smoothing 5`. Threshold in noises that does not bite (never exceeded, or exceeded all day): `--fraction 0.3`, then read the sequence around the extreme, not the first and the last exceedance. A \"1 measurements\" line is a peak, not a cycle.\n\n### metrics\n\n```\n.venv/bin/python tools/scripts/metrics.py [--names A,B] [--step 1h] [--stat median|min|max] [--against temperature] [--smoothing 24h] [--metrics-only] [--start T] [--end T] [--out D]\n```\n\nThe system metrics of `metrics/` (one value per hour), never the identifiers (`SIM_CCID`, `ip*`):\n- the available metrics with their number of values over the window (\"empty\": none; all empty is an absent datum, not a stable temperature);\n- a table per `--step`: `temperature` (median of the `sensor_*_deg_c` components, the one the detectors read), each metric of `--names` (default: the `*_deg_c` and `BusVoltage`), then, unless `--metrics-only`, `tgt_corr_x`, `tgt_corr_y` (median over the targets of `corr` minus each target's own level, accepted measurements) and the raw camera pose (`cam_pan` … `cam_sigma0`); an empty cell is skipped, a text metric (`link`, `BatteryState`, `last_sync`) is returned as it is. `--step 1d --stat min` (or `max`): the minimum or the maximum of each day;\n- per column: filled steps, min and max with their instant; the correlation r and the slope of each column on `--against` (with `--smoothing 24h`, on its rolling mean, column `_smooth`: for a station where the temperature varies little and fast, indoors); the dated runs of steps without any metric;\n- a PNG: temperatures on one panel (median in black), each other metric on its own, then `tgt_corr_x`, `tgt_corr_y` and the pose, line cut on a gap.\n\nAn r does not say a cause: say it as a value, with the window where it is computed.\n\n### stations\n\n```\n.venv/bin/python tools/scripts/stations.py [...] [--columns temperature,cam_tilt,cam_rotation,cam_scale,tgt_corr_x,tgt_corr_y] [--step 1h] [--stat median|min|max] [--table T1/T2|no] [--start T] [--end T] [--out D]\n```\n\n**Several stations on the same timeline** (neighbouring stations, same building). Columns: `temperature` (as in `metrics.py`), `cam_pan` … `cam_sigma0` (raw pose), `tgt_corr_x`, `tgt_corr_y` (as in `metrics.py`), `rej_targets`, `rej_refs` (number of rejected targets, of rejected references, the largest of the step).\n- Prints per station the period, the cadence and the number of instants; the **gaps**: the runs of steps without measurement or without temperature, with the stations where they are missing (a gap common to several stations on a single line); the table by step (one `STATION:column` column each, tabs; `--table` as in `overview.py`); per column and per pair of stations, r of the values and r of the steps from one value to the next (a common movement shows on the steps, a common trend on the values), with n.\n- PNG **stations**: a panel per column, a line per station (raw temperature, the rest minus its median), and a band per station of the steps without measurement.\n- Take `--step` equal to the slowest cadence of the stations; over a month at `1h`, first `--table no`.\n\n### quality\n\n```\npython3 tools/scripts/quality.py [--calm T1/T2,T3/T4] [--common] [--table M] [--step 15min] [--threshold 0.5] [--sensors A,B] [--start T] [--end T]\n... --labels F [--numbers 3,7] [--margin 60] [--edges]\n... --labels F --outside [--min 1] [--except \"Thermal displacement\"]\n.venv/bin/python tools/scripts/quality.py --figure [--metrics flux,snr,dominance] [--labels F] [--zone T1/T2 ...] [--out D]\npython3 tools/scripts/quality.py --self-test\n```\n\nThe six **image quality metrics** (`peak`, `flux`, `sharpness`, `fwhm`, `dominance`, `snr`; definitions: `tools/DATA.md`), on the stations that have them (otherwise: \"No quality metrics\", and nothing else). Each measurement becomes a **ratio** to the **calm reference** of its sensor: the median of the metric over its measurements in the `--calm` windows, at the same UTC hour of the day (without `--calm`: the whole folder); 1 = like the reference, < 1 lower, > 1 higher; for `fwhm` and `dominance`, the rise says a degraded image; rejected measurements included.\n- Without options: the folder's maximal `peak`, then per sensor (`r` = reference) the rejected measurements, `pk/max` (median peak over the window divided by this maximum: at 1, the spot touches the image ceiling, its `peak` no longer moves and its `sharpness` follows the exposure: read `flux`, `snr` instead), and for each metric the median ratio and the extreme with its instant; then the median of the targets and of the references.\n- `--common`: per step, the median of the ratios of the targets / of the references for each metric (what affects the whole scene, visibility or turbulence; `--step 1d` shows on one screen on which days the reference holds).\n- `--table M`: per step, the ratio of `M` of each sensor (`*`: a rejected measurement), their median and how many pass `--threshold` (below, or above 1/`--threshold` for `fwhm`, `dominance`): a target that goes out and comes back; on a moment, `--table flux --sensors …` says which targets are hidden (flux cut) or veiled, from which instant to which instant: write them by their name.\n- `--labels F` (one JSON per line, `start`, `end`, `family`): per numbered label, the median ratio of the targets and of the references over the hour before, the range and the hour after (`tgt 0.96|0.26|0.79`, `--margin` minutes), then the sensors **affected** over the range (flux or snr below `--threshold`, or dominance above 1/`--threshold`), with their worst flux, from lowest to highest. `--edges`: per instant of the widened range, the number of affected sensors and the median of the targets of flux, snr, dominance (`<` within the range), to date the first and the last degraded instant.\n- `--outside`: the runs of instants that no label covers (outside `--except` families) where at least `--min` sensors are affected, with the sensors and their worst flux: candidates for forgotten labels, to check on `corr_x`, `corr_y`.\n- `--figure` (instead of the tables): PNG **quality-common** (a panel per metric, log scale: median of the targets in black, of the references in red, grey band from the 10th to the 90th percentile of the targets: a disturbance of the whole scene moves the median, an occultation of a few targets only the bottom of the band) and a PNG **quality-** per `--metrics` (a small chart per sensor, references in red); `--labels` greys each label in one colour per family, `--zone` ranges.\n\nReading: the metrics say **why** a measurement degrades, where `error_value` says only that it degrades; they prove a cause and name the affected targets. What they showed on LENZSPITZE (to be confirmed on each station): `flux` cut (close to 0) on a group of targets, the others intact, for one to a few measurements: these targets are hidden (the list is read on the flux each time, not on the usual list; a hidden target can stay under its error threshold, and its point is wrong); `flux` down over the whole scene, stronger on the distant targets: reduced visibility; `sharpness` down and `dominance` up, `flux` whole: the image shakes (turbulence); nothing moves: neither the image nor the view, to be looked for in the movement. A whole flux refutes an occultation. `fwhm`, truncated to the disc, moves little; on a spot at the ceiling (`pk/max` at 1), it goes down when the spot darkens.\n\n**The calm reference decides everything**: take `--calm` on calm hours of the **same image regime** as the range read. When the lighting or the exposure changes (after a gap, an intervention), a reference on the other side skews the ratios by a factor of two or three: `--common --step 1d` over the batch shows this change (medians of the targets and of the references far from 1 for whole days, then at 1); then take a reference on each side and read each side with its own. Calm days are often days of thermal cycle: a reading of the thermal against them is circular.\n\n### thumbnails\n\n```\n.venv/bin/python tools/scripts/thumbnails.py --sensors A,B --times T1,T2 [--radius 100] [--contrast [MIN,MAX]] [--fixed] [--zone X,Y,W,H] [--out D]\n```\n\nA sheet of full-resolution thumbnails: one row per sensor, one column per time, centred on the sensor's raw position (`x`, `y`) at each time. Look at it with Read: a whole image read by Read is reduced, a small reflector becomes illegible in it.\n- The centre of the frame is written under each thumbnail: when `x`, `y` jump, the frame moves by as much, and a spot that enters the frame seems to appear; `--fixed` keeps for each sensor the frame of the first time and marks with a red cross the `x`, `y` of each time.\n- Unretouched pixels: the brightness compares from one thumbnail to the next; prints for each thumbnail the background (median), the 99th percentile and the peak (grey levels 0 to 255). Without an image at the requested time, takes the nearest and prints the gap (the actual time is in the title).\n- A faint or deformed spot is invisible as it is: `--contrast MIN,MAX` puts all the thumbnails in grey with the same stretch (without value: from the 1st percentile to the sheet's maximum, crushed by a saturated pixel; then choose MIN,MAX from the printed background and peak, e.g. `10,40`); `--radius 30` to `50` magnifies. Compare the shape and the peak before, during and after an episode, at the same hour of the day.\n- A frame that the image edge cuts is flagged (\"frame cut by the image edge (W × H px)\"): on some stations, `x`, `y` are not pixels (values close to 0) and the frame falls in the corner; then look at the scene through `--zone`.\n- `--zone X,Y,W,H` (pixels of the original image: top left corner, width, height, as in `gif.py`): the same zone at each time, side by side (up to 4 per row), same stretch with `--contrast`; `--sensors` becomes optional, those given are marked with a cross and their name. For the scene around the targets (foreground object, headlights, lighting), prefer it to a large `--radius`.\n- Each thumbnail is rendered pixel for pixel up to 1000 px a side, but Read reduces a wide PNG: with a large `--radius` or a large `--zone`, three or four times per sheet.\n\n### gif\n\n```\n.venv/bin/python tools/scripts/gif.py --start T --end T [--width 720] [--duration 700] [--max 150] [--zone X,Y,W,H] [--out D]\n```\n\nA GIF of the camera images between `--start` and `--end` inclusive, cropped to `--zone` if needed, set to `--width` px, UTC date and time at the bottom right; beyond `--max` images, `--max` at regular intervals; prints the time of each image, then the path and the size of the GIF. To attach the scene to a reply to the customer; Read does not read a GIF: to look, `thumbnails.py --zone`.\n\n### whole image\n\n```\nls /images/ | grep TZ\n```\n\nThen Read on the file found (Read takes no pattern): the whole camera image at that time (UTC), for the scene (occultation, lighting, weather).\n\n## Conventions\n\n- Instants: `2026-01-01T00:00Z`; a time without time zone is read as UTC; `--end` includes the minute given. On a batch, `--start` and `--end` of the batch.\n- Bash is used only to run these tools, `ls`, `grep` and `date`, one command per call, without a `for` loop (a pipe to `grep` is allowed): permissions are granted command by command. If the current directory is not the root of the calling repository, `cd && ` counts as one command. Write no other script. Whoever calls you may add commands to this list.\n- **An output too long for one call** (beyond a few hundred lines, cut at display): shorten it first with the tool's options (`--table no` then `--table T1/T2`, `--min-measurements`, `--sensors`, `--columns`, a shorter window), or read a section of it through a pipe to `grep` (`| grep -A40 '^Title'`, `| grep '^pose_tilt '`). If you have to reread it several times, store it in the output folder in the same call (` > /.txt`) and read that file with Read (`offset`, `limit`) or with `grep`: no `head`, `tail`, `sed`, `cut`. The tools create their output folder themselves: no `mkdir`.\n- A sensor name that carries an apostrophe (`COLH20'''`, `REFP''21`) goes in double quotes in the shell: `--sensors \"COLH20'''\",COLI22`.\n- **Each PNG is looked at with Read**: you read a chart better than a table, and a PNG you have not looked at has shown nothing.\n- A rejected measurement (`error_value` above the threshold) is not a measurement: the station empties the `corr` of a rejected target, but leaves those of a rejected **reference**, often absurd; the tools empty them (`corr`, ranges, residuals, jumps cover only accepted measurements). When the compensation retains only **two references**, their `corr` is 0 (to 1e-13): it passes exactly through them; their noise prints as `0` and their deviations in noises as \"-\"; read nothing into these values, read the references through `x`, `y` (`overview.py --rigid`) and `error_value`. Its `x`, `y` remain: before citing a jump of `x`, `y`, check whether it is marked `(rejected)`; a rejected measurement is not cited as a movement.\n\n## The method\n\n1. **Inventory** (`inventory.py`): what is available, what is missing. A filled column that the tools do not show or a source that no tool reads (`images_diff/`) remains data: know that it exists. The image quality columns (`peak` to `snr`, recent cameras) are read through `quality.py`; `metrics/` through `metrics.py`: a cut of the measurements is read against the steps without metric and the voltage (`--names BusVoltage,BusCurrent,Power,BatteryPercent --metrics-only` on the cut). On a batch, rerun it with the batch's `--start`/`--end`: the absent steps and the rejections of the batch, dated; those of the whole period say nothing about the batch. Read the rejections of the **references** as much as those of the targets: a sensor rejected at the same hours every day makes a moment on its own (say its share of rejected measurements and its hours, day by day); when it is a reference, say with how many references the compensation then runs (the list of retained references). When several targets jump together by one step, or the compensation drops (no pose), look first in that list at which references were lost at that instant.\n2. **Wide first**:\n - `overview.py` on the batch, first (on a batch of more than a few days, `--table no`, then `--table T1/T2` on the days to read), read in the order of its Reading section: the pose, who moves in the image (`--rigid` as soon as the pose rotates or changes scale), `x`, `y`, `sigma0` before `corr`, the residuals on every batch.\n - On a batch of more than two days, then `days.py`, before reading the isolated steps of `ranges.py`: first its **byhour** PNGs and table by slot, then its **night levels**; `days.py --bounds` for what comes back every day and is labelled day by day.\n - Several neighbouring stations given by whoever calls you: `stations.py` (temperatures, poses, `corr` of the targets, common rejections and gaps, at the same hours) before comparing their moments.\n - When the pose or the `corr` of the targets drift over several days, or move without day/night cycle: `metrics.py` on the batch, the temperature against `tgt_corr_x`, `tgt_corr_y` and the pose, on the PNG, then r and the slope.\n - On a station that has the image quality metrics: `quality.py --common --step 1d` on the batch (choice of the calm reference), then `quality.py --figure` with this reference: the median `flux` of the targets and of the references dates the hours of reduced visibility, the grey band that dives alone the occultations; with a labels file, `--labels F --outside`.\n - Then `plot.py` on all the sensors, `error_value` then `corr_x`, `corr_y` (or `relative_x`, `relative_y`), references and targets; `summary.py` on these columns with a wide step (6h or 1d).\n3. **Then zoom**: `summary.py` at 15min (`--stat max` for the real peak of a sensor), and `plot.py` on the windows and the sensors that move.\n4. **Each sensor against its own usual level** (its median and its MAD), never against an absolute threshold; on a batch, the level is computed on the batch (`--level window`, `overview.py`), not on the whole period.\n5. **Each retained moment is dated and measured at the native 15 min step**: start, end and maximum read on the 15 min table (`overview.py` by default, `summary.py --step 15min`), never on an hourly table; also `overview.py --min 1` for single sensors; `ranges.py` on the batch (first `--min-measurements 6`) for, per sensor, start, end, extreme and largest jump at the native step (`--outside` around a long episode, `--rolling` and `--instants 2` under a long drift or several steps); the tables of `x`, `y` on the windows where they stir. On a station that has the quality metrics, for each moment: `quality.py --table flux --sensors …` (or `--labels F --numbers N --edges` on a label): which targets are hidden or veiled, from which instant to which instant.\n6. **The images**: thumbnails (with `--contrast` for a faint target) spaced, one every 2 to 3 h, tighter where the curves move, always with an unaffected witness sensor, at a time before, during and after (at the same hour of the day if possible); when `x`, `y` of a sensor jump between two thumbnails (centre of the frame written under each), rerun with `--fixed` before saying that a spot appears or disappears; the whole image for the scene (occultation, lighting, weather).\n\n## What the reading returns\n\nOne line per moment. A moment: a sensor or a group of sensors that leaves its usual level during a window you can date.\n\n| Start | End | Sensors | Columns | What I see | Images |\n|---|---|---|---|---|---|\n\n- **Sensors**: references or targets, how many, which ones.\n- **What I see**: the shape (one-step peak, step, slow rise, agitation), the amplitude against the usual level (in MAD or in times the median), the return to normal or not, what the other sensors do, **what the camera does** at the same moment (pose moving, by how much, or still; registration absent; \"no `camera/`\" if the folder has none).\n- **Images**: what the thumbnails and the whole image show at that moment, or \"no image\".\n\nTimes in UTC.\n# The data of a station\n\nWhat the files of a station folder are, and what each column means. How to read them with the tools: `GUIDE.md`. What they mean for a label (causes, reading rules, false friends): `labeling/reading-rules.md`. Maintained by hand; `GUIDE.md` is the tool-builder's.\n\n## The displacements: the \"advanced\" export\n\n`displacement/_advanced__.csv`, the source of the analyses: one row per sensor and per measurement, at the native rate of the station (10 or 15 min), `time_utc` in explicit UTC.\n\n| Column | Meaning |\n|---|---|\n| `sensor_name` | the sensor (target or reference) |\n| `pattern_type` | `global_ref`: a reference of the compensation; `ref`: a *local reference*, treated as a target, outside the compensation, without `reproj_err`; empty: a target |\n| `x`, `y` | raw position in the image [px]. Not the centroid of the spot: the offset centroid − (`x`, `y`) is constant per sensor by day and differs between sensors; it changes at night, when the spot is saturated. Probably the position of the reference pattern |\n| `relative_x`, `relative_y` | relative displacement before the camera compensation [px]; not `x − x0` |\n| `corr_x`, `corr_y` | the position of the target once the estimated camera movement is removed: **the curves that are labelled**. In px, not mm (below) |\n| `corr_x_mm`, `corr_y_mm` | `corr_x`, `corr_y` in mm: × the sensor's `mm_per_px` (`targets.csv`, below), computed by `data.load`; empty without a sure factor. The same curves in another unit: the noise threshold of a label is read in noises, whatever the unit; mm say how far a target moves, for the reader |\n| `error_value` | recognition error of the pattern, not an uncertainty |\n| `error_threshold` | specific to each sensor (0.3 to 0.7). Above it, the measurement is rejected: the row and its `error_value` stay, `corr_x` and `corr_y` are empty, not interpolated |\n| `reproj_err`, `inlier` | references only: residual and contribution of each reference in the compensation |\n| `sigma0` | residual of the fit on the references: one value per measurement, repeated on every row |\n| `peak`, `flux`, `sharpness`, `fwhm`, `dominance`, `snr` | image quality of each sensor, recent cameras only (below) |\n\n- \"Rejected\" is a judgment of the AIMsight platform, not of the camera: the camera delivers all its measurements, and a client's platform that integrates the data receives them all.\n- **Unit of `corr_x`, `corr_y`**: px. The hourly export's `horizontal_displacement` (mm) is a factor × the hourly mean of `corr_x` + a constant (likewise `vertical` and `corr_y`, correlation ≥ 0.99); the factor (mm per px) depends on the pattern and on the station.\n- **LENZSPITZE**: its export gives `x`, `y` relative to the pattern; the extraction rewrites them in image px and fills `pattern_type`. Sensors 1023 and 8019 have no pattern: their `x`, `y` are empty. The tools' crosses may sit slightly off the spots there.\n- `inventory.py` says, on a batch, which columns carry values.\n\n## The targets\n\n`targets.csv`, from the pumping: one line per sensor of the platform, `sensor_name`, `pattern_type`, `distance_mm` (from the camera) and `mm_per_px` (`distance_convertion_factor`, the factor of the dashboard's exports in mm), their current values. Read by `data.load_targets`, shown by `inventory.py` (sensor table).\n- The references are not in it yet (pumped from the next pumping on): no distance, no mm for them. They are assumed fixed.\n- `distance_mm` 1000: not filled in on the platform; the line is ignored.\n- A name may have several lines (a target counted twice, an older configuration of the unit, another lens): when they disagree, `data.load_targets` keeps no value (`inventory.py`: `?(n)`) and that target has no mm; the distance stays when the lines agree on it.\n- The distance says which targets are near and far. A far target moves few px for many mm: targets are compared with each other in mm, or in px with their distance. A camera that turns shifts every target by about the same px (the mm grow with the distance); a movement of the structure of the same mm gives px that shrink with the distance; a parallax shows between targets at different distances.\n\n## The camera pose\n\n`camera/_camera_.csv`, from the pumping only: the pose at each registration, `time_utc` in UTC, `median_|min_|max_` of `pan`, `tilt`, `rotation` [deg], `scale`, `sigma0`, one row per measurement (min = max). A measurement instant without a row: the camera was not registered.\n\n- Orders of magnitude: `pan`, `tilt` of a few hundredths of a degree, `scale` within 10⁻³ of 1; some stations show several degrees, not explained.\n- **A positive `tilt` means the camera is nosing down** (the expert).\n- Read by `overview.py` and `inventory.py`.\n\n## The weather\n\n`weather/_weather_.csv`, from the pumping, for a station with a Swiss position only: the hourly measurements of the nearest MeteoSwiss station, `time_utc` in UTC (start of the hour); `position`, `place`, `station`, `station_name`, `distance_km`, `height_m` say where; then `precipitation_mm`, `temperature_c`, `humidity_pct`, `wind_speed_kmh`, `wind_gust_kmh`, `wind_direction_deg`, `pressure_hpa`, `sunshine_min`, `global_radiation_wm2`, `snow_depth_cm` (empty: not measured there). The weather a few km away, not at the camera: what the images show prevails. Read by `data.load_weather`.\n\n## The hourly export\n\n`__to__1hour.csv`: one row per hour, targets only; per target `horizontal_displacement`, `vertical_displacement`, their `_min` / `_max`, `_error` (mean `error_value` of the hour), `_count_val` (measurements of the hour, rejected ones included).\n\n- **`timestamp` has no time zone: Swiss local time** (UTC+2 in summer), at the start of the hour.\n\n## Image quality of a target\n\nSix columns of the advanced export, computed by the GPU of recent cameras on the sensor's window in the DIFF image, in units of that image. Filled only where `inventory.py` says so (\"Export image quality\"); for older cameras, `~/optical_emulator` can recompute them from the DIFF images. \"Disc\": the neighbourhood of the peak, radius `min(H, W)/6` (at least 3 px); \"background\": the rest of the window.\n\n| Metric | Definition | What it measures | Reading |\n|---|---|---|---|\n| `peak` | `max(I)` | the brightness of the return | high, saturation; low, underexposure or missed flash. All targets dropping: the lighting; a single one: that target (fouling, misalignment) |\n| `flux` | flux of the disc minus the background | the light of the target, background removed | reflectivity of the target (fouling, ageing, flash), not ambient light; drops well before `error_value` exceeds its threshold |\n| `sharpness` | `Σ(I²) / (ΣI)²` | concentration of the energy (higher = sharper) | drops: drifting focus, turbulence, degrading target. Independent of the gain, not of the background: follow it over time on one target, do not compare cameras |\n| `fwhm` | width at half height around the peak, background removed [px] | width of the spot | rises: defocus, turbulence, motion blur. Truncated to the disc: under strong defocus it flattens instead of rising |\n| `dominance` | `(second peak − background) / (peak − background)`, 0 (clean) toward 1 (ambiguous) | does a single spot dominate the window? | high: a comparable second reflection, a stray bright point, or the target has gone and something else is the brightest: the correlation can latch onto the wrong pattern, which `error_value` does not see. One hot pixel outside the disc is enough |\n| `snr` | `(peak − background) / bg_sigma` | the signal above the background noise | low: marginal return, even when `peak` looks normal. Independent of exposure and gain. The emulator marks `empty` below 8 |\n\n`peak` and `flux` give the brightness, `sharpness` and `fwhm` the sharpness, `dominance` and `snr` the validity: together they say **why** a measurement degrades, where `error_value` only says that it does. They describe the image of **one target**, not the health of the reference network.\n\n## Camera images: IRON and DIFF\n\n- **IRON** (`images/`): the ordinary image of the scene, JPG. The cause of an event is seen on it (condensation, rain, train, snow).\n- **DIFF** (`images_diff/`): several captures combined to raise the contrast of the reflectors; **the image the displacement algorithms measure**, by default. Not a difference between two instants. 16-bit PNG.\n- Acquisition modes (station manual): \"Single with infrared light\", one image per measurement; \"Differential\", several combined (`Stacking` 20 to 40 when light is difficult); option \"Work on IRON images\", to follow a texture without reflector.\n- Not every station has DIFF images; the pumping keeps about one image per hour. The tools look only at IRON images; `inventory.py` counts the DIFF ones, which your own scripts may read. What is very close to the lens (a web) may stand out better on DIFF.\n# The labeling rules\n\nHow to place a label: the only source of these rules for the aimsight-app `analyst` (before it, the Support-Agent `etiqueteur`) and for those who review their labels. The families, their boundaries and the catalogue of phenomena are in `families.md`; what the data mean, in `reading-rules.md`.\n\nSources in brackets: [instruction] the section \"Les étiquettes\" of `.claude/agents/etiqueteur.md`; [cross ] the cross review of 2026-11-04, `auto/revue-croisee/2026-11-04//revue.md`; [finishing ] its finishing pass, `auto/revue-croisee/2026-11-04/finition//revue.md`; [] the station review, `auto/revue/_/revue.md`; [consistency] that of BREITHORN, MICHIGAN and NEBRASKA; [expert] a label or an answer of the expert.\n\n## 1. What is labeled\n\n- **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]\n- **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]\n- **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]\n- **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]\n- **\"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]\n- **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]\n- **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]\n- **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]\n\n## 2. The bounds\n\n- **`start` is the measurement just before the first touched point, `end` the measurement just after the last, never `start` = `end`**: a touched point moves or is missing; an anomaly of a single measurement goes from the point before to the point after (a passage at 11:00, 15 min rate: 10:45 → 11:15). [instruction, WILDSTRUBEL]\n- **The bounds are measurement instants, at the minute of the measurement**: at a 15 min rate, it is the quarter hour; at 10 min or 5 min, the minute of the measurement, like the expert's label. [cross Obstruction, CLARIDEN, expert]\n- **The bounds are read on the curves, not on the rejections**: a reference that drifts before being rejected, a target that comes back after the last rejection are touched; read the two or three measurements before the first rejection (the `error_value` of a reference and the pose often already move there), and, for a loss of references at night, the `corr_x` of the targets and of the neighboring references. [cross Visibility, FLORIDA, LENZSPITZE]\n- **Each edge is checked sensor by sensor, in both columns, not on the median**: all sensors, not only those named; a `corr_x` peak can touch `corr_y` longer. [instruction, NORDEND, NEBRASKA, MICHIGAN]\n- **A measurement that has come back halfway is still touched; one more measurement, already back, is too many**: read the value of the next step before closing, without rounding inward or outward. [instruction, BREITHORN, JUNGFRAU, CLARIDEN]\n- **A range of rejections ends at the measurement following the last rejection of all touched targets**: the first rejected measurement is not the start either. [instruction, BREITHORN, NIEDERHORN, SNCF01]\n- **A reference rejected at a bound counts as a touched point, unless it is rejected there as usual**: its usual rejections (by day, in the morning, a Target issue target) do not move the bound. [cross Obstruction, CLARIDEN]\n- **At the edge of a gap, the bound is the first measurement after the gap, or the last before**: an event that starts at the resumption starts at that measurement, which is also the `end` of the No data; a single measurement inside an outage is bounded one rate step on either side. [cross Obstruction, WILDSTRUBEL, JUNGFRAU]\n- **Before writing, a script checks the bounds**: `start` < `end`, they are measurement instants, and no sensor is touched there outside its usual rejections, references included. [cross Obstruction, WILDSTRUBEL]\n- **The end of a nuisance specific to a target is read on its `corr_x` and `corr_y`, against its level before, over several nights**: not on the return of its `error_value`; without a return, the label runs to the end of the batch; without a level before, it ends where the curves stop changing. [cross Target issue, NORDEND]\n- **A return ends where the curve stops coming back**: not at midnight; a plateau is not a return. [LENZSPITZE]\n- **A label goes to the end of the batch only if points are still missing or moving there**: otherwise it ends at the return. [cross Displacement]\n- **A lasting jump is bounded on the jump**: from the measurement before to the measurement after the one where the new level is reached; hidden in an outage, on the outage and the first measurement after; hidden under another label, at the first measurements where it is seen. [cross Displacement, expert]\n- **The bounds of a thermal cycle are read day by day, on the turning points of the pose and of the `corr`**: never at midnight or at a fixed hour, except at the start and the end of the batch; when the pose is noisy, on its hourly median. [cross Thermal displacement, FLORIDA, SNCF01]\n- **The camera cycle starts at the morning turning point**: the first instant when the tilt and the pan leave their end-of-night level without coming back, the later of the two; not the fast part of the movement, nor the first deviation of `days.py --bounds`; a deviation of a single rate step from the bound placed stays within the uncertainty. [cross Thermal displacement, NORDEND, finishing nordend]\n- **It ends at the later of the two returns, the pose on its main axes and the curves at their night level**: an axis returns to the level where it then stays, not under a threshold set on the night, which may differ; the slow relaxation of a secondary axis (often the scale) does not push the end back, as in the expert's labels; without rest, the cycle ends at the next start and the labels follow one another. [cross Thermal displacement, NORDEND, WILDSTRUBEL, expert, finishing niederhorn, finishing wildstrubel]\n- **A nuisance at night stops the cycle only if it distorts the pose**: a reference rejected, discarded, or that drifts against the targets (`overview.py --rigid`); a target bothered alone does not stop it. [finishing divers, finishing nordend]\n- **A gap does not cut a cycle visible on both sides** (so the gaps of one or two measurements); otherwise, a gap or a jump at night stops it: the cycle ends at the rest of the pose if it comes before, otherwise at the last measurement before the gap or at the measurement before the jump. [finishing divers, finishing nordend]\n- **Before extending a cycle over a night that moves, read the housing temperature and the references**: it must still drop there, or the pose follow its usual profile; a pose that moves at flat temperature, with a reference that drifts, is the nuisance of that reference, not the thermal return. [finishing divers]\n- **The reference night of a cycle is chosen calm, not by civil day**: when the pose comes back all night, a start is dated at the turning point, not at the first deviation from that night. [SNCF01, cross Thermal displacement]\n- **The phases of the structure are cut at the turning points**: when the trough is flat for several hours, the cut is placed in the flat and the two phases touch. [JUNGFRAU, cross Thermal displacement]\n- **An event that touches the edge of the batch extends the label of the neighboring batch, if there is one**: it is not redone; otherwise, it starts or ends at the batch edge. [JUNGFRAU, cross Target issue]\n\n## 3. A single event","numLines":357,"startLine":1,"totalLines":422,"truncatedByTokenCap":true}},"tool_result_meta":[{"id":"toolu_017RJJ3rkQYvkbaXq518356P","permission_decision":{"decision":"accept","source":"config","reason_type":"rule"}}]}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98n1nnueGR4pjfB2gt2","type":"message","role":"assistant","content":[{"type":"tool_use","id":"toolu_01RdrGGPsTPyhzPtYU3iGrRS","name":"Read","input":{"file_path":"/home/maxime/.claude/projects/-home-maxime-aimsight-app/b1dece15-7ed2-440e-993c-de42f2e6a4bf/tool-results/bi79iapup.txt"},"caller":{"type":"direct"}}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":1886,"cache_read_input_tokens":11636,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":1886},"output_tokens":16,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"c99097a7-fedb-4ba3-bf91-ff45e7c96ea7","timestamp":"2026-11-17T20:31:07.041Z","request_id":"req_011Ch98n1ZuGw3Ugyh4DMV2R","wire_tool_inputs":{"toolu_01RdrGGPsTPyhzPtYU3iGrRS":{"file_path":"/home/maxime/.claude/projects/-home-maxime-aimsight-app/b1dece15-7ed2-440e-993c-de42f2e6a4bf/tool-results/bi79iapup.txt"}}}
-{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_01RdrGGPsTPyhzPtYU3iGrRS","type":"tool_result","content":"1\t# The label families\n2\t\n3\tOne 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.\n4\t\n5\t| Key | Detector | What happens | For the client |\n6\t|---|---|---|---|\n7\t| `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 |\n8\t| `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 |\n9\t| `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 |\n10\t| `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 |\n11\t| `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 |\n12\t| `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 |\n13\t\n14\tFor 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:\n15\t\n16\t| Variety | For the client |\n17\t|---|---|\n18\t| `Poor visibility reduced` | use the data over the range with care: they are less precise |\n19\t| `Heat shimmer` | nothing to do: the small fast wiggles are not movement |\n20\t| `Camera thermal movement` | nothing to do: this is not a movement of the structure |\n21\t| `Brief obstruction` | ignore this single point on the curves |\n22\t| `Sudden jump, back to normal` | look at the images: the cause is not established |\n23\t| `Lasting shift` | check whether the structure moved: look at the images |\n24\t| `Jump, not back yet` | check whether the structure moved: look at the images |\n25\t| `Slow drift` | keep watching it |\n26\t\n27\t## The boundaries\n28\t\n29\t- **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.\n30\t- **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.\n31\t- **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 Displacement without a cause. The description says it is a reference, and that the targets move together because of it.\n32\t- **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.\n33\t- **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.\n34\t- **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.\n35\t- **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.\n36\t- **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.\n37\t- **Target issue or Displacement**: a changed configuration (moved sensors, changed starting position, setting) is Target issue; the jump that results is not a Displacement.\n38\t\n39\t## The phenomena\n40\t\n41\tWhat has been labelled so far, one line each: **name**: what is seen; how to tell it from its neighbours. The hypotheses to weigh for a moment of a range; the cases, their bounds and descriptions come from the labels, through `precedents.py`. A phenomenon not in this list is labelled too, without forcing a cause.\n42\t\n43\t### No data\n44\t- **A gap common to several stations**: the measurements missing at the same minutes on every station measuring then; a cause outside the stations, not established. Read the other stations before the station's metrics.\n45\t- **The station runs, the measurement is missing**: one station, powered and communicating (synchronization, image or `DB_not_uploaded` at the missing instant), misses a measurement.\n46\t- **The station goes silent on its own, for a long time**: no measurements, no images, no metrics, for hours or days, without the signature of a lack of energy.\n47\t- **The station shuts down for lack of energy**: the battery does not last the night; voltage below the knee before the gap, a restart with the solar charge.\n48\t- **Mains cut: the station runs on its battery**: a station on mains stops, or comes back on a drawn-down battery, until the mains return.\n49\t\n50\t### Obstruction\n51\t- **A pass-by hides the targets for the length of one measurement**: a train, a vehicle, passers-by: the hidden targets rejected for one acquisition, back at the next; a reference behind it makes the whole base jump. Insects give the same signature: only the image tells.\n52\t- **A target left under the threshold latches onto a headlight, a reflection or another spot**: during a pass-by, one false point kept in the curve, without rejection; `dominance` rises on a recent camera.\n53\t- **A vehicle or machine that stays in front of the targets**: the same sensors hidden for hours or days, sometimes a reference; one label per parking.\n54\t- **An animal very close to the lens**: lit at night, it hides part or all of the scene for one or two measurements; a spider is not its web.\n55\t- **A plant shaken by the wind in front of a target**: one target, at times, on windy days; it grows over weeks.\n56\t- **An obstacle covers part of the spot**: an obstacle, or a mark on the glass in front of one spot, hides part of it for hours or weeks: the measured centre slides; the sliding is the artifact, the jump back is the return to normal.\n57\t\n58\t### Visibility\n59\t- **Rain**: drops in front of the lens veil the spots during the hours of rain, at night above all; the references, higher up, may suffer less.\n60\t- **The soiled glass**: after rain, drop marks veil part of the scene durably; under a single spot, it is an obstacle (Obstruction).\n61\t- **Visibility drops over the whole scene, without an obstacle**: fog, condensation, a milky dawn: flux down on all sensors, `error_value` up, rejections; raw positions without a step.\n62\t- **Part of the scene goes dark at night**: the distant spots, or a few neighbours at the edge of the group, lose their light, nothing in front.\n63\t- **A reference loses its brightness, without an obstacle**: one or two references weaken and shrink, most often at night, then come back on their own; the centre does not move.\n64\t- **Atmospheric turbulence**: by day, air heated above a road, ballast or rails makes the spots tremble: a fast noise, `error_value` up. Without the `error_value` rising, an agitation of the pose is the camera heating (Thermal displacement).\n65\t- **The sun in the field or behind a spot**: the sun enters the field, or lights the background of a target or a reference as bright as it: rejections at the same hours on sunny days only.\n66\t- **A faint spot lost when the light is missing**: a faint target crosses its threshold at the change from night to day, under an overcast sky or in a noisy night image; its rejections come with the light, not every day (else Target issue).\n67\t\n68\t### Target issue\n69\t- **A target rejected at all its measurements**: never accepted, whatever the weather.\n70\t- **A target right at the threshold, the whole batch**: its `error_value` keeps crossing the threshold, with many own rejections.\n71\t- **A target rejected every night or every day**: under the station's ordinary regime (floodlight, daylight), at the same hours, whatever the weather.\n72\t- **A target that degrades, and sometimes recovers**: seen worse and worse from a date on; back only after weeks, if ever, often at another level.\n73\t- **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.\n74\t\n75\t### Thermal displacement\n76\t- **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.\n77\t- **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.\n78\t- **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.\n79\t- **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).\n80\t\n81\t### Displacement\n82\t- **A step of the camera that the compensation does not erase**: the camera moves at once and a remainder passes into the curves; a step that leaves nothing beyond the noise is not labelled.\n83\t- **The camera tilts little by little**: over weeks, the tilt rises and the compensation corrects some targets better than others; the targets do not move relative to each other.\n84\t- **The base changes without a reference lost**: all references kept, the distance between them changes a little; all targets shift together without moving in the image.\n85\t- **A real movement of the structure**: targets shift and stay, with references and pose stable and a good image; if the camera and references moved too, the amplitude is not established.\n86\t- **Targets move slowly, alone, then come back**: one or a few targets, hours or days, without a camera movement or an obstructed view.\n87\t- **A target or a small group jumps and stays shifted**: at once, to another level, without the camera moving or a visible cause.\n88\t- **A step taken during a measurement outage**: on resumption, targets do not find their previous level.\n89\t\n90\t### Family of the cause\n91\t- **A reference dropped: the base changes**: one reference above its threshold, dropped: all targets jump together, the reprojection error at zero; the family is that of what hindered the reference.\n92\t- **Two references lost: the camera is blind**: two of three references dropped one after the other: every point of the range is invalid; the family of the cause.\n93\t- **A compensation on two references**: a station built with two, or having lost one for good: the slightest difference between them passes into all the targets; the family of what disturbs them.\n94\t- **A spider web in front of the lens**: Visibility when it veils the image, Obstruction when a thread hides a few spots; no signal at all is possible, only the images show it.\n95\t\n96\t## What is not labeled\n97\t\n98\t- 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.\n99\t- 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.\n100\t- 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).\n101\t- The expert can say so with the key `None` (labeling tool: \"None (curves untouched)\"): such a label is not counted.\n102\t# Reading rules\n103\t\n104\tWhat the data of a station mean: where each cause enters the measurement, what it touches, and the rules and false friends that the expert and the reviewed labels have established. What the files and columns are: `tools/DATA.md`. How to place a label: `labeling-rules.md`; the families and their boundaries: `families.md`, whose rules are not repeated here.\n105\t\n106\tCases are cited by label id (`NORDEND-80`, in `auto/.jsonl`; `precedents.py` finds others); `[expert]`: the expert's word, from a label that is not in `auto/`. Maintained by hand.\n107\t\n108\t## 1. How a measurement is made\n109\t\n110\t1. **The scene**: targets on the structure, references around it, assumed fixed.\n111\t2. **The view**: the air between the camera and the targets, and what can pass or settle in front.\n112\t3. **The image**: the lens, then the capture (IRON, or DIFF which combines several captures).\n113\t4. **The pattern measurement**: each sensor is found in the image: `x`, `y`, `error_value`; on recent cameras, the image quality. Above `error_threshold`, the measurement is rejected.\n114\t5. **The compensation**: a 2D similarity (translation, rotation, scale) fitted on the references (`global_ref`) gives the camera pose (`pan`, `tilt`, `rotation`, `scale`, `sigma0`) and, per reference, `reproj_err` and `inlier`.\n115\t6. **The corrected curve**: `corr_x`, `corr_y`, the position of the target once the estimated camera movement is removed.\n116\t\n117\tA displayed value is the end of this chain: find the stage that gave way.\n118\t\n119\t## 2. Where each cause enters, and what it touches\n120\t\n121\t| Stage | Cause | What it touches | Time | Witnesses |\n122\t|---|---|---|---|---|\n123\t| View (air) | fog, rain, condensation: **reduced visibility** | a homogeneous drop in flux; `error_value` rises, rejections; raw positions without a step | hours | quality (`flux`), images |\n124\t| View (air) | **heat haze** (turbulence) | a fast noise; only when the structure really heats up; not under a bridge | the hot hours | temperature, `error_value` by day versus night |\n125\t| View (obstacle) | object, leaves, snow on a target: **occultation**; a passage | one or a few targets; on a recent camera, their flux cut, the neighbours intact (LENZSPITZE-9); a passage: one measurement | from one measurement to weeks | quality, images |\n126\t| Target | problem target (badly oriented, dirty, glued) | one target, lastingly | days and more | `error_value` of the target alone |\n127\t| Lens | **thermal deformation of the optics** (sun on the station) | the whole image deforms, which a similarity cannot represent | short: follows the sun on the station | housing temperature |\n128\t| Camera and mount | **expansion of the mount**; wind, jolt, shock | raw positions of all sensors, references included, together; the compensation absorbs it (`corr` flat) or badly: `corr` follows the inflections of the camera movement | specific to the mount | camera pose, housing temperature |\n129\t| References | **reference hidden or less well seen** | the transformation is redone without it: points shifted at once, often grouped in one part of the image, the shift growing with the distance to the references; back when it returns: reversible | the time of the nuisance | `error_value`, `reproj_err` of the references, `sigma0`, camera pose |\n130\t| References | a reference moved | the `corr` of the targets shifted lastingly | lasting | `reproj_err` of the reference |\n131\t| Structure | **thermal expansion of the structure** | `corr`, an amplitude specific to each target, references stable | the longest: slow heating, late cooling | no air temperature (section 3) |\n132\t| Structure | real movement | `corr` of one or several targets, which lasts; references and pose stable, good image quality | lasting | all of the above, at calm |\n133\t\n134\t**A jump that returns** to normal is not serious: the return is what makes it benign. Saying \"jump\" is not enough; the question is its cause, quite often a reference hidden or less well seen.\n135\t\n136\t## 3. Thermal effects\n137\t\n138\t- **Three movement effects**: the lens, the mount, the structure, told apart by their heating and cooling times; the structure is the slowest. Heat haze is apart: a noise, not a movement.\n139\t- **The cases cross**: a camera on a bridge has two structures, the one that carries it (the mount) and the one it monitors.\n140\t- **In waves**: expansion, then contraction; often stronger in Y than in X, depending on the orientation.\n141\t- **The kind of structure says whether a thermal movement is possible**: a bridge yes; a rock face, too massive, or a road, no: the movement is then that of the camera (`stations.md`). [expert, WILDSTRUBEL-102]\n142\t- **The camera can move through a thermal effect at a different rhythm from the structure**, not having the same heating time. [expert]\n143\t- **The temperature that counts is that of the camera housing, not that of the air around**, even sheltered. The temperatures available are those of the compute board (`sensor_*_deg_c`), inside the housing, heated by the sun and by the computing, as hourly means: a witness for the lens and the mount, not for the structure nor the air. `temperature_deg_c`, on a few stations: unknown sensor. [expert, BREITHORN-14]\n144\t- **A change of regime is understood through the temperature**: look at it. [expert]\n145\t- **The direction of a thermal movement is read on the housing temperature, not on the hour**; when the scale of the camera follows it, the effect is on the camera. [NORDEND-155, CLARIDEN-13]\n146\t\n147\t## 4. Gaps\n148\t\n149\t- **A gap is not necessarily an outage**: acquisition, transmission, ingestion and display are distinct layers.\n150\t - At the end of a file, empty values can be only a synchronization delay (`last_sync`): a delay only if the other stations do not have their data yet either.\n151\t - At the start of a file, empty values precede the first measurement: not an outage.\n152\t - A gap surrounded by a normal voltage is not an energy problem.\n153\t- **A gap is read with the other stations and the metrics** (the boundary \"A gap\" of `families.md`). [JUNGFRAU-52, NORDEND-50, WILDSTRUBEL-201, CLARIDEN-19]\n154\t- **A power cut leaves a signature**: the voltage below the knee (about 12.8 V) just before or just after the gap; the temperature drops during the gap more than at the same hours on nights without a gap, which alone does not settle it (a common gap can do the same, an outage that comes back after sunrise shows nothing).\n155\t- **A station on mains that comes back with its battery drawn down has lost the mains.**\n156\t- **A `NaN` or `inf` value** in an export is an absence of measurement.\n157\t\n158\t## 5. Reading rules\n159\t\n160\t- **What moves in the image is read before the cause, on the raw positions against the overall movement** (`overview.py --rigid`): the targets do not move relative to each other, it is the camera [BREITHORN-2]; targets move alone, a movement is not excluded [CLARIDEN-14]; nothing moves and the curves jump, it is the base or the configuration [WILDSTRUBEL-136, CLARIDEN-38].\n161\t- **A jump is judged against the neighbours**: if it brings the target back toward them, it is a return to normal, and the artifact was before; if it takes it away from them, it is to be treated quite differently. [expert]\n162\t- **A level is also judged against the past of the target, over weeks**: a jump that brings it back to an old level is a return. [NORDEND-94, NORDEND-169]\n163\t- **A high `error_value` is not a problem in itself: its variations count.** [expert]\n164\t- **A very stable `error_value` says the targets stay well visible**: while they move, it rather suggests a poor compensation than an obstruction of the view. [expert]\n165\t- **A rejected measurement is removed from the display, not a measurement just under the threshold**: a target left under the threshold keeps its jump. [expert, NIEDERHORN-13]\n166\t- **At least three references are needed; dropping a single one is enough to distort everything**: a kind of triangulation. **The position of the targets rests on the network of references**: references badly seen, targets badly anchored. [expert]\n167\t- **The reprojection error says how many references hold**: at zero, only two remain, a very bad sign, not a perfect measurement; absent, only one, and no measurement is possible. Except on a station built with two references, where it is always at zero. [JUNGFRAU-22, FLORIDA-4, expert]\n168\t- **The pose of the camera is reliable only if the references hold**: a reference rejected, dropped or sliding against the targets distorts it; a single hindered target does not. [FLORIDA-58]\n169\t- **A drift specific to a few targets that follows the camera, on the same dates, is the scene deforming with it**, not a second movement; it is separate only if it has its own dates. [NEBRASKA-6, NEBRASKA-5]\n170\t- **Neighbouring cameras are read together**: the same movement, the same loss or the same gap on the cameras of one building have a common cause; what touches only one is on its line of sight. [MICHIGAN-3, BREITHORN-20]\n171\t\n172\t## 6. False friends\n173\t\n174\t- **Jumps of many targets, all in the same direction, are not a movement** when they fall at the reference switches: raw positions without a step, daily cycle that continues. [expert]\n175\t- **A target that slides slowly away from its neighbours is not moving** when its `error_value` rises with the sliding and a step brings it back toward them. [expert]\n176\t- **A rise over several days is not necessarily a real movement**: it may follow a lasting drop in temperature. [expert]\n177\t- **Corrections stuck at zero are not a failure**: a twin of a reference. [expert]\n178\t- **No signal does not mean no obstruction**: only the images show the web. [expert]\n179\t- **A web is not the spider**: the web veils in part for hours or days; the spider hides everything for the length of one measurement. [expert]\n180\t- **References that do not move in the rain do not contradict the rain**: higher up, they suffer it less. [NIEDERHORN-12]\n181\t- **The step of a real movement is not its amplitude** when the camera and the references have moved too. [expert]\n182\t- **A swarm of insects is not a train**: same signature; only the image tells them apart. [NIEDERHORN-66]\n183\t- **In a tunnel, a temperature drop at the same moment does not make a thermal effect**: the bump of a group comes with the `error_value` and returns before the scale of the camera. [CLARIDEN-12, CLARIDEN-13]\n184\t- **The return of the `error_value` is not the end of an obstruction**: after a mark on the glass, the curves stay shifted. [NORDEND-169]\n185\t- **A spot on a thumbnail that follows the measurement is not necessarily there**: the frame follows a measurement perhaps latched onto the neighbour; only a fixed frame shows it. [FLORIDA-43]\n186\t\n187\t## 7. Non-negotiable rules\n188\t\n189\t- Judge nothing on a binary `inlier`: use continuous weights, residuals, influence.\n190\t- Neither `sigma0` alone nor the number of references is ever a sufficient criterion.\n191\t- The image quality of a target is not the quality of the reference network; a small residual is not a well-constrained transformation.\n192\t- A common-mode movement is not a structural movement; coherent references are not physically fixed references: the camera cannot prove that a network moving as a block is fixed.\n193\t\n194\t## 8. Lessons from cases outside the labels\n195\t\n196\t- **When everything moves together, the measurements alone do not separate the structure from the camera** (Barcelona, a bridge whose vault subsided: the references, the camera and the structure moved; the expert called it a real movement, confirmed by other monitoring systems of the site). An unstable compensation then distorts the amplitude of a real movement: the movement is reported, its amplitude is not established. [expert]\n197\t- **Two prisms too close interfere**: a 24 h cycle correlated between the two, or isolated peaks on one target at a time, too large for the structure, with no obstruction on the images; a neighbour much brighter than the others. On a recent camera, `dominance` shows it. [client report]\n198\t- **Vegetation grows over days and weeks**: a partial, progressive occultation, not reversible from one measurement to the next like a passage; the hardest obstruction according to the expert. [client report]\n199\t- **References masked (two of four, by vegetation)**: a 24 h cycle on pan, roll and tilt, badly compensated, is then not a movement of the camera but a base too weak for the transformation. [client report]\n200\t- **A target of low contrast**: by day, square waves on one axis, back at night, `error_value` rising by day without reaching the threshold. [client report]\n201\t- **Snow**: noise and apparent movements on all sensors and the camera, a brief loss of data, the signal quickly back. [client report]\n202\t# The stations\n203\t\n204\tWhat each station is: its structure, its camera, its references, its neighbours. Context for reading a station's data, not a rule: what happens at a station is in its labels (`auto/.jsonl`, `precedents.py`). The kind of structure says whether a thermal movement of the structure is possible (`reading-rules.md`, section 3). Cases are cited by label id; `[expert]`: the expert's word. Maintained by hand: a new station gets its row when its first range is analysed.\n205\t\n206\t| Station | Structure | Camera | References | Neighbouring cameras |\n207\t|---|---|---|---|---|\n208\t| BREITHORN | in a building (a factory, indoors) [expert] | one measurement every four hours; COLJ19 and POUI19 much closer to the camera than the other targets [expert]; the camera nods forward over October, compensation incomplete [expert] | REFH22, REFPOU22 among the sensors at the bottom of the image | MICHIGAN and NEBRASKA, in the same building: a drift common to the three [BREITHORN-2] |\n209\t| CLARIDEN | a tunnel under construction, with other measurement systems [expert] | images always dark; on mains | four references, D-302-C, PR-291, PR-293, PR-295; PR-284 is a local reference, read as a target; D-302-B and PR_BG on the same prism [CLARIDEN-38] | — |\n210\t| FLORIDA | — | — | two references only, p1_r and r1_r, each with its twin target (Sellette 3, Pont Ernen) [expert] | its one-measurement gaps at night fall at the same instants as SNCF01's |\n211\t| JUNGFRAU | a bridge, which rises as it cools [expert] | under the deck, fixed to the bridge | three references off the bridge, REF_D, REF_G, REF_CT | — |\n212\t| LENZSPITZE | a railway seen from under a bridge, a work site and machines next to it | recent camera, with image quality; `x`, `y` relative in the export (`tools/DATA.md`); only `temperature_deg_c` is filled | nine references, including the distant 8011 to 8014 | — |\n213\t| MICHIGAN | in the same building as BREITHORN, indoors [expert] | one measurement every four hours | two references since the loss of REFPOU22 on 09.10 [MICHIGAN-3]; COLH21' and REFH22' on the same point until 05.10 [MICHIGAN-1] | BREITHORN, NEBRASKA: lost a reference at the same measurement as NEBRASKA |\n214\t| NEBRASKA | in the same building as BREITHORN [expert] | one measurement every four hours | two references since the loss of REFCOLH22 [NEBRASKA-2] | BREITHORN, MICHIGAN |\n215\t| NIEDERHORN | railway tracks | floodlight at night | higher up, on the road above the tracks (PWD_REF08 to PWD_REF12) | — |\n216\t| NORDEND | a quarry: a rock face too massive to move with the temperature [expert] | infrared lighting at night; DIFF images | three references, CTR02, CTR03, CTR04; CTR01 is a local reference, read as a target | — |\n217\t| SNCF01 | a masonry wall along railway tracks | no system metrics, hence no temperature | three references, BG.3.1, R1, R2 | FLORIDA (gaps at the same instants) |\n218\t| WILDSTRUBEL | a road, in a town [WILDSTRUBEL-102] | solar battery | six references, R1 and R2 at the edge of the road; R3 invisible by day [WILDSTRUBEL-130] | — |\n219\t"}]},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"255b0b23-2688-439a-abe7-daf88c42d448","timestamp":"2026-11-17T20:31:07.275Z","tool_use_result":{"type":"text","file":{"filePath":"/home/maxime/.claude/projects/-home-maxime-aimsight-app/b1dece15-7ed2-440e-993c-de42f2e6a4bf/tool-results/bi79iapup.txt","content":"# The label families\n\nOne 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.\n\n| Key | Detector | What happens | For the client |\n|---|---|---|---|\n| `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 |\n| `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 |\n| `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 |\n| `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 |\n| `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 |\n| `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 |\n\nFor 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:\n\n| Variety | For the client |\n|---|---|\n| `Poor visibility reduced` | use the data over the range with care: they are less precise |\n| `Heat shimmer` | nothing to do: the small fast wiggles are not movement |\n| `Camera thermal movement` | nothing to do: this is not a movement of the structure |\n| `Brief obstruction` | ignore this single point on the curves |\n| `Sudden jump, back to normal` | look at the images: the cause is not established |\n| `Lasting shift` | check whether the structure moved: look at the images |\n| `Jump, not back yet` | check whether the structure moved: look at the images |\n| `Slow drift` | keep watching it |\n\n## The boundaries\n\n- **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.\n- **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.\n- **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 Displacement without a cause. The description says it is a reference, and that the targets move together because of it.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **Target issue or Displacement**: a changed configuration (moved sensors, changed starting position, setting) is Target issue; the jump that results is not a Displacement.\n\n## The phenomena\n\nWhat has been labelled so far, one line each: **name**: what is seen; how to tell it from its neighbours. The hypotheses to weigh for a moment of a range; the cases, their bounds and descriptions come from the labels, through `precedents.py`. A phenomenon not in this list is labelled too, without forcing a cause.\n\n### No data\n- **A gap common to several stations**: the measurements missing at the same minutes on every station measuring then; a cause outside the stations, not established. Read the other stations before the station's metrics.\n- **The station runs, the measurement is missing**: one station, powered and communicating (synchronization, image or `DB_not_uploaded` at the missing instant), misses a measurement.\n- **The station goes silent on its own, for a long time**: no measurements, no images, no metrics, for hours or days, without the signature of a lack of energy.\n- **The station shuts down for lack of energy**: the battery does not last the night; voltage below the knee before the gap, a restart with the solar charge.\n- **Mains cut: the station runs on its battery**: a station on mains stops, or comes back on a drawn-down battery, until the mains return.\n\n### Obstruction\n- **A pass-by hides the targets for the length of one measurement**: a train, a vehicle, passers-by: the hidden targets rejected for one acquisition, back at the next; a reference behind it makes the whole base jump. Insects give the same signature: only the image tells.\n- **A target left under the threshold latches onto a headlight, a reflection or another spot**: during a pass-by, one false point kept in the curve, without rejection; `dominance` rises on a recent camera.\n- **A vehicle or machine that stays in front of the targets**: the same sensors hidden for hours or days, sometimes a reference; one label per parking.\n- **An animal very close to the lens**: lit at night, it hides part or all of the scene for one or two measurements; a spider is not its web.\n- **A plant shaken by the wind in front of a target**: one target, at times, on windy days; it grows over weeks.\n- **An obstacle covers part of the spot**: an obstacle, or a mark on the glass in front of one spot, hides part of it for hours or weeks: the measured centre slides; the sliding is the artifact, the jump back is the return to normal.\n\n### Visibility\n- **Rain**: drops in front of the lens veil the spots during the hours of rain, at night above all; the references, higher up, may suffer less.\n- **The soiled glass**: after rain, drop marks veil part of the scene durably; under a single spot, it is an obstacle (Obstruction).\n- **Visibility drops over the whole scene, without an obstacle**: fog, condensation, a milky dawn: flux down on all sensors, `error_value` up, rejections; raw positions without a step.\n- **Part of the scene goes dark at night**: the distant spots, or a few neighbours at the edge of the group, lose their light, nothing in front.\n- **A reference loses its brightness, without an obstacle**: one or two references weaken and shrink, most often at night, then come back on their own; the centre does not move.\n- **Atmospheric turbulence**: by day, air heated above a road, ballast or rails makes the spots tremble: a fast noise, `error_value` up. Without the `error_value` rising, an agitation of the pose is the camera heating (Thermal displacement).\n- **The sun in the field or behind a spot**: the sun enters the field, or lights the background of a target or a reference as bright as it: rejections at the same hours on sunny days only.\n- **A faint spot lost when the light is missing**: a faint target crosses its threshold at the change from night to day, under an overcast sky or in a noisy night image; its rejections come with the light, not every day (else Target issue).\n\n### Target issue\n- **A target rejected at all its measurements**: never accepted, whatever the weather.\n- **A target right at the threshold, the whole batch**: its `error_value` keeps crossing the threshold, with many own rejections.\n- **A target rejected every night or every day**: under the station's ordinary regime (floodlight, daylight), at the same hours, whatever the weather.\n- **A target that degrades, and sometimes recovers**: seen worse and worse from a date on; back only after weeks, if ever, often at another level.\n- **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.\n\n### Thermal displacement\n- **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.\n- **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.\n- **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.\n- **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).\n\n### Displacement\n- **A step of the camera that the compensation does not erase**: the camera moves at once and a remainder passes into the curves; a step that leaves nothing beyond the noise is not labelled.\n- **The camera tilts little by little**: over weeks, the tilt rises and the compensation corrects some targets better than others; the targets do not move relative to each other.\n- **The base changes without a reference lost**: all references kept, the distance between them changes a little; all targets shift together without moving in the image.\n- **A real movement of the structure**: targets shift and stay, with references and pose stable and a good image; if the camera and references moved too, the amplitude is not established.\n- **Targets move slowly, alone, then come back**: one or a few targets, hours or days, without a camera movement or an obstructed view.\n- **A target or a small group jumps and stays shifted**: at once, to another level, without the camera moving or a visible cause.\n- **A step taken during a measurement outage**: on resumption, targets do not find their previous level.\n\n### Family of the cause\n- **A reference dropped: the base changes**: one reference above its threshold, dropped: all targets jump together, the reprojection error at zero; the family is that of what hindered the reference.\n- **Two references lost: the camera is blind**: two of three references dropped one after the other: every point of the range is invalid; the family of the cause.\n- **A compensation on two references**: a station built with two, or having lost one for good: the slightest difference between them passes into all the targets; the family of what disturbs them.\n- **A spider web in front of the lens**: Visibility when it veils the image, Obstruction when a thread hides a few spots; no signal at all is possible, only the images show it.\n\n## What is not labeled\n\n- 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.\n- 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.\n- 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).\n- The expert can say so with the key `None` (labeling tool: \"None (curves untouched)\"): such a label is not counted.\n# Reading rules\n\nWhat the data of a station mean: where each cause enters the measurement, what it touches, and the rules and false friends that the expert and the reviewed labels have established. What the files and columns are: `tools/DATA.md`. How to place a label: `labeling-rules.md`; the families and their boundaries: `families.md`, whose rules are not repeated here.\n\nCases are cited by label id (`NORDEND-80`, in `auto/.jsonl`; `precedents.py` finds others); `[expert]`: the expert's word, from a label that is not in `auto/`. Maintained by hand.\n\n## 1. How a measurement is made\n\n1. **The scene**: targets on the structure, references around it, assumed fixed.\n2. **The view**: the air between the camera and the targets, and what can pass or settle in front.\n3. **The image**: the lens, then the capture (IRON, or DIFF which combines several captures).\n4. **The pattern measurement**: each sensor is found in the image: `x`, `y`, `error_value`; on recent cameras, the image quality. Above `error_threshold`, the measurement is rejected.\n5. **The compensation**: a 2D similarity (translation, rotation, scale) fitted on the references (`global_ref`) gives the camera pose (`pan`, `tilt`, `rotation`, `scale`, `sigma0`) and, per reference, `reproj_err` and `inlier`.\n6. **The corrected curve**: `corr_x`, `corr_y`, the position of the target once the estimated camera movement is removed.\n\nA displayed value is the end of this chain: find the stage that gave way.\n\n## 2. Where each cause enters, and what it touches\n\n| Stage | Cause | What it touches | Time | Witnesses |\n|---|---|---|---|---|\n| View (air) | fog, rain, condensation: **reduced visibility** | a homogeneous drop in flux; `error_value` rises, rejections; raw positions without a step | hours | quality (`flux`), images |\n| View (air) | **heat haze** (turbulence) | a fast noise; only when the structure really heats up; not under a bridge | the hot hours | temperature, `error_value` by day versus night |\n| View (obstacle) | object, leaves, snow on a target: **occultation**; a passage | one or a few targets; on a recent camera, their flux cut, the neighbours intact (LENZSPITZE-9); a passage: one measurement | from one measurement to weeks | quality, images |\n| Target | problem target (badly oriented, dirty, glued) | one target, lastingly | days and more | `error_value` of the target alone |\n| Lens | **thermal deformation of the optics** (sun on the station) | the whole image deforms, which a similarity cannot represent | short: follows the sun on the station | housing temperature |\n| Camera and mount | **expansion of the mount**; wind, jolt, shock | raw positions of all sensors, references included, together; the compensation absorbs it (`corr` flat) or badly: `corr` follows the inflections of the camera movement | specific to the mount | camera pose, housing temperature |\n| References | **reference hidden or less well seen** | the transformation is redone without it: points shifted at once, often grouped in one part of the image, the shift growing with the distance to the references; back when it returns: reversible | the time of the nuisance | `error_value`, `reproj_err` of the references, `sigma0`, camera pose |\n| References | a reference moved | the `corr` of the targets shifted lastingly | lasting | `reproj_err` of the reference |\n| Structure | **thermal expansion of the structure** | `corr`, an amplitude specific to each target, references stable | the longest: slow heating, late cooling | no air temperature (section 3) |\n| Structure | real movement | `corr` of one or several targets, which lasts; references and pose stable, good image quality | lasting | all of the above, at calm |\n\n**A jump that returns** to normal is not serious: the return is what makes it benign. Saying \"jump\" is not enough; the question is its cause, quite often a reference hidden or less well seen.\n\n## 3. Thermal effects\n\n- **Three movement effects**: the lens, the mount, the structure, told apart by their heating and cooling times; the structure is the slowest. Heat haze is apart: a noise, not a movement.\n- **The cases cross**: a camera on a bridge has two structures, the one that carries it (the mount) and the one it monitors.\n- **In waves**: expansion, then contraction; often stronger in Y than in X, depending on the orientation.\n- **The kind of structure says whether a thermal movement is possible**: a bridge yes; a rock face, too massive, or a road, no: the movement is then that of the camera (`stations.md`). [expert, WILDSTRUBEL-102]\n- **The camera can move through a thermal effect at a different rhythm from the structure**, not having the same heating time. [expert]\n- **The temperature that counts is that of the camera housing, not that of the air around**, even sheltered. The temperatures available are those of the compute board (`sensor_*_deg_c`), inside the housing, heated by the sun and by the computing, as hourly means: a witness for the lens and the mount, not for the structure nor the air. `temperature_deg_c`, on a few stations: unknown sensor. [expert, BREITHORN-14]\n- **A change of regime is understood through the temperature**: look at it. [expert]\n- **The direction of a thermal movement is read on the housing temperature, not on the hour**; when the scale of the camera follows it, the effect is on the camera. [NORDEND-155, CLARIDEN-13]\n\n## 4. Gaps\n\n- **A gap is not necessarily an outage**: acquisition, transmission, ingestion and display are distinct layers.\n - At the end of a file, empty values can be only a synchronization delay (`last_sync`): a delay only if the other stations do not have their data yet either.\n - At the start of a file, empty values precede the first measurement: not an outage.\n - A gap surrounded by a normal voltage is not an energy problem.\n- **A gap is read with the other stations and the metrics** (the boundary \"A gap\" of `families.md`). [JUNGFRAU-52, NORDEND-50, WILDSTRUBEL-201, CLARIDEN-19]\n- **A power cut leaves a signature**: the voltage below the knee (about 12.8 V) just before or just after the gap; the temperature drops during the gap more than at the same hours on nights without a gap, which alone does not settle it (a common gap can do the same, an outage that comes back after sunrise shows nothing).\n- **A station on mains that comes back with its battery drawn down has lost the mains.**\n- **A `NaN` or `inf` value** in an export is an absence of measurement.\n\n## 5. Reading rules\n\n- **What moves in the image is read before the cause, on the raw positions against the overall movement** (`overview.py --rigid`): the targets do not move relative to each other, it is the camera [BREITHORN-2]; targets move alone, a movement is not excluded [CLARIDEN-14]; nothing moves and the curves jump, it is the base or the configuration [WILDSTRUBEL-136, CLARIDEN-38].\n- **A jump is judged against the neighbours**: if it brings the target back toward them, it is a return to normal, and the artifact was before; if it takes it away from them, it is to be treated quite differently. [expert]\n- **A level is also judged against the past of the target, over weeks**: a jump that brings it back to an old level is a return. [NORDEND-94, NORDEND-169]\n- **A high `error_value` is not a problem in itself: its variations count.** [expert]\n- **A very stable `error_value` says the targets stay well visible**: while they move, it rather suggests a poor compensation than an obstruction of the view. [expert]\n- **A rejected measurement is removed from the display, not a measurement just under the threshold**: a target left under the threshold keeps its jump. [expert, NIEDERHORN-13]\n- **At least three references are needed; dropping a single one is enough to distort everything**: a kind of triangulation. **The position of the targets rests on the network of references**: references badly seen, targets badly anchored. [expert]\n- **The reprojection error says how many references hold**: at zero, only two remain, a very bad sign, not a perfect measurement; absent, only one, and no measurement is possible. Except on a station built with two references, where it is always at zero. [JUNGFRAU-22, FLORIDA-4, expert]\n- **The pose of the camera is reliable only if the references hold**: a reference rejected, dropped or sliding against the targets distorts it; a single hindered target does not. [FLORIDA-58]\n- **A drift specific to a few targets that follows the camera, on the same dates, is the scene deforming with it**, not a second movement; it is separate only if it has its own dates. [NEBRASKA-6, NEBRASKA-5]\n- **Neighbouring cameras are read together**: the same movement, the same loss or the same gap on the cameras of one building have a common cause; what touches only one is on its line of sight. [MICHIGAN-3, BREITHORN-20]\n\n## 6. False friends\n\n- **Jumps of many targets, all in the same direction, are not a movement** when they fall at the reference switches: raw positions without a step, daily cycle that continues. [expert]\n- **A target that slides slowly away from its neighbours is not moving** when its `error_value` rises with the sliding and a step brings it back toward them. [expert]\n- **A rise over several days is not necessarily a real movement**: it may follow a lasting drop in temperature. [expert]\n- **Corrections stuck at zero are not a failure**: a twin of a reference. [expert]\n- **No signal does not mean no obstruction**: only the images show the web. [expert]\n- **A web is not the spider**: the web veils in part for hours or days; the spider hides everything for the length of one measurement. [expert]\n- **References that do not move in the rain do not contradict the rain**: higher up, they suffer it less. [NIEDERHORN-12]\n- **The step of a real movement is not its amplitude** when the camera and the references have moved too. [expert]\n- **A swarm of insects is not a train**: same signature; only the image tells them apart. [NIEDERHORN-66]\n- **In a tunnel, a temperature drop at the same moment does not make a thermal effect**: the bump of a group comes with the `error_value` and returns before the scale of the camera. [CLARIDEN-12, CLARIDEN-13]\n- **The return of the `error_value` is not the end of an obstruction**: after a mark on the glass, the curves stay shifted. [NORDEND-169]\n- **A spot on a thumbnail that follows the measurement is not necessarily there**: the frame follows a measurement perhaps latched onto the neighbour; only a fixed frame shows it. [FLORIDA-43]\n\n## 7. Non-negotiable rules\n\n- Judge nothing on a binary `inlier`: use continuous weights, residuals, influence.\n- Neither `sigma0` alone nor the number of references is ever a sufficient criterion.\n- The image quality of a target is not the quality of the reference network; a small residual is not a well-constrained transformation.\n- A common-mode movement is not a structural movement; coherent references are not physically fixed references: the camera cannot prove that a network moving as a block is fixed.\n\n## 8. Lessons from cases outside the labels\n\n- **When everything moves together, the measurements alone do not separate the structure from the camera** (Barcelona, a bridge whose vault subsided: the references, the camera and the structure moved; the expert called it a real movement, confirmed by other monitoring systems of the site). An unstable compensation then distorts the amplitude of a real movement: the movement is reported, its amplitude is not established. [expert]\n- **Two prisms too close interfere**: a 24 h cycle correlated between the two, or isolated peaks on one target at a time, too large for the structure, with no obstruction on the images; a neighbour much brighter than the others. On a recent camera, `dominance` shows it. [client report]\n- **Vegetation grows over days and weeks**: a partial, progressive occultation, not reversible from one measurement to the next like a passage; the hardest obstruction according to the expert. [client report]\n- **References masked (two of four, by vegetation)**: a 24 h cycle on pan, roll and tilt, badly compensated, is then not a movement of the camera but a base too weak for the transformation. [client report]\n- **A target of low contrast**: by day, square waves on one axis, back at night, `error_value` rising by day without reaching the threshold. [client report]\n- **Snow**: noise and apparent movements on all sensors and the camera, a brief loss of data, the signal quickly back. [client report]\n# The stations\n\nWhat each station is: its structure, its camera, its references, its neighbours. Context for reading a station's data, not a rule: what happens at a station is in its labels (`auto/.jsonl`, `precedents.py`). The kind of structure says whether a thermal movement of the structure is possible (`reading-rules.md`, section 3). Cases are cited by label id; `[expert]`: the expert's word. Maintained by hand: a new station gets its row when its first range is analysed.\n\n| Station | Structure | Camera | References | Neighbouring cameras |\n|---|---|---|---|---|\n| BREITHORN | in a building (a factory, indoors) [expert] | one measurement every four hours; COLJ19 and POUI19 much closer to the camera than the other targets [expert]; the camera nods forward over October, compensation incomplete [expert] | REFH22, REFPOU22 among the sensors at the bottom of the image | MICHIGAN and NEBRASKA, in the same building: a drift common to the three [BREITHORN-2] |\n| CLARIDEN | a tunnel under construction, with other measurement systems [expert] | images always dark; on mains | four references, D-302-C, PR-291, PR-293, PR-295; PR-284 is a local reference, read as a target; D-302-B and PR_BG on the same prism [CLARIDEN-38] | — |\n| FLORIDA | — | — | two references only, p1_r and r1_r, each with its twin target (Sellette 3, Pont Ernen) [expert] | its one-measurement gaps at night fall at the same instants as SNCF01's |\n| JUNGFRAU | a bridge, which rises as it cools [expert] | under the deck, fixed to the bridge | three references off the bridge, REF_D, REF_G, REF_CT | — |\n| LENZSPITZE | a railway seen from under a bridge, a work site and machines next to it | recent camera, with image quality; `x`, `y` relative in the export (`tools/DATA.md`); only `temperature_deg_c` is filled | nine references, including the distant 8011 to 8014 | — |\n| MICHIGAN | in the same building as BREITHORN, indoors [expert] | one measurement every four hours | two references since the loss of REFPOU22 on 09.10 [MICHIGAN-3]; COLH21' and REFH22' on the same point until 05.10 [MICHIGAN-1] | BREITHORN, NEBRASKA: lost a reference at the same measurement as NEBRASKA |\n| NEBRASKA | in the same building as BREITHORN [expert] | one measurement every four hours | two references since the loss of REFCOLH22 [NEBRASKA-2] | BREITHORN, MICHIGAN |\n| NIEDERHORN | railway tracks | floodlight at night | higher up, on the road above the tracks (PWD_REF08 to PWD_REF12) | — |\n| NORDEND | a quarry: a rock face too massive to move with the temperature [expert] | infrared lighting at night; DIFF images | three references, CTR02, CTR03, CTR04; CTR01 is a local reference, read as a target | — |\n| SNCF01 | a masonry wall along railway tracks | no system metrics, hence no temperature | three references, BG.3.1, R1, R2 | FLORIDA (gaps at the same instants) |\n| WILDSTRUBEL | a road, in a town [WILDSTRUBEL-102] | solar battery | six references, R1 and R2 at the edge of the road; R3 invisible by day [WILDSTRUBEL-130] | — |\n","numLines":219,"startLine":1,"totalLines":219}},"tool_result_meta":[{"id":"toolu_01RdrGGPsTPyhzPtYU3iGrRS","permission_decision":{"decision":"accept","source":"config","reason_type":"rule"}}]}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98nGCTvGhhQE2Nqp68Q","type":"message","role":"assistant","content":[{"type":"tool_use","id":"toolu_0134tTNj3gJEAV6RyE4T8y5b","name":"Read","input":{"file_path":"/home/maxime/.claude/projects/-home-maxime-aimsight-app/b1dece15-7ed2-440e-993c-de42f2e6a4bf/tool-results/bbi9zey7i.txt","offset":357},"caller":{"type":"direct"}}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":33065,"cache_read_input_tokens":13522,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":33065},"output_tokens":16,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"980bf089-fea9-4e62-ac22-743ef716bac4","timestamp":"2026-11-17T20:31:12.604Z","request_id":"req_011Ch98nFxposPZEXSqDyuqn","wire_tool_inputs":{"toolu_0134tTNj3gJEAV6RyE4T8y5b":{"file_path":"/home/maxime/.claude/projects/-home-maxime-aimsight-app/b1dece15-7ed2-440e-993c-de42f2e6a4bf/tool-results/bbi9zey7i.txt","offset":357}}}
-{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_0134tTNj3gJEAV6RyE4T8y5b","type":"tool_result","content":"357\t## 3. A single event\n358\t\n359\t- **One label, a single event**: two events, even close or mixed, make two labels; an event that repeats (a passage, the rain of each night, the thermal cycle of each day) makes one label each time. [instruction]\n360\t- **The outward and return of a drift are two labels**: after each slow drift, look for its return, and do not join a descent and its rise because the description says so. [instruction, CLARIDEN, cross Displacement]\n361\t- **The thermal cycle of the camera, outward and return, is a single event per day; the structure makes two, the expansion and the contraction**: this is what the expert does; the outward-and-return rule does not apply to the camera cycle. [cross Thermal displacement, expert]\n362\t- **An event in one piece over several days makes one label**: a change of speed does not cut it, nor a tilt that continues in the same direction; only a stop followed by a return, or a change of direction, cuts it. [instruction, BREITHORN, cross Displacement]\n363\t- **A return that exceeds the starting level remains the same event**: it does not start a new movement. [LENZSPITZE]\n364\t- **A lasting jump: the label bounds the jump, the return is another label**: the step is stated in the description; a step that returns within the day remains one label (a jump then the return); two steps separated by days of plateau make two labels, even in the same direction. [cross Displacement]\n365\t- **A bump that is only the trace of a slow camera movement follows the cutting of that movement**: it is not a separate event. [cross Displacement]\n366\t- **Two gaps separated by a single measurement that came back make a single No data label; separated by two measurements or more, two**: a single measurement does not make a resumption. [cross No data, SNCF01]\n367\t- **A measurement where a target is rejected alone just after a passage is the same event; a clean measurement between the two makes two labels**: the rejection that follows is the end of the passage. [cross Obstruction]\n368\t- **Two nuisance episodes separated by a few hours where targets stay shifted make only one**: the shifted targets are still touched. [NORDEND]\n369\t- **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]\n370\t- **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]\n371\t- **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]\n372\t- **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]\n373\t- **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]\n374\t\n375\t## 4. The family\n376\t\n377\t- **A single family per label, its key in `families.md`, following its boundaries**: `Visibility`, `Obstruction`, `Thermal displacement`, `Displacement`, `Target issue`, `No data`; no other key, nor old names. [instruction, MICHIGAN, WILDSTRUBEL]\n378\t- **We decide by the signature, not by coincidence**: a temperature drop at the same moment does not make a thermal, an `error_value` that moves a little does not make a Visibility. [cross Thermal displacement, cross Visibility]\n379\t- **A same target keeps the same family from one batch to the next, and a same phenomenon on neighboring stations the same family**: otherwise the defect of a target or a site reads as two causes. [NORDEND, consistency]\n380\t- **The sun at sunrise in the field and the lit background behind a spot are the same nuisance**: same family, same way of stating the cause. [cross Visibility]\n381\t\n382\t## 5. The description\n383\t\n384\t- **As the expert would write it, in English: what is seen, the cause and how it was known, the conclusion for the client**: which targets or references with their exact names, which magnitudes, the return or not; then nothing to do, data not to be believed, or movement to monitor. [instruction]\n385\t- **Qualitative, without numeric values, even in words**: \"a tenth\", \"half a pixel\", \"a few hundredths\", \"up to almost 1\" are numbers; say \"a little\", \"clearly\", \"strongly\". [instruction, FLORIDA, JUNGFRAU]\n386\t- **The targets named are those that move the most, read instant by instant, in the right column**: not the usual list; a rejected target does not \"jump\"; the direction is stated as it is that day. [instruction, CLARIDEN, NEBRASKA, FLORIDA, NIEDERHORN]\n387\t- **A sentence taken from a model is reread on the range of each label**: the hours, the weather, the targets, the image, the return, the overshoot; a precision true for a single label is not copied. [cross Visibility, cross Thermal displacement, SNCF01, LENZSPITZE, NORDEND, FLORIDA]\n388\t- **\"Nothing on the images\", \"image without obstacle\" are written only after looking at the image of the hour**: a passage is often seen in transparency; the image cited is that of the day when it exists. [instruction, CLARIDEN, MICHIGAN, FLORIDA, WILDSTRUBEL, cross Visibility, JUNGFRAU]\n389\t- **\"No image\" is written only at an instant when the camera usually takes an image, and after searching for the file**: a station that takes one only on the hour proves nothing at the half hour, and the hourly images often fall on the minute of the measurements. [cross No data, LENZSPITZE]\n390\t- **A fact given by the expert is written \"according to the expert\", in words, without his numbers**: not \"the map knows\". [instruction, BREITHORN, MICHIGAN, NIEDERHORN]\n391\t- **The temperature is \"the housing temperature\" (of the camera)**: the column being either `sensor_*_deg_c`, or, failing that, `temperature_deg_c`; never of the air, the building, the plant, the station, the components, the camera alone, nor the name of the column; without any metric, \"no temperature is available\". [instruction, cross Thermal displacement, LENZSPITZE, NORDEND, JUNGFRAU, consistency]\n392\t- **The weather is not drawn from the housing temperature**: \"cold and overcast day\" is seen on the images. [FLORIDA]\n393\t- **The moments of the day (morning, late afternoon, night) are judged on the images, never on the UTC hour**: the station can be anywhere. Every hour written is in UTC, no numeric local hour. [cross Visibility, label map, expert's reading rule]\n394\t- **A level \"back\" or \"a little below\" is compared over several days**: a single day after may be in the middle of a thermal cycle; a night level that changes from one night to another is compared with several nights; a target rejected at night, with the nearest neighboring night where it is measured, never across a step. [instruction, MICHIGAN, cross Visibility, WILDSTRUBEL, finishing niederhorn]\n395\t- **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]\n396\t- **\"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]\n397\t- **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]\n398\t- **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]\n399\t- **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]\n400\t- **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]\n401\t- **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]\n402\t- **A lasting jump states its step**: its duration, its return or not. [cross Displacement]\n403\t- **Each label of a sequence (outward, return, resumption) names the other**: \"return of the drift of…, labeled apart\", \"without return until the end of the batch\". [cross Displacement]\n404\t- **A Target issue says when the rejections stop before the end of the label**: the end is read on the curves, the rejections may stop before. [cross Target issue]\n405\t- **A No data states the metrics and the image of the instant**: present or not, checked, for each gap. [NIEDERHORN, cross No data]\n406\t\n407\t- **On a recent camera (image quality filled, `tools/scripts/quality.py`), an occultation is written only after reading the flux of the instant**: a cut flux proves it, a full flux denies it; the hidden targets are named from their flux, each time, and a hidden target that stayed under its threshold is stated (its point stays, wrong). The metrics: `tools/DATA.md`. [LENZSPITZE quality review, D-129]\n408\t- **\"Bigger spots\" is written only after comparison with a calm day of the same image regime and reading of the `fwhm`**: a spot that has lost its light can look swollen. [LENZSPITZE quality review, D-129]\n409\t- **A jump without rejection is in no list of rejections**: on a recent camera, `quality.py --labels --outside` gives the degraded instants outside the labels; `corr` is checked at each. [LENZSPITZE quality review, D-129]\n410\t\n411\t## 6. The stated cause\n412\t\n413\t- **A cause is stated in three ways only: seen, deduced, not established**: \"seen on the image (or the thumbnail) of HH:MM\", saying what is seen there; \"deduced from…\" (the signature, the other passages seen, the curves and the camera pose), saying why it is not seen; \"not established\", with its hypotheses; or \"according to the expert\". [instruction, cross Obstruction, cross Displacement]\n414\t- **A cause deduced from a known signature is stated \"deduced\", not \"not established\" followed by hypotheses**: the signature is a proof. [cross Visibility]\n415\t- **\"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]\n416\t- **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]\n417\t- **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]\n418\t- **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]\n419\t- **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]\n420\t\n421\tThe boundaries between families, and what is not labeled: `families.md`.\n422\t"}]},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"af24fb15-4a25-478c-b8b4-d4ce98413418","timestamp":"2026-11-17T20:31:12.642Z","tool_use_result":{"type":"text","file":{"filePath":"/home/maxime/.claude/projects/-home-maxime-aimsight-app/b1dece15-7ed2-440e-993c-de42f2e6a4bf/tool-results/bbi9zey7i.txt","content":"## 3. A single event\n\n- **One label, a single event**: two events, even close or mixed, make two labels; an event that repeats (a passage, the rain of each night, the thermal cycle of each day) makes one label each time. [instruction]\n- **The outward and return of a drift are two labels**: after each slow drift, look for its return, and do not join a descent and its rise because the description says so. [instruction, CLARIDEN, cross Displacement]\n- **The thermal cycle of the camera, outward and return, is a single event per day; the structure makes two, the expansion and the contraction**: this is what the expert does; the outward-and-return rule does not apply to the camera cycle. [cross Thermal displacement, expert]\n- **An event in one piece over several days makes one label**: a change of speed does not cut it, nor a tilt that continues in the same direction; only a stop followed by a return, or a change of direction, cuts it. [instruction, BREITHORN, cross Displacement]\n- **A return that exceeds the starting level remains the same event**: it does not start a new movement. [LENZSPITZE]\n- **A lasting jump: the label bounds the jump, the return is another label**: the step is stated in the description; a step that returns within the day remains one label (a jump then the return); two steps separated by days of plateau make two labels, even in the same direction. [cross Displacement]\n- **A bump that is only the trace of a slow camera movement follows the cutting of that movement**: it is not a separate event. [cross Displacement]\n- **Two gaps separated by a single measurement that came back make a single No data label; separated by two measurements or more, two**: a single measurement does not make a resumption. [cross No data, SNCF01]\n- **A measurement where a target is rejected alone just after a passage is the same event; a clean measurement between the two makes two labels**: the rejection that follows is the end of the passage. [cross Obstruction]\n- **Two nuisance episodes separated by a few hours where targets stay shifted make only one**: the shifted targets are still touched. [NORDEND]\n- **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]\n- **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]\n- **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]\n- **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]\n- **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]\n\n## 4. The family\n\n- **A single family per label, its key in `families.md`, following its boundaries**: `Visibility`, `Obstruction`, `Thermal displacement`, `Displacement`, `Target issue`, `No data`; no other key, nor old names. [instruction, MICHIGAN, WILDSTRUBEL]\n- **We decide by the signature, not by coincidence**: a temperature drop at the same moment does not make a thermal, an `error_value` that moves a little does not make a Visibility. [cross Thermal displacement, cross Visibility]\n- **A same target keeps the same family from one batch to the next, and a same phenomenon on neighboring stations the same family**: otherwise the defect of a target or a site reads as two causes. [NORDEND, consistency]\n- **The sun at sunrise in the field and the lit background behind a spot are the same nuisance**: same family, same way of stating the cause. [cross Visibility]\n\n## 5. The description\n\n- **As the expert would write it, in English: what is seen, the cause and how it was known, the conclusion for the client**: which targets or references with their exact names, which magnitudes, the return or not; then nothing to do, data not to be believed, or movement to monitor. [instruction]\n- **Qualitative, without numeric values, even in words**: \"a tenth\", \"half a pixel\", \"a few hundredths\", \"up to almost 1\" are numbers; say \"a little\", \"clearly\", \"strongly\". [instruction, FLORIDA, JUNGFRAU]\n- **The targets named are those that move the most, read instant by instant, in the right column**: not the usual list; a rejected target does not \"jump\"; the direction is stated as it is that day. [instruction, CLARIDEN, NEBRASKA, FLORIDA, NIEDERHORN]\n- **A sentence taken from a model is reread on the range of each label**: the hours, the weather, the targets, the image, the return, the overshoot; a precision true for a single label is not copied. [cross Visibility, cross Thermal displacement, SNCF01, LENZSPITZE, NORDEND, FLORIDA]\n- **\"Nothing on the images\", \"image without obstacle\" are written only after looking at the image of the hour**: a passage is often seen in transparency; the image cited is that of the day when it exists. [instruction, CLARIDEN, MICHIGAN, FLORIDA, WILDSTRUBEL, cross Visibility, JUNGFRAU]\n- **\"No image\" is written only at an instant when the camera usually takes an image, and after searching for the file**: a station that takes one only on the hour proves nothing at the half hour, and the hourly images often fall on the minute of the measurements. [cross No data, LENZSPITZE]\n- **A fact given by the expert is written \"according to the expert\", in words, without his numbers**: not \"the map knows\". [instruction, BREITHORN, MICHIGAN, NIEDERHORN]\n- **The temperature is \"the housing temperature\" (of the camera)**: the column being either `sensor_*_deg_c`, or, failing that, `temperature_deg_c`; never of the air, the building, the plant, the station, the components, the camera alone, nor the name of the column; without any metric, \"no temperature is available\". [instruction, cross Thermal displacement, LENZSPITZE, NORDEND, JUNGFRAU, consistency]\n- **The weather is not drawn from the housing temperature**: \"cold and overcast day\" is seen on the images. [FLORIDA]\n- **The moments of the day (morning, late afternoon, night) are judged on the images, never on the UTC hour**: the station can be anywhere. Every hour written is in UTC, no numeric local hour. [cross Visibility, label map, expert's reading rule]\n- **A level \"back\" or \"a little below\" is compared over several days**: a single day after may be in the middle of a thermal cycle; a night level that changes from one night to another is compared with several nights; a target rejected at night, with the nearest neighboring night where it is measured, never across a step. [instruction, MICHIGAN, cross Visibility, WILDSTRUBEL, finishing niederhorn]\n- **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]\n- **\"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]\n- **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]\n- **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]\n- **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]\n- **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]\n- **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]\n- **A lasting jump states its step**: its duration, its return or not. [cross Displacement]\n- **Each label of a sequence (outward, return, resumption) names the other**: \"return of the drift of…, labeled apart\", \"without return until the end of the batch\". [cross Displacement]\n- **A Target issue says when the rejections stop before the end of the label**: the end is read on the curves, the rejections may stop before. [cross Target issue]\n- **A No data states the metrics and the image of the instant**: present or not, checked, for each gap. [NIEDERHORN, cross No data]\n\n- **On a recent camera (image quality filled, `tools/scripts/quality.py`), an occultation is written only after reading the flux of the instant**: a cut flux proves it, a full flux denies it; the hidden targets are named from their flux, each time, and a hidden target that stayed under its threshold is stated (its point stays, wrong). The metrics: `tools/DATA.md`. [LENZSPITZE quality review, D-129]\n- **\"Bigger spots\" is written only after comparison with a calm day of the same image regime and reading of the `fwhm`**: a spot that has lost its light can look swollen. [LENZSPITZE quality review, D-129]\n- **A jump without rejection is in no list of rejections**: on a recent camera, `quality.py --labels --outside` gives the degraded instants outside the labels; `corr` is checked at each. [LENZSPITZE quality review, D-129]\n\n## 6. The stated cause\n\n- **A cause is stated in three ways only: seen, deduced, not established**: \"seen on the image (or the thumbnail) of HH:MM\", saying what is seen there; \"deduced from…\" (the signature, the other passages seen, the curves and the camera pose), saying why it is not seen; \"not established\", with its hypotheses; or \"according to the expert\". [instruction, cross Obstruction, cross Displacement]\n- **A cause deduced from a known signature is stated \"deduced\", not \"not established\" followed by hypotheses**: the signature is a proof. [cross Visibility]\n- **\"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]\n- **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]\n- **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]\n- **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]\n- **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]\n\nThe boundaries between families, and what is not labeled: `families.md`.\n","numLines":66,"startLine":357,"totalLines":422}},"tool_result_meta":[{"id":"toolu_0134tTNj3gJEAV6RyE4T8y5b","permission_decision":{"decision":"accept","source":"config","reason_type":"rule"}}]}
-{"type":"system","subtype":"thinking_tokens","estimated_tokens":50,"estimated_tokens_delta":50,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"b944fa07-835c-45da-b7ba-fc5edc0206c3"}
-{"type":"system","subtype":"thinking_tokens","estimated_tokens":200,"estimated_tokens_delta":150,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"15bb4267-a7ef-4da7-8747-70bae0aa2915"}
-{"type":"system","subtype":"thinking_tokens","estimated_tokens":366,"estimated_tokens_delta":166,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"7718853a-8b58-4997-9d6a-9a68e55d3f98"}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98nfB5uQuoWEByg5PVV","type":"message","role":"assistant","content":[{"type":"thinking","thinking":"","signature":"CAQSrAsKEAgTGAI4AUIIdGhpbmtpbmcSDGe+sl1SBL4LBXocAxoMW3jfwFiFWHMFMOGOIjA2yr+94LhwOmM8GLomP0A5Rao5ioVXXWsmuv9yqm4CDA7E0fHIjj4PjmYZRA05ZxEqyQoJo4KQ58d/WaobaA5SMLfsrvgX3bVqzOryRCKx9VPsUEtinyamuJvHN1/3eIO43N84b28FE1etl5aB2iw20fl+0Zd9lpcvesjQXce6T7wdmSF2FAWkjlK/czmTC2SoLYTSRZeT7EB6MStlGgH0vywvnk0big6sScNbRXxjeCeg8/XI76mmxrmWigqCEYZcsNs2rBrSV14RIZVvMdmSeVFeN42Bpxpfmqsf1l1HjALMfKuMYtqrthve4SVHnUX+p4/g2bp4MCzKT0qkFIvGEaasm1cWHrk1BHVxIPtTzExbuTXYaMGanw30frT/6RI6ADCA6gbO82W5StIr5JLgA3kdR27eXpxlsgSD+n1a9X0ZJHxoPPEs4I68ZowlAho81cp7p4PFsGV5+hkpqWGLuRzXRscNX9NVOZFD5l06nuVRLEypLPGiDqUFVEiDjfmklzE8xpWX6PXPov/ZNJALVKiTahLyskQrbpTAl0ASO3+83QPCTBC/mbonvLo4LSnCnpaCzPy2lIgOaAecbqGrYAJYo/JZD2y93JdsLyGOKXq6PfbvJpsmbntmT3wNYwOn+IiH0rRLKmwU9+Okozwo9BNgkmUgeaR3SyMSvGoWWmjdiaMD35Vfne2Iy4hyrDNGW9QPG6LHZWBkioiOAyxGRpIPu0mCQogqdBArtslNpO28PfFJwYLTXF6qcPKoIh1uCaRpgiBLSyYqHjXPdJQOeNjIhNZf2J/DmugusOeelnCgCK0AZfqIaq1xHV+T26PIv4zeWUjxUj2dlBmP9kagw6zaMffkMKptZmApNV83kdDHeVxYBqv+LNqq1HlD/kDkNPe9oiL89fkm99Fa/hh8dMgcUepG1iLRSZ3KelhaG8RwFTcSl8a+WWq3s2SelWmWtg6ARpehF8eu82kM+PdKzTT8Iv5TZXM7adcMawFax9Mk7ywbmTzmk+rPRkdNWhGxo/hqSnb06GpdmrKEHIXJMri8IE7onbcX4cKOrodnktpjb/JO+CxoouVIRjOMVA7pWuJVvIed9g2bnTuHblgiGUa4Za0CWT3L6tXYT7XILf6Hxk35qyWMkejKvOykugTVvHqjwMNtq8QHJUXgCz1HxBt/3rHhSooYI28+Y4FdL0T35fbnGqjSoCdHn3HI6e5K9TRm3qqcmxrbBnxQP9k+qqu6z9av7h/cbqNRxbRKj6/FQ6ZqjizCxX4axFLk8nc9ca/5mMw+YO2jn4XGNlVpt5HF4qZEu63glC2cL6XQvX66mIwA+HHcttPtClYqDu7t0aimwvmZWOy1yHBklOv2anYhjxs+WB5F3i3Qg8aaaY9QgBW8RYsyEZA0DrI/T2rlXasiGqMNlQbX809wY0hoo4Su1VRlHUXbKhCuZPecx5SNR49cO1yb+jHr4pHJv8+oJrbWYI873sBRhIEhHx/q5GgReYM9FWmHEKh1/7aBgxa20duHilL+8tJbItpHX4FUshaYESRsbwu3UpxeVwbnkzDtKx3VoIVv5oqqA7wBUE3Zcglw2KdQM//icypyZfj3B5UatkNOvFyAy6r7Xbae4DSK1vXrSfR07g6KaTPcETIk2H7xx1LTMswd3246TWMdHeFVptPxp5Dvdl6qe6oYqx4rvDVbe/IXqXvajMEMsZJwj61OGJiMS5LVPzrzoJmhp5T9c2FJL3Fakrp/fIEWifMbepFaQ+eAwTNxEpUBKZmV/7Ed+gUE/6unh25UE/T3zXfiIbg8F4MHJKuInKvCYkNzVGtEEYFLC5cSNDR7SaMw9KU66QoQukEHSPgoFjhpLxTMMRGviJA1T68YAQ=="}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":4611,"cache_read_input_tokens":46587,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":4611},"output_tokens":4,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"994c82d0-d13e-4a38-b41a-2b1293566570","timestamp":"2026-11-17T20:31:17.201Z","request_id":"req_011Ch98nevhGtuHytm69vViX","thinking_duration_ms":2908,"thinking_display":"updates"}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98nfB5uQuoWEByg5PVV","type":"message","role":"assistant","content":[{"type":"tool_use","id":"toolu_019JgK5pQ4tndhJUJtBodkJy","name":"Bash","input":{"command":"cd /home/maxime/aimsight-app; ls labeling/auto/analyses/BREITHORN_*/; grep -c . labeling/auto/BREITHORN.jsonl; python3 tools/scripts/inventory.py data/BREITHORN --start 2026-10-03T00:00Z --end 2026-11-01T00:00Z > labeling/auto/analyses/long-labels/BREITHORN/work/inventory.txt; grep -n -A60 '^Sensors\\|^sensor' labeling/auto/analyses/long-labels/BREITHORN/work/inventory.txt | head -80","description":"List reports, run inventory"},"caller":{"type":"direct"}}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":4611,"cache_read_input_tokens":46587,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":4611},"output_tokens":4,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"79acefc7-a753-411e-ab38-327cd26cc5e9","timestamp":"2026-11-17T20:31:19.164Z","request_id":"req_011Ch98nevhGtuHytm69vViX","wire_tool_inputs":{"toolu_019JgK5pQ4tndhJUJtBodkJy":{"command":"cd /home/maxime/aimsight-app; ls labeling/auto/analyses/BREITHORN_*/; grep -c . labeling/auto/BREITHORN.jsonl; python3 tools/scripts/inventory.py data/BREITHORN --start 2026-10-03T00:00Z --end 2026-11-01T00:00Z > labeling/auto/analyses/long-labels/BREITHORN/work/inventory.txt; grep -n -A60 '^Sensors\\|^sensor' labeling/auto/analyses/long-labels/BREITHORN/work/inventory.txt | head -80","description":"List reports, run inventory"}}}
-{"type":"system","subtype":"task_summary","detail":"Listing reports, running inventory","uuid":"6c14d075-6b40-4a21-927f-b53753380f7b","session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf"}
-{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_019JgK5pQ4tndhJUJtBodkJy","type":"tool_result","content":"labeling/auto/analyses/BREITHORN_2026-10-03T0000_2026-10-13T0000/:\nanalysis.md\nlabels.jsonl\nreport.md\nrequest.json\nscripts\nthermal_mornings.png\nwork\n\nlabeling/auto/analyses/BREITHORN_2026-10-13T0000_2026-10-22T1600/:\nanalysis.md\nfig_14oct_lit_objects.png\nfig_14oct_night_bump.png\nfig_spot_sizes.png\nlabels.jsonl\nreport.md\nrequest.json\nscripts\nwork\n\nlabeling/auto/analyses/BREITHORN_2026-10-22T1600_2026-11-01T0000/:\nanalysis.md\ncar_then_structure_26_october.png\nlabels.jsonl\nreport.md\nrequest.json\nscripts\nvehicle_22-23_october.png\nwork\n24\n37:Sensors: 16 (4 references, 12 targets)\n38- distance (m) and mm/px: targets.csv (data.load_targets); \"-\": not in it, or not filled in (distance 1000 mm); \"?\": its lines (n) disagree, no corr_x_mm / corr_y_mm\n39:sensor type pattern threshold measurements rejected distance mm/px\n40-REFG44N reference global_ref 0.7 446 16 - -\n41-REFH22 reference global_ref 0.7 446 10 - -\n42-REFI'21 reference global_ref 0.7 446 57 - -\n43-REFPOU22 reference global_ref 0.7 446 61 - -\n44-COLH20 target target 0.7 446 0 21.6 8.116\n45-COLH20''' target target 0.7 446 38 22.6 8.560\n46-COLI20 target target 0.7 446 0 20.2 7.571\n47-COLI21 target target 0.7 446 0 30.3 11.351\n48-COLI22 target target 0.7 446 23 40.2 15.004\n49-COLI24 target target 0.7 446 67 60.3 22.539\n50-COLJ19 target target 0.7 446 0 8.9 3.272\n51-POUH21 target target 0.7 446 0 29.8 11.347\n52-POUI19 target target 0.7 446 0 9.4 3.546\n53-POUI20 target target 0.7 446 0 20.5 7.798\n54-POUI22 target target 0.7 446 45 40.4 15.220\n55-POUI24 target target 0.7 446 11 60.5 22.835\n56-\n57-Camera pose over the whole period: 436 registrations, 2026-09-01T00:00Z → 2026-11-16T00:00Z\n58-Measurement instants without a pose (no registration): 10 of 446\n59-\n60-Window 2026-10-03T00:00Z → 2026-11-01T00:00Z: 172 instants present\n61-Steps absent for all sensors, between two present instants (cadence of 240 min):\n62- between 2026-10-15T20:00Z and 2026-10-16T12:00Z: 3\n63-Present instants where sensors have no measurement:\n64- (none)\n65-Rejected measurements in the window, per sensor (start → end of each run of consecutive steps, count):\n66- REFH22 (6): 2026-10-09T00:00Z → 04:00Z (2); 2026-10-26T00:00Z → 04:00Z (2); 2026-10-26T16:00Z → 20:00Z (2)\n67- REFI'21 (1): 2026-10-07T12:00Z\n68- REFPOU22 (14): 2026-10-03T04:00Z → 2026-10-04T16:00Z (10); 2026-10-26T00:00Z → 04:00Z (2); 2026-10-27T00:00Z → 04:00Z (2)\n69- COLH20''' (15): 2026-10-03T04:00Z → 2026-10-04T16:00Z (10); 2026-10-13T04:00Z; 2026-10-26T00:00Z → 04:00Z (2); 2026-10-27T00:00Z → 04:00Z (2)\n70- COLI22 (13): 2026-10-06T20:00Z → 2026-10-07T04:00Z (3); 2026-10-08T00:00Z; 2026-10-09T00:00Z → 04:00Z (2); 2026-10-09T20:00Z; 2026-10-10T04:00Z; 2026-10-24T04:00Z → 12:00Z (3); 2026-10-26T00:00Z → 04:00Z (2)\n71- COLI24 (33): 2026-10-06T20:00Z → 2026-10-07T04:00Z (3); 2026-10-07T20:00Z → 2026-10-08T00:00Z (2); 2026-10-09T00:00Z → 04:00Z (2); 2026-10-09T20:00Z; 2026-10-10T04:00Z; 2026-10-13T04:00Z; 2026-10-21T20:00Z → 2026-10-22T04:00Z (3); 2026-10-22T20:00Z → 2026-10-23T04:00Z (3); 2026-10-23T20:00Z → 2026-10-25T20:00Z (13); 2026-10-26T16:00Z → 20:00Z (2); 2026-10-29T20:00Z → 2026-10-30T00:00Z (2)\n72- POUI22 (32): 2026-10-03T04:00Z → 2026-10-04T16:00Z (10); 2026-10-06T20:00Z → 2026-10-07T04:00Z (3); 2026-10-08T00:00Z; 2026-10-09T00:00Z → 04:00Z (2); 2026-10-09T20:00Z; 2026-10-10T04:00Z; 2026-10-24T04:00Z → 2026-10-25T20:00Z (11); 2026-10-26T20:00Z → 2026-10-27T04:00Z (3)\n73- POUI24 (8): 2026-10-04T16:00Z; 2026-10-10T04:00Z; 2026-10-24T04:00Z → 12:00Z (3); 2026-10-26T00:00Z → 04:00Z (2); 2026-10-26T16:00Z\n74-Retained references by the compensation (inlier = 1) out of 4, number of instants: 4: 153, 3: 17, 0: 2\n75-Instants where references are not retained (runs of consecutive steps with the same references out; r = rejected, empty = inlier empty, otherwise the inlier value):\n76- 2026-10-03T04:00Z → 2026-10-04T16:00Z (10): 3 retained; out: REFPOU22 (r)\n77- 2026-10-07T12:00Z: 3 retained; out: REFI'21 (r)\n78- 2026-10-09T00:00Z → 04:00Z (2): 3 retained; out: REFH22 (r)\n79- 2026-10-26T00:00Z → 04:00Z (2): 0 retained; out: REFG44N (empty), REFH22 (r), REFI'21 (empty), REFPOU22 (r)\n80- 2026-10-26T16:00Z → 20:00Z (2): 3 retained; out: REFH22 (r)\n81- 2026-10-27T00:00Z → 04:00Z (2): 3 retained; out: REFPOU22 (r)\n82-\n83-Camera pose in the window: 172 registrations, 2026-10-03T00:00Z → 2026-11-01T00:00Z\n84-Measurement instants without a pose (no registration): 0 of 172","is_error":false}]},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"1924ac27-0702-4636-9540-24b311d0c478","timestamp":"2026-11-17T20:31:21.565Z","tool_use_result":{"stdout":"labeling/auto/analyses/BREITHORN_2026-10-03T0000_2026-10-13T0000/:\nanalysis.md\nlabels.jsonl\nreport.md\nrequest.json\nscripts\nthermal_mornings.png\nwork\n\nlabeling/auto/analyses/BREITHORN_2026-10-13T0000_2026-10-22T1600/:\nanalysis.md\nfig_14oct_lit_objects.png\nfig_14oct_night_bump.png\nfig_spot_sizes.png\nlabels.jsonl\nreport.md\nrequest.json\nscripts\nwork\n\nlabeling/auto/analyses/BREITHORN_2026-10-22T1600_2026-11-01T0000/:\nanalysis.md\ncar_then_structure_26_october.png\nlabels.jsonl\nreport.md\nrequest.json\nscripts\nvehicle_22-23_october.png\nwork\n24\n37:Sensors: 16 (4 references, 12 targets)\n38- distance (m) and mm/px: targets.csv (data.load_targets); \"-\": not in it, or not filled in (distance 1000 mm); \"?\": its lines (n) disagree, no corr_x_mm / corr_y_mm\n39:sensor type pattern threshold measurements rejected distance mm/px\n40-REFG44N reference global_ref 0.7 446 16 - -\n41-REFH22 reference global_ref 0.7 446 10 - -\n42-REFI'21 reference global_ref 0.7 446 57 - -\n43-REFPOU22 reference global_ref 0.7 446 61 - -\n44-COLH20 target target 0.7 446 0 21.6 8.116\n45-COLH20''' target target 0.7 446 38 22.6 8.560\n46-COLI20 target target 0.7 446 0 20.2 7.571\n47-COLI21 target target 0.7 446 0 30.3 11.351\n48-COLI22 target target 0.7 446 23 40.2 15.004\n49-COLI24 target target 0.7 446 67 60.3 22.539\n50-COLJ19 target target 0.7 446 0 8.9 3.272\n51-POUH21 target target 0.7 446 0 29.8 11.347\n52-POUI19 target target 0.7 446 0 9.4 3.546\n53-POUI20 target target 0.7 446 0 20.5 7.798\n54-POUI22 target target 0.7 446 45 40.4 15.220\n55-POUI24 target target 0.7 446 11 60.5 22.835\n56-\n57-Camera pose over the whole period: 436 registrations, 2026-09-01T00:00Z → 2026-11-16T00:00Z\n58-Measurement instants without a pose (no registration): 10 of 446\n59-\n60-Window 2026-10-03T00:00Z → 2026-11-01T00:00Z: 172 instants present\n61-Steps absent for all sensors, between two present instants (cadence of 240 min):\n62- between 2026-10-15T20:00Z and 2026-10-16T12:00Z: 3\n63-Present instants where sensors have no measurement:\n64- (none)\n65-Rejected measurements in the window, per sensor (start → end of each run of consecutive steps, count):\n66- REFH22 (6): 2026-10-09T00:00Z → 04:00Z (2); 2026-10-26T00:00Z → 04:00Z (2); 2026-10-26T16:00Z → 20:00Z (2)\n67- REFI'21 (1): 2026-10-07T12:00Z\n68- REFPOU22 (14): 2026-10-03T04:00Z → 2026-10-04T16:00Z (10); 2026-10-26T00:00Z → 04:00Z (2); 2026-10-27T00:00Z → 04:00Z (2)\n69- COLH20''' (15): 2026-10-03T04:00Z → 2026-10-04T16:00Z (10); 2026-10-13T04:00Z; 2026-10-26T00:00Z → 04:00Z (2); 2026-10-27T00:00Z → 04:00Z (2)\n70- COLI22 (13): 2026-10-06T20:00Z → 2026-10-07T04:00Z (3); 2026-10-08T00:00Z; 2026-10-09T00:00Z → 04:00Z (2); 2026-10-09T20:00Z; 2026-10-10T04:00Z; 2026-10-24T04:00Z → 12:00Z (3); 2026-10-26T00:00Z → 04:00Z (2)\n71- COLI24 (33): 2026-10-06T20:00Z → 2026-10-07T04:00Z (3); 2026-10-07T20:00Z → 2026-10-08T00:00Z (2); 2026-10-09T00:00Z → 04:00Z (2); 2026-10-09T20:00Z; 2026-10-10T04:00Z; 2026-10-13T04:00Z; 2026-10-21T20:00Z → 2026-10-22T04:00Z (3); 2026-10-22T20:00Z → 2026-10-23T04:00Z (3); 2026-10-23T20:00Z → 2026-10-25T20:00Z (13); 2026-10-26T16:00Z → 20:00Z (2); 2026-10-29T20:00Z → 2026-10-30T00:00Z (2)\n72- POUI22 (32): 2026-10-03T04:00Z → 2026-10-04T16:00Z (10); 2026-10-06T20:00Z → 2026-10-07T04:00Z (3); 2026-10-08T00:00Z; 2026-10-09T00:00Z → 04:00Z (2); 2026-10-09T20:00Z; 2026-10-10T04:00Z; 2026-10-24T04:00Z → 2026-10-25T20:00Z (11); 2026-10-26T20:00Z → 2026-10-27T04:00Z (3)\n73- POUI24 (8): 2026-10-04T16:00Z; 2026-10-10T04:00Z; 2026-10-24T04:00Z → 12:00Z (3); 2026-10-26T00:00Z → 04:00Z (2); 2026-10-26T16:00Z\n74-Retained references by the compensation (inlier = 1) out of 4, number of instants: 4: 153, 3: 17, 0: 2\n75-Instants where references are not retained (runs of consecutive steps with the same references out; r = rejected, empty = inlier empty, otherwise the inlier value):\n76- 2026-10-03T04:00Z → 2026-10-04T16:00Z (10): 3 retained; out: REFPOU22 (r)\n77- 2026-10-07T12:00Z: 3 retained; out: REFI'21 (r)\n78- 2026-10-09T00:00Z → 04:00Z (2): 3 retained; out: REFH22 (r)\n79- 2026-10-26T00:00Z → 04:00Z (2): 0 retained; out: REFG44N (empty), REFH22 (r), REFI'21 (empty), REFPOU22 (r)\n80- 2026-10-26T16:00Z → 20:00Z (2): 3 retained; out: REFH22 (r)\n81- 2026-10-27T00:00Z → 04:00Z (2): 3 retained; out: REFPOU22 (r)\n82-\n83-Camera pose in the window: 172 registrations, 2026-10-03T00:00Z → 2026-11-01T00:00Z\n84-Measurement instants without a pose (no registration): 0 of 172","stderr":"","interrupted":false,"isImage":false,"noOutputExpected":false},"tool_result_meta":[{"id":"toolu_019JgK5pQ4tndhJUJtBodkJy","permission_decision":{"decision":"accept","source":"config","reason_type":"rule"}}]}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98oKWvMd8CcfKENhbPz","type":"message","role":"assistant","content":[{"type":"thinking","thinking":"","signature":"CAQSsQUKEAgTGAI4AUIIdGhpbmtpbmcSDB1HpP8M52nrSdcHCRoMZ64nAmSAfhqNTrkHIjDOHlcZThR0nxEnOfWuTD8DxJV+eW/j33Xq0d+GR6RX4LQwpIy3qSj/abGGKk/tB4EqzgS4z7NqVpb3a50OGand8N0za0OYfENyohaIGyG5GIwkMVe7JHHoQrg0Rn6q7picYUu9eluu64qRapDDqUniEUo/8yIn1byK8MB+p6GffoxqflEAZwemknbgS7jYMDk8uHoVlDaWi3K1kUuAypsHNg2U9PIccskJZTJvjD1n7hUBckEhZOiN9X9db5BPBGbTtV+pWnXPPZMkjd58MwxGoeYCU7ADMwehsd+pKoiwFgn61uPzJFQMHx8Ej/24AIQCgEc6rw6yQjDIUDmuepwK93033ndfOXauEOcBCjEZ78aekC8rE1ybM29Hr3Xn2qM6XIKxX0zm6S9yxeUXWum1rxwwZz8gkn3atBoMrNTQ9moH0/9Xt0ecfLn4gGjNX/a5QFm3Gc6+w/Sg2Zk34zA/CaGUl+l3LN1pslIClaGqqfZXTBaH8GiXjn9pnva8wv0U5XXOxb8HA6aVWU0rV+6Qd8/I6oDeS7c+zRO4xLkyKLPMexBQvH7tRDjZJNjOCnYCHwuvbzhz9XDX+kQzMkx6V38s2t94eX/YCmlTSoQd35uqw+2ijW/aA316z3tR16wACNoKcxjj3ItFDO1foMFXQ1ynV+fKtSqNkfx3/4IKZma0rH2ftn+B4deUi4UPhol3hbe17vsq5mnY5+MzE1L+i37DxaEPbEGVkQQvv+jgK6LjT1q2ZbYxF4UcB5cX6SwPhxXIhRDD12S0ip/VfD2SGUr5z9/Q8+t8A1Y7SpMpCcj7GGtXcQmPbFRIHdt0S3+UGg2MXl+oO8SG2AIZVZpGrBgB"}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":3171,"cache_read_input_tokens":51198,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":3171},"output_tokens":3,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"e9106bb8-6d6f-4479-aed2-dc340b782cf5","timestamp":"2026-11-17T20:31:24.037Z","request_id":"req_011Ch98oK595DDma8FZ6UBZP","thinking_duration_ms":864,"thinking_display":"updates"}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98oKWvMd8CcfKENhbPz","type":"message","role":"assistant","content":[{"type":"text","text":"Reading done; now measuring the two drifts (BREITHORN-2, BREITHORN-13) with ranges.py."}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":3171,"cache_read_input_tokens":51198,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":3171},"output_tokens":3,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"5dccfbf9-caba-44f9-87ba-461c005496c2","timestamp":"2026-11-17T20:31:24.038Z","request_id":"req_011Ch98oK595DDma8FZ6UBZP"}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98oKWvMd8CcfKENhbPz","type":"message","role":"assistant","content":[{"type":"tool_use","id":"toolu_013trqnKARFvKxsYkPitPcBh","name":"Bash","input":{"command":"cd /home/maxime/aimsight-app; W=labeling/auto/analyses/long-labels/BREITHORN/work; python3 tools/scripts/ranges.py data/BREITHORN --columns corr_x,corr_y --start 2026-10-03T00:00Z --end 2026-10-13T04:00Z --min-measurements 6 > $W/ranges_2.txt; python3 tools/scripts/ranges.py data/BREITHORN --columns corr_x,corr_y,corr_x_mm,corr_y_mm --start 2026-10-16T20:00Z --end 2026-11-01T00:00Z --min-measurements 6 > $W/ranges_13.txt; wc -l $W/ranges_*.txt","description":"Run ranges.py on both label ranges"},"caller":{"type":"direct"}}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":3171,"cache_read_input_tokens":51198,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":3171},"output_tokens":3,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"2d585142-2357-43ba-bebb-46f1268d1e09","timestamp":"2026-11-17T20:31:26.103Z","request_id":"req_011Ch98oK595DDma8FZ6UBZP","wire_tool_inputs":{"toolu_013trqnKARFvKxsYkPitPcBh":{"command":"cd /home/maxime/aimsight-app; W=labeling/auto/analyses/long-labels/BREITHORN/work; python3 tools/scripts/ranges.py data/BREITHORN --columns corr_x,corr_y --start 2026-10-03T00:00Z --end 2026-10-13T04:00Z --min-measurements 6 > $W/ranges_2.txt; python3 tools/scripts/ranges.py data/BREITHORN --columns corr_x,corr_y,corr_x_mm,corr_y_mm --start 2026-10-16T20:00Z --end 2026-11-01T00:00Z --min-measurements 6 > $W/ranges_13.txt; wc -l $W/ranges_*.txt","description":"Run ranges.py on both label ranges"}}}
-{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_013trqnKARFvKxsYkPitPcBh","type":"tool_result","content":" 92 labeling/auto/analyses/long-labels/BREITHORN/work/ranges_13.txt\n 46 labeling/auto/analyses/long-labels/BREITHORN/work/ranges_2.txt\n 138 total","is_error":false}]},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"1ab04c1c-822d-4b19-a652-1d25d3cac9ba","timestamp":"2026-11-17T20:31:26.636Z","tool_use_result":{"stdout":" 92 labeling/auto/analyses/long-labels/BREITHORN/work/ranges_13.txt\n 46 labeling/auto/analyses/long-labels/BREITHORN/work/ranges_2.txt\n 138 total","stderr":"","interrupted":false,"isImage":false,"noOutputExpected":false},"tool_result_meta":[{"id":"toolu_013trqnKARFvKxsYkPitPcBh","permission_decision":{"decision":"accept","source":"config","reason_type":"rule"}}]}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98oguYPXyuUXSoot5Ju","type":"message","role":"assistant","content":[{"type":"tool_use","id":"toolu_01Tf1Xb5CV9r2dxnkRm2iBrC","name":"Read","input":{"file_path":"/home/maxime/aimsight-app/labeling/auto/analyses/long-labels/BREITHORN/work/ranges_2.txt"},"caller":{"type":"direct"}}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":475,"cache_read_input_tokens":54369,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":475},"output_tokens":16,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"b44d8f2a-12c0-493a-a3be-eacfc9021b08","timestamp":"2026-11-17T20:31:28.705Z","request_id":"req_011Ch98ogfeSUnsmm1ZmjwfA","wire_tool_inputs":{"toolu_01Tf1Xb5CV9r2dxnkRm2iBrC":{"file_path":"/home/maxime/aimsight-app/labeling/auto/analyses/long-labels/BREITHORN/work/ranges_2.txt"}}}
-{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_01Tf1Xb5CV9r2dxnkRm2iBrC","type":"tool_result","content":"1\t\n2\t== corr_x: level, noise, largest jump from one measurement to the next ==\n3\tsensor n level noise jump (noises) between\n4\tREFG44N 62 0.02075 0.00364 +0.07406 20.4 2026-10-04T16:00Z and 2026-10-04T20:00Z\n5\tREFH22 60 0.006956 0.00503 +0.1296 25.8 2026-10-04T12:00Z and 2026-10-04T16:00Z\n6\tREFI'21 61 0.01611 0.00329 +0.06322 19.2 2026-10-04T16:00Z and 2026-10-04T20:00Z\n7\tREFPOU22 52 -0.0439 0.00456 +0.03488 7.7 2026-10-10T04:00Z and 2026-10-10T08:00Z\n8\tCOLH20 62 0.05263 0.00816 +0.07961 9.8 2026-10-04T16:00Z and 2026-10-04T20:00Z\n9\tCOLH20''' 51 0.02156 0.00486 +0.03378 7.0 2026-10-10T04:00Z and 2026-10-10T08:00Z\n10\tCOLI20 62 0.002981 0.00751 +0.06947 9.3 2026-10-04T16:00Z and 2026-10-04T20:00Z\n11\tCOLI21 62 0.02725 0.0141 +0.06925 4.9 2026-10-04T16:00Z and 2026-10-04T20:00Z\n12\tCOLI22 54 -0.002826 0.00782 +0.09883 12.6 2026-10-04T16:00Z and 2026-10-04T20:00Z\n13\tCOLI24 52 0.004593 0.00934 +0.07898 8.5 2026-10-04T16:00Z and 2026-10-04T20:00Z\n14\tCOLJ19 62 0.1228 0.00616 +0.06809 11.1 2026-10-04T16:00Z and 2026-10-04T20:00Z\n15\tPOUH21 62 0.01067 0.00676 +0.07469 11.1 2026-10-04T16:00Z and 2026-10-04T20:00Z\n16\tPOUI19 62 0.209 0.0075 +0.07604 10.1 2026-10-04T16:00Z and 2026-10-04T20:00Z\n17\tPOUI20 62 0.05464 0.00692 +0.0734 10.6 2026-10-04T16:00Z and 2026-10-04T20:00Z\n18\tPOUI22 44 -0.03399 0.00738 +0.2778 37.6 2026-10-13T00:00Z and 2026-10-13T04:00Z\n19\tPOUI24 60 0.04776 0.00882 +0.2178 24.7 2026-10-13T00:00Z and 2026-10-13T04:00Z\n20\t\n21\tcorr_x: ranges more than 5 noises from the level (merge 60 min); 0 of at least 6 measurements out of 90\n22\tsensor start end measurements extreme (noises) at rejected\n23\t(none)\n24\t\n25\t== corr_y: level, noise, largest jump from one measurement to the next ==\n26\tsensor n level noise jump (noises) between\n27\tREFG44N 62 0.01303 0.00481 +0.1232 25.6 2026-10-10T04:00Z and 2026-10-10T08:00Z\n28\tREFH22 60 -0.02975 0.00508 +0.3601 70.9 2026-10-10T00:00Z and 2026-10-10T04:00Z\n29\tREFI'21 61 0.01426 0.00407 +0.121 29.7 2026-10-10T04:00Z and 2026-10-10T08:00Z\n30\tREFPOU22 52 -0.002744 0.00776 -0.1199 -15.4 2026-10-10T00:00Z and 2026-10-10T04:00Z\n31\tCOLH20 62 0.06168 0.0122 -0.1213 -10.0 2026-10-10T00:00Z and 2026-10-10T04:00Z\n32\tCOLH20''' 51 -0.03286 0.00835 +0.1216 14.6 2026-10-10T04:00Z and 2026-10-10T08:00Z\n33\tCOLI20 62 -0.04809 0.00954 +0.1165 12.2 2026-10-10T04:00Z and 2026-10-10T08:00Z\n34\tCOLI21 62 -0.02485 0.0112 +0.117 10.4 2026-10-10T04:00Z and 2026-10-10T08:00Z\n35\tCOLI22 54 0.02148 0.0092 +0.2358 25.6 2026-10-04T16:00Z and 2026-10-04T20:00Z\n36\tCOLI24 52 -0.09136 0.0134 +0.1254 9.4 2026-10-04T16:00Z and 2026-10-04T20:00Z\n37\tCOLJ19 62 -0.03669 0.0124 -0.1162 -9.4 2026-10-04T12:00Z and 2026-10-04T16:00Z\n38\tPOUH21 62 -0.01986 0.00785 +0.1152 14.7 2026-10-04T16:00Z and 2026-10-04T20:00Z\n39\tPOUI19 62 -0.1216 0.0109 -0.1134 -10.4 2026-10-10T00:00Z and 2026-10-10T04:00Z\n40\tPOUI20 62 -0.05099 0.0101 +0.1135 11.2 2026-10-04T16:00Z and 2026-10-04T20:00Z\n41\tPOUI22 44 -0.07427 0.0143 -0.3166 -22.2 2026-10-13T00:00Z and 2026-10-13T04:00Z\n42\tPOUI24 60 -0.009546 0.00718 -0.4317 -60.2 2026-10-08T00:00Z and 2026-10-08T04:00Z\n43\t\n44\tcorr_y: ranges more than 5 noises from the level (merge 60 min); 0 of at least 6 measurements out of 47\n45\tsensor start end measurements extreme (noises) at rejected\n46\t(none)\n47\t"}]},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"c0172532-766b-49a7-904d-46bd3ef90e33","timestamp":"2026-11-17T20:31:28.743Z","tool_use_result":{"type":"text","file":{"filePath":"/home/maxime/aimsight-app/labeling/auto/analyses/long-labels/BREITHORN/work/ranges_2.txt","content":"\n== corr_x: level, noise, largest jump from one measurement to the next ==\nsensor n level noise jump (noises) between\nREFG44N 62 0.02075 0.00364 +0.07406 20.4 2026-10-04T16:00Z and 2026-10-04T20:00Z\nREFH22 60 0.006956 0.00503 +0.1296 25.8 2026-10-04T12:00Z and 2026-10-04T16:00Z\nREFI'21 61 0.01611 0.00329 +0.06322 19.2 2026-10-04T16:00Z and 2026-10-04T20:00Z\nREFPOU22 52 -0.0439 0.00456 +0.03488 7.7 2026-10-10T04:00Z and 2026-10-10T08:00Z\nCOLH20 62 0.05263 0.00816 +0.07961 9.8 2026-10-04T16:00Z and 2026-10-04T20:00Z\nCOLH20''' 51 0.02156 0.00486 +0.03378 7.0 2026-10-10T04:00Z and 2026-10-10T08:00Z\nCOLI20 62 0.002981 0.00751 +0.06947 9.3 2026-10-04T16:00Z and 2026-10-04T20:00Z\nCOLI21 62 0.02725 0.0141 +0.06925 4.9 2026-10-04T16:00Z and 2026-10-04T20:00Z\nCOLI22 54 -0.002826 0.00782 +0.09883 12.6 2026-10-04T16:00Z and 2026-10-04T20:00Z\nCOLI24 52 0.004593 0.00934 +0.07898 8.5 2026-10-04T16:00Z and 2026-10-04T20:00Z\nCOLJ19 62 0.1228 0.00616 +0.06809 11.1 2026-10-04T16:00Z and 2026-10-04T20:00Z\nPOUH21 62 0.01067 0.00676 +0.07469 11.1 2026-10-04T16:00Z and 2026-10-04T20:00Z\nPOUI19 62 0.209 0.0075 +0.07604 10.1 2026-10-04T16:00Z and 2026-10-04T20:00Z\nPOUI20 62 0.05464 0.00692 +0.0734 10.6 2026-10-04T16:00Z and 2026-10-04T20:00Z\nPOUI22 44 -0.03399 0.00738 +0.2778 37.6 2026-10-13T00:00Z and 2026-10-13T04:00Z\nPOUI24 60 0.04776 0.00882 +0.2178 24.7 2026-10-13T00:00Z and 2026-10-13T04:00Z\n\ncorr_x: ranges more than 5 noises from the level (merge 60 min); 0 of at least 6 measurements out of 90\nsensor start end measurements extreme (noises) at rejected\n(none)\n\n== corr_y: level, noise, largest jump from one measurement to the next ==\nsensor n level noise jump (noises) between\nREFG44N 62 0.01303 0.00481 +0.1232 25.6 2026-10-10T04:00Z and 2026-10-10T08:00Z\nREFH22 60 -0.02975 0.00508 +0.3601 70.9 2026-10-10T00:00Z and 2026-10-10T04:00Z\nREFI'21 61 0.01426 0.00407 +0.121 29.7 2026-10-10T04:00Z and 2026-10-10T08:00Z\nREFPOU22 52 -0.002744 0.00776 -0.1199 -15.4 2026-10-10T00:00Z and 2026-10-10T04:00Z\nCOLH20 62 0.06168 0.0122 -0.1213 -10.0 2026-10-10T00:00Z and 2026-10-10T04:00Z\nCOLH20''' 51 -0.03286 0.00835 +0.1216 14.6 2026-10-10T04:00Z and 2026-10-10T08:00Z\nCOLI20 62 -0.04809 0.00954 +0.1165 12.2 2026-10-10T04:00Z and 2026-10-10T08:00Z\nCOLI21 62 -0.02485 0.0112 +0.117 10.4 2026-10-10T04:00Z and 2026-10-10T08:00Z\nCOLI22 54 0.02148 0.0092 +0.2358 25.6 2026-10-04T16:00Z and 2026-10-04T20:00Z\nCOLI24 52 -0.09136 0.0134 +0.1254 9.4 2026-10-04T16:00Z and 2026-10-04T20:00Z\nCOLJ19 62 -0.03669 0.0124 -0.1162 -9.4 2026-10-04T12:00Z and 2026-10-04T16:00Z\nPOUH21 62 -0.01986 0.00785 +0.1152 14.7 2026-10-04T16:00Z and 2026-10-04T20:00Z\nPOUI19 62 -0.1216 0.0109 -0.1134 -10.4 2026-10-10T00:00Z and 2026-10-10T04:00Z\nPOUI20 62 -0.05099 0.0101 +0.1135 11.2 2026-10-04T16:00Z and 2026-10-04T20:00Z\nPOUI22 44 -0.07427 0.0143 -0.3166 -22.2 2026-10-13T00:00Z and 2026-10-13T04:00Z\nPOUI24 60 -0.009546 0.00718 -0.4317 -60.2 2026-10-08T00:00Z and 2026-10-08T04:00Z\n\ncorr_y: ranges more than 5 noises from the level (merge 60 min); 0 of at least 6 measurements out of 47\nsensor start end measurements extreme (noises) at rejected\n(none)\n","numLines":47,"startLine":1,"totalLines":47}},"tool_result_meta":[{"id":"toolu_01Tf1Xb5CV9r2dxnkRm2iBrC","permission_decision":{"decision":"accept","source":"config","reason_type":"rule"}}]}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98oguYPXyuUXSoot5Ju","type":"message","role":"assistant","content":[{"type":"tool_use","id":"toolu_01TriuREidwt3EN4jUFyejjC","name":"Read","input":{"file_path":"/home/maxime/aimsight-app/labeling/auto/analyses/long-labels/BREITHORN/work/ranges_13.txt"},"caller":{"type":"direct"}}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":475,"cache_read_input_tokens":54369,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":475},"output_tokens":16,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"ca89b267-9797-484c-8ddc-5d638e831967","timestamp":"2026-11-17T20:31:29.207Z","request_id":"req_011Ch98ogfeSUnsmm1ZmjwfA","wire_tool_inputs":{"toolu_01TriuREidwt3EN4jUFyejjC":{"file_path":"/home/maxime/aimsight-app/labeling/auto/analyses/long-labels/BREITHORN/work/ranges_13.txt"}}}
-{"type":"rate_limit_event","rate_limit_info":{"status":"allowed_warning","resetsAt":1794954600,"rateLimitType":"five_hour","utilization":0.99,"isUsingOverage":false,"surpassedThreshold":0.9,"rateLimitGraceActive":true,"unifiedWindows":{"five_hour":{"utilization":0.99,"resetsAt":1794954600,"status":"allowed_warning","surpassedThreshold":0.9},"seven_day":{"utilization":0.72,"resetsAt":1795302000,"status":"allowed"}},"overageEnabled":false},"uuid":"dfe2e43e-30be-4dc0-8ff3-3b0e6a9a83c2","session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf"}
-{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_01TriuREidwt3EN4jUFyejjC","type":"tool_result","content":"1\t\n2\t== corr_x: level, noise, largest jump from one measurement to the next ==\n3\tsensor n level noise jump (noises) between\n4\tREFG44N 92 0.0323 0.00347 +0.03735 10.8 2026-10-26T04:00Z and 2026-10-26T08:00Z\n5\tREFH22 88 -0.003408 0.005 -0.02222 -4.4 2026-10-26T12:00Z and 2026-10-27T00:00Z\n6\tREFI'21 92 0.02696 0.00296 +0.03238 11.0 2026-10-26T04:00Z and 2026-10-26T08:00Z\n7\tREFPOU22 88 -0.05694 0.00319 -0.0162 -5.1 2026-10-22T00:00Z and 2026-10-22T04:00Z\n8\tCOLH20 92 0.1104 0.0052 +0.04307 8.3 2026-10-26T04:00Z and 2026-10-26T08:00Z\n9\tCOLH20''' 88 -0.003447 0.00772 -0.2166 -28.0 2026-10-29T20:00Z and 2026-10-30T00:00Z\n10\tCOLI20 92 0.06404 0.00764 -0.04873 -6.4 2026-10-25T20:00Z and 2026-10-26T00:00Z\n11\tCOLI21 92 0.1319 0.011 +0.08134 7.4 2026-10-19T08:00Z and 2026-10-19T12:00Z\n12\tCOLI22 87 -0.005334 0.0127 -0.8344 -65.7 2026-10-23T16:00Z and 2026-10-23T20:00Z\n13\tCOLI24 69 -0.009728 0.00729 -0.05299 -7.3 2026-10-29T08:00Z and 2026-10-29T12:00Z\n14\tCOLJ19 92 0.2332 0.00755 +0.0571 7.6 2026-10-26T04:00Z and 2026-10-26T08:00Z\n15\tPOUH21 92 0.0165 0.00584 -0.04224 -7.2 2026-10-29T08:00Z and 2026-10-29T12:00Z\n16\tPOUI19 92 0.4154 0.00802 +0.05978 7.5 2026-10-26T04:00Z and 2026-10-26T08:00Z\n17\tPOUI20 92 0.1139 0.00558 -0.04597 -8.2 2026-10-25T20:00Z and 2026-10-26T00:00Z\n18\tPOUI22 78 -0.0315 0.0094 +0.5136 54.6 2026-10-29T16:00Z and 2026-10-29T20:00Z\n19\tPOUI24 86 0.07349 0.00946 -0.2316 -24.5 2026-10-26T20:00Z and 2026-10-27T00:00Z\n20\t\n21\tcorr_x: ranges more than 5 noises from the level (merge 60 min); 0 of at least 6 measurements out of 170\n22\tsensor start end measurements extreme (noises) at rejected\n23\t(none)\n24\t\n25\t== corr_y: level, noise, largest jump from one measurement to the next ==\n26\tsensor n level noise jump (noises) between\n27\tREFG44N 92 0.01141 0.00512 +0.0517 10.1 2026-10-28T08:00Z and 2026-10-28T12:00Z\n28\tREFH22 88 -0.05604 0.01 +0.03504 3.5 2026-10-24T04:00Z and 2026-10-24T08:00Z\n29\tREFI'21 92 0.01533 0.00421 +0.04284 10.2 2026-10-28T08:00Z and 2026-10-28T12:00Z\n30\tREFPOU22 88 0.02956 0.00977 -0.0705 -7.2 2026-10-29T08:00Z and 2026-10-29T12:00Z\n31\tCOLH20 92 0.1286 0.00817 -0.06091 -7.5 2026-10-19T08:00Z and 2026-10-19T12:00Z\n32\tCOLH20''' 88 -0.008465 0.00883 -0.2612 -29.6 2026-10-29T20:00Z and 2026-10-30T00:00Z\n33\tCOLI20 92 0.02538 0.00962 +0.04766 5.0 2026-10-29T08:00Z and 2026-10-29T12:00Z\n34\tCOLI21 92 0.06171 0.0118 +0.08119 6.9 2026-10-29T08:00Z and 2026-10-29T12:00Z\n35\tCOLI22 87 0.03629 0.00742 +0.1536 20.7 2026-10-23T04:00Z and 2026-10-23T08:00Z\n36\tCOLI24 69 -0.1456 0.00982 +0.06328 6.4 2026-10-29T16:00Z and 2026-10-30T04:00Z\n37\tCOLJ19 92 0.02882 0.0112 +0.06114 5.5 2026-10-30T16:00Z and 2026-10-30T20:00Z\n38\tPOUH21 92 -0.01284 0.00734 -0.02311 -3.1 2026-10-26T12:00Z and 2026-10-26T16:00Z\n39\tPOUI19 92 -0.1173 0.00767 -0.04744 -6.2 2026-10-29T08:00Z and 2026-10-29T12:00Z\n40\tPOUI20 92 -0.01327 0.00834 -0.04015 -4.8 2026-10-21T04:00Z and 2026-10-21T08:00Z\n41\tPOUI22 78 -0.09938 0.016 -1.289 -80.5 2026-10-26T16:00Z and 2026-10-27T08:00Z\n42\tPOUI24 86 -0.02697 0.0121 +0.07923 6.6 2026-10-26T20:00Z and 2026-10-27T00:00Z\n43\t\n44\tcorr_y: ranges more than 5 noises from the level (merge 60 min); 0 of at least 6 measurements out of 102\n45\tsensor start end measurements extreme (noises) at rejected\n46\t(none)\n47\t\n48\t== corr_x_mm: level, noise, largest jump from one measurement to the next ==\n49\tsensor n level noise jump (noises) between\n50\tREFG44N 0 (fewer than 2 values)\n51\tREFH22 0 (fewer than 2 values)\n52\tREFI'21 0 (fewer than 2 values)\n53\tREFPOU22 0 (fewer than 2 values)\n54\tCOLH20 92 0.8962 0.0422 +0.3495 8.3 2026-10-26T04:00Z and 2026-10-26T08:00Z\n55\tCOLH20''' 88 -0.0295 0.0661 -1.854 -28.0 2026-10-29T20:00Z and 2026-10-30T00:00Z\n56\tCOLI20 92 0.4849 0.0578 -0.3689 -6.4 2026-10-25T20:00Z and 2026-10-26T00:00Z\n57\tCOLI21 92 1.497 0.125 +0.9233 7.4 2026-10-19T08:00Z and 2026-10-19T12:00Z\n58\tCOLI22 87 -0.08003 0.19 -12.52 -65.7 2026-10-23T16:00Z and 2026-10-23T20:00Z\n59\tCOLI24 69 -0.2193 0.164 -1.194 -7.3 2026-10-29T08:00Z and 2026-10-29T12:00Z\n60\tCOLJ19 92 0.7631 0.0247 +0.1868 7.6 2026-10-26T04:00Z and 2026-10-26T08:00Z\n61\tPOUH21 92 0.1872 0.0662 -0.4793 -7.2 2026-10-29T08:00Z and 2026-10-29T12:00Z\n62\tPOUI19 92 1.473 0.0284 +0.2119 7.5 2026-10-26T04:00Z and 2026-10-26T08:00Z\n63\tPOUI20 92 0.8883 0.0435 -0.3585 -8.2 2026-10-25T20:00Z and 2026-10-26T00:00Z\n64\tPOUI22 78 -0.4795 0.143 +7.817 54.6 2026-10-29T16:00Z and 2026-10-29T20:00Z\n65\tPOUI24 86 1.678 0.216 -5.288 -24.5 2026-10-26T20:00Z and 2026-10-27T00:00Z\n66\t\n67\tcorr_x_mm: ranges more than 5 noises from the level (merge 60 min); 0 of at least 6 measurements out of 157\n68\tsensor start end measurements extreme (noises) at rejected\n69\t(none)\n70\t\n71\t== corr_y_mm: level, noise, largest jump from one measurement to the next ==\n72\tsensor n level noise jump (noises) between\n73\tREFG44N 0 (fewer than 2 values)\n74\tREFH22 0 (fewer than 2 values)\n75\tREFI'21 0 (fewer than 2 values)\n76\tREFPOU22 0 (fewer than 2 values)\n77\tCOLH20 92 1.044 0.0663 -0.4943 -7.5 2026-10-19T08:00Z and 2026-10-19T12:00Z\n78\tCOLH20''' 88 -0.07246 0.0755 -2.236 -29.6 2026-10-29T20:00Z and 2026-10-30T00:00Z\n79\tCOLI20 92 0.1922 0.0728 +0.3608 5.0 2026-10-29T08:00Z and 2026-10-29T12:00Z\n80\tCOLI21 92 0.7005 0.134 +0.9216 6.9 2026-10-29T08:00Z and 2026-10-29T12:00Z\n81\tCOLI22 87 0.5444 0.111 +2.304 20.7 2026-10-23T04:00Z and 2026-10-23T08:00Z\n82\tCOLI24 69 -3.282 0.221 +1.426 6.4 2026-10-29T16:00Z and 2026-10-30T04:00Z\n83\tCOLJ19 92 0.09428 0.0366 +0.2 5.5 2026-10-30T16:00Z and 2026-10-30T20:00Z\n84\tPOUH21 92 -0.1456 0.0833 -0.2622 -3.1 2026-10-26T12:00Z and 2026-10-26T16:00Z\n85\tPOUI19 92 -0.4159 0.0272 -0.1682 -6.2 2026-10-29T08:00Z and 2026-10-29T12:00Z\n86\tPOUI20 92 -0.1035 0.065 -0.3131 -4.8 2026-10-21T04:00Z and 2026-10-21T08:00Z\n87\tPOUI22 78 -1.513 0.244 -19.62 -80.5 2026-10-26T16:00Z and 2026-10-27T08:00Z\n88\tPOUI24 86 -0.6158 0.276 +1.809 6.6 2026-10-26T20:00Z and 2026-10-27T00:00Z\n89\t\n90\tcorr_y_mm: ranges more than 5 noises from the level (merge 60 min); 0 of at least 6 measurements out of 83\n91\tsensor start end measurements extreme (noises) at rejected\n92\t(none)\n93\t"}]},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"f86f5837-748a-4275-9d97-27e51f13fb10","timestamp":"2026-11-17T20:31:29.233Z","tool_use_result":{"type":"text","file":{"filePath":"/home/maxime/aimsight-app/labeling/auto/analyses/long-labels/BREITHORN/work/ranges_13.txt","content":"\n== corr_x: level, noise, largest jump from one measurement to the next ==\nsensor n level noise jump (noises) between\nREFG44N 92 0.0323 0.00347 +0.03735 10.8 2026-10-26T04:00Z and 2026-10-26T08:00Z\nREFH22 88 -0.003408 0.005 -0.02222 -4.4 2026-10-26T12:00Z and 2026-10-27T00:00Z\nREFI'21 92 0.02696 0.00296 +0.03238 11.0 2026-10-26T04:00Z and 2026-10-26T08:00Z\nREFPOU22 88 -0.05694 0.00319 -0.0162 -5.1 2026-10-22T00:00Z and 2026-10-22T04:00Z\nCOLH20 92 0.1104 0.0052 +0.04307 8.3 2026-10-26T04:00Z and 2026-10-26T08:00Z\nCOLH20''' 88 -0.003447 0.00772 -0.2166 -28.0 2026-10-29T20:00Z and 2026-10-30T00:00Z\nCOLI20 92 0.06404 0.00764 -0.04873 -6.4 2026-10-25T20:00Z and 2026-10-26T00:00Z\nCOLI21 92 0.1319 0.011 +0.08134 7.4 2026-10-19T08:00Z and 2026-10-19T12:00Z\nCOLI22 87 -0.005334 0.0127 -0.8344 -65.7 2026-10-23T16:00Z and 2026-10-23T20:00Z\nCOLI24 69 -0.009728 0.00729 -0.05299 -7.3 2026-10-29T08:00Z and 2026-10-29T12:00Z\nCOLJ19 92 0.2332 0.00755 +0.0571 7.6 2026-10-26T04:00Z and 2026-10-26T08:00Z\nPOUH21 92 0.0165 0.00584 -0.04224 -7.2 2026-10-29T08:00Z and 2026-10-29T12:00Z\nPOUI19 92 0.4154 0.00802 +0.05978 7.5 2026-10-26T04:00Z and 2026-10-26T08:00Z\nPOUI20 92 0.1139 0.00558 -0.04597 -8.2 2026-10-25T20:00Z and 2026-10-26T00:00Z\nPOUI22 78 -0.0315 0.0094 +0.5136 54.6 2026-10-29T16:00Z and 2026-10-29T20:00Z\nPOUI24 86 0.07349 0.00946 -0.2316 -24.5 2026-10-26T20:00Z and 2026-10-27T00:00Z\n\ncorr_x: ranges more than 5 noises from the level (merge 60 min); 0 of at least 6 measurements out of 170\nsensor start end measurements extreme (noises) at rejected\n(none)\n\n== corr_y: level, noise, largest jump from one measurement to the next ==\nsensor n level noise jump (noises) between\nREFG44N 92 0.01141 0.00512 +0.0517 10.1 2026-10-28T08:00Z and 2026-10-28T12:00Z\nREFH22 88 -0.05604 0.01 +0.03504 3.5 2026-10-24T04:00Z and 2026-10-24T08:00Z\nREFI'21 92 0.01533 0.00421 +0.04284 10.2 2026-10-28T08:00Z and 2026-10-28T12:00Z\nREFPOU22 88 0.02956 0.00977 -0.0705 -7.2 2026-10-29T08:00Z and 2026-10-29T12:00Z\nCOLH20 92 0.1286 0.00817 -0.06091 -7.5 2026-10-19T08:00Z and 2026-10-19T12:00Z\nCOLH20''' 88 -0.008465 0.00883 -0.2612 -29.6 2026-10-29T20:00Z and 2026-10-30T00:00Z\nCOLI20 92 0.02538 0.00962 +0.04766 5.0 2026-10-29T08:00Z and 2026-10-29T12:00Z\nCOLI21 92 0.06171 0.0118 +0.08119 6.9 2026-10-29T08:00Z and 2026-10-29T12:00Z\nCOLI22 87 0.03629 0.00742 +0.1536 20.7 2026-10-23T04:00Z and 2026-10-23T08:00Z\nCOLI24 69 -0.1456 0.00982 +0.06328 6.4 2026-10-29T16:00Z and 2026-10-30T04:00Z\nCOLJ19 92 0.02882 0.0112 +0.06114 5.5 2026-10-30T16:00Z and 2026-10-30T20:00Z\nPOUH21 92 -0.01284 0.00734 -0.02311 -3.1 2026-10-26T12:00Z and 2026-10-26T16:00Z\nPOUI19 92 -0.1173 0.00767 -0.04744 -6.2 2026-10-29T08:00Z and 2026-10-29T12:00Z\nPOUI20 92 -0.01327 0.00834 -0.04015 -4.8 2026-10-21T04:00Z and 2026-10-21T08:00Z\nPOUI22 78 -0.09938 0.016 -1.289 -80.5 2026-10-26T16:00Z and 2026-10-27T08:00Z\nPOUI24 86 -0.02697 0.0121 +0.07923 6.6 2026-10-26T20:00Z and 2026-10-27T00:00Z\n\ncorr_y: ranges more than 5 noises from the level (merge 60 min); 0 of at least 6 measurements out of 102\nsensor start end measurements extreme (noises) at rejected\n(none)\n\n== corr_x_mm: level, noise, largest jump from one measurement to the next ==\nsensor n level noise jump (noises) between\nREFG44N 0 (fewer than 2 values)\nREFH22 0 (fewer than 2 values)\nREFI'21 0 (fewer than 2 values)\nREFPOU22 0 (fewer than 2 values)\nCOLH20 92 0.8962 0.0422 +0.3495 8.3 2026-10-26T04:00Z and 2026-10-26T08:00Z\nCOLH20''' 88 -0.0295 0.0661 -1.854 -28.0 2026-10-29T20:00Z and 2026-10-30T00:00Z\nCOLI20 92 0.4849 0.0578 -0.3689 -6.4 2026-10-25T20:00Z and 2026-10-26T00:00Z\nCOLI21 92 1.497 0.125 +0.9233 7.4 2026-10-19T08:00Z and 2026-10-19T12:00Z\nCOLI22 87 -0.08003 0.19 -12.52 -65.7 2026-10-23T16:00Z and 2026-10-23T20:00Z\nCOLI24 69 -0.2193 0.164 -1.194 -7.3 2026-10-29T08:00Z and 2026-10-29T12:00Z\nCOLJ19 92 0.7631 0.0247 +0.1868 7.6 2026-10-26T04:00Z and 2026-10-26T08:00Z\nPOUH21 92 0.1872 0.0662 -0.4793 -7.2 2026-10-29T08:00Z and 2026-10-29T12:00Z\nPOUI19 92 1.473 0.0284 +0.2119 7.5 2026-10-26T04:00Z and 2026-10-26T08:00Z\nPOUI20 92 0.8883 0.0435 -0.3585 -8.2 2026-10-25T20:00Z and 2026-10-26T00:00Z\nPOUI22 78 -0.4795 0.143 +7.817 54.6 2026-10-29T16:00Z and 2026-10-29T20:00Z\nPOUI24 86 1.678 0.216 -5.288 -24.5 2026-10-26T20:00Z and 2026-10-27T00:00Z\n\ncorr_x_mm: ranges more than 5 noises from the level (merge 60 min); 0 of at least 6 measurements out of 157\nsensor start end measurements extreme (noises) at rejected\n(none)\n\n== corr_y_mm: level, noise, largest jump from one measurement to the next ==\nsensor n level noise jump (noises) between\nREFG44N 0 (fewer than 2 values)\nREFH22 0 (fewer than 2 values)\nREFI'21 0 (fewer than 2 values)\nREFPOU22 0 (fewer than 2 values)\nCOLH20 92 1.044 0.0663 -0.4943 -7.5 2026-10-19T08:00Z and 2026-10-19T12:00Z\nCOLH20''' 88 -0.07246 0.0755 -2.236 -29.6 2026-10-29T20:00Z and 2026-10-30T00:00Z\nCOLI20 92 0.1922 0.0728 +0.3608 5.0 2026-10-29T08:00Z and 2026-10-29T12:00Z\nCOLI21 92 0.7005 0.134 +0.9216 6.9 2026-10-29T08:00Z and 2026-10-29T12:00Z\nCOLI22 87 0.5444 0.111 +2.304 20.7 2026-10-23T04:00Z and 2026-10-23T08:00Z\nCOLI24 69 -3.282 0.221 +1.426 6.4 2026-10-29T16:00Z and 2026-10-30T04:00Z\nCOLJ19 92 0.09428 0.0366 +0.2 5.5 2026-10-30T16:00Z and 2026-10-30T20:00Z\nPOUH21 92 -0.1456 0.0833 -0.2622 -3.1 2026-10-26T12:00Z and 2026-10-26T16:00Z\nPOUI19 92 -0.4159 0.0272 -0.1682 -6.2 2026-10-29T08:00Z and 2026-10-29T12:00Z\nPOUI20 92 -0.1035 0.065 -0.3131 -4.8 2026-10-21T04:00Z and 2026-10-21T08:00Z\nPOUI22 78 -1.513 0.244 -19.62 -80.5 2026-10-26T16:00Z and 2026-10-27T08:00Z\nPOUI24 86 -0.6158 0.276 +1.809 6.6 2026-10-26T20:00Z and 2026-10-27T00:00Z\n\ncorr_y_mm: ranges more than 5 noises from the level (merge 60 min); 0 of at least 6 measurements out of 83\nsensor start end measurements extreme (noises) at rejected\n(none)\n","numLines":93,"startLine":1,"totalLines":93}},"tool_result_meta":[{"id":"toolu_01TriuREidwt3EN4jUFyejjC","permission_decision":{"decision":"accept","source":"config","reason_type":"rule"}}]}
-{"type":"user","message":{"role":"user","content":[{"type":"text","text":"[Usage limit reached; a short grace allowance remains, then this turn is cut off without warning. Judge what's left: if it's genuinely only a few steps, finish it properly, then stop and say so without extra polishing. Otherwise don't attempt it all: finish the piece in hand and at most two more like it, then stop. The allowance also pays for any subagents you have running: they don't get this message and will keep going, so it's up to you how to handle them. Either way, end by telling the user their usage limit was reached, what's done and what's left.]"}]},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"cf858d9b-27db-453f-bb0a-72fe1d8c9f71","timestamp":"2026-11-17T20:31:29.485Z","isSynthetic":true}
-{"type":"system","subtype":"thinking_tokens","estimated_tokens":50,"estimated_tokens_delta":50,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"ecb76ba6-9a34-4bd1-8f99-58dc4ed07ca1"}
-{"type":"system","subtype":"thinking_tokens","estimated_tokens":150,"estimated_tokens_delta":100,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"2e4180e6-217d-42cd-bcb7-44844b067802"}
-{"type":"system","subtype":"thinking_tokens","estimated_tokens":250,"estimated_tokens_delta":100,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"5f0c69db-de1b-4074-9dad-7915e09c74a5"}
-{"type":"system","subtype":"thinking_tokens","estimated_tokens":372,"estimated_tokens_delta":122,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"96d86513-b65a-4c3f-aea2-f1b9e1f7006d"}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98ou4Hpmu75q8EqTJzY","type":"message","role":"assistant","content":[{"type":"thinking","thinking":"","signature":"CAQSyQsKEAgTGAI4AUIIdGhpbmtpbmcSDDRHdQzvlTdPtgm4QBoMbBU0Aw6poJomRU+DIjAhYGKd1xrOfgSHZ5K2riU9gnpeYkB55dts41bJIerJGVLAdlt9E6jDKgMrT+iSKpcq5grYp5bUiwD6+DEbKiWxJKgLqVXpV+0O/Rwly1YLdo1XSGb8OVGC1Kuy2I3AAfVhZzV1qkB5GYRa1EuGEYWWP3LOE2tWPI77GlzAhhP8uriLCml6MCCJfJWCubjnVwep+Qk1Dq3ZU6U01sf4du3qSzySt75zFeuyx7cSt8GHRgMbzVEQ8dAjm1Fg7mdvpGmsCdkuicrBwwV1qn+CGommmuSbx+fSciCvb5wRifKCucwLp6ZlHMd84jXQh6fzIHnKN8MNWUBgbqPSN518qZxpy6mqz0knhWKQCxGD9ZRcuIFBdxwbXnynmN+gUmzVyi4jg5KHlFq+Yt/TeWs2GRa2j5RnkfjQpEoQ42Ii7X2rz42SOKy7kHBM4x9BHm8t+yELcXHMrrWMrg9RBdq6sFHjxlX/N3xYCNkHKj33HSfEoeLYJPDZMjQwWhiPOFQTjLSvz5Z7gEJ8wMKik3B37+8pkDQK60zyExWfd811H9arZ4GcoXW1oZkzKBlyvW1Zz2f1VIOM6oiCM4j5LUSUtjUOBwo7S61F5LjxnCCKThb+NljAhJZ0M/3Txz7yHq1nukwReII85Xvka9H3GvLoNWuytbPfWZiTRM0BY7v1OiBeROKgRU0v85mpcJYaJ1GP2SpwtaUPerNPZFdw6JYNhd0A8Oam30cgfuDF6OJ34uOh1rtpY257U15UK1ShRdo0qheZdAOoDOydO1LciC+0cdonef3q7bSY2NNyQRGhBea4wpryZii9Aa3WiRPPOqRKyErEIGG83M6H68aJsw6fFaMXrNNBnEkfzGIc92sOVc0dwUN6Rc00obyUwSY4Wo9dwIzk4veQxGiM0ztAOUMcegeP3kl+reCR0Zi9nt+78sm5kAk8TcFeS3D7an6IsFjLKEoCkjfwFg307kJa5B/zV6SAc3d93AZwXhUaJ8iX6n9QDlGI2Oy+5CzWXVzWDKs3IQrB105p2maBE/SMMtBBL5aA04rooxnDo4m+i9d40+DH2Al6/ZM4myPZi91YITwutl9lj/1twMRGiVV3Fdlul2FngfITm0Fxcfng9FfqODcjE+dM4/mUrvNfKlM1bqhNmA5QZTgEl7BwKZ2ZOOokz0p8II8zs0OsAvsZYMulM3n2Cl7eZq7SxgPlFZcHfxDBjfRM9GvVhRNElrpgrj5Ad5c2Bb6nTCTSfY3RAURt5bqwvZeKm0kSH4BaVkLaQtSMFbIhhGPtwOYrkBS1rybJ3dCY8gpMTlrcY1GQDQVN0g2S/bAay7Iil7SPWWTCfrMTUo9KlR8lldtK5UyesMTp2q18qNY+7cAi2czAP3WdOLlFE557GKBcWMwwV8P+qgxsNkftNfrbyhANFt86tTwtLRDXiRfKrqVqN4pB60uAvLISLVRkhHVq2w/6B5rFvr2I392ZAhsBqRLCfnrE027wvg3XebkSycs7j3DMLGctk0d/NL7TxI4P0xLL6SD0cm8dHJuDKwnrrzNaMDwMcEcmyoNfg4PnVS26ORdPuptbN+xpdO6x+LLo+eglOdkbbGJb3T3lPW2g3rPobocl972VpdjWvokGejNRb3OTBnt/aa8ltp2Yfriky6B+RJo1AyFMh9uxJ0y9fvWnhYskk5GOJeel6iyZjWQKKmlaCywb4UlpucAS9kBjTPDGhqiHWsEktJ7FnQHcYs0GikG7VwpQOeavwqLX1gn8kaqF7Ql9IqqxOk6FQz7yNVVypVwbJGk16Tm/EXH1Aw7h/xbBS7/rd5KjsP0+KnsDdRfaFCb2bSd33l9YhcPeN9xniVJCkE0XfjiyFZBGuN+OxO0+ORouBNN/gQRfFsYoXqFbmZDN8EfE/DRGTSlrJ/DBhxgB"}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":4,"cache_creation_input_tokens":7451,"cache_read_input_tokens":54844,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":7451},"output_tokens":3,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"8f858ca5-61dd-4bfa-8731-5b9109695a86","timestamp":"2026-11-17T20:31:34.635Z","request_id":"req_011Ch98otqtXQKtL2kwvjfxW","thinking_duration_ms":3060,"thinking_display":"updates"}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98ou4Hpmu75q8EqTJzY","type":"message","role":"assistant","content":[{"type":"tool_use","id":"toolu_016HfU7taud6Fs8bhUM6cmNj","name":"Bash","input":{"command":"cd /home/maxime/aimsight-app; W=labeling/auto/analyses/long-labels/BREITHORN/work; for r in \"2026-10-03T00:00Z 2026-10-13T04:00Z 2\" \"2026-10-16T20:00Z 2026-11-01T00:00Z 13\"; do set -- $r; python3 tools/scripts/ranges.py data/BREITHORN --columns corr_x,corr_y --sensors COLH20,COLI20,COLI21,COLJ19,POUI19,POUI20,COLI24,COLI22,\"COLH20'''\",POUI22,POUI24,POUH21 --start $1 --end $2 --merge 12h > $W/ranges_all_$3.txt; echo \"== $3\"; grep -E '^\\S+ +20' $W/ranges_all_$3.txt | sort -k2,2 | awk '{print $1,$2,$3,$4,$5,$6,$7}' | sort -t' ' -k6 -g | tail -25; done","description":"Ranges per drifting target, all lengths"},"caller":{"type":"direct"}}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":4,"cache_creation_input_tokens":7451,"cache_read_input_tokens":54844,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":7451},"output_tokens":3,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"48e2a0ab-af95-4fcd-b65c-b4e5229c416a","timestamp":"2026-11-17T20:31:37.657Z","request_id":"req_011Ch98otqtXQKtL2kwvjfxW","wire_tool_inputs":{"toolu_016HfU7taud6Fs8bhUM6cmNj":{"command":"cd /home/maxime/aimsight-app; W=labeling/auto/analyses/long-labels/BREITHORN/work; for r in \"2026-10-03T00:00Z 2026-10-13T04:00Z 2\" \"2026-10-16T20:00Z 2026-11-01T00:00Z 13\"; do set -- $r; python3 tools/scripts/ranges.py data/BREITHORN --columns corr_x,corr_y --sensors COLH20,COLI20,COLI21,COLJ19,POUI19,POUI20,COLI24,COLI22,\"COLH20'''\",POUI22,POUI24,POUH21 --start $1 --end $2 --merge 12h > $W/ranges_all_$3.txt; echo \"== $3\"; grep -E '^\\S+ +20' $W/ranges_all_$3.txt | sort -k2,2 | awk '{print $1,$2,$3,$4,$5,$6,$7}' | sort -t' ' -k6 -g | tail -25; done","description":"Ranges per drifting target, all lengths"}}}
-{"type":"system","subtype":"task_summary","detail":"Ranges per drifting target, all lengths","uuid":"f9302421-651a-4276-addd-a28c84e484b2","session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf"}
-{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_016HfU7taud6Fs8bhUM6cmNj","type":"tool_result","content":"== 2\nPOUI19 2026-10-07T00:00Z 2026-10-07T00:00Z 1 -0.0397 -5.3 2026-10-07T00:00Z\nPOUI19 2026-10-12T08:00Z 2026-10-12T08:00Z 1 -0.05751 -5.3 2026-10-12T08:00Z\nPOUH21 2026-10-10T04:00Z 2026-10-10T04:00Z 1 -0.03465 -5.1 2026-10-10T04:00Z\nCOLJ19 2026-10-11T00:00Z 2026-10-11T00:00Z 1 +0.03129 5.1 2026-10-11T00:00Z\nPOUI22 2026-10-05T04:00Z 2026-10-05T04:00Z 1 +0.07261 5.1 2026-10-05T04:00Z\nPOUI22 2026-10-06T04:00Z 2026-10-06T04:00Z 1 +0.0773 5.4 2026-10-06T04:00Z\nCOLI20 2026-10-07T12:00Z 2026-10-07T12:00Z 1 +0.04192 5.6 2026-10-07T12:00Z\nPOUI19 2026-10-09T12:00Z 2026-10-09T12:00Z 1 +0.04354 5.8 2026-10-09T12:00Z\nCOLI20 2026-10-07T12:00Z 2026-10-07T12:00Z 1 +0.05639 5.9 2026-10-07T12:00Z\nPOUI24 2026-10-07T12:00Z 2026-10-07T12:00Z 1 +0.04867 6.8 2026-10-07T12:00Z\nCOLI22 2026-10-07T12:00Z 2026-10-07T12:00Z 1 +0.05743 7.3 2026-10-07T12:00Z\nCOLJ19 2026-10-11T12:00Z 2026-10-13T04:00Z 11 +0.04724 7.7 2026-10-13T00:00Z\nPOUI19 2026-10-07T12:00Z 2026-10-07T12:00Z 1 +0.09486 8.7 2026-10-07T12:00Z\nCOLJ19 2026-10-07T12:00Z 2026-10-07T12:00Z 1 +0.1097 8.9 2026-10-07T12:00Z\nPOUI19 2026-10-10T20:00Z 2026-10-13T04:00Z 14 +0.08356 11.1 2026-10-12T12:00Z\nPOUI24 2026-10-09T00:00Z 2026-10-09T04:00Z 2 +0.1253 14.2 2026-10-09T00:00Z\nPOUI22 2026-10-07T20:00Z 2026-10-07T20:00Z 1 +0.2734 19.1 2026-10-07T20:00Z\nPOUI24 2026-10-13T04:00Z 2026-10-13T04:00Z 1 +0.2221 25.2 2026-10-13T04:00Z\nPOUI22 2026-10-07T12:00Z 2026-10-07T20:00Z 2 +0.1903 25.8 2026-10-07T20:00Z\nPOUI22 2026-10-13T04:00Z 2026-10-13T04:00Z 1 +0.2757 37.3 2026-10-13T04:00Z\nPOUI24 2026-10-09T00:00Z 2026-10-09T04:00Z 2 +0.3558 49.6 2026-10-09T04:00Z\nPOUI24 2026-10-08T00:00Z 2026-10-08T00:00Z 1 +0.4185 58.3 2026-10-08T00:00Z\nCOLH20'''2026-10-07T12:00Z 2026-10-07T12:00Z 1 +0.02826 5.8 2026-10-07T12:00Z 0\nCOLH20'''2026-10-10T04:00Z 2026-10-10T04:00Z 1 -0.03797 -7.8 2026-10-10T04:00Z 0\nCOLH20'''2026-10-10T04:00Z 2026-10-10T04:00Z 1 -0.114 -13.6 2026-10-10T04:00Z 0\n== 13\nPOUI19 2026-10-30T16:00Z 2026-10-31T04:00Z 4 +0.05072 6.3 2026-10-31T00:00Z\nCOLI20 2026-10-31T12:00Z 2026-11-01T00:00Z 4 +0.04967 6.5 2026-10-31T16:00Z\nCOLI20 2026-10-26T16:00Z 2026-10-26T16:00Z 1 +0.05016 6.6 2026-10-26T16:00Z\nPOUI19 2026-10-26T08:00Z 2026-10-26T08:00Z 1 +0.053 6.6 2026-10-26T08:00Z\nCOLI24 2026-10-29T08:00Z 2026-10-29T08:00Z 1 +0.04863 6.7 2026-10-29T08:00Z\nPOUI19 2026-10-29T00:00Z 2026-10-29T08:00Z 3 +0.05891 7.3 2026-10-29T08:00Z\nCOLH20 2026-10-26T08:00Z 2026-10-26T08:00Z 1 +0.0602 7.4 2026-10-26T08:00Z\nPOUH21 2026-10-29T08:00Z 2026-10-29T08:00Z 1 +0.04628 7.9 2026-10-29T08:00Z\nCOLJ19 2026-10-28T20:00Z 2026-10-29T08:00Z 4 +0.06185 8.2 2026-10-29T08:00Z\nPOUI24 2026-10-29T08:00Z 2026-10-29T08:00Z 1 +0.08821 9.3 2026-10-29T08:00Z\nPOUI22 2026-10-21T20:00Z 2026-10-22T04:00Z 3 +0.1516 9.5 2026-10-21T20:00Z\nPOUI22 2026-10-26T16:00Z 2026-10-26T16:00Z 1 +0.09302 9.9 2026-10-26T16:00Z\nCOLH20 2026-10-28T20:00Z 2026-10-29T08:00Z 4 +0.09137 11.2 2026-10-29T04:00Z\nPOUI22 2026-10-23T20:00Z 2026-10-24T00:00Z 2 +0.1791 11.2 2026-10-23T20:00Z\nPOUI22 2026-10-21T20:00Z 2026-10-22T04:00Z 3 +0.114 12.1 2026-10-22T00:00Z\nCOLH20 2026-10-30T00:00Z 2026-10-30T08:00Z 3 +0.1027 12.6 2026-10-30T04:00Z\nPOUI24 2026-10-26T20:00Z 2026-10-26T20:00Z 1 +0.2066 21.8 2026-10-26T20:00Z\nPOUI22 2026-10-23T20:00Z 2026-10-24T00:00Z 2 +0.2609 27.8 2026-10-23T20:00Z\nPOUI22 2026-10-26T00:00Z 2026-10-26T04:00Z 2 +0.3215 34.2 2026-10-26T04:00Z\nPOUI22 2026-10-29T20:00Z 2026-10-30T00:00Z 2 +0.511 54.4 2026-10-29T20:00Z\nPOUI22 2026-10-26T16:00Z 2026-10-26T16:00Z 1 +1.236 77.2 2026-10-26T16:00Z\nCOLH20'''2026-10-29T20:00Z 2026-10-29T20:00Z 1 +0.1717 22.2 2026-10-29T20:00Z 0\nCOLH20'''2026-10-30T00:00Z 2026-10-30T00:00Z 1 -0.0449 -5.8 2026-10-30T00:00Z 0\nCOLH20'''2026-10-30T00:00Z 2026-10-30T00:00Z 1 -0.2293 -26.0 2026-10-30T00:00Z 0\nCOLH20'''2026-10-31T12:00Z 2026-10-31T12:00Z 1 +0.04929 5.6 2026-10-31T12:00Z 0","is_error":false}]},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"f9b5561c-d6f4-49af-8f1f-974f5e404a90","timestamp":"2026-11-17T20:31:38.174Z","tool_use_result":{"stdout":"== 2\nPOUI19 2026-10-07T00:00Z 2026-10-07T00:00Z 1 -0.0397 -5.3 2026-10-07T00:00Z\nPOUI19 2026-10-12T08:00Z 2026-10-12T08:00Z 1 -0.05751 -5.3 2026-10-12T08:00Z\nPOUH21 2026-10-10T04:00Z 2026-10-10T04:00Z 1 -0.03465 -5.1 2026-10-10T04:00Z\nCOLJ19 2026-10-11T00:00Z 2026-10-11T00:00Z 1 +0.03129 5.1 2026-10-11T00:00Z\nPOUI22 2026-10-05T04:00Z 2026-10-05T04:00Z 1 +0.07261 5.1 2026-10-05T04:00Z\nPOUI22 2026-10-06T04:00Z 2026-10-06T04:00Z 1 +0.0773 5.4 2026-10-06T04:00Z\nCOLI20 2026-10-07T12:00Z 2026-10-07T12:00Z 1 +0.04192 5.6 2026-10-07T12:00Z\nPOUI19 2026-10-09T12:00Z 2026-10-09T12:00Z 1 +0.04354 5.8 2026-10-09T12:00Z\nCOLI20 2026-10-07T12:00Z 2026-10-07T12:00Z 1 +0.05639 5.9 2026-10-07T12:00Z\nPOUI24 2026-10-07T12:00Z 2026-10-07T12:00Z 1 +0.04867 6.8 2026-10-07T12:00Z\nCOLI22 2026-10-07T12:00Z 2026-10-07T12:00Z 1 +0.05743 7.3 2026-10-07T12:00Z\nCOLJ19 2026-10-11T12:00Z 2026-10-13T04:00Z 11 +0.04724 7.7 2026-10-13T00:00Z\nPOUI19 2026-10-07T12:00Z 2026-10-07T12:00Z 1 +0.09486 8.7 2026-10-07T12:00Z\nCOLJ19 2026-10-07T12:00Z 2026-10-07T12:00Z 1 +0.1097 8.9 2026-10-07T12:00Z\nPOUI19 2026-10-10T20:00Z 2026-10-13T04:00Z 14 +0.08356 11.1 2026-10-12T12:00Z\nPOUI24 2026-10-09T00:00Z 2026-10-09T04:00Z 2 +0.1253 14.2 2026-10-09T00:00Z\nPOUI22 2026-10-07T20:00Z 2026-10-07T20:00Z 1 +0.2734 19.1 2026-10-07T20:00Z\nPOUI24 2026-10-13T04:00Z 2026-10-13T04:00Z 1 +0.2221 25.2 2026-10-13T04:00Z\nPOUI22 2026-10-07T12:00Z 2026-10-07T20:00Z 2 +0.1903 25.8 2026-10-07T20:00Z\nPOUI22 2026-10-13T04:00Z 2026-10-13T04:00Z 1 +0.2757 37.3 2026-10-13T04:00Z\nPOUI24 2026-10-09T00:00Z 2026-10-09T04:00Z 2 +0.3558 49.6 2026-10-09T04:00Z\nPOUI24 2026-10-08T00:00Z 2026-10-08T00:00Z 1 +0.4185 58.3 2026-10-08T00:00Z\nCOLH20'''2026-10-07T12:00Z 2026-10-07T12:00Z 1 +0.02826 5.8 2026-10-07T12:00Z 0\nCOLH20'''2026-10-10T04:00Z 2026-10-10T04:00Z 1 -0.03797 -7.8 2026-10-10T04:00Z 0\nCOLH20'''2026-10-10T04:00Z 2026-10-10T04:00Z 1 -0.114 -13.6 2026-10-10T04:00Z 0\n== 13\nPOUI19 2026-10-30T16:00Z 2026-10-31T04:00Z 4 +0.05072 6.3 2026-10-31T00:00Z\nCOLI20 2026-10-31T12:00Z 2026-11-01T00:00Z 4 +0.04967 6.5 2026-10-31T16:00Z\nCOLI20 2026-10-26T16:00Z 2026-10-26T16:00Z 1 +0.05016 6.6 2026-10-26T16:00Z\nPOUI19 2026-10-26T08:00Z 2026-10-26T08:00Z 1 +0.053 6.6 2026-10-26T08:00Z\nCOLI24 2026-10-29T08:00Z 2026-10-29T08:00Z 1 +0.04863 6.7 2026-10-29T08:00Z\nPOUI19 2026-10-29T00:00Z 2026-10-29T08:00Z 3 +0.05891 7.3 2026-10-29T08:00Z\nCOLH20 2026-10-26T08:00Z 2026-10-26T08:00Z 1 +0.0602 7.4 2026-10-26T08:00Z\nPOUH21 2026-10-29T08:00Z 2026-10-29T08:00Z 1 +0.04628 7.9 2026-10-29T08:00Z\nCOLJ19 2026-10-28T20:00Z 2026-10-29T08:00Z 4 +0.06185 8.2 2026-10-29T08:00Z\nPOUI24 2026-10-29T08:00Z 2026-10-29T08:00Z 1 +0.08821 9.3 2026-10-29T08:00Z\nPOUI22 2026-10-21T20:00Z 2026-10-22T04:00Z 3 +0.1516 9.5 2026-10-21T20:00Z\nPOUI22 2026-10-26T16:00Z 2026-10-26T16:00Z 1 +0.09302 9.9 2026-10-26T16:00Z\nCOLH20 2026-10-28T20:00Z 2026-10-29T08:00Z 4 +0.09137 11.2 2026-10-29T04:00Z\nPOUI22 2026-10-23T20:00Z 2026-10-24T00:00Z 2 +0.1791 11.2 2026-10-23T20:00Z\nPOUI22 2026-10-21T20:00Z 2026-10-22T04:00Z 3 +0.114 12.1 2026-10-22T00:00Z\nCOLH20 2026-10-30T00:00Z 2026-10-30T08:00Z 3 +0.1027 12.6 2026-10-30T04:00Z\nPOUI24 2026-10-26T20:00Z 2026-10-26T20:00Z 1 +0.2066 21.8 2026-10-26T20:00Z\nPOUI22 2026-10-23T20:00Z 2026-10-24T00:00Z 2 +0.2609 27.8 2026-10-23T20:00Z\nPOUI22 2026-10-26T00:00Z 2026-10-26T04:00Z 2 +0.3215 34.2 2026-10-26T04:00Z\nPOUI22 2026-10-29T20:00Z 2026-10-30T00:00Z 2 +0.511 54.4 2026-10-29T20:00Z\nPOUI22 2026-10-26T16:00Z 2026-10-26T16:00Z 1 +1.236 77.2 2026-10-26T16:00Z\nCOLH20'''2026-10-29T20:00Z 2026-10-29T20:00Z 1 +0.1717 22.2 2026-10-29T20:00Z 0\nCOLH20'''2026-10-30T00:00Z 2026-10-30T00:00Z 1 -0.0449 -5.8 2026-10-30T00:00Z 0\nCOLH20'''2026-10-30T00:00Z 2026-10-30T00:00Z 1 -0.2293 -26.0 2026-10-30T00:00Z 0\nCOLH20'''2026-10-31T12:00Z 2026-10-31T12:00Z 1 +0.04929 5.6 2026-10-31T12:00Z 0","stderr":"","interrupted":false,"isImage":false,"noOutputExpected":false},"tool_result_meta":[{"id":"toolu_016HfU7taud6Fs8bhUM6cmNj","permission_decision":{"decision":"accept","source":"config","reason_type":"rule"}}]}
-{"type":"system","subtype":"thinking_tokens","estimated_tokens":50,"estimated_tokens_delta":50,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"86d00359-4947-4a72-a7ab-e7bdaf446d8b"}
-{"type":"system","subtype":"thinking_tokens","estimated_tokens":150,"estimated_tokens_delta":100,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"79cda03c-4d65-40e5-a661-3ad2be3df950"}
-{"type":"system","subtype":"thinking_tokens","estimated_tokens":281,"estimated_tokens_delta":131,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"d522b8e5-61f0-4161-88e4-9104b89b2f7f"}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98pYH9p8vbb8GUfCYAP","type":"message","role":"assistant","content":[{"type":"thinking","thinking":"","signature":"CAQS2ggKEAgTGAI4AUIIdGhpbmtpbmcSDBAvbLp5RPhdOz/ImRoMolbDpw87YKZ29NheIjAs9Dc+SniC8uYDVBYZnGC4BW44TY6kYsFI6Xsg3UJrCnYvaErxs/iPmtHTEzRhukgq9wewSRdX9LcKF1PkCuXRECUN4bYRr9gbZNPwMKP1GuSakMIzxutdxGfFIN5VCFgc6s/7U0NiGZCVjeidBmrkJewBvOhjSjBWSXj4JgoYVYYnH5TgPQIEHgt3ybTmaFdJ9yD7oNd/N2hdSCpQBxRNndGUXbM57Vns/HhnOZtgr52lDwFvvzEMTEfvGY+Zdt+FsrDUq6Uac6R5B8Zj409qBOSzcAtD7LDkx+ogLTo9u1Xwleq4o8NN55QqRd/J6/DXIa5ncGPYOVzVCmTIsa9/j12+zb/lKxmU0q6bq08sPvuuDmREouNxucRpAqq1+67Ghr8GHmc+D6aTQ6sKOQ32SmOb+yuNqOWySprERm69Trjf9DSgKjPqbkZ+ZEpaIv63MTckjtN0cEEpcnL6kjAI1NuGl/5nUhXjax94yqztSBaDWUPoQWMq5qraS4y9IgaLiV8b6fwZK/GNIZLOAwMDuY8RKTMuVSCzAkR5u9ZPhSUlY0QkNfR6EW3YipOk/VPm28BIao5AvR7N0BuqVsWryz1MpNlVaVFLvsRaHrMy0eCbcbOwUozOysl1TrrFHOuv98Um6dN2RQ/JVTFM7iEA3njSWZkMrttTdW5tHHgnH21fNWeoJMSHtJ338EkKr5PzBTLpI9U4ldzyQnFhVgEhwV6ZEXEUEpScBXaFHqg2yKmlKmDVJZ/vmfGpmFZVIHu56xDRmVp/TjjXYFPdk5b1m9Vgc44oQM9w8dIQLhqozefINQrfKeVGsf4dceftTOVQ1Ybpji2iv5SoOihprQTLwl3GilWbBVehhufUaWkVsAizN+z6x2/WF6dHeDedQZR5y+4+g9M3WM/2bXRWxl4fw7b4fh/UbA0hzMiyGG8Gj6HtxNsY19eLU5rgY/Ldup72WUNL/+SohYFQbgYvHC/C9LKxXkwC386mYHoIGc1ty/3dmNlKwstv1LICpiF3YMxPuX9eezlQf0FpcsviETtXI1Qy8LES/uIwRb7CMM8wIQvnhoKMgMixRfs8AxpgmZ0hnJkv54oiYQy29tDUFeCO6mgX2vsRoPL19DeZ6OFPOSxkKbMRb4yGU2aQchL2NEIgB6Z50117ZoMWSf0QSD+SeBognBOCnLW4BT+HYpDoexPIHKaaixjiCGC0L319K2azKndDlOF7qMyKdKV7CgXB18UiezKplSzMMPiSlz8mikubjhWhxb+ANdvfJoQqd2OlquzFyHnjy2kvLnjsDoinsVTfTBh54qQCtI2TJPdEMMAb6GWXsXO8g8A6Z3vH5OJCFEfb+r2Y3t6un27UbyMDgqInfGurW96sdgNqtvAhU5G6dd73s+5cN2Hx79CV8u2/5LHxW6M38FPdGAE="}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":3568,"cache_read_input_tokens":62295,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":3568},"output_tokens":3,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"1bcce332-87e0-4474-9ee5-3fd35d367582","timestamp":"2026-11-17T20:31:41.899Z","request_id":"req_011Ch98pY4Ftzhbv7k1tqTGc","thinking_duration_ms":2358,"thinking_display":"updates"}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98pYH9p8vbb8GUfCYAP","type":"message","role":"assistant","content":[{"type":"tool_use","id":"toolu_01SetP6xnwHyJaXbUANB8y8f","name":"Bash","input":{"command":"cd /home/maxime/aimsight-app/labeling/auto/analyses/long-labels/BREITHORN; python3 - <<'EOF'\nimport json\nL=[json.loads(l) for l in open('input.jsonl')]\na,b=L\nd=b['description']\nold=\"COLI24 drifts in the opposite direction in corr_y.\"\nassert old in d\nb['description']=d.replace(old, old+\" COLI22, COLH20''', POUI22 and POUI24 drift too, more noisily, between their own rejections.\")\nb.pop('review')\nwith open('labels.jsonl','w') as f:\n for x in (a,b): f.write(json.dumps(x,ensure_ascii=False)+'\\n')\nEOF\ncd /home/maxime/aimsight-app; python3 labeling/scripts/validate.py labeling/auto/analyses/long-labels/BREITHORN/labels.jsonl","description":"Write labels and validate"},"caller":{"type":"direct"}}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":3568,"cache_read_input_tokens":62295,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":3568},"output_tokens":3,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"3c5a4006-c98c-4bde-98ba-6b123545979c","timestamp":"2026-11-17T20:31:44.456Z","request_id":"req_011Ch98pY4Ftzhbv7k1tqTGc","wire_tool_inputs":{"toolu_01SetP6xnwHyJaXbUANB8y8f":{"command":"cd /home/maxime/aimsight-app/labeling/auto/analyses/long-labels/BREITHORN; python3 - <<'EOF'\nimport json\nL=[json.loads(l) for l in open('input.jsonl')]\na,b=L\nd=b['description']\nold=\"COLI24 drifts in the opposite direction in corr_y.\"\nassert old in d\nb['description']=d.replace(old, old+\" COLI22, COLH20''', POUI22 and POUI24 drift too, more noisily, between their own rejections.\")\nb.pop('review')\nwith open('labels.jsonl','w') as f:\n for x in (a,b): f.write(json.dumps(x,ensure_ascii=False)+'\\n')\nEOF\ncd /home/maxime/aimsight-app; python3 labeling/scripts/validate.py labeling/auto/analyses/long-labels/BREITHORN/labels.jsonl","description":"Write labels and validate"}}}
-{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_01SetP6xnwHyJaXbUANB8y8f","type":"tool_result","content":"2 labels, 1 stations: 0 errors, 0 overlaps to look at","is_error":false}]},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"37dcc74d-5902-4ef8-823f-c76f2abce6c6","timestamp":"2026-11-17T20:31:44.593Z","tool_use_result":{"stdout":"2 labels, 1 stations: 0 errors, 0 overlaps to look at","stderr":"","interrupted":false,"isImage":false,"noOutputExpected":false},"tool_result_meta":[{"id":"toolu_01SetP6xnwHyJaXbUANB8y8f","permission_decision":{"decision":"accept","source":"config","reason_type":"rule"}}]}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98q1hfXhW8M7zp9hUKx","type":"message","role":"assistant","content":[{"type":"tool_use","id":"toolu_013tdB5u3gsnip9GYSvZrmEH","name":"Bash","input":{"command":"cd /home/maxime/aimsight-app/labeling/auto/analyses/long-labels/BREITHORN; cat > analysis.md <<'EOF'\n# Requalification of the long labels: BREITHORN\n\nMeasured with `tools/scripts/ranges.py --columns corr_x,corr_y` (k 5, merge 12h) on each label's range, level = median of the range, noise = own noise (work/ranges_*.txt, work/ranges_all_*.txt).\n\n- **BREITHORN-2**: kept. The drift goes beyond the threshold. POUI19 corr_x stays above its level from 10/10 20:00 to the end of the range (14 measurements), up to +11.1 noises (12/10 12:00, +0.084 px, about +0.3 mm). COLJ19 corr_x goes up to +7.7 noises (11 measurements, 11/10 12:00 → 13/10 04:00). This is a movement of the corr, not missing points.\n- **BREITHORN-13**: corrected. The drift goes beyond the threshold: COLH20 corr_x up to +12.6 noises (30/10 04:00, about +0.8 mm), +11.2 noises on 28–29/10; COLJ19 +8.2 noises; POUI19 +7.3 noises; COLI20 +6.5 noises at the end of the range. I applied the correction the period analysts found: COLI22, COLH20''', POUI22 and POUI24 are added to the description. The label loses its review field.\n\nNot checked in this pass (usage limit): the rolling level under the drift (`--rolling`). It is not needed to keep these labels, since the plain level already passes 5 noises.\nEOF\ncat > report.md <<'EOF'\n# BREITHORN long labels: requalification\n\n2 labels: 1 kept, 1 corrected, 0 removed.\n\n- **BREITHORN-13** (corrected): the drift is real, beyond the noise (COLH20 up to about 0.8 mm, about 13 noises). The description now also names COLI22, COLH20''', POUI22 and POUI24, which drift too, as the period analysts found. The review field was removed.\n\nBREITHORN-2 is kept as it is: POUI19 drifts by about 0.3 mm, about 11 noises.\nEOF","description":"Write analysis and report"},"caller":{"type":"direct"}}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":633,"cache_read_input_tokens":65863,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":633},"output_tokens":21,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"34117d0e-901b-4c75-b860-50dcb3d96ae7","timestamp":"2026-11-17T20:31:52.669Z","request_id":"req_011Ch98q1UGjqB2JrtTim8QL","wire_tool_inputs":{"toolu_013tdB5u3gsnip9GYSvZrmEH":{"command":"cd /home/maxime/aimsight-app/labeling/auto/analyses/long-labels/BREITHORN; cat > analysis.md <<'EOF'\n# Requalification of the long labels: BREITHORN\n\nMeasured with `tools/scripts/ranges.py --columns corr_x,corr_y` (k 5, merge 12h) on each label's range, level = median of the range, noise = own noise (work/ranges_*.txt, work/ranges_all_*.txt).\n\n- **BREITHORN-2**: kept. The drift goes beyond the threshold. POUI19 corr_x stays above its level from 10/10 20:00 to the end of the range (14 measurements), up to +11.1 noises (12/10 12:00, +0.084 px, about +0.3 mm). COLJ19 corr_x goes up to +7.7 noises (11 measurements, 11/10 12:00 → 13/10 04:00). This is a movement of the corr, not missing points.\n- **BREITHORN-13**: corrected. The drift goes beyond the threshold: COLH20 corr_x up to +12.6 noises (30/10 04:00, about +0.8 mm), +11.2 noises on 28–29/10; COLJ19 +8.2 noises; POUI19 +7.3 noises; COLI20 +6.5 noises at the end of the range. I applied the correction the period analysts found: COLI22, COLH20''', POUI22 and POUI24 are added to the description. The label loses its review field.\n\nNot checked in this pass (usage limit): the rolling level under the drift (`--rolling`). It is not needed to keep these labels, since the plain level already passes 5 noises.\nEOF\ncat > report.md <<'EOF'\n# BREITHORN long labels: requalification\n\n2 labels: 1 kept, 1 corrected, 0 removed.\n\n- **BREITHORN-13** (corrected): the drift is real, beyond the noise (COLH20 up to about 0.8 mm, about 13 noises). The description now also names COLI22, COLH20''', POUI22 and POUI24, which drift too, as the period analysts found. The review field was removed.\n\nBREITHORN-2 is kept as it is: POUI19 drifts by about 0.3 mm, about 11 noises.\nEOF","description":"Write analysis and report"}}}
-{"type":"system","subtype":"task_summary","detail":"Writing analysis and reporting","uuid":"7c974ecd-686c-468d-adbb-3f85023a5b25","session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf"}
-{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_013tdB5u3gsnip9GYSvZrmEH","type":"tool_result","content":"(Bash completed with no output)","is_error":false}]},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"2653e552-9053-41ed-9d90-e8265f8c9663","timestamp":"2026-11-17T20:31:52.750Z","tool_use_result":{"stdout":"","stderr":"","interrupted":false,"isImage":false,"noOutputExpected":false},"tool_result_meta":[{"id":"toolu_013tdB5u3gsnip9GYSvZrmEH","permission_decision":{"decision":"accept","source":"config","reason_type":"rule"}}]}
-{"type":"system","subtype":"thinking_tokens","estimated_tokens":50,"estimated_tokens_delta":50,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"64d5f7e3-30af-4af2-a07e-e288ebfc7cd3"}
-{"type":"system","subtype":"thinking_tokens","estimated_tokens":199,"estimated_tokens_delta":149,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"b7c04375-2240-4e13-b6c0-033a80a14cd3"}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98qcmoDsxxpjmdqs4Yi","type":"message","role":"assistant","content":[{"type":"thinking","thinking":"","signature":"CAQSkgYKEAgTGAI4AUIIdGhpbmtpbmcSDDmMDUMFrDhZJwQqGxoMC4KsUoG5+MMsQDvkIjAh9a3HkrtLPf1/Cyan5Xs/PiI/ty65Ok1RCS72tSj677vW2KL9FKaRy0vnGnW7M5QqrwUzv9ddpFBoM7OgANhxSV8LkbXQSTOrdMVvcjThJAatC82y/nHvkO1snt8lWXwAFXqGglAJkCXpBBmL9Y5ppq+0+to9X6aNiT9eC+OjEzj8HMFP3n7o+SJkR9EkJdP5QGyBpAQqGu3N1kKV2rSxbzdzRmHmxZz7cO4rI5/PHfDzMJP5mH0RJRC7539sGTlyaBCbRU8KikA0QuG3K0+JVVz6FxOwn5tLW2Q8P4x3cACjOiXoDuMe55Hm5/sgWwE8IJyGplpLGURMNcEWlWxR6+2A1D2FrR7Hg22xRrDX5EGHjrPFggqn6FRGzQT3vtv/72UfRJMlVIocH1sh3B8t/rvE3rH4UMbFln8T/m484af9Gg2gaOxrqcLvKzzvO/24Z567Lq3FTDwDo1S98A7MFDAneIar0c6RQ+H1NfzT9iCRkPHzGgg66Py0tUFxxYtiOct1+8IXRsTlR9Aik/UaQ/RZavkJJJNrWqBhbIvOzDcBXLPOMHzw3HUTsFWj2FOW8DJc4CBmWXzxi0+xwvMsvGBcZwi+5+VGqX+0EDLVQv1fpOixC7ENjDldXX7VmqzKRiyg1X5wIdEsK67Etzbr1QK4MwPF763OwVFZxk3MrLOEFI5womrvWK6o3RSFppAZPGuQKge5djhtEfPAsRftxMxsFIjj0KwhR1M8ZjpT6Xe4/a9ioM9VMF0Z7cLCCwlpC1uSgZnG5k64MWfkRJsOaHmcgpv5GtNDQs9HS5uqK160O9M1a2aJ3+TAyZN55LhVhGiGcGAWcglmLxkUc5u5HW7ORBv/jqFWHAohfdNt2/G/My+yWAshZ3+kmzx5YAshJcd/ujbsuXvtoWb7VNQTyX249frvfVFBm+Mfmq37vDEH/O4YsBrtHSYRHiBWowidJvwmZP3ILSvHo4pX5M9D8AMYAQ=="}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":913,"cache_read_input_tokens":66496,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":913},"output_tokens":3,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"a9bafa6d-1b70-4ba6-85ea-2d00bec5af18","timestamp":"2026-11-17T20:32:01.169Z","request_id":"req_011Ch98qcZAGTtuSXU5RvW2K","thinking_duration_ms":6181,"thinking_display":"updates"}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98qcmoDsxxpjmdqs4Yi","type":"message","role":"assistant","content":[{"type":"text","text":"J'ai requalifié les 2 labels longs de BREITHORN : 1 gardé tel quel, 1 corrigé, aucun supprimé. Le fichier de labels passe la validation avec 0 erreur.\n\n- **BREITHORN-2** (gardé tel quel) : la dérive dépasse bien le seuil de 5 bruits. Sur `corr_x`, POUI19 monte jusqu'à environ 11 bruits (à peu près +0,3 mm) et COLJ19 jusqu'à environ 8 bruits.\n- **BREITHORN-13** (corrigé) : la dérive dépasse aussi le seuil. COLH20 monte jusqu'à environ 13 bruits sur `corr_x` (à peu près +0,8 mm), COLJ19 et POUI19 vers 7 à 8 bruits. J'ai ajouté à la description COLI22, COLH20''', POUI22 et POUI24, la correction trouvée par les analystes de période. Le label perd donc son champ review.\n\n**Pas fait :** je n'ai pas relancé la mesure avec `--rolling` sous la dérive. Elle ne changerait pas la décision, puisque le niveau calculé sur toute la plage dépasse déjà 5 bruits. En revanche, je n'ai pas vérifié moi-même que les quatre cibles ajoutées dérivent vraiment : j'ai appliqué la correction telle que fournie.\n\nLa limite d'usage a été atteinte, donc l'analyse et le rapport sont courts. Pour finir, il resterait à confirmer la dérive de ces quatre cibles sur leur courbe glissante et à étoffer `analysis.md`.\n\nFichiers dans `labeling/auto/analyses/long-labels/BREITHORN/` :\n- `labels.jsonl`\n- `analysis.md`\n- `report.md`"}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":913,"cache_read_input_tokens":66496,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":913},"output_tokens":3,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","uuid":"855bd7ff-a880-433c-be7d-6af67d0aec2d","timestamp":"2026-11-17T20:32:01.182Z","request_id":"req_011Ch98qcZAGTtuSXU5RvW2K"}
-{"type":"system","subtype":"post_turn_summary","summarizes_uuid":"855bd7ff-a880-433c-be7d-6af67d0aec2d","status_category":"review_ready","status_detail":"- `report.md`","needs_action":"","uuid":"e0a62029-a1fc-483b-a242-7bd3890ac023","session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf"}
-{"duration_api_ms":59780,"stop_reason":"end_turn","session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf","total_cost_usd":0.6779048000000001,"usage":{"input_tokens":24,"cache_creation_input_tokens":61433,"cache_read_input_tokens":442724,"output_tokens":4890,"output_tokens_details":{"thinking_tokens":941},"server_tool_use":{"web_search_requests":0,"web_fetch_requests":0},"service_tier":"standard","cache_creation":{"ephemeral_1h_input_tokens":61433,"ephemeral_5m_input_tokens":0},"inference_geo":"global","iterations":[{"input_tokens":2,"output_tokens":719,"cache_read_input_tokens":66496,"cache_creation_input_tokens":913,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":913},"type":"message"}],"speed":"standard","fallback_credit":null},"modelUsage":{"claude-opus-5-5":{"inputTokens":24,"outputTokens":4890,"cacheReadInputTokens":442724,"cacheCreationInputTokens":61433,"webSearchRequests":0,"costUSD":0.6779048000000001,"contextWindow":1000000,"maxOutputTokens":128000,"thinkingTokens":941,"cacheCreationEphemeral5mInputTokens":0,"cacheCreationEphemeral1hInputTokens":61433,"canonicalModel":"claude-opus-5-5","provider":"firstParty","costBasis":"list"}},"permission_denials":[],"terminal_reason":"completed","fast_mode_state":"off","fast_mode_disabled_reason":"sdk_opt_in_required","subagent_stats":{"spawned":0,"requested":{"background":0,"foreground":0,"unset":0},"started_in_background":0,"max_depth":0,"spawned_by_subagents":0,"completed":0,"failed":0,"killed":{"parent":0,"user":0,"system":0},"refused":{"depth_limit":0,"concurrency_limit":0,"budget":0},"by_type":{}},"safety_stops":0,"is_error":false,"num_turns":15,"subtype":"success","api_error_status":null,"result":"J'ai requalifié les 2 labels longs de BREITHORN : 1 gardé tel quel, 1 corrigé, aucun supprimé. Le fichier de labels passe la validation avec 0 erreur.\n\n- **BREITHORN-2** (gardé tel quel) : la dérive dépasse bien le seuil de 5 bruits. Sur `corr_x`, POUI19 monte jusqu'à environ 11 bruits (à peu près +0,3 mm) et COLJ19 jusqu'à environ 8 bruits.\n- **BREITHORN-13** (corrigé) : la dérive dépasse aussi le seuil. COLH20 monte jusqu'à environ 13 bruits sur `corr_x` (à peu près +0,8 mm), COLJ19 et POUI19 vers 7 à 8 bruits. J'ai ajouté à la description COLI22, COLH20''', POUI22 et POUI24, la correction trouvée par les analystes de période. Le label perd donc son champ review.\n\n**Pas fait :** je n'ai pas relancé la mesure avec `--rolling` sous la dérive. Elle ne changerait pas la décision, puisque le niveau calculé sur toute la plage dépasse déjà 5 bruits. En revanche, je n'ai pas vérifié moi-même que les quatre cibles ajoutées dérivent vraiment : j'ai appliqué la correction telle que fournie.\n\nLa limite d'usage a été atteinte, donc l'analyse et le rapport sont courts. Pour finir, il resterait à confirmer la dérive de ces quatre cibles sur leur courbe glissante et à étoffer `analysis.md`.\n\nFichiers dans `labeling/auto/analyses/long-labels/BREITHORN/` :\n- `labels.jsonl`\n- `analysis.md`\n- `report.md`","ttft_ms":3069,"type":"result","duration_ms":65092,"uuid":"486c4561-e140-4344-b126-d4f3a2eb5e31","ttft_stream_ms":2509,"time_to_request_ms":789,"time_to_request_phases_ms":{"other":14,"system_prompt":282,"resume_other":0,"process_user_input":12,"input_attachments":134,"input_hooks":6,"conversation_append":2,"transcript_persist":101,"tool_pool_refresh":18,"init_message":24,"init_frame_send":9,"engine_pickup":3,"loop_entry":25,"message_prep":3,"model_config_wait":4,"autocompact":4,"request_announcements":23,"query_setup":1,"model_gates":1,"tool_schema_build":17,"message_normalization":6,"client_creation":18,"request_build":82},"turn_start_resume_kind":"none","process_turn_index":0,"time_to_request_loop_lag_ms":220,"time_to_request_cpu_ms":1277,"time_to_request_major_faults":0,"input_attachments_detail":{"slowest_producer":"session_settings","slowest_producer_ms":114,"cpu_ms":82,"major_faults":0,"setup_ms":2,"prompt_producers_ms":2,"ambient_start_ms":8,"ambient_wait_ms":113,"render_ms":5,"producers":43,"token_counts":0},"tool_schema_build_detail":{"betas_ms":1,"waits_ms":2,"placement_ms":2,"render_ms":11,"after_ms":1,"other_ms":0,"tools":3,"new_schemas":3},"message_normalization_detail":{"before_ms":0,"normalize_ms":4,"images_ms":0,"post_process_ms":1,"after_ms":1,"other_ms":0,"messages":9,"wire_messages":2},"request_build_detail":{"records_ms":1,"system_ms":3,"headers_ms":2,"cache_break_record_ms":2,"plans_ms":2,"retry_setup_ms":0,"sent_build_ms":10,"record_attempt_ms":62,"other_ms":0,"sent_build_safety_context_ms":0,"sent_build_cache_breakpoints_ms":2,"sent_build_surrogate_scan_ms":0},"first_content_frame_ms":2510,"queued_turn_count":0,"result_index":0,"model_usage_since_last_result":{"claude-opus-5-5":{"inputTokens":24,"outputTokens":4890,"cacheReadInputTokens":442724,"cacheCreationInputTokens":61433,"webSearchRequests":0,"costUSD":0.6779048000000001,"contextWindow":1000000,"maxOutputTokens":128000,"thinkingTokens":941,"cacheCreationEphemeral5mInputTokens":0,"cacheCreationEphemeral1hInputTokens":61433,"canonicalModel":"claude-opus-5-5","provider":"firstParty","costBasis":"list"}},"credential_expires_at":"2026-12-14T16:38:37.087Z"}
-{"type":"system","subtype":"task_summary","detail":null,"uuid":"e0487fb6-988f-43bc-9ca8-ada3c3481b63","session_id":"b1dece15-7ed2-440e-993c-de42f2e6a4bf"}
diff --git a/auto/analyses/long-labels/BREITHORN/work/ranges_13.txt b/auto/analyses/long-labels/BREITHORN/work/ranges_13.txt
deleted file mode 100644
index 0440d73..0000000
--- a/auto/analyses/long-labels/BREITHORN/work/ranges_13.txt
+++ /dev/null
@@ -1,92 +0,0 @@
-
-== corr_x: level, noise, largest jump from one measurement to the next ==
-sensor n level noise jump (noises) between
-REFG44N 92 0.0323 0.00347 +0.03735 10.8 2026-10-26T04:00Z and 2026-10-26T08:00Z
-REFH22 88 -0.003408 0.005 -0.02222 -4.4 2026-10-26T12:00Z and 2026-10-27T00:00Z
-REFI'21 92 0.02696 0.00296 +0.03238 11.0 2026-10-26T04:00Z and 2026-10-26T08:00Z
-REFPOU22 88 -0.05694 0.00319 -0.0162 -5.1 2026-10-22T00:00Z and 2026-10-22T04:00Z
-COLH20 92 0.1104 0.0052 +0.04307 8.3 2026-10-26T04:00Z and 2026-10-26T08:00Z
-COLH20''' 88 -0.003447 0.00772 -0.2166 -28.0 2026-10-29T20:00Z and 2026-10-30T00:00Z
-COLI20 92 0.06404 0.00764 -0.04873 -6.4 2026-10-25T20:00Z and 2026-10-26T00:00Z
-COLI21 92 0.1319 0.011 +0.08134 7.4 2026-10-19T08:00Z and 2026-10-19T12:00Z
-COLI22 87 -0.005334 0.0127 -0.8344 -65.7 2026-10-23T16:00Z and 2026-10-23T20:00Z
-COLI24 69 -0.009728 0.00729 -0.05299 -7.3 2026-10-29T08:00Z and 2026-10-29T12:00Z
-COLJ19 92 0.2332 0.00755 +0.0571 7.6 2026-10-26T04:00Z and 2026-10-26T08:00Z
-POUH21 92 0.0165 0.00584 -0.04224 -7.2 2026-10-29T08:00Z and 2026-10-29T12:00Z
-POUI19 92 0.4154 0.00802 +0.05978 7.5 2026-10-26T04:00Z and 2026-10-26T08:00Z
-POUI20 92 0.1139 0.00558 -0.04597 -8.2 2026-10-25T20:00Z and 2026-10-26T00:00Z
-POUI22 78 -0.0315 0.0094 +0.5136 54.6 2026-10-29T16:00Z and 2026-10-29T20:00Z
-POUI24 86 0.07349 0.00946 -0.2316 -24.5 2026-10-26T20:00Z and 2026-10-27T00:00Z
-
-corr_x: ranges more than 5 noises from the level (merge 60 min); 0 of at least 6 measurements out of 170
-sensor start end measurements extreme (noises) at rejected
-(none)
-
-== corr_y: level, noise, largest jump from one measurement to the next ==
-sensor n level noise jump (noises) between
-REFG44N 92 0.01141 0.00512 +0.0517 10.1 2026-10-28T08:00Z and 2026-10-28T12:00Z
-REFH22 88 -0.05604 0.01 +0.03504 3.5 2026-10-24T04:00Z and 2026-10-24T08:00Z
-REFI'21 92 0.01533 0.00421 +0.04284 10.2 2026-10-28T08:00Z and 2026-10-28T12:00Z
-REFPOU22 88 0.02956 0.00977 -0.0705 -7.2 2026-10-29T08:00Z and 2026-10-29T12:00Z
-COLH20 92 0.1286 0.00817 -0.06091 -7.5 2026-10-19T08:00Z and 2026-10-19T12:00Z
-COLH20''' 88 -0.008465 0.00883 -0.2612 -29.6 2026-10-29T20:00Z and 2026-10-30T00:00Z
-COLI20 92 0.02538 0.00962 +0.04766 5.0 2026-10-29T08:00Z and 2026-10-29T12:00Z
-COLI21 92 0.06171 0.0118 +0.08119 6.9 2026-10-29T08:00Z and 2026-10-29T12:00Z
-COLI22 87 0.03629 0.00742 +0.1536 20.7 2026-10-23T04:00Z and 2026-10-23T08:00Z
-COLI24 69 -0.1456 0.00982 +0.06328 6.4 2026-10-29T16:00Z and 2026-10-30T04:00Z
-COLJ19 92 0.02882 0.0112 +0.06114 5.5 2026-10-30T16:00Z and 2026-10-30T20:00Z
-POUH21 92 -0.01284 0.00734 -0.02311 -3.1 2026-10-26T12:00Z and 2026-10-26T16:00Z
-POUI19 92 -0.1173 0.00767 -0.04744 -6.2 2026-10-29T08:00Z and 2026-10-29T12:00Z
-POUI20 92 -0.01327 0.00834 -0.04015 -4.8 2026-10-21T04:00Z and 2026-10-21T08:00Z
-POUI22 78 -0.09938 0.016 -1.289 -80.5 2026-10-26T16:00Z and 2026-10-27T08:00Z
-POUI24 86 -0.02697 0.0121 +0.07923 6.6 2026-10-26T20:00Z and 2026-10-27T00:00Z
-
-corr_y: ranges more than 5 noises from the level (merge 60 min); 0 of at least 6 measurements out of 102
-sensor start end measurements extreme (noises) at rejected
-(none)
-
-== corr_x_mm: level, noise, largest jump from one measurement to the next ==
-sensor n level noise jump (noises) between
-REFG44N 0 (fewer than 2 values)
-REFH22 0 (fewer than 2 values)
-REFI'21 0 (fewer than 2 values)
-REFPOU22 0 (fewer than 2 values)
-COLH20 92 0.8962 0.0422 +0.3495 8.3 2026-10-26T04:00Z and 2026-10-26T08:00Z
-COLH20''' 88 -0.0295 0.0661 -1.854 -28.0 2026-10-29T20:00Z and 2026-10-30T00:00Z
-COLI20 92 0.4849 0.0578 -0.3689 -6.4 2026-10-25T20:00Z and 2026-10-26T00:00Z
-COLI21 92 1.497 0.125 +0.9233 7.4 2026-10-19T08:00Z and 2026-10-19T12:00Z
-COLI22 87 -0.08003 0.19 -12.52 -65.7 2026-10-23T16:00Z and 2026-10-23T20:00Z
-COLI24 69 -0.2193 0.164 -1.194 -7.3 2026-10-29T08:00Z and 2026-10-29T12:00Z
-COLJ19 92 0.7631 0.0247 +0.1868 7.6 2026-10-26T04:00Z and 2026-10-26T08:00Z
-POUH21 92 0.1872 0.0662 -0.4793 -7.2 2026-10-29T08:00Z and 2026-10-29T12:00Z
-POUI19 92 1.473 0.0284 +0.2119 7.5 2026-10-26T04:00Z and 2026-10-26T08:00Z
-POUI20 92 0.8883 0.0435 -0.3585 -8.2 2026-10-25T20:00Z and 2026-10-26T00:00Z
-POUI22 78 -0.4795 0.143 +7.817 54.6 2026-10-29T16:00Z and 2026-10-29T20:00Z
-POUI24 86 1.678 0.216 -5.288 -24.5 2026-10-26T20:00Z and 2026-10-27T00:00Z
-
-corr_x_mm: ranges more than 5 noises from the level (merge 60 min); 0 of at least 6 measurements out of 157
-sensor start end measurements extreme (noises) at rejected
-(none)
-
-== corr_y_mm: level, noise, largest jump from one measurement to the next ==
-sensor n level noise jump (noises) between
-REFG44N 0 (fewer than 2 values)
-REFH22 0 (fewer than 2 values)
-REFI'21 0 (fewer than 2 values)
-REFPOU22 0 (fewer than 2 values)
-COLH20 92 1.044 0.0663 -0.4943 -7.5 2026-10-19T08:00Z and 2026-10-19T12:00Z
-COLH20''' 88 -0.07246 0.0755 -2.236 -29.6 2026-10-29T20:00Z and 2026-10-30T00:00Z
-COLI20 92 0.1922 0.0728 +0.3608 5.0 2026-10-29T08:00Z and 2026-10-29T12:00Z
-COLI21 92 0.7005 0.134 +0.9216 6.9 2026-10-29T08:00Z and 2026-10-29T12:00Z
-COLI22 87 0.5444 0.111 +2.304 20.7 2026-10-23T04:00Z and 2026-10-23T08:00Z
-COLI24 69 -3.282 0.221 +1.426 6.4 2026-10-29T16:00Z and 2026-10-30T04:00Z
-COLJ19 92 0.09428 0.0366 +0.2 5.5 2026-10-30T16:00Z and 2026-10-30T20:00Z
-POUH21 92 -0.1456 0.0833 -0.2622 -3.1 2026-10-26T12:00Z and 2026-10-26T16:00Z
-POUI19 92 -0.4159 0.0272 -0.1682 -6.2 2026-10-29T08:00Z and 2026-10-29T12:00Z
-POUI20 92 -0.1035 0.065 -0.3131 -4.8 2026-10-21T04:00Z and 2026-10-21T08:00Z
-POUI22 78 -1.513 0.244 -19.62 -80.5 2026-10-26T16:00Z and 2026-10-27T08:00Z
-POUI24 86 -0.6158 0.276 +1.809 6.6 2026-10-26T20:00Z and 2026-10-27T00:00Z
-
-corr_y_mm: ranges more than 5 noises from the level (merge 60 min); 0 of at least 6 measurements out of 83
-sensor start end measurements extreme (noises) at rejected
-(none)
diff --git a/auto/analyses/long-labels/BREITHORN/work/ranges_2.txt b/auto/analyses/long-labels/BREITHORN/work/ranges_2.txt
deleted file mode 100644
index 661dda6..0000000
--- a/auto/analyses/long-labels/BREITHORN/work/ranges_2.txt
+++ /dev/null
@@ -1,46 +0,0 @@
-
-== corr_x: level, noise, largest jump from one measurement to the next ==
-sensor n level noise jump (noises) between
-REFG44N 62 0.02075 0.00364 +0.07406 20.4 2026-10-04T16:00Z and 2026-10-04T20:00Z
-REFH22 60 0.006956 0.00503 +0.1296 25.8 2026-10-04T12:00Z and 2026-10-04T16:00Z
-REFI'21 61 0.01611 0.00329 +0.06322 19.2 2026-10-04T16:00Z and 2026-10-04T20:00Z
-REFPOU22 52 -0.0439 0.00456 +0.03488 7.7 2026-10-10T04:00Z and 2026-10-10T08:00Z
-COLH20 62 0.05263 0.00816 +0.07961 9.8 2026-10-04T16:00Z and 2026-10-04T20:00Z
-COLH20''' 51 0.02156 0.00486 +0.03378 7.0 2026-10-10T04:00Z and 2026-10-10T08:00Z
-COLI20 62 0.002981 0.00751 +0.06947 9.3 2026-10-04T16:00Z and 2026-10-04T20:00Z
-COLI21 62 0.02725 0.0141 +0.06925 4.9 2026-10-04T16:00Z and 2026-10-04T20:00Z
-COLI22 54 -0.002826 0.00782 +0.09883 12.6 2026-10-04T16:00Z and 2026-10-04T20:00Z
-COLI24 52 0.004593 0.00934 +0.07898 8.5 2026-10-04T16:00Z and 2026-10-04T20:00Z
-COLJ19 62 0.1228 0.00616 +0.06809 11.1 2026-10-04T16:00Z and 2026-10-04T20:00Z
-POUH21 62 0.01067 0.00676 +0.07469 11.1 2026-10-04T16:00Z and 2026-10-04T20:00Z
-POUI19 62 0.209 0.0075 +0.07604 10.1 2026-10-04T16:00Z and 2026-10-04T20:00Z
-POUI20 62 0.05464 0.00692 +0.0734 10.6 2026-10-04T16:00Z and 2026-10-04T20:00Z
-POUI22 44 -0.03399 0.00738 +0.2778 37.6 2026-10-13T00:00Z and 2026-10-13T04:00Z
-POUI24 60 0.04776 0.00882 +0.2178 24.7 2026-10-13T00:00Z and 2026-10-13T04:00Z
-
-corr_x: ranges more than 5 noises from the level (merge 60 min); 0 of at least 6 measurements out of 90
-sensor start end measurements extreme (noises) at rejected
-(none)
-
-== corr_y: level, noise, largest jump from one measurement to the next ==
-sensor n level noise jump (noises) between
-REFG44N 62 0.01303 0.00481 +0.1232 25.6 2026-10-10T04:00Z and 2026-10-10T08:00Z
-REFH22 60 -0.02975 0.00508 +0.3601 70.9 2026-10-10T00:00Z and 2026-10-10T04:00Z
-REFI'21 61 0.01426 0.00407 +0.121 29.7 2026-10-10T04:00Z and 2026-10-10T08:00Z
-REFPOU22 52 -0.002744 0.00776 -0.1199 -15.4 2026-10-10T00:00Z and 2026-10-10T04:00Z
-COLH20 62 0.06168 0.0122 -0.1213 -10.0 2026-10-10T00:00Z and 2026-10-10T04:00Z
-COLH20''' 51 -0.03286 0.00835 +0.1216 14.6 2026-10-10T04:00Z and 2026-10-10T08:00Z
-COLI20 62 -0.04809 0.00954 +0.1165 12.2 2026-10-10T04:00Z and 2026-10-10T08:00Z
-COLI21 62 -0.02485 0.0112 +0.117 10.4 2026-10-10T04:00Z and 2026-10-10T08:00Z
-COLI22 54 0.02148 0.0092 +0.2358 25.6 2026-10-04T16:00Z and 2026-10-04T20:00Z
-COLI24 52 -0.09136 0.0134 +0.1254 9.4 2026-10-04T16:00Z and 2026-10-04T20:00Z
-COLJ19 62 -0.03669 0.0124 -0.1162 -9.4 2026-10-04T12:00Z and 2026-10-04T16:00Z
-POUH21 62 -0.01986 0.00785 +0.1152 14.7 2026-10-04T16:00Z and 2026-10-04T20:00Z
-POUI19 62 -0.1216 0.0109 -0.1134 -10.4 2026-10-10T00:00Z and 2026-10-10T04:00Z
-POUI20 62 -0.05099 0.0101 +0.1135 11.2 2026-10-04T16:00Z and 2026-10-04T20:00Z
-POUI22 44 -0.07427 0.0143 -0.3166 -22.2 2026-10-13T00:00Z and 2026-10-13T04:00Z
-POUI24 60 -0.009546 0.00718 -0.4317 -60.2 2026-10-08T00:00Z and 2026-10-08T04:00Z
-
-corr_y: ranges more than 5 noises from the level (merge 60 min); 0 of at least 6 measurements out of 47
-sensor start end measurements extreme (noises) at rejected
-(none)
diff --git a/auto/analyses/long-labels/BREITHORN/work/ranges_all_13.txt b/auto/analyses/long-labels/BREITHORN/work/ranges_all_13.txt
deleted file mode 100644
index aae9bd7..0000000
--- a/auto/analyses/long-labels/BREITHORN/work/ranges_all_13.txt
+++ /dev/null
@@ -1,104 +0,0 @@
-
-== corr_x: level, noise, largest jump from one measurement to the next ==
-sensor n level noise jump (noises) between
-COLH20 92 0.1104 0.0052 +0.04307 8.3 2026-10-26T04:00Z and 2026-10-26T08:00Z
-COLI20 92 0.06404 0.00764 -0.04873 -6.4 2026-10-25T20:00Z and 2026-10-26T00:00Z
-COLI21 92 0.1319 0.011 +0.08134 7.4 2026-10-19T08:00Z and 2026-10-19T12:00Z
-COLJ19 92 0.2332 0.00755 +0.0571 7.6 2026-10-26T04:00Z and 2026-10-26T08:00Z
-POUI19 92 0.4154 0.00802 +0.05978 7.5 2026-10-26T04:00Z and 2026-10-26T08:00Z
-POUI20 92 0.1139 0.00558 -0.04597 -8.2 2026-10-25T20:00Z and 2026-10-26T00:00Z
-COLI24 69 -0.009728 0.00729 -0.05299 -7.3 2026-10-29T08:00Z and 2026-10-29T12:00Z
-COLI22 87 -0.005334 0.0127 -0.8344 -65.7 2026-10-23T16:00Z and 2026-10-23T20:00Z
-COLH20''' 88 -0.003447 0.00772 -0.2166 -28.0 2026-10-29T20:00Z and 2026-10-30T00:00Z
-POUI22 78 -0.0315 0.0094 +0.5136 54.6 2026-10-29T16:00Z and 2026-10-29T20:00Z
-POUI24 86 0.07349 0.00946 -0.2316 -24.5 2026-10-26T20:00Z and 2026-10-27T00:00Z
-POUH21 92 0.0165 0.00584 -0.04224 -7.2 2026-10-29T08:00Z and 2026-10-29T12:00Z
-
-corr_x: ranges more than 5 noises from the level (merge 720 min)
-sensor start end measurements extreme (noises) at rejected
-COLH20 2026-10-16T20:00Z 2026-10-18T08:00Z 8 -0.04848 -9.3 2026-10-16T20:00Z 0
-COLH20 2026-10-26T04:00Z 2026-10-26T04:00Z 1 -0.02661 -5.1 2026-10-26T04:00Z 0
-COLI20 2026-10-16T20:00Z 2026-10-19T20:00Z 17 -0.06111 -8.0 2026-10-18T16:00Z 0
-COLI20 2026-10-26T16:00Z 2026-10-26T16:00Z 1 +0.05016 6.6 2026-10-26T16:00Z 0
-COLI20 2026-10-31T12:00Z 2026-11-01T00:00Z 4 +0.04967 6.5 2026-10-31T16:00Z 0
-COLI21 2026-10-16T20:00Z 2026-10-19T08:00Z 10 -0.1063 -9.6 2026-10-19T08:00Z 0
-COLJ19 2026-10-16T20:00Z 2026-10-20T16:00Z 23 -0.09631 -12.8 2026-10-16T20:00Z 0
-COLJ19 2026-10-26T08:00Z 2026-10-26T08:00Z 1 +0.03835 5.1 2026-10-26T08:00Z 0
-COLJ19 2026-10-28T20:00Z 2026-10-29T08:00Z 4 +0.06185 8.2 2026-10-29T08:00Z 0
-COLJ19 2026-10-30T04:00Z 2026-10-30T04:00Z 1 +0.04486 5.9 2026-10-30T04:00Z 0
-POUI19 2026-10-16T20:00Z 2026-10-21T20:00Z 31 -0.1755 -21.9 2026-10-17T04:00Z 0
-POUI19 2026-10-26T08:00Z 2026-10-26T08:00Z 1 +0.053 6.6 2026-10-26T08:00Z 0
-POUI19 2026-10-29T00:00Z 2026-10-29T08:00Z 3 +0.05891 7.3 2026-10-29T08:00Z 0
-POUI19 2026-10-30T04:00Z 2026-10-30T04:00Z 1 +0.04176 5.2 2026-10-30T04:00Z 0
-POUI19 2026-10-30T16:00Z 2026-10-31T04:00Z 4 +0.05072 6.3 2026-10-31T00:00Z 0
-POUI19 2026-10-31T16:00Z 2026-11-01T00:00Z 3 +0.04911 6.1 2026-10-31T20:00Z 0
-POUI20 2026-10-16T20:00Z 2026-10-18T16:00Z 12 -0.0584 -10.5 2026-10-17T04:00Z 0
-POUI20 2026-10-20T04:00Z 2026-10-20T04:00Z 1 -0.03357 -6.0 2026-10-20T04:00Z 0
-POUI20 2026-10-26T00:00Z 2026-10-26T00:00Z 1 -0.02806 -5.0 2026-10-26T00:00Z 0
-POUI20 2026-10-29T08:00Z 2026-10-29T08:00Z 1 +0.02853 5.1 2026-10-29T08:00Z 0
-POUI20 2026-10-31T20:00Z 2026-10-31T20:00Z 1 +0.03429 6.1 2026-10-31T20:00Z 0
-COLI24 2026-10-29T08:00Z 2026-10-29T08:00Z 1 +0.04863 6.7 2026-10-29T08:00Z 0
-COLI22 2026-10-21T20:00Z 2026-10-22T04:00Z 3 -0.1092 -8.6 2026-10-21T20:00Z 0
-COLI22 2026-10-22T20:00Z 2026-10-22T20:00Z 1 -0.07188 -5.7 2026-10-22T20:00Z 0
-COLI22 2026-10-23T20:00Z 2026-10-24T00:00Z 2 -0.8431 -66.4 2026-10-23T20:00Z 0
-COLI22 2026-10-26T16:00Z 2026-10-26T16:00Z 1 +0.07106 5.6 2026-10-26T16:00Z 0
-COLI22 2026-10-29T20:00Z 2026-10-30T00:00Z 2 -0.08981 -7.1 2026-10-29T20:00Z 0
-COLH20'''2026-10-29T20:00Z 2026-10-29T20:00Z 1 +0.1717 22.2 2026-10-29T20:00Z 0
-COLH20'''2026-10-30T00:00Z 2026-10-30T00:00Z 1 -0.0449 -5.8 2026-10-30T00:00Z 0
-POUI22 2026-10-21T20:00Z 2026-10-22T04:00Z 3 +0.114 12.1 2026-10-22T00:00Z 0
-POUI22 2026-10-23T20:00Z 2026-10-24T00:00Z 2 +0.2609 27.8 2026-10-23T20:00Z 0
-POUI22 2026-10-26T00:00Z 2026-10-26T04:00Z 2 +0.3215 34.2 2026-10-26T04:00Z 0
-POUI22 2026-10-26T16:00Z 2026-10-26T16:00Z 1 +0.09302 9.9 2026-10-26T16:00Z 0
-POUI22 2026-10-29T20:00Z 2026-10-30T00:00Z 2 +0.511 54.4 2026-10-29T20:00Z 0
-POUI24 2026-10-26T20:00Z 2026-10-26T20:00Z 1 +0.2066 21.8 2026-10-26T20:00Z 0
-POUI24 2026-10-27T04:00Z 2026-10-27T04:00Z 1 -0.04816 -5.1 2026-10-27T04:00Z 0
-POUI24 2026-10-29T08:00Z 2026-10-29T08:00Z 1 +0.08821 9.3 2026-10-29T08:00Z 0
-POUH21 2026-10-26T00:00Z 2026-10-26T04:00Z 2 -0.03588 -6.1 2026-10-26T00:00Z 0
-POUH21 2026-10-29T08:00Z 2026-10-29T08:00Z 1 +0.04628 7.9 2026-10-29T08:00Z 0
-
-== corr_y: level, noise, largest jump from one measurement to the next ==
-sensor n level noise jump (noises) between
-COLH20 92 0.1286 0.00817 -0.06091 -7.5 2026-10-19T08:00Z and 2026-10-19T12:00Z
-COLI20 92 0.02538 0.00962 +0.04766 5.0 2026-10-29T08:00Z and 2026-10-29T12:00Z
-COLI21 92 0.06171 0.0118 +0.08119 6.9 2026-10-29T08:00Z and 2026-10-29T12:00Z
-COLJ19 92 0.02882 0.0112 +0.06114 5.5 2026-10-30T16:00Z and 2026-10-30T20:00Z
-POUI19 92 -0.1173 0.00767 -0.04744 -6.2 2026-10-29T08:00Z and 2026-10-29T12:00Z
-POUI20 92 -0.01327 0.00834 -0.04015 -4.8 2026-10-21T04:00Z and 2026-10-21T08:00Z
-COLI24 69 -0.1456 0.00982 +0.06328 6.4 2026-10-29T16:00Z and 2026-10-30T04:00Z
-COLI22 87 0.03629 0.00742 +0.1536 20.7 2026-10-23T04:00Z and 2026-10-23T08:00Z
-COLH20''' 88 -0.008465 0.00883 -0.2612 -29.6 2026-10-29T20:00Z and 2026-10-30T00:00Z
-POUI22 78 -0.09938 0.016 -1.289 -80.5 2026-10-26T16:00Z and 2026-10-27T08:00Z
-POUI24 86 -0.02697 0.0121 +0.07923 6.6 2026-10-26T20:00Z and 2026-10-27T00:00Z
-POUH21 92 -0.01284 0.00734 -0.02311 -3.1 2026-10-26T12:00Z and 2026-10-26T16:00Z
-
-corr_y: ranges more than 5 noises from the level (merge 720 min)
-sensor start end measurements extreme (noises) at rejected
-COLH20 2026-10-16T20:00Z 2026-10-18T16:00Z 10 -0.06145 -7.5 2026-10-16T20:00Z 0
-COLH20 2026-10-24T00:00Z 2026-10-24T04:00Z 2 +0.0456 5.6 2026-10-24T00:00Z 0
-COLH20 2026-10-26T08:00Z 2026-10-26T08:00Z 1 +0.0602 7.4 2026-10-26T08:00Z 0
-COLH20 2026-10-28T04:00Z 2026-10-28T08:00Z 2 +0.04793 5.9 2026-10-28T08:00Z 0
-COLH20 2026-10-28T20:00Z 2026-10-29T08:00Z 4 +0.09137 11.2 2026-10-29T04:00Z 0
-COLH20 2026-10-30T00:00Z 2026-10-30T08:00Z 3 +0.1027 12.6 2026-10-30T04:00Z 0
-COLI20 2026-10-16T20:00Z 2026-10-18T20:00Z 13 -0.08666 -9.0 2026-10-18T16:00Z 0
-COLI20 2026-10-19T20:00Z 2026-10-19T20:00Z 1 -0.05631 -5.9 2026-10-19T20:00Z 0
-COLI21 2026-10-16T20:00Z 2026-10-18T00:00Z 6 -0.08605 -7.3 2026-10-17T00:00Z 0
-COLI21 2026-10-19T04:00Z 2026-10-19T08:00Z 2 -0.07861 -6.6 2026-10-19T08:00Z 0
-COLI21 2026-10-29T16:00Z 2026-10-29T16:00Z 1 +0.07142 6.0 2026-10-29T16:00Z 0
-COLI21 2026-10-30T08:00Z 2026-10-30T12:00Z 2 +0.07422 6.3 2026-10-30T12:00Z 0
-COLI21 2026-10-31T08:00Z 2026-11-01T00:00Z 5 +0.07178 6.1 2026-10-31T12:00Z 0
-COLJ19 2026-10-16T20:00Z 2026-10-17T12:00Z 5 -0.06884 -6.2 2026-10-17T08:00Z 0
-COLJ19 2026-10-18T16:00Z 2026-10-18T16:00Z 1 -0.05929 -5.3 2026-10-18T16:00Z 0
-POUI19 2026-10-29T04:00Z 2026-10-29T08:00Z 2 +0.04117 5.4 2026-10-29T08:00Z 0
-COLI24 2026-10-31T16:00Z 2026-10-31T16:00Z 1 -0.056 -5.7 2026-10-31T16:00Z 0
-COLI22 2026-10-21T20:00Z 2026-10-22T04:00Z 3 -0.07929 -10.7 2026-10-21T20:00Z 0
-COLI22 2026-10-22T20:00Z 2026-10-23T04:00Z 3 -0.1584 -21.3 2026-10-23T04:00Z 0
-COLI22 2026-10-29T20:00Z 2026-10-30T00:00Z 2 -0.06485 -8.7 2026-10-29T20:00Z 0
-COLH20'''2026-10-30T00:00Z 2026-10-30T00:00Z 1 -0.2293 -26.0 2026-10-30T00:00Z 0
-COLH20'''2026-10-31T12:00Z 2026-10-31T12:00Z 1 +0.04929 5.6 2026-10-31T12:00Z 0
-POUI22 2026-10-21T20:00Z 2026-10-22T04:00Z 3 +0.1516 9.5 2026-10-21T20:00Z 0
-POUI22 2026-10-23T20:00Z 2026-10-24T00:00Z 2 +0.1791 11.2 2026-10-23T20:00Z 0
-POUI22 2026-10-26T00:00Z 2026-10-26T04:00Z 2 -0.579 -36.2 2026-10-26T00:00Z 0
-POUI22 2026-10-26T16:00Z 2026-10-26T16:00Z 1 +1.236 77.2 2026-10-26T16:00Z 0
-POUI22 2026-10-29T20:00Z 2026-10-30T00:00Z 2 -0.2719 -17.0 2026-10-29T20:00Z 0
-POUI24 2026-10-25T04:00Z 2026-10-25T04:00Z 1 +0.0607 5.0 2026-10-25T04:00Z 0
-POUI24 2026-10-29T00:00Z 2026-10-29T00:00Z 1 -0.06331 -5.2 2026-10-29T00:00Z 0
diff --git a/auto/analyses/long-labels/BREITHORN/work/ranges_all_2.txt b/auto/analyses/long-labels/BREITHORN/work/ranges_all_2.txt
deleted file mode 100644
index f339860..0000000
--- a/auto/analyses/long-labels/BREITHORN/work/ranges_all_2.txt
+++ /dev/null
@@ -1,91 +0,0 @@
-
-== corr_x: level, noise, largest jump from one measurement to the next ==
-sensor n level noise jump (noises) between
-COLH20 62 0.05263 0.00816 +0.07961 9.8 2026-10-04T16:00Z and 2026-10-04T20:00Z
-COLI20 62 0.002981 0.00751 +0.06947 9.3 2026-10-04T16:00Z and 2026-10-04T20:00Z
-COLI21 62 0.02725 0.0141 +0.06925 4.9 2026-10-04T16:00Z and 2026-10-04T20:00Z
-COLJ19 62 0.1228 0.00616 +0.06809 11.1 2026-10-04T16:00Z and 2026-10-04T20:00Z
-POUI19 62 0.209 0.0075 +0.07604 10.1 2026-10-04T16:00Z and 2026-10-04T20:00Z
-POUI20 62 0.05464 0.00692 +0.0734 10.6 2026-10-04T16:00Z and 2026-10-04T20:00Z
-COLI24 52 0.004593 0.00934 +0.07898 8.5 2026-10-04T16:00Z and 2026-10-04T20:00Z
-COLI22 54 -0.002826 0.00782 +0.09883 12.6 2026-10-04T16:00Z and 2026-10-04T20:00Z
-COLH20''' 51 0.02156 0.00486 +0.03378 7.0 2026-10-10T04:00Z and 2026-10-10T08:00Z
-POUI22 44 -0.03399 0.00738 +0.2778 37.6 2026-10-13T00:00Z and 2026-10-13T04:00Z
-POUI24 60 0.04776 0.00882 +0.2178 24.7 2026-10-13T00:00Z and 2026-10-13T04:00Z
-POUH21 62 0.01067 0.00676 +0.07469 11.1 2026-10-04T16:00Z and 2026-10-04T20:00Z
-
-corr_x: ranges more than 5 noises from the level (merge 720 min)
-sensor start end measurements extreme (noises) at rejected
-COLH20 2026-10-04T16:00Z 2026-10-04T16:00Z 1 -0.1006 -12.3 2026-10-04T16:00Z 0
-COLI20 2026-10-04T16:00Z 2026-10-04T16:00Z 1 -0.06945 -9.2 2026-10-04T16:00Z 0
-COLI20 2026-10-07T12:00Z 2026-10-07T12:00Z 1 +0.04192 5.6 2026-10-07T12:00Z 0
-COLI21 2026-10-04T16:00Z 2026-10-04T16:00Z 1 -0.07563 -5.3 2026-10-04T16:00Z 0
-COLJ19 2026-10-03T00:00Z 2026-10-03T20:00Z 6 -0.04729 -7.7 2026-10-03T00:00Z 0
-COLJ19 2026-10-04T12:00Z 2026-10-05T00:00Z 3 -0.0854 -13.9 2026-10-04T16:00Z 0
-COLJ19 2026-10-11T00:00Z 2026-10-11T00:00Z 1 +0.03129 5.1 2026-10-11T00:00Z 0
-COLJ19 2026-10-11T12:00Z 2026-10-13T04:00Z 11 +0.04724 7.7 2026-10-13T00:00Z 0
-POUI19 2026-10-03T00:00Z 2026-10-06T04:00Z 18 -0.1387 -18.5 2026-10-04T16:00Z 0
-POUI19 2026-10-07T00:00Z 2026-10-07T00:00Z 1 -0.0397 -5.3 2026-10-07T00:00Z 0
-POUI19 2026-10-09T12:00Z 2026-10-09T12:00Z 1 +0.04354 5.8 2026-10-09T12:00Z 0
-POUI19 2026-10-10T20:00Z 2026-10-13T04:00Z 14 +0.08356 11.1 2026-10-12T12:00Z 0
-POUI20 2026-10-04T16:00Z 2026-10-04T16:00Z 1 -0.08818 -12.7 2026-10-04T16:00Z 0
-COLI24 2026-10-04T16:00Z 2026-10-04T16:00Z 1 -0.06115 -6.5 2026-10-04T16:00Z 0
-COLI22 2026-10-04T16:00Z 2026-10-04T16:00Z 1 -0.08362 -10.7 2026-10-04T16:00Z 0
-COLI22 2026-10-07T12:00Z 2026-10-07T12:00Z 1 +0.05743 7.3 2026-10-07T12:00Z 0
-COLI22 2026-10-13T04:00Z 2026-10-13T04:00Z 1 -0.04617 -5.9 2026-10-13T04:00Z 0
-COLH20'''2026-10-07T12:00Z 2026-10-07T12:00Z 1 +0.02826 5.8 2026-10-07T12:00Z 0
-COLH20'''2026-10-10T04:00Z 2026-10-10T04:00Z 1 -0.03797 -7.8 2026-10-10T04:00Z 0
-POUI22 2026-10-07T12:00Z 2026-10-07T20:00Z 2 +0.1903 25.8 2026-10-07T20:00Z 0
-POUI22 2026-10-13T04:00Z 2026-10-13T04:00Z 1 +0.2757 37.3 2026-10-13T04:00Z 0
-POUI24 2026-10-09T00:00Z 2026-10-09T04:00Z 2 +0.1253 14.2 2026-10-09T00:00Z 0
-POUI24 2026-10-13T04:00Z 2026-10-13T04:00Z 1 +0.2221 25.2 2026-10-13T04:00Z 0
-POUH21 2026-10-04T16:00Z 2026-10-04T16:00Z 1 -0.07381 -10.9 2026-10-04T16:00Z 0
-POUH21 2026-10-10T04:00Z 2026-10-10T04:00Z 1 -0.03465 -5.1 2026-10-10T04:00Z 0
-
-== corr_y: level, noise, largest jump from one measurement to the next ==
-sensor n level noise jump (noises) between
-COLH20 62 0.06168 0.0122 -0.1213 -10.0 2026-10-10T00:00Z and 2026-10-10T04:00Z
-COLI20 62 -0.04809 0.00954 +0.1165 12.2 2026-10-10T04:00Z and 2026-10-10T08:00Z
-COLI21 62 -0.02485 0.0112 +0.117 10.4 2026-10-10T04:00Z and 2026-10-10T08:00Z
-COLJ19 62 -0.03669 0.0124 -0.1162 -9.4 2026-10-04T12:00Z and 2026-10-04T16:00Z
-POUI19 62 -0.1216 0.0109 -0.1134 -10.4 2026-10-10T00:00Z and 2026-10-10T04:00Z
-POUI20 62 -0.05099 0.0101 +0.1135 11.2 2026-10-04T16:00Z and 2026-10-04T20:00Z
-COLI24 52 -0.09136 0.0134 +0.1254 9.4 2026-10-04T16:00Z and 2026-10-04T20:00Z
-COLI22 54 0.02148 0.0092 +0.2358 25.6 2026-10-04T16:00Z and 2026-10-04T20:00Z
-COLH20''' 51 -0.03286 0.00835 +0.1216 14.6 2026-10-10T04:00Z and 2026-10-10T08:00Z
-POUI22 44 -0.07427 0.0143 -0.3166 -22.2 2026-10-13T00:00Z and 2026-10-13T04:00Z
-POUI24 60 -0.009546 0.00718 -0.4317 -60.2 2026-10-08T00:00Z and 2026-10-08T04:00Z
-POUH21 62 -0.01986 0.00785 +0.1152 14.7 2026-10-04T16:00Z and 2026-10-04T20:00Z
-
-corr_y: ranges more than 5 noises from the level (merge 720 min)
-sensor start end measurements extreme (noises) at rejected
-COLH20 2026-10-04T16:00Z 2026-10-04T16:00Z 1 -0.1486 -12.2 2026-10-04T16:00Z 0
-COLH20 2026-10-10T04:00Z 2026-10-10T04:00Z 1 -0.1111 -9.1 2026-10-10T04:00Z 0
-COLI20 2026-10-04T16:00Z 2026-10-04T16:00Z 1 -0.1376 -14.4 2026-10-04T16:00Z 0
-COLI20 2026-10-07T12:00Z 2026-10-07T12:00Z 1 +0.05639 5.9 2026-10-07T12:00Z 0
-COLI20 2026-10-10T04:00Z 2026-10-10T04:00Z 1 -0.1026 -10.8 2026-10-10T04:00Z 0
-COLI21 2026-10-04T16:00Z 2026-10-04T16:00Z 1 -0.1243 -11.1 2026-10-04T16:00Z 0
-COLI21 2026-10-10T04:00Z 2026-10-10T04:00Z 1 -0.1022 -9.1 2026-10-10T04:00Z 0
-COLJ19 2026-10-04T16:00Z 2026-10-04T16:00Z 1 -0.1534 -12.4 2026-10-04T16:00Z 0
-COLJ19 2026-10-07T12:00Z 2026-10-07T12:00Z 1 +0.1097 8.9 2026-10-07T12:00Z 0
-COLJ19 2026-10-10T04:00Z 2026-10-10T04:00Z 1 -0.08489 -6.9 2026-10-10T04:00Z 0
-POUI19 2026-10-04T16:00Z 2026-10-04T16:00Z 1 -0.1186 -10.9 2026-10-04T16:00Z 0
-POUI19 2026-10-07T12:00Z 2026-10-07T12:00Z 1 +0.09486 8.7 2026-10-07T12:00Z 0
-POUI19 2026-10-10T04:00Z 2026-10-10T04:00Z 1 -0.0829 -7.6 2026-10-10T04:00Z 0
-POUI19 2026-10-12T08:00Z 2026-10-12T08:00Z 1 -0.05751 -5.3 2026-10-12T08:00Z 0
-POUI20 2026-10-04T16:00Z 2026-10-04T16:00Z 1 -0.124 -12.3 2026-10-04T16:00Z 0
-POUI20 2026-10-10T04:00Z 2026-10-10T04:00Z 1 -0.1043 -10.3 2026-10-10T04:00Z 0
-COLI24 2026-10-04T16:00Z 2026-10-04T16:00Z 1 -0.09925 -7.4 2026-10-04T16:00Z 0
-COLI22 2026-10-04T16:00Z 2026-10-04T16:00Z 1 -0.2303 -25.0 2026-10-04T16:00Z 0
-COLI22 2026-10-13T04:00Z 2026-10-13T04:00Z 1 -0.163 -17.7 2026-10-13T04:00Z 0
-COLH20'''2026-10-10T04:00Z 2026-10-10T04:00Z 1 -0.114 -13.6 2026-10-10T04:00Z 0
-POUI22 2026-10-05T04:00Z 2026-10-05T04:00Z 1 +0.07261 5.1 2026-10-05T04:00Z 0
-POUI22 2026-10-06T04:00Z 2026-10-06T04:00Z 1 +0.0773 5.4 2026-10-06T04:00Z 0
-POUI22 2026-10-07T20:00Z 2026-10-07T20:00Z 1 +0.2734 19.1 2026-10-07T20:00Z 0
-POUI22 2026-10-13T04:00Z 2026-10-13T04:00Z 1 -0.3533 -24.7 2026-10-13T04:00Z 0
-POUI24 2026-10-07T12:00Z 2026-10-07T12:00Z 1 +0.04867 6.8 2026-10-07T12:00Z 0
-POUI24 2026-10-08T00:00Z 2026-10-08T00:00Z 1 +0.4185 58.3 2026-10-08T00:00Z 0
-POUI24 2026-10-09T00:00Z 2026-10-09T04:00Z 2 +0.3558 49.6 2026-10-09T04:00Z 0
-POUI24 2026-10-12T04:00Z 2026-10-12T04:00Z 1 -0.05764 -8.0 2026-10-12T04:00Z 0
-POUH21 2026-10-04T16:00Z 2026-10-04T16:00Z 1 -0.1116 -14.2 2026-10-04T16:00Z 0
-POUH21 2026-10-10T04:00Z 2026-10-10T04:00Z 1 -0.1128 -14.4 2026-10-10T04:00Z 0
diff --git a/auto/analyses/long-labels/BREITHORN/work/session b/auto/analyses/long-labels/BREITHORN/work/session
deleted file mode 100644
index 9d54b88..0000000
--- a/auto/analyses/long-labels/BREITHORN/work/session
+++ /dev/null
@@ -1 +0,0 @@
-b1dece15-7ed2-440e-993c-de42f2e6a4bf
\ No newline at end of file
diff --git a/auto/analyses/long-labels/CLARIDEN/input.jsonl b/auto/analyses/long-labels/CLARIDEN/input.jsonl
deleted file mode 100644
index 2267560..0000000
--- a/auto/analyses/long-labels/CLARIDEN/input.jsonl
+++ /dev/null
@@ -1,2 +0,0 @@
-{"id": "CLARIDEN-1", "start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The target P-300-B is rejected at every measurement of the batch: its recognition error stays almost at 1, its corrected curve is missing over the whole month. This has lasted since 29 September in the late afternoon, the time when the recognition error of other targets, including its neighbor P-301-B, also changes level all at once: a station setting changed that day. On the thumbnails (the 1st, the 15th and the 31st), the prism spot is sharp and bright, but next to the position where the system looks for it: the target seems badly configured or badly positioned, not hidden. Curve to ignore; correct the position of the target in the configuration or check the prism.", "review": "2026-11-17"}
-{"id": "CLARIDEN-14", "start": "2026-10-06T22:00Z", "end": "2026-10-11T06:00Z", "family": "Displacement", "description": "Slow drift of several targets over four days, made of small steps, then stabilization: D-303-B rises vertically, D-303-C and D-304-C rise vertically, D-301-C rises horizontally, D-306-B goes down horizontally. No camera movement, ordinary recognition error, nothing on the images; the position in the image of D-301-C and D-303-B moves slightly away from that of the other targets, in the direction of their curves. The camera housing temperature stays almost constant over these days: no link with it. Slow return from the 11th to the 19th, labeled separately. Cause not established, in a tunnel under construction: a movement of these targets is not excluded. To be checked against the other measurements of the site; monitor this row.", "review": "2026-11-17"}
diff --git a/auto/analyses/long-labels/CLARIDEN/labels.jsonl b/auto/analyses/long-labels/CLARIDEN/labels.jsonl
deleted file mode 100644
index 7e43a8a..0000000
--- a/auto/analyses/long-labels/CLARIDEN/labels.jsonl
+++ /dev/null
@@ -1,2 +0,0 @@
-{"id": "CLARIDEN-1", "start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "The target P-300-B is rejected at every measurement of the batch: its recognition error stays almost at 1, its corrected curve is missing over the whole month. This has lasted since 29 September in the late afternoon, the time when the recognition error of other targets, including its neighbor P-301-B, also changes level all at once: a station setting changed that day. On the thumbnails (the 1st, the 15th and the 31st), the prism spot is sharp and bright, but next to the position where the system looks for it: the target seems badly configured or badly positioned, not hidden. Curve to ignore; correct the position of the target in the configuration or check the prism.", "review": "2026-11-17"}
-{"id": "CLARIDEN-14", "start": "2026-10-06T22:00Z", "end": "2026-10-11T06:00Z", "family": "Displacement", "description": "Slow drift of several targets over four days, made of small steps, then stabilization: D-303-B rises vertically, D-303-C and D-304-C rise vertically, D-301-C rises horizontally, D-306-B goes down horizontally. The camera moves: its tilt drifts slowly over the same days, with a small step on the 8th, and these targets follow it closely in the directions of their curves; the compensation does not absorb this tilt equally on every target. Ordinary recognition error, nothing on the images. The camera housing temperature stays almost constant over these days: no link with it. Slow return from the 11th to the 19th, labeled separately. Deduced from the curves and the camera pose: mostly a remainder of the camera tilt, not established as a movement of the structure; the camera is to be monitored, and these targets checked against the other measurements of the site."}
diff --git a/auto/analyses/long-labels/CLARIDEN/work/inv_month.txt b/auto/analyses/long-labels/CLARIDEN/work/inv_month.txt
deleted file mode 100644
index b1c39be..0000000
--- a/auto/analyses/long-labels/CLARIDEN/work/inv_month.txt
+++ /dev/null
@@ -1,157 +0,0 @@
-Folder: data/CLARIDEN
-"advanced" exports (source of the measurements): 79
- 79 files, first and last (--files for the full list):
- data/CLARIDEN/displacement/CLARIDEN_advanced_20260901.csv
- data/CLARIDEN/displacement/L9 BCN_advanced_20260917_20260920.csv
-Duplicate readings (same sensor, same instant in an export already read, in name order; the tools keep the one of the last file):
- L9 BCN_advanced_20260917_20260920.csv: 12528 of 12528 already read, 0 of them with different values
-Hourly exports: 1 (not read by the tools: hourly averages, local time without a zone; see tools/DATA.md)
- data/CLARIDEN/displacement/L9 BCN_20260918_to_20260920_1hour.csv
-Camera movements (pose at each registration): 78
- 78 files, first and last (--files for the full list):
- data/CLARIDEN/camera/CLARIDEN_camera_20260901.csv
- data/CLARIDEN/camera/CLARIDEN_camera_20261117.csv
-Other files: 1561
- 1561 files, first and last (--files for the full list):
- data/CLARIDEN/metrics/CLARIDEN_BatteryPercent_2026_09_01_00_00 to 2026_09_01_23_00.csv
- data/CLARIDEN/targets.csv
-
-What the data contain, over the window (per column, the rows that have a value; "empty": none):
- "advanced" export: 118030 rows; x 118030, y 118030, error_value 118030, error_threshold 118030, relative_x 118030, relative_y 118030, corr_x 113949 (28 sensors of 29), corr_y 113949 (28 sensors of 29), reproj_err 20349 (5 sensors of 29), inlier 20349 (5 sensors of 29), sigma0 118030, pattern_type 118030, peak empty, flux empty, sharpness empty, fwhm empty, dominance empty, snr empty, corr_x_mm 85463 (21 sensors of 29), corr_y_mm 85463 (21 sensors of 29)
- Export image quality (peak to snr): empty
- Camera pose (camera/): 4070 rows; median_pan 4070, min_pan 4070, max_pan 4070, median_tilt 4070, min_tilt 4070, max_tilt 4070, median_scale 4070, min_scale 4070, max_scale 4070, median_rotation 4070, min_rotation 4070, max_rotation 4070, median_sigma0 4070, min_sigma0 4070, max_sigma0 4070
- System metrics (metrics/, one CSV per metric and per day; read by metrics.py): 20: BatteryPercent (32 d), BatteryState (32 d), BusCurrent (32 d), BusVoltage (32 d), BusVoltageOCV (32 d), BusVoltageTrend (32 d), Power (32 d), ShuntVoltage (32 d), data_storage_free_gb (32 d), data_storage_total_gb (32 d), data_storage_used_gb (32 d), last_sync (32 d), link (32 d), schedule_skipped_conflict (32 d), schedule_success (32 d), sensor_A0_deg_c (32 d), sensor_CPU_deg_c (32 d), sensor_GPU_deg_c (32 d), sensor_PLL_deg_c (32 d), sensor_thermal_deg_c (32 d)
- Camera images: 685
- Others: targets.csv (1)
-Images: 3167, from 2026-09-01T00:00Z to 2026-11-17T16:00Z
- gap between two images over the window, per run of equal gaps (within 5 min):
- 2026-10-01T00:00Z → 2026-10-03T17:00Z: 66 images, every 60 min
- 2026-10-03T17:00Z → 2026-10-05T10:30Z: one gap of 2490 min
- 2026-10-05T10:30Z → 2026-10-05T11:00Z: one gap of 30 min
- 2026-10-05T11:00Z → 2026-10-15T22:00Z: 252 images, every 60 min
- 2026-10-15T22:00Z → 2026-10-16T10:30Z: one gap of 750 min
- 2026-10-16T10:30Z → 2026-10-16T11:00Z: one gap of 30 min
- 2026-10-16T11:00Z → 2026-10-18T13:00Z: 51 images, every 60 min
- 2026-10-18T13:00Z → 2026-10-18T23:30Z: one gap of 630 min
- 2026-10-18T23:30Z → 2026-10-19T00:00Z: one gap of 30 min
- 2026-10-19T00:00Z → 2026-10-19T09:00Z: 10 images, every 60 min
- 2026-10-19T09:00Z → 2026-10-19T10:10Z: one gap of 70 min
- 2026-10-19T10:10Z → 2026-10-19T11:00Z: one gap of 50 min
- 2026-10-19T11:00Z → 2026-10-19T20:00Z: 10 images, every 60 min
- 2026-10-19T20:00Z → 2026-10-19T21:10Z: one gap of 70 min
- 2026-10-19T21:10Z → 2026-10-19T22:00Z: one gap of 50 min
- 2026-10-19T22:00Z → 2026-10-26T14:00Z: 161 images, every 60 min
- 2026-10-26T14:00Z → 2026-10-26T15:10Z: one gap of 70 min
- 2026-10-26T15:10Z → 2026-10-26T16:00Z: one gap of 50 min
- 2026-10-26T16:00Z → 2026-10-29T14:00Z: 71 images, every 60 min
- 2026-10-29T14:00Z → 2026-10-29T15:10Z: one gap of 70 min
- 2026-10-29T15:10Z → 2026-10-29T16:00Z: one gap of 50 min
- 2026-10-29T16:00Z → 2026-11-01T00:00Z: 57 images, every 60 min
-
-Measurement period: 2026-09-01T00:00Z → 2026-11-17T08:30Z, 10137 instants
-Cadence (median step): 10 min
-Missing measurements (instants absent from the cadence): 1003
- between 2026-09-01T01:00Z and 2026-09-01T01:30Z: 2
- between 2026-09-02T01:00Z and 2026-09-02T01:20Z: 1
- between 2026-09-03T01:40Z and 2026-09-03T02:00Z: 1
- between 2026-09-04T01:30Z and 2026-09-04T01:50Z: 1
- between 2026-09-05T02:00Z and 2026-09-05T02:30Z: 2
- between 2026-09-13T04:00Z and 2026-09-15T14:13Z: 348
- between 2026-09-29T09:30Z and 2026-09-29T10:00Z: 2
- between 2026-09-29T10:10Z and 2026-09-29T11:10Z: 5
- between 2026-10-03T07:40Z and 2026-10-03T08:00Z: 1
- between 2026-10-03T17:40Z and 2026-10-05T10:30Z: 244
- between 2026-10-15T22:50Z and 2026-10-16T10:30Z: 69
- between 2026-10-16T14:20Z and 2026-10-16T14:40Z: 1
- between 2026-10-18T13:50Z and 2026-10-18T23:30Z: 57
- between 2026-10-19T09:00Z and 2026-10-19T09:30Z: 2
- between 2026-10-19T09:30Z and 2026-10-19T09:50Z: 1
- between 2026-10-19T09:50Z and 2026-10-19T10:10Z: 1
- between 2026-10-19T20:40Z and 2026-10-19T21:10Z: 2
- between 2026-10-19T21:10Z and 2026-10-19T21:30Z: 1
- between 2026-10-20T06:10Z and 2026-10-20T06:30Z: 1
- between 2026-10-20T20:40Z and 2026-10-20T21:40Z: 5
- between 2026-10-26T14:30Z and 2026-10-26T15:10Z: 3
- between 2026-10-27T09:00Z and 2026-10-27T09:30Z: 2
- between 2026-10-29T14:50Z and 2026-10-29T15:10Z: 1
- between 2026-10-30T17:00Z and 2026-10-30T17:50Z: 4
- between 2026-11-03T08:50Z and 2026-11-03T09:20Z: 2
- between 2026-11-10T08:20Z and 2026-11-10T08:40Z: 1
- between 2026-11-11T00:30Z and 2026-11-12T10:40Z: 204
- between 2026-11-16T17:20Z and 2026-11-17T00:00Z: 39
-
-Sensors: 29 (5 references, 24 targets)
- distance (m) and mm/px: targets.csv (data.load_targets); "-": not in it, or not filled in (distance 1000 mm); "?": its lines (n) disagree, no corr_x_mm / corr_y_mm
-sensor type pattern threshold measurements rejected distance mm/px
-D-302-C reference global_ref 0.7 10137 12 - -
-PR-291 reference global_ref 0.7 10137 1 - -
-PR-293 reference global_ref 0.7 10137 1 - -
-PR-295 reference global_ref 0.7 10137 7 - -
-PR-296 reference global_ref 0.7 10137 3 - -
-D-300-A target target 0.7 10137 2 13.51 5.072
-D-300-C target target 0.7 10137 10 13.81 5.418
-D-301-A target target 0.7 10137 1 12.07 4.452
-D-301-C target target 0.7 10137 10 12.2 4.736
-D-302-B target target 0.7 10137 2 9.409 3.752
-D-302_A target target 0.7 10137 2 10.42 3.772
-D-303-A target target 0.7 10137 1 8.67 3.074
-D-303-B target target 0.7 10137 28 7.83 3.132
-D-303-C target target 0.7 10137 10 9.33 3.485
-D-304-A target target 0.7 10137 2 7.3 2.536
-D-304-B target target 0.7 10137 0 6.4 2.557
-D-304-C target target 0.7 10137 5 8.1 2.989
-D-306-B target target 0.7 10137 0 2.14 0.821
-P-298-A target target 0.7 10137 1 16.87 6.444
-P-298-B target target 0.7 10137 2 16.75 6.592
-P-298-C target target 0.7 10137 4 17.36 6.927
-P-299-A target target 0.7 10137 1 15.37 5.810
-P-299-B target target 0.7 10137 2 15.06 6.000
-P-299-C target target 0.7 10137 3 15.54 6.192
-P-300-B target target 0.7 10137 6371 13.12 5.215
-P-301-B target target 0.7 10137 2 11.23 4.488
-PR-283 target ref 0.7 10137 1970 - -
-PR-284 target ref 0.7 10137 38 - -
-PR_BG target target 0.7 10137 40 30 11.963
-
-Camera pose over the whole period: 9902 registrations, 2026-09-01T00:00Z → 2026-11-16T00:20Z
-Measurement instants without a pose (no registration): 235 of 10137
-
-Window 2026-10-01T00:00Z → 2026-11-01T00:00Z: 4070 instants present
-Steps absent for all sensors, between two present instants (cadence of 10 min):
- between 2026-10-03T07:40Z and 2026-10-03T08:00Z: 1
- between 2026-10-03T17:40Z and 2026-10-05T10:30Z: 244
- between 2026-10-15T22:50Z and 2026-10-16T10:30Z: 69
- between 2026-10-16T14:20Z and 2026-10-16T14:40Z: 1
- between 2026-10-18T13:50Z and 2026-10-18T23:30Z: 57
- between 2026-10-19T09:00Z and 2026-10-19T09:30Z: 2
- between 2026-10-19T09:30Z and 2026-10-19T09:50Z: 1
- between 2026-10-19T09:50Z and 2026-10-19T10:10Z: 1
- between 2026-10-19T20:40Z and 2026-10-19T21:10Z: 2
- between 2026-10-19T21:10Z and 2026-10-19T21:30Z: 1
- between 2026-10-20T06:10Z and 2026-10-20T06:30Z: 1
- between 2026-10-20T20:40Z and 2026-10-20T21:40Z: 5
- between 2026-10-26T14:30Z and 2026-10-26T15:10Z: 3
- between 2026-10-27T09:00Z and 2026-10-27T09:30Z: 2
- between 2026-10-29T14:50Z and 2026-10-29T15:10Z: 1
- between 2026-10-30T17:00Z and 2026-10-30T17:50Z: 4
-Present instants where sensors have no measurement:
- (none)
-Rejected measurements in the window, per sensor (start → end of each run of consecutive steps, count):
- D-302-C (1): 2026-10-05T12:20Z
- PR-295 (4): 2026-10-31T19:50Z; 2026-10-31T22:30Z → 22:40Z (2); 2026-10-31T23:10Z
- D-300-C (1): 2026-10-05T12:20Z
- D-301-C (1): 2026-10-05T12:20Z
- D-303-C (1): 2026-10-05T12:20Z
- D-304-C (2): 2026-10-05T10:30Z; 2026-10-05T12:20Z
- P-298-C (1): 2026-10-05T12:20Z
- P-299-C (1): 2026-10-05T12:20Z
- P-300-B (4070): 2026-10-01T00:00Z → 2026-10-03T07:40Z (335); 2026-10-03T08:00Z → 17:40Z (59); 2026-10-05T10:30Z → 2026-10-15T22:50Z (1515); 2026-10-16T10:30Z → 14:20Z (24); 2026-10-16T14:40Z → 2026-10-18T13:50Z (284); 2026-10-18T23:30Z → 2026-10-19T09:00Z (58); 2026-10-19T09:30Z; 2026-10-19T09:50Z; 2026-10-19T10:10Z → 20:40Z (64); 2026-10-19T21:10Z; 2026-10-19T21:30Z → 2026-10-20T06:10Z (53); 2026-10-20T06:30Z → 20:40Z (86); 2026-10-20T21:40Z → 2026-10-26T14:30Z (822); 2026-10-26T15:10Z → 2026-10-27T09:00Z (108); 2026-10-27T09:30Z → 2026-10-29T14:50Z (321); 2026-10-29T15:10Z → 2026-10-30T17:00Z (156); 2026-10-30T17:50Z → 2026-11-01T00:00Z (182)
-Retained references by the compensation (inlier = 1) out of 5, number of instants: 5: 4065, 4: 5
-Instants where references are not retained (runs of consecutive steps with the same references out; r = rejected, empty = inlier empty, otherwise the inlier value):
- 2026-10-05T12:20Z: 4 retained; out: D-302-C (r)
- 2026-10-31T19:50Z: 4 retained; out: PR-295 (r)
- 2026-10-31T22:30Z → 22:40Z (2): 4 retained; out: PR-295 (r)
- 2026-10-31T23:10Z: 4 retained; out: PR-295 (r)
-
-Camera pose in the window: 4070 registrations, 2026-10-01T00:00Z → 2026-11-01T00:00Z
-Measurement instants without a pose (no registration): 0 of 4070
diff --git a/auto/analyses/long-labels/CLARIDEN/work/log.jsonl b/auto/analyses/long-labels/CLARIDEN/work/log.jsonl
deleted file mode 100644
index a3ddd3b..0000000
--- a/auto/analyses/long-labels/CLARIDEN/work/log.jsonl
+++ /dev/null
@@ -1,68 +0,0 @@
-{"type":"system","subtype":"init","cwd":"/home/maxime/aimsight-app","session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","tools":["Read","Bash","Write"],"mcp_servers":[],"model":"claude-opus-5-5","permissionMode":"acceptEdits","slash_commands":["deep-research","design","slides","design-sync","dataviz","artifact-diagramming","whiteboard","artifact-capabilities","update-config","verify","debug","code-review","simplify","batch","fewer-permission-prompts","doctor","loop","schedule","claude-api","workflow-authoring","run","run-skill-generator","plugin-authoring","advisor","agents","auto-mode-setup","autocompact","clear","color","compact","config","output-style","context","effort","fast","focus","heapdump","init","mcp","import","model","__remote-workflow","workflow-launch-exec","reload-plugins","reload-skills","rename","ultrareview","security-review","usage-credits","extra-usage","usage","insights","recap","skill-doctor","goal","design-consent","design-revoke","list-agents","team-onboarding"],"terminal_slash_commands":["doctor","color","focus","reload-plugins"],"apiKeySource":"none","claude_code_version":"2.1.326","output_style":"default","agents":["agents:analyst","agents:support","agents:upgrader","agents:validator","claude","claude-code-guide","Explore","general-purpose","Plan","statusline-setup"],"skills":["deep-research","design","slides","design-sync","dataviz","artifact-diagramming","whiteboard","artifact-capabilities","update-config","verify","debug","code-review","simplify","batch","fewer-permission-prompts","doctor","loop","schedule","claude-api","workflow-authoring","run","run-skill-generator","plugin-authoring"],"plugins":[{"name":"agents","path":"/home/maxime/aimsight-app/agents","source":"agents@inline"},{"name":"cc-plugin-agents-md","path":"builtin","source":"cc-plugin-agents-md@builtin"},{"name":"cc-plugin-telemetry","path":"builtin","source":"cc-plugin-telemetry@builtin"},{"name":"cc-plugin-privacy","path":"builtin","source":"cc-plugin-privacy@builtin"},{"name":"cc-plugin-plugin-authoring","path":"builtin","source":"cc-plugin-plugin-authoring@builtin"}],"capabilities":["interrupt_receipt_v1","interrupt_cancel_queued_v1","interrupt_send_now_v1","interrupt_requeue_taken_v1","msg_lifecycle_v1","request_marker_lists_v1","ask_user_question_unanswered_v1","lifecycle_wakeup_source_v1","sdk_mcp_tools_list_changed","sdk_mcp_manifests","mcp_read_resource_v1","mcp_tool_ui_meta_v1","ui_surface_v1","mcp_call_result_not_for_model_v1","mcp_call_check_permissions_v1","voice_call_talk_line_v1","withdrawn_files_note_v2","ui_pane_widget_v1","reload_plugins_refuse_if_busy_v1","silent_resend_files_v1"],"analytics_disabled":false,"product_feedback_disabled":false,"uuid":"06fa90b6-0752-476e-b1a4-d9d65769778b","memory_paths":{"auto":"/home/maxime/.claude/projects/-home-maxime-aimsight-app/memory/"},"scratchpad_path":"/tmp/claude-1000/-home-maxime-aimsight-app/1d552933-66a2-4aee-a79d-97df96c159c7/scratchpad","original_cwd":"/home/maxime/aimsight-app","additional_directories":["/home/maxime/aimsight-data/data","/home/maxime/aimsight-labeling","/home/maxime/aimsight-tools"],"messaging_socket_path":"/run/user/1000/cc-socks/41402.sock","fast_mode_state":"off","fast_mode_disabled_reason":"sdk_opt_in_required","per_turn_effort_active":true,"ultrathink_available":false,"ultrathink_typed_raises":false,"view_mode":"default","startup_timing":{"entrypoint":"claude-desktop","warm_spare_claimed":false,"plugin_full_loads":0,"user_context_builds":1,"sdk_mcp_dial_runs":0,"sdk_mcp_servers_dialed":0,"flag_fetch_kick":"not_eligible","flag_fetch_kick_judged_at_ms":661,"hooks_init_source":"startup","phases":{"node_boot_ms":375,"settings_load_ms":0,"pre_action_mdm_keychain_ms":8,"pre_action_init_ms":263,"pre_action_client_data_url_ms":0,"pre_action_migrations_ms":0,"pre_action_managed_settings_ms":4,"pre_action_ms":300,"permission_context_ms":225,"setup_import_ms":0,"setup_uds_dir_ms":25,"setup_uds_listen_ms":17,"setup_uds_publish_ms":9,"setup_uds_messaging_ms":55,"setup_hooks_snapshot_ms":0,"setup_file_watcher_ms":0,"setup_release_notes_ms":47,"setup_ms":107,"skills_load_ms":192,"tools_commands_load_ms":77,"model_catalog_decision_ms":70,"mcp_config_wait_ms":17,"mcp_config_load_ms":1,"mcp_connect_ms":3,"hooks_init_ms":24,"print_import_ms":43,"grove_check_ms":27,"headless_prologue_ms":32,"initial_messages_load_ms":0,"headless_post_load_ms":7,"input_ready_ms":1417,"first_message_read_ms":1430,"sdk_mcp_update_ms":2,"first_message_handle_ms":3,"first_message_handle_cpu_ms":3,"first_message_handle_loop_lag_ms":0,"mcp_prewait_ms":1,"qe_system_prompt_ms":325,"prompt_submit_hooks_ms":7,"qe_plugin_skills_load_ms":6,"init_emit_ms":6},"time_origin_ms":1794947454986.5928,"phase_start_ms":{"node_boot_ms":0,"settings_load_ms":383,"pre_action_mdm_keychain_ms":390,"pre_action_init_ms":397,"pre_action_client_data_url_ms":660,"pre_action_migrations_ms":665,"pre_action_managed_settings_ms":665,"pre_action_ms":390,"permission_context_ms":702,"setup_import_ms":930,"setup_uds_dir_ms":939,"setup_uds_listen_ms":964,"setup_uds_publish_ms":981,"setup_uds_messaging_ms":936,"setup_hooks_snapshot_ms":993,"setup_file_watcher_ms":993,"setup_release_notes_ms":995,"setup_ms":939,"skills_load_ms":937,"tools_commands_load_ms":1082,"model_catalog_decision_ms":1161,"mcp_config_wait_ms":1251,"mcp_connect_ms":1299,"hooks_init_ms":1281,"print_import_ms":1305,"grove_check_ms":1350,"headless_prologue_ms":1348,"initial_messages_load_ms":1381,"headless_post_load_ms":1381,"input_ready_ms":0,"first_message_read_ms":0,"sdk_mcp_update_ms":1430,"first_message_handle_ms":1430,"mcp_prewait_ms":1435,"qe_system_prompt_ms":1454,"prompt_submit_hooks_ms":1939,"qe_plugin_skills_load_ms":2109,"init_emit_ms":2115}}}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98mXhrAHiahNd72b1pD","type":"message","role":"assistant","content":[{"type":"thinking","thinking":"","signature":"CAQSrAUKEAgTGAI4AUIIdGhpbmtpbmcSDF7UXKF434BSvk14gxoMDhqjJ/dNWbF9Rh9eIjAHmlYp0NhSs3+w3ZVz8ILcP+rgMqHeRaEjTi5olntZhPUi2UfOkqm9FqBMOdvtBwsqyQTEDNzxiFHA118nELJRi4/XUBGPxsJWhK0ZYILNKwufzmkmEZavNJFHO1iAxKM5IGRNl3gkd8oJn7FxoZX+9/wvvSmLtfTGbdHJ/em6BtwtQkWV3qEYCpZvpwYVyTdKBmEwfYmLWNGRV7NzULZcy8A6OfRhjJ0S4zVcdu0gaDnu4gOppvMYWa2Lp7D3DfbdgqDOEIa6q2SRi3KFQumxhcKMGGgcxWH6jpqt635XqB7ulrbjmvDDSDG//PLhOkL/ySMvuMVJplDktzaoWfjE6sEBbes5r3zDIt8jecq31dEonYXfSgEHW3lIp65mEqDfLiOnS1rF4gVRMfhuRooURE0bjnE1j0toUx6V8W0izqw+blkvWOfEr0GmzX0UPxgz4OfiX59Cl5wPYMNW5FAIkxGa+cs2i7iWMxD+YEL+aR8OYhZ6ciIodoN4t9g3Slkz+IGWAwIJKCq5ObHP1VT5PLW3nGJwTmJfrJBMP/et+ox08z0CaF2z68/4ETOXNQFk0ENw6kH7i8Owth4SnfDM7Ocu9ZRnPSDez48XHDG7o9voAMpvEOsWJotNCP8gK/cIRZWBvz5YJpwZfpumiePGkV+H6UMcT/Z0OjYyV5QKw+U3MMmmvyZzyDSNWxGX2yfd2QxkSd3WbqzhUclU07EII5swDc9picMskN3UGwIuqEiDgQ4TQ/2+FsTIVhITqFh0Gb4sHOJmT17Qld7h1xP7AiiCoCpga53feu7VuwoNZO6kX9N9JNZZhSptn2S1bTJ0GjwrrzgssxoqsisYAQ=="}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":3961,"cache_read_input_tokens":5976,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":3961},"output_tokens":8,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"3424f02d-6e06-4b21-ab2e-5d1123b58358","timestamp":"2026-11-17T20:30:59.630Z","request_id":"req_011Ch98mXUTNbi9eBQvvKv2d","thinking_duration_ms":455,"thinking_display":"updates"}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98mXhrAHiahNd72b1pD","type":"message","role":"assistant","content":[{"type":"tool_use","id":"toolu_01G87Y9yk96h4a9yLckcjgSX","name":"Bash","input":{"command":"cd /home/maxime/aimsight-app; cat labeling/auto/analyses/long-labels/CLARIDEN/input.jsonl; ls labeling/auto/analyses/long-labels/CLARIDEN/; ls labeling/auto/analyses/ | grep CLARIDEN; ls labeling/auto/analyses/long-labels/","description":"Show input labels and analyses folders"},"caller":{"type":"direct"}}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":3961,"cache_read_input_tokens":5976,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":3961},"output_tokens":8,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"41706511-e0db-4f8f-845f-f6007080d863","timestamp":"2026-11-17T20:31:00.642Z","request_id":"req_011Ch98mXUTNbi9eBQvvKv2d","wire_tool_inputs":{"toolu_01G87Y9yk96h4a9yLckcjgSX":{"command":"cd /home/maxime/aimsight-app; cat labeling/auto/analyses/long-labels/CLARIDEN/input.jsonl; ls labeling/auto/analyses/long-labels/CLARIDEN/; ls labeling/auto/analyses/ | grep CLARIDEN; ls labeling/auto/analyses/long-labels/","description":"Show input labels and analyses folders"}}}
-{"type":"rate_limit_event","rate_limit_info":{"status":"allowed_warning","resetsAt":1794954600,"rateLimitType":"five_hour","utilization":0.99,"overageStatus":"rejected","overageDisabledReason":"org_level_disabled","isUsingOverage":false,"surpassedThreshold":0.9,"unifiedWindows":{"five_hour":{"utilization":0.99,"resetsAt":1794954600,"status":"allowed_warning","surpassedThreshold":0.9},"seven_day":{"utilization":0.72,"resetsAt":1795302000,"status":"allowed"}},"overageEnabled":false},"uuid":"14254929-bb3d-4089-89fb-00d7bf2ecb06","session_id":"1d552933-66a2-4aee-a79d-97df96c159c7"}
-{"type":"system","subtype":"task_summary","detail":"Showing input labels and analyses folders","uuid":"c11c195f-ab07-4b7b-92be-576c75b476c9","session_id":"1d552933-66a2-4aee-a79d-97df96c159c7"}
-{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_01G87Y9yk96h4a9yLckcjgSX","type":"tool_result","content":"{\"id\": \"CLARIDEN-1\", \"start\": \"2026-10-01T00:00Z\", \"end\": \"2026-11-01T00:00Z\", \"family\": \"Target issue\", \"description\": \"The target P-300-B is rejected at every measurement of the batch: its recognition error stays almost at 1, its corrected curve is missing over the whole month. This has lasted since 29 September in the late afternoon, the time when the recognition error of other targets, including its neighbor P-301-B, also changes level all at once: a station setting changed that day. On the thumbnails (the 1st, the 15th and the 31st), the prism spot is sharp and bright, but next to the position where the system looks for it: the target seems badly configured or badly positioned, not hidden. Curve to ignore; correct the position of the target in the configuration or check the prism.\", \"review\": \"2026-11-17\"}\n{\"id\": \"CLARIDEN-14\", \"start\": \"2026-10-06T22:00Z\", \"end\": \"2026-10-11T06:00Z\", \"family\": \"Displacement\", \"description\": \"Slow drift of several targets over four days, made of small steps, then stabilization: D-303-B rises vertically, D-303-C and D-304-C rise vertically, D-301-C rises horizontally, D-306-B goes down horizontally. No camera movement, ordinary recognition error, nothing on the images; the position in the image of D-301-C and D-303-B moves slightly away from that of the other targets, in the direction of their curves. The camera housing temperature stays almost constant over these days: no link with it. Slow return from the 11th to the 19th, labeled separately. Cause not established, in a tunnel under construction: a movement of these targets is not excluded. To be checked against the other measurements of the site; monitor this row.\", \"review\": \"2026-11-17\"}\ninput.jsonl\nwork\nCLARIDEN_2026-10-01T0000_2026-10-11T0000\nCLARIDEN_2026-10-11T0000_2026-10-20T0400\nCLARIDEN_2026-10-20T0400_2026-11-01T0010\nBREITHORN\nCLARIDEN\nFLORIDA\nJUNGFRAU\nMICHIGAN","is_error":false}]},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"cf298e45-f71f-49c3-ba9d-c049f0b37b41","timestamp":"2026-11-17T20:31:01.017Z","tool_use_result":{"stdout":"{\"id\": \"CLARIDEN-1\", \"start\": \"2026-10-01T00:00Z\", \"end\": \"2026-11-01T00:00Z\", \"family\": \"Target issue\", \"description\": \"The target P-300-B is rejected at every measurement of the batch: its recognition error stays almost at 1, its corrected curve is missing over the whole month. This has lasted since 29 September in the late afternoon, the time when the recognition error of other targets, including its neighbor P-301-B, also changes level all at once: a station setting changed that day. On the thumbnails (the 1st, the 15th and the 31st), the prism spot is sharp and bright, but next to the position where the system looks for it: the target seems badly configured or badly positioned, not hidden. Curve to ignore; correct the position of the target in the configuration or check the prism.\", \"review\": \"2026-11-17\"}\n{\"id\": \"CLARIDEN-14\", \"start\": \"2026-10-06T22:00Z\", \"end\": \"2026-10-11T06:00Z\", \"family\": \"Displacement\", \"description\": \"Slow drift of several targets over four days, made of small steps, then stabilization: D-303-B rises vertically, D-303-C and D-304-C rise vertically, D-301-C rises horizontally, D-306-B goes down horizontally. No camera movement, ordinary recognition error, nothing on the images; the position in the image of D-301-C and D-303-B moves slightly away from that of the other targets, in the direction of their curves. The camera housing temperature stays almost constant over these days: no link with it. Slow return from the 11th to the 19th, labeled separately. Cause not established, in a tunnel under construction: a movement of these targets is not excluded. To be checked against the other measurements of the site; monitor this row.\", \"review\": \"2026-11-17\"}\ninput.jsonl\nwork\nCLARIDEN_2026-10-01T0000_2026-10-11T0000\nCLARIDEN_2026-10-11T0000_2026-10-20T0400\nCLARIDEN_2026-10-20T0400_2026-11-01T0010\nBREITHORN\nCLARIDEN\nFLORIDA\nJUNGFRAU\nMICHIGAN","stderr":"","interrupted":false,"isImage":false,"noOutputExpected":false},"tool_result_meta":[{"id":"toolu_01G87Y9yk96h4a9yLckcjgSX","permission_decision":{"decision":"accept","source":"config","reason_type":"rule"}}]}
-{"type":"system","subtype":"thinking_tokens","estimated_tokens":50,"estimated_tokens_delta":50,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"daee8c01-da1c-462a-bf09-211ea86bf955"}
-{"type":"system","subtype":"thinking_tokens","estimated_tokens":193,"estimated_tokens_delta":143,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"31117430-ce85-46bf-861d-e6e55adc45c2"}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98moTdZgsQZv4PqMtfT","type":"message","role":"assistant","content":[{"type":"thinking","thinking":"","signature":"CAQS+gUKEAgTGAI4AUIIdGhpbmtpbmcSDMKGJO/OUAcJuz1jHxoMlwzJ0VrU8tlosz1+IjAP8UUicLENnCxq8JOzXmv8tuhVw2vLB2rvNOe1b0qFDDDr+R7pNqMFvh8LpI9xm8UqlwXk9rcXpKOrxhDeGDn/I6Z3eAFOWGDvKEnTHnJWSOUPMU5zq+8N+5dX3k0v7yRHcqDRWRUYB583qXt4Ef6uQNMlDi8C8Q3y25TXw2jYRUJVtyuS092LlLied8eWTmoHqnLii5cGdTnTqFvD9+/1bPCsZJW1qN2iYclqgqdS7RtwdQJjDD+vZ+nzL8DtB2ADuY3qS90Lv2++k4YAsHYaZf/5EtqRfAyW9q++cg6uYlWibAaojf1SDPuoV6gHru6ryOc06E0URl4G0VnYMKW5hMHMpAHSWtxpOimz/7ovSOM7zil5kAOoq6ooqK01jDwKRtocQcLXEfUzXv643HUdT6HROY053I6hjrQdJy+MKvZSZP7hDLHGzSCl92NVB7HtaTWIz6JTay4UkgCFcjrHXo6jjzx260UX75ntY5ZNaEUycP/nM/Xl5Cs2b0i3e1sUWR3QhpeESb+tSpYmvr0n4FgE3fgd96QNf75t+NSa+KmTNQEamZbvOC144kF8JaGJ3N8zyu6aOMqGDGxqfRRM1G5VVQXnec3RnmGJTVqipAkkcLB7u+zWhx9plbvQsnrz2MXJk/Qtb0Xm5zsRrzeCmboQwcTsm+uLt6SrzcKCsA+YoSWbQlxNKaF8li++MjME0uJ/0ywbn+j7X1iVwJ9V5pCZg7He+GbHPGsPcNUygXBa5mKnpQjM0EVaAxiFQdAGN93G6j+by/M8fwfVPrf/dcycJXkBTScP3t5E61bhL0EUYYCRIZz7WKq49MaM8Jq4IVaIB5TEh70nmDRmYRSvZ8PE1TUTAWFQ0PyZgB/lQtkI4jPrGic9CmOBGU43+u/WtQNG+PU9oUK5FvDuJ2YK0ahqaTRkhhOOvgny2Or6HrxPQkTisSDgeGwYAQ=="}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":939,"cache_read_input_tokens":9937,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":939},"output_tokens":3,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"2e2a49df-43e2-471f-ba21-4270bb68a17c","timestamp":"2026-11-17T20:31:02.972Z","request_id":"req_011Ch98moDkGJKA69qAZeTZ8","thinking_duration_ms":872,"thinking_display":"updates"}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98moTdZgsQZv4PqMtfT","type":"message","role":"assistant","content":[{"type":"tool_use","id":"toolu_01STcmocxb7BYFY12YeY5Fxv","name":"Bash","input":{"command":"cd /home/maxime/aimsight-app; ls labeling/auto/analyses/long-labels/*/; ls labeling/auto/analyses/long-labels/CLARIDEN/work; wc -l tools/GUIDE.md tools/DATA.md labeling/families.md labeling/labeling-rules.md labeling/reading-rules.md labeling/stations.md","description":"List long-label folders and doc sizes"},"caller":{"type":"direct"}}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":939,"cache_read_input_tokens":9937,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":939},"output_tokens":3,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"0c3d885c-1fc7-43f0-a8fe-ec6315eea9aa","timestamp":"2026-11-17T20:31:04.222Z","request_id":"req_011Ch98moDkGJKA69qAZeTZ8","wire_tool_inputs":{"toolu_01STcmocxb7BYFY12YeY5Fxv":{"command":"cd /home/maxime/aimsight-app; ls labeling/auto/analyses/long-labels/*/; ls labeling/auto/analyses/long-labels/CLARIDEN/work; wc -l tools/GUIDE.md tools/DATA.md labeling/families.md labeling/labeling-rules.md labeling/reading-rules.md labeling/stations.md","description":"List long-label folders and doc sizes"}}}
-{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_01STcmocxb7BYFY12YeY5Fxv","type":"tool_result","content":"labeling/auto/analyses/long-labels/BREITHORN/:\ninput.jsonl\nwork\n\nlabeling/auto/analyses/long-labels/CLARIDEN/:\ninput.jsonl\nwork\n\nlabeling/auto/analyses/long-labels/FLORIDA/:\ninput.jsonl\nwork\n\nlabeling/auto/analyses/long-labels/JUNGFRAU/:\ninput.jsonl\nwork\n\nlabeling/auto/analyses/long-labels/MICHIGAN/:\ninput.jsonl\nwork\nlog.jsonl\nsession\n 240 tools/GUIDE.md\n 74 tools/DATA.md\n 101 labeling/families.md\n 107 labeling/labeling-rules.md\n 100 labeling/reading-rules.md\n 17 labeling/stations.md\n 639 total","is_error":false}]},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"fe675169-40bd-4a2a-a20b-d837931327e4","timestamp":"2026-11-17T20:31:04.307Z","tool_use_result":{"stdout":"labeling/auto/analyses/long-labels/BREITHORN/:\ninput.jsonl\nwork\n\nlabeling/auto/analyses/long-labels/CLARIDEN/:\ninput.jsonl\nwork\n\nlabeling/auto/analyses/long-labels/FLORIDA/:\ninput.jsonl\nwork\n\nlabeling/auto/analyses/long-labels/JUNGFRAU/:\ninput.jsonl\nwork\n\nlabeling/auto/analyses/long-labels/MICHIGAN/:\ninput.jsonl\nwork\nlog.jsonl\nsession\n 240 tools/GUIDE.md\n 74 tools/DATA.md\n 101 labeling/families.md\n 107 labeling/labeling-rules.md\n 100 labeling/reading-rules.md\n 17 labeling/stations.md\n 639 total","stderr":"","interrupted":false,"isImage":false,"noOutputExpected":false},"tool_result_meta":[{"id":"toolu_01STcmocxb7BYFY12YeY5Fxv","permission_decision":{"decision":"accept","source":"config","reason_type":"rule"}}]}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98n3RGUXfNwFvkqgaDt","type":"message","role":"assistant","content":[{"type":"tool_use","id":"toolu_01Sm7cbD7iXk22kFLnocZkiF","name":"Read","input":{"file_path":"/home/maxime/aimsight-app/tools/GUIDE.md"},"caller":{"type":"direct"}}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":524,"cache_read_input_tokens":10876,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":524},"output_tokens":16,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"af3e9f52-0e7b-4748-ba7e-f37c45eff36b","timestamp":"2026-11-17T20:31:05.993Z","request_id":"req_011Ch98n3C8UGUW8Q6NtwAzR","wire_tool_inputs":{"toolu_01Sm7cbD7iXk22kFLnocZkiF":{"file_path":"/home/maxime/aimsight-app/tools/GUIDE.md"}}}
-{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_01Sm7cbD7iXk22kFLnocZkiF","type":"tool_result","content":"1\t# Reading the data\n2\t\n3\tThe guide to the reading harness: followed by the analyst; improved by the upgrader (agents repository), run by Optimizer's `optimize` skill, the only one that writes here.\n4\t\n5\tA camera tracks targets (reflectors) fixed on a structure; its own movement is compensated thanks to reference targets, assumed fixed. This movement, the **camera pose** (`pan`, `tilt`, `rotation` in degrees, `scale`, `sigma0` of the registration, in `camera/`), is read before the sensors: it explains a large part of what moves on the curves (D-073). This guide says how to read a station's data: what the curves and the images show, moment by moment. It does not say what they mean: family, known event, hypothesis and verdict are the business of whoever calls you.\n6\t\n7\t## Read first\n8\t\n9\t- `tools/DATA.md`: the files of a station and the meaning of each column, the image quality metrics, the camera images (**first**);\n10\t- `labeling/reading-rules.md`: what the data mean (the measurement chain, gaps, reading rules, false friends).\n11\t\n12\t## The tools\n13\t\n14\tRun them from the root of the calling repository, where `tools/`, `data/` and `labeling/` are links. They return values, never verdicts: you judge. `--out `: where whoever calls you stores your figures; they give it to you. The method (below) says in which order to run them; each section says what a tool returns and how to read it.\n15\t\n16\t| Tool | The question it answers |\n17\t|---|---|\n18\t| [`inventory.py`](#inventory) | What is there, what is missing: files, contents of each source, images, poses, cadence, sensors, rejections |\n19\t| [`summary.py`](#summary) | The usual level of each sensor, then one column by time step |\n20\t| [`plot.py`](#plot) | The series of chosen sensors and columns, as a PNG |\n21\t| [`overview.py`](#overview) | All the sensors together, against the camera pose: common movement, single sensors, residuals, rigid movement |\n22\t| [`ranges.py`](#ranges) | Dated ranges where each sensor leaves its level, at the native step |\n23\t| [`days.py`](#days) | What comes back from one day to the next: night levels, days superimposed by hour, bounds of each day |\n24\t| [`metrics.py`](#metrics) | The system metrics (temperature, voltage…) against the targets and the pose |\n25\t| [`stations.py`](#stations) | Several stations on the same timeline |\n26\t| [`quality.py`](#quality) | The six image quality metrics against a calm reference; labels; degraded instants no label covers |\n27\t| [`thumbnails.py`](#thumbnails) | Full-resolution thumbnails of the camera images, around sensors or of a zone |\n28\t| [`gif.py`](#gif) | A GIF of the camera images over a range, for a reply to the customer |\n29\t| [`ls … \\| grep`](#whole-image) | The whole camera image at a time |\n30\t\n31\t### inventory\n32\t\n33\t```\n34\tpython3 tools/scripts/inventory.py [--start T] [--end T] [--files]\n35\t```\n36\t\n37\tNames and counts, never values. Over the **whole period**:\n38\t- files by type: beyond 5 per type, the count, the first and the last (`--files`: the full list, only to look for a specific file);\n39\t- **what each source contains** over the window: the columns of the export, of the pose, of `quality/` and of `weather/` (the MeteoSwiss weather, hourly; a station without a Swiss position has none), with the number of rows that have a value (\"empty\" otherwise; an export column that not all sensors carry says how many carry it); the names of the system metrics of `metrics/`; the images and the difference images. The \"Export image quality (peak to snr)\" line says whether the six quality metrics are filled (then `quality.py`) or empty;\n40\t- images by runs of equal gaps between two images (within 5 min, over the window if given): one line per change of gap, a hole is dated by its two images;\n41\t- camera poses (count, period, measurement instants without registration), period, cadence, missing measurements, sensors (reference or target, error threshold, rejected measurements, distance from the camera and mm per px of `targets.csv`). When `pattern_type` is empty, a sensor is a reference if it carries `reproj_err` or `inlier` (the \"pattern_type empty for N sensors\" line says so);\n42\t- \"Duplicate readings\": an export (often named after the customer's project) whose readings are already in the others; with 0 different values, it changes nothing to the reading, otherwise the tools keep the one of the last file in name order.\n43\t\n44\tWith `--start`/`--end` (on a batch: those of the batch), a section for the window: the missing steps, dated (for all the sensors, or which ones are missing); by sensor, the rejected measurements, dated (runs of consecutive steps; rejected: `error_value` above the sensor's threshold, **references included**); then the **number of references retained by the compensation** (`inlier` = 1) at each instant and the dated runs where some are not, which ones and why (`r` rejected, `0` discarded by the compensation, `empty`; another mark is the value of `inlier`, e.g. `-1`). When `inlier` is empty over the window, the retained references are read from the filled `reproj_err` (the title says so).\n45\t\n46\tA run that ends the same day writes only the time of its end. Over a month, the output with `--start`/`--end` exceeds what a call displays: read each section through `grep` (`| grep -A40 '^Retained references'`, `| grep '^ PR04 '`).\n47\t\n48\t### summary\n49\t\n50\t```\n51\tpython3 tools/scripts/summary.py [--column C] [--stat median|min|max] [--step 1h] [--level period|window] [--sensors A,B] [--start T] [--end T] [--instants T1,T2] [--mark]\n52\t```\n53\t\n54\tThe usual level of each sensor (median, MAD, min, max) over the whole period, or over the `--start`/`--end` window with `--level window` (for a batch: a level change within the batch is not compared with weeks of other measurements); then a table by time step, the sensor header repeated every 24 lines.\n55\t- Columns: `error_value`, `corr_x`, `corr_y`, `relative_x`, `relative_y`, `x`, `y`, `sigma0`, `reproj_err`, `corr_x_mm`, `corr_y_mm` (the `corr` in mm, empty without a sure factor: `tools/DATA.md`, \"The targets\"), and the six image quality metrics `peak`, `flux`, `sharpness`, `fwhm`, `dominance`, `snr` (raw values; against a calm reference, `quality.py`).\n56\t- `--mark`: `*` after the value when a measurement of the step is rejected (`x`, `y`, `error_value` of a rejected measurement stay filled), `o` when one has inlier = 0.\n57\t- `--instants T1,T2`: only the steps that contain these instants (the values of all the sensors at a few chosen times).\n58\t- With `--step` equal to the cadence, `--level window --mark`: the per-instant, per-sensor table of one column, one column per run.\n59\t\n60\t### plot\n61\t\n62\t```\n63\t.venv/bin/python tools/scripts/plot.py [--sensors A,B] [--columns C1,C2] [--start T] [--end T] [--zone T1/T2 ...] [--out D]\n64\t```\n65\t\n66\tA PNG of the series, each `--zone` greyed; prints its path. Columns: those of `summary.py`, quality metrics included (raw values).\n67\t\n68\t### overview\n69\t\n70\t```\n71\t.venv/bin/python tools/scripts/overview.py [--columns x,y,sigma0] [--column error_value] [--step 15min] [--k 5] [--min 5] [--residuals corr_x,corr_y,error_value|no] [--outside T1/T2] [--others] [--rigid BASE [--without A,B] [--follow A,B]] [--table T1/T2|no] [--sensors A,B] [--start T] [--end T] [--out D]\n72\t```\n73\t\n74\tAll the sensors together, each against its median and its MAD over the window.\n75\t\n76\tPNGs:\n77\t- **common**: at the top, if the folder has `camera/`, the **camera pose** (raw values, one point per registration, the line cut at measurement instants without registration); the median across sensors of `x`, `y`, `sigma0`, the dispersion across sensors as a grey band; on the `x`, `y` panels, also **each global reference separately** (one line each) and the **median of the targets alone** (black line); at each step, the number of sensors whose `--column` exceeds its median by more than `--k` MAD. Ticks every 1 to 12 h depending on the window, every n days beyond 20 days.\n78\t- **multiples**: a small chart per sensor, one scale each: a step of a single sensor shows there.\n79\t- **residuals-corr_x**, **-corr_y**, **-error_value** (`--residuals`; `no`: none of these PNGs nor their tables): a small chart per sensor of the column minus the sensor's own level (its median over the window; with `--outside T1/T2`, that of the rest of the window, outside the moment read), one scale each, zero dotted: a deviation of a few hundredths on `corr`, hidden in the parallel bands of `plot.py`, shows there.\n80\t- **residuals-…-others** (`--others`): each sensor minus its own median **and minus the median of the other sensors at the same instant**: what all share (the remainder of the compensation of a common movement) cancels, what is specific remains.\n81\t- **rigid** (`--rigid BASE`): at each measurement, the overall movement of the targets since the instant `BASE` (translation, rotation, scale, estimated by medians: a target that jumps alone does not pull it; `--without A,B` removes targets from it) and, for each sensor, the **residual** `dx`, `dy` (raw position minus its position at `BASE` carried by this movement, in px). Panels: `dx`, `dy` of each global reference against the median and the 10th-90th percentile of the targets, `|residual|` of the targets (median, 90th percentile), fitted rotation and scale, `reproj_err` of the references; a rejected reference is a cross (the scale is that of the accepted measurements, a far cross is out of frame).\n82\t\n83\tPrinted:\n84\t- the **common median table**, one line per `--step`: the time, the deviation from the window median of `x`, `y`, `sigma0`, then `x_targets`, `y_targets` (median of the targets alone), then the raw camera pose `cam_pan`, `cam_tilt`, `cam_rotation`, `cam_scale`, `cam_sigma0` (empty without registration); the minimum and the maximum of each column with their instant; then those of `x`, `y` of each global reference (`(rejected)` when the measurement is, with the reference's number of rejected measurements); the measurement instants without pose (dated runs); the instants where at least `--min` sensors exceed together, with their names (`--min 1`: also a single sensor that leaves its level, absent from the default list of 5 sensors);\n85\t- `--residuals`: per sensor, the level, the own noise (median of the differences between two measurements), the min/max deviation per step with their instant, in units and in noises;\n86\t- `--others`: per sensor, the slope and the correlation r of the residual on the common median of `x`, `y`, `sigma0`;\n87\t- `--rigid`: the table by step (`rot_deg`, `scale`, `tx`, `ty`, `tgt_med`, `tgt_max`, `dx`, `dy` of each reference and of each sensor of `--follow A,B`: the step-by-step sequence of a target) and, per sensor, min, max and value at the last instant of `dx`, `dy`. Rejected measurements enter neither the fit, nor the band of the targets, `tgt_med`, `tgt_max`, nor the columns of the table (over several days, parked cars or night rejections no longer drown the rest); the per-sensor summary gives them separately (`; N rejected: min …, max …`, and `(rejected)` after a last value that is rejected).\n88\t\n89\tThe tables by step (common median, `--rigid`) repeat their header every 24 lines; `--table T1/T2` prints them only between T1 and T2 (`no`: not at all), levels, min, max, PNGs and the rest remaining over the whole window: over a one-month batch, first `--table no`, then `--table` on the day of a moment (same levels, which a shorter `--start`/`--end` window would not give). The default step is 15 min, the cadence of the measurements: a one-hour step flattens a peak of one to four steps, dates to the hour and erases an agitation of `x`, `y`; do not widen it to read a batch.\n90\t\n91\tReading, in this order:\n92\t1. **The camera pose first** (top panels, `cam_` columns), dated at the native step: when it rotates (`pan`, `tilt`, `rotation`), changes scale, when its registration degrades (`sigma0`) or is absent (line cut, instants without pose). Each moment of the sensors is read against it: during a movement or a registration gap, or camera still.\n93\t2. **Who moves in the image.** The pose is computed from the global references: a change of pose (or a rise of `sigma0`) is a camera movement only if **the targets also move in the image** (on the `x`, `y` panels, the lines of the references against the black line of the targets alone; `x_targets`, `y_targets`). Only references move, targets still: these references moved, and the pose and the `corr` of all the targets are skewed without raw movement of the targets; say which references and by how much. References and targets together: the camera or the scene; then look whether the `corr` come back.\n94\t3. **Rotation or scale: `--rigid`.** Then the deviation from the median no longer says who moves alone (each sensor deviates according to its place in the image; the rigid residual does not). Before writing \"everything moves together\", rerun with `--rigid BASE`, `BASE` a calm instant before the first movement: a reference whose residual stays far from the 10th-90th percentile of the targets, or a `reproj_err` of the references that does not come back, means the compensation remains skewed by these references and the steps of `corr` partly come from it (say which, by how much, until when); a rising `|residual|` of the targets says they do not move as a block.\n95\t4. **Then `x`, `y`, `sigma0`, before `corr`**: the median of `x`, `y` (raw position, references included), the references one by one, the targets alone and `sigma0` say what moves in the image. Date the start, the end, the return of a movement, or a level that does not come back, on the printed table (time, value), not on the PNG axis. A dip of `corr` after a movement of the raw median is the remainder of the compensation, not a movement of these sensors. The multiples of `error_value` show a lasting step of a sensor, the count the instants where many rise together.\n96\t5. **The residuals, on every batch, without waiting for a suspicion**: a single sensor that rises or falls, a `corr` that drifts by a few hundredths, a step specific to one sensor under a common movement show there; the table says by how much (in noises) and when. On a target whose `corr` goes down under a strong common movement, `--others` separates a remainder of the compensation from a movement of its own: a dip that remains is not a remainder shared by all; a high slope with r close to ±1 on common `y` says it is proportional to the common movement (gain specific to the sensor); without r or slope, it is independent of the movement.\n97\t\n98\t### ranges\n99\t\n100\t```\n101\tpython3 tools/scripts/ranges.py [--columns error_value,corr_x,corr_y] [--k 5] [--merge 1h] [--min-measurements 1] [--outside T1/T2] [--rolling N|DURATION] [--instants N] [--sensors A,B] [--start T] [--end T]\n102\t```\n103\t\n104\tDates the start and the end of a sensor's moment without rerunning ten tables. By column and by sensor, at the measurements (native step, never averaged): level (median of the window), own noise, **largest jump** from one measurement to the next (value, in noises, the two instants; `(rejected: …)` when one end is); then the **ranges** where the sensor deviates from its level by more than `--k` noises: start, end, number of measurements, extreme (signed, in units and in noises) and its instant. Two ranges of the same sign less than `--merge` apart make one; rejected measurements do not cut a range; column `rejected`: how many of the range's measurements are (and `rejected extreme`). A range that touches the edge of the window is dated at the edge.\n105\t- `--outside T1/T2`: level and noise computed outside an episode that skews the window median (the sensor spends half the batch there). Rerun with it around a long episode to date its return to the level: do not conclude \"does not come back\" without having read it.\n106\t- `--min-measurements N`: only the ranges of at least N measurements (and how many out of the total). Over several days, the one-step ranges number in the hundreds and drown the long steps: first `--min-measurements 6`, then without.\n107\t- `--rolling N` (N measurements on each side) or `--rolling 1d` (the measurements within a duration): the level of each measurement is the median of its neighbours, without it; a long drift or a step follows this local level, only the deviations shorter than the window remain (the level column and the noise do not change; with `--outside`, only the noise is computed outside the episode).\n108\t- `--instants N`: at the end, the instants where at least N sensors are out of level on one of the columns, with each sensor and its signed deviation in noises (`cx` corr_x, `cy` corr_y, `ev` error_value), the sensors rejected at that instant (among `--sensors`: removing the always-rejected sensors lightens the list), and each reference: `error_value` (`r` if rejected) / inlier.\n109\t- When the batch has a long drift or several steps (the ranges number in the hundreds, or one half of the batch is \"out of level\"), rerun with `--rolling` (a few measurements, or a few hours to a day depending on the cadence) and `--instants 2`: the brief deviations under the drift come out alone, and the list per instant says which sensors deviate together, which are rejected and what the references do; a deviation of all the targets with the references at the same instant is read against the camera pose.\n110\t\n111\tA noise of `0` (and \"-\" in noises, no range): the values are constant to rounding (deviations below 1e-9), like the `corr` of the references when the compensation retains only two (see Conventions); the same in `overview.py --residuals` and `days.py`.\n112\t\n113\t### days\n114\t\n115\t```\n116\t.venv/bin/python tools/scripts/days.py [--columns corr_x,corr_y,error_value] [--night 20-3] [--k 5] [--days 2] [--step 15min] [--sensors A,B] [--bounds [--smoothing N] [--fraction F]] [--start T] [--end T] [--out D]\n117\t```\n118\t\n119\tWhat comes back from one day to the next, on accepted measurements only. A night: the hours `--night` H1-H2 UTC, straddling midnight, dated from the day it starts; choose hours where the day cycle (`error_value`, camera pose) has subsided (**byhour** figure).\n120\t\n121\t1. **Level of each night**, by sensor and by column: median, MAD, number of measurements, own noise; from one night to the next, the **step** (difference of the medians, in units and in noises) and **where it falls** (\"between A and B\": where the night measurements of the two nights split best between the two levels; B at the start of the following night: the cut falls by day). Read it for any sensor that has already made a step or for which `--outside` is not enough (several levels in the batch): a step of a few noises is dated by its \"between A and B\", a step of `error_value` and one of `corr` at the same instant are linked, a slow drift reads from one night to the next.\n122\t2. **Superimposed days**: PNG **byhour-**, a small chart per sensor, hour of the day on the x axis, one curve per day, each measurement minus the level of the last night started (night greyed, frame from the 1st to the 99th percentile, the title says how many measurements fall outside it). Table: per `--step` slot of the hour of the day, the sensors whose deviation exceeds `--k` noises on the same side at least `--days` days, with the number of days and the median of these deviations. What comes back every day at the same hour, on one or several sensors, groups there, even when it lasts one to three measurements: one moment per hour of the day (say which sensors, how many days out of how many, the amplitude, what the camera pose does at that hour), not one moment per day, nor nothing because each step is short.\n123\t3. **Bounds of each day** (`--bounds`), for what comes back every day and is labelled day by day (thermal cycle, warming and cooling), rather than fixing the same hours for all the days: for the median of the targets of each column (with `--sensors`, the median of these sensors; with one, its own) and for the camera pose (`pan`, `tilt`, `rotation`, `scale`, `sigma0`, if `camera/` exists), the deviation from the level of the night that precedes each day (a day goes from the end of one night to the end of the next). Per day: number of measurements, the first and the last; first and last instant beyond `--k` noises, with the measurement just before and just after, at the native step; signed max and min with their instant; the sequence of measurements beyond `--k` noises around the larger of the two; the following night minus the reference night. A day without measurement says so; a reference night that is not the previous one is named. Each day line starts with the short name of its series (`corr_x`, `pose_tilt`…): `| grep '^pose_tilt '` reads one, `| grep ' 12/10 '` one day. PNG **bounds**: the deviation over the batch, first → last exceedance light grey, sequence around the extreme dark grey, max and min marked.\n124\t - `--smoothing N`: the deviation of each measurement is the median of the N measurements of the day centred on it (noise and `--k` unchanged; PNG: smoothed in blue, raw in grey): an isolated point no longer cuts the sequence around the extreme nor makes a first or a last exceedance.\n125\t - `--fraction F`: the threshold of each day is F times its largest |deviation| (printed on its line, `threshold …`), instead of `--k` noises: when the noise at the native step is unrelated to the amplitude of the cycle (very noisy or very smooth pose).\n126\t - Reading: the sequence around the extreme dates the cycle, the max and the min a go and a return (morning and afternoon); \"before\" and \"after\" give the bounds at the native step (at a cadence of 1 h or 4 h, an event goes from the measurement before to the one after). First exceedance at the start of the day (\"before -\") and last at its end every day: the night is not calm; change `--night`, or `--sensors` the targets that carry the cycle. Camera drifting all night: a short night just before the morning (`--night 3-5`: the level of the rest that precedes the start). Noisy series or isolated points: `--smoothing 5`. Threshold in noises that does not bite (never exceeded, or exceeded all day): `--fraction 0.3`, then read the sequence around the extreme, not the first and the last exceedance. A \"1 measurements\" line is a peak, not a cycle.\n127\t\n128\t### metrics\n129\t\n130\t```\n131\t.venv/bin/python tools/scripts/metrics.py [--names A,B] [--step 1h] [--stat median|min|max] [--against temperature] [--smoothing 24h] [--metrics-only] [--start T] [--end T] [--out D]\n132\t```\n133\t\n134\tThe system metrics of `metrics/` (one value per hour), never the identifiers (`SIM_CCID`, `ip*`):\n135\t- the available metrics with their number of values over the window (\"empty\": none; all empty is an absent datum, not a stable temperature);\n136\t- a table per `--step`: `temperature` (median of the `sensor_*_deg_c` components, the one the detectors read), each metric of `--names` (default: the `*_deg_c` and `BusVoltage`), then, unless `--metrics-only`, `tgt_corr_x`, `tgt_corr_y` (median over the targets of `corr` minus each target's own level, accepted measurements) and the raw camera pose (`cam_pan` … `cam_sigma0`); an empty cell is skipped, a text metric (`link`, `BatteryState`, `last_sync`) is returned as it is. `--step 1d --stat min` (or `max`): the minimum or the maximum of each day;\n137\t- per column: filled steps, min and max with their instant; the correlation r and the slope of each column on `--against` (with `--smoothing 24h`, on its rolling mean, column `_smooth`: for a station where the temperature varies little and fast, indoors); the dated runs of steps without any metric;\n138\t- a PNG: temperatures on one panel (median in black), each other metric on its own, then `tgt_corr_x`, `tgt_corr_y` and the pose, line cut on a gap.\n139\t\n140\tAn r does not say a cause: say it as a value, with the window where it is computed.\n141\t\n142\t### stations\n143\t\n144\t```\n145\t.venv/bin/python tools/scripts/stations.py [...] [--columns temperature,cam_tilt,cam_rotation,cam_scale,tgt_corr_x,tgt_corr_y] [--step 1h] [--stat median|min|max] [--table T1/T2|no] [--start T] [--end T] [--out D]\n146\t```\n147\t\n148\t**Several stations on the same timeline** (neighbouring stations, same building). Columns: `temperature` (as in `metrics.py`), `cam_pan` … `cam_sigma0` (raw pose), `tgt_corr_x`, `tgt_corr_y` (as in `metrics.py`), `rej_targets`, `rej_refs` (number of rejected targets, of rejected references, the largest of the step).\n149\t- Prints per station the period, the cadence and the number of instants; the **gaps**: the runs of steps without measurement or without temperature, with the stations where they are missing (a gap common to several stations on a single line); the table by step (one `STATION:column` column each, tabs; `--table` as in `overview.py`); per column and per pair of stations, r of the values and r of the steps from one value to the next (a common movement shows on the steps, a common trend on the values), with n.\n150\t- PNG **stations**: a panel per column, a line per station (raw temperature, the rest minus its median), and a band per station of the steps without measurement.\n151\t- Take `--step` equal to the slowest cadence of the stations; over a month at `1h`, first `--table no`.\n152\t\n153\t### quality\n154\t\n155\t```\n156\tpython3 tools/scripts/quality.py [--calm T1/T2,T3/T4] [--common] [--table M] [--step 15min] [--threshold 0.5] [--sensors A,B] [--start T] [--end T]\n157\t... --labels F [--numbers 3,7] [--margin 60] [--edges]\n158\t... --labels F --outside [--min 1] [--except \"Thermal displacement\"]\n159\t.venv/bin/python tools/scripts/quality.py --figure [--metrics flux,snr,dominance] [--labels F] [--zone T1/T2 ...] [--out D]\n160\tpython3 tools/scripts/quality.py --self-test\n161\t```\n162\t\n163\tThe six **image quality metrics** (`peak`, `flux`, `sharpness`, `fwhm`, `dominance`, `snr`; definitions: `tools/DATA.md`), on the stations that have them (otherwise: \"No quality metrics\", and nothing else). Each measurement becomes a **ratio** to the **calm reference** of its sensor: the median of the metric over its measurements in the `--calm` windows, at the same UTC hour of the day (without `--calm`: the whole folder); 1 = like the reference, < 1 lower, > 1 higher; for `fwhm` and `dominance`, the rise says a degraded image; rejected measurements included.\n164\t- Without options: the folder's maximal `peak`, then per sensor (`r` = reference) the rejected measurements, `pk/max` (median peak over the window divided by this maximum: at 1, the spot touches the image ceiling, its `peak` no longer moves and its `sharpness` follows the exposure: read `flux`, `snr` instead), and for each metric the median ratio and the extreme with its instant; then the median of the targets and of the references.\n165\t- `--common`: per step, the median of the ratios of the targets / of the references for each metric (what affects the whole scene, visibility or turbulence; `--step 1d` shows on one screen on which days the reference holds).\n166\t- `--table M`: per step, the ratio of `M` of each sensor (`*`: a rejected measurement), their median and how many pass `--threshold` (below, or above 1/`--threshold` for `fwhm`, `dominance`): a target that goes out and comes back; on a moment, `--table flux --sensors …` says which targets are hidden (flux cut) or veiled, from which instant to which instant: write them by their name.\n167\t- `--labels F` (one JSON per line, `start`, `end`, `family`): per numbered label, the median ratio of the targets and of the references over the hour before, the range and the hour after (`tgt 0.96|0.26|0.79`, `--margin` minutes), then the sensors **affected** over the range (flux or snr below `--threshold`, or dominance above 1/`--threshold`), with their worst flux, from lowest to highest. `--edges`: per instant of the widened range, the number of affected sensors and the median of the targets of flux, snr, dominance (`<` within the range), to date the first and the last degraded instant.\n168\t- `--outside`: the runs of instants that no label covers (outside `--except` families) where at least `--min` sensors are affected, with the sensors and their worst flux: candidates for forgotten labels, to check on `corr_x`, `corr_y`.\n169\t- `--figure` (instead of the tables): PNG **quality-common** (a panel per metric, log scale: median of the targets in black, of the references in red, grey band from the 10th to the 90th percentile of the targets: a disturbance of the whole scene moves the median, an occultation of a few targets only the bottom of the band) and a PNG **quality-** per `--metrics` (a small chart per sensor, references in red); `--labels` greys each label in one colour per family, `--zone` ranges.\n170\t\n171\tReading: the metrics say **why** a measurement degrades, where `error_value` says only that it degrades; they prove a cause and name the affected targets. What they showed on LENZSPITZE (to be confirmed on each station): `flux` cut (close to 0) on a group of targets, the others intact, for one to a few measurements: these targets are hidden (the list is read on the flux each time, not on the usual list; a hidden target can stay under its error threshold, and its point is wrong); `flux` down over the whole scene, stronger on the distant targets: reduced visibility; `sharpness` down and `dominance` up, `flux` whole: the image shakes (turbulence); nothing moves: neither the image nor the view, to be looked for in the movement. A whole flux refutes an occultation. `fwhm`, truncated to the disc, moves little; on a spot at the ceiling (`pk/max` at 1), it goes down when the spot darkens.\n172\t\n173\t**The calm reference decides everything**: take `--calm` on calm hours of the **same image regime** as the range read. When the lighting or the exposure changes (after a gap, an intervention), a reference on the other side skews the ratios by a factor of two or three: `--common --step 1d` over the batch shows this change (medians of the targets and of the references far from 1 for whole days, then at 1); then take a reference on each side and read each side with its own. Calm days are often days of thermal cycle: a reading of the thermal against them is circular.\n174\t\n175\t### thumbnails\n176\t\n177\t```\n178\t.venv/bin/python tools/scripts/thumbnails.py --sensors A,B --times T1,T2 [--radius 100] [--contrast [MIN,MAX]] [--fixed] [--zone X,Y,W,H] [--out D]\n179\t```\n180\t\n181\tA sheet of full-resolution thumbnails: one row per sensor, one column per time, centred on the sensor's raw position (`x`, `y`) at each time. Look at it with Read: a whole image read by Read is reduced, a small reflector becomes illegible in it.\n182\t- The centre of the frame is written under each thumbnail: when `x`, `y` jump, the frame moves by as much, and a spot that enters the frame seems to appear; `--fixed` keeps for each sensor the frame of the first time and marks with a red cross the `x`, `y` of each time.\n183\t- Unretouched pixels: the brightness compares from one thumbnail to the next; prints for each thumbnail the background (median), the 99th percentile and the peak (grey levels 0 to 255). Without an image at the requested time, takes the nearest and prints the gap (the actual time is in the title).\n184\t- A faint or deformed spot is invisible as it is: `--contrast MIN,MAX` puts all the thumbnails in grey with the same stretch (without value: from the 1st percentile to the sheet's maximum, crushed by a saturated pixel; then choose MIN,MAX from the printed background and peak, e.g. `10,40`); `--radius 30` to `50` magnifies. Compare the shape and the peak before, during and after an episode, at the same hour of the day.\n185\t- A frame that the image edge cuts is flagged (\"frame cut by the image edge (W × H px)\"): on some stations, `x`, `y` are not pixels (values close to 0) and the frame falls in the corner; then look at the scene through `--zone`.\n186\t- `--zone X,Y,W,H` (pixels of the original image: top left corner, width, height, as in `gif.py`): the same zone at each time, side by side (up to 4 per row), same stretch with `--contrast`; `--sensors` becomes optional, those given are marked with a cross and their name. For the scene around the targets (foreground object, headlights, lighting), prefer it to a large `--radius`.\n187\t- Each thumbnail is rendered pixel for pixel up to 1000 px a side, but Read reduces a wide PNG: with a large `--radius` or a large `--zone`, three or four times per sheet.\n188\t\n189\t### gif\n190\t\n191\t```\n192\t.venv/bin/python tools/scripts/gif.py --start T --end T [--width 720] [--duration 700] [--max 150] [--zone X,Y,W,H] [--out D]\n193\t```\n194\t\n195\tA GIF of the camera images between `--start` and `--end` inclusive, cropped to `--zone` if needed, set to `--width` px, UTC date and time at the bottom right; beyond `--max` images, `--max` at regular intervals; prints the time of each image, then the path and the size of the GIF. To attach the scene to a reply to the customer; Read does not read a GIF: to look, `thumbnails.py --zone`.\n196\t\n197\t### whole image\n198\t\n199\t```\n200\tls /images/ | grep TZ\n201\t```\n202\t\n203\tThen Read on the file found (Read takes no pattern): the whole camera image at that time (UTC), for the scene (occultation, lighting, weather).\n204\t\n205\t## Conventions\n206\t\n207\t- Instants: `2026-01-01T00:00Z`; a time without time zone is read as UTC; `--end` includes the minute given. On a batch, `--start` and `--end` of the batch.\n208\t- Bash is used only to run these tools, `ls`, `grep` and `date`, one command per call, without a `for` loop (a pipe to `grep` is allowed): permissions are granted command by command. If the current directory is not the root of the calling repository, `cd && ` counts as one command. Write no other script. Whoever calls you may add commands to this list.\n209\t- **An output too long for one call** (beyond a few hundred lines, cut at display): shorten it first with the tool's options (`--table no` then `--table T1/T2`, `--min-measurements`, `--sensors`, `--columns`, a shorter window), or read a section of it through a pipe to `grep` (`| grep -A40 '^Title'`, `| grep '^pose_tilt '`). If you have to reread it several times, store it in the output folder in the same call (` > /.txt`) and read that file with Read (`offset`, `limit`) or with `grep`: no `head`, `tail`, `sed`, `cut`. The tools create their output folder themselves: no `mkdir`.\n210\t- A sensor name that carries an apostrophe (`COLH20'''`, `REFP''21`) goes in double quotes in the shell: `--sensors \"COLH20'''\",COLI22`.\n211\t- **Each PNG is looked at with Read**: you read a chart better than a table, and a PNG you have not looked at has shown nothing.\n212\t- A rejected measurement (`error_value` above the threshold) is not a measurement: the station empties the `corr` of a rejected target, but leaves those of a rejected **reference**, often absurd; the tools empty them (`corr`, ranges, residuals, jumps cover only accepted measurements). When the compensation retains only **two references**, their `corr` is 0 (to 1e-13): it passes exactly through them; their noise prints as `0` and their deviations in noises as \"-\"; read nothing into these values, read the references through `x`, `y` (`overview.py --rigid`) and `error_value`. Its `x`, `y` remain: before citing a jump of `x`, `y`, check whether it is marked `(rejected)`; a rejected measurement is not cited as a movement.\n213\t\n214\t## The method\n215\t\n216\t1. **Inventory** (`inventory.py`): what is available, what is missing. A filled column that the tools do not show or a source that no tool reads (`images_diff/`) remains data: know that it exists. The image quality columns (`peak` to `snr`, recent cameras) are read through `quality.py`; `metrics/` through `metrics.py`: a cut of the measurements is read against the steps without metric and the voltage (`--names BusVoltage,BusCurrent,Power,BatteryPercent --metrics-only` on the cut). On a batch, rerun it with the batch's `--start`/`--end`: the absent steps and the rejections of the batch, dated; those of the whole period say nothing about the batch. Read the rejections of the **references** as much as those of the targets: a sensor rejected at the same hours every day makes a moment on its own (say its share of rejected measurements and its hours, day by day); when it is a reference, say with how many references the compensation then runs (the list of retained references). When several targets jump together by one step, or the compensation drops (no pose), look first in that list at which references were lost at that instant.\n217\t2. **Wide first**:\n218\t - `overview.py` on the batch, first (on a batch of more than a few days, `--table no`, then `--table T1/T2` on the days to read), read in the order of its Reading section: the pose, who moves in the image (`--rigid` as soon as the pose rotates or changes scale), `x`, `y`, `sigma0` before `corr`, the residuals on every batch.\n219\t - On a batch of more than two days, then `days.py`, before reading the isolated steps of `ranges.py`: first its **byhour** PNGs and table by slot, then its **night levels**; `days.py --bounds` for what comes back every day and is labelled day by day.\n220\t - Several neighbouring stations given by whoever calls you: `stations.py` (temperatures, poses, `corr` of the targets, common rejections and gaps, at the same hours) before comparing their moments.\n221\t - When the pose or the `corr` of the targets drift over several days, or move without day/night cycle: `metrics.py` on the batch, the temperature against `tgt_corr_x`, `tgt_corr_y` and the pose, on the PNG, then r and the slope.\n222\t - On a station that has the image quality metrics: `quality.py --common --step 1d` on the batch (choice of the calm reference), then `quality.py --figure` with this reference: the median `flux` of the targets and of the references dates the hours of reduced visibility, the grey band that dives alone the occultations; with a labels file, `--labels F --outside`.\n223\t - Then `plot.py` on all the sensors, `error_value` then `corr_x`, `corr_y` (or `relative_x`, `relative_y`), references and targets; `summary.py` on these columns with a wide step (6h or 1d).\n224\t3. **Then zoom**: `summary.py` at 15min (`--stat max` for the real peak of a sensor), and `plot.py` on the windows and the sensors that move.\n225\t4. **Each sensor against its own usual level** (its median and its MAD), never against an absolute threshold; on a batch, the level is computed on the batch (`--level window`, `overview.py`), not on the whole period.\n226\t5. **Each retained moment is dated and measured at the native 15 min step**: start, end and maximum read on the 15 min table (`overview.py` by default, `summary.py --step 15min`), never on an hourly table; also `overview.py --min 1` for single sensors; `ranges.py` on the batch (first `--min-measurements 6`) for, per sensor, start, end, extreme and largest jump at the native step (`--outside` around a long episode, `--rolling` and `--instants 2` under a long drift or several steps); the tables of `x`, `y` on the windows where they stir. On a station that has the quality metrics, for each moment: `quality.py --table flux --sensors …` (or `--labels F --numbers N --edges` on a label): which targets are hidden or veiled, from which instant to which instant.\n227\t6. **The images**: thumbnails (with `--contrast` for a faint target) spaced, one every 2 to 3 h, tighter where the curves move, always with an unaffected witness sensor, at a time before, during and after (at the same hour of the day if possible); when `x`, `y` of a sensor jump between two thumbnails (centre of the frame written under each), rerun with `--fixed` before saying that a spot appears or disappears; the whole image for the scene (occultation, lighting, weather).\n228\t\n229\t## What the reading returns\n230\t\n231\tOne line per moment. A moment: a sensor or a group of sensors that leaves its usual level during a window you can date.\n232\t\n233\t| Start | End | Sensors | Columns | What I see | Images |\n234\t|---|---|---|---|---|---|\n235\t\n236\t- **Sensors**: references or targets, how many, which ones.\n237\t- **What I see**: the shape (one-step peak, step, slow rise, agitation), the amplitude against the usual level (in MAD or in times the median), the return to normal or not, what the other sensors do, **what the camera does** at the same moment (pose moving, by how much, or still; registration absent; \"no `camera/`\" if the folder has none).\n238\t- **Images**: what the thumbnails and the whole image show at that moment, or \"no image\".\n239\t\n240\tTimes in UTC.\n241\t"}]},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"b83c385f-4523-4ad6-9a7d-033c98b579b5","timestamp":"2026-11-17T20:31:06.252Z","tool_use_result":{"type":"text","file":{"filePath":"/home/maxime/aimsight-app/tools/GUIDE.md","content":"# Reading the data\n\nThe guide to the reading harness: followed by the analyst; improved by the upgrader (agents repository), run by Optimizer's `optimize` skill, the only one that writes here.\n\nA camera tracks targets (reflectors) fixed on a structure; its own movement is compensated thanks to reference targets, assumed fixed. This movement, the **camera pose** (`pan`, `tilt`, `rotation` in degrees, `scale`, `sigma0` of the registration, in `camera/`), is read before the sensors: it explains a large part of what moves on the curves (D-073). This guide says how to read a station's data: what the curves and the images show, moment by moment. It does not say what they mean: family, known event, hypothesis and verdict are the business of whoever calls you.\n\n## Read first\n\n- `tools/DATA.md`: the files of a station and the meaning of each column, the image quality metrics, the camera images (**first**);\n- `labeling/reading-rules.md`: what the data mean (the measurement chain, gaps, reading rules, false friends).\n\n## The tools\n\nRun them from the root of the calling repository, where `tools/`, `data/` and `labeling/` are links. They return values, never verdicts: you judge. `--out `: where whoever calls you stores your figures; they give it to you. The method (below) says in which order to run them; each section says what a tool returns and how to read it.\n\n| Tool | The question it answers |\n|---|---|\n| [`inventory.py`](#inventory) | What is there, what is missing: files, contents of each source, images, poses, cadence, sensors, rejections |\n| [`summary.py`](#summary) | The usual level of each sensor, then one column by time step |\n| [`plot.py`](#plot) | The series of chosen sensors and columns, as a PNG |\n| [`overview.py`](#overview) | All the sensors together, against the camera pose: common movement, single sensors, residuals, rigid movement |\n| [`ranges.py`](#ranges) | Dated ranges where each sensor leaves its level, at the native step |\n| [`days.py`](#days) | What comes back from one day to the next: night levels, days superimposed by hour, bounds of each day |\n| [`metrics.py`](#metrics) | The system metrics (temperature, voltage…) against the targets and the pose |\n| [`stations.py`](#stations) | Several stations on the same timeline |\n| [`quality.py`](#quality) | The six image quality metrics against a calm reference; labels; degraded instants no label covers |\n| [`thumbnails.py`](#thumbnails) | Full-resolution thumbnails of the camera images, around sensors or of a zone |\n| [`gif.py`](#gif) | A GIF of the camera images over a range, for a reply to the customer |\n| [`ls … \\| grep`](#whole-image) | The whole camera image at a time |\n\n### inventory\n\n```\npython3 tools/scripts/inventory.py [--start T] [--end T] [--files]\n```\n\nNames and counts, never values. Over the **whole period**:\n- files by type: beyond 5 per type, the count, the first and the last (`--files`: the full list, only to look for a specific file);\n- **what each source contains** over the window: the columns of the export, of the pose, of `quality/` and of `weather/` (the MeteoSwiss weather, hourly; a station without a Swiss position has none), with the number of rows that have a value (\"empty\" otherwise; an export column that not all sensors carry says how many carry it); the names of the system metrics of `metrics/`; the images and the difference images. The \"Export image quality (peak to snr)\" line says whether the six quality metrics are filled (then `quality.py`) or empty;\n- images by runs of equal gaps between two images (within 5 min, over the window if given): one line per change of gap, a hole is dated by its two images;\n- camera poses (count, period, measurement instants without registration), period, cadence, missing measurements, sensors (reference or target, error threshold, rejected measurements, distance from the camera and mm per px of `targets.csv`). When `pattern_type` is empty, a sensor is a reference if it carries `reproj_err` or `inlier` (the \"pattern_type empty for N sensors\" line says so);\n- \"Duplicate readings\": an export (often named after the customer's project) whose readings are already in the others; with 0 different values, it changes nothing to the reading, otherwise the tools keep the one of the last file in name order.\n\nWith `--start`/`--end` (on a batch: those of the batch), a section for the window: the missing steps, dated (for all the sensors, or which ones are missing); by sensor, the rejected measurements, dated (runs of consecutive steps; rejected: `error_value` above the sensor's threshold, **references included**); then the **number of references retained by the compensation** (`inlier` = 1) at each instant and the dated runs where some are not, which ones and why (`r` rejected, `0` discarded by the compensation, `empty`; another mark is the value of `inlier`, e.g. `-1`). When `inlier` is empty over the window, the retained references are read from the filled `reproj_err` (the title says so).\n\nA run that ends the same day writes only the time of its end. Over a month, the output with `--start`/`--end` exceeds what a call displays: read each section through `grep` (`| grep -A40 '^Retained references'`, `| grep '^ PR04 '`).\n\n### summary\n\n```\npython3 tools/scripts/summary.py [--column C] [--stat median|min|max] [--step 1h] [--level period|window] [--sensors A,B] [--start T] [--end T] [--instants T1,T2] [--mark]\n```\n\nThe usual level of each sensor (median, MAD, min, max) over the whole period, or over the `--start`/`--end` window with `--level window` (for a batch: a level change within the batch is not compared with weeks of other measurements); then a table by time step, the sensor header repeated every 24 lines.\n- Columns: `error_value`, `corr_x`, `corr_y`, `relative_x`, `relative_y`, `x`, `y`, `sigma0`, `reproj_err`, `corr_x_mm`, `corr_y_mm` (the `corr` in mm, empty without a sure factor: `tools/DATA.md`, \"The targets\"), and the six image quality metrics `peak`, `flux`, `sharpness`, `fwhm`, `dominance`, `snr` (raw values; against a calm reference, `quality.py`).\n- `--mark`: `*` after the value when a measurement of the step is rejected (`x`, `y`, `error_value` of a rejected measurement stay filled), `o` when one has inlier = 0.\n- `--instants T1,T2`: only the steps that contain these instants (the values of all the sensors at a few chosen times).\n- With `--step` equal to the cadence, `--level window --mark`: the per-instant, per-sensor table of one column, one column per run.\n\n### plot\n\n```\n.venv/bin/python tools/scripts/plot.py [--sensors A,B] [--columns C1,C2] [--start T] [--end T] [--zone T1/T2 ...] [--out D]\n```\n\nA PNG of the series, each `--zone` greyed; prints its path. Columns: those of `summary.py`, quality metrics included (raw values).\n\n### overview\n\n```\n.venv/bin/python tools/scripts/overview.py [--columns x,y,sigma0] [--column error_value] [--step 15min] [--k 5] [--min 5] [--residuals corr_x,corr_y,error_value|no] [--outside T1/T2] [--others] [--rigid BASE [--without A,B] [--follow A,B]] [--table T1/T2|no] [--sensors A,B] [--start T] [--end T] [--out D]\n```\n\nAll the sensors together, each against its median and its MAD over the window.\n\nPNGs:\n- **common**: at the top, if the folder has `camera/`, the **camera pose** (raw values, one point per registration, the line cut at measurement instants without registration); the median across sensors of `x`, `y`, `sigma0`, the dispersion across sensors as a grey band; on the `x`, `y` panels, also **each global reference separately** (one line each) and the **median of the targets alone** (black line); at each step, the number of sensors whose `--column` exceeds its median by more than `--k` MAD. Ticks every 1 to 12 h depending on the window, every n days beyond 20 days.\n- **multiples**: a small chart per sensor, one scale each: a step of a single sensor shows there.\n- **residuals-corr_x**, **-corr_y**, **-error_value** (`--residuals`; `no`: none of these PNGs nor their tables): a small chart per sensor of the column minus the sensor's own level (its median over the window; with `--outside T1/T2`, that of the rest of the window, outside the moment read), one scale each, zero dotted: a deviation of a few hundredths on `corr`, hidden in the parallel bands of `plot.py`, shows there.\n- **residuals-…-others** (`--others`): each sensor minus its own median **and minus the median of the other sensors at the same instant**: what all share (the remainder of the compensation of a common movement) cancels, what is specific remains.\n- **rigid** (`--rigid BASE`): at each measurement, the overall movement of the targets since the instant `BASE` (translation, rotation, scale, estimated by medians: a target that jumps alone does not pull it; `--without A,B` removes targets from it) and, for each sensor, the **residual** `dx`, `dy` (raw position minus its position at `BASE` carried by this movement, in px). Panels: `dx`, `dy` of each global reference against the median and the 10th-90th percentile of the targets, `|residual|` of the targets (median, 90th percentile), fitted rotation and scale, `reproj_err` of the references; a rejected reference is a cross (the scale is that of the accepted measurements, a far cross is out of frame).\n\nPrinted:\n- the **common median table**, one line per `--step`: the time, the deviation from the window median of `x`, `y`, `sigma0`, then `x_targets`, `y_targets` (median of the targets alone), then the raw camera pose `cam_pan`, `cam_tilt`, `cam_rotation`, `cam_scale`, `cam_sigma0` (empty without registration); the minimum and the maximum of each column with their instant; then those of `x`, `y` of each global reference (`(rejected)` when the measurement is, with the reference's number of rejected measurements); the measurement instants without pose (dated runs); the instants where at least `--min` sensors exceed together, with their names (`--min 1`: also a single sensor that leaves its level, absent from the default list of 5 sensors);\n- `--residuals`: per sensor, the level, the own noise (median of the differences between two measurements), the min/max deviation per step with their instant, in units and in noises;\n- `--others`: per sensor, the slope and the correlation r of the residual on the common median of `x`, `y`, `sigma0`;\n- `--rigid`: the table by step (`rot_deg`, `scale`, `tx`, `ty`, `tgt_med`, `tgt_max`, `dx`, `dy` of each reference and of each sensor of `--follow A,B`: the step-by-step sequence of a target) and, per sensor, min, max and value at the last instant of `dx`, `dy`. Rejected measurements enter neither the fit, nor the band of the targets, `tgt_med`, `tgt_max`, nor the columns of the table (over several days, parked cars or night rejections no longer drown the rest); the per-sensor summary gives them separately (`; N rejected: min …, max …`, and `(rejected)` after a last value that is rejected).\n\nThe tables by step (common median, `--rigid`) repeat their header every 24 lines; `--table T1/T2` prints them only between T1 and T2 (`no`: not at all), levels, min, max, PNGs and the rest remaining over the whole window: over a one-month batch, first `--table no`, then `--table` on the day of a moment (same levels, which a shorter `--start`/`--end` window would not give). The default step is 15 min, the cadence of the measurements: a one-hour step flattens a peak of one to four steps, dates to the hour and erases an agitation of `x`, `y`; do not widen it to read a batch.\n\nReading, in this order:\n1. **The camera pose first** (top panels, `cam_` columns), dated at the native step: when it rotates (`pan`, `tilt`, `rotation`), changes scale, when its registration degrades (`sigma0`) or is absent (line cut, instants without pose). Each moment of the sensors is read against it: during a movement or a registration gap, or camera still.\n2. **Who moves in the image.** The pose is computed from the global references: a change of pose (or a rise of `sigma0`) is a camera movement only if **the targets also move in the image** (on the `x`, `y` panels, the lines of the references against the black line of the targets alone; `x_targets`, `y_targets`). Only references move, targets still: these references moved, and the pose and the `corr` of all the targets are skewed without raw movement of the targets; say which references and by how much. References and targets together: the camera or the scene; then look whether the `corr` come back.\n3. **Rotation or scale: `--rigid`.** Then the deviation from the median no longer says who moves alone (each sensor deviates according to its place in the image; the rigid residual does not). Before writing \"everything moves together\", rerun with `--rigid BASE`, `BASE` a calm instant before the first movement: a reference whose residual stays far from the 10th-90th percentile of the targets, or a `reproj_err` of the references that does not come back, means the compensation remains skewed by these references and the steps of `corr` partly come from it (say which, by how much, until when); a rising `|residual|` of the targets says they do not move as a block.\n4. **Then `x`, `y`, `sigma0`, before `corr`**: the median of `x`, `y` (raw position, references included), the references one by one, the targets alone and `sigma0` say what moves in the image. Date the start, the end, the return of a movement, or a level that does not come back, on the printed table (time, value), not on the PNG axis. A dip of `corr` after a movement of the raw median is the remainder of the compensation, not a movement of these sensors. The multiples of `error_value` show a lasting step of a sensor, the count the instants where many rise together.\n5. **The residuals, on every batch, without waiting for a suspicion**: a single sensor that rises or falls, a `corr` that drifts by a few hundredths, a step specific to one sensor under a common movement show there; the table says by how much (in noises) and when. On a target whose `corr` goes down under a strong common movement, `--others` separates a remainder of the compensation from a movement of its own: a dip that remains is not a remainder shared by all; a high slope with r close to ±1 on common `y` says it is proportional to the common movement (gain specific to the sensor); without r or slope, it is independent of the movement.\n\n### ranges\n\n```\npython3 tools/scripts/ranges.py [--columns error_value,corr_x,corr_y] [--k 5] [--merge 1h] [--min-measurements 1] [--outside T1/T2] [--rolling N|DURATION] [--instants N] [--sensors A,B] [--start T] [--end T]\n```\n\nDates the start and the end of a sensor's moment without rerunning ten tables. By column and by sensor, at the measurements (native step, never averaged): level (median of the window), own noise, **largest jump** from one measurement to the next (value, in noises, the two instants; `(rejected: …)` when one end is); then the **ranges** where the sensor deviates from its level by more than `--k` noises: start, end, number of measurements, extreme (signed, in units and in noises) and its instant. Two ranges of the same sign less than `--merge` apart make one; rejected measurements do not cut a range; column `rejected`: how many of the range's measurements are (and `rejected extreme`). A range that touches the edge of the window is dated at the edge.\n- `--outside T1/T2`: level and noise computed outside an episode that skews the window median (the sensor spends half the batch there). Rerun with it around a long episode to date its return to the level: do not conclude \"does not come back\" without having read it.\n- `--min-measurements N`: only the ranges of at least N measurements (and how many out of the total). Over several days, the one-step ranges number in the hundreds and drown the long steps: first `--min-measurements 6`, then without.\n- `--rolling N` (N measurements on each side) or `--rolling 1d` (the measurements within a duration): the level of each measurement is the median of its neighbours, without it; a long drift or a step follows this local level, only the deviations shorter than the window remain (the level column and the noise do not change; with `--outside`, only the noise is computed outside the episode).\n- `--instants N`: at the end, the instants where at least N sensors are out of level on one of the columns, with each sensor and its signed deviation in noises (`cx` corr_x, `cy` corr_y, `ev` error_value), the sensors rejected at that instant (among `--sensors`: removing the always-rejected sensors lightens the list), and each reference: `error_value` (`r` if rejected) / inlier.\n- When the batch has a long drift or several steps (the ranges number in the hundreds, or one half of the batch is \"out of level\"), rerun with `--rolling` (a few measurements, or a few hours to a day depending on the cadence) and `--instants 2`: the brief deviations under the drift come out alone, and the list per instant says which sensors deviate together, which are rejected and what the references do; a deviation of all the targets with the references at the same instant is read against the camera pose.\n\nA noise of `0` (and \"-\" in noises, no range): the values are constant to rounding (deviations below 1e-9), like the `corr` of the references when the compensation retains only two (see Conventions); the same in `overview.py --residuals` and `days.py`.\n\n### days\n\n```\n.venv/bin/python tools/scripts/days.py [--columns corr_x,corr_y,error_value] [--night 20-3] [--k 5] [--days 2] [--step 15min] [--sensors A,B] [--bounds [--smoothing N] [--fraction F]] [--start T] [--end T] [--out D]\n```\n\nWhat comes back from one day to the next, on accepted measurements only. A night: the hours `--night` H1-H2 UTC, straddling midnight, dated from the day it starts; choose hours where the day cycle (`error_value`, camera pose) has subsided (**byhour** figure).\n\n1. **Level of each night**, by sensor and by column: median, MAD, number of measurements, own noise; from one night to the next, the **step** (difference of the medians, in units and in noises) and **where it falls** (\"between A and B\": where the night measurements of the two nights split best between the two levels; B at the start of the following night: the cut falls by day). Read it for any sensor that has already made a step or for which `--outside` is not enough (several levels in the batch): a step of a few noises is dated by its \"between A and B\", a step of `error_value` and one of `corr` at the same instant are linked, a slow drift reads from one night to the next.\n2. **Superimposed days**: PNG **byhour-**, a small chart per sensor, hour of the day on the x axis, one curve per day, each measurement minus the level of the last night started (night greyed, frame from the 1st to the 99th percentile, the title says how many measurements fall outside it). Table: per `--step` slot of the hour of the day, the sensors whose deviation exceeds `--k` noises on the same side at least `--days` days, with the number of days and the median of these deviations. What comes back every day at the same hour, on one or several sensors, groups there, even when it lasts one to three measurements: one moment per hour of the day (say which sensors, how many days out of how many, the amplitude, what the camera pose does at that hour), not one moment per day, nor nothing because each step is short.\n3. **Bounds of each day** (`--bounds`), for what comes back every day and is labelled day by day (thermal cycle, warming and cooling), rather than fixing the same hours for all the days: for the median of the targets of each column (with `--sensors`, the median of these sensors; with one, its own) and for the camera pose (`pan`, `tilt`, `rotation`, `scale`, `sigma0`, if `camera/` exists), the deviation from the level of the night that precedes each day (a day goes from the end of one night to the end of the next). Per day: number of measurements, the first and the last; first and last instant beyond `--k` noises, with the measurement just before and just after, at the native step; signed max and min with their instant; the sequence of measurements beyond `--k` noises around the larger of the two; the following night minus the reference night. A day without measurement says so; a reference night that is not the previous one is named. Each day line starts with the short name of its series (`corr_x`, `pose_tilt`…): `| grep '^pose_tilt '` reads one, `| grep ' 12/10 '` one day. PNG **bounds**: the deviation over the batch, first → last exceedance light grey, sequence around the extreme dark grey, max and min marked.\n - `--smoothing N`: the deviation of each measurement is the median of the N measurements of the day centred on it (noise and `--k` unchanged; PNG: smoothed in blue, raw in grey): an isolated point no longer cuts the sequence around the extreme nor makes a first or a last exceedance.\n - `--fraction F`: the threshold of each day is F times its largest |deviation| (printed on its line, `threshold …`), instead of `--k` noises: when the noise at the native step is unrelated to the amplitude of the cycle (very noisy or very smooth pose).\n - Reading: the sequence around the extreme dates the cycle, the max and the min a go and a return (morning and afternoon); \"before\" and \"after\" give the bounds at the native step (at a cadence of 1 h or 4 h, an event goes from the measurement before to the one after). First exceedance at the start of the day (\"before -\") and last at its end every day: the night is not calm; change `--night`, or `--sensors` the targets that carry the cycle. Camera drifting all night: a short night just before the morning (`--night 3-5`: the level of the rest that precedes the start). Noisy series or isolated points: `--smoothing 5`. Threshold in noises that does not bite (never exceeded, or exceeded all day): `--fraction 0.3`, then read the sequence around the extreme, not the first and the last exceedance. A \"1 measurements\" line is a peak, not a cycle.\n\n### metrics\n\n```\n.venv/bin/python tools/scripts/metrics.py [--names A,B] [--step 1h] [--stat median|min|max] [--against temperature] [--smoothing 24h] [--metrics-only] [--start T] [--end T] [--out D]\n```\n\nThe system metrics of `metrics/` (one value per hour), never the identifiers (`SIM_CCID`, `ip*`):\n- the available metrics with their number of values over the window (\"empty\": none; all empty is an absent datum, not a stable temperature);\n- a table per `--step`: `temperature` (median of the `sensor_*_deg_c` components, the one the detectors read), each metric of `--names` (default: the `*_deg_c` and `BusVoltage`), then, unless `--metrics-only`, `tgt_corr_x`, `tgt_corr_y` (median over the targets of `corr` minus each target's own level, accepted measurements) and the raw camera pose (`cam_pan` … `cam_sigma0`); an empty cell is skipped, a text metric (`link`, `BatteryState`, `last_sync`) is returned as it is. `--step 1d --stat min` (or `max`): the minimum or the maximum of each day;\n- per column: filled steps, min and max with their instant; the correlation r and the slope of each column on `--against` (with `--smoothing 24h`, on its rolling mean, column `_smooth`: for a station where the temperature varies little and fast, indoors); the dated runs of steps without any metric;\n- a PNG: temperatures on one panel (median in black), each other metric on its own, then `tgt_corr_x`, `tgt_corr_y` and the pose, line cut on a gap.\n\nAn r does not say a cause: say it as a value, with the window where it is computed.\n\n### stations\n\n```\n.venv/bin/python tools/scripts/stations.py [...] [--columns temperature,cam_tilt,cam_rotation,cam_scale,tgt_corr_x,tgt_corr_y] [--step 1h] [--stat median|min|max] [--table T1/T2|no] [--start T] [--end T] [--out D]\n```\n\n**Several stations on the same timeline** (neighbouring stations, same building). Columns: `temperature` (as in `metrics.py`), `cam_pan` … `cam_sigma0` (raw pose), `tgt_corr_x`, `tgt_corr_y` (as in `metrics.py`), `rej_targets`, `rej_refs` (number of rejected targets, of rejected references, the largest of the step).\n- Prints per station the period, the cadence and the number of instants; the **gaps**: the runs of steps without measurement or without temperature, with the stations where they are missing (a gap common to several stations on a single line); the table by step (one `STATION:column` column each, tabs; `--table` as in `overview.py`); per column and per pair of stations, r of the values and r of the steps from one value to the next (a common movement shows on the steps, a common trend on the values), with n.\n- PNG **stations**: a panel per column, a line per station (raw temperature, the rest minus its median), and a band per station of the steps without measurement.\n- Take `--step` equal to the slowest cadence of the stations; over a month at `1h`, first `--table no`.\n\n### quality\n\n```\npython3 tools/scripts/quality.py [--calm T1/T2,T3/T4] [--common] [--table M] [--step 15min] [--threshold 0.5] [--sensors A,B] [--start T] [--end T]\n... --labels F [--numbers 3,7] [--margin 60] [--edges]\n... --labels F --outside [--min 1] [--except \"Thermal displacement\"]\n.venv/bin/python tools/scripts/quality.py --figure [--metrics flux,snr,dominance] [--labels F] [--zone T1/T2 ...] [--out D]\npython3 tools/scripts/quality.py --self-test\n```\n\nThe six **image quality metrics** (`peak`, `flux`, `sharpness`, `fwhm`, `dominance`, `snr`; definitions: `tools/DATA.md`), on the stations that have them (otherwise: \"No quality metrics\", and nothing else). Each measurement becomes a **ratio** to the **calm reference** of its sensor: the median of the metric over its measurements in the `--calm` windows, at the same UTC hour of the day (without `--calm`: the whole folder); 1 = like the reference, < 1 lower, > 1 higher; for `fwhm` and `dominance`, the rise says a degraded image; rejected measurements included.\n- Without options: the folder's maximal `peak`, then per sensor (`r` = reference) the rejected measurements, `pk/max` (median peak over the window divided by this maximum: at 1, the spot touches the image ceiling, its `peak` no longer moves and its `sharpness` follows the exposure: read `flux`, `snr` instead), and for each metric the median ratio and the extreme with its instant; then the median of the targets and of the references.\n- `--common`: per step, the median of the ratios of the targets / of the references for each metric (what affects the whole scene, visibility or turbulence; `--step 1d` shows on one screen on which days the reference holds).\n- `--table M`: per step, the ratio of `M` of each sensor (`*`: a rejected measurement), their median and how many pass `--threshold` (below, or above 1/`--threshold` for `fwhm`, `dominance`): a target that goes out and comes back; on a moment, `--table flux --sensors …` says which targets are hidden (flux cut) or veiled, from which instant to which instant: write them by their name.\n- `--labels F` (one JSON per line, `start`, `end`, `family`): per numbered label, the median ratio of the targets and of the references over the hour before, the range and the hour after (`tgt 0.96|0.26|0.79`, `--margin` minutes), then the sensors **affected** over the range (flux or snr below `--threshold`, or dominance above 1/`--threshold`), with their worst flux, from lowest to highest. `--edges`: per instant of the widened range, the number of affected sensors and the median of the targets of flux, snr, dominance (`<` within the range), to date the first and the last degraded instant.\n- `--outside`: the runs of instants that no label covers (outside `--except` families) where at least `--min` sensors are affected, with the sensors and their worst flux: candidates for forgotten labels, to check on `corr_x`, `corr_y`.\n- `--figure` (instead of the tables): PNG **quality-common** (a panel per metric, log scale: median of the targets in black, of the references in red, grey band from the 10th to the 90th percentile of the targets: a disturbance of the whole scene moves the median, an occultation of a few targets only the bottom of the band) and a PNG **quality-** per `--metrics` (a small chart per sensor, references in red); `--labels` greys each label in one colour per family, `--zone` ranges.\n\nReading: the metrics say **why** a measurement degrades, where `error_value` says only that it degrades; they prove a cause and name the affected targets. What they showed on LENZSPITZE (to be confirmed on each station): `flux` cut (close to 0) on a group of targets, the others intact, for one to a few measurements: these targets are hidden (the list is read on the flux each time, not on the usual list; a hidden target can stay under its error threshold, and its point is wrong); `flux` down over the whole scene, stronger on the distant targets: reduced visibility; `sharpness` down and `dominance` up, `flux` whole: the image shakes (turbulence); nothing moves: neither the image nor the view, to be looked for in the movement. A whole flux refutes an occultation. `fwhm`, truncated to the disc, moves little; on a spot at the ceiling (`pk/max` at 1), it goes down when the spot darkens.\n\n**The calm reference decides everything**: take `--calm` on calm hours of the **same image regime** as the range read. When the lighting or the exposure changes (after a gap, an intervention), a reference on the other side skews the ratios by a factor of two or three: `--common --step 1d` over the batch shows this change (medians of the targets and of the references far from 1 for whole days, then at 1); then take a reference on each side and read each side with its own. Calm days are often days of thermal cycle: a reading of the thermal against them is circular.\n\n### thumbnails\n\n```\n.venv/bin/python tools/scripts/thumbnails.py --sensors A,B --times T1,T2 [--radius 100] [--contrast [MIN,MAX]] [--fixed] [--zone X,Y,W,H] [--out D]\n```\n\nA sheet of full-resolution thumbnails: one row per sensor, one column per time, centred on the sensor's raw position (`x`, `y`) at each time. Look at it with Read: a whole image read by Read is reduced, a small reflector becomes illegible in it.\n- The centre of the frame is written under each thumbnail: when `x`, `y` jump, the frame moves by as much, and a spot that enters the frame seems to appear; `--fixed` keeps for each sensor the frame of the first time and marks with a red cross the `x`, `y` of each time.\n- Unretouched pixels: the brightness compares from one thumbnail to the next; prints for each thumbnail the background (median), the 99th percentile and the peak (grey levels 0 to 255). Without an image at the requested time, takes the nearest and prints the gap (the actual time is in the title).\n- A faint or deformed spot is invisible as it is: `--contrast MIN,MAX` puts all the thumbnails in grey with the same stretch (without value: from the 1st percentile to the sheet's maximum, crushed by a saturated pixel; then choose MIN,MAX from the printed background and peak, e.g. `10,40`); `--radius 30` to `50` magnifies. Compare the shape and the peak before, during and after an episode, at the same hour of the day.\n- A frame that the image edge cuts is flagged (\"frame cut by the image edge (W × H px)\"): on some stations, `x`, `y` are not pixels (values close to 0) and the frame falls in the corner; then look at the scene through `--zone`.\n- `--zone X,Y,W,H` (pixels of the original image: top left corner, width, height, as in `gif.py`): the same zone at each time, side by side (up to 4 per row), same stretch with `--contrast`; `--sensors` becomes optional, those given are marked with a cross and their name. For the scene around the targets (foreground object, headlights, lighting), prefer it to a large `--radius`.\n- Each thumbnail is rendered pixel for pixel up to 1000 px a side, but Read reduces a wide PNG: with a large `--radius` or a large `--zone`, three or four times per sheet.\n\n### gif\n\n```\n.venv/bin/python tools/scripts/gif.py --start T --end T [--width 720] [--duration 700] [--max 150] [--zone X,Y,W,H] [--out D]\n```\n\nA GIF of the camera images between `--start` and `--end` inclusive, cropped to `--zone` if needed, set to `--width` px, UTC date and time at the bottom right; beyond `--max` images, `--max` at regular intervals; prints the time of each image, then the path and the size of the GIF. To attach the scene to a reply to the customer; Read does not read a GIF: to look, `thumbnails.py --zone`.\n\n### whole image\n\n```\nls /images/ | grep TZ\n```\n\nThen Read on the file found (Read takes no pattern): the whole camera image at that time (UTC), for the scene (occultation, lighting, weather).\n\n## Conventions\n\n- Instants: `2026-01-01T00:00Z`; a time without time zone is read as UTC; `--end` includes the minute given. On a batch, `--start` and `--end` of the batch.\n- Bash is used only to run these tools, `ls`, `grep` and `date`, one command per call, without a `for` loop (a pipe to `grep` is allowed): permissions are granted command by command. If the current directory is not the root of the calling repository, `cd && ` counts as one command. Write no other script. Whoever calls you may add commands to this list.\n- **An output too long for one call** (beyond a few hundred lines, cut at display): shorten it first with the tool's options (`--table no` then `--table T1/T2`, `--min-measurements`, `--sensors`, `--columns`, a shorter window), or read a section of it through a pipe to `grep` (`| grep -A40 '^Title'`, `| grep '^pose_tilt '`). If you have to reread it several times, store it in the output folder in the same call (` > /.txt`) and read that file with Read (`offset`, `limit`) or with `grep`: no `head`, `tail`, `sed`, `cut`. The tools create their output folder themselves: no `mkdir`.\n- A sensor name that carries an apostrophe (`COLH20'''`, `REFP''21`) goes in double quotes in the shell: `--sensors \"COLH20'''\",COLI22`.\n- **Each PNG is looked at with Read**: you read a chart better than a table, and a PNG you have not looked at has shown nothing.\n- A rejected measurement (`error_value` above the threshold) is not a measurement: the station empties the `corr` of a rejected target, but leaves those of a rejected **reference**, often absurd; the tools empty them (`corr`, ranges, residuals, jumps cover only accepted measurements). When the compensation retains only **two references**, their `corr` is 0 (to 1e-13): it passes exactly through them; their noise prints as `0` and their deviations in noises as \"-\"; read nothing into these values, read the references through `x`, `y` (`overview.py --rigid`) and `error_value`. Its `x`, `y` remain: before citing a jump of `x`, `y`, check whether it is marked `(rejected)`; a rejected measurement is not cited as a movement.\n\n## The method\n\n1. **Inventory** (`inventory.py`): what is available, what is missing. A filled column that the tools do not show or a source that no tool reads (`images_diff/`) remains data: know that it exists. The image quality columns (`peak` to `snr`, recent cameras) are read through `quality.py`; `metrics/` through `metrics.py`: a cut of the measurements is read against the steps without metric and the voltage (`--names BusVoltage,BusCurrent,Power,BatteryPercent --metrics-only` on the cut). On a batch, rerun it with the batch's `--start`/`--end`: the absent steps and the rejections of the batch, dated; those of the whole period say nothing about the batch. Read the rejections of the **references** as much as those of the targets: a sensor rejected at the same hours every day makes a moment on its own (say its share of rejected measurements and its hours, day by day); when it is a reference, say with how many references the compensation then runs (the list of retained references). When several targets jump together by one step, or the compensation drops (no pose), look first in that list at which references were lost at that instant.\n2. **Wide first**:\n - `overview.py` on the batch, first (on a batch of more than a few days, `--table no`, then `--table T1/T2` on the days to read), read in the order of its Reading section: the pose, who moves in the image (`--rigid` as soon as the pose rotates or changes scale), `x`, `y`, `sigma0` before `corr`, the residuals on every batch.\n - On a batch of more than two days, then `days.py`, before reading the isolated steps of `ranges.py`: first its **byhour** PNGs and table by slot, then its **night levels**; `days.py --bounds` for what comes back every day and is labelled day by day.\n - Several neighbouring stations given by whoever calls you: `stations.py` (temperatures, poses, `corr` of the targets, common rejections and gaps, at the same hours) before comparing their moments.\n - When the pose or the `corr` of the targets drift over several days, or move without day/night cycle: `metrics.py` on the batch, the temperature against `tgt_corr_x`, `tgt_corr_y` and the pose, on the PNG, then r and the slope.\n - On a station that has the image quality metrics: `quality.py --common --step 1d` on the batch (choice of the calm reference), then `quality.py --figure` with this reference: the median `flux` of the targets and of the references dates the hours of reduced visibility, the grey band that dives alone the occultations; with a labels file, `--labels F --outside`.\n - Then `plot.py` on all the sensors, `error_value` then `corr_x`, `corr_y` (or `relative_x`, `relative_y`), references and targets; `summary.py` on these columns with a wide step (6h or 1d).\n3. **Then zoom**: `summary.py` at 15min (`--stat max` for the real peak of a sensor), and `plot.py` on the windows and the sensors that move.\n4. **Each sensor against its own usual level** (its median and its MAD), never against an absolute threshold; on a batch, the level is computed on the batch (`--level window`, `overview.py`), not on the whole period.\n5. **Each retained moment is dated and measured at the native 15 min step**: start, end and maximum read on the 15 min table (`overview.py` by default, `summary.py --step 15min`), never on an hourly table; also `overview.py --min 1` for single sensors; `ranges.py` on the batch (first `--min-measurements 6`) for, per sensor, start, end, extreme and largest jump at the native step (`--outside` around a long episode, `--rolling` and `--instants 2` under a long drift or several steps); the tables of `x`, `y` on the windows where they stir. On a station that has the quality metrics, for each moment: `quality.py --table flux --sensors …` (or `--labels F --numbers N --edges` on a label): which targets are hidden or veiled, from which instant to which instant.\n6. **The images**: thumbnails (with `--contrast` for a faint target) spaced, one every 2 to 3 h, tighter where the curves move, always with an unaffected witness sensor, at a time before, during and after (at the same hour of the day if possible); when `x`, `y` of a sensor jump between two thumbnails (centre of the frame written under each), rerun with `--fixed` before saying that a spot appears or disappears; the whole image for the scene (occultation, lighting, weather).\n\n## What the reading returns\n\nOne line per moment. A moment: a sensor or a group of sensors that leaves its usual level during a window you can date.\n\n| Start | End | Sensors | Columns | What I see | Images |\n|---|---|---|---|---|---|\n\n- **Sensors**: references or targets, how many, which ones.\n- **What I see**: the shape (one-step peak, step, slow rise, agitation), the amplitude against the usual level (in MAD or in times the median), the return to normal or not, what the other sensors do, **what the camera does** at the same moment (pose moving, by how much, or still; registration absent; \"no `camera/`\" if the folder has none).\n- **Images**: what the thumbnails and the whole image show at that moment, or \"no image\".\n\nTimes in UTC.\n","numLines":241,"startLine":1,"totalLines":241}},"tool_result_meta":[{"id":"toolu_01Sm7cbD7iXk22kFLnocZkiF","permission_decision":{"decision":"accept","source":"config","reason_type":"rule"}}]}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98n3RGUXfNwFvkqgaDt","type":"message","role":"assistant","content":[{"type":"tool_use","id":"toolu_01Sm3RseXnHDTBJyNTT6MFsq","name":"Read","input":{"file_path":"/home/maxime/aimsight-app/tools/DATA.md"},"caller":{"type":"direct"}}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":524,"cache_read_input_tokens":10876,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":524},"output_tokens":16,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"3f60d6e4-b1c0-41e5-bfce-ef183880226b","timestamp":"2026-11-17T20:31:06.393Z","request_id":"req_011Ch98n3C8UGUW8Q6NtwAzR","wire_tool_inputs":{"toolu_01Sm3RseXnHDTBJyNTT6MFsq":{"file_path":"/home/maxime/aimsight-app/tools/DATA.md"}}}
-{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_01Sm3RseXnHDTBJyNTT6MFsq","type":"tool_result","content":"1\t# The data of a station\n2\t\n3\tWhat the files of a station folder are, and what each column means. How to read them with the tools: `GUIDE.md`. What they mean for a label (causes, reading rules, false friends): `labeling/reading-rules.md`. Maintained by hand; `GUIDE.md` is the tool-builder's.\n4\t\n5\t## The displacements: the \"advanced\" export\n6\t\n7\t`displacement/_advanced__.csv`, the source of the analyses: one row per sensor and per measurement, at the native rate of the station (10 or 15 min), `time_utc` in explicit UTC.\n8\t\n9\t| Column | Meaning |\n10\t|---|---|\n11\t| `sensor_name` | the sensor (target or reference) |\n12\t| `pattern_type` | `global_ref`: a reference of the compensation; `ref`: a *local reference*, treated as a target, outside the compensation, without `reproj_err`; empty: a target |\n13\t| `x`, `y` | raw position in the image [px]. Not the centroid of the spot: the offset centroid − (`x`, `y`) is constant per sensor by day and differs between sensors; it changes at night, when the spot is saturated. Probably the position of the reference pattern |\n14\t| `relative_x`, `relative_y` | relative displacement before the camera compensation [px]; not `x − x0` |\n15\t| `corr_x`, `corr_y` | the position of the target once the estimated camera movement is removed: **the curves that are labelled**. In px, not mm (below) |\n16\t| `corr_x_mm`, `corr_y_mm` | `corr_x`, `corr_y` in mm: × the sensor's `mm_per_px` (`targets.csv`, below), computed by `data.load`; empty without a sure factor. The same curves in another unit: the noise threshold of a label is read in noises, whatever the unit; mm say how far a target moves, for the reader |\n17\t| `error_value` | recognition error of the pattern, not an uncertainty |\n18\t| `error_threshold` | specific to each sensor (0.3 to 0.7). Above it, the measurement is rejected: the row and its `error_value` stay, `corr_x` and `corr_y` are empty, not interpolated |\n19\t| `reproj_err`, `inlier` | references only: residual and contribution of each reference in the compensation |\n20\t| `sigma0` | residual of the fit on the references: one value per measurement, repeated on every row |\n21\t| `peak`, `flux`, `sharpness`, `fwhm`, `dominance`, `snr` | image quality of each sensor, recent cameras only (below) |\n22\t\n23\t- \"Rejected\" is a judgment of the AIMsight platform, not of the camera: the camera delivers all its measurements, and a client's platform that integrates the data receives them all.\n24\t- **Unit of `corr_x`, `corr_y`**: px. The hourly export's `horizontal_displacement` (mm) is a factor × the hourly mean of `corr_x` + a constant (likewise `vertical` and `corr_y`, correlation ≥ 0.99); the factor (mm per px) depends on the pattern and on the station.\n25\t- **LENZSPITZE**: its export gives `x`, `y` relative to the pattern; the extraction rewrites them in image px and fills `pattern_type`. Sensors 1023 and 8019 have no pattern: their `x`, `y` are empty. The tools' crosses may sit slightly off the spots there.\n26\t- `inventory.py` says, on a batch, which columns carry values.\n27\t\n28\t## The targets\n29\t\n30\t`targets.csv`, from the pumping: one line per sensor of the platform, `sensor_name`, `pattern_type`, `distance_mm` (from the camera) and `mm_per_px` (`distance_convertion_factor`, the factor of the dashboard's exports in mm), their current values. Read by `data.load_targets`, shown by `inventory.py` (sensor table).\n31\t- The references are not in it yet (pumped from the next pumping on): no distance, no mm for them. They are assumed fixed.\n32\t- `distance_mm` 1000: not filled in on the platform; the line is ignored.\n33\t- A name may have several lines (a target counted twice, an older configuration of the unit, another lens): when they disagree, `data.load_targets` keeps no value (`inventory.py`: `?(n)`) and that target has no mm; the distance stays when the lines agree on it.\n34\t- The distance says which targets are near and far. A far target moves few px for many mm: targets are compared with each other in mm, or in px with their distance. A camera that turns shifts every target by about the same px (the mm grow with the distance); a movement of the structure of the same mm gives px that shrink with the distance; a parallax shows between targets at different distances.\n35\t\n36\t## The camera pose\n37\t\n38\t`camera/_camera_.csv`, from the pumping only: the pose at each registration, `time_utc` in UTC, `median_|min_|max_` of `pan`, `tilt`, `rotation` [deg], `scale`, `sigma0`, one row per measurement (min = max). A measurement instant without a row: the camera was not registered.\n39\t\n40\t- Orders of magnitude: `pan`, `tilt` of a few hundredths of a degree, `scale` within 10⁻³ of 1; some stations show several degrees, not explained.\n41\t- **A positive `tilt` means the camera is nosing down** (the expert).\n42\t- Read by `overview.py` and `inventory.py`.\n43\t\n44\t## The weather\n45\t\n46\t`weather/_weather_.csv`, from the pumping, for a station with a Swiss position only: the hourly measurements of the nearest MeteoSwiss station, `time_utc` in UTC (start of the hour); `position`, `place`, `station`, `station_name`, `distance_km`, `height_m` say where; then `precipitation_mm`, `temperature_c`, `humidity_pct`, `wind_speed_kmh`, `wind_gust_kmh`, `wind_direction_deg`, `pressure_hpa`, `sunshine_min`, `global_radiation_wm2`, `snow_depth_cm` (empty: not measured there). The weather a few km away, not at the camera: what the images show prevails. Read by `data.load_weather`.\n47\t\n48\t## The hourly export\n49\t\n50\t`__to__1hour.csv`: one row per hour, targets only; per target `horizontal_displacement`, `vertical_displacement`, their `_min` / `_max`, `_error` (mean `error_value` of the hour), `_count_val` (measurements of the hour, rejected ones included).\n51\t\n52\t- **`timestamp` has no time zone: Swiss local time** (UTC+2 in summer), at the start of the hour.\n53\t\n54\t## Image quality of a target\n55\t\n56\tSix columns of the advanced export, computed by the GPU of recent cameras on the sensor's window in the DIFF image, in units of that image. Filled only where `inventory.py` says so (\"Export image quality\"); for older cameras, `~/optical_emulator` can recompute them from the DIFF images. \"Disc\": the neighbourhood of the peak, radius `min(H, W)/6` (at least 3 px); \"background\": the rest of the window.\n57\t\n58\t| Metric | Definition | What it measures | Reading |\n59\t|---|---|---|---|\n60\t| `peak` | `max(I)` | the brightness of the return | high, saturation; low, underexposure or missed flash. All targets dropping: the lighting; a single one: that target (fouling, misalignment) |\n61\t| `flux` | flux of the disc minus the background | the light of the target, background removed | reflectivity of the target (fouling, ageing, flash), not ambient light; drops well before `error_value` exceeds its threshold |\n62\t| `sharpness` | `Σ(I²) / (ΣI)²` | concentration of the energy (higher = sharper) | drops: drifting focus, turbulence, degrading target. Independent of the gain, not of the background: follow it over time on one target, do not compare cameras |\n63\t| `fwhm` | width at half height around the peak, background removed [px] | width of the spot | rises: defocus, turbulence, motion blur. Truncated to the disc: under strong defocus it flattens instead of rising |\n64\t| `dominance` | `(second peak − background) / (peak − background)`, 0 (clean) toward 1 (ambiguous) | does a single spot dominate the window? | high: a comparable second reflection, a stray bright point, or the target has gone and something else is the brightest: the correlation can latch onto the wrong pattern, which `error_value` does not see. One hot pixel outside the disc is enough |\n65\t| `snr` | `(peak − background) / bg_sigma` | the signal above the background noise | low: marginal return, even when `peak` looks normal. Independent of exposure and gain. The emulator marks `empty` below 8 |\n66\t\n67\t`peak` and `flux` give the brightness, `sharpness` and `fwhm` the sharpness, `dominance` and `snr` the validity: together they say **why** a measurement degrades, where `error_value` only says that it does. They describe the image of **one target**, not the health of the reference network.\n68\t\n69\t## Camera images: IRON and DIFF\n70\t\n71\t- **IRON** (`images/`): the ordinary image of the scene, JPG. The cause of an event is seen on it (condensation, rain, train, snow).\n72\t- **DIFF** (`images_diff/`): several captures combined to raise the contrast of the reflectors; **the image the displacement algorithms measure**, by default. Not a difference between two instants. 16-bit PNG.\n73\t- Acquisition modes (station manual): \"Single with infrared light\", one image per measurement; \"Differential\", several combined (`Stacking` 20 to 40 when light is difficult); option \"Work on IRON images\", to follow a texture without reflector.\n74\t- Not every station has DIFF images; the pumping keeps about one image per hour. The tools look only at IRON images; `inventory.py` counts the DIFF ones, which your own scripts may read. What is very close to the lens (a web) may stand out better on DIFF.\n75\t"}]},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"587d1bd4-bfcc-4023-99b5-58ece2b6432a","timestamp":"2026-11-17T20:31:06.421Z","tool_use_result":{"type":"text","file":{"filePath":"/home/maxime/aimsight-app/tools/DATA.md","content":"# The data of a station\n\nWhat the files of a station folder are, and what each column means. How to read them with the tools: `GUIDE.md`. What they mean for a label (causes, reading rules, false friends): `labeling/reading-rules.md`. Maintained by hand; `GUIDE.md` is the tool-builder's.\n\n## The displacements: the \"advanced\" export\n\n`displacement/_advanced__.csv`, the source of the analyses: one row per sensor and per measurement, at the native rate of the station (10 or 15 min), `time_utc` in explicit UTC.\n\n| Column | Meaning |\n|---|---|\n| `sensor_name` | the sensor (target or reference) |\n| `pattern_type` | `global_ref`: a reference of the compensation; `ref`: a *local reference*, treated as a target, outside the compensation, without `reproj_err`; empty: a target |\n| `x`, `y` | raw position in the image [px]. Not the centroid of the spot: the offset centroid − (`x`, `y`) is constant per sensor by day and differs between sensors; it changes at night, when the spot is saturated. Probably the position of the reference pattern |\n| `relative_x`, `relative_y` | relative displacement before the camera compensation [px]; not `x − x0` |\n| `corr_x`, `corr_y` | the position of the target once the estimated camera movement is removed: **the curves that are labelled**. In px, not mm (below) |\n| `corr_x_mm`, `corr_y_mm` | `corr_x`, `corr_y` in mm: × the sensor's `mm_per_px` (`targets.csv`, below), computed by `data.load`; empty without a sure factor. The same curves in another unit: the noise threshold of a label is read in noises, whatever the unit; mm say how far a target moves, for the reader |\n| `error_value` | recognition error of the pattern, not an uncertainty |\n| `error_threshold` | specific to each sensor (0.3 to 0.7). Above it, the measurement is rejected: the row and its `error_value` stay, `corr_x` and `corr_y` are empty, not interpolated |\n| `reproj_err`, `inlier` | references only: residual and contribution of each reference in the compensation |\n| `sigma0` | residual of the fit on the references: one value per measurement, repeated on every row |\n| `peak`, `flux`, `sharpness`, `fwhm`, `dominance`, `snr` | image quality of each sensor, recent cameras only (below) |\n\n- \"Rejected\" is a judgment of the AIMsight platform, not of the camera: the camera delivers all its measurements, and a client's platform that integrates the data receives them all.\n- **Unit of `corr_x`, `corr_y`**: px. The hourly export's `horizontal_displacement` (mm) is a factor × the hourly mean of `corr_x` + a constant (likewise `vertical` and `corr_y`, correlation ≥ 0.99); the factor (mm per px) depends on the pattern and on the station.\n- **LENZSPITZE**: its export gives `x`, `y` relative to the pattern; the extraction rewrites them in image px and fills `pattern_type`. Sensors 1023 and 8019 have no pattern: their `x`, `y` are empty. The tools' crosses may sit slightly off the spots there.\n- `inventory.py` says, on a batch, which columns carry values.\n\n## The targets\n\n`targets.csv`, from the pumping: one line per sensor of the platform, `sensor_name`, `pattern_type`, `distance_mm` (from the camera) and `mm_per_px` (`distance_convertion_factor`, the factor of the dashboard's exports in mm), their current values. Read by `data.load_targets`, shown by `inventory.py` (sensor table).\n- The references are not in it yet (pumped from the next pumping on): no distance, no mm for them. They are assumed fixed.\n- `distance_mm` 1000: not filled in on the platform; the line is ignored.\n- A name may have several lines (a target counted twice, an older configuration of the unit, another lens): when they disagree, `data.load_targets` keeps no value (`inventory.py`: `?(n)`) and that target has no mm; the distance stays when the lines agree on it.\n- The distance says which targets are near and far. A far target moves few px for many mm: targets are compared with each other in mm, or in px with their distance. A camera that turns shifts every target by about the same px (the mm grow with the distance); a movement of the structure of the same mm gives px that shrink with the distance; a parallax shows between targets at different distances.\n\n## The camera pose\n\n`camera/_camera_.csv`, from the pumping only: the pose at each registration, `time_utc` in UTC, `median_|min_|max_` of `pan`, `tilt`, `rotation` [deg], `scale`, `sigma0`, one row per measurement (min = max). A measurement instant without a row: the camera was not registered.\n\n- Orders of magnitude: `pan`, `tilt` of a few hundredths of a degree, `scale` within 10⁻³ of 1; some stations show several degrees, not explained.\n- **A positive `tilt` means the camera is nosing down** (the expert).\n- Read by `overview.py` and `inventory.py`.\n\n## The weather\n\n`weather/_weather_.csv`, from the pumping, for a station with a Swiss position only: the hourly measurements of the nearest MeteoSwiss station, `time_utc` in UTC (start of the hour); `position`, `place`, `station`, `station_name`, `distance_km`, `height_m` say where; then `precipitation_mm`, `temperature_c`, `humidity_pct`, `wind_speed_kmh`, `wind_gust_kmh`, `wind_direction_deg`, `pressure_hpa`, `sunshine_min`, `global_radiation_wm2`, `snow_depth_cm` (empty: not measured there). The weather a few km away, not at the camera: what the images show prevails. Read by `data.load_weather`.\n\n## The hourly export\n\n`__to__1hour.csv`: one row per hour, targets only; per target `horizontal_displacement`, `vertical_displacement`, their `_min` / `_max`, `_error` (mean `error_value` of the hour), `_count_val` (measurements of the hour, rejected ones included).\n\n- **`timestamp` has no time zone: Swiss local time** (UTC+2 in summer), at the start of the hour.\n\n## Image quality of a target\n\nSix columns of the advanced export, computed by the GPU of recent cameras on the sensor's window in the DIFF image, in units of that image. Filled only where `inventory.py` says so (\"Export image quality\"); for older cameras, `~/optical_emulator` can recompute them from the DIFF images. \"Disc\": the neighbourhood of the peak, radius `min(H, W)/6` (at least 3 px); \"background\": the rest of the window.\n\n| Metric | Definition | What it measures | Reading |\n|---|---|---|---|\n| `peak` | `max(I)` | the brightness of the return | high, saturation; low, underexposure or missed flash. All targets dropping: the lighting; a single one: that target (fouling, misalignment) |\n| `flux` | flux of the disc minus the background | the light of the target, background removed | reflectivity of the target (fouling, ageing, flash), not ambient light; drops well before `error_value` exceeds its threshold |\n| `sharpness` | `Σ(I²) / (ΣI)²` | concentration of the energy (higher = sharper) | drops: drifting focus, turbulence, degrading target. Independent of the gain, not of the background: follow it over time on one target, do not compare cameras |\n| `fwhm` | width at half height around the peak, background removed [px] | width of the spot | rises: defocus, turbulence, motion blur. Truncated to the disc: under strong defocus it flattens instead of rising |\n| `dominance` | `(second peak − background) / (peak − background)`, 0 (clean) toward 1 (ambiguous) | does a single spot dominate the window? | high: a comparable second reflection, a stray bright point, or the target has gone and something else is the brightest: the correlation can latch onto the wrong pattern, which `error_value` does not see. One hot pixel outside the disc is enough |\n| `snr` | `(peak − background) / bg_sigma` | the signal above the background noise | low: marginal return, even when `peak` looks normal. Independent of exposure and gain. The emulator marks `empty` below 8 |\n\n`peak` and `flux` give the brightness, `sharpness` and `fwhm` the sharpness, `dominance` and `snr` the validity: together they say **why** a measurement degrades, where `error_value` only says that it does. They describe the image of **one target**, not the health of the reference network.\n\n## Camera images: IRON and DIFF\n\n- **IRON** (`images/`): the ordinary image of the scene, JPG. The cause of an event is seen on it (condensation, rain, train, snow).\n- **DIFF** (`images_diff/`): several captures combined to raise the contrast of the reflectors; **the image the displacement algorithms measure**, by default. Not a difference between two instants. 16-bit PNG.\n- Acquisition modes (station manual): \"Single with infrared light\", one image per measurement; \"Differential\", several combined (`Stacking` 20 to 40 when light is difficult); option \"Work on IRON images\", to follow a texture without reflector.\n- Not every station has DIFF images; the pumping keeps about one image per hour. The tools look only at IRON images; `inventory.py` counts the DIFF ones, which your own scripts may read. What is very close to the lens (a web) may stand out better on DIFF.\n","numLines":75,"startLine":1,"totalLines":75}},"tool_result_meta":[{"id":"toolu_01Sm3RseXnHDTBJyNTT6MFsq","permission_decision":{"decision":"accept","source":"config","reason_type":"rule"}}]}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98n3RGUXfNwFvkqgaDt","type":"message","role":"assistant","content":[{"type":"tool_use","id":"toolu_01VAjupnTTS1MbGejN81sWmh","name":"Read","input":{"file_path":"/home/maxime/aimsight-app/labeling/labeling-rules.md"},"caller":{"type":"direct"}}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":524,"cache_read_input_tokens":10876,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":524},"output_tokens":16,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"4ef69944-caef-46cc-a989-d6ecf1811705","timestamp":"2026-11-17T20:31:06.906Z","request_id":"req_011Ch98n3C8UGUW8Q6NtwAzR","wire_tool_inputs":{"toolu_01VAjupnTTS1MbGejN81sWmh":{"file_path":"/home/maxime/aimsight-app/labeling/labeling-rules.md"}}}
-{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_01VAjupnTTS1MbGejN81sWmh","type":"tool_result","content":"1\t# The labeling rules\n2\t\n3\tHow to place a label: the only source of these rules for the aimsight-app `analyst` (before it, the Support-Agent `etiqueteur`) and for those who review their labels. The families, their boundaries and the catalogue of phenomena are in `families.md`; what the data mean, in `reading-rules.md`.\n4\t\n5\tSources in brackets: [instruction] the section \"Les étiquettes\" of `.claude/agents/etiqueteur.md`; [cross ] the cross review of 2026-11-04, `auto/revue-croisee/2026-11-04//revue.md`; [finishing ] its finishing pass, `auto/revue-croisee/2026-11-04/finition//revue.md`; [] the station review, `auto/revue/_/revue.md`; [consistency] that of BREITHORN, MICHIGAN and NEBRASKA; [expert] a label or an answer of the expert.\n6\t\n7\t## 1. What is labeled\n8\t\n9\t- **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]\n10\t- **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]\n11\t- **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]\n12\t- **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]\n13\t- **\"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]\n14\t- **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]\n15\t- **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]\n16\t- **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]\n17\t\n18\t## 2. The bounds\n19\t\n20\t- **`start` is the measurement just before the first touched point, `end` the measurement just after the last, never `start` = `end`**: a touched point moves or is missing; an anomaly of a single measurement goes from the point before to the point after (a passage at 11:00, 15 min rate: 10:45 → 11:15). [instruction, WILDSTRUBEL]\n21\t- **The bounds are measurement instants, at the minute of the measurement**: at a 15 min rate, it is the quarter hour; at 10 min or 5 min, the minute of the measurement, like the expert's label. [cross Obstruction, CLARIDEN, expert]\n22\t- **The bounds are read on the curves, not on the rejections**: a reference that drifts before being rejected, a target that comes back after the last rejection are touched; read the two or three measurements before the first rejection (the `error_value` of a reference and the pose often already move there), and, for a loss of references at night, the `corr_x` of the targets and of the neighboring references. [cross Visibility, FLORIDA, LENZSPITZE]\n23\t- **Each edge is checked sensor by sensor, in both columns, not on the median**: all sensors, not only those named; a `corr_x` peak can touch `corr_y` longer. [instruction, NORDEND, NEBRASKA, MICHIGAN]\n24\t- **A measurement that has come back halfway is still touched; one more measurement, already back, is too many**: read the value of the next step before closing, without rounding inward or outward. [instruction, BREITHORN, JUNGFRAU, CLARIDEN]\n25\t- **A range of rejections ends at the measurement following the last rejection of all touched targets**: the first rejected measurement is not the start either. [instruction, BREITHORN, NIEDERHORN, SNCF01]\n26\t- **A reference rejected at a bound counts as a touched point, unless it is rejected there as usual**: its usual rejections (by day, in the morning, a Target issue target) do not move the bound. [cross Obstruction, CLARIDEN]\n27\t- **At the edge of a gap, the bound is the first measurement after the gap, or the last before**: an event that starts at the resumption starts at that measurement, which is also the `end` of the No data; a single measurement inside an outage is bounded one rate step on either side. [cross Obstruction, WILDSTRUBEL, JUNGFRAU]\n28\t- **Before writing, a script checks the bounds**: `start` < `end`, they are measurement instants, and no sensor is touched there outside its usual rejections, references included. [cross Obstruction, WILDSTRUBEL]\n29\t- **The end of a nuisance specific to a target is read on its `corr_x` and `corr_y`, against its level before, over several nights**: not on the return of its `error_value`; without a return, the label runs to the end of the batch; without a level before, it ends where the curves stop changing. [cross Target issue, NORDEND]\n30\t- **A return ends where the curve stops coming back**: not at midnight; a plateau is not a return. [LENZSPITZE]\n31\t- **A label goes to the end of the batch only if points are still missing or moving there**: otherwise it ends at the return. [cross Displacement]\n32\t- **A lasting jump is bounded on the jump**: from the measurement before to the measurement after the one where the new level is reached; hidden in an outage, on the outage and the first measurement after; hidden under another label, at the first measurements where it is seen. [cross Displacement, expert]\n33\t- **The bounds of a thermal cycle are read day by day, on the turning points of the pose and of the `corr`**: never at midnight or at a fixed hour, except at the start and the end of the batch; when the pose is noisy, on its hourly median. [cross Thermal displacement, FLORIDA, SNCF01]\n34\t- **The camera cycle starts at the morning turning point**: the first instant when the tilt and the pan leave their end-of-night level without coming back, the later of the two; not the fast part of the movement, nor the first deviation of `days.py --bounds`; a deviation of a single rate step from the bound placed stays within the uncertainty. [cross Thermal displacement, NORDEND, finishing nordend]\n35\t- **It ends at the later of the two returns, the pose on its main axes and the curves at their night level**: an axis returns to the level where it then stays, not under a threshold set on the night, which may differ; the slow relaxation of a secondary axis (often the scale) does not push the end back, as in the expert's labels; without rest, the cycle ends at the next start and the labels follow one another. [cross Thermal displacement, NORDEND, WILDSTRUBEL, expert, finishing niederhorn, finishing wildstrubel]\n36\t- **A nuisance at night stops the cycle only if it distorts the pose**: a reference rejected, discarded, or that drifts against the targets (`overview.py --rigid`); a target bothered alone does not stop it. [finishing divers, finishing nordend]\n37\t- **A gap does not cut a cycle visible on both sides** (so the gaps of one or two measurements); otherwise, a gap or a jump at night stops it: the cycle ends at the rest of the pose if it comes before, otherwise at the last measurement before the gap or at the measurement before the jump. [finishing divers, finishing nordend]\n38\t- **Before extending a cycle over a night that moves, read the housing temperature and the references**: it must still drop there, or the pose follow its usual profile; a pose that moves at flat temperature, with a reference that drifts, is the nuisance of that reference, not the thermal return. [finishing divers]\n39\t- **The reference night of a cycle is chosen calm, not by civil day**: when the pose comes back all night, a start is dated at the turning point, not at the first deviation from that night. [SNCF01, cross Thermal displacement]\n40\t- **The phases of the structure are cut at the turning points**: when the trough is flat for several hours, the cut is placed in the flat and the two phases touch. [JUNGFRAU, cross Thermal displacement]\n41\t- **An event that touches the edge of the batch extends the label of the neighboring batch, if there is one**: it is not redone; otherwise, it starts or ends at the batch edge. [JUNGFRAU, cross Target issue]\n42\t\n43\t## 3. A single event\n44\t\n45\t- **One label, a single event**: two events, even close or mixed, make two labels; an event that repeats (a passage, the rain of each night, the thermal cycle of each day) makes one label each time. [instruction]\n46\t- **The outward and return of a drift are two labels**: after each slow drift, look for its return, and do not join a descent and its rise because the description says so. [instruction, CLARIDEN, cross Displacement]\n47\t- **The thermal cycle of the camera, outward and return, is a single event per day; the structure makes two, the expansion and the contraction**: this is what the expert does; the outward-and-return rule does not apply to the camera cycle. [cross Thermal displacement, expert]\n48\t- **An event in one piece over several days makes one label**: a change of speed does not cut it, nor a tilt that continues in the same direction; only a stop followed by a return, or a change of direction, cuts it. [instruction, BREITHORN, cross Displacement]\n49\t- **A return that exceeds the starting level remains the same event**: it does not start a new movement. [LENZSPITZE]\n50\t- **A lasting jump: the label bounds the jump, the return is another label**: the step is stated in the description; a step that returns within the day remains one label (a jump then the return); two steps separated by days of plateau make two labels, even in the same direction. [cross Displacement]\n51\t- **A bump that is only the trace of a slow camera movement follows the cutting of that movement**: it is not a separate event. [cross Displacement]\n52\t- **Two gaps separated by a single measurement that came back make a single No data label; separated by two measurements or more, two**: a single measurement does not make a resumption. [cross No data, SNCF01]\n53\t- **A measurement where a target is rejected alone just after a passage is the same event; a clean measurement between the two makes two labels**: the rejection that follows is the end of the passage. [cross Obstruction]\n54\t- **Two nuisance episodes separated by a few hours where targets stay shifted make only one**: the shifted targets are still touched. [NORDEND]\n55\t- **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]\n56\t- **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]\n57\t- **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]\n58\t- **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]\n59\t- **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]\n60\t\n61\t## 4. The family\n62\t\n63\t- **A single family per label, its key in `families.md`, following its boundaries**: `Visibility`, `Obstruction`, `Thermal displacement`, `Displacement`, `Target issue`, `No data`; no other key, nor old names. [instruction, MICHIGAN, WILDSTRUBEL]\n64\t- **We decide by the signature, not by coincidence**: a temperature drop at the same moment does not make a thermal, an `error_value` that moves a little does not make a Visibility. [cross Thermal displacement, cross Visibility]\n65\t- **A same target keeps the same family from one batch to the next, and a same phenomenon on neighboring stations the same family**: otherwise the defect of a target or a site reads as two causes. [NORDEND, consistency]\n66\t- **The sun at sunrise in the field and the lit background behind a spot are the same nuisance**: same family, same way of stating the cause. [cross Visibility]\n67\t\n68\t## 5. The description\n69\t\n70\t- **As the expert would write it, in English: what is seen, the cause and how it was known, the conclusion for the client**: which targets or references with their exact names, which magnitudes, the return or not; then nothing to do, data not to be believed, or movement to monitor. [instruction]\n71\t- **Qualitative, without numeric values, even in words**: \"a tenth\", \"half a pixel\", \"a few hundredths\", \"up to almost 1\" are numbers; say \"a little\", \"clearly\", \"strongly\". [instruction, FLORIDA, JUNGFRAU]\n72\t- **The targets named are those that move the most, read instant by instant, in the right column**: not the usual list; a rejected target does not \"jump\"; the direction is stated as it is that day. [instruction, CLARIDEN, NEBRASKA, FLORIDA, NIEDERHORN]\n73\t- **A sentence taken from a model is reread on the range of each label**: the hours, the weather, the targets, the image, the return, the overshoot; a precision true for a single label is not copied. [cross Visibility, cross Thermal displacement, SNCF01, LENZSPITZE, NORDEND, FLORIDA]\n74\t- **\"Nothing on the images\", \"image without obstacle\" are written only after looking at the image of the hour**: a passage is often seen in transparency; the image cited is that of the day when it exists. [instruction, CLARIDEN, MICHIGAN, FLORIDA, WILDSTRUBEL, cross Visibility, JUNGFRAU]\n75\t- **\"No image\" is written only at an instant when the camera usually takes an image, and after searching for the file**: a station that takes one only on the hour proves nothing at the half hour, and the hourly images often fall on the minute of the measurements. [cross No data, LENZSPITZE]\n76\t- **A fact given by the expert is written \"according to the expert\", in words, without his numbers**: not \"the map knows\". [instruction, BREITHORN, MICHIGAN, NIEDERHORN]\n77\t- **The temperature is \"the housing temperature\" (of the camera)**: the column being either `sensor_*_deg_c`, or, failing that, `temperature_deg_c`; never of the air, the building, the plant, the station, the components, the camera alone, nor the name of the column; without any metric, \"no temperature is available\". [instruction, cross Thermal displacement, LENZSPITZE, NORDEND, JUNGFRAU, consistency]\n78\t- **The weather is not drawn from the housing temperature**: \"cold and overcast day\" is seen on the images. [FLORIDA]\n79\t- **The moments of the day (morning, late afternoon, night) are judged on the images, never on the UTC hour**: the station can be anywhere. Every hour written is in UTC, no numeric local hour. [cross Visibility, label map, expert's reading rule]\n80\t- **A level \"back\" or \"a little below\" is compared over several days**: a single day after may be in the middle of a thermal cycle; a night level that changes from one night to another is compared with several nights; a target rejected at night, with the nearest neighboring night where it is measured, never across a step. [instruction, MICHIGAN, cross Visibility, WILDSTRUBEL, finishing niederhorn]\n81\t- **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]\n82\t- **\"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]\n83\t- **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]\n84\t- **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]\n85\t- **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]\n86\t- **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]\n87\t- **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]\n88\t- **A lasting jump states its step**: its duration, its return or not. [cross Displacement]\n89\t- **Each label of a sequence (outward, return, resumption) names the other**: \"return of the drift of…, labeled apart\", \"without return until the end of the batch\". [cross Displacement]\n90\t- **A Target issue says when the rejections stop before the end of the label**: the end is read on the curves, the rejections may stop before. [cross Target issue]\n91\t- **A No data states the metrics and the image of the instant**: present or not, checked, for each gap. [NIEDERHORN, cross No data]\n92\t\n93\t- **On a recent camera (image quality filled, `tools/scripts/quality.py`), an occultation is written only after reading the flux of the instant**: a cut flux proves it, a full flux denies it; the hidden targets are named from their flux, each time, and a hidden target that stayed under its threshold is stated (its point stays, wrong). The metrics: `tools/DATA.md`. [LENZSPITZE quality review, D-129]\n94\t- **\"Bigger spots\" is written only after comparison with a calm day of the same image regime and reading of the `fwhm`**: a spot that has lost its light can look swollen. [LENZSPITZE quality review, D-129]\n95\t- **A jump without rejection is in no list of rejections**: on a recent camera, `quality.py --labels --outside` gives the degraded instants outside the labels; `corr` is checked at each. [LENZSPITZE quality review, D-129]\n96\t\n97\t## 6. The stated cause\n98\t\n99\t- **A cause is stated in three ways only: seen, deduced, not established**: \"seen on the image (or the thumbnail) of HH:MM\", saying what is seen there; \"deduced from…\" (the signature, the other passages seen, the curves and the camera pose), saying why it is not seen; \"not established\", with its hypotheses; or \"according to the expert\". [instruction, cross Obstruction, cross Displacement]\n100\t- **A cause deduced from a known signature is stated \"deduced\", not \"not established\" followed by hypotheses**: the signature is a proof. [cross Visibility]\n101\t- **\"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]\n102\t- **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]\n103\t- **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]\n104\t- **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]\n105\t- **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]\n106\t\n107\tThe boundaries between families, and what is not labeled: `families.md`.\n108\t"}]},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"93075ea3-d90b-4c6b-aa7d-a36a300e57a7","timestamp":"2026-11-17T20:31:06.941Z","tool_use_result":{"type":"text","file":{"filePath":"/home/maxime/aimsight-app/labeling/labeling-rules.md","content":"# The labeling rules\n\nHow to place a label: the only source of these rules for the aimsight-app `analyst` (before it, the Support-Agent `etiqueteur`) and for those who review their labels. The families, their boundaries and the catalogue of phenomena are in `families.md`; what the data mean, in `reading-rules.md`.\n\nSources in brackets: [instruction] the section \"Les étiquettes\" of `.claude/agents/etiqueteur.md`; [cross ] the cross review of 2026-11-04, `auto/revue-croisee/2026-11-04//revue.md`; [finishing ] its finishing pass, `auto/revue-croisee/2026-11-04/finition//revue.md`; [] the station review, `auto/revue/_/revue.md`; [consistency] that of BREITHORN, MICHIGAN and NEBRASKA; [expert] a label or an answer of the expert.\n\n## 1. What is labeled\n\n- **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]\n- **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]\n- **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]\n- **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]\n- **\"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]\n- **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]\n- **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]\n- **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]\n\n## 2. The bounds\n\n- **`start` is the measurement just before the first touched point, `end` the measurement just after the last, never `start` = `end`**: a touched point moves or is missing; an anomaly of a single measurement goes from the point before to the point after (a passage at 11:00, 15 min rate: 10:45 → 11:15). [instruction, WILDSTRUBEL]\n- **The bounds are measurement instants, at the minute of the measurement**: at a 15 min rate, it is the quarter hour; at 10 min or 5 min, the minute of the measurement, like the expert's label. [cross Obstruction, CLARIDEN, expert]\n- **The bounds are read on the curves, not on the rejections**: a reference that drifts before being rejected, a target that comes back after the last rejection are touched; read the two or three measurements before the first rejection (the `error_value` of a reference and the pose often already move there), and, for a loss of references at night, the `corr_x` of the targets and of the neighboring references. [cross Visibility, FLORIDA, LENZSPITZE]\n- **Each edge is checked sensor by sensor, in both columns, not on the median**: all sensors, not only those named; a `corr_x` peak can touch `corr_y` longer. [instruction, NORDEND, NEBRASKA, MICHIGAN]\n- **A measurement that has come back halfway is still touched; one more measurement, already back, is too many**: read the value of the next step before closing, without rounding inward or outward. [instruction, BREITHORN, JUNGFRAU, CLARIDEN]\n- **A range of rejections ends at the measurement following the last rejection of all touched targets**: the first rejected measurement is not the start either. [instruction, BREITHORN, NIEDERHORN, SNCF01]\n- **A reference rejected at a bound counts as a touched point, unless it is rejected there as usual**: its usual rejections (by day, in the morning, a Target issue target) do not move the bound. [cross Obstruction, CLARIDEN]\n- **At the edge of a gap, the bound is the first measurement after the gap, or the last before**: an event that starts at the resumption starts at that measurement, which is also the `end` of the No data; a single measurement inside an outage is bounded one rate step on either side. [cross Obstruction, WILDSTRUBEL, JUNGFRAU]\n- **Before writing, a script checks the bounds**: `start` < `end`, they are measurement instants, and no sensor is touched there outside its usual rejections, references included. [cross Obstruction, WILDSTRUBEL]\n- **The end of a nuisance specific to a target is read on its `corr_x` and `corr_y`, against its level before, over several nights**: not on the return of its `error_value`; without a return, the label runs to the end of the batch; without a level before, it ends where the curves stop changing. [cross Target issue, NORDEND]\n- **A return ends where the curve stops coming back**: not at midnight; a plateau is not a return. [LENZSPITZE]\n- **A label goes to the end of the batch only if points are still missing or moving there**: otherwise it ends at the return. [cross Displacement]\n- **A lasting jump is bounded on the jump**: from the measurement before to the measurement after the one where the new level is reached; hidden in an outage, on the outage and the first measurement after; hidden under another label, at the first measurements where it is seen. [cross Displacement, expert]\n- **The bounds of a thermal cycle are read day by day, on the turning points of the pose and of the `corr`**: never at midnight or at a fixed hour, except at the start and the end of the batch; when the pose is noisy, on its hourly median. [cross Thermal displacement, FLORIDA, SNCF01]\n- **The camera cycle starts at the morning turning point**: the first instant when the tilt and the pan leave their end-of-night level without coming back, the later of the two; not the fast part of the movement, nor the first deviation of `days.py --bounds`; a deviation of a single rate step from the bound placed stays within the uncertainty. [cross Thermal displacement, NORDEND, finishing nordend]\n- **It ends at the later of the two returns, the pose on its main axes and the curves at their night level**: an axis returns to the level where it then stays, not under a threshold set on the night, which may differ; the slow relaxation of a secondary axis (often the scale) does not push the end back, as in the expert's labels; without rest, the cycle ends at the next start and the labels follow one another. [cross Thermal displacement, NORDEND, WILDSTRUBEL, expert, finishing niederhorn, finishing wildstrubel]\n- **A nuisance at night stops the cycle only if it distorts the pose**: a reference rejected, discarded, or that drifts against the targets (`overview.py --rigid`); a target bothered alone does not stop it. [finishing divers, finishing nordend]\n- **A gap does not cut a cycle visible on both sides** (so the gaps of one or two measurements); otherwise, a gap or a jump at night stops it: the cycle ends at the rest of the pose if it comes before, otherwise at the last measurement before the gap or at the measurement before the jump. [finishing divers, finishing nordend]\n- **Before extending a cycle over a night that moves, read the housing temperature and the references**: it must still drop there, or the pose follow its usual profile; a pose that moves at flat temperature, with a reference that drifts, is the nuisance of that reference, not the thermal return. [finishing divers]\n- **The reference night of a cycle is chosen calm, not by civil day**: when the pose comes back all night, a start is dated at the turning point, not at the first deviation from that night. [SNCF01, cross Thermal displacement]\n- **The phases of the structure are cut at the turning points**: when the trough is flat for several hours, the cut is placed in the flat and the two phases touch. [JUNGFRAU, cross Thermal displacement]\n- **An event that touches the edge of the batch extends the label of the neighboring batch, if there is one**: it is not redone; otherwise, it starts or ends at the batch edge. [JUNGFRAU, cross Target issue]\n\n## 3. A single event\n\n- **One label, a single event**: two events, even close or mixed, make two labels; an event that repeats (a passage, the rain of each night, the thermal cycle of each day) makes one label each time. [instruction]\n- **The outward and return of a drift are two labels**: after each slow drift, look for its return, and do not join a descent and its rise because the description says so. [instruction, CLARIDEN, cross Displacement]\n- **The thermal cycle of the camera, outward and return, is a single event per day; the structure makes two, the expansion and the contraction**: this is what the expert does; the outward-and-return rule does not apply to the camera cycle. [cross Thermal displacement, expert]\n- **An event in one piece over several days makes one label**: a change of speed does not cut it, nor a tilt that continues in the same direction; only a stop followed by a return, or a change of direction, cuts it. [instruction, BREITHORN, cross Displacement]\n- **A return that exceeds the starting level remains the same event**: it does not start a new movement. [LENZSPITZE]\n- **A lasting jump: the label bounds the jump, the return is another label**: the step is stated in the description; a step that returns within the day remains one label (a jump then the return); two steps separated by days of plateau make two labels, even in the same direction. [cross Displacement]\n- **A bump that is only the trace of a slow camera movement follows the cutting of that movement**: it is not a separate event. [cross Displacement]\n- **Two gaps separated by a single measurement that came back make a single No data label; separated by two measurements or more, two**: a single measurement does not make a resumption. [cross No data, SNCF01]\n- **A measurement where a target is rejected alone just after a passage is the same event; a clean measurement between the two makes two labels**: the rejection that follows is the end of the passage. [cross Obstruction]\n- **Two nuisance episodes separated by a few hours where targets stay shifted make only one**: the shifted targets are still touched. [NORDEND]\n- **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]\n- **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]\n- **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]\n- **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]\n- **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]\n\n## 4. The family\n\n- **A single family per label, its key in `families.md`, following its boundaries**: `Visibility`, `Obstruction`, `Thermal displacement`, `Displacement`, `Target issue`, `No data`; no other key, nor old names. [instruction, MICHIGAN, WILDSTRUBEL]\n- **We decide by the signature, not by coincidence**: a temperature drop at the same moment does not make a thermal, an `error_value` that moves a little does not make a Visibility. [cross Thermal displacement, cross Visibility]\n- **A same target keeps the same family from one batch to the next, and a same phenomenon on neighboring stations the same family**: otherwise the defect of a target or a site reads as two causes. [NORDEND, consistency]\n- **The sun at sunrise in the field and the lit background behind a spot are the same nuisance**: same family, same way of stating the cause. [cross Visibility]\n\n## 5. The description\n\n- **As the expert would write it, in English: what is seen, the cause and how it was known, the conclusion for the client**: which targets or references with their exact names, which magnitudes, the return or not; then nothing to do, data not to be believed, or movement to monitor. [instruction]\n- **Qualitative, without numeric values, even in words**: \"a tenth\", \"half a pixel\", \"a few hundredths\", \"up to almost 1\" are numbers; say \"a little\", \"clearly\", \"strongly\". [instruction, FLORIDA, JUNGFRAU]\n- **The targets named are those that move the most, read instant by instant, in the right column**: not the usual list; a rejected target does not \"jump\"; the direction is stated as it is that day. [instruction, CLARIDEN, NEBRASKA, FLORIDA, NIEDERHORN]\n- **A sentence taken from a model is reread on the range of each label**: the hours, the weather, the targets, the image, the return, the overshoot; a precision true for a single label is not copied. [cross Visibility, cross Thermal displacement, SNCF01, LENZSPITZE, NORDEND, FLORIDA]\n- **\"Nothing on the images\", \"image without obstacle\" are written only after looking at the image of the hour**: a passage is often seen in transparency; the image cited is that of the day when it exists. [instruction, CLARIDEN, MICHIGAN, FLORIDA, WILDSTRUBEL, cross Visibility, JUNGFRAU]\n- **\"No image\" is written only at an instant when the camera usually takes an image, and after searching for the file**: a station that takes one only on the hour proves nothing at the half hour, and the hourly images often fall on the minute of the measurements. [cross No data, LENZSPITZE]\n- **A fact given by the expert is written \"according to the expert\", in words, without his numbers**: not \"the map knows\". [instruction, BREITHORN, MICHIGAN, NIEDERHORN]\n- **The temperature is \"the housing temperature\" (of the camera)**: the column being either `sensor_*_deg_c`, or, failing that, `temperature_deg_c`; never of the air, the building, the plant, the station, the components, the camera alone, nor the name of the column; without any metric, \"no temperature is available\". [instruction, cross Thermal displacement, LENZSPITZE, NORDEND, JUNGFRAU, consistency]\n- **The weather is not drawn from the housing temperature**: \"cold and overcast day\" is seen on the images. [FLORIDA]\n- **The moments of the day (morning, late afternoon, night) are judged on the images, never on the UTC hour**: the station can be anywhere. Every hour written is in UTC, no numeric local hour. [cross Visibility, label map, expert's reading rule]\n- **A level \"back\" or \"a little below\" is compared over several days**: a single day after may be in the middle of a thermal cycle; a night level that changes from one night to another is compared with several nights; a target rejected at night, with the nearest neighboring night where it is measured, never across a step. [instruction, MICHIGAN, cross Visibility, WILDSTRUBEL, finishing niederhorn]\n- **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]\n- **\"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]\n- **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]\n- **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]\n- **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]\n- **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]\n- **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]\n- **A lasting jump states its step**: its duration, its return or not. [cross Displacement]\n- **Each label of a sequence (outward, return, resumption) names the other**: \"return of the drift of…, labeled apart\", \"without return until the end of the batch\". [cross Displacement]\n- **A Target issue says when the rejections stop before the end of the label**: the end is read on the curves, the rejections may stop before. [cross Target issue]\n- **A No data states the metrics and the image of the instant**: present or not, checked, for each gap. [NIEDERHORN, cross No data]\n\n- **On a recent camera (image quality filled, `tools/scripts/quality.py`), an occultation is written only after reading the flux of the instant**: a cut flux proves it, a full flux denies it; the hidden targets are named from their flux, each time, and a hidden target that stayed under its threshold is stated (its point stays, wrong). The metrics: `tools/DATA.md`. [LENZSPITZE quality review, D-129]\n- **\"Bigger spots\" is written only after comparison with a calm day of the same image regime and reading of the `fwhm`**: a spot that has lost its light can look swollen. [LENZSPITZE quality review, D-129]\n- **A jump without rejection is in no list of rejections**: on a recent camera, `quality.py --labels --outside` gives the degraded instants outside the labels; `corr` is checked at each. [LENZSPITZE quality review, D-129]\n\n## 6. The stated cause\n\n- **A cause is stated in three ways only: seen, deduced, not established**: \"seen on the image (or the thumbnail) of HH:MM\", saying what is seen there; \"deduced from…\" (the signature, the other passages seen, the curves and the camera pose), saying why it is not seen; \"not established\", with its hypotheses; or \"according to the expert\". [instruction, cross Obstruction, cross Displacement]\n- **A cause deduced from a known signature is stated \"deduced\", not \"not established\" followed by hypotheses**: the signature is a proof. [cross Visibility]\n- **\"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]\n- **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]\n- **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]\n- **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]\n- **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]\n\nThe boundaries between families, and what is not labeled: `families.md`.\n","numLines":108,"startLine":1,"totalLines":108}},"tool_result_meta":[{"id":"toolu_01VAjupnTTS1MbGejN81sWmh","permission_decision":{"decision":"accept","source":"config","reason_type":"rule"}}]}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98n3RGUXfNwFvkqgaDt","type":"message","role":"assistant","content":[{"type":"tool_use","id":"toolu_01KbsyhP8CZpRaPgCJsyBpbL","name":"Read","input":{"file_path":"/home/maxime/aimsight-app/labeling/families.md"},"caller":{"type":"direct"}}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":524,"cache_read_input_tokens":10876,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":524},"output_tokens":16,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"73303608-6ec7-4dab-bedf-b269b50e53b7","timestamp":"2026-11-17T20:31:07.244Z","request_id":"req_011Ch98n3C8UGUW8Q6NtwAzR","wire_tool_inputs":{"toolu_01KbsyhP8CZpRaPgCJsyBpbL":{"file_path":"/home/maxime/aimsight-app/labeling/families.md"}}}
-{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_01KbsyhP8CZpRaPgCJsyBpbL","type":"tool_result","content":"1\t# The label families\n2\t\n3\tOne 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.\n4\t\n5\t| Key | Detector | What happens | For the client |\n6\t|---|---|---|---|\n7\t| `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 |\n8\t| `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 |\n9\t| `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 |\n10\t| `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 |\n11\t| `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 |\n12\t| `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 |\n13\t\n14\tFor 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:\n15\t\n16\t| Variety | For the client |\n17\t|---|---|\n18\t| `Poor visibility reduced` | use the data over the range with care: they are less precise |\n19\t| `Heat shimmer` | nothing to do: the small fast wiggles are not movement |\n20\t| `Camera thermal movement` | nothing to do: this is not a movement of the structure |\n21\t| `Brief obstruction` | ignore this single point on the curves |\n22\t| `Sudden jump, back to normal` | look at the images: the cause is not established |\n23\t| `Lasting shift` | check whether the structure moved: look at the images |\n24\t| `Jump, not back yet` | check whether the structure moved: look at the images |\n25\t| `Slow drift` | keep watching it |\n26\t\n27\t## The boundaries\n28\t\n29\t- **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.\n30\t- **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.\n31\t- **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 Displacement without a cause. The description says it is a reference, and that the targets move together because of it.\n32\t- **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.\n33\t- **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.\n34\t- **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.\n35\t- **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.\n36\t- **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.\n37\t- **Target issue or Displacement**: a changed configuration (moved sensors, changed starting position, setting) is Target issue; the jump that results is not a Displacement.\n38\t\n39\t## The phenomena\n40\t\n41\tWhat has been labelled so far, one line each: **name**: what is seen; how to tell it from its neighbours. The hypotheses to weigh for a moment of a range; the cases, their bounds and descriptions come from the labels, through `precedents.py`. A phenomenon not in this list is labelled too, without forcing a cause.\n42\t\n43\t### No data\n44\t- **A gap common to several stations**: the measurements missing at the same minutes on every station measuring then; a cause outside the stations, not established. Read the other stations before the station's metrics.\n45\t- **The station runs, the measurement is missing**: one station, powered and communicating (synchronization, image or `DB_not_uploaded` at the missing instant), misses a measurement.\n46\t- **The station goes silent on its own, for a long time**: no measurements, no images, no metrics, for hours or days, without the signature of a lack of energy.\n47\t- **The station shuts down for lack of energy**: the battery does not last the night; voltage below the knee before the gap, a restart with the solar charge.\n48\t- **Mains cut: the station runs on its battery**: a station on mains stops, or comes back on a drawn-down battery, until the mains return.\n49\t\n50\t### Obstruction\n51\t- **A pass-by hides the targets for the length of one measurement**: a train, a vehicle, passers-by: the hidden targets rejected for one acquisition, back at the next; a reference behind it makes the whole base jump. Insects give the same signature: only the image tells.\n52\t- **A target left under the threshold latches onto a headlight, a reflection or another spot**: during a pass-by, one false point kept in the curve, without rejection; `dominance` rises on a recent camera.\n53\t- **A vehicle or machine that stays in front of the targets**: the same sensors hidden for hours or days, sometimes a reference; one label per parking.\n54\t- **An animal very close to the lens**: lit at night, it hides part or all of the scene for one or two measurements; a spider is not its web.\n55\t- **A plant shaken by the wind in front of a target**: one target, at times, on windy days; it grows over weeks.\n56\t- **An obstacle covers part of the spot**: an obstacle, or a mark on the glass in front of one spot, hides part of it for hours or weeks: the measured centre slides; the sliding is the artifact, the jump back is the return to normal.\n57\t\n58\t### Visibility\n59\t- **Rain**: drops in front of the lens veil the spots during the hours of rain, at night above all; the references, higher up, may suffer less.\n60\t- **The soiled glass**: after rain, drop marks veil part of the scene durably; under a single spot, it is an obstacle (Obstruction).\n61\t- **Visibility drops over the whole scene, without an obstacle**: fog, condensation, a milky dawn: flux down on all sensors, `error_value` up, rejections; raw positions without a step.\n62\t- **Part of the scene goes dark at night**: the distant spots, or a few neighbours at the edge of the group, lose their light, nothing in front.\n63\t- **A reference loses its brightness, without an obstacle**: one or two references weaken and shrink, most often at night, then come back on their own; the centre does not move.\n64\t- **Atmospheric turbulence**: by day, air heated above a road, ballast or rails makes the spots tremble: a fast noise, `error_value` up. Without the `error_value` rising, an agitation of the pose is the camera heating (Thermal displacement).\n65\t- **The sun in the field or behind a spot**: the sun enters the field, or lights the background of a target or a reference as bright as it: rejections at the same hours on sunny days only.\n66\t- **A faint spot lost when the light is missing**: a faint target crosses its threshold at the change from night to day, under an overcast sky or in a noisy night image; its rejections come with the light, not every day (else Target issue).\n67\t\n68\t### Target issue\n69\t- **A target rejected at all its measurements**: never accepted, whatever the weather.\n70\t- **A target right at the threshold, the whole batch**: its `error_value` keeps crossing the threshold, with many own rejections.\n71\t- **A target rejected every night or every day**: under the station's ordinary regime (floodlight, daylight), at the same hours, whatever the weather.\n72\t- **A target that degrades, and sometimes recovers**: seen worse and worse from a date on; back only after weeks, if ever, often at another level.\n73\t- **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.\n74\t\n75\t### Thermal displacement\n76\t- **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.\n77\t- **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.\n78\t- **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.\n79\t- **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).\n80\t\n81\t### Displacement\n82\t- **A step of the camera that the compensation does not erase**: the camera moves at once and a remainder passes into the curves; a step that leaves nothing beyond the noise is not labelled.\n83\t- **The camera tilts little by little**: over weeks, the tilt rises and the compensation corrects some targets better than others; the targets do not move relative to each other.\n84\t- **The base changes without a reference lost**: all references kept, the distance between them changes a little; all targets shift together without moving in the image.\n85\t- **A real movement of the structure**: targets shift and stay, with references and pose stable and a good image; if the camera and references moved too, the amplitude is not established.\n86\t- **Targets move slowly, alone, then come back**: one or a few targets, hours or days, without a camera movement or an obstructed view.\n87\t- **A target or a small group jumps and stays shifted**: at once, to another level, without the camera moving or a visible cause.\n88\t- **A step taken during a measurement outage**: on resumption, targets do not find their previous level.\n89\t\n90\t### Family of the cause\n91\t- **A reference dropped: the base changes**: one reference above its threshold, dropped: all targets jump together, the reprojection error at zero; the family is that of what hindered the reference.\n92\t- **Two references lost: the camera is blind**: two of three references dropped one after the other: every point of the range is invalid; the family of the cause.\n93\t- **A compensation on two references**: a station built with two, or having lost one for good: the slightest difference between them passes into all the targets; the family of what disturbs them.\n94\t- **A spider web in front of the lens**: Visibility when it veils the image, Obstruction when a thread hides a few spots; no signal at all is possible, only the images show it.\n95\t\n96\t## What is not labeled\n97\t\n98\t- 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.\n99\t- 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.\n100\t- 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).\n101\t- The expert can say so with the key `None` (labeling tool: \"None (curves untouched)\"): such a label is not counted.\n102\t"}]},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"83725a14-3dca-42c5-b46e-5b478aa900d5","timestamp":"2026-11-17T20:31:07.268Z","tool_use_result":{"type":"text","file":{"filePath":"/home/maxime/aimsight-app/labeling/families.md","content":"# The label families\n\nOne 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.\n\n| Key | Detector | What happens | For the client |\n|---|---|---|---|\n| `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 |\n| `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 |\n| `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 |\n| `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 |\n| `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 |\n| `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 |\n\nFor 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:\n\n| Variety | For the client |\n|---|---|\n| `Poor visibility reduced` | use the data over the range with care: they are less precise |\n| `Heat shimmer` | nothing to do: the small fast wiggles are not movement |\n| `Camera thermal movement` | nothing to do: this is not a movement of the structure |\n| `Brief obstruction` | ignore this single point on the curves |\n| `Sudden jump, back to normal` | look at the images: the cause is not established |\n| `Lasting shift` | check whether the structure moved: look at the images |\n| `Jump, not back yet` | check whether the structure moved: look at the images |\n| `Slow drift` | keep watching it |\n\n## The boundaries\n\n- **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.\n- **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.\n- **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 Displacement without a cause. The description says it is a reference, and that the targets move together because of it.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **Target issue or Displacement**: a changed configuration (moved sensors, changed starting position, setting) is Target issue; the jump that results is not a Displacement.\n\n## The phenomena\n\nWhat has been labelled so far, one line each: **name**: what is seen; how to tell it from its neighbours. The hypotheses to weigh for a moment of a range; the cases, their bounds and descriptions come from the labels, through `precedents.py`. A phenomenon not in this list is labelled too, without forcing a cause.\n\n### No data\n- **A gap common to several stations**: the measurements missing at the same minutes on every station measuring then; a cause outside the stations, not established. Read the other stations before the station's metrics.\n- **The station runs, the measurement is missing**: one station, powered and communicating (synchronization, image or `DB_not_uploaded` at the missing instant), misses a measurement.\n- **The station goes silent on its own, for a long time**: no measurements, no images, no metrics, for hours or days, without the signature of a lack of energy.\n- **The station shuts down for lack of energy**: the battery does not last the night; voltage below the knee before the gap, a restart with the solar charge.\n- **Mains cut: the station runs on its battery**: a station on mains stops, or comes back on a drawn-down battery, until the mains return.\n\n### Obstruction\n- **A pass-by hides the targets for the length of one measurement**: a train, a vehicle, passers-by: the hidden targets rejected for one acquisition, back at the next; a reference behind it makes the whole base jump. Insects give the same signature: only the image tells.\n- **A target left under the threshold latches onto a headlight, a reflection or another spot**: during a pass-by, one false point kept in the curve, without rejection; `dominance` rises on a recent camera.\n- **A vehicle or machine that stays in front of the targets**: the same sensors hidden for hours or days, sometimes a reference; one label per parking.\n- **An animal very close to the lens**: lit at night, it hides part or all of the scene for one or two measurements; a spider is not its web.\n- **A plant shaken by the wind in front of a target**: one target, at times, on windy days; it grows over weeks.\n- **An obstacle covers part of the spot**: an obstacle, or a mark on the glass in front of one spot, hides part of it for hours or weeks: the measured centre slides; the sliding is the artifact, the jump back is the return to normal.\n\n### Visibility\n- **Rain**: drops in front of the lens veil the spots during the hours of rain, at night above all; the references, higher up, may suffer less.\n- **The soiled glass**: after rain, drop marks veil part of the scene durably; under a single spot, it is an obstacle (Obstruction).\n- **Visibility drops over the whole scene, without an obstacle**: fog, condensation, a milky dawn: flux down on all sensors, `error_value` up, rejections; raw positions without a step.\n- **Part of the scene goes dark at night**: the distant spots, or a few neighbours at the edge of the group, lose their light, nothing in front.\n- **A reference loses its brightness, without an obstacle**: one or two references weaken and shrink, most often at night, then come back on their own; the centre does not move.\n- **Atmospheric turbulence**: by day, air heated above a road, ballast or rails makes the spots tremble: a fast noise, `error_value` up. Without the `error_value` rising, an agitation of the pose is the camera heating (Thermal displacement).\n- **The sun in the field or behind a spot**: the sun enters the field, or lights the background of a target or a reference as bright as it: rejections at the same hours on sunny days only.\n- **A faint spot lost when the light is missing**: a faint target crosses its threshold at the change from night to day, under an overcast sky or in a noisy night image; its rejections come with the light, not every day (else Target issue).\n\n### Target issue\n- **A target rejected at all its measurements**: never accepted, whatever the weather.\n- **A target right at the threshold, the whole batch**: its `error_value` keeps crossing the threshold, with many own rejections.\n- **A target rejected every night or every day**: under the station's ordinary regime (floodlight, daylight), at the same hours, whatever the weather.\n- **A target that degrades, and sometimes recovers**: seen worse and worse from a date on; back only after weeks, if ever, often at another level.\n- **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.\n\n### Thermal displacement\n- **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.\n- **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.\n- **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.\n- **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).\n\n### Displacement\n- **A step of the camera that the compensation does not erase**: the camera moves at once and a remainder passes into the curves; a step that leaves nothing beyond the noise is not labelled.\n- **The camera tilts little by little**: over weeks, the tilt rises and the compensation corrects some targets better than others; the targets do not move relative to each other.\n- **The base changes without a reference lost**: all references kept, the distance between them changes a little; all targets shift together without moving in the image.\n- **A real movement of the structure**: targets shift and stay, with references and pose stable and a good image; if the camera and references moved too, the amplitude is not established.\n- **Targets move slowly, alone, then come back**: one or a few targets, hours or days, without a camera movement or an obstructed view.\n- **A target or a small group jumps and stays shifted**: at once, to another level, without the camera moving or a visible cause.\n- **A step taken during a measurement outage**: on resumption, targets do not find their previous level.\n\n### Family of the cause\n- **A reference dropped: the base changes**: one reference above its threshold, dropped: all targets jump together, the reprojection error at zero; the family is that of what hindered the reference.\n- **Two references lost: the camera is blind**: two of three references dropped one after the other: every point of the range is invalid; the family of the cause.\n- **A compensation on two references**: a station built with two, or having lost one for good: the slightest difference between them passes into all the targets; the family of what disturbs them.\n- **A spider web in front of the lens**: Visibility when it veils the image, Obstruction when a thread hides a few spots; no signal at all is possible, only the images show it.\n\n## What is not labeled\n\n- 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.\n- 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.\n- 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).\n- The expert can say so with the key `None` (labeling tool: \"None (curves untouched)\"): such a label is not counted.\n","numLines":102,"startLine":1,"totalLines":102}},"tool_result_meta":[{"id":"toolu_01KbsyhP8CZpRaPgCJsyBpbL","permission_decision":{"decision":"accept","source":"config","reason_type":"rule"}}]}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98n3RGUXfNwFvkqgaDt","type":"message","role":"assistant","content":[{"type":"tool_use","id":"toolu_01FzWpapAwFg1PdA9vYqMuac","name":"Read","input":{"file_path":"/home/maxime/aimsight-app/labeling/reading-rules.md"},"caller":{"type":"direct"}}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":524,"cache_read_input_tokens":10876,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":524},"output_tokens":16,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"a80117dd-2201-4a8e-8e15-25c0f866b7de","timestamp":"2026-11-17T20:31:07.694Z","request_id":"req_011Ch98n3C8UGUW8Q6NtwAzR","wire_tool_inputs":{"toolu_01FzWpapAwFg1PdA9vYqMuac":{"file_path":"/home/maxime/aimsight-app/labeling/reading-rules.md"}}}
-{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_01FzWpapAwFg1PdA9vYqMuac","type":"tool_result","content":"1\t# Reading rules\n2\t\n3\tWhat the data of a station mean: where each cause enters the measurement, what it touches, and the rules and false friends that the expert and the reviewed labels have established. What the files and columns are: `tools/DATA.md`. How to place a label: `labeling-rules.md`; the families and their boundaries: `families.md`, whose rules are not repeated here.\n4\t\n5\tCases are cited by label id (`NORDEND-80`, in `auto/.jsonl`; `precedents.py` finds others); `[expert]`: the expert's word, from a label that is not in `auto/`. Maintained by hand.\n6\t\n7\t## 1. How a measurement is made\n8\t\n9\t1. **The scene**: targets on the structure, references around it, assumed fixed.\n10\t2. **The view**: the air between the camera and the targets, and what can pass or settle in front.\n11\t3. **The image**: the lens, then the capture (IRON, or DIFF which combines several captures).\n12\t4. **The pattern measurement**: each sensor is found in the image: `x`, `y`, `error_value`; on recent cameras, the image quality. Above `error_threshold`, the measurement is rejected.\n13\t5. **The compensation**: a 2D similarity (translation, rotation, scale) fitted on the references (`global_ref`) gives the camera pose (`pan`, `tilt`, `rotation`, `scale`, `sigma0`) and, per reference, `reproj_err` and `inlier`.\n14\t6. **The corrected curve**: `corr_x`, `corr_y`, the position of the target once the estimated camera movement is removed.\n15\t\n16\tA displayed value is the end of this chain: find the stage that gave way.\n17\t\n18\t## 2. Where each cause enters, and what it touches\n19\t\n20\t| Stage | Cause | What it touches | Time | Witnesses |\n21\t|---|---|---|---|---|\n22\t| View (air) | fog, rain, condensation: **reduced visibility** | a homogeneous drop in flux; `error_value` rises, rejections; raw positions without a step | hours | quality (`flux`), images |\n23\t| View (air) | **heat haze** (turbulence) | a fast noise; only when the structure really heats up; not under a bridge | the hot hours | temperature, `error_value` by day versus night |\n24\t| View (obstacle) | object, leaves, snow on a target: **occultation**; a passage | one or a few targets; on a recent camera, their flux cut, the neighbours intact (LENZSPITZE-9); a passage: one measurement | from one measurement to weeks | quality, images |\n25\t| Target | problem target (badly oriented, dirty, glued) | one target, lastingly | days and more | `error_value` of the target alone |\n26\t| Lens | **thermal deformation of the optics** (sun on the station) | the whole image deforms, which a similarity cannot represent | short: follows the sun on the station | housing temperature |\n27\t| Camera and mount | **expansion of the mount**; wind, jolt, shock | raw positions of all sensors, references included, together; the compensation absorbs it (`corr` flat) or badly: `corr` follows the inflections of the camera movement | specific to the mount | camera pose, housing temperature |\n28\t| References | **reference hidden or less well seen** | the transformation is redone without it: points shifted at once, often grouped in one part of the image, the shift growing with the distance to the references; back when it returns: reversible | the time of the nuisance | `error_value`, `reproj_err` of the references, `sigma0`, camera pose |\n29\t| References | a reference moved | the `corr` of the targets shifted lastingly | lasting | `reproj_err` of the reference |\n30\t| Structure | **thermal expansion of the structure** | `corr`, an amplitude specific to each target, references stable | the longest: slow heating, late cooling | no air temperature (section 3) |\n31\t| Structure | real movement | `corr` of one or several targets, which lasts; references and pose stable, good image quality | lasting | all of the above, at calm |\n32\t\n33\t**A jump that returns** to normal is not serious: the return is what makes it benign. Saying \"jump\" is not enough; the question is its cause, quite often a reference hidden or less well seen.\n34\t\n35\t## 3. Thermal effects\n36\t\n37\t- **Three movement effects**: the lens, the mount, the structure, told apart by their heating and cooling times; the structure is the slowest. Heat haze is apart: a noise, not a movement.\n38\t- **The cases cross**: a camera on a bridge has two structures, the one that carries it (the mount) and the one it monitors.\n39\t- **In waves**: expansion, then contraction; often stronger in Y than in X, depending on the orientation.\n40\t- **The kind of structure says whether a thermal movement is possible**: a bridge yes; a rock face, too massive, or a road, no: the movement is then that of the camera (`stations.md`). [expert, WILDSTRUBEL-102]\n41\t- **The camera can move through a thermal effect at a different rhythm from the structure**, not having the same heating time. [expert]\n42\t- **The temperature that counts is that of the camera housing, not that of the air around**, even sheltered. The temperatures available are those of the compute board (`sensor_*_deg_c`), inside the housing, heated by the sun and by the computing, as hourly means: a witness for the lens and the mount, not for the structure nor the air. `temperature_deg_c`, on a few stations: unknown sensor. [expert, BREITHORN-14]\n43\t- **A change of regime is understood through the temperature**: look at it. [expert]\n44\t- **The direction of a thermal movement is read on the housing temperature, not on the hour**; when the scale of the camera follows it, the effect is on the camera. [NORDEND-155, CLARIDEN-13]\n45\t\n46\t## 4. Gaps\n47\t\n48\t- **A gap is not necessarily an outage**: acquisition, transmission, ingestion and display are distinct layers.\n49\t - At the end of a file, empty values can be only a synchronization delay (`last_sync`): a delay only if the other stations do not have their data yet either.\n50\t - At the start of a file, empty values precede the first measurement: not an outage.\n51\t - A gap surrounded by a normal voltage is not an energy problem.\n52\t- **A gap is read with the other stations and the metrics** (the boundary \"A gap\" of `families.md`). [JUNGFRAU-52, NORDEND-50, WILDSTRUBEL-201, CLARIDEN-19]\n53\t- **A power cut leaves a signature**: the voltage below the knee (about 12.8 V) just before or just after the gap; the temperature drops during the gap more than at the same hours on nights without a gap, which alone does not settle it (a common gap can do the same, an outage that comes back after sunrise shows nothing).\n54\t- **A station on mains that comes back with its battery drawn down has lost the mains.**\n55\t- **A `NaN` or `inf` value** in an export is an absence of measurement.\n56\t\n57\t## 5. Reading rules\n58\t\n59\t- **What moves in the image is read before the cause, on the raw positions against the overall movement** (`overview.py --rigid`): the targets do not move relative to each other, it is the camera [BREITHORN-2]; targets move alone, a movement is not excluded [CLARIDEN-14]; nothing moves and the curves jump, it is the base or the configuration [WILDSTRUBEL-136, CLARIDEN-38].\n60\t- **A jump is judged against the neighbours**: if it brings the target back toward them, it is a return to normal, and the artifact was before; if it takes it away from them, it is to be treated quite differently. [expert]\n61\t- **A level is also judged against the past of the target, over weeks**: a jump that brings it back to an old level is a return. [NORDEND-94, NORDEND-169]\n62\t- **A high `error_value` is not a problem in itself: its variations count.** [expert]\n63\t- **A very stable `error_value` says the targets stay well visible**: while they move, it rather suggests a poor compensation than an obstruction of the view. [expert]\n64\t- **A rejected measurement is removed from the display, not a measurement just under the threshold**: a target left under the threshold keeps its jump. [expert, NIEDERHORN-13]\n65\t- **At least three references are needed; dropping a single one is enough to distort everything**: a kind of triangulation. **The position of the targets rests on the network of references**: references badly seen, targets badly anchored. [expert]\n66\t- **The reprojection error says how many references hold**: at zero, only two remain, a very bad sign, not a perfect measurement; absent, only one, and no measurement is possible. Except on a station built with two references, where it is always at zero. [JUNGFRAU-22, FLORIDA-4, expert]\n67\t- **The pose of the camera is reliable only if the references hold**: a reference rejected, dropped or sliding against the targets distorts it; a single hindered target does not. [FLORIDA-58]\n68\t- **A drift specific to a few targets that follows the camera, on the same dates, is the scene deforming with it**, not a second movement; it is separate only if it has its own dates. [NEBRASKA-6, NEBRASKA-5]\n69\t- **Neighbouring cameras are read together**: the same movement, the same loss or the same gap on the cameras of one building have a common cause; what touches only one is on its line of sight. [MICHIGAN-3, BREITHORN-20]\n70\t\n71\t## 6. False friends\n72\t\n73\t- **Jumps of many targets, all in the same direction, are not a movement** when they fall at the reference switches: raw positions without a step, daily cycle that continues. [expert]\n74\t- **A target that slides slowly away from its neighbours is not moving** when its `error_value` rises with the sliding and a step brings it back toward them. [expert]\n75\t- **A rise over several days is not necessarily a real movement**: it may follow a lasting drop in temperature. [expert]\n76\t- **Corrections stuck at zero are not a failure**: a twin of a reference. [expert]\n77\t- **No signal does not mean no obstruction**: only the images show the web. [expert]\n78\t- **A web is not the spider**: the web veils in part for hours or days; the spider hides everything for the length of one measurement. [expert]\n79\t- **References that do not move in the rain do not contradict the rain**: higher up, they suffer it less. [NIEDERHORN-12]\n80\t- **The step of a real movement is not its amplitude** when the camera and the references have moved too. [expert]\n81\t- **A swarm of insects is not a train**: same signature; only the image tells them apart. [NIEDERHORN-66]\n82\t- **In a tunnel, a temperature drop at the same moment does not make a thermal effect**: the bump of a group comes with the `error_value` and returns before the scale of the camera. [CLARIDEN-12, CLARIDEN-13]\n83\t- **The return of the `error_value` is not the end of an obstruction**: after a mark on the glass, the curves stay shifted. [NORDEND-169]\n84\t- **A spot on a thumbnail that follows the measurement is not necessarily there**: the frame follows a measurement perhaps latched onto the neighbour; only a fixed frame shows it. [FLORIDA-43]\n85\t\n86\t## 7. Non-negotiable rules\n87\t\n88\t- Judge nothing on a binary `inlier`: use continuous weights, residuals, influence.\n89\t- Neither `sigma0` alone nor the number of references is ever a sufficient criterion.\n90\t- The image quality of a target is not the quality of the reference network; a small residual is not a well-constrained transformation.\n91\t- A common-mode movement is not a structural movement; coherent references are not physically fixed references: the camera cannot prove that a network moving as a block is fixed.\n92\t\n93\t## 8. Lessons from cases outside the labels\n94\t\n95\t- **When everything moves together, the measurements alone do not separate the structure from the camera** (Barcelona, a bridge whose vault subsided: the references, the camera and the structure moved; the expert called it a real movement, confirmed by other monitoring systems of the site). An unstable compensation then distorts the amplitude of a real movement: the movement is reported, its amplitude is not established. [expert]\n96\t- **Two prisms too close interfere**: a 24 h cycle correlated between the two, or isolated peaks on one target at a time, too large for the structure, with no obstruction on the images; a neighbour much brighter than the others. On a recent camera, `dominance` shows it. [client report]\n97\t- **Vegetation grows over days and weeks**: a partial, progressive occultation, not reversible from one measurement to the next like a passage; the hardest obstruction according to the expert. [client report]\n98\t- **References masked (two of four, by vegetation)**: a 24 h cycle on pan, roll and tilt, badly compensated, is then not a movement of the camera but a base too weak for the transformation. [client report]\n99\t- **A target of low contrast**: by day, square waves on one axis, back at night, `error_value` rising by day without reaching the threshold. [client report]\n100\t- **Snow**: noise and apparent movements on all sensors and the camera, a brief loss of data, the signal quickly back. [client report]\n101\t"}]},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"a0c33946-6944-4d01-bb6b-35c66f18763f","timestamp":"2026-11-17T20:31:07.721Z","tool_use_result":{"type":"text","file":{"filePath":"/home/maxime/aimsight-app/labeling/reading-rules.md","content":"# Reading rules\n\nWhat the data of a station mean: where each cause enters the measurement, what it touches, and the rules and false friends that the expert and the reviewed labels have established. What the files and columns are: `tools/DATA.md`. How to place a label: `labeling-rules.md`; the families and their boundaries: `families.md`, whose rules are not repeated here.\n\nCases are cited by label id (`NORDEND-80`, in `auto/.jsonl`; `precedents.py` finds others); `[expert]`: the expert's word, from a label that is not in `auto/`. Maintained by hand.\n\n## 1. How a measurement is made\n\n1. **The scene**: targets on the structure, references around it, assumed fixed.\n2. **The view**: the air between the camera and the targets, and what can pass or settle in front.\n3. **The image**: the lens, then the capture (IRON, or DIFF which combines several captures).\n4. **The pattern measurement**: each sensor is found in the image: `x`, `y`, `error_value`; on recent cameras, the image quality. Above `error_threshold`, the measurement is rejected.\n5. **The compensation**: a 2D similarity (translation, rotation, scale) fitted on the references (`global_ref`) gives the camera pose (`pan`, `tilt`, `rotation`, `scale`, `sigma0`) and, per reference, `reproj_err` and `inlier`.\n6. **The corrected curve**: `corr_x`, `corr_y`, the position of the target once the estimated camera movement is removed.\n\nA displayed value is the end of this chain: find the stage that gave way.\n\n## 2. Where each cause enters, and what it touches\n\n| Stage | Cause | What it touches | Time | Witnesses |\n|---|---|---|---|---|\n| View (air) | fog, rain, condensation: **reduced visibility** | a homogeneous drop in flux; `error_value` rises, rejections; raw positions without a step | hours | quality (`flux`), images |\n| View (air) | **heat haze** (turbulence) | a fast noise; only when the structure really heats up; not under a bridge | the hot hours | temperature, `error_value` by day versus night |\n| View (obstacle) | object, leaves, snow on a target: **occultation**; a passage | one or a few targets; on a recent camera, their flux cut, the neighbours intact (LENZSPITZE-9); a passage: one measurement | from one measurement to weeks | quality, images |\n| Target | problem target (badly oriented, dirty, glued) | one target, lastingly | days and more | `error_value` of the target alone |\n| Lens | **thermal deformation of the optics** (sun on the station) | the whole image deforms, which a similarity cannot represent | short: follows the sun on the station | housing temperature |\n| Camera and mount | **expansion of the mount**; wind, jolt, shock | raw positions of all sensors, references included, together; the compensation absorbs it (`corr` flat) or badly: `corr` follows the inflections of the camera movement | specific to the mount | camera pose, housing temperature |\n| References | **reference hidden or less well seen** | the transformation is redone without it: points shifted at once, often grouped in one part of the image, the shift growing with the distance to the references; back when it returns: reversible | the time of the nuisance | `error_value`, `reproj_err` of the references, `sigma0`, camera pose |\n| References | a reference moved | the `corr` of the targets shifted lastingly | lasting | `reproj_err` of the reference |\n| Structure | **thermal expansion of the structure** | `corr`, an amplitude specific to each target, references stable | the longest: slow heating, late cooling | no air temperature (section 3) |\n| Structure | real movement | `corr` of one or several targets, which lasts; references and pose stable, good image quality | lasting | all of the above, at calm |\n\n**A jump that returns** to normal is not serious: the return is what makes it benign. Saying \"jump\" is not enough; the question is its cause, quite often a reference hidden or less well seen.\n\n## 3. Thermal effects\n\n- **Three movement effects**: the lens, the mount, the structure, told apart by their heating and cooling times; the structure is the slowest. Heat haze is apart: a noise, not a movement.\n- **The cases cross**: a camera on a bridge has two structures, the one that carries it (the mount) and the one it monitors.\n- **In waves**: expansion, then contraction; often stronger in Y than in X, depending on the orientation.\n- **The kind of structure says whether a thermal movement is possible**: a bridge yes; a rock face, too massive, or a road, no: the movement is then that of the camera (`stations.md`). [expert, WILDSTRUBEL-102]\n- **The camera can move through a thermal effect at a different rhythm from the structure**, not having the same heating time. [expert]\n- **The temperature that counts is that of the camera housing, not that of the air around**, even sheltered. The temperatures available are those of the compute board (`sensor_*_deg_c`), inside the housing, heated by the sun and by the computing, as hourly means: a witness for the lens and the mount, not for the structure nor the air. `temperature_deg_c`, on a few stations: unknown sensor. [expert, BREITHORN-14]\n- **A change of regime is understood through the temperature**: look at it. [expert]\n- **The direction of a thermal movement is read on the housing temperature, not on the hour**; when the scale of the camera follows it, the effect is on the camera. [NORDEND-155, CLARIDEN-13]\n\n## 4. Gaps\n\n- **A gap is not necessarily an outage**: acquisition, transmission, ingestion and display are distinct layers.\n - At the end of a file, empty values can be only a synchronization delay (`last_sync`): a delay only if the other stations do not have their data yet either.\n - At the start of a file, empty values precede the first measurement: not an outage.\n - A gap surrounded by a normal voltage is not an energy problem.\n- **A gap is read with the other stations and the metrics** (the boundary \"A gap\" of `families.md`). [JUNGFRAU-52, NORDEND-50, WILDSTRUBEL-201, CLARIDEN-19]\n- **A power cut leaves a signature**: the voltage below the knee (about 12.8 V) just before or just after the gap; the temperature drops during the gap more than at the same hours on nights without a gap, which alone does not settle it (a common gap can do the same, an outage that comes back after sunrise shows nothing).\n- **A station on mains that comes back with its battery drawn down has lost the mains.**\n- **A `NaN` or `inf` value** in an export is an absence of measurement.\n\n## 5. Reading rules\n\n- **What moves in the image is read before the cause, on the raw positions against the overall movement** (`overview.py --rigid`): the targets do not move relative to each other, it is the camera [BREITHORN-2]; targets move alone, a movement is not excluded [CLARIDEN-14]; nothing moves and the curves jump, it is the base or the configuration [WILDSTRUBEL-136, CLARIDEN-38].\n- **A jump is judged against the neighbours**: if it brings the target back toward them, it is a return to normal, and the artifact was before; if it takes it away from them, it is to be treated quite differently. [expert]\n- **A level is also judged against the past of the target, over weeks**: a jump that brings it back to an old level is a return. [NORDEND-94, NORDEND-169]\n- **A high `error_value` is not a problem in itself: its variations count.** [expert]\n- **A very stable `error_value` says the targets stay well visible**: while they move, it rather suggests a poor compensation than an obstruction of the view. [expert]\n- **A rejected measurement is removed from the display, not a measurement just under the threshold**: a target left under the threshold keeps its jump. [expert, NIEDERHORN-13]\n- **At least three references are needed; dropping a single one is enough to distort everything**: a kind of triangulation. **The position of the targets rests on the network of references**: references badly seen, targets badly anchored. [expert]\n- **The reprojection error says how many references hold**: at zero, only two remain, a very bad sign, not a perfect measurement; absent, only one, and no measurement is possible. Except on a station built with two references, where it is always at zero. [JUNGFRAU-22, FLORIDA-4, expert]\n- **The pose of the camera is reliable only if the references hold**: a reference rejected, dropped or sliding against the targets distorts it; a single hindered target does not. [FLORIDA-58]\n- **A drift specific to a few targets that follows the camera, on the same dates, is the scene deforming with it**, not a second movement; it is separate only if it has its own dates. [NEBRASKA-6, NEBRASKA-5]\n- **Neighbouring cameras are read together**: the same movement, the same loss or the same gap on the cameras of one building have a common cause; what touches only one is on its line of sight. [MICHIGAN-3, BREITHORN-20]\n\n## 6. False friends\n\n- **Jumps of many targets, all in the same direction, are not a movement** when they fall at the reference switches: raw positions without a step, daily cycle that continues. [expert]\n- **A target that slides slowly away from its neighbours is not moving** when its `error_value` rises with the sliding and a step brings it back toward them. [expert]\n- **A rise over several days is not necessarily a real movement**: it may follow a lasting drop in temperature. [expert]\n- **Corrections stuck at zero are not a failure**: a twin of a reference. [expert]\n- **No signal does not mean no obstruction**: only the images show the web. [expert]\n- **A web is not the spider**: the web veils in part for hours or days; the spider hides everything for the length of one measurement. [expert]\n- **References that do not move in the rain do not contradict the rain**: higher up, they suffer it less. [NIEDERHORN-12]\n- **The step of a real movement is not its amplitude** when the camera and the references have moved too. [expert]\n- **A swarm of insects is not a train**: same signature; only the image tells them apart. [NIEDERHORN-66]\n- **In a tunnel, a temperature drop at the same moment does not make a thermal effect**: the bump of a group comes with the `error_value` and returns before the scale of the camera. [CLARIDEN-12, CLARIDEN-13]\n- **The return of the `error_value` is not the end of an obstruction**: after a mark on the glass, the curves stay shifted. [NORDEND-169]\n- **A spot on a thumbnail that follows the measurement is not necessarily there**: the frame follows a measurement perhaps latched onto the neighbour; only a fixed frame shows it. [FLORIDA-43]\n\n## 7. Non-negotiable rules\n\n- Judge nothing on a binary `inlier`: use continuous weights, residuals, influence.\n- Neither `sigma0` alone nor the number of references is ever a sufficient criterion.\n- The image quality of a target is not the quality of the reference network; a small residual is not a well-constrained transformation.\n- A common-mode movement is not a structural movement; coherent references are not physically fixed references: the camera cannot prove that a network moving as a block is fixed.\n\n## 8. Lessons from cases outside the labels\n\n- **When everything moves together, the measurements alone do not separate the structure from the camera** (Barcelona, a bridge whose vault subsided: the references, the camera and the structure moved; the expert called it a real movement, confirmed by other monitoring systems of the site). An unstable compensation then distorts the amplitude of a real movement: the movement is reported, its amplitude is not established. [expert]\n- **Two prisms too close interfere**: a 24 h cycle correlated between the two, or isolated peaks on one target at a time, too large for the structure, with no obstruction on the images; a neighbour much brighter than the others. On a recent camera, `dominance` shows it. [client report]\n- **Vegetation grows over days and weeks**: a partial, progressive occultation, not reversible from one measurement to the next like a passage; the hardest obstruction according to the expert. [client report]\n- **References masked (two of four, by vegetation)**: a 24 h cycle on pan, roll and tilt, badly compensated, is then not a movement of the camera but a base too weak for the transformation. [client report]\n- **A target of low contrast**: by day, square waves on one axis, back at night, `error_value` rising by day without reaching the threshold. [client report]\n- **Snow**: noise and apparent movements on all sensors and the camera, a brief loss of data, the signal quickly back. [client report]\n","numLines":101,"startLine":1,"totalLines":101}},"tool_result_meta":[{"id":"toolu_01FzWpapAwFg1PdA9vYqMuac","permission_decision":{"decision":"accept","source":"config","reason_type":"rule"}}]}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98n3RGUXfNwFvkqgaDt","type":"message","role":"assistant","content":[{"type":"tool_use","id":"toolu_01PzhVjEqPb4Ap7DXXYKZ2BV","name":"Read","input":{"file_path":"/home/maxime/aimsight-app/labeling/stations.md"},"caller":{"type":"direct"}}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":524,"cache_read_input_tokens":10876,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":524},"output_tokens":16,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"1f2ad0f4-d3c1-4581-bbc5-a2f45e2dafeb","timestamp":"2026-11-17T20:31:08.059Z","request_id":"req_011Ch98n3C8UGUW8Q6NtwAzR","wire_tool_inputs":{"toolu_01PzhVjEqPb4Ap7DXXYKZ2BV":{"file_path":"/home/maxime/aimsight-app/labeling/stations.md"}}}
-{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_01PzhVjEqPb4Ap7DXXYKZ2BV","type":"tool_result","content":"1\t# The stations\n2\t\n3\tWhat each station is: its structure, its camera, its references, its neighbours. Context for reading a station's data, not a rule: what happens at a station is in its labels (`auto/.jsonl`, `precedents.py`). The kind of structure says whether a thermal movement of the structure is possible (`reading-rules.md`, section 3). Cases are cited by label id; `[expert]`: the expert's word. Maintained by hand: a new station gets its row when its first range is analysed.\n4\t\n5\t| Station | Structure | Camera | References | Neighbouring cameras |\n6\t|---|---|---|---|---|\n7\t| BREITHORN | in a building (a factory, indoors) [expert] | one measurement every four hours; COLJ19 and POUI19 much closer to the camera than the other targets [expert]; the camera nods forward over October, compensation incomplete [expert] | REFH22, REFPOU22 among the sensors at the bottom of the image | MICHIGAN and NEBRASKA, in the same building: a drift common to the three [BREITHORN-2] |\n8\t| CLARIDEN | a tunnel under construction, with other measurement systems [expert] | images always dark; on mains | four references, D-302-C, PR-291, PR-293, PR-295; PR-284 is a local reference, read as a target; D-302-B and PR_BG on the same prism [CLARIDEN-38] | — |\n9\t| FLORIDA | — | — | two references only, p1_r and r1_r, each with its twin target (Sellette 3, Pont Ernen) [expert] | its one-measurement gaps at night fall at the same instants as SNCF01's |\n10\t| JUNGFRAU | a bridge, which rises as it cools [expert] | under the deck, fixed to the bridge | three references off the bridge, REF_D, REF_G, REF_CT | — |\n11\t| LENZSPITZE | a railway seen from under a bridge, a work site and machines next to it | recent camera, with image quality; `x`, `y` relative in the export (`tools/DATA.md`); only `temperature_deg_c` is filled | nine references, including the distant 8011 to 8014 | — |\n12\t| MICHIGAN | in the same building as BREITHORN, indoors [expert] | one measurement every four hours | two references since the loss of REFPOU22 on 09.10 [MICHIGAN-3]; COLH21' and REFH22' on the same point until 05.10 [MICHIGAN-1] | BREITHORN, NEBRASKA: lost a reference at the same measurement as NEBRASKA |\n13\t| NEBRASKA | in the same building as BREITHORN [expert] | one measurement every four hours | two references since the loss of REFCOLH22 [NEBRASKA-2] | BREITHORN, MICHIGAN |\n14\t| NIEDERHORN | railway tracks | floodlight at night | higher up, on the road above the tracks (PWD_REF08 to PWD_REF12) | — |\n15\t| NORDEND | a quarry: a rock face too massive to move with the temperature [expert] | infrared lighting at night; DIFF images | three references, CTR02, CTR03, CTR04; CTR01 is a local reference, read as a target | — |\n16\t| SNCF01 | a masonry wall along railway tracks | no system metrics, hence no temperature | three references, BG.3.1, R1, R2 | FLORIDA (gaps at the same instants) |\n17\t| WILDSTRUBEL | a road, in a town [WILDSTRUBEL-102] | solar battery | six references, R1 and R2 at the edge of the road; R3 invisible by day [WILDSTRUBEL-130] | — |\n18\t"}]},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"eb5bdbde-5212-4579-a25a-a2c91fef0817","timestamp":"2026-11-17T20:31:08.096Z","tool_use_result":{"type":"text","file":{"filePath":"/home/maxime/aimsight-app/labeling/stations.md","content":"# The stations\n\nWhat each station is: its structure, its camera, its references, its neighbours. Context for reading a station's data, not a rule: what happens at a station is in its labels (`auto/.jsonl`, `precedents.py`). The kind of structure says whether a thermal movement of the structure is possible (`reading-rules.md`, section 3). Cases are cited by label id; `[expert]`: the expert's word. Maintained by hand: a new station gets its row when its first range is analysed.\n\n| Station | Structure | Camera | References | Neighbouring cameras |\n|---|---|---|---|---|\n| BREITHORN | in a building (a factory, indoors) [expert] | one measurement every four hours; COLJ19 and POUI19 much closer to the camera than the other targets [expert]; the camera nods forward over October, compensation incomplete [expert] | REFH22, REFPOU22 among the sensors at the bottom of the image | MICHIGAN and NEBRASKA, in the same building: a drift common to the three [BREITHORN-2] |\n| CLARIDEN | a tunnel under construction, with other measurement systems [expert] | images always dark; on mains | four references, D-302-C, PR-291, PR-293, PR-295; PR-284 is a local reference, read as a target; D-302-B and PR_BG on the same prism [CLARIDEN-38] | — |\n| FLORIDA | — | — | two references only, p1_r and r1_r, each with its twin target (Sellette 3, Pont Ernen) [expert] | its one-measurement gaps at night fall at the same instants as SNCF01's |\n| JUNGFRAU | a bridge, which rises as it cools [expert] | under the deck, fixed to the bridge | three references off the bridge, REF_D, REF_G, REF_CT | — |\n| LENZSPITZE | a railway seen from under a bridge, a work site and machines next to it | recent camera, with image quality; `x`, `y` relative in the export (`tools/DATA.md`); only `temperature_deg_c` is filled | nine references, including the distant 8011 to 8014 | — |\n| MICHIGAN | in the same building as BREITHORN, indoors [expert] | one measurement every four hours | two references since the loss of REFPOU22 on 09.10 [MICHIGAN-3]; COLH21' and REFH22' on the same point until 05.10 [MICHIGAN-1] | BREITHORN, NEBRASKA: lost a reference at the same measurement as NEBRASKA |\n| NEBRASKA | in the same building as BREITHORN [expert] | one measurement every four hours | two references since the loss of REFCOLH22 [NEBRASKA-2] | BREITHORN, MICHIGAN |\n| NIEDERHORN | railway tracks | floodlight at night | higher up, on the road above the tracks (PWD_REF08 to PWD_REF12) | — |\n| NORDEND | a quarry: a rock face too massive to move with the temperature [expert] | infrared lighting at night; DIFF images | three references, CTR02, CTR03, CTR04; CTR01 is a local reference, read as a target | — |\n| SNCF01 | a masonry wall along railway tracks | no system metrics, hence no temperature | three references, BG.3.1, R1, R2 | FLORIDA (gaps at the same instants) |\n| WILDSTRUBEL | a road, in a town [WILDSTRUBEL-102] | solar battery | six references, R1 and R2 at the edge of the road; R3 invisible by day [WILDSTRUBEL-130] | — |\n","numLines":18,"startLine":1,"totalLines":18}},"tool_result_meta":[{"id":"toolu_01PzhVjEqPb4Ap7DXXYKZ2BV","permission_decision":{"decision":"accept","source":"config","reason_type":"rule"}}]}
-{"type":"system","subtype":"thinking_tokens","estimated_tokens":50,"estimated_tokens_delta":50,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"5948d149-89bf-479d-8f58-3f5195832dad"}
-{"type":"system","subtype":"thinking_tokens","estimated_tokens":150,"estimated_tokens_delta":100,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"8c562ea6-77cb-40eb-a716-cb3152532b66"}
-{"type":"system","subtype":"thinking_tokens","estimated_tokens":286,"estimated_tokens_delta":136,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"b2d37997-ddfe-41e2-8c96-e6759494853a"}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98nLBpxDUwXRGPNJcLf","type":"message","role":"assistant","content":[{"type":"thinking","thinking":"","signature":"CAQS7wgKEAgTGAI4AUIIdGhpbmtpbmcSDKHXjoVH2iaM2zbMBxoMfT2RH5/UVp4u7CSIIjDE9YZj9+3djkM7Fwg/EzfZxy29YuTJBEcjvX5mfz/qTb7dRmMOTpbwa3nM92x1qEgqjAiF5+0ZGcZ0o2HHpifOG84HW5oBmA3S81M7FEKWW1i3HWxlXMRM2vaVdDKDwWRCFhfza02BxNSnGjyujqfkQiHJnt7rihNZmdcrLkiPqejIue1eoaHWuvh0MyGKWmasZxMOpS58nTryhbZSWYHS7wxQm9hOua2xl311cG4sipUzPPFB0bG6sPxXPUfSnknFgd8LMXHMHN6EYkR/yeQxbEo8BYjwVeKF6jS8TeuAqlReLix1G7QhzArGc8PuQZb7nd+UFu4bT9tEVHLFh6XnqQg9SBNALmfokHdZ7I0TJGKkTJqP0o6gQhjqn8zqh+u5KdsPf+Brrln1GNyXUBb+2zARxYnhK4Mj18dXCvDATmStP3znYoo8Y3u1ME3R5wN+0brZA1L7yq0CP9RgFGLG4hknJvrI+rfXPMW5K1TrTfDJLmsn15ubNiGEfD26LaoDE2kUfbz9QBzfuQ4hBOOoArBGD34iApwjez9BqLi6IlEcrpJmfIrcErMK82/5NZJXVLDgU5lZv5GcDYmUp+aOrR9NCKezbpVi2hSPNYHIFZDoRGI1jTQqlKF1ohB5KmYteN1Lnun0wKouvcnjTuxJ628Tx25NDOMoTlvOUtyEQSdRd2kXQbDfYNKNByXEP1Y6DgeXhMX48Df5gb7H+nfgFVW1jAO9jGaSwTNXA0X4EHfe4j9xtBBh4pI+MA2Bf7FnUSnpAE5bqLW+8ayBLwd8dtz84JXhF80wpnufI43YL2Fbqhs+KDmM6VEGupqpZTUhC1+qweZ6RpN78nUCwFe3sP3oVRr7M1A2oGbdby57Ns+bUHdpjI5L47Zj1SPTpbdSw+aGNZoafotddleNTLGhBC3mpZG5FybRAnO+f/Wan3RX5xW/16Ej6W6s5XlR2ufeh0FDBb+1dI3JWSYlBuipEijLFwhuYQNZvKAwVKfowoepmhEe7eDv4Az3brsiLVz3MCaHQjYU08FMZxZ3kpyyemLZWxlfqaFLHxxsO9Oh8Foj2ox3ITh0aaK36p4zXsN/Q4hjRUwlh8kwGzm3QsS1gH2Tt759sDgoCj6vKNuhPMa19RiLqTFbia2d8OR/98Z/izRMeRk+4j9c4NYh34nqDGYAu5bO1CgsUr2a5nVHvObJXhS8KR1rbBChe5fLXn91a6glNMxQkfC5uhMdualftU/TMh4gZ+H8+pki5xJwVgk49MIk4l5VJbLXBRq4wws1b6kFv48A3ivLAKYVT1eZKpETHrzlgwSoQT0Dl+jizgPR/QZjhV1YK/MJOWLlT9PvRO4OZWQvLySed0Shl75sGazDyoX6QKKt0L9jAXlA0MO0QrCwGY7vwDqmdzYUuRy//sfBpxj4/fRLZ+oiOZTgU0cfuGZrOJsMCiTmnubMGAE="}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":4,"cache_creation_input_tokens":39788,"cache_read_input_tokens":11400,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":39788},"output_tokens":5,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"0c4bb667-f66c-4f5e-858b-291ec813ddc9","timestamp":"2026-11-17T20:31:16.014Z","request_id":"req_011Ch98nKzfjAPob8FLsjhNF","thinking_duration_ms":1850,"thinking_display":"updates"}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98nLBpxDUwXRGPNJcLf","type":"message","role":"assistant","content":[{"type":"tool_use","id":"toolu_01C54NY2fnmVnWLiMhbPwqH3","name":"Bash","input":{"command":"cd /home/maxime/aimsight-app; ls labeling/auto/analyses/CLARIDEN_2026-10-01T0000_2026-10-11T0000/; grep -n \"CLARIDEN-14\\|CLARIDEN-1[^0-9]\\|P-300-B\" labeling/auto/analyses/CLARIDEN_2026-10-*/*.md | head -50; grep -E '\"id\": \"CLARIDEN-(1|14|15)\"' labeling/auto/CLARIDEN.jsonl | cut -c1-400","description":"Look at period reports mentioning these labels"},"caller":{"type":"direct"}}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":4,"cache_creation_input_tokens":39788,"cache_read_input_tokens":11400,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":39788},"output_tokens":5,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"0b074dc3-40d7-4386-b6d7-3bd5500157c6","timestamp":"2026-11-17T20:31:17.776Z","request_id":"req_011Ch98nKzfjAPob8FLsjhNF","wire_tool_inputs":{"toolu_01C54NY2fnmVnWLiMhbPwqH3":{"command":"cd /home/maxime/aimsight-app; ls labeling/auto/analyses/CLARIDEN_2026-10-01T0000_2026-10-11T0000/; grep -n \"CLARIDEN-14\\|CLARIDEN-1[^0-9]\\|P-300-B\" labeling/auto/analyses/CLARIDEN_2026-10-*/*.md | head -50; grep -E '\"id\": \"CLARIDEN-(1|14|15)\"' labeling/auto/CLARIDEN.jsonl | cut -c1-400","description":"Look at period reports mentioning these labels"}}}
-{"type":"system","subtype":"task_summary","detail":"Look at period reports mentioning these labels","uuid":"d96f1d15-1e2f-45cc-a09b-552bb57e89c0","session_id":"1d552933-66a2-4aee-a79d-97df96c159c7"}
-{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_01C54NY2fnmVnWLiMhbPwqH3","type":"tool_result","content":"analysis.md\nd303b_tilt.png\nlabels.jsonl\nreport.md\nrequest.json\nrowB_1to3oct.png\nscripts\nwork\nlabeling/auto/analyses/CLARIDEN_2026-10-11T0000_2026-10-20T0400/analysis.md:23:- **CLARIDEN-1** (P-300-B Target issue): holds in the range. P-300-B is rejected at all 1187 instants (inventory), with error_value about 0.93.\nlabeling/auto/analyses/CLARIDEN_2026-10-11T0000_2026-10-20T0400/analysis.md:24:- **CLARIDEN-14** (drift of the 6th–11th, ends 11th 06:00): its in-range part (11th 00:00–06:00) is a plateau, which is consistent. But its sentence \"No camera movement\" is contradicted just before the range: the tilt goes from +0.8 (9th 00h) to −2.0 (11th) thousandths of a degree (6 h table, `work/tilt_vs_targets_6h.txt`), and D-306-B corr_y follows it down (0.045 → 0.022). This is outside my range (9th–11th); it is to be checked by whoever verifies the range of the 6th–11th.\nlabeling/auto/analyses/CLARIDEN_2026-10-11T0000_2026-10-20T0400/analysis.md:30:- **Precedents**: CLARIDEN-14 (its outward), reviewed.\nlabeling/auto/analyses/CLARIDEN_2026-10-11T0000_2026-10-20T0400/analysis.md:114:- Contradicted: CLARIDEN-14 and CLARIDEN-15 said \"No camera movement\", but the camera tilt does move by a few thousandths of a degree over days. This is small next to \"a few hundredths\" (DATA.md orders of magnitude), but enough to leave remainders of several noises on some targets. `stations.md` lists four references for CLARIDEN, while PR-296 is a fifth global reference retained at every instant.\nlabeling/auto/analyses/CLARIDEN_2026-10-20T0400_2026-11-01T0010/analysis.md:5:The task was to verify the 21 labels already on the range (`work/existing.jsonl`, all reviewed 2026-11-17) and the one spanning label (CLARIDEN-1).\nlabeling/auto/analyses/CLARIDEN_2026-10-20T0400_2026-11-01T0010/analysis.md:34:| CLARIDEN-1 (spanning) | holds | P-300-B is rejected at all 1690 instants of the range (inventory). Nothing to say. |\nlabeling/auto/analyses/CLARIDEN_2026-10-20T0400_2026-11-01T0010/analysis.md:92:- **20→22/10: row B in x drifts slowly** (6 h medians). D-306-B goes from +0.042 to +0.003, about 3.5 noises; P-301-B from −0.02 to −0.04; D-303-B a little; P-299-B goes up and back. In the image (rigid dx), D-306-B barely moves against the other targets (−0.006 → −0.018), so most of it comes from the base. It is small, without dates of its own, and overlaps the reviewed row B labels. If the expert wants it, it would continue the D-306-B horizontal decline already named in CLARIDEN-14.\nlabeling/auto/analyses/CLARIDEN_2026-10-20T0400_2026-11-01T0010/analysis.md:152:Earlier work: `instructions/analyst.md` (twice), `tools/GUIDE.md`, `tools/DATA.md`, `labeling/families.md`, `labeling/labeling-rules.md`, `labeling/reading-rules.md`, `labeling/stations.md`, `labeling/auto/CLARIDEN.jsonl` (labels at and around the range: CLARIDEN-1, 5, 11–15, 20–22), `work/existing.jsonl`, `work/spanning.jsonl`, `request.json`, `~/aimsight-data/extraction/stations.txt` (CLARIDEN line, no place). Precedents: `precedents.py` (WYOMING-17, NIEDERHORN-126, CLARIDEN-11, NORDEND-65/89, SNCF01-42). Tools: inventory, overview (common, residuals, rigid at 10 min and 6 h, with --follow), ranges (--rolling 6, --instants 3 and 4), days --bounds --smoothing 5, metrics (3 h and 1 h), summary (10 min, 30 min, 1 h, 6 h), plot. Raw: displacement CSVs (instants of all stations around the gaps), `metrics/` BusVoltage, last_sync, link, GPU on 30/10. Images: 20261030T1800Z, 20261031T1200Z (whole). No quality metrics on this camera (empty columns).\nlabeling/auto/analyses/CLARIDEN_2026-10-01T0000_2026-10-11T0000/analysis.md:3:Task: check the 12 existing labels of the range (`work/existing.jsonl`, CLARIDEN-2 to CLARIDEN-13, all reviewed on 2026-11-17) and the 2 spanning labels (`work/spanning.jsonl`: CLARIDEN-1 and CLARIDEN-14), then look for what they miss. Result: 16 labels in `labels.jsonl` (11 kept as they are, 1 corrected, 4 added, 0 removed).\nlabeling/auto/analyses/CLARIDEN_2026-10-01T0000_2026-10-11T0000/analysis.md:29:- **CLARIDEN-1** (P-300-B Target issue): holds within the range. P-300-B is rejected at all 1196 instants of the range.\nlabeling/auto/analyses/CLARIDEN_2026-10-01T0000_2026-10-11T0000/analysis.md:30:- **CLARIDEN-14** (Displacement, 6 Oct 22:00 → 11 Oct 06:00): the bounds and the family hold, but **its description is wrong within the range**. It says \"No camera movement\". In fact the camera tilt decreases steadily from about +0.007° (7 Oct) to about −0.0025° (10 Oct), with a step at 09:00 on 8 Oct. D-303-B's vertical rise follows this tilt (see added labels C and D below).\nlabeling/auto/analyses/CLARIDEN_2026-10-01T0000_2026-10-11T0000/analysis.md:74:### The link between D-303-B and the camera tilt (for C, D and CLARIDEN-14)\nlabeling/auto/analyses/CLARIDEN_2026-10-01T0000_2026-10-11T0000/analysis.md:75:Over 5 Oct 13:00 → 11 Oct 00:00 (hourly medians, 124 hours), D-303-B corr_y follows the camera tilt with r = −0.95. D-303-C corr_y (r = −0.91), D-304-C corr_y (r = −0.86) and D-301-C corr_x (r = −0.92) also follow it closely. These are exactly the targets and the directions that CLARIDEN-14 describes as drifting. Figure: `d303b_tilt.png` (D-303-B against the tilt, reversed, with the two steps in grey). The tilt itself drifts slowly from about +0.007° (7 Oct) to about −0.0025° (10 Oct), besides the two steps. The housing temperature stays at 39.7–40.7 °C, so this drift is not thermal.\nlabeling/auto/analyses/CLARIDEN_2026-10-01T0000_2026-10-11T0000/analysis.md:82:- **CLARIDEN-48**, 2026-10-08T08:50Z → 2026-10-08T09:10Z, Displacement: under the threshold. The camera tilt step is absorbed by the compensation for every target; the remainder on D-303-B corr_y reaches +4.2 own noises at 09:00–09:10 (+0.039 px, about 0.12 mm; level 03:00–08:50, noise 0.0092 px), no other sensor beyond 5 noises at k=5, and none with `--rolling 6h`. Its single point at 5.1 noises (11:20) is outside the label and inside the slow drift CLARIDEN-14.\nlabeling/auto/analyses/CLARIDEN_2026-10-01T0000_2026-10-11T0000/analysis.md:86:- **6 Oct 13:30 → 22:00**: D-303-B stays low after the step of C (smoothed −0.03 to −0.04). It is the level kept after the camera step, not a new event. From 18:00 it is inside CLARIDEN-12, from 22:00 inside CLARIDEN-14.\nlabeling/auto/analyses/CLARIDEN_2026-10-01T0000_2026-10-11T0000/analysis.md:89:- **9–10 Oct**: D-301-C corr_x and D-303-B corr_y above their level for long stretches. They are inside CLARIDEN-14 (the slow drift, which follows the camera tilt) and need no other label.\nlabeling/auto/analyses/CLARIDEN_2026-10-01T0000_2026-10-11T0000/analysis.md:98:- **Contradicted by the data**: CLARIDEN-14 says \"No camera movement\" and \"the camera housing temperature stays almost constant: no link with it\". The second part holds; the first does not: the camera tilt drifts over the same days and the drifting targets follow it closely (r −0.86 to −0.95). The label stays (it is outside this range's set and its bounds and family hold), but its description should be corrected the next time its range is verified: the drift is mostly a remainder of the camera tilt that the compensation does not absorb on these targets, not an established movement. In the catalogue it is \"The camera tilts little by little\" (the compensation corrects some targets better than others), not \"Targets move slowly, alone, then come back\".\n{\"id\": \"CLARIDEN-1\", \"start\": \"2026-10-01T00:00Z\", \"end\": \"2026-11-01T00:00Z\", \"family\": \"Target issue\", \"description\": \"The target P-300-B is rejected at every measurement of the batch: its recognition error stays almost at 1, its corrected curve is missing over the whole month. This has lasted since 29 September in the late afternoon, the time when the recognition error of other targets, includi\n{\"id\": \"CLARIDEN-14\", \"start\": \"2026-10-06T22:00Z\", \"end\": \"2026-10-11T06:00Z\", \"family\": \"Displacement\", \"description\": \"Slow drift of several targets over four days, made of small steps, then stabilization: D-303-B rises vertically, D-303-C and D-304-C rise vertically, D-301-C rises horizontally, D-306-B goes down horizontally. No camera movement, ordinary recognition error, nothing on the image","is_error":false}]},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"c11cab82-4489-4545-814d-ce4a7d1d06d4","timestamp":"2026-11-17T20:31:17.846Z","tool_use_result":{"stdout":"analysis.md\nd303b_tilt.png\nlabels.jsonl\nreport.md\nrequest.json\nrowB_1to3oct.png\nscripts\nwork\nlabeling/auto/analyses/CLARIDEN_2026-10-11T0000_2026-10-20T0400/analysis.md:23:- **CLARIDEN-1** (P-300-B Target issue): holds in the range. P-300-B is rejected at all 1187 instants (inventory), with error_value about 0.93.\nlabeling/auto/analyses/CLARIDEN_2026-10-11T0000_2026-10-20T0400/analysis.md:24:- **CLARIDEN-14** (drift of the 6th–11th, ends 11th 06:00): its in-range part (11th 00:00–06:00) is a plateau, which is consistent. But its sentence \"No camera movement\" is contradicted just before the range: the tilt goes from +0.8 (9th 00h) to −2.0 (11th) thousandths of a degree (6 h table, `work/tilt_vs_targets_6h.txt`), and D-306-B corr_y follows it down (0.045 → 0.022). This is outside my range (9th–11th); it is to be checked by whoever verifies the range of the 6th–11th.\nlabeling/auto/analyses/CLARIDEN_2026-10-11T0000_2026-10-20T0400/analysis.md:30:- **Precedents**: CLARIDEN-14 (its outward), reviewed.\nlabeling/auto/analyses/CLARIDEN_2026-10-11T0000_2026-10-20T0400/analysis.md:114:- Contradicted: CLARIDEN-14 and CLARIDEN-15 said \"No camera movement\", but the camera tilt does move by a few thousandths of a degree over days. This is small next to \"a few hundredths\" (DATA.md orders of magnitude), but enough to leave remainders of several noises on some targets. `stations.md` lists four references for CLARIDEN, while PR-296 is a fifth global reference retained at every instant.\nlabeling/auto/analyses/CLARIDEN_2026-10-20T0400_2026-11-01T0010/analysis.md:5:The task was to verify the 21 labels already on the range (`work/existing.jsonl`, all reviewed 2026-11-17) and the one spanning label (CLARIDEN-1).\nlabeling/auto/analyses/CLARIDEN_2026-10-20T0400_2026-11-01T0010/analysis.md:34:| CLARIDEN-1 (spanning) | holds | P-300-B is rejected at all 1690 instants of the range (inventory). Nothing to say. |\nlabeling/auto/analyses/CLARIDEN_2026-10-20T0400_2026-11-01T0010/analysis.md:92:- **20→22/10: row B in x drifts slowly** (6 h medians). D-306-B goes from +0.042 to +0.003, about 3.5 noises; P-301-B from −0.02 to −0.04; D-303-B a little; P-299-B goes up and back. In the image (rigid dx), D-306-B barely moves against the other targets (−0.006 → −0.018), so most of it comes from the base. It is small, without dates of its own, and overlaps the reviewed row B labels. If the expert wants it, it would continue the D-306-B horizontal decline already named in CLARIDEN-14.\nlabeling/auto/analyses/CLARIDEN_2026-10-20T0400_2026-11-01T0010/analysis.md:152:Earlier work: `instructions/analyst.md` (twice), `tools/GUIDE.md`, `tools/DATA.md`, `labeling/families.md`, `labeling/labeling-rules.md`, `labeling/reading-rules.md`, `labeling/stations.md`, `labeling/auto/CLARIDEN.jsonl` (labels at and around the range: CLARIDEN-1, 5, 11–15, 20–22), `work/existing.jsonl`, `work/spanning.jsonl`, `request.json`, `~/aimsight-data/extraction/stations.txt` (CLARIDEN line, no place). Precedents: `precedents.py` (WYOMING-17, NIEDERHORN-126, CLARIDEN-11, NORDEND-65/89, SNCF01-42). Tools: inventory, overview (common, residuals, rigid at 10 min and 6 h, with --follow), ranges (--rolling 6, --instants 3 and 4), days --bounds --smoothing 5, metrics (3 h and 1 h), summary (10 min, 30 min, 1 h, 6 h), plot. Raw: displacement CSVs (instants of all stations around the gaps), `metrics/` BusVoltage, last_sync, link, GPU on 30/10. Images: 20261030T1800Z, 20261031T1200Z (whole). No quality metrics on this camera (empty columns).\nlabeling/auto/analyses/CLARIDEN_2026-10-01T0000_2026-10-11T0000/analysis.md:3:Task: check the 12 existing labels of the range (`work/existing.jsonl`, CLARIDEN-2 to CLARIDEN-13, all reviewed on 2026-11-17) and the 2 spanning labels (`work/spanning.jsonl`: CLARIDEN-1 and CLARIDEN-14), then look for what they miss. Result: 16 labels in `labels.jsonl` (11 kept as they are, 1 corrected, 4 added, 0 removed).\nlabeling/auto/analyses/CLARIDEN_2026-10-01T0000_2026-10-11T0000/analysis.md:29:- **CLARIDEN-1** (P-300-B Target issue): holds within the range. P-300-B is rejected at all 1196 instants of the range.\nlabeling/auto/analyses/CLARIDEN_2026-10-01T0000_2026-10-11T0000/analysis.md:30:- **CLARIDEN-14** (Displacement, 6 Oct 22:00 → 11 Oct 06:00): the bounds and the family hold, but **its description is wrong within the range**. It says \"No camera movement\". In fact the camera tilt decreases steadily from about +0.007° (7 Oct) to about −0.0025° (10 Oct), with a step at 09:00 on 8 Oct. D-303-B's vertical rise follows this tilt (see added labels C and D below).\nlabeling/auto/analyses/CLARIDEN_2026-10-01T0000_2026-10-11T0000/analysis.md:74:### The link between D-303-B and the camera tilt (for C, D and CLARIDEN-14)\nlabeling/auto/analyses/CLARIDEN_2026-10-01T0000_2026-10-11T0000/analysis.md:75:Over 5 Oct 13:00 → 11 Oct 00:00 (hourly medians, 124 hours), D-303-B corr_y follows the camera tilt with r = −0.95. D-303-C corr_y (r = −0.91), D-304-C corr_y (r = −0.86) and D-301-C corr_x (r = −0.92) also follow it closely. These are exactly the targets and the directions that CLARIDEN-14 describes as drifting. Figure: `d303b_tilt.png` (D-303-B against the tilt, reversed, with the two steps in grey). The tilt itself drifts slowly from about +0.007° (7 Oct) to about −0.0025° (10 Oct), besides the two steps. The housing temperature stays at 39.7–40.7 °C, so this drift is not thermal.\nlabeling/auto/analyses/CLARIDEN_2026-10-01T0000_2026-10-11T0000/analysis.md:82:- **CLARIDEN-48**, 2026-10-08T08:50Z → 2026-10-08T09:10Z, Displacement: under the threshold. The camera tilt step is absorbed by the compensation for every target; the remainder on D-303-B corr_y reaches +4.2 own noises at 09:00–09:10 (+0.039 px, about 0.12 mm; level 03:00–08:50, noise 0.0092 px), no other sensor beyond 5 noises at k=5, and none with `--rolling 6h`. Its single point at 5.1 noises (11:20) is outside the label and inside the slow drift CLARIDEN-14.\nlabeling/auto/analyses/CLARIDEN_2026-10-01T0000_2026-10-11T0000/analysis.md:86:- **6 Oct 13:30 → 22:00**: D-303-B stays low after the step of C (smoothed −0.03 to −0.04). It is the level kept after the camera step, not a new event. From 18:00 it is inside CLARIDEN-12, from 22:00 inside CLARIDEN-14.\nlabeling/auto/analyses/CLARIDEN_2026-10-01T0000_2026-10-11T0000/analysis.md:89:- **9–10 Oct**: D-301-C corr_x and D-303-B corr_y above their level for long stretches. They are inside CLARIDEN-14 (the slow drift, which follows the camera tilt) and need no other label.\nlabeling/auto/analyses/CLARIDEN_2026-10-01T0000_2026-10-11T0000/analysis.md:98:- **Contradicted by the data**: CLARIDEN-14 says \"No camera movement\" and \"the camera housing temperature stays almost constant: no link with it\". The second part holds; the first does not: the camera tilt drifts over the same days and the drifting targets follow it closely (r −0.86 to −0.95). The label stays (it is outside this range's set and its bounds and family hold), but its description should be corrected the next time its range is verified: the drift is mostly a remainder of the camera tilt that the compensation does not absorb on these targets, not an established movement. In the catalogue it is \"The camera tilts little by little\" (the compensation corrects some targets better than others), not \"Targets move slowly, alone, then come back\".\n{\"id\": \"CLARIDEN-1\", \"start\": \"2026-10-01T00:00Z\", \"end\": \"2026-11-01T00:00Z\", \"family\": \"Target issue\", \"description\": \"The target P-300-B is rejected at every measurement of the batch: its recognition error stays almost at 1, its corrected curve is missing over the whole month. This has lasted since 29 September in the late afternoon, the time when the recognition error of other targets, includi\n{\"id\": \"CLARIDEN-14\", \"start\": \"2026-10-06T22:00Z\", \"end\": \"2026-10-11T06:00Z\", \"family\": \"Displacement\", \"description\": \"Slow drift of several targets over four days, made of small steps, then stabilization: D-303-B rises vertically, D-303-C and D-304-C rise vertically, D-301-C rises horizontally, D-306-B goes down horizontally. No camera movement, ordinary recognition error, nothing on the image","stderr":"","interrupted":false,"isImage":false,"noOutputExpected":false},"tool_result_meta":[{"id":"toolu_01C54NY2fnmVnWLiMhbPwqH3","permission_decision":{"decision":"accept","source":"config","reason_type":"rule"}}]}
-{"type":"system","subtype":"thinking_tokens","estimated_tokens":50,"estimated_tokens_delta":50,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"774f745c-18a3-4a2e-8e4d-08c58b7f9560"}
-{"type":"system","subtype":"thinking_tokens","estimated_tokens":150,"estimated_tokens_delta":100,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"472a9cd8-f4a9-45ac-8616-a47582fa3e7f"}
-{"type":"system","subtype":"thinking_tokens","estimated_tokens":250,"estimated_tokens_delta":100,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"a8498adc-55be-47de-8b9f-9ca257b66cee"}
-{"type":"system","subtype":"thinking_tokens","estimated_tokens":350,"estimated_tokens_delta":100,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"3437803c-9226-4d6a-a711-0b2b50f6aa1c"}
-{"type":"system","subtype":"thinking_tokens","estimated_tokens":459,"estimated_tokens_delta":109,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"df0c97fe-99e7-4124-83e6-30d72e826e55"}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98o3Q4dTGQHV8rkJpbi","type":"message","role":"assistant","content":[{"type":"thinking","thinking":"","signature":"CAQSpQ4KEAgTGAI4AUIIdGhpbmtpbmcSDPOHhmHJ1pTxX15PmxoMAF+Fr4Y3BvJpLimEIjCln3UJTIhL7nOJHRSKiDKlDVCE6ucx/zHB1akrr/N5NDFAnwRQYjE4vNv1Fh4Om/Mqwg0GnXd/4dFSh5ynRVJqG1GPkwMq+QDLJ3fc88Y+n5x1FO5SDnKtU9ASV7EMOIk5+y4OgagR9RDRJmJg0hiiXwOUR7/9OO9spijLoxMStTb54QfcUbBAyW/4DBLd/TkY/7EizyE35tysAZ1C6+T1oJKf9qMuQu2Lv4hy7Sb37Q4iTeqJEPSgZYwuEpP+L9cYCFTyzqPkQq0flHbnH7OmTJXffeOBzwIQfUoQP+Kajm7ICBSPqpciVi0CEdjW+g2Uj2oPtHSe0xpzHJ+gaM6g8cu7aDOAOqydB6kA2XJlAWBGnA6GfOIxF+WfzAYXU9D45pCCZY2eL+HzXeuOaNvNcEes8D/xNFF79f/Fkn6zilFJXKA9Vk/8ripheT/zorBim3Y65HwtyaTLEAHJC3bdJQII5CRiVqvS8iDRP2cMSRrZC8zt8NEAYY9jxfnTtf6SCVeKs8aEHSXyctaU1eTZ5S0fj0Zf+eO+vjV3X7g8w21/41J3yqdyxrpKIGgr4rEyYvZ3NSnRAmMrNptQ04jZHDRh9YLr9xAz4V3Yzzwh05iX7Ffzy1cWqBykFFYOOr4aRkMM4q3aM/7zbuMKJBqbDqVhbjWp1UXWNbCNQ20hgajU2skf4eikGfp3VfYtOhlxX7is6gz4tZJHr0gqRevAJvyBh3edWMPWKsfvBdh9LnX2alOUol/2WajId1FynAw8M0h+Wzk9gyDlWR1Ju7aI+5qs8T1uPcq5lNBXKsEefs0UPlEpn2Wk3nc/QlKHC6dUN7X9sDji22/NyS8X4R2j86YvbWYqYuvu7atmioJyJ4dUYWYwFavY/4zTsGTlX46w2zfhtCIZbGafso8KV011sbKpXIfGTNfjf7+Htg0GaviIfibBzRoszNYId/uN6ohb3NWsLsR10neekMBg5uK42mU+ivtxts834XoWKdB4JSA79EAVfbw1T2QmD8JFMeM1muGVmks4p9KJPNPeP86AFL1bPJ4IWc9kkkF55ZEzgZ4wWMazdWc30JGHVNh4TbGhWMSCHkQyO7Ks63PjB/Y4uf2WJXj37CEjFGFUAJoiCLLoo28d6YNq8A7bGPRYbyFrbY623nrpWZ14S62hFxJfiT8mmIANoeJv/x04A6L22rkByiPPKz28HlYQ5zZ2GVI03Ymzcj0AN0AfsfBRYt5HCxSXa5MsODzstHgJBVYGoAgxge1GRsFGlUvdTefBYB5JQ2Q/VRnIktCJSm/URVquIxGiTIPCky9BrjQYb+3eD59KMjWzwxEOhBJgSplcA3n43TnEGe/xGMf/7UDQMIe3q5GHfWZrg7O4TgyOIHQSteeBkpqkFiwDSMeIoOpXkJCD7eV3TDOdwPDT1IGQzOrTN5OU4WlTliE/ZUlers/oAi9L5+g7RCoZv4/xI9Ivm7I7mVsLM/Lium4GVbOiLc/8iHh7D9Kz/qv4B6HRCG0l49DFP7IVikNXyCnK1d2GV3XYN6u46fB4mEHdfj7h8cEp6vhqBU447tOrY8wm0IqMlPp0n/dIoyWOMi7YfhRIeI401dKrXnBMdbwT7jR1XbHqDewAROLRYB8xrw6sEIpDaXfin9oXl1w9YXCb6n+Tc2NaxVJi1GW1Djv4YyaOOYajK89u7tU/HDjwunblHfpN5ke/hL6GwLUxIFgS5dWmv2YmbRXfJNaPJYVO5vc7ebzmk8PnK3gBttJ185Lx8X4oDJ5fOF4jR2vbM6FJPom5yKoHQRE3V432hWflKopOEQC+BQK7v8cB9XQ3Wvl/YYp+dOKZKemk8O1snB/PzUCai9kGe3vdyTB2Z5NnAA7O2bKehvB0T7zRAnT+3taxbw9p7E58TLzeoNQBnndb32MBGZpVI9jLMPYeOE+aBQgByi6qkvS5GTMMUTlzGrvfjUqfSbkkk0qPFqSXYARF+4F7Dh2u/FOGE0TVJ9Y6fi3eS5zlAUQ/ENqwzxZ41f4UMWp6bxIOFVleDZiVnrqQjOGBXM/G/ptM0cWzalg0NjWUP4ME9VdmepOYMpAraBgzT+NNU6+AIVVx4aCbHfZ04oINw9m7rP/1ArCiG8r3rjmlv7rCB0/l4eWABXUEey+giKaqfIZ2vpQGPgD8xET0ikyUof6gbXdXfafJaoXi9OZAEsVklubPM89+kzAjPJ3Kwax5rSTTLtwx70QS/D5K9PtpTW0ft+ul66qC4y+B1LrnDFm9uu4VBRZ0wuvj936hDC+AJ7CrfQT72rq67WZj2J8Y7o2TRKsdWRLFhzWuo9D9T39cuLWzn4tnl/9pVG/Gx8nkGocJH3gbP/eI+6thLnfpx3zoiETVZRgB"}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":4158,"cache_read_input_tokens":51188,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":4158},"output_tokens":8,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"938cb81a-5d29-42e2-afdd-839f27c9527c","timestamp":"2026-11-17T20:31:23.988Z","request_id":"req_011Ch98o39RbK77mZF4dJrwk","thinking_duration_ms":4606,"thinking_display":"updates"}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98o3Q4dTGQHV8rkJpbi","type":"message","role":"assistant","content":[{"type":"tool_use","id":"toolu_01YD6yisxBiPmQw58atsY85W","name":"Bash","input":{"command":"cd /home/maxime/aimsight-app; O=labeling/auto/analyses/long-labels/CLARIDEN/work; python3 tools/scripts/inventory.py data/CLARIDEN --start 2026-10-01T00:00Z --end 2026-11-01T00:00Z > $O/inv_month.txt; grep -n \"P-300-B\\|Cadence\\|cadence\\|instants\" $O/inv_month.txt | head -20; grep -E '\"id\": \"CLARIDEN-15\"' labeling/auto/CLARIDEN.jsonl | cut -c1-600","description":"Inventory month, P-300-B rejections"},"caller":{"type":"direct"}}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":4158,"cache_read_input_tokens":51188,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":4158},"output_tokens":8,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"6de739a6-3738-463a-b98c-52ad535da3b0","timestamp":"2026-11-17T20:31:25.897Z","request_id":"req_011Ch98o39RbK77mZF4dJrwk","wire_tool_inputs":{"toolu_01YD6yisxBiPmQw58atsY85W":{"command":"cd /home/maxime/aimsight-app; O=labeling/auto/analyses/long-labels/CLARIDEN/work; python3 tools/scripts/inventory.py data/CLARIDEN --start 2026-10-01T00:00Z --end 2026-11-01T00:00Z > $O/inv_month.txt; grep -n \"P-300-B\\|Cadence\\|cadence\\|instants\" $O/inv_month.txt | head -20; grep -E '\"id\": \"CLARIDEN-15\"' labeling/auto/CLARIDEN.jsonl | cut -c1-600","description":"Inventory month, P-300-B rejections"}}}
-{"type":"system","subtype":"task_started","task_id":"brn40qceu","run_id":"0mwl5e2ep-6edc085f","tool_use_id":"toolu_01YD6yisxBiPmQw58atsY85W","description":"Inventory month, P-300-B rejections","is_backgrounded":false,"task_type":"local_bash","uuid":"10c40145-6309-4e23-a31b-b9c0bce680bb","session_id":"1d552933-66a2-4aee-a79d-97df96c159c7"}
-{"type":"system","subtype":"task_notification","task_id":"brn40qceu","run_id":"0mwl5e2ep-6edc085f","tool_use_id":"toolu_01YD6yisxBiPmQw58atsY85W","status":"completed","output_file":"","summary":"Inventory month, P-300-B rejections","uuid":"2d7d224c-3c5a-46c1-9301-0c8fcdabf6be","session_id":"1d552933-66a2-4aee-a79d-97df96c159c7"}
-{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_01YD6yisxBiPmQw58atsY85W","type":"tool_result","content":"51:Measurement period: 2026-09-01T00:00Z → 2026-11-17T08:30Z, 10137 instants\n52:Cadence (median step): 10 min\n53:Missing measurements (instants absent from the cadence): 1003\n110:P-300-B target target 0.7 10137 6371 13.12 5.215\n117:Measurement instants without a pose (no registration): 235 of 10137\n119:Window 2026-10-01T00:00Z → 2026-11-01T00:00Z: 4070 instants present\n120:Steps absent for all sensors, between two present instants (cadence of 10 min):\n137:Present instants where sensors have no measurement:\n148: P-300-B (4070): 2026-10-01T00:00Z → 2026-10-03T07:40Z (335); 2026-10-03T08:00Z → 17:40Z (59); 2026-10-05T10:30Z → 2026-10-15T22:50Z (1515); 2026-10-16T10:30Z → 14:20Z (24); 2026-10-16T14:40Z → 2026-10-18T13:50Z (284); 2026-10-18T23:30Z → 2026-10-19T09:00Z (58); 2026-10-19T09:30Z; 2026-10-19T09:50Z; 2026-10-19T10:10Z → 20:40Z (64); 2026-10-19T21:10Z; 2026-10-19T21:30Z → 2026-10-20T06:10Z (53); 2026-10-20T06:30Z → 20:40Z (86); 2026-10-20T21:40Z → 2026-10-26T14:30Z (822); 2026-10-26T15:10Z → 2026-10-27T09:00Z (108); 2026-10-27T09:30Z → 2026-10-29T14:50Z (321); 2026-10-29T15:10Z → 2026-10-30T17:00Z (156); 2026-10-30T17:50Z → 2026-11-01T00:00Z (182)\n149:Retained references by the compensation (inlier = 1) out of 5, number of instants: 5: 4065, 4: 5\n157:Measurement instants without a pose (no registration): 0 of 4070","is_error":false}]},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"c0e96da4-4006-472f-bf73-5c084b5a4a23","timestamp":"2026-11-17T20:31:38.663Z","tool_use_result":{"stdout":"51:Measurement period: 2026-09-01T00:00Z → 2026-11-17T08:30Z, 10137 instants\n52:Cadence (median step): 10 min\n53:Missing measurements (instants absent from the cadence): 1003\n110:P-300-B target target 0.7 10137 6371 13.12 5.215\n117:Measurement instants without a pose (no registration): 235 of 10137\n119:Window 2026-10-01T00:00Z → 2026-11-01T00:00Z: 4070 instants present\n120:Steps absent for all sensors, between two present instants (cadence of 10 min):\n137:Present instants where sensors have no measurement:\n148: P-300-B (4070): 2026-10-01T00:00Z → 2026-10-03T07:40Z (335); 2026-10-03T08:00Z → 17:40Z (59); 2026-10-05T10:30Z → 2026-10-15T22:50Z (1515); 2026-10-16T10:30Z → 14:20Z (24); 2026-10-16T14:40Z → 2026-10-18T13:50Z (284); 2026-10-18T23:30Z → 2026-10-19T09:00Z (58); 2026-10-19T09:30Z; 2026-10-19T09:50Z; 2026-10-19T10:10Z → 20:40Z (64); 2026-10-19T21:10Z; 2026-10-19T21:30Z → 2026-10-20T06:10Z (53); 2026-10-20T06:30Z → 20:40Z (86); 2026-10-20T21:40Z → 2026-10-26T14:30Z (822); 2026-10-26T15:10Z → 2026-10-27T09:00Z (108); 2026-10-27T09:30Z → 2026-10-29T14:50Z (321); 2026-10-29T15:10Z → 2026-10-30T17:00Z (156); 2026-10-30T17:50Z → 2026-11-01T00:00Z (182)\n149:Retained references by the compensation (inlier = 1) out of 5, number of instants: 5: 4065, 4: 5\n157:Measurement instants without a pose (no registration): 0 of 4070","stderr":"","interrupted":false,"isImage":false,"noOutputExpected":false},"tool_result_meta":[{"id":"toolu_01YD6yisxBiPmQw58atsY85W","permission_decision":{"decision":"accept","source":"config","reason_type":"rule"}}]}
-{"type":"system","subtype":"thinking_tokens","estimated_tokens":50,"estimated_tokens_delta":50,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"74686764-b152-462a-8b28-f7c3fb68815a"}
-{"type":"system","subtype":"thinking_tokens","estimated_tokens":198,"estimated_tokens_delta":148,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"7ffe7321-3efd-4d60-afef-1eae746792bb"}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98paKw1bGkTitgZX2im","type":"message","role":"assistant","content":[{"type":"thinking","thinking":"","signature":"CAQSjQYKEAgTGAI4AUIIdGhpbmtpbmcSDAREd/2DJVV+LbZ/fxoM3Y/gjFCSWexm9NqcIjDDfozCgKVLUm+8BY6hXpBge23bQyRe/gETF4o+n2PoxyxTw6jA6rIswwrDhuo/tRcqqgVVgGDmqPt9cZyGmYjzRCeopNCMGNrECFImj1xCh4sjF6FbfXju1zQ7YcpPpGz7FQSw0dN5TpRLSxMIvir5JZQIvmpayA2hcju4DyBZnFSNPTkIDjQi8YVzb7QHHTFi7TO9lrxZs0J/g/a318NbWV5d4erq8CU8VOL2SsP0Ynh1ewdy6ym9tktip/phKRBHB9voebJMk6xKxy3II8gs0h+WbBN3iEMhI5D/kfj1g/qT8N5BnbyR/51Mvz3i8z0ycrLD75NLyqTIWO7TVcni7Io2nDx3oOE/TFf7NHC0WhkfTFfFAnrXcxCfEG/AvIGnxORuW5qWDbnpatNzoLBOewcLF9riL2BfMujr1+8RSfA/0mzFJs3XXxiofW/UHw7NlPppytWibqZZw5Mwtb6Fs/dewqWWNROwStndYrWXAm7t3C0Xc05Z/xJ6p/JaEbeeSnII6CB6qesZzS+NVWklOVDj7G3W2r1NydIQN5iX9z0c8/ciUp0Jeca3+y/5EShNgwS/iHsw8wpNaKS2bTh1QOD/FifC/JrSS1uo/UOdTU3CD/ZN7TjXaXbA1uGleUENCzIPyoCiHkn9qOvDvN8cI57BbjkzeiJQFCkxQAC1DsE/KdQN7cDM76TMbRJTxTD+kt8gKR5Fr0Y3xJVIuh33COIRMbhvLrmGtfmcy3xFE+t4Tnq6Z140QPEJf/LTj/gk2HTObRBATNezn7qLo0l2b4MCqK0UktAGvJYQ3pDKfFCYorcAImA1UJXXiA1hNkYr3UoJeko81/WbA4oXhNNDoVbH1pDLoyLgTXn2UaP8zEIe+ysx7QIITsJ9mlzkQDgY6ClvgRbUF2fuc8nzOpUahDIsSvBTJhe8lH17yqqwDrDBRQX7ReyBzq1jGLfSjcjCZ2CiOAFvbk7tlAouGAE="}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":1477,"cache_read_input_tokens":55346,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":1477},"output_tokens":8,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"e340be24-aebb-4623-b3d6-a41e3c2a92be","timestamp":"2026-11-17T20:31:41.474Z","request_id":"req_011Ch98pa6YZUhtNdKrzzVGn","thinking_duration_ms":1306,"thinking_display":"updates"}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98paKw1bGkTitgZX2im","type":"message","role":"assistant","content":[{"type":"text","text":"Checking P-300-B's rejection rate over October (it looks rejected at every measurement), then I'll measure the CLARIDEN-14 drift against the 5-noise rule."}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":1477,"cache_read_input_tokens":55346,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":1477},"output_tokens":8,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"db0d23cc-ca8f-4192-854c-419d232be8ab","timestamp":"2026-11-17T20:31:41.476Z","request_id":"req_011Ch98pa6YZUhtNdKrzzVGn"}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98paKw1bGkTitgZX2im","type":"message","role":"assistant","content":[{"type":"tool_use","id":"toolu_01V9iZQiTaQKNM5Ci58VXY9V","name":"Read","input":{"file_path":"/home/maxime/aimsight-app/labeling/auto/analyses/long-labels/CLARIDEN/work/inv_month.txt","offset":95,"limit":60},"caller":{"type":"direct"}}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":1477,"cache_read_input_tokens":55346,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":1477},"output_tokens":8,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"a1c4d124-f0d7-4953-a03f-b2b238ea79be","timestamp":"2026-11-17T20:31:42.385Z","request_id":"req_011Ch98pa6YZUhtNdKrzzVGn","wire_tool_inputs":{"toolu_01V9iZQiTaQKNM5Ci58VXY9V":{"file_path":"/home/maxime/aimsight-app/labeling/auto/analyses/long-labels/CLARIDEN/work/inv_month.txt","offset":95,"limit":60}}}
-{"type":"rate_limit_event","rate_limit_info":{"status":"allowed_warning","resetsAt":1794954600,"rateLimitType":"five_hour","utilization":0.99,"isUsingOverage":false,"surpassedThreshold":0.9,"rateLimitGraceActive":true,"unifiedWindows":{"five_hour":{"utilization":0.99,"resetsAt":1794954600,"status":"allowed_warning","surpassedThreshold":0.9},"seven_day":{"utilization":0.72,"resetsAt":1795302000,"status":"allowed"}},"overageEnabled":false},"uuid":"10a8319e-7b34-4d46-9b27-0b55ac21804b","session_id":"1d552933-66a2-4aee-a79d-97df96c159c7"}
-{"type":"system","subtype":"task_summary","detail":"Reading labeling/auto/analyses/long-labels/CLARIDEN/work/inv_month.txt","uuid":"79da2ad0-d3e3-4c5e-a948-4d06080ada7c","session_id":"1d552933-66a2-4aee-a79d-97df96c159c7"}
-{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_01V9iZQiTaQKNM5Ci58VXY9V","type":"tool_result","content":"95\tD-302-B target target 0.7 10137 2 9.409 3.752\n96\tD-302_A target target 0.7 10137 2 10.42 3.772\n97\tD-303-A target target 0.7 10137 1 8.67 3.074\n98\tD-303-B target target 0.7 10137 28 7.83 3.132\n99\tD-303-C target target 0.7 10137 10 9.33 3.485\n100\tD-304-A target target 0.7 10137 2 7.3 2.536\n101\tD-304-B target target 0.7 10137 0 6.4 2.557\n102\tD-304-C target target 0.7 10137 5 8.1 2.989\n103\tD-306-B target target 0.7 10137 0 2.14 0.821\n104\tP-298-A target target 0.7 10137 1 16.87 6.444\n105\tP-298-B target target 0.7 10137 2 16.75 6.592\n106\tP-298-C target target 0.7 10137 4 17.36 6.927\n107\tP-299-A target target 0.7 10137 1 15.37 5.810\n108\tP-299-B target target 0.7 10137 2 15.06 6.000\n109\tP-299-C target target 0.7 10137 3 15.54 6.192\n110\tP-300-B target target 0.7 10137 6371 13.12 5.215\n111\tP-301-B target target 0.7 10137 2 11.23 4.488\n112\tPR-283 target ref 0.7 10137 1970 - -\n113\tPR-284 target ref 0.7 10137 38 - -\n114\tPR_BG target target 0.7 10137 40 30 11.963\n115\t\n116\tCamera pose over the whole period: 9902 registrations, 2026-09-01T00:00Z → 2026-11-16T00:20Z\n117\tMeasurement instants without a pose (no registration): 235 of 10137\n118\t\n119\tWindow 2026-10-01T00:00Z → 2026-11-01T00:00Z: 4070 instants present\n120\tSteps absent for all sensors, between two present instants (cadence of 10 min):\n121\t between 2026-10-03T07:40Z and 2026-10-03T08:00Z: 1\n122\t between 2026-10-03T17:40Z and 2026-10-05T10:30Z: 244\n123\t between 2026-10-15T22:50Z and 2026-10-16T10:30Z: 69\n124\t between 2026-10-16T14:20Z and 2026-10-16T14:40Z: 1\n125\t between 2026-10-18T13:50Z and 2026-10-18T23:30Z: 57\n126\t between 2026-10-19T09:00Z and 2026-10-19T09:30Z: 2\n127\t between 2026-10-19T09:30Z and 2026-10-19T09:50Z: 1\n128\t between 2026-10-19T09:50Z and 2026-10-19T10:10Z: 1\n129\t between 2026-10-19T20:40Z and 2026-10-19T21:10Z: 2\n130\t between 2026-10-19T21:10Z and 2026-10-19T21:30Z: 1\n131\t between 2026-10-20T06:10Z and 2026-10-20T06:30Z: 1\n132\t between 2026-10-20T20:40Z and 2026-10-20T21:40Z: 5\n133\t between 2026-10-26T14:30Z and 2026-10-26T15:10Z: 3\n134\t between 2026-10-27T09:00Z and 2026-10-27T09:30Z: 2\n135\t between 2026-10-29T14:50Z and 2026-10-29T15:10Z: 1\n136\t between 2026-10-30T17:00Z and 2026-10-30T17:50Z: 4\n137\tPresent instants where sensors have no measurement:\n138\t (none)\n139\tRejected measurements in the window, per sensor (start → end of each run of consecutive steps, count):\n140\t D-302-C (1): 2026-10-05T12:20Z\n141\t PR-295 (4): 2026-10-31T19:50Z; 2026-10-31T22:30Z → 22:40Z (2); 2026-10-31T23:10Z\n142\t D-300-C (1): 2026-10-05T12:20Z\n143\t D-301-C (1): 2026-10-05T12:20Z\n144\t D-303-C (1): 2026-10-05T12:20Z\n145\t D-304-C (2): 2026-10-05T10:30Z; 2026-10-05T12:20Z\n146\t P-298-C (1): 2026-10-05T12:20Z\n147\t P-299-C (1): 2026-10-05T12:20Z\n148\t P-300-B (4070): 2026-10-01T00:00Z → 2026-10-03T07:40Z (335); 2026-10-03T08:00Z → 17:40Z (59); 2026-10-05T10:30Z → 2026-10-15T22:50Z (1515); 2026-10-16T10:30Z → 14:20Z (24); 2026-10-16T14:40Z → 2026-10-18T13:50Z (284); 2026-10-18T23:30Z → 2026-10-19T09:00Z (58); 2026-10-19T09:30Z; 2026-10-19T09:50Z; 2026-10-19T10:10Z → 20:40Z (64); 2026-10-19T21:10Z; 2026-10-19T21:30Z → 2026-10-20T06:10Z (53); 2026-10-20T06:30Z → 20:40Z (86); 2026-10-20T21:40Z → 2026-10-26T14:30Z (822); 2026-10-26T15:10Z → 2026-10-27T09:00Z (108); 2026-10-27T09:30Z → 2026-10-29T14:50Z (321); 2026-10-29T15:10Z → 2026-10-30T17:00Z (156); 2026-10-30T17:50Z → 2026-11-01T00:00Z (182)\n149\tRetained references by the compensation (inlier = 1) out of 5, number of instants: 5: 4065, 4: 5\n150\tInstants where references are not retained (runs of consecutive steps with the same references out; r = rejected, empty = inlier empty, otherwise the inlier value):\n151\t 2026-10-05T12:20Z: 4 retained; out: D-302-C (r)\n152\t 2026-10-31T19:50Z: 4 retained; out: PR-295 (r)\n153\t 2026-10-31T22:30Z → 22:40Z (2): 4 retained; out: PR-295 (r)\n154\t 2026-10-31T23:10Z: 4 retained; out: PR-295 (r)"}]},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"c3c2a07e-6d05-43a0-8b77-53a3a6dec03c","timestamp":"2026-11-17T20:31:42.408Z","tool_use_result":{"type":"text","file":{"filePath":"/home/maxime/aimsight-app/labeling/auto/analyses/long-labels/CLARIDEN/work/inv_month.txt","content":"D-302-B target target 0.7 10137 2 9.409 3.752\nD-302_A target target 0.7 10137 2 10.42 3.772\nD-303-A target target 0.7 10137 1 8.67 3.074\nD-303-B target target 0.7 10137 28 7.83 3.132\nD-303-C target target 0.7 10137 10 9.33 3.485\nD-304-A target target 0.7 10137 2 7.3 2.536\nD-304-B target target 0.7 10137 0 6.4 2.557\nD-304-C target target 0.7 10137 5 8.1 2.989\nD-306-B target target 0.7 10137 0 2.14 0.821\nP-298-A target target 0.7 10137 1 16.87 6.444\nP-298-B target target 0.7 10137 2 16.75 6.592\nP-298-C target target 0.7 10137 4 17.36 6.927\nP-299-A target target 0.7 10137 1 15.37 5.810\nP-299-B target target 0.7 10137 2 15.06 6.000\nP-299-C target target 0.7 10137 3 15.54 6.192\nP-300-B target target 0.7 10137 6371 13.12 5.215\nP-301-B target target 0.7 10137 2 11.23 4.488\nPR-283 target ref 0.7 10137 1970 - -\nPR-284 target ref 0.7 10137 38 - -\nPR_BG target target 0.7 10137 40 30 11.963\n\nCamera pose over the whole period: 9902 registrations, 2026-09-01T00:00Z → 2026-11-16T00:20Z\nMeasurement instants without a pose (no registration): 235 of 10137\n\nWindow 2026-10-01T00:00Z → 2026-11-01T00:00Z: 4070 instants present\nSteps absent for all sensors, between two present instants (cadence of 10 min):\n between 2026-10-03T07:40Z and 2026-10-03T08:00Z: 1\n between 2026-10-03T17:40Z and 2026-10-05T10:30Z: 244\n between 2026-10-15T22:50Z and 2026-10-16T10:30Z: 69\n between 2026-10-16T14:20Z and 2026-10-16T14:40Z: 1\n between 2026-10-18T13:50Z and 2026-10-18T23:30Z: 57\n between 2026-10-19T09:00Z and 2026-10-19T09:30Z: 2\n between 2026-10-19T09:30Z and 2026-10-19T09:50Z: 1\n between 2026-10-19T09:50Z and 2026-10-19T10:10Z: 1\n between 2026-10-19T20:40Z and 2026-10-19T21:10Z: 2\n between 2026-10-19T21:10Z and 2026-10-19T21:30Z: 1\n between 2026-10-20T06:10Z and 2026-10-20T06:30Z: 1\n between 2026-10-20T20:40Z and 2026-10-20T21:40Z: 5\n between 2026-10-26T14:30Z and 2026-10-26T15:10Z: 3\n between 2026-10-27T09:00Z and 2026-10-27T09:30Z: 2\n between 2026-10-29T14:50Z and 2026-10-29T15:10Z: 1\n between 2026-10-30T17:00Z and 2026-10-30T17:50Z: 4\nPresent instants where sensors have no measurement:\n (none)\nRejected measurements in the window, per sensor (start → end of each run of consecutive steps, count):\n D-302-C (1): 2026-10-05T12:20Z\n PR-295 (4): 2026-10-31T19:50Z; 2026-10-31T22:30Z → 22:40Z (2); 2026-10-31T23:10Z\n D-300-C (1): 2026-10-05T12:20Z\n D-301-C (1): 2026-10-05T12:20Z\n D-303-C (1): 2026-10-05T12:20Z\n D-304-C (2): 2026-10-05T10:30Z; 2026-10-05T12:20Z\n P-298-C (1): 2026-10-05T12:20Z\n P-299-C (1): 2026-10-05T12:20Z\n P-300-B (4070): 2026-10-01T00:00Z → 2026-10-03T07:40Z (335); 2026-10-03T08:00Z → 17:40Z (59); 2026-10-05T10:30Z → 2026-10-15T22:50Z (1515); 2026-10-16T10:30Z → 14:20Z (24); 2026-10-16T14:40Z → 2026-10-18T13:50Z (284); 2026-10-18T23:30Z → 2026-10-19T09:00Z (58); 2026-10-19T09:30Z; 2026-10-19T09:50Z; 2026-10-19T10:10Z → 20:40Z (64); 2026-10-19T21:10Z; 2026-10-19T21:30Z → 2026-10-20T06:10Z (53); 2026-10-20T06:30Z → 20:40Z (86); 2026-10-20T21:40Z → 2026-10-26T14:30Z (822); 2026-10-26T15:10Z → 2026-10-27T09:00Z (108); 2026-10-27T09:30Z → 2026-10-29T14:50Z (321); 2026-10-29T15:10Z → 2026-10-30T17:00Z (156); 2026-10-30T17:50Z → 2026-11-01T00:00Z (182)\nRetained references by the compensation (inlier = 1) out of 5, number of instants: 5: 4065, 4: 5\nInstants where references are not retained (runs of consecutive steps with the same references out; r = rejected, empty = inlier empty, otherwise the inlier value):\n 2026-10-05T12:20Z: 4 retained; out: D-302-C (r)\n 2026-10-31T19:50Z: 4 retained; out: PR-295 (r)\n 2026-10-31T22:30Z → 22:40Z (2): 4 retained; out: PR-295 (r)\n 2026-10-31T23:10Z: 4 retained; out: PR-295 (r)","numLines":60,"startLine":95,"totalLines":158}},"tool_result_meta":[{"id":"toolu_01V9iZQiTaQKNM5Ci58VXY9V","permission_decision":{"decision":"accept","source":"config","reason_type":"rule"}}]}
-{"type":"user","message":{"role":"user","content":[{"type":"text","text":"[Usage limit reached; a short grace allowance remains, then this turn is cut off without warning. Judge what's left: if it's genuinely only a few steps, finish it properly, then stop and say so without extra polishing. Otherwise don't attempt it all: finish the piece in hand and at most two more like it, then stop. The allowance also pays for any subagents you have running: they don't get this message and will keep going, so it's up to you how to handle them. Either way, end by telling the user their usage limit was reached, what's done and what's left.]"}]},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"4ae44578-0826-449a-a4cd-edafdc33cce7","timestamp":"2026-11-17T20:31:42.523Z","isSynthetic":true}
-{"type":"system","subtype":"thinking_tokens","estimated_tokens":50,"estimated_tokens_delta":50,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"c6944b0d-484d-4c79-817f-79c9903b3c55"}
-{"type":"system","subtype":"thinking_tokens","estimated_tokens":207,"estimated_tokens_delta":157,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"deb590f8-a9c6-4513-8906-eb7232c6ece4"}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98pro97bXf3jaYjypKt","type":"message","role":"assistant","content":[{"type":"thinking","thinking":"","signature":"CAQStAYKEAgTGAI4AUIIdGhpbmtpbmcSDHaUBawwO5LGnUJ6aBoM15/ca5zTkfwJZZWOIjCIfm0qV/XvnDPO/6NjcN5cUvezqQGuOng6CnpLp/MSWaAfaevhYgltaIGb9JTfB0Iq0QUQGUS9yejtmLqv+4ScGTp8j2wrs2bGUR0+cBzDpb1C7Fcv03m0Ln6McEA+hrLJ2uAfTCRscOog7usjjV7lV7rF3UsRz/VgG/xPqeSRH1KePgqxuUGsyojxcU9uJlStgwggbtcVSKCyvI/03vk+XOKO+LRIRrm66L1sJK3FIyjLIf2PsB3id5UP/LxrnsI8AARPyKHd/RaRZUmJ+dETnykrMLV6g05h2H3abQDKcY1484kh6CDC6lwAYoVqN4QL6R+htex6DZKAcCfyXNXjViTWkpdi3awo7mlwk7Qk4+6X/U/ekzflyWbhKT11XSdtLXz/kQKNnS/Txilg9kbxw/j2SphQ2Fd35LwER9zL1d3lVqHxNW0RUNed+EjkL6Sbvvlwr+sUP8vsnZP0U2Ic0r5QsSG37LMeLfucWHLVSqzsXUr/aJ2C4mLQIYybm6vhnLjFbTsO9O5tx8MXN6H6DliadGSNSUvxlzK26EW6izWPlKdKAGAAs1mnr1QFwJL/s8Mh2LzWbwmGFflWzwsgytiIKS6YJvUxHSFmrv8iWIqxMblwdPyHOgJ0Ygc/vrI//BaDPan+OmQImEivP5/fI1UytdKlGt7d/ImP+eWrDJpgd87mOXqZNlX8jlVtB2UobXGdIyirwmgD9hel3kQL2THX1HhXsf0BoKyHmmXog2CkfNXEdIxfuwM72euljIHOCQRjTxMEwAQRcHuvXZkr6LaLxG7rrE8VVlR45o1KrdvE+8hH/wUTwdnksIobKO6yPMzgDfSy/rXwWdvWWUKij7bseWmzWVY8lVmpDJi69v3V+UF7W55mdeGMLmOvI5xs0CaR/HNZLEeEZfHrDo1TmEdDSbMzQfpyxl1bamFV6rFUgBKGXYfs5iwym/Rhf8JAwsQfqrUC1Hf1jPMD1A8MB1EVyOaUgMp5JuJHRToP++Mz7Ys9MVmppPc9LV1lc+vBFC69GAE="}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":4,"cache_creation_input_tokens":2714,"cache_read_input_tokens":56823,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":2714},"output_tokens":8,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"700c599d-8f2f-4c67-9b32-ac6cb321e58b","timestamp":"2026-11-17T20:31:44.900Z","request_id":"req_011Ch98prajBLKab99yA3oZa","thinking_duration_ms":945,"thinking_display":"updates"}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98pro97bXf3jaYjypKt","type":"message","role":"assistant","content":[{"type":"tool_use","id":"toolu_01YBWTn3XWfxDW8gmgDYDitM","name":"Bash","input":{"command":"cd /home/maxime/aimsight-app; python3 tools/scripts/ranges.py data/CLARIDEN --columns corr_y,corr_x,corr_y_mm,corr_x_mm --sensors D-303-B,D-303-C,D-304-C,D-301-C,D-306-B --start 2026-10-05T10:30Z --end 2026-10-15T22:50Z --outside 2026-10-06T22:00Z/2026-10-11T06:00Z --min-measurements 6 --merge 6h 2>&1 | grep -v \"^$\" | head -70","description":"Measure the drift in noises and mm"},"caller":{"type":"direct"}}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":4,"cache_creation_input_tokens":2714,"cache_read_input_tokens":56823,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":2714},"output_tokens":8,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"c5258f07-8d2b-4e1c-9726-1af98f764677","timestamp":"2026-11-17T20:31:46.689Z","request_id":"req_011Ch98prajBLKab99yA3oZa","wire_tool_inputs":{"toolu_01YBWTn3XWfxDW8gmgDYDitM":{"command":"cd /home/maxime/aimsight-app; python3 tools/scripts/ranges.py data/CLARIDEN --columns corr_y,corr_x,corr_y_mm,corr_x_mm --sensors D-303-B,D-303-C,D-304-C,D-301-C,D-306-B --start 2026-10-05T10:30Z --end 2026-10-15T22:50Z --outside 2026-10-06T22:00Z/2026-10-11T06:00Z --min-measurements 6 --merge 6h 2>&1 | grep -v \"^$\" | head -70","description":"Measure the drift in noises and mm"}}}
-{"type":"system","subtype":"task_started","task_id":"bdz5glk0x","run_id":"0mwl5eifx-42490bd9","tool_use_id":"toolu_01YBWTn3XWfxDW8gmgDYDitM","description":"Measure the drift in noises and mm","is_backgrounded":false,"task_type":"local_bash","uuid":"2a54c42b-caaf-48ff-8860-69c55b58aef8","session_id":"1d552933-66a2-4aee-a79d-97df96c159c7"}
-{"type":"system","subtype":"task_notification","task_id":"bdz5glk0x","run_id":"0mwl5eifx-42490bd9","tool_use_id":"toolu_01YBWTn3XWfxDW8gmgDYDitM","status":"completed","output_file":"","summary":"Measure the drift in noises and mm","uuid":"6a2e65f7-1649-41cb-8f5c-e23bfb1305fc","session_id":"1d552933-66a2-4aee-a79d-97df96c159c7"}
-{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_01YBWTn3XWfxDW8gmgDYDitM","type":"tool_result","content":"== corr_y: level, noise, largest jump from one measurement to the next ==\nsensor n level noise jump (noises) between\nD-303-B 1515 0.06687 0.00893 +0.09841 11.0 2026-10-05T10:30Z and 2026-10-05T10:40Z\nD-303-C 1514 -0.1325 0.00957 -0.07941 -8.3 2026-10-05T10:30Z and 2026-10-05T10:40Z\nD-304-C 1513 -0.4751 0.0108 -0.05733 -5.3 2026-10-07T12:40Z and 2026-10-07T12:50Z\nD-301-C 1514 -0.004675 0.00861 +0.04458 5.2 2026-10-06T00:50Z and 2026-10-06T01:00Z\nD-306-B 1515 0.05139 0.0101 +0.4799 47.3 2026-10-05T12:10Z and 2026-10-05T12:20Z\ncorr_y: ranges more than 5 noises from the level (level outside 2026-10-06T22:00Z/2026-10-11T06:00Z) (merge 360 min); 6 of at least 6 measurements out of 19\nsensor start end measurements extreme (noises) at rejected\nD-303-B 2026-10-05T10:30Z 2026-10-08T08:40Z 398 -0.1393 -15.6 2026-10-05T10:30Z 0\nD-303-C 2026-10-05T13:10Z 2026-10-06T05:30Z 26 -0.0693 -7.2 2026-10-05T23:10Z 0\nD-303-C 2026-10-06T14:00Z 2026-10-07T19:00Z 70 -0.06785 -7.1 2026-10-06T21:30Z 0\nD-304-C 2026-10-06T14:00Z 2026-10-06T22:20Z 25 -0.07895 -7.3 2026-10-06T19:30Z 0\nD-304-C 2026-10-07T05:10Z 2026-10-07T14:10Z 8 -0.06866 -6.4 2026-10-07T12:50Z 0\nD-301-C 2026-10-06T13:50Z 2026-10-06T17:20Z 7 -0.05659 -6.6 2026-10-06T16:50Z 0\n== corr_x: level, noise, largest jump from one measurement to the next ==\nsensor n level noise jump (noises) between\nD-303-B 1515 0.02938 0.00704 -0.06155 -8.7 2026-10-05T12:10Z and 2026-10-05T12:20Z\nD-303-C 1514 0.2287 0.0094 -0.3001 -31.9 2026-10-05T10:30Z and 2026-10-05T10:40Z\nD-304-C 1513 0.183 0.0111 -0.05665 -5.1 2026-10-13T16:10Z and 2026-10-13T16:20Z\nD-301-C 1514 -0.08024 0.0115 -0.09389 -8.2 2026-10-06T18:00Z and 2026-10-06T18:10Z\nD-306-B 1515 0.05992 0.0103 +0.1582 15.3 2026-10-05T12:20Z and 2026-10-05T12:30Z\ncorr_x: ranges more than 5 noises from the level (level outside 2026-10-06T22:00Z/2026-10-11T06:00Z) (merge 360 min); 4 of at least 6 measurements out of 17\nsensor start end measurements extreme (noises) at rejected\nD-303-B 2026-10-06T18:10Z 2026-10-06T23:10Z 21 +0.05524 7.8 2026-10-06T18:40Z 0\nD-304-C 2026-10-06T14:20Z 2026-10-07T06:00Z 30 -0.1002 -9.0 2026-10-06T20:10Z 0\nD-301-C 2026-10-05T10:30Z 2026-10-08T09:20Z 246 -0.224 -19.5 2026-10-06T20:00Z 0\nD-306-B 2026-10-06T18:10Z 2026-10-07T00:10Z 9 +0.06551 6.4 2026-10-06T18:20Z 0\n== corr_y_mm: level, noise, largest jump from one measurement to the next ==\nsensor n level noise jump (noises) between\nD-303-B 1515 0.2094 0.028 +0.3082 11.0 2026-10-05T10:30Z and 2026-10-05T10:40Z\nD-303-C 1514 -0.4619 0.0334 -0.2767 -8.3 2026-10-05T10:30Z and 2026-10-05T10:40Z\nD-304-C 1513 -1.42 0.0323 -0.1714 -5.3 2026-10-07T12:40Z and 2026-10-07T12:50Z\nD-301-C 1514 -0.02214 0.0408 +0.2111 5.2 2026-10-06T00:50Z and 2026-10-06T01:00Z\nD-306-B 1515 0.0422 0.00832 +0.394 47.3 2026-10-05T12:10Z and 2026-10-05T12:20Z\ncorr_y_mm: ranges more than 5 noises from the level (level outside 2026-10-06T22:00Z/2026-10-11T06:00Z) (merge 360 min); 6 of at least 6 measurements out of 19\nsensor start end measurements extreme (noises) at rejected\nD-303-B 2026-10-05T10:30Z 2026-10-08T08:40Z 398 -0.4362 -15.6 2026-10-05T10:30Z 0\nD-303-C 2026-10-05T13:10Z 2026-10-06T05:30Z 26 -0.2415 -7.2 2026-10-05T23:10Z 0\nD-303-C 2026-10-06T14:00Z 2026-10-07T19:00Z 70 -0.2364 -7.1 2026-10-06T21:30Z 0\nD-304-C 2026-10-06T14:00Z 2026-10-06T22:20Z 25 -0.236 -7.3 2026-10-06T19:30Z 0\nD-304-C 2026-10-07T05:10Z 2026-10-07T14:10Z 8 -0.2052 -6.4 2026-10-07T12:50Z 0\nD-301-C 2026-10-06T13:50Z 2026-10-06T17:20Z 7 -0.268 -6.6 2026-10-06T16:50Z 0\n== corr_x_mm: level, noise, largest jump from one measurement to the next ==\nsensor n level noise jump (noises) between\nD-303-B 1515 0.09201 0.022 -0.1927 -8.7 2026-10-05T12:10Z and 2026-10-05T12:20Z\nD-303-C 1514 0.7968 0.0327 -1.046 -31.9 2026-10-05T10:30Z and 2026-10-05T10:40Z\nD-304-C 1513 0.5469 0.0333 -0.1693 -5.1 2026-10-13T16:10Z and 2026-10-13T16:20Z\nD-301-C 1514 -0.3801 0.0545 -0.4447 -8.2 2026-10-06T18:00Z and 2026-10-06T18:10Z\nD-306-B 1515 0.0492 0.00847 +0.1299 15.3 2026-10-05T12:20Z and 2026-10-05T12:30Z\ncorr_x_mm: ranges more than 5 noises from the level (level outside 2026-10-06T22:00Z/2026-10-11T06:00Z) (merge 360 min); 4 of at least 6 measurements out of 17\nsensor start end measurements extreme (noises) at rejected\nD-303-B 2026-10-06T18:10Z 2026-10-06T23:10Z 21 +0.173 7.8 2026-10-06T18:40Z 0\nD-304-C 2026-10-06T14:20Z 2026-10-07T06:00Z 30 -0.2995 -9.0 2026-10-06T20:10Z 0\nD-301-C 2026-10-05T10:30Z 2026-10-08T09:20Z 246 -1.061 -19.5 2026-10-06T20:00Z 0\nD-306-B 2026-10-06T18:10Z 2026-10-07T00:10Z 9 +0.05379 6.4 2026-10-06T18:20Z 0","is_error":false}]},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"48e02ccc-8cd5-4af7-9464-8c078c193b07","timestamp":"2026-11-17T20:31:53.034Z","tool_use_result":{"stdout":"== corr_y: level, noise, largest jump from one measurement to the next ==\nsensor n level noise jump (noises) between\nD-303-B 1515 0.06687 0.00893 +0.09841 11.0 2026-10-05T10:30Z and 2026-10-05T10:40Z\nD-303-C 1514 -0.1325 0.00957 -0.07941 -8.3 2026-10-05T10:30Z and 2026-10-05T10:40Z\nD-304-C 1513 -0.4751 0.0108 -0.05733 -5.3 2026-10-07T12:40Z and 2026-10-07T12:50Z\nD-301-C 1514 -0.004675 0.00861 +0.04458 5.2 2026-10-06T00:50Z and 2026-10-06T01:00Z\nD-306-B 1515 0.05139 0.0101 +0.4799 47.3 2026-10-05T12:10Z and 2026-10-05T12:20Z\ncorr_y: ranges more than 5 noises from the level (level outside 2026-10-06T22:00Z/2026-10-11T06:00Z) (merge 360 min); 6 of at least 6 measurements out of 19\nsensor start end measurements extreme (noises) at rejected\nD-303-B 2026-10-05T10:30Z 2026-10-08T08:40Z 398 -0.1393 -15.6 2026-10-05T10:30Z 0\nD-303-C 2026-10-05T13:10Z 2026-10-06T05:30Z 26 -0.0693 -7.2 2026-10-05T23:10Z 0\nD-303-C 2026-10-06T14:00Z 2026-10-07T19:00Z 70 -0.06785 -7.1 2026-10-06T21:30Z 0\nD-304-C 2026-10-06T14:00Z 2026-10-06T22:20Z 25 -0.07895 -7.3 2026-10-06T19:30Z 0\nD-304-C 2026-10-07T05:10Z 2026-10-07T14:10Z 8 -0.06866 -6.4 2026-10-07T12:50Z 0\nD-301-C 2026-10-06T13:50Z 2026-10-06T17:20Z 7 -0.05659 -6.6 2026-10-06T16:50Z 0\n== corr_x: level, noise, largest jump from one measurement to the next ==\nsensor n level noise jump (noises) between\nD-303-B 1515 0.02938 0.00704 -0.06155 -8.7 2026-10-05T12:10Z and 2026-10-05T12:20Z\nD-303-C 1514 0.2287 0.0094 -0.3001 -31.9 2026-10-05T10:30Z and 2026-10-05T10:40Z\nD-304-C 1513 0.183 0.0111 -0.05665 -5.1 2026-10-13T16:10Z and 2026-10-13T16:20Z\nD-301-C 1514 -0.08024 0.0115 -0.09389 -8.2 2026-10-06T18:00Z and 2026-10-06T18:10Z\nD-306-B 1515 0.05992 0.0103 +0.1582 15.3 2026-10-05T12:20Z and 2026-10-05T12:30Z\ncorr_x: ranges more than 5 noises from the level (level outside 2026-10-06T22:00Z/2026-10-11T06:00Z) (merge 360 min); 4 of at least 6 measurements out of 17\nsensor start end measurements extreme (noises) at rejected\nD-303-B 2026-10-06T18:10Z 2026-10-06T23:10Z 21 +0.05524 7.8 2026-10-06T18:40Z 0\nD-304-C 2026-10-06T14:20Z 2026-10-07T06:00Z 30 -0.1002 -9.0 2026-10-06T20:10Z 0\nD-301-C 2026-10-05T10:30Z 2026-10-08T09:20Z 246 -0.224 -19.5 2026-10-06T20:00Z 0\nD-306-B 2026-10-06T18:10Z 2026-10-07T00:10Z 9 +0.06551 6.4 2026-10-06T18:20Z 0\n== corr_y_mm: level, noise, largest jump from one measurement to the next ==\nsensor n level noise jump (noises) between\nD-303-B 1515 0.2094 0.028 +0.3082 11.0 2026-10-05T10:30Z and 2026-10-05T10:40Z\nD-303-C 1514 -0.4619 0.0334 -0.2767 -8.3 2026-10-05T10:30Z and 2026-10-05T10:40Z\nD-304-C 1513 -1.42 0.0323 -0.1714 -5.3 2026-10-07T12:40Z and 2026-10-07T12:50Z\nD-301-C 1514 -0.02214 0.0408 +0.2111 5.2 2026-10-06T00:50Z and 2026-10-06T01:00Z\nD-306-B 1515 0.0422 0.00832 +0.394 47.3 2026-10-05T12:10Z and 2026-10-05T12:20Z\ncorr_y_mm: ranges more than 5 noises from the level (level outside 2026-10-06T22:00Z/2026-10-11T06:00Z) (merge 360 min); 6 of at least 6 measurements out of 19\nsensor start end measurements extreme (noises) at rejected\nD-303-B 2026-10-05T10:30Z 2026-10-08T08:40Z 398 -0.4362 -15.6 2026-10-05T10:30Z 0\nD-303-C 2026-10-05T13:10Z 2026-10-06T05:30Z 26 -0.2415 -7.2 2026-10-05T23:10Z 0\nD-303-C 2026-10-06T14:00Z 2026-10-07T19:00Z 70 -0.2364 -7.1 2026-10-06T21:30Z 0\nD-304-C 2026-10-06T14:00Z 2026-10-06T22:20Z 25 -0.236 -7.3 2026-10-06T19:30Z 0\nD-304-C 2026-10-07T05:10Z 2026-10-07T14:10Z 8 -0.2052 -6.4 2026-10-07T12:50Z 0\nD-301-C 2026-10-06T13:50Z 2026-10-06T17:20Z 7 -0.268 -6.6 2026-10-06T16:50Z 0\n== corr_x_mm: level, noise, largest jump from one measurement to the next ==\nsensor n level noise jump (noises) between\nD-303-B 1515 0.09201 0.022 -0.1927 -8.7 2026-10-05T12:10Z and 2026-10-05T12:20Z\nD-303-C 1514 0.7968 0.0327 -1.046 -31.9 2026-10-05T10:30Z and 2026-10-05T10:40Z\nD-304-C 1513 0.5469 0.0333 -0.1693 -5.1 2026-10-13T16:10Z and 2026-10-13T16:20Z\nD-301-C 1514 -0.3801 0.0545 -0.4447 -8.2 2026-10-06T18:00Z and 2026-10-06T18:10Z\nD-306-B 1515 0.0492 0.00847 +0.1299 15.3 2026-10-05T12:20Z and 2026-10-05T12:30Z\ncorr_x_mm: ranges more than 5 noises from the level (level outside 2026-10-06T22:00Z/2026-10-11T06:00Z) (merge 360 min); 4 of at least 6 measurements out of 17\nsensor start end measurements extreme (noises) at rejected\nD-303-B 2026-10-06T18:10Z 2026-10-06T23:10Z 21 +0.173 7.8 2026-10-06T18:40Z 0\nD-304-C 2026-10-06T14:20Z 2026-10-07T06:00Z 30 -0.2995 -9.0 2026-10-06T20:10Z 0\nD-301-C 2026-10-05T10:30Z 2026-10-08T09:20Z 246 -1.061 -19.5 2026-10-06T20:00Z 0\nD-306-B 2026-10-06T18:10Z 2026-10-07T00:10Z 9 +0.05379 6.4 2026-10-06T18:20Z 0","stderr":"","interrupted":false,"isImage":false,"noOutputExpected":false},"tool_result_meta":[{"id":"toolu_01YBWTn3XWfxDW8gmgDYDitM","permission_decision":{"decision":"accept","source":"config","reason_type":"rule"}}]}
-{"type":"system","subtype":"thinking_tokens","estimated_tokens":50,"estimated_tokens_delta":50,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"d6b01aa6-406d-4c79-9499-feb47a46d23a"}
-{"type":"system","subtype":"thinking_tokens","estimated_tokens":150,"estimated_tokens_delta":100,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"2a23e5c8-9ace-4bcd-8b06-00becb2b9003"}
-{"type":"system","subtype":"thinking_tokens","estimated_tokens":250,"estimated_tokens_delta":100,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"ffa05720-0e9b-483b-ad02-43af846cd4fb"}
-{"type":"system","subtype":"thinking_tokens","estimated_tokens":390,"estimated_tokens_delta":140,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"892785bf-d7d0-45d1-8e7b-f01ef01859cc"}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98qdn5aqPcrAdscDFeS","type":"message","role":"assistant","content":[{"type":"thinking","thinking":"","signature":"CAQSkQwKEAgTGAI4AUIIdGhpbmtpbmcSDApjNyAxS8gikl2XJBoMNfAUH50M40BU/KxmIjDTcErxWDkKWTpMP0VzOA4OPef+dJeC4fDwZPq3aIhd7iGJZptxSXfeWIon/2J+vlEqrgvXtgfXcD1g/VqA9ICXAHxn5I+psl8LyGiwbXshOl0+Mv6etY38ayNWxE4k71tgQlkABms+wSYUjJz1dMhB2c6bE8O4tf1ExizsH+cu8iq1gRknCHF0JXE2UgGhg2tquKedkR1mRryQp4OF7rPtNUTkfFn3ixBdc0iM1pRQkm60HRVMEq+SDlj78PZvMXP0ugL9rJpEZZjovdieUa+hdtHF8qSEImZK9iqsw/mk6HjFFelQ2uHQc2secJPb3/cexLo7DdkfjVSWjD+4SIdW4IYO3Z7CWVg0guCrsAJlWIs1kAVhmMdV4xThdUaIz+o7HXD2f9j15CrMD7eGzAlaQwPxSNl3qDASyj4S15nLv5G/GL8151w/BlWaLaqjS2VEWb/8uVPhYJ5Bwr/jRhHaQdV0P/7R7gTEwaeO4kEcv7qEGf0DCt3pKE8ZfLeebX8Apo6avH1hbHstguP1kj6dAvouH0MmctFLV77Iz6j75HzVRvZC6VHWa69xRQxS4E+juuHEGr28aQmECuDpORXzdp7SkOrdtTpZU+bhTM9heYVA5e4fkOReohPLpv1wa7h0DdCCGwTrlb7rhV026GmPnqmwPZBOYAHwvsfmMkiApFN+DjyRhKBym3uKhjExkt1UyeoUgDkJ20HG5f9315Kg3XfxO7J+ltD+7+t690lZbcO1mKkuZoVXfeuK4MCrYguKA/dKl7bPO3fSnxccfzSKxBxEASKL1NMG0xjyl5JE8rIGq3wLe8zBHp/9rpXGfyQ+dmmR80IBTo6rpW69QmGXLVp8rC2HRSyuzHv5TkNOdSlZZ4j7ybZ1Z8jBFvJfMvZRZofPGEvZVSQI0J7LJeCbrxFzDKYkIK6Vshh+FT3MceF3SbR9p09HBujL6aZFlQ5JNxqXJBKMWsj9D0bnClxyi/xKvw7Fo2kk97+x61X2GDTpFwDsMkSfWdb+KHmfA4401G0ZSinIpedUWZcySikm1rTpchv9OBOATSYGjgoRm1kTg9sd8ZJU95pPtLK3LDwdQ9YIHa2ovmPrlOKNtZMnJCrQRIn1ASJnw6gz41orb4Z6bSNOF3I+bhj3bxl0PjiS/Sm/19u0aoU2IQT8gPFTcDBEZ6+FRsoF2WqG5K2nERqOr4we/804BNGllJn3/o5/9TAgWtkRpwQKjlST7KnItp75Uq4ZHsNb4WTjasRiJrXvPvNUH39qvwIytjuMT0VGZ9C3zOLtpHLTVljDiEMcepqxqmxim4x2kijnJXyKCPQHYOZQrI9mAviw89CMXisnSzLTqe9AIZ+vFL7HpSJBVthGjPpIiVsU3HWbAJcOLzyRjFI0objxkYR8dPp/308dqDWk7rbcgg0sTRMIus7TjXLuKB12YP+TluRYmiMfY7T2GLlszJQay28OP89G2JtOtbQS7F9b+gx4d8eMCumy/1OuSFpWi9H9pDtkwifq78XdQX+tegu71lgYw1lnaO8XvyPxfw25eqACkmBTJPIgVHgbGic4KcgLeGPzdmeDvU1mCH2E4fY5Y97eLE4U9zcIz/jLUBzk0Xz1dmWg1V2WLXXmc3G/UAWFDkFuYWqRmh5pmyZQMV0efcBpIsAGDJoSZ1AnQSlZkySYfVbSbup2kAcgPQ9jEWNfUz82ntlhoo2YXROvD8VQVLhoK54oBbzsAvdKHzOE6xH8CxV1AFrC1itnD4bBlHprMSuXXnmv2E8dfu6ochh+ufN92lQPeTwMjWkNhM/DRa3he0rOUuX0ou9dtk0+qn5yg3BkNdneLYR1NgPRVZ1EQzL7Btl8YEVlWFK5vu/VmZIZ6xY3O4QR2+FFmBAWo0kcE7mJmDkWSRzQJXmNa2eqxYQo8W1S9oeuS8jKsUKXoJPmu+d3c6jrk9xzc65MaJO+FaTS8Z5pfCMPi5jnrhTu8Bz9I5uq5MWb3D9ixHIyiDM3dWf6vz3CUhgB"}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":3283,"cache_read_input_tokens":59537,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":3283},"output_tokens":5,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"069a957b-53bf-4860-9359-de73581f7b4c","timestamp":"2026-11-17T20:31:58.351Z","request_id":"req_011Ch98qdYwVVkCCPNTDVjRw","thinking_duration_ms":3848,"thinking_display":"updates"}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98qdn5aqPcrAdscDFeS","type":"message","role":"assistant","content":[{"type":"tool_use","id":"toolu_0136ZKTCSaVA47NpFp4H9kQt","name":"Bash","input":{"command":"cd /home/maxime/aimsight-app/labeling/auto/analyses/long-labels/CLARIDEN; python3 - <<'EOF'\nimport json\nsrc=[json.loads(l) for l in open('input.jsonl')]\nout=[]\nfor l in src:\n if l['id']=='CLARIDEN-14':\n l=dict(l); l.pop('review',None)\n l['description']=(\"Slow drift of several targets over four days, made of small steps, then stabilization: D-303-B rises vertically, D-303-C and D-304-C rise vertically, D-301-C rises horizontally, D-306-B goes down horizontally. \"\n \"The camera moves: its tilt drifts slowly over the same days, with a small step on the 8th, and these targets follow it closely in the directions of their curves; the compensation does not absorb this tilt equally on every target. \"\n \"Ordinary recognition error, nothing on the images. The camera housing temperature stays almost constant over these days: no link with it. Slow return from the 11th to the 19th, labeled separately. \"\n \"Deduced from the curves and the camera pose: mostly a remainder of the camera tilt, not established as a movement of the structure; the camera is to be monitored, and these targets checked against the other measurements of the site.\")\n out.append(l)\nwith open('labels.jsonl','w') as f:\n for l in out: f.write(json.dumps(l,ensure_ascii=False)+'\\n')\nEOF\ncat > analysis.md <<'EOF'\n# Requalification of the long labels: CLARIDEN\n\n- **CLARIDEN-1** (Target issue, P-300-B, 01/10 → 01/11): **kept** as is. P-300-B is rejected at 4070 of the 4070 measurement instants present in the range (`inventory.py --start 2026-10-01T00:00Z --end 2026-11-01T00:00Z`; 6371 of 10137 over the whole period, since 29/09). A target rejected almost always: Target issue.\n- **CLARIDEN-14** (Displacement, 06/10 22:00 → 11/10 06:00): **corrected** (description). The drift is beyond the threshold: `ranges.py --k 5` from 05/10 10:30 to 15/10 22:50, the level taken outside the label: D-301-C corr_x out of level up to −19.5 noises (−0.22 px, about −1.1 mm) until 08/10 09:20 before it rises to its later level; D-303-B corr_y up to −15.6 noises (about −0.44 mm) until 08/10 08:40; D-304-C corr_x −9.0, D-303-C corr_y −7.1, D-306-B corr_x +6.4 noises. Bounds and family hold. Correction applied (found by the analyst of the 01/10–11/10 period): \"No camera movement\" is wrong, the camera tilt drifts over these days and D-303-B, D-303-C, D-304-C, D-301-C follow it (hourly r −0.86 to −0.95, `CLARIDEN_2026-10-01T0000_2026-10-11T0000/analysis.md`); the conclusion becomes \"camera to monitor\". Review removed.\n\nSources read: `tools/GUIDE.md`, `tools/DATA.md`, `labeling/families.md`, `labeling/labeling-rules.md`, `labeling/reading-rules.md`, `labeling/stations.md`, `input.jsonl`, the analyses of the three CLARIDEN periods (lines on CLARIDEN-1 and CLARIDEN-14). Commands: `inventory.py` (month, `work/inv_month.txt`), `ranges.py` (corr and corr_mm, 5 targets, `--outside` the label).\nEOF\ncat > report.md <<'EOF'\n# CLARIDEN long labels: requalification\n\n2 labels: 1 kept, 1 corrected, 0 removed.\n\n- **CLARIDEN-14** corrected: the drift does stand out (up to about 20 noises: D-301-C horizontal about 1 mm, D-303-B vertical about 0.4 mm), but its text said \"no camera movement\". In fact the targets follow the slow tilt of the camera, so the conclusion is now \"the camera is to be monitored\" rather than \"the targets may be moving\". The bounds and the family are unchanged.\nEOF\ncd /home/maxime/aimsight-app; python3 labeling/scripts/validate.py labeling/auto/analyses/long-labels/CLARIDEN/labels.jsonl","description":"Write labels, analysis, report; validate"},"caller":{"type":"direct"}}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":3283,"cache_read_input_tokens":59537,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":3283},"output_tokens":5,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"6e6f1456-3273-4356-88d5-4ae7b235e153","timestamp":"2026-11-17T20:32:10.680Z","request_id":"req_011Ch98qdYwVVkCCPNTDVjRw","wire_tool_inputs":{"toolu_0136ZKTCSaVA47NpFp4H9kQt":{"command":"cd /home/maxime/aimsight-app/labeling/auto/analyses/long-labels/CLARIDEN; python3 - <<'EOF'\nimport json\nsrc=[json.loads(l) for l in open('input.jsonl')]\nout=[]\nfor l in src:\n if l['id']=='CLARIDEN-14':\n l=dict(l); l.pop('review',None)\n l['description']=(\"Slow drift of several targets over four days, made of small steps, then stabilization: D-303-B rises vertically, D-303-C and D-304-C rise vertically, D-301-C rises horizontally, D-306-B goes down horizontally. \"\n \"The camera moves: its tilt drifts slowly over the same days, with a small step on the 8th, and these targets follow it closely in the directions of their curves; the compensation does not absorb this tilt equally on every target. \"\n \"Ordinary recognition error, nothing on the images. The camera housing temperature stays almost constant over these days: no link with it. Slow return from the 11th to the 19th, labeled separately. \"\n \"Deduced from the curves and the camera pose: mostly a remainder of the camera tilt, not established as a movement of the structure; the camera is to be monitored, and these targets checked against the other measurements of the site.\")\n out.append(l)\nwith open('labels.jsonl','w') as f:\n for l in out: f.write(json.dumps(l,ensure_ascii=False)+'\\n')\nEOF\ncat > analysis.md <<'EOF'\n# Requalification of the long labels: CLARIDEN\n\n- **CLARIDEN-1** (Target issue, P-300-B, 01/10 → 01/11): **kept** as is. P-300-B is rejected at 4070 of the 4070 measurement instants present in the range (`inventory.py --start 2026-10-01T00:00Z --end 2026-11-01T00:00Z`; 6371 of 10137 over the whole period, since 29/09). A target rejected almost always: Target issue.\n- **CLARIDEN-14** (Displacement, 06/10 22:00 → 11/10 06:00): **corrected** (description). The drift is beyond the threshold: `ranges.py --k 5` from 05/10 10:30 to 15/10 22:50, the level taken outside the label: D-301-C corr_x out of level up to −19.5 noises (−0.22 px, about −1.1 mm) until 08/10 09:20 before it rises to its later level; D-303-B corr_y up to −15.6 noises (about −0.44 mm) until 08/10 08:40; D-304-C corr_x −9.0, D-303-C corr_y −7.1, D-306-B corr_x +6.4 noises. Bounds and family hold. Correction applied (found by the analyst of the 01/10–11/10 period): \"No camera movement\" is wrong, the camera tilt drifts over these days and D-303-B, D-303-C, D-304-C, D-301-C follow it (hourly r −0.86 to −0.95, `CLARIDEN_2026-10-01T0000_2026-10-11T0000/analysis.md`); the conclusion becomes \"camera to monitor\". Review removed.\n\nSources read: `tools/GUIDE.md`, `tools/DATA.md`, `labeling/families.md`, `labeling/labeling-rules.md`, `labeling/reading-rules.md`, `labeling/stations.md`, `input.jsonl`, the analyses of the three CLARIDEN periods (lines on CLARIDEN-1 and CLARIDEN-14). Commands: `inventory.py` (month, `work/inv_month.txt`), `ranges.py` (corr and corr_mm, 5 targets, `--outside` the label).\nEOF\ncat > report.md <<'EOF'\n# CLARIDEN long labels: requalification\n\n2 labels: 1 kept, 1 corrected, 0 removed.\n\n- **CLARIDEN-14** corrected: the drift does stand out (up to about 20 noises: D-301-C horizontal about 1 mm, D-303-B vertical about 0.4 mm), but its text said \"no camera movement\". In fact the targets follow the slow tilt of the camera, so the conclusion is now \"the camera is to be monitored\" rather than \"the targets may be moving\". The bounds and the family are unchanged.\nEOF\ncd /home/maxime/aimsight-app; python3 labeling/scripts/validate.py labeling/auto/analyses/long-labels/CLARIDEN/labels.jsonl","description":"Write labels, analysis, report; validate"}}}
-{"type":"system","subtype":"task_summary","detail":"Writing labels, analysis, reporting; validate","uuid":"4b3bb18f-7d6f-45f4-a334-bea83cce37ba","session_id":"1d552933-66a2-4aee-a79d-97df96c159c7"}
-{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_0136ZKTCSaVA47NpFp4H9kQt","type":"tool_result","content":"2 labels, 1 stations: 0 errors, 0 overlaps to look at","is_error":false}]},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"77607ef3-a0a0-40c2-a2e9-2ff0f37f719b","timestamp":"2026-11-17T20:32:10.844Z","tool_use_result":{"stdout":"2 labels, 1 stations: 0 errors, 0 overlaps to look at","stderr":"","interrupted":false,"isImage":false,"noOutputExpected":false},"tool_result_meta":[{"id":"toolu_0136ZKTCSaVA47NpFp4H9kQt","permission_decision":{"decision":"accept","source":"config","reason_type":"rule"}}]}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98rxFbwQSeo6dibpfxz","type":"message","role":"assistant","content":[{"type":"text","text":"I requalified both CLARIDEN long labels: one is kept as it was and one is corrected. Validation gives 0 errors. Your usage limit was reached, so I kept the checks to the minimum.\n\n- **CLARIDEN-1** (target P-300-B, Target issue): kept exactly as it was, review included. P-300-B is rejected at all 4070 measurements in October, so it counts as rejected almost always.\n- **CLARIDEN-14** (drift, Displacement): corrected, so it loses its review field. The drift does stand out from the noise. Measured against the level outside the label, D-301-C moves horizontally by up to about 20 noises (about 1.1 mm), and D-303-B vertically by about 16 noises (about 0.4 mm). D-304-C, D-303-C and D-306-B also go past 5 noises. Start, end and family stay the same. I applied the correction you gave me: the text no longer says \"no camera movement\". It now says the targets follow the slow tilt of the camera, and the conclusion becomes \"the camera is to be monitored\".\n\nTwo shortcuts:\n- **Camera link not re-measured:** for CLARIDEN-14 I took the link with the camera tilt from the report of the 1–11 October period, which found strong correlations. I did not recompute it, and I did not check target by target which ones move in the image.\n- **No proper rolling check:** my reference level comes partly from after the slow return of the 11th–19th, which is labelled separately. Proper rolling-level checks and a closer look at the threshold were not done.\n\nFiles are in `labeling/auto/analyses/long-labels/CLARIDEN/`:\n- labels.jsonl\n- analysis.md\n- report.md"}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":1979,"cache_read_input_tokens":62820,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":1979},"output_tokens":560,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","uuid":"164cc262-de6d-436b-9ad1-5f3cede61860","timestamp":"2026-11-17T20:32:18.094Z","request_id":"req_011Ch98rx2TncgJt9tao8GwR"}
-{"type":"system","subtype":"post_turn_summary","summarizes_uuid":"164cc262-de6d-436b-9ad1-5f3cede61860","status_category":"review_ready","status_detail":"- report.md","needs_action":"","uuid":"a1e70046-3344-4505-aa21-a69c46760074","session_id":"1d552933-66a2-4aee-a79d-97df96c159c7"}
-{"duration_api_ms":61047,"stop_reason":"end_turn","session_id":"1d552933-66a2-4aee-a79d-97df96c159c7","total_cost_usd":0.6384726000000001,"usage":{"input_tokens":22,"cache_creation_input_tokens":58823,"cache_read_input_tokens":323903,"output_tokens":5151,"output_tokens_details":{"thinking_tokens":1175},"server_tool_use":{"web_search_requests":0,"web_fetch_requests":0},"service_tier":"standard","cache_creation":{"ephemeral_1h_input_tokens":58823,"ephemeral_5m_input_tokens":0},"inference_geo":"global","iterations":[{"input_tokens":2,"output_tokens":560,"cache_read_input_tokens":62820,"cache_creation_input_tokens":1979,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":1979},"type":"message"}],"speed":"standard","fallback_credit":null},"modelUsage":{"claude-opus-5-5":{"inputTokens":22,"outputTokens":5151,"cacheReadInputTokens":323903,"cacheCreationInputTokens":58823,"webSearchRequests":0,"costUSD":0.6384726000000001,"contextWindow":1000000,"maxOutputTokens":128000,"thinkingTokens":1175,"cacheCreationEphemeral5mInputTokens":0,"cacheCreationEphemeral1hInputTokens":58823,"canonicalModel":"claude-opus-5-5","provider":"firstParty","costBasis":"list"}},"permission_denials":[],"terminal_reason":"completed","fast_mode_state":"off","fast_mode_disabled_reason":"sdk_opt_in_required","subagent_stats":{"spawned":0,"requested":{"background":0,"foreground":0,"unset":0},"started_in_background":0,"max_depth":0,"spawned_by_subagents":0,"completed":0,"failed":0,"killed":{"parent":0,"user":0,"system":0},"refused":{"depth_limit":0,"concurrency_limit":0,"budget":0},"by_type":{}},"safety_stops":0,"is_error":false,"num_turns":15,"subtype":"success","api_error_status":null,"result":"I requalified both CLARIDEN long labels: one is kept as it was and one is corrected. Validation gives 0 errors. Your usage limit was reached, so I kept the checks to the minimum.\n\n- **CLARIDEN-1** (target P-300-B, Target issue): kept exactly as it was, review included. P-300-B is rejected at all 4070 measurements in October, so it counts as rejected almost always.\n- **CLARIDEN-14** (drift, Displacement): corrected, so it loses its review field. The drift does stand out from the noise. Measured against the level outside the label, D-301-C moves horizontally by up to about 20 noises (about 1.1 mm), and D-303-B vertically by about 16 noises (about 0.4 mm). D-304-C, D-303-C and D-306-B also go past 5 noises. Start, end and family stay the same. I applied the correction you gave me: the text no longer says \"no camera movement\". It now says the targets follow the slow tilt of the camera, and the conclusion becomes \"the camera is to be monitored\".\n\nTwo shortcuts:\n- **Camera link not re-measured:** for CLARIDEN-14 I took the link with the camera tilt from the report of the 1–11 October period, which found strong correlations. I did not recompute it, and I did not check target by target which ones move in the image.\n- **No proper rolling check:** my reference level comes partly from after the slow return of the 11th–19th, which is labelled separately. Proper rolling-level checks and a closer look at the threshold were not done.\n\nFiles are in `labeling/auto/analyses/long-labels/CLARIDEN/`:\n- labels.jsonl\n- analysis.md\n- report.md","ttft_ms":3196,"type":"result","duration_ms":81989,"uuid":"01fe0ee7-03fb-49d7-9c5e-7740b5f121e1","ttft_stream_ms":2740,"time_to_request_ms":821,"time_to_request_phases_ms":{"other":20,"system_prompt":327,"resume_other":1,"process_user_input":8,"input_attachments":149,"input_hooks":8,"conversation_append":1,"transcript_persist":113,"tool_pool_refresh":47,"init_message":13,"init_frame_send":9,"engine_pickup":3,"loop_entry":15,"message_prep":3,"model_config_wait":4,"autocompact":7,"request_announcements":24,"query_setup":1,"model_gates":2,"tool_schema_build":20,"message_normalization":8,"client_creation":13,"request_build":25},"turn_start_resume_kind":"none","process_turn_index":0,"time_to_request_loop_lag_ms":218,"time_to_request_cpu_ms":1260,"time_to_request_major_faults":0,"input_attachments_detail":{"slowest_producer":"session_settings","slowest_producer_ms":134,"cpu_ms":91,"major_faults":0,"setup_ms":1,"prompt_producers_ms":1,"ambient_start_ms":6,"ambient_wait_ms":134,"render_ms":4,"producers":43,"token_counts":0},"tool_schema_build_detail":{"betas_ms":1,"waits_ms":3,"placement_ms":3,"render_ms":13,"after_ms":0,"other_ms":0,"tools":3,"new_schemas":3},"message_normalization_detail":{"before_ms":0,"normalize_ms":4,"images_ms":1,"post_process_ms":2,"after_ms":1,"other_ms":0,"messages":9,"wire_messages":2},"request_build_detail":{"records_ms":1,"system_ms":5,"headers_ms":2,"cache_break_record_ms":2,"plans_ms":2,"retry_setup_ms":1,"sent_build_ms":6,"record_attempt_ms":6,"other_ms":0,"sent_build_safety_context_ms":0,"sent_build_cache_breakpoints_ms":1,"sent_build_surrogate_scan_ms":1},"first_content_frame_ms":2740,"queued_turn_count":0,"result_index":0,"model_usage_since_last_result":{"claude-opus-5-5":{"inputTokens":22,"outputTokens":5151,"cacheReadInputTokens":323903,"cacheCreationInputTokens":58823,"webSearchRequests":0,"costUSD":0.6384726000000001,"contextWindow":1000000,"maxOutputTokens":128000,"thinkingTokens":1175,"cacheCreationEphemeral5mInputTokens":0,"cacheCreationEphemeral1hInputTokens":58823,"canonicalModel":"claude-opus-5-5","provider":"firstParty","costBasis":"list"}},"credential_expires_at":"2026-12-14T16:38:37.087Z"}
-{"type":"system","subtype":"task_summary","detail":null,"uuid":"f4cbdb8f-db31-4b60-a15f-e859ce1d5dcf","session_id":"1d552933-66a2-4aee-a79d-97df96c159c7"}
diff --git a/auto/analyses/long-labels/CLARIDEN/work/session b/auto/analyses/long-labels/CLARIDEN/work/session
deleted file mode 100644
index b59288f..0000000
--- a/auto/analyses/long-labels/CLARIDEN/work/session
+++ /dev/null
@@ -1 +0,0 @@
-1d552933-66a2-4aee-a79d-97df96c159c7
\ No newline at end of file
diff --git a/auto/analyses/long-labels/FLORIDA/input.jsonl b/auto/analyses/long-labels/FLORIDA/input.jsonl
deleted file mode 100644
index 972e5e3..0000000
--- a/auto/analyses/long-labels/FLORIDA/input.jsonl
+++ /dev/null
@@ -1,2 +0,0 @@
-{"id": "FLORIDA-1", "start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "Sellette 6 is a constantly problematic target: its error_value stays just above the threshold, a large part of its measurements are rejected all month, day and night, whatever the weather: its curve has gaps every day and its kept measurements jump. Seen on the thumbnails: a very small spot, almost invisible by day, very close to the halo of Sellette 5, which is much brighter; on the morning of the 20th, the measurement of Sellette 5 even latched onto the spot of Sellette 6. Ignore its curve; check the orientation or cleanliness of the prism.", "review": "2026-11-17"}
-{"id": "FLORIDA-14", "start": "2026-10-06T10:15Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "Massif 2 becomes a problematic target: by day, its spot is only a point (noon thumbnails of the 3rd and the 6th), and from the 6th its error_value goes above the threshold at times, measurements rejected by day; from the rain episode of the 8th, its spot also weakens at night and does not come back, the majority of its measurements are rejected day and night until the 29th, and its kept measurements change level (corr_y clearly going downward, corr_x going down at the end of the month). On the 30th and 31st, it is kept again, but just under the threshold and with a corr_y much lower than at the start of the month. Seen on the thumbnails: wide and bright spot at night in early October, small and weak afterwards, invisible by day on the 12th, 30th and 31st. Cause not established (prism tarnished, dirty or veiled). Ignore its curve; check the prism.", "review": "2026-11-17"}
diff --git a/auto/analyses/long-labels/FLORIDA/labels.jsonl b/auto/analyses/long-labels/FLORIDA/labels.jsonl
deleted file mode 100644
index 972e5e3..0000000
--- a/auto/analyses/long-labels/FLORIDA/labels.jsonl
+++ /dev/null
@@ -1,2 +0,0 @@
-{"id": "FLORIDA-1", "start": "2026-10-01T00:00Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "Sellette 6 is a constantly problematic target: its error_value stays just above the threshold, a large part of its measurements are rejected all month, day and night, whatever the weather: its curve has gaps every day and its kept measurements jump. Seen on the thumbnails: a very small spot, almost invisible by day, very close to the halo of Sellette 5, which is much brighter; on the morning of the 20th, the measurement of Sellette 5 even latched onto the spot of Sellette 6. Ignore its curve; check the orientation or cleanliness of the prism.", "review": "2026-11-17"}
-{"id": "FLORIDA-14", "start": "2026-10-06T10:15Z", "end": "2026-11-01T00:00Z", "family": "Target issue", "description": "Massif 2 becomes a problematic target: by day, its spot is only a point (noon thumbnails of the 3rd and the 6th), and from the 6th its error_value goes above the threshold at times, measurements rejected by day; from the rain episode of the 8th, its spot also weakens at night and does not come back, the majority of its measurements are rejected day and night until the 29th, and its kept measurements change level (corr_y clearly going downward, corr_x going down at the end of the month). On the 30th and 31st, it is kept again, but just under the threshold and with a corr_y much lower than at the start of the month. Seen on the thumbnails: wide and bright spot at night in early October, small and weak afterwards, invisible by day on the 12th, 30th and 31st. Cause not established (prism tarnished, dirty or veiled). Ignore its curve; check the prism.", "review": "2026-11-17"}
diff --git a/auto/analyses/long-labels/FLORIDA/work/inventory.txt b/auto/analyses/long-labels/FLORIDA/work/inventory.txt
deleted file mode 100644
index b208217..0000000
--- a/auto/analyses/long-labels/FLORIDA/work/inventory.txt
+++ /dev/null
@@ -1,269 +0,0 @@
-Folder: data/FLORIDA
-"advanced" exports (source of the measurements): 78
- 78 files, first and last (--files for the full list):
- data/FLORIDA/displacement/FLORIDA_advanced_20260901.csv
- data/FLORIDA/displacement/FLORIDA_advanced_20261117.csv
-Hourly exports: 0 (not read by the tools: hourly averages, local time without a zone; see tools/DATA.md)
-Camera movements (pose at each registration): 78
- 78 files, first and last (--files for the full list):
- data/FLORIDA/camera/FLORIDA_camera_20260901.csv
- data/FLORIDA/camera/FLORIDA_camera_20261117.csv
-Other files: 1873
- 1873 files, first and last (--files for the full list):
- data/FLORIDA/metrics/FLORIDA_BusCurrent_2026_09_01_00_00 to 2026_09_01_23_00.csv
- data/FLORIDA/targets.csv
-
-What the data contain, over the window (per column, the rows that have a value; "empty": none):
- "advanced" export: 23320 rows; x 23320, y 23320, error_value 23320, error_threshold 23320, relative_x 23320, relative_y 23320, corr_x 18965, corr_y 18965, reproj_err 5116 (2 sensors of 8), inlier empty, sigma0 empty, pattern_type 23320, peak empty, flux empty, sharpness empty, fwhm empty, dominance empty, snr empty, corr_x_mm 13321 (6 sensors of 8), corr_y_mm 13321 (6 sensors of 8)
- Export image quality (peak to snr): empty
- Camera pose (camera/): 2558 rows; median_pan 2558, min_pan 2558, max_pan 2558, median_tilt 2558, min_tilt 2558, max_tilt 2558, median_scale 2558, min_scale 2558, max_scale 2558, median_rotation 2558, min_rotation 2558, max_rotation 2558, median_sigma0 empty, min_sigma0 empty, max_sigma0 empty
- System metrics (metrics/, one CSV per metric and per day; read by metrics.py): 24: BusCurrent (32 d), BusVoltage (32 d), DB_file_size (32 d), DB_not_uploaded (32 d), DB_total_entries (32 d), DB_uploaded (32 d), Power (32 d), SIM_CCID (32 d), ShuntVoltage (32 d), avail_disk_1k-blk (32 d), ip_eth0 (32 d), ip_modem (32 d), ip_nebula1 (32 d), last_sync (32 d), mode (32 d), rsrp_dBm (32 d), rsrq_dB (32 d), sensor_A0_deg_c (32 d), sensor_CPU_deg_c (32 d), sensor_GPU_deg_c (32 d), sensor_PLL_deg_c (32 d), sensor_thermal_deg_c (32 d), total_disk_1k-blk (32 d), used_disk_1k-blk (32 d)
- Camera images: 1623
- Others: targets.csv (1)
-Images: 2773, from 2026-09-01T00:00Z to 2026-11-17T16:00Z
- gap between two images over the window, per run of equal gaps (within 5 min):
- 2026-10-01T00:00Z → 2026-10-09T01:00Z: 194 images, every 60 min
- 2026-10-09T01:00Z → 2026-10-09T02:15Z: one gap of 75 min
- 2026-10-09T02:15Z → 2026-10-09T03:00Z: one gap of 45 min
- 2026-10-09T03:00Z → 2026-10-13T00:00Z: 94 images, every 60 min
- 2026-10-13T00:00Z → 2026-10-13T01:45Z: 8 images, every 15 min
- 2026-10-13T01:45Z → 2026-10-13T02:15Z: one gap of 30 min
- 2026-10-13T02:15Z → 2026-10-14T01:15Z: 93 images, every 15 min
- 2026-10-14T01:15Z → 2026-10-14T01:45Z: one gap of 30 min
- 2026-10-14T01:45Z → 2026-10-15T01:45Z: 97 images, every 15 min
- 2026-10-15T01:45Z → 2026-10-15T02:45Z: 3 images, every 30 min
- 2026-10-15T02:45Z → 2026-10-15T22:45Z: 81 images, every 15 min
- 2026-10-15T22:45Z → 2026-10-16T10:45Z: one gap of 720 min
- 2026-10-16T10:45Z → 2026-10-16T13:30Z: 12 images, every 15 min
- 2026-10-16T13:30Z → 2026-10-16T14:00Z: one gap of 30 min
- 2026-10-16T14:00Z → 2026-10-16T14:15Z: one gap of 15 min
- 2026-10-16T14:15Z → 2026-10-16T14:45Z: one gap of 30 min
- 2026-10-16T14:45Z → 2026-10-19T09:00Z: 266 images, every 15 min
- 2026-10-19T09:00Z → 2026-10-19T10:15Z: one gap of 75 min
- 2026-10-19T10:15Z → 2026-10-19T20:45Z: 43 images, every 15 min
- 2026-10-19T20:45Z → 2026-10-19T21:15Z: one gap of 30 min
- 2026-10-19T21:15Z → 2026-10-26T00:00Z: 588 images, every 15 min
- 2026-10-26T00:00Z → 2026-10-26T14:00Z: 15 images, every 60 min
- 2026-10-26T14:00Z → 2026-10-26T15:15Z: one gap of 75 min
- 2026-10-26T15:15Z → 2026-10-26T16:00Z: one gap of 45 min
- 2026-10-26T16:00Z → 2026-11-01T00:00Z: 129 images, every 60 min
-
-Measurement period: 2026-09-01T00:00Z → 2026-11-17T08:30Z, 7175 instants
-Cadence (median step): 15 min
-Missing measurements (instants absent from the cadence): 252
- between 2026-09-01T00:45Z and 2026-09-01T01:30Z: 2
- between 2026-09-02T00:30Z and 2026-09-02T01:15Z: 2
- between 2026-09-03T01:15Z and 2026-09-03T02:00Z: 2
- between 2026-09-04T01:00Z and 2026-09-04T01:45Z: 2
- between 2026-09-05T01:15Z and 2026-09-05T02:15Z: 3
- between 2026-09-06T01:15Z and 2026-09-06T02:00Z: 2
- between 2026-09-07T00:45Z and 2026-09-07T01:15Z: 1
- between 2026-09-08T00:45Z and 2026-09-08T01:15Z: 1
- between 2026-09-09T00:45Z and 2026-09-09T01:30Z: 2
- between 2026-09-09T01:30Z and 2026-09-09T02:00Z: 1
- between 2026-09-14T11:15Z and 2026-09-14T11:45Z: 1
- between 2026-09-14T17:45Z and 2026-09-14T18:15Z: 1
- between 2026-09-14T19:45Z and 2026-09-14T20:15Z: 1
- between 2026-09-15T01:45Z and 2026-09-15T02:30Z: 2
- between 2026-09-17T13:45Z and 2026-09-17T14:15Z: 1
- between 2026-09-20T00:45Z and 2026-09-20T01:15Z: 1
- between 2026-09-22T01:45Z and 2026-09-22T02:15Z: 1
- between 2026-09-24T00:45Z and 2026-09-24T01:15Z: 1
- between 2026-09-25T01:45Z and 2026-09-25T02:15Z: 1
- between 2026-10-02T01:45Z and 2026-10-02T02:15Z: 1
- between 2026-10-09T01:45Z and 2026-10-09T02:15Z: 1
- between 2026-10-14T01:15Z and 2026-10-14T01:45Z: 1
- between 2026-10-15T01:45Z and 2026-10-15T02:15Z: 1
- between 2026-10-15T02:15Z and 2026-10-15T02:45Z: 1
- between 2026-10-15T22:45Z and 2026-10-16T10:45Z: 47
- between 2026-10-16T13:30Z and 2026-10-16T14:00Z: 1
- between 2026-10-16T14:15Z and 2026-10-16T14:45Z: 1
- between 2026-10-19T09:00Z and 2026-10-19T10:15Z: 4
- between 2026-10-19T20:45Z and 2026-10-19T21:15Z: 1
- between 2026-10-26T14:30Z and 2026-10-26T15:15Z: 2
- between 2026-10-27T09:00Z and 2026-10-27T09:30Z: 1
- between 2026-11-11T00:30Z and 2026-11-12T10:45Z: 136
- between 2026-11-16T17:15Z and 2026-11-17T00:00Z: 26
-
-Sensors: 8 (2 references, 6 targets)
- distance (m) and mm/px: targets.csv (data.load_targets); "-": not in it, or not filled in (distance 1000 mm); "?": its lines (n) disagree, no corr_x_mm / corr_y_mm
-sensor type pattern threshold measurements rejected distance mm/px
-p1_r reference global_ref 0.7 7175 331 - -
-r1_r reference global_ref 0.7 7175 563 - -
-Massif 2 target target 0.7 7175 3170 98.8 19.633
-Pont Ernen target target 0.7 7175 367 373.3 74.314
-Sellette 3 target target 0.7 7175 331 33 6.518
-Sellette 4 target target 0.7 7175 757 48.4 9.585
-Sellette 5 target target 0.7 7175 773 64.3 12.755
-Sellette 6 target target 0.7 7175 3207 80.3 15.941
-
-Camera pose over the whole period: 6433 registrations, 2026-09-01T00:00Z → 2026-11-15T20:15Z
-Measurement instants without a pose (no registration): 742 of 7175
-
-Window 2026-10-01T00:00Z → 2026-11-01T00:00Z: 2915 instants present
-Steps absent for all sensors, between two present instants (cadence of 15 min):
- between 2026-10-02T01:45Z and 2026-10-02T02:15Z: 1
- between 2026-10-09T01:45Z and 2026-10-09T02:15Z: 1
- between 2026-10-14T01:15Z and 2026-10-14T01:45Z: 1
- between 2026-10-15T01:45Z and 2026-10-15T02:15Z: 1
- between 2026-10-15T02:15Z and 2026-10-15T02:45Z: 1
- between 2026-10-15T22:45Z and 2026-10-16T10:45Z: 47
- between 2026-10-16T13:30Z and 2026-10-16T14:00Z: 1
- between 2026-10-16T14:15Z and 2026-10-16T14:45Z: 1
- between 2026-10-19T09:00Z and 2026-10-19T10:15Z: 4
- between 2026-10-19T20:45Z and 2026-10-19T21:15Z: 1
- between 2026-10-26T14:30Z and 2026-10-26T15:15Z: 2
- between 2026-10-27T09:00Z and 2026-10-27T09:30Z: 1
-Present instants where sensors have no measurement:
- (none)
-Rejected measurements in the window, per sensor (start → end of each run of consecutive steps, count):
- p1_r (190): 2026-10-01T21:00Z → 2026-10-02T01:45Z (20); 2026-10-02T02:15Z → 07:45Z (23); 2026-10-08T03:45Z → 05:15Z (7); 2026-10-08T05:45Z → 07:00Z (6); 2026-10-08T07:45Z → 08:00Z (2); 2026-10-08T08:30Z → 09:00Z (3); 2026-10-08T13:15Z; 2026-10-08T14:00Z → 15:15Z (6); 2026-10-08T16:00Z; 2026-10-08T17:30Z → 18:00Z (3); 2026-10-09T04:15Z → 04:30Z (2); 2026-10-10T08:15Z → 09:30Z (6); 2026-10-18T05:15Z → 06:00Z (4); 2026-10-18T21:30Z → 23:45Z (10); 2026-10-20T18:00Z; 2026-10-20T20:45Z; 2026-10-20T22:30Z; 2026-10-20T23:15Z → 2026-10-21T00:45Z (7); 2026-10-21T01:15Z → 04:30Z (14); 2026-10-21T05:00Z → 07:45Z (12); 2026-10-21T08:15Z → 08:30Z (2); 2026-10-21T09:00Z → 12:45Z (16); 2026-10-21T13:15Z → 15:15Z (9); 2026-10-23T14:00Z → 14:15Z (2); 2026-10-23T14:45Z → 15:00Z (2); 2026-10-24T22:30Z; 2026-10-24T23:00Z → 2026-10-25T05:00Z (25); 2026-10-25T13:45Z; 2026-10-25T14:30Z; 2026-10-25T16:15Z
- r1_r (260): 2026-10-01T22:45Z → 2026-10-02T01:45Z (13); 2026-10-02T02:15Z; 2026-10-02T02:45Z; 2026-10-02T03:15Z; 2026-10-02T03:45Z → 04:00Z (2); 2026-10-02T04:30Z; 2026-10-02T05:30Z → 06:00Z (3); 2026-10-02T06:30Z → 07:30Z (5); 2026-10-02T10:00Z → 10:15Z (2); 2026-10-08T07:45Z; 2026-10-08T08:30Z → 09:00Z (3); 2026-10-08T09:45Z; 2026-10-09T04:00Z → 04:45Z (4); 2026-10-09T10:00Z; 2026-10-10T08:30Z; 2026-10-11T10:00Z; 2026-10-19T00:15Z → 00:30Z (2); 2026-10-21T03:30Z; 2026-10-21T04:30Z → 05:45Z (6); 2026-10-21T06:15Z; 2026-10-21T06:45Z → 11:30Z (20); 2026-10-21T12:00Z; 2026-10-21T12:30Z; 2026-10-21T16:45Z → 17:00Z (2); 2026-10-21T17:30Z → 18:15Z (4); 2026-10-22T11:30Z; 2026-10-22T12:30Z → 13:15Z (4); 2026-10-23T04:00Z; 2026-10-23T05:45Z → 06:00Z (2); 2026-10-23T06:30Z → 09:00Z (11); 2026-10-23T13:45Z → 15:45Z (9); 2026-10-23T16:30Z → 17:45Z (6); 2026-10-23T18:15Z; 2026-10-24T02:00Z; 2026-10-24T07:15Z → 14:30Z (30); 2026-10-24T22:15Z → 2026-10-25T10:30Z (50); 2026-10-25T11:15Z → 12:15Z (5); 2026-10-25T14:30Z; 2026-10-25T15:30Z → 19:00Z (15); 2026-10-26T08:45Z → 11:45Z (13); 2026-10-27T06:15Z → 09:00Z (12); 2026-10-27T09:30Z → 11:30Z (9); 2026-10-28T07:15Z; 2026-10-28T08:15Z → 10:15Z (9)
- Massif 2 (1452): 2026-10-01T07:30Z → 07:45Z (2); 2026-10-01T22:45Z → 2026-10-02T00:15Z (7); 2026-10-02T00:45Z → 01:00Z (2); 2026-10-02T01:30Z → 01:45Z (2); 2026-10-02T03:15Z → 04:45Z (7); 2026-10-02T05:15Z → 06:00Z (4); 2026-10-02T06:30Z → 07:30Z (5); 2026-10-02T08:00Z → 08:15Z (2); 2026-10-02T10:45Z → 11:30Z (4); 2026-10-02T21:45Z → 22:00Z (2); 2026-10-06T10:30Z → 10:45Z (2); 2026-10-06T11:15Z → 12:00Z (4); 2026-10-06T13:15Z → 13:45Z (3); 2026-10-07T05:45Z → 08:45Z (13); 2026-10-07T11:00Z → 11:15Z (2); 2026-10-07T12:15Z → 12:30Z (2); 2026-10-08T07:45Z; 2026-10-08T08:45Z → 09:15Z (3); 2026-10-08T09:45Z; 2026-10-08T18:30Z → 19:00Z (3); 2026-10-08T23:30Z → 2026-10-09T01:45Z (10); 2026-10-09T02:15Z → 02:30Z (2); 2026-10-09T03:15Z → 05:45Z (11); 2026-10-09T07:00Z → 11:45Z (20); 2026-10-09T12:45Z; 2026-10-10T00:45Z → 07:45Z (29); 2026-10-10T08:30Z; 2026-10-10T09:15Z; 2026-10-10T09:45Z → 12:15Z (11); 2026-10-10T20:00Z → 23:15Z (14); 2026-10-11T01:45Z → 02:15Z (3); 2026-10-11T06:15Z → 15:30Z (38); 2026-10-11T16:00Z → 16:15Z (2); 2026-10-11T17:00Z → 2026-10-12T06:30Z (55); 2026-10-12T07:00Z; 2026-10-12T07:45Z; 2026-10-12T10:15Z → 2026-10-13T06:15Z (81); 2026-10-13T10:30Z → 16:00Z (23); 2026-10-13T17:45Z → 2026-10-14T01:15Z (31); 2026-10-14T01:45Z → 15:00Z (54); 2026-10-14T18:30Z; 2026-10-14T20:00Z → 20:15Z (2); 2026-10-14T21:15Z → 22:15Z (5); 2026-10-14T22:45Z → 2026-10-15T01:45Z (13); 2026-10-15T02:15Z; 2026-10-15T02:45Z → 14:15Z (47); 2026-10-15T19:45Z → 20:30Z (4); 2026-10-15T21:30Z → 22:00Z (3); 2026-10-15T22:30Z; 2026-10-16T10:45Z → 12:45Z (9); 2026-10-16T13:15Z; 2026-10-16T19:15Z; 2026-10-16T20:30Z; 2026-10-16T21:45Z → 2026-10-17T07:45Z (41); 2026-10-17T08:45Z; 2026-10-17T11:45Z → 15:30Z (16); 2026-10-17T16:30Z; 2026-10-17T18:00Z; 2026-10-17T18:30Z → 20:45Z (10); 2026-10-17T21:45Z; 2026-10-17T23:45Z; 2026-10-18T00:30Z → 01:15Z (4); 2026-10-18T05:45Z → 07:30Z (8); 2026-10-18T08:30Z; 2026-10-18T09:00Z; 2026-10-18T09:45Z → 12:15Z (11); 2026-10-18T12:45Z → 13:30Z (4); 2026-10-18T14:30Z; 2026-10-18T15:15Z; 2026-10-18T15:45Z → 16:15Z (3); 2026-10-18T17:00Z; 2026-10-18T20:00Z → 20:45Z (4); 2026-10-18T22:45Z → 2026-10-19T05:15Z (27); 2026-10-19T07:00Z → 07:30Z (3); 2026-10-19T12:45Z; 2026-10-19T19:45Z → 20:00Z (2); 2026-10-19T22:30Z → 2026-10-20T05:30Z (29); 2026-10-20T08:45Z; 2026-10-20T13:00Z; 2026-10-20T15:30Z; 2026-10-20T17:00Z → 17:15Z (2); 2026-10-20T17:45Z; 2026-10-20T18:45Z → 20:15Z (7); 2026-10-20T21:00Z; 2026-10-20T21:30Z → 22:45Z (6); 2026-10-21T02:15Z; 2026-10-21T02:45Z → 05:45Z (13); 2026-10-21T06:15Z → 09:15Z (13); 2026-10-21T09:45Z → 10:00Z (2); 2026-10-21T10:30Z → 11:15Z (4); 2026-10-21T12:00Z; 2026-10-21T15:30Z → 16:00Z (3); 2026-10-21T19:45Z; 2026-10-21T20:30Z → 2026-10-22T18:00Z (87); 2026-10-22T18:30Z → 19:45Z (6); 2026-10-23T02:00Z → 13:00Z (45); 2026-10-23T14:45Z → 18:30Z (16); 2026-10-23T20:00Z → 2026-10-26T14:30Z (267); 2026-10-26T15:15Z → 15:45Z (3); 2026-10-26T18:30Z → 2026-10-27T09:00Z (59); 2026-10-27T09:30Z → 14:30Z (21); 2026-10-27T20:15Z → 2026-10-28T12:15Z (65); 2026-10-28T20:45Z → 21:00Z (2); 2026-10-28T23:00Z → 2026-10-29T09:15Z (42); 2026-10-29T11:00Z → 17:45Z (28); 2026-10-29T20:15Z; 2026-10-29T21:15Z → 21:45Z (3); 2026-10-29T22:15Z → 22:45Z (3); 2026-10-29T23:30Z; 2026-10-30T00:00Z; 2026-10-30T00:45Z; 2026-10-30T02:15Z; 2026-10-30T05:00Z → 06:00Z (5); 2026-10-31T12:00Z → 13:45Z (8); 2026-10-31T21:00Z → 22:30Z (7)
- Pont Ernen (179): 2026-10-01T22:45Z → 2026-10-02T00:15Z (7); 2026-10-02T00:45Z → 01:45Z (5); 2026-10-02T03:15Z; 2026-10-02T03:45Z → 04:00Z (2); 2026-10-02T04:30Z; 2026-10-02T05:30Z → 06:00Z (3); 2026-10-02T06:30Z → 07:30Z (5); 2026-10-02T10:00Z → 10:15Z (2); 2026-10-08T08:30Z → 09:00Z (3); 2026-10-08T09:45Z; 2026-10-09T04:00Z → 04:30Z (3); 2026-10-19T00:15Z → 00:30Z (2); 2026-10-21T04:30Z → 05:45Z (6); 2026-10-21T06:15Z; 2026-10-21T06:45Z → 11:30Z (20); 2026-10-21T12:00Z; 2026-10-21T12:30Z; 2026-10-21T17:00Z; 2026-10-21T17:30Z; 2026-10-21T18:00Z; 2026-10-23T08:45Z; 2026-10-23T13:45Z → 15:45Z (9); 2026-10-23T16:30Z → 17:45Z (6); 2026-10-23T18:15Z; 2026-10-24T02:00Z; 2026-10-24T09:45Z → 12:00Z (10); 2026-10-24T12:45Z → 13:15Z (3); 2026-10-24T13:45Z; 2026-10-24T14:15Z; 2026-10-24T22:30Z → 2026-10-25T10:15Z (48); 2026-10-25T11:15Z → 12:15Z (5); 2026-10-25T14:30Z; 2026-10-25T15:30Z → 19:00Z (15); 2026-10-26T10:45Z → 11:30Z (4); 2026-10-27T09:30Z; 2026-10-27T10:30Z; 2026-10-28T09:15Z → 10:00Z (4)
- Sellette 3 (190): 2026-10-01T21:00Z → 2026-10-02T01:45Z (20); 2026-10-02T02:15Z → 07:45Z (23); 2026-10-08T03:45Z → 05:15Z (7); 2026-10-08T05:45Z → 07:00Z (6); 2026-10-08T07:45Z → 08:00Z (2); 2026-10-08T08:30Z → 09:00Z (3); 2026-10-08T13:15Z; 2026-10-08T14:00Z → 15:15Z (6); 2026-10-08T16:00Z; 2026-10-08T17:30Z → 18:00Z (3); 2026-10-09T04:15Z → 04:30Z (2); 2026-10-10T08:15Z → 09:30Z (6); 2026-10-18T05:15Z → 06:00Z (4); 2026-10-18T21:30Z → 23:45Z (10); 2026-10-20T18:00Z; 2026-10-20T20:45Z; 2026-10-20T22:30Z; 2026-10-20T23:15Z → 2026-10-21T00:45Z (7); 2026-10-21T01:15Z → 04:30Z (14); 2026-10-21T05:00Z → 07:45Z (12); 2026-10-21T08:15Z → 08:30Z (2); 2026-10-21T09:00Z → 12:45Z (16); 2026-10-21T13:15Z → 15:15Z (9); 2026-10-23T14:00Z → 14:15Z (2); 2026-10-23T14:45Z → 15:00Z (2); 2026-10-24T22:30Z; 2026-10-24T23:00Z → 2026-10-25T05:00Z (25); 2026-10-25T13:45Z; 2026-10-25T14:30Z; 2026-10-25T16:15Z
- Sellette 4 (342): 2026-10-01T21:00Z → 2026-10-02T01:45Z (20); 2026-10-02T02:15Z → 08:30Z (26); 2026-10-08T03:45Z → 10:45Z (29); 2026-10-08T13:30Z → 2026-10-09T01:45Z (50); 2026-10-09T02:15Z; 2026-10-09T03:45Z → 04:45Z (5); 2026-10-09T05:30Z; 2026-10-10T08:30Z; 2026-10-10T09:15Z; 2026-10-18T05:15Z → 07:15Z (9); 2026-10-18T21:00Z → 2026-10-19T01:00Z (17); 2026-10-20T15:30Z → 18:30Z (13); 2026-10-20T20:30Z → 21:15Z (4); 2026-10-20T21:45Z → 2026-10-21T16:30Z (76); 2026-10-23T13:30Z → 17:15Z (16); 2026-10-23T18:45Z; 2026-10-24T22:15Z → 2026-10-25T08:30Z (42); 2026-10-25T11:45Z; 2026-10-25T12:15Z; 2026-10-25T12:45Z → 19:30Z (28)
- Sellette 5 (333): 2026-10-01T21:00Z → 2026-10-02T01:45Z (20); 2026-10-02T02:15Z → 08:00Z (24); 2026-10-08T03:45Z → 09:15Z (23); 2026-10-08T12:00Z → 12:30Z (3); 2026-10-08T13:00Z; 2026-10-08T13:30Z → 15:15Z (8); 2026-10-08T15:45Z → 21:45Z (25); 2026-10-09T00:00Z → 00:15Z (2); 2026-10-09T01:30Z → 01:45Z (2); 2026-10-09T02:15Z; 2026-10-09T03:45Z → 07:45Z (17); 2026-10-10T08:00Z → 11:15Z (14); 2026-10-18T05:15Z → 07:00Z (8); 2026-10-18T21:00Z → 2026-10-19T01:00Z (17); 2026-10-20T05:30Z → 05:45Z (2); 2026-10-20T15:45Z → 18:45Z (13); 2026-10-20T20:45Z → 2026-10-21T15:45Z (77); 2026-10-23T13:15Z → 15:00Z (8); 2026-10-23T16:45Z; 2026-10-24T22:00Z → 2026-10-25T05:15Z (30); 2026-10-25T07:00Z; 2026-10-25T11:00Z → 19:45Z (36)
- Sellette 6 (1651): 2026-10-01T07:30Z → 07:45Z (2); 2026-10-01T09:30Z → 11:30Z (9); 2026-10-01T22:45Z → 2026-10-02T00:15Z (7); 2026-10-02T00:45Z → 01:45Z (5); 2026-10-02T03:15Z → 04:45Z (7); 2026-10-02T05:15Z → 08:15Z (13); 2026-10-02T10:00Z → 10:30Z (3); 2026-10-02T13:15Z → 16:30Z (14); 2026-10-02T17:30Z → 18:15Z (4); 2026-10-02T23:45Z → 2026-10-03T03:30Z (16); 2026-10-03T04:15Z → 06:45Z (11); 2026-10-03T08:00Z → 12:15Z (18); 2026-10-03T18:45Z → 22:00Z (14); 2026-10-03T22:30Z; 2026-10-03T23:00Z; 2026-10-03T23:30Z; 2026-10-04T00:00Z → 00:30Z (3); 2026-10-04T01:00Z → 01:15Z (2); 2026-10-04T02:00Z → 02:45Z (4); 2026-10-04T03:30Z → 03:45Z (2); 2026-10-04T04:15Z → 05:15Z (5); 2026-10-04T05:45Z; 2026-10-04T06:30Z → 06:45Z (2); 2026-10-04T07:15Z; 2026-10-04T09:00Z → 13:00Z (17); 2026-10-04T18:45Z; 2026-10-04T19:15Z; 2026-10-04T20:00Z → 21:15Z (6); 2026-10-05T07:30Z → 08:15Z (4); 2026-10-05T10:00Z → 11:30Z (7); 2026-10-05T12:30Z → 14:00Z (7); 2026-10-05T18:30Z → 19:15Z (4); 2026-10-05T21:30Z → 22:30Z (5); 2026-10-06T01:00Z; 2026-10-06T01:45Z → 04:15Z (11); 2026-10-06T04:45Z → 06:00Z (6); 2026-10-06T07:00Z; 2026-10-06T10:00Z → 13:45Z (16); 2026-10-06T17:15Z → 17:30Z (2); 2026-10-06T18:00Z → 20:30Z (11); 2026-10-06T21:00Z; 2026-10-07T01:15Z → 05:45Z (19); 2026-10-07T07:30Z → 09:00Z (7); 2026-10-07T10:00Z; 2026-10-07T10:45Z → 14:15Z (15); 2026-10-07T15:15Z → 15:30Z (2); 2026-10-07T19:45Z; 2026-10-08T05:45Z → 06:15Z (3); 2026-10-08T07:45Z → 11:30Z (16); 2026-10-08T15:15Z → 15:30Z (2); 2026-10-08T18:30Z → 23:45Z (22); 2026-10-09T00:15Z; 2026-10-09T01:30Z → 01:45Z (2); 2026-10-09T02:15Z → 03:15Z (5); 2026-10-09T04:00Z → 04:45Z (4); 2026-10-09T07:15Z → 08:30Z (6); 2026-10-09T10:15Z → 18:30Z (34); 2026-10-09T20:00Z → 2026-10-10T04:30Z (35); 2026-10-10T05:00Z → 14:15Z (38); 2026-10-10T20:15Z → 22:15Z (9); 2026-10-11T07:45Z → 15:30Z (32); 2026-10-11T16:00Z → 16:15Z (2); 2026-10-12T10:15Z → 16:30Z (26); 2026-10-12T21:15Z → 22:00Z (4); 2026-10-12T22:45Z → 2026-10-13T06:30Z (32); 2026-10-13T07:45Z → 08:45Z (5); 2026-10-13T10:00Z → 13:30Z (15); 2026-10-13T18:00Z → 18:30Z (3); 2026-10-13T19:00Z → 23:00Z (17); 2026-10-13T23:30Z → 2026-10-14T00:45Z (6); 2026-10-14T01:45Z → 09:00Z (30); 2026-10-14T10:00Z → 13:00Z (13); 2026-10-14T18:45Z; 2026-10-14T20:15Z → 21:15Z (5); 2026-10-14T22:00Z → 22:30Z (3); 2026-10-14T23:00Z → 2026-10-15T01:45Z (12); 2026-10-15T02:15Z; 2026-10-15T02:45Z → 05:45Z (13); 2026-10-15T06:30Z → 07:00Z (3); 2026-10-15T07:30Z; 2026-10-15T10:15Z → 13:15Z (13); 2026-10-15T18:15Z → 18:30Z (2); 2026-10-15T19:30Z; 2026-10-15T20:15Z → 21:30Z (6); 2026-10-15T22:00Z → 22:15Z (2); 2026-10-15T22:45Z; 2026-10-16T11:00Z → 12:45Z (8); 2026-10-16T18:15Z → 20:00Z (8); 2026-10-16T20:45Z → 23:00Z (10); 2026-10-16T23:30Z → 2026-10-17T09:30Z (41); 2026-10-17T10:45Z → 15:15Z (19); 2026-10-17T18:00Z → 18:15Z (2); 2026-10-17T23:00Z; 2026-10-18T00:45Z → 01:15Z (3); 2026-10-18T05:15Z → 06:30Z (6); 2026-10-18T08:30Z → 09:15Z (4); 2026-10-18T12:00Z → 17:45Z (24); 2026-10-18T18:45Z → 19:15Z (3); 2026-10-18T21:15Z; 2026-10-18T21:45Z → 2026-10-19T05:15Z (31); 2026-10-19T06:45Z → 09:00Z (10); 2026-10-19T10:15Z → 12:30Z (10); 2026-10-19T18:15Z; 2026-10-19T22:45Z → 2026-10-20T02:15Z (15); 2026-10-20T02:45Z → 08:00Z (22); 2026-10-20T12:00Z; 2026-10-20T14:00Z → 14:30Z (3); 2026-10-20T16:15Z; 2026-10-20T16:45Z; 2026-10-20T18:00Z → 18:15Z (2); 2026-10-20T20:15Z → 21:00Z (4); 2026-10-20T23:00Z → 2026-10-21T12:45Z (56); 2026-10-21T15:15Z; 2026-10-22T09:00Z → 14:45Z (24); 2026-10-22T18:00Z → 2026-10-23T01:00Z (29); 2026-10-23T01:45Z; 2026-10-23T02:15Z → 09:00Z (28); 2026-10-23T13:00Z → 13:15Z (2); 2026-10-23T14:45Z → 15:15Z (3); 2026-10-23T17:00Z → 17:15Z (2); 2026-10-23T18:15Z → 18:30Z (2); 2026-10-23T21:15Z → 21:30Z (2); 2026-10-24T07:15Z → 2026-10-25T21:30Z (154); 2026-10-26T00:30Z → 05:15Z (20); 2026-10-26T05:45Z → 14:30Z (36); 2026-10-26T15:15Z → 22:00Z (28); 2026-10-26T23:15Z; 2026-10-27T04:30Z; 2026-10-27T21:30Z → 2026-10-28T01:30Z (17); 2026-10-28T04:30Z → 07:00Z (11); 2026-10-28T08:45Z → 12:00Z (14); 2026-10-28T15:00Z; 2026-10-28T17:00Z → 18:00Z (5); 2026-10-28T20:15Z; 2026-10-28T21:30Z → 2026-10-29T07:30Z (41); 2026-10-29T11:00Z → 2026-10-30T07:30Z (83); 2026-10-30T09:45Z → 12:00Z (10); 2026-10-30T12:30Z → 2026-10-31T15:45Z (110); 2026-10-31T16:45Z → 20:30Z (16); 2026-10-31T23:30Z → 2026-11-01T00:00Z (3)
-Retained references by the compensation (inlier empty over the window: reproj_err filled instead) out of 2, number of instants: 2: 2558, 0: 357
-Instants where references are not retained (runs of consecutive steps with the same references out; r = rejected, empty = reproj_err empty, otherwise the inlier value):
- 2026-10-01T21:00Z → 22:30Z (7): 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-01T22:45Z → 2026-10-02T02:15Z (14): 0 retained; out: p1_r (r), r1_r (r)
- 2026-10-02T02:30Z: 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-02T02:45Z: 0 retained; out: p1_r (r), r1_r (r)
- 2026-10-02T03:00Z: 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-02T03:15Z: 0 retained; out: p1_r (r), r1_r (r)
- 2026-10-02T03:30Z: 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-02T03:45Z → 04:00Z (2): 0 retained; out: p1_r (r), r1_r (r)
- 2026-10-02T04:15Z: 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-02T04:30Z: 0 retained; out: p1_r (r), r1_r (r)
- 2026-10-02T04:45Z → 05:15Z (3): 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-02T05:30Z → 06:00Z (3): 0 retained; out: p1_r (r), r1_r (r)
- 2026-10-02T06:15Z: 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-02T06:30Z → 07:30Z (5): 0 retained; out: p1_r (r), r1_r (r)
- 2026-10-02T07:45Z: 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-02T10:00Z → 10:15Z (2): 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-08T03:45Z → 05:15Z (7): 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-08T05:45Z → 07:00Z (6): 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-08T07:45Z: 0 retained; out: p1_r (r), r1_r (r)
- 2026-10-08T08:00Z: 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-08T08:30Z → 09:00Z (3): 0 retained; out: p1_r (r), r1_r (r)
- 2026-10-08T09:45Z: 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-08T13:15Z: 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-08T14:00Z → 15:15Z (6): 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-08T16:00Z: 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-08T17:30Z → 18:00Z (3): 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-09T04:00Z: 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-09T04:15Z → 04:30Z (2): 0 retained; out: p1_r (r), r1_r (r)
- 2026-10-09T04:45Z: 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-09T10:00Z: 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-10T08:15Z: 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-10T08:30Z: 0 retained; out: p1_r (r), r1_r (r)
- 2026-10-10T08:45Z → 09:30Z (4): 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-11T10:00Z: 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-18T05:15Z → 06:00Z (4): 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-18T21:30Z → 23:45Z (10): 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-19T00:15Z → 00:30Z (2): 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-20T18:00Z: 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-20T20:45Z: 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-20T22:30Z: 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-20T23:15Z → 2026-10-21T00:45Z (7): 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-21T01:15Z → 03:15Z (9): 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-21T03:30Z: 0 retained; out: p1_r (r), r1_r (r)
- 2026-10-21T03:45Z → 04:15Z (3): 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-21T04:30Z: 0 retained; out: p1_r (r), r1_r (r)
- 2026-10-21T04:45Z: 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-21T05:00Z → 05:45Z (4): 0 retained; out: p1_r (r), r1_r (r)
- 2026-10-21T06:00Z: 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-21T06:15Z: 0 retained; out: p1_r (r), r1_r (r)
- 2026-10-21T06:30Z: 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-21T06:45Z → 07:45Z (5): 0 retained; out: p1_r (r), r1_r (r)
- 2026-10-21T08:00Z: 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-21T08:15Z → 08:30Z (2): 0 retained; out: p1_r (r), r1_r (r)
- 2026-10-21T08:45Z: 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-21T09:00Z → 11:30Z (11): 0 retained; out: p1_r (r), r1_r (r)
- 2026-10-21T11:45Z: 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-21T12:00Z: 0 retained; out: p1_r (r), r1_r (r)
- 2026-10-21T12:15Z: 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-21T12:30Z: 0 retained; out: p1_r (r), r1_r (r)
- 2026-10-21T12:45Z: 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-21T13:15Z → 15:15Z (9): 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-21T16:45Z → 17:00Z (2): 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-21T17:30Z → 18:15Z (4): 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-22T11:30Z: 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-22T12:30Z → 13:15Z (4): 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-23T04:00Z: 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-23T05:45Z → 06:00Z (2): 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-23T06:30Z → 09:00Z (11): 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-23T13:45Z: 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-23T14:00Z → 14:15Z (2): 0 retained; out: p1_r (r), r1_r (r)
- 2026-10-23T14:30Z: 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-23T14:45Z → 15:00Z (2): 0 retained; out: p1_r (r), r1_r (r)
- 2026-10-23T15:15Z → 15:45Z (3): 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-23T16:30Z → 17:45Z (6): 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-23T18:15Z: 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-24T02:00Z: 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-24T07:15Z → 14:30Z (30): 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-24T22:15Z: 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-24T22:30Z: 0 retained; out: p1_r (r), r1_r (r)
- 2026-10-24T22:45Z: 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-24T23:00Z → 2026-10-25T05:00Z (25): 0 retained; out: p1_r (r), r1_r (r)
- 2026-10-25T05:15Z → 10:30Z (22): 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-25T11:15Z → 12:15Z (5): 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-25T13:45Z: 0 retained; out: p1_r (r), r1_r (empty)
- 2026-10-25T14:30Z: 0 retained; out: p1_r (r), r1_r (r)
- 2026-10-25T15:30Z → 16:00Z (3): 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-25T16:15Z: 0 retained; out: p1_r (r), r1_r (r)
- 2026-10-25T16:30Z → 19:00Z (11): 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-26T08:45Z → 11:45Z (13): 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-27T06:15Z → 11:30Z (21): 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-28T07:15Z: 0 retained; out: p1_r (empty), r1_r (r)
- 2026-10-28T08:15Z → 10:15Z (9): 0 retained; out: p1_r (empty), r1_r (r)
-
-Camera pose in the window: 2558 registrations, 2026-10-01T00:00Z → 2026-11-01T00:00Z
-Measurement instants without a pose (no registration): 357 of 2915
- 2026-10-01T21:00Z → 2026-10-02T07:45Z (43)
- 2026-10-02T10:00Z → 10:15Z (2)
- 2026-10-08T03:45Z → 05:15Z (7)
- 2026-10-08T05:45Z → 07:00Z (6)
- 2026-10-08T07:45Z → 08:00Z (2)
- 2026-10-08T08:30Z → 09:00Z (3)
- 2026-10-08T09:45Z
- 2026-10-08T13:15Z
- 2026-10-08T14:00Z → 15:15Z (6)
- 2026-10-08T16:00Z
- 2026-10-08T17:30Z → 18:00Z (3)
- 2026-10-09T04:00Z → 04:45Z (4)
- 2026-10-09T10:00Z
- 2026-10-10T08:15Z → 09:30Z (6)
- 2026-10-11T10:00Z
- 2026-10-18T05:15Z → 06:00Z (4)
- 2026-10-18T21:30Z → 23:45Z (10)
- 2026-10-19T00:15Z → 00:30Z (2)
- 2026-10-20T18:00Z
- 2026-10-20T20:45Z
- 2026-10-20T22:30Z
- 2026-10-20T23:15Z → 2026-10-21T00:45Z (7)
- 2026-10-21T01:15Z → 12:45Z (47)
- 2026-10-21T13:15Z → 15:15Z (9)
- 2026-10-21T16:45Z → 17:00Z (2)
- 2026-10-21T17:30Z → 18:15Z (4)
- 2026-10-22T11:30Z
- 2026-10-22T12:30Z → 13:15Z (4)
- 2026-10-23T04:00Z
- 2026-10-23T05:45Z → 06:00Z (2)
- 2026-10-23T06:30Z → 09:00Z (11)
- 2026-10-23T13:45Z → 15:45Z (9)
- 2026-10-23T16:30Z → 17:45Z (6)
- 2026-10-23T18:15Z
- 2026-10-24T02:00Z
- 2026-10-24T07:15Z → 14:30Z (30)
- 2026-10-24T22:15Z → 2026-10-25T10:30Z (50)
- 2026-10-25T11:15Z → 12:15Z (5)
- 2026-10-25T13:45Z
- 2026-10-25T14:30Z
- 2026-10-25T15:30Z → 19:00Z (15)
- 2026-10-26T08:45Z → 11:45Z (13)
- 2026-10-27T06:15Z → 11:30Z (21)
- 2026-10-28T07:15Z
- 2026-10-28T08:15Z → 10:15Z (9)
diff --git a/auto/analyses/long-labels/FLORIDA/work/log.jsonl b/auto/analyses/long-labels/FLORIDA/work/log.jsonl
deleted file mode 100644
index 311f56f..0000000
--- a/auto/analyses/long-labels/FLORIDA/work/log.jsonl
+++ /dev/null
@@ -1,45 +0,0 @@
-{"type":"system","subtype":"init","cwd":"/home/maxime/aimsight-app","session_id":"4d470fcf-4228-4dc5-8c0d-b90f8d37cbb1","tools":["Read","Bash","Write"],"mcp_servers":[],"model":"claude-opus-5-5","permissionMode":"acceptEdits","slash_commands":["deep-research","design","slides","design-sync","dataviz","artifact-diagramming","whiteboard","artifact-capabilities","update-config","verify","debug","code-review","simplify","batch","fewer-permission-prompts","doctor","loop","schedule","claude-api","workflow-authoring","run","run-skill-generator","plugin-authoring","advisor","agents","auto-mode-setup","autocompact","clear","color","compact","config","output-style","context","effort","fast","focus","heapdump","init","mcp","import","model","__remote-workflow","workflow-launch-exec","reload-plugins","reload-skills","rename","ultrareview","security-review","usage-credits","extra-usage","usage","insights","recap","skill-doctor","goal","design-consent","design-revoke","list-agents","team-onboarding"],"terminal_slash_commands":["doctor","color","focus","reload-plugins"],"apiKeySource":"none","claude_code_version":"2.1.326","output_style":"default","agents":["agents:analyst","agents:support","agents:upgrader","agents:validator","claude","claude-code-guide","Explore","general-purpose","Plan","statusline-setup"],"skills":["deep-research","design","slides","design-sync","dataviz","artifact-diagramming","whiteboard","artifact-capabilities","update-config","verify","debug","code-review","simplify","batch","fewer-permission-prompts","doctor","loop","schedule","claude-api","workflow-authoring","run","run-skill-generator","plugin-authoring"],"plugins":[{"name":"agents","path":"/home/maxime/aimsight-app/agents","source":"agents@inline"},{"name":"cc-plugin-agents-md","path":"builtin","source":"cc-plugin-agents-md@builtin"},{"name":"cc-plugin-telemetry","path":"builtin","source":"cc-plugin-telemetry@builtin"},{"name":"cc-plugin-privacy","path":"builtin","source":"cc-plugin-privacy@builtin"},{"name":"cc-plugin-plugin-authoring","path":"builtin","source":"cc-plugin-plugin-authoring@builtin"}],"capabilities":["interrupt_receipt_v1","interrupt_cancel_queued_v1","interrupt_send_now_v1","interrupt_requeue_taken_v1","msg_lifecycle_v1","request_marker_lists_v1","ask_user_question_unanswered_v1","lifecycle_wakeup_source_v1","sdk_mcp_tools_list_changed","sdk_mcp_manifests","mcp_read_resource_v1","mcp_tool_ui_meta_v1","ui_surface_v1","mcp_call_result_not_for_model_v1","mcp_call_check_permissions_v1","voice_call_talk_line_v1","withdrawn_files_note_v2","ui_pane_widget_v1","reload_plugins_refuse_if_busy_v1","silent_resend_files_v1"],"analytics_disabled":false,"product_feedback_disabled":false,"uuid":"8f555c87-a3e2-41b5-866a-2e552c0a55fd","memory_paths":{"auto":"/home/maxime/.claude/projects/-home-maxime-aimsight-app/memory/"},"scratchpad_path":"/tmp/claude-1000/-home-maxime-aimsight-app/4d470fcf-4228-4dc5-8c0d-b90f8d37cbb1/scratchpad","original_cwd":"/home/maxime/aimsight-app","additional_directories":["/home/maxime/aimsight-data/data","/home/maxime/aimsight-labeling","/home/maxime/aimsight-tools"],"messaging_socket_path":"/run/user/1000/cc-socks/41403.sock","fast_mode_state":"off","fast_mode_disabled_reason":"sdk_opt_in_required","per_turn_effort_active":true,"ultrathink_available":false,"ultrathink_typed_raises":false,"view_mode":"default","startup_timing":{"entrypoint":"claude-desktop","warm_spare_claimed":false,"plugin_full_loads":0,"user_context_builds":1,"sdk_mcp_dial_runs":0,"sdk_mcp_servers_dialed":0,"flag_fetch_kick":"not_eligible","flag_fetch_kick_judged_at_ms":661,"hooks_init_source":"startup","phases":{"node_boot_ms":376,"settings_load_ms":1,"pre_action_mdm_keychain_ms":7,"pre_action_init_ms":261,"pre_action_client_data_url_ms":0,"pre_action_migrations_ms":0,"pre_action_managed_settings_ms":5,"pre_action_ms":299,"permission_context_ms":308,"setup_import_ms":0,"setup_uds_dir_ms":76,"setup_uds_listen_ms":14,"setup_uds_publish_ms":7,"setup_uds_messaging_ms":101,"setup_hooks_snapshot_ms":0,"setup_file_watcher_ms":0,"setup_release_notes_ms":31,"setup_ms":136,"skills_load_ms":221,"tools_commands_load_ms":82,"model_catalog_decision_ms":45,"mcp_config_wait_ms":16,"mcp_config_load_ms":1,"mcp_connect_ms":3,"hooks_init_ms":29,"print_import_ms":41,"grove_check_ms":24,"headless_prologue_ms":30,"initial_messages_load_ms":1,"headless_post_load_ms":5,"input_ready_ms":1521,"first_message_read_ms":1533,"sdk_mcp_update_ms":3,"first_message_handle_ms":3,"first_message_handle_cpu_ms":3,"first_message_handle_loop_lag_ms":0,"mcp_prewait_ms":10,"qe_system_prompt_ms":263,"prompt_submit_hooks_ms":5,"qe_plugin_skills_load_ms":6,"init_emit_ms":5},"time_origin_ms":1794947454986.3423,"phase_start_ms":{"node_boot_ms":0,"settings_load_ms":384,"pre_action_mdm_keychain_ms":391,"pre_action_init_ms":398,"pre_action_client_data_url_ms":659,"pre_action_migrations_ms":663,"pre_action_managed_settings_ms":664,"pre_action_ms":391,"permission_context_ms":702,"setup_import_ms":1012,"setup_uds_dir_ms":1021,"setup_uds_listen_ms":1097,"setup_uds_publish_ms":1110,"setup_uds_messaging_ms":1018,"setup_hooks_snapshot_ms":1122,"setup_file_watcher_ms":1122,"setup_release_notes_ms":1125,"setup_ms":1020,"skills_load_ms":1018,"tools_commands_load_ms":1199,"model_catalog_decision_ms":1283,"mcp_config_wait_ms":1346,"mcp_connect_ms":1401,"hooks_init_ms":1381,"print_import_ms":1409,"grove_check_ms":1453,"headless_prologue_ms":1451,"initial_messages_load_ms":1482,"headless_post_load_ms":1482,"input_ready_ms":0,"first_message_read_ms":0,"sdk_mcp_update_ms":1533,"first_message_handle_ms":1533,"mcp_prewait_ms":1540,"qe_system_prompt_ms":1571,"prompt_submit_hooks_ms":1993,"qe_plugin_skills_load_ms":2161,"init_emit_ms":2168}}}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98mXoo8jjgKwfzha5DH","type":"message","role":"assistant","content":[{"type":"thinking","thinking":"","signature":"CAQSsQUKEAgTGAI4AUIIdGhpbmtpbmcSDHVXcSwy21R2JPnzHxoMFBDVj4O9504IT9RyIjDOSvy1tqG2iYneWq8Il0FeJn4qx1GTGpDrYl1go5mLosMFOtPxLSkpc5L6UTuM4LkqzgTd/q2ZJZj86gA+oq3wkDxBFtXfoqlAqAPFShCu7SPdAG5yIvLhoAs1WI3klfXRFnCZf8Mrlf9J4+R2zkoFIb/Mn1d9dYsLTwA7Z80VPOhgAIU/MAOe4gQTc2CIAMjie84ymhS6ivYimEeJvR+CQ1sxJ/h+Axp0GXf9I3liS5g5YKvJJcccr1KIberhIKgkj/03JCMtet2HeBJTzP88ho2O6oBoP55EHb0jwLMR29eprlB2bUPx2apl010LXX3gtOKu7bjkf/+ZBEME+QOE/AmhnDKoiaiDR6akOGOtucxaksLEh1FssC6ucsWWmmgqUmYOqKtSnqfX5qySGolMUTJn44tqufw7BlosioGWi3UNd0mLFEWpSkMhuNQfCpBDYWGCi284rQyYmh5GIE6uvY2tdr7I8WeJfW5wCeNCMqfk0/KNhNBHJ48B3MPT34RayXwSiUzGMh0EJxdTTTIagV7Pt3IVm31oUbx9E1CQQCyN3tGve+O32TV4xafGPAYDvN3L8fdjRYvbC4yURi/vrv5bfdgDIBvdY519iBHKgLTBeIjZh86+ll17EsP4iFjlJAsdomFHvEiUa3bc1H9fiQMK39QoX3YoN1rXu8IUydaHGx9FnBmWpMOQ/r9b4+QsUXxigFWZbhzV6zuT4LehgoWeuxdsNfVQ9hiJIfj/7jyqjRzSaICj0Bp8+0aWkUcIru4X08oxRR/e7IcrerR9DKyH+kOBrrTkroqTgbTfLJC7XNxwOStTdcOJYe0hz4WiLYcCjMJG2Yw/BYg1oBgo7BgB"}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":3899,"cache_read_input_tokens":5976,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":3899},"output_tokens":8,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"4d470fcf-4228-4dc5-8c0d-b90f8d37cbb1","uuid":"b07a2a5b-be44-49b5-b573-ae5dd43e37d3","timestamp":"2026-11-17T20:31:00.614Z","request_id":"req_011Ch98mXZACJL7KnQpThfai","thinking_duration_ms":466,"thinking_display":"updates"}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98mXoo8jjgKwfzha5DH","type":"message","role":"assistant","content":[{"type":"tool_use","id":"toolu_01Fx1eBnvJHuq2LX8rZWBAWZ","name":"Bash","input":{"command":"cd /home/maxime/aimsight-app; cat labeling/auto/analyses/long-labels/FLORIDA/input.jsonl; ls labeling/auto/analyses/long-labels/FLORIDA/ labeling/auto/analyses/ | head -50; wc -l tools/GUIDE.md tools/DATA.md labeling/families.md labeling/labeling-rules.md labeling/reading-rules.md labeling/stations.md","description":"Read input labels and list folders"},"caller":{"type":"direct"}}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":3899,"cache_read_input_tokens":5976,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":3899},"output_tokens":8,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"4d470fcf-4228-4dc5-8c0d-b90f8d37cbb1","uuid":"67d4115c-1abc-4068-9065-c8abb11539a0","timestamp":"2026-11-17T20:31:01.801Z","request_id":"req_011Ch98mXZACJL7KnQpThfai","wire_tool_inputs":{"toolu_01Fx1eBnvJHuq2LX8rZWBAWZ":{"command":"cd /home/maxime/aimsight-app; cat labeling/auto/analyses/long-labels/FLORIDA/input.jsonl; ls labeling/auto/analyses/long-labels/FLORIDA/ labeling/auto/analyses/ | head -50; wc -l tools/GUIDE.md tools/DATA.md labeling/families.md labeling/labeling-rules.md labeling/reading-rules.md labeling/stations.md","description":"Read input labels and list folders"}}}
-{"type":"rate_limit_event","rate_limit_info":{"status":"allowed_warning","resetsAt":1794954600,"rateLimitType":"five_hour","utilization":0.99,"overageStatus":"rejected","overageDisabledReason":"org_level_disabled","isUsingOverage":false,"surpassedThreshold":0.9,"unifiedWindows":{"five_hour":{"utilization":0.99,"resetsAt":1794954600,"status":"allowed_warning","surpassedThreshold":0.9},"seven_day":{"utilization":0.72,"resetsAt":1795302000,"status":"allowed"}},"overageEnabled":false},"uuid":"fbd602ee-5ee7-4121-824d-4b8a41e2b16e","session_id":"4d470fcf-4228-4dc5-8c0d-b90f8d37cbb1"}
-{"type":"system","subtype":"task_summary","detail":"Reading input labels and listing folders","uuid":"3583a2ab-c36d-41be-b1eb-387e80aa8cbe","session_id":"4d470fcf-4228-4dc5-8c0d-b90f8d37cbb1"}
-{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_01Fx1eBnvJHuq2LX8rZWBAWZ","type":"tool_result","content":"{\"id\": \"FLORIDA-1\", \"start\": \"2026-10-01T00:00Z\", \"end\": \"2026-11-01T00:00Z\", \"family\": \"Target issue\", \"description\": \"Sellette 6 is a constantly problematic target: its error_value stays just above the threshold, a large part of its measurements are rejected all month, day and night, whatever the weather: its curve has gaps every day and its kept measurements jump. Seen on the thumbnails: a very small spot, almost invisible by day, very close to the halo of Sellette 5, which is much brighter; on the morning of the 20th, the measurement of Sellette 5 even latched onto the spot of Sellette 6. Ignore its curve; check the orientation or cleanliness of the prism.\", \"review\": \"2026-11-17\"}\n{\"id\": \"FLORIDA-14\", \"start\": \"2026-10-06T10:15Z\", \"end\": \"2026-11-01T00:00Z\", \"family\": \"Target issue\", \"description\": \"Massif 2 becomes a problematic target: by day, its spot is only a point (noon thumbnails of the 3rd and the 6th), and from the 6th its error_value goes above the threshold at times, measurements rejected by day; from the rain episode of the 8th, its spot also weakens at night and does not come back, the majority of its measurements are rejected day and night until the 29th, and its kept measurements change level (corr_y clearly going downward, corr_x going down at the end of the month). On the 30th and 31st, it is kept again, but just under the threshold and with a corr_y much lower than at the start of the month. Seen on the thumbnails: wide and bright spot at night in early October, small and weak afterwards, invisible by day on the 12th, 30th and 31st. Cause not established (prism tarnished, dirty or veiled). Ignore its curve; check the prism.\", \"review\": \"2026-11-17\"}\nlabeling/auto/analyses/:\nBREITHORN_2026-10-03T0000_2026-10-13T0000\nBREITHORN_2026-10-13T0000_2026-10-22T1600\nBREITHORN_2026-10-22T1600_2026-11-01T0000\nCLARIDEN_2026-10-01T0000_2026-10-11T0000\nCLARIDEN_2026-10-11T0000_2026-10-20T0400\nCLARIDEN_2026-10-20T0400_2026-11-01T0010\nFLORIDA_2026-10-01T0000_2026-10-11T0945\nFLORIDA_2026-10-11T0945_2026-10-22T0315\nFLORIDA_2026-10-22T0315_2026-11-01T0000\nJUNGFRAU_2026-09-30T0000_2026-10-10T1615\nJUNGFRAU_2026-10-10T1615_2026-10-21T1030\nJUNGFRAU_2026-10-21T1030_2026-11-01T0000\nLENZSPITZE_2026-10-16T0235_2026-10-23T2355\nLENZSPITZE_2026-10-23T2355_2026-11-01T1140\nMICHIGAN_2026-10-03T0000_2026-10-12T1600\nMICHIGAN_2026-10-12T1600_2026-10-23T2000\nMICHIGAN_2026-10-23T2000_2026-11-01T0000\nNEBRASKA_2026-10-03T0000_2026-10-13T0000\nNEBRASKA_2026-10-13T0000_2026-10-22T0000\nNEBRASKA_2026-10-22T0000_2026-11-01T0000\nNIEDERHORN_2026-10-01T0000_2026-10-11T0500\nNIEDERHORN_2026-10-11T0500_2026-10-21T1200\nNIEDERHORN_2026-10-21T1200_2026-11-01T0000\nNORDEND_2026-08-10T0115_2026-08-23T0515\nNORDEND_2026-08-23T0515_2026-09-04T0615\nNORDEND_2026-09-04T0615_2026-09-17T0545\nNORDEND_2026-09-17T0545_2026-09-30T0415\nNORDEND_2026-09-30T0415_2026-10-13T0745\nNORDEND_2026-10-13T0745_2026-10-24T1630\nNORDEND_2026-10-24T1630_2026-11-07T1400\nSNCF01_2026-10-04T0000_2026-10-14T0645\nSNCF01_2026-10-14T0645_2026-10-22T1030\nSNCF01_2026-10-22T1030_2026-11-01T0000\nWILDSTRUBEL_2026-09-01T0000_2026-09-13T0000\nWILDSTRUBEL_2026-09-13T0000_2026-09-24T0230\nWILDSTRUBEL_2026-09-24T0230_2026-10-06T1945\nWILDSTRUBEL_2026-10-06T1945_2026-10-20T0000\nWILDSTRUBEL_2026-10-20T0000_2026-11-01T0000\nWYOMING_2026-11-06T0805_2026-11-16T0627\nlong-labels\n\nlabeling/auto/analyses/long-labels/FLORIDA/:\ninput.jsonl\nwork\n 240 tools/GUIDE.md\n 74 tools/DATA.md\n 101 labeling/families.md\n 107 labeling/labeling-rules.md\n 100 labeling/reading-rules.md\n 17 labeling/stations.md\n 639 total","is_error":false}]},"parent_tool_use_id":null,"session_id":"4d470fcf-4228-4dc5-8c0d-b90f8d37cbb1","uuid":"b076aa7f-9fb8-43d5-bb7c-389d57faa958","timestamp":"2026-11-17T20:31:02.046Z","tool_use_result":{"stdout":"{\"id\": \"FLORIDA-1\", \"start\": \"2026-10-01T00:00Z\", \"end\": \"2026-11-01T00:00Z\", \"family\": \"Target issue\", \"description\": \"Sellette 6 is a constantly problematic target: its error_value stays just above the threshold, a large part of its measurements are rejected all month, day and night, whatever the weather: its curve has gaps every day and its kept measurements jump. Seen on the thumbnails: a very small spot, almost invisible by day, very close to the halo of Sellette 5, which is much brighter; on the morning of the 20th, the measurement of Sellette 5 even latched onto the spot of Sellette 6. Ignore its curve; check the orientation or cleanliness of the prism.\", \"review\": \"2026-11-17\"}\n{\"id\": \"FLORIDA-14\", \"start\": \"2026-10-06T10:15Z\", \"end\": \"2026-11-01T00:00Z\", \"family\": \"Target issue\", \"description\": \"Massif 2 becomes a problematic target: by day, its spot is only a point (noon thumbnails of the 3rd and the 6th), and from the 6th its error_value goes above the threshold at times, measurements rejected by day; from the rain episode of the 8th, its spot also weakens at night and does not come back, the majority of its measurements are rejected day and night until the 29th, and its kept measurements change level (corr_y clearly going downward, corr_x going down at the end of the month). On the 30th and 31st, it is kept again, but just under the threshold and with a corr_y much lower than at the start of the month. Seen on the thumbnails: wide and bright spot at night in early October, small and weak afterwards, invisible by day on the 12th, 30th and 31st. Cause not established (prism tarnished, dirty or veiled). Ignore its curve; check the prism.\", \"review\": \"2026-11-17\"}\nlabeling/auto/analyses/:\nBREITHORN_2026-10-03T0000_2026-10-13T0000\nBREITHORN_2026-10-13T0000_2026-10-22T1600\nBREITHORN_2026-10-22T1600_2026-11-01T0000\nCLARIDEN_2026-10-01T0000_2026-10-11T0000\nCLARIDEN_2026-10-11T0000_2026-10-20T0400\nCLARIDEN_2026-10-20T0400_2026-11-01T0010\nFLORIDA_2026-10-01T0000_2026-10-11T0945\nFLORIDA_2026-10-11T0945_2026-10-22T0315\nFLORIDA_2026-10-22T0315_2026-11-01T0000\nJUNGFRAU_2026-09-30T0000_2026-10-10T1615\nJUNGFRAU_2026-10-10T1615_2026-10-21T1030\nJUNGFRAU_2026-10-21T1030_2026-11-01T0000\nLENZSPITZE_2026-10-16T0235_2026-10-23T2355\nLENZSPITZE_2026-10-23T2355_2026-11-01T1140\nMICHIGAN_2026-10-03T0000_2026-10-12T1600\nMICHIGAN_2026-10-12T1600_2026-10-23T2000\nMICHIGAN_2026-10-23T2000_2026-11-01T0000\nNEBRASKA_2026-10-03T0000_2026-10-13T0000\nNEBRASKA_2026-10-13T0000_2026-10-22T0000\nNEBRASKA_2026-10-22T0000_2026-11-01T0000\nNIEDERHORN_2026-10-01T0000_2026-10-11T0500\nNIEDERHORN_2026-10-11T0500_2026-10-21T1200\nNIEDERHORN_2026-10-21T1200_2026-11-01T0000\nNORDEND_2026-08-10T0115_2026-08-23T0515\nNORDEND_2026-08-23T0515_2026-09-04T0615\nNORDEND_2026-09-04T0615_2026-09-17T0545\nNORDEND_2026-09-17T0545_2026-09-30T0415\nNORDEND_2026-09-30T0415_2026-10-13T0745\nNORDEND_2026-10-13T0745_2026-10-24T1630\nNORDEND_2026-10-24T1630_2026-11-07T1400\nSNCF01_2026-10-04T0000_2026-10-14T0645\nSNCF01_2026-10-14T0645_2026-10-22T1030\nSNCF01_2026-10-22T1030_2026-11-01T0000\nWILDSTRUBEL_2026-09-01T0000_2026-09-13T0000\nWILDSTRUBEL_2026-09-13T0000_2026-09-24T0230\nWILDSTRUBEL_2026-09-24T0230_2026-10-06T1945\nWILDSTRUBEL_2026-10-06T1945_2026-10-20T0000\nWILDSTRUBEL_2026-10-20T0000_2026-11-01T0000\nWYOMING_2026-11-06T0805_2026-11-16T0627\nlong-labels\n\nlabeling/auto/analyses/long-labels/FLORIDA/:\ninput.jsonl\nwork\n 240 tools/GUIDE.md\n 74 tools/DATA.md\n 101 labeling/families.md\n 107 labeling/labeling-rules.md\n 100 labeling/reading-rules.md\n 17 labeling/stations.md\n 639 total","stderr":"","interrupted":false,"isImage":false,"noOutputExpected":false},"tool_result_meta":[{"id":"toolu_01Fx1eBnvJHuq2LX8rZWBAWZ","permission_decision":{"decision":"accept","source":"config","reason_type":"rule"}}]}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98msoa6AmhQwoppdAXa","type":"message","role":"assistant","content":[{"type":"text","text":"Two labels, both Target issue. Let me read the docs."}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":2089,"cache_read_input_tokens":9875,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":2089},"output_tokens":41,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"4d470fcf-4228-4dc5-8c0d-b90f8d37cbb1","uuid":"86e31e83-2fd1-42e7-8f9f-4f5d2e05db91","timestamp":"2026-11-17T20:31:04.280Z","request_id":"req_011Ch98msd9qgrTSbWA8QFUq"}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98msoa6AmhQwoppdAXa","type":"message","role":"assistant","content":[{"type":"tool_use","id":"toolu_01R2BCrcWoSiSdDurZJFrVcm","name":"Bash","input":{"command":"cd /home/maxime/aimsight-app; cat tools/GUIDE.md tools/DATA.md labeling/labeling-rules.md; ls labeling/auto/analyses/long-labels/FLORIDA/work","description":"Read guide, data docs, labeling rules"},"caller":{"type":"direct"}}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":2089,"cache_read_input_tokens":9875,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":2089},"output_tokens":41,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"4d470fcf-4228-4dc5-8c0d-b90f8d37cbb1","uuid":"aa0e6ef8-c0fa-42f7-8fdd-13417d2f5ceb","timestamp":"2026-11-17T20:31:05.236Z","request_id":"req_011Ch98msd9qgrTSbWA8QFUq","wire_tool_inputs":{"toolu_01R2BCrcWoSiSdDurZJFrVcm":{"command":"cd /home/maxime/aimsight-app; cat tools/GUIDE.md tools/DATA.md labeling/labeling-rules.md; ls labeling/auto/analyses/long-labels/FLORIDA/work","description":"Read guide, data docs, labeling rules"}}}
-{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_01R2BCrcWoSiSdDurZJFrVcm","type":"tool_result","content":"\nOutput too large (70KB). Full output saved to: /home/maxime/.claude/projects/-home-maxime-aimsight-app/4d470fcf-4228-4dc5-8c0d-b90f8d37cbb1/tool-results/bejht3h5f.txt\n\nPreview (first 2KB):\n# Reading the data\n\nThe guide to the reading harness: followed by the analyst; improved by the upgrader (agents repository), run by Optimizer's `optimize` skill, the only one that writes here.\n\nA camera tracks targets (reflectors) fixed on a structure; its own movement is compensated thanks to reference targets, assumed fixed. This movement, the **camera pose** (`pan`, `tilt`, `rotation` in degrees, `scale`, `sigma0` of the registration, in `camera/`), is read before the sensors: it explains a large part of what moves on the curves (D-073). This guide says how to read a station's data: what the curves and the images show, moment by moment. It does not say what they mean: family, known event, hypothesis and verdict are the business of whoever calls you.\n\n## Read first\n\n- `tools/DATA.md`: the files of a station and the meaning of each column, the image quality metrics, the camera images (**first**);\n- `labeling/reading-rules.md`: what the data mean (the measurement chain, gaps, reading rules, false friends).\n\n## The tools\n\nRun them from the root of the calling repository, where `tools/`, `data/` and `labeling/` are links. They return values, never verdicts: you judge. `--out `: where whoever calls you stores your figures; they give it to you. The method (below) says in which order to run them; each section says what a tool returns and how to read it.\n\n| Tool | The question it answers |\n|---|---|\n| [`inventory.py`](#inventory) | What is there, what is missing: files, contents of each source, images, poses, cadence, sensors, rejections |\n| [`summary.py`](#summary) | The usual level of each sensor, then one column by time step |\n| [`plot.py`](#plot) | The series of chosen sensors and columns, as a PNG |\n| [`overview.py`](#overview) | All the sensors together, against the camera pose: common movement, single sensors, residuals, rigid movement |\n| [`ranges.py`](#ranges) | Dated ranges where each sensor leaves its level, at the native step |\n...\n","is_error":false}]},"parent_tool_use_id":null,"session_id":"4d470fcf-4228-4dc5-8c0d-b90f8d37cbb1","uuid":"28450a1a-1f2e-4bd1-9c76-33dae93e5a30","timestamp":"2026-11-17T20:31:05.310Z","tool_use_result":{"stdout":"# Reading the data\n\nThe guide to the reading harness: followed by the analyst; improved by the upgrader (agents repository), run by Optimizer's `optimize` skill, the only one that writes here.\n\nA camera tracks targets (reflectors) fixed on a structure; its own movement is compensated thanks to reference targets, assumed fixed. This movement, the **camera pose** (`pan`, `tilt`, `rotation` in degrees, `scale`, `sigma0` of the registration, in `camera/`), is read before the sensors: it explains a large part of what moves on the curves (D-073). This guide says how to read a station's data: what the curves and the images show, moment by moment. It does not say what they mean: family, known event, hypothesis and verdict are the business of whoever calls you.\n\n## Read first\n\n- `tools/DATA.md`: the files of a station and the meaning of each column, the image quality metrics, the camera images (**first**);\n- `labeling/reading-rules.md`: what the data mean (the measurement chain, gaps, reading rules, false friends).\n\n## The tools\n\nRun them from the root of the calling repository, where `tools/`, `data/` and `labeling/` are links. They return values, never verdicts: you judge. `--out `: where whoever calls you stores your figures; they give it to you. The method (below) says in which order to run them; each section says what a tool returns and how to read it.\n\n| Tool | The question it answers |\n|---|---|\n| [`inventory.py`](#inventory) | What is there, what is missing: files, contents of each source, images, poses, cadence, sensors, rejections |\n| [`summary.py`](#summary) | The usual level of each sensor, then one column by time step |\n| [`plot.py`](#plot) | The series of chosen sensors and columns, as a PNG |\n| [`overview.py`](#overview) | All the sensors together, against the camera pose: common movement, single sensors, residuals, rigid movement |\n| [`ranges.py`](#ranges) | Dated ranges where each sensor leaves its level, at the native step |\n| [`days.py`](#days) | What comes back from one day to the next: night levels, days superimposed by hour, bounds of each day |\n| [`metrics.py`](#metrics) | The system metrics (temperature, voltage…) against the targets and the pose |\n| [`stations.py`](#stations) | Several stations on the same timeline |\n| [`quality.py`](#quality) | The six image quality metrics against a calm reference; labels; degraded instants no label covers |\n| [`thumbnails.py`](#thumbnails) | Full-resolution thumbnails of the camera images, around sensors or of a zone |\n| [`gif.py`](#gif) | A GIF of the camera images over a range, for a reply to the customer |\n| [`ls … \\| grep`](#whole-image) | The whole camera image at a time |\n\n### inventory\n\n```\npython3 tools/scripts/inventory.py [--start T] [--end T] [--files]\n```\n\nNames and counts, never values. Over the **whole period**:\n- files by type: beyond 5 per type, the count, the first and the last (`--files`: the full list, only to look for a specific file);\n- **what each source contains** over the window: the columns of the export, of the pose, of `quality/` and of `weather/` (the MeteoSwiss weather, hourly; a station without a Swiss position has none), with the number of rows that have a value (\"empty\" otherwise; an export column that not all sensors carry says how many carry it); the names of the system metrics of `metrics/`; the images and the difference images. The \"Export image quality (peak to snr)\" line says whether the six quality metrics are filled (then `quality.py`) or empty;\n- images by runs of equal gaps between two images (within 5 min, over the window if given): one line per change of gap, a hole is dated by its two images;\n- camera poses (count, period, measurement instants without registration), period, cadence, missing measurements, sensors (reference or target, error threshold, rejected measurements, distance from the camera and mm per px of `targets.csv`). When `pattern_type` is empty, a sensor is a reference if it carries `reproj_err` or `inlier` (the \"pattern_type empty for N sensors\" line says so);\n- \"Duplicate readings\": an export (often named after the customer's project) whose readings are already in the others; with 0 different values, it changes nothing to the reading, otherwise the tools keep the one of the last file in name order.\n\nWith `--start`/`--end` (on a batch: those of the batch), a section for the window: the missing steps, dated (for all the sensors, or which ones are missing); by sensor, the rejected measurements, dated (runs of consecutive steps; rejected: `error_value` above the sensor's threshold, **references included**); then the **number of references retained by the compensation** (`inlier` = 1) at each instant and the dated runs where some are not, which ones and why (`r` rejected, `0` discarded by the compensation, `empty`; another mark is the value of `inlier`, e.g. `-1`). When `inlier` is empty over the window, the retained references are read from the filled `reproj_err` (the title says so).\n\nA run that ends the same day writes only the time of its end. Over a month, the output with `--start`/`--end` exceeds what a call displays: read each section through `grep` (`| grep -A40 '^Retained references'`, `| grep '^ PR04 '`).\n\n### summary\n\n```\npython3 tools/scripts/summary.py [--column C] [--stat median|min|max] [--step 1h] [--level period|window] [--sensors A,B] [--start T] [--end T] [--instants T1,T2] [--mark]\n```\n\nThe usual level of each sensor (median, MAD, min, max) over the whole period, or over the `--start`/`--end` window with `--level window` (for a batch: a level change within the batch is not compared with weeks of other measurements); then a table by time step, the sensor header repeated every 24 lines.\n- Columns: `error_value`, `corr_x`, `corr_y`, `relative_x`, `relative_y`, `x`, `y`, `sigma0`, `reproj_err`, `corr_x_mm`, `corr_y_mm` (the `corr` in mm, empty without a sure factor: `tools/DATA.md`, \"The targets\"), and the six image quality metrics `peak`, `flux`, `sharpness`, `fwhm`, `dominance`, `snr` (raw values; against a calm reference, `quality.py`).\n- `--mark`: `*` after the value when a measurement of the step is rejected (`x`, `y`, `error_value` of a rejected measurement stay filled), `o` when one has inlier = 0.\n- `--instants T1,T2`: only the steps that contain these instants (the values of all the sensors at a few chosen times).\n- With `--step` equal to the cadence, `--level window --mark`: the per-instant, per-sensor table of one column, one column per run.\n\n### plot\n\n```\n.venv/bin/python tools/scripts/plot.py [--sensors A,B] [--columns C1,C2] [--start T] [--end T] [--zone T1/T2 ...] [--out D]\n```\n\nA PNG of the series, each `--zone` greyed; prints its path. Columns: those of `summary.py`, quality metrics included (raw values).\n\n### overview\n\n```\n.venv/bin/python tools/scripts/overview.py [--columns x,y,sigma0] [--column error_value] [--step 15min] [--k 5] [--min 5] [--residuals corr_x,corr_y,error_value|no] [--outside T1/T2] [--others] [--rigid BASE [--without A,B] [--follow A,B]] [--table T1/T2|no] [--sensors A,B] [--start T] [--end T] [--out D]\n```\n\nAll the sensors together, each against its median and its MAD over the window.\n\nPNGs:\n- **common**: at the top, if the folder has `camera/`, the **camera pose** (raw values, one point per registration, the line cut at measurement instants without registration); the median across sensors of `x`, `y`, `sigma0`, the dispersion across sensors as a grey band; on the `x`, `y` panels, also **each global reference separately** (one line each) and the **median of the targets alone** (black line); at each step, the number of sensors whose `--column` exceeds its median by more than `--k` MAD. Ticks every 1 to 12 h depending on the window, every n days beyond 20 days.\n- **multiples**: a small chart per sensor, one scale each: a step of a single sensor shows there.\n- **residuals-corr_x**, **-corr_y**, **-error_value** (`--residuals`; `no`: none of these PNGs nor their tables): a small chart per sensor of the column minus the sensor's own level (its median over the window; with `--outside T1/T2`, that of the rest of the window, outside the moment read), one scale each, zero dotted: a deviation of a few hundredths on `corr`, hidden in the parallel bands of `plot.py`, shows there.\n- **residuals-…-others** (`--others`): each sensor minus its own median **and minus the median of the other sensors at the same instant**: what all share (the remainder of the compensation of a common movement) cancels, what is specific remains.\n- **rigid** (`--rigid BASE`): at each measurement, the overall movement of the targets since the instant `BASE` (translation, rotation, scale, estimated by medians: a target that jumps alone does not pull it; `--without A,B` removes targets from it) and, for each sensor, the **residual** `dx`, `dy` (raw position minus its position at `BASE` carried by this movement, in px). Panels: `dx`, `dy` of each global reference against the median and the 10th-90th percentile of the targets, `|residual|` of the targets (median, 90th percentile), fitted rotation and scale, `reproj_err` of the references; a rejected reference is a cross (the scale is that of the accepted measurements, a far cross is out of frame).\n\nPrinted:\n- the **common median table**, one line per `--step`: the time, the deviation from the window median of `x`, `y`, `sigma0`, then `x_targets`, `y_targets` (median of the targets alone), then the raw camera pose `cam_pan`, `cam_tilt`, `cam_rotation`, `cam_scale`, `cam_sigma0` (empty without registration); the minimum and the maximum of each column with their instant; then those of `x`, `y` of each global reference (`(rejected)` when the measurement is, with the reference's number of rejected measurements); the measurement instants without pose (dated runs); the instants where at least `--min` sensors exceed together, with their names (`--min 1`: also a single sensor that leaves its level, absent from the default list of 5 sensors);\n- `--residuals`: per sensor, the level, the own noise (median of the differences between two measurements), the min/max deviation per step with their instant, in units and in noises;\n- `--others`: per sensor, the slope and the correlation r of the residual on the common median of `x`, `y`, `sigma0`;\n- `--rigid`: the table by step (`rot_deg`, `scale`, `tx`, `ty`, `tgt_med`, `tgt_max`, `dx`, `dy` of each reference and of each sensor of `--follow A,B`: the step-by-step sequence of a target) and, per sensor, min, max and value at the last instant of `dx`, `dy`. Rejected measurements enter neither the fit, nor the band of the targets, `tgt_med`, `tgt_max`, nor the columns of the table (over several days, parked cars or night rejections no longer drown the rest); the per-sensor summary gives them separately (`; N rejected: min …, max …`, and `(rejected)` after a last value that is rejected).\n\nThe tables by step (common median, `--rigid`) repeat their header every 24 lines; `--table T1/T2` prints them only between T1 and T2 (`no`: not at all), levels, min, max, PNGs and the rest remaining over the whole window: over a one-month batch, first `--table no`, then `--table` on the day of a moment (same levels, which a shorter `--start`/`--end` window would not give). The default step is 15 min, the cadence of the measurements: a one-hour step flattens a peak of one to four steps, dates to the hour and erases an agitation of `x`, `y`; do not widen it to read a batch.\n\nReading, in this order:\n1. **The camera pose first** (top panels, `cam_` columns), dated at the native step: when it rotates (`pan`, `tilt`, `rotation`), changes scale, when its registration degrades (`sigma0`) or is absent (line cut, instants without pose). Each moment of the sensors is read against it: during a movement or a registration gap, or camera still.\n2. **Who moves in the image.** The pose is computed from the global references: a change of pose (or a rise of `sigma0`) is a camera movement only if **the targets also move in the image** (on the `x`, `y` panels, the lines of the references against the black line of the targets alone; `x_targets`, `y_targets`). Only references move, targets still: these references moved, and the pose and the `corr` of all the targets are skewed without raw movement of the targets; say which references and by how much. References and targets together: the camera or the scene; then look whether the `corr` come back.\n3. **Rotation or scale: `--rigid`.** Then the deviation from the median no longer says who moves alone (each sensor deviates according to its place in the image; the rigid residual does not). Before writing \"everything moves together\", rerun with `--rigid BASE`, `BASE` a calm instant before the first movement: a reference whose residual stays far from the 10th-90th percentile of the targets, or a `reproj_err` of the references that does not come back, means the compensation remains skewed by these references and the steps of `corr` partly come from it (say which, by how much, until when); a rising `|residual|` of the targets says they do not move as a block.\n4. **Then `x`, `y`, `sigma0`, before `corr`**: the median of `x`, `y` (raw position, references included), the references one by one, the targets alone and `sigma0` say what moves in the image. Date the start, the end, the return of a movement, or a level that does not come back, on the printed table (time, value), not on the PNG axis. A dip of `corr` after a movement of the raw median is the remainder of the compensation, not a movement of these sensors. The multiples of `error_value` show a lasting step of a sensor, the count the instants where many rise together.\n5. **The residuals, on every batch, without waiting for a suspicion**: a single sensor that rises or falls, a `corr` that drifts by a few hundredths, a step specific to one sensor under a common movement show there; the table says by how much (in noises) and when. On a target whose `corr` goes down under a strong common movement, `--others` separates a remainder of the compensation from a movement of its own: a dip that remains is not a remainder shared by all; a high slope with r close to ±1 on common `y` says it is proportional to the common movement (gain specific to the sensor); without r or slope, it is independent of the movement.\n\n### ranges\n\n```\npython3 tools/scripts/ranges.py [--columns error_value,corr_x,corr_y] [--k 5] [--merge 1h] [--min-measurements 1] [--outside T1/T2] [--rolling N|DURATION] [--instants N] [--sensors A,B] [--start T] [--end T]\n```\n\nDates the start and the end of a sensor's moment without rerunning ten tables. By column and by sensor, at the measurements (native step, never averaged): level (median of the window), own noise, **largest jump** from one measurement to the next (value, in noises, the two instants; `(rejected: …)` when one end is); then the **ranges** where the sensor deviates from its level by more than `--k` noises: start, end, number of measurements, extreme (signed, in units and in noises) and its instant. Two ranges of the same sign less than `--merge` apart make one; rejected measurements do not cut a range; column `rejected`: how many of the range's measurements are (and `rejected extreme`). A range that touches the edge of the window is dated at the edge.\n- `--outside T1/T2`: level and noise computed outside an episode that skews the window median (the sensor spends half the batch there). Rerun with it around a long episode to date its return to the level: do not conclude \"does not come back\" without having read it.\n- `--min-measurements N`: only the ranges of at least N measurements (and how many out of the total). Over several days, the one-step ranges number in the hundreds and drown the long steps: first `--min-measurements 6`, then without.\n- `--rolling N` (N measurements on each side) or `--rolling 1d` (the measurements within a duration): the level of each measurement is the median of its neighbours, without it; a long drift or a step follows this local level, only the deviations shorter than the window remain (the level column and the noise do not change; with `--outside`, only the noise is computed outside the episode).\n- `--instants N`: at the end, the instants where at least N sensors are out of level on one of the columns, with each sensor and its signed deviation in noises (`cx` corr_x, `cy` corr_y, `ev` error_value), the sensors rejected at that instant (among `--sensors`: removing the always-rejected sensors lightens the list), and each reference: `error_value` (`r` if rejected) / inlier.\n- When the batch has a long drift or several steps (the ranges number in the hundreds, or one half of the batch is \"out of level\"), rerun with `--rolling` (a few measurements, or a few hours to a day depending on the cadence) and `--instants 2`: the brief deviations under the drift come out alone, and the list per instant says which sensors deviate together, which are rejected and what the references do; a deviation of all the targets with the references at the same instant is read against the camera pose.\n\nA noise of `0` (and \"-\" in noises, no range): the values are constant to rounding (deviations below 1e-9), like the `corr` of the references when the compensation retains only two (see Conventions); the same in `overview.py --residuals` and `days.py`.\n\n### days\n\n```\n.venv/bin/python tools/scripts/days.py [--columns corr_x,corr_y,error_value] [--night 20-3] [--k 5] [--days 2] [--step 15min] [--sensors A,B] [--bounds [--smoothing N] [--fraction F]] [--start T] [--end T] [--out D]\n```\n\nWhat comes back from one day to the next, on accepted measurements only. A night: the hours `--night` H1-H2 UTC, straddling midnight, dated from the day it starts; choose hours where the day cycle (`error_value`, camera pose) has subsided (**byhour** figure).\n\n1. **Level of each night**, by sensor and by column: median, MAD, number of measurements, own noise; from one night to the next, the **step** (difference of the medians, in units and in noises) and **where it falls** (\"between A and B\": where the night measurements of the two nights split best between the two levels; B at the start of the following night: the cut falls by day). Read it for any sensor that has already made a step or for which `--outside` is not enough (several levels in the batch): a step of a few noises is dated by its \"between A and B\", a step of `error_value` and one of `corr` at the same instant are linked, a slow drift reads from one night to the next.\n2. **Superimposed days**: PNG **byhour-**, a small chart per sensor, hour of the day on the x axis, one curve per day, each measurement minus the level of the last night started (night greyed, frame from the 1st to the 99th percentile, the title says how many measurements fall outside it). Table: per `--step` slot of the hour of the day, the sensors whose deviation exceeds `--k` noises on the same side at least `--days` days, with the number of days and the median of these deviations. What comes back every day at the same hour, on one or several sensors, groups there, even when it lasts one to three measurements: one moment per hour of the day (say which sensors, how many days out of how many, the amplitude, what the camera pose does at that hour), not one moment per day, nor nothing because each step is short.\n3. **Bounds of each day** (`--bounds`), for what comes back every day and is labelled day by day (thermal cycle, warming and cooling), rather than fixing the same hours for all the days: for the median of the targets of each column (with `--sensors`, the median of these sensors; with one, its own) and for the camera pose (`pan`, `tilt`, `rotation`, `scale`, `sigma0`, if `camera/` exists), the deviation from the level of the night that precedes each day (a day goes from the end of one night to the end of the next). Per day: number of measurements, the first and the last; first and last instant beyond `--k` noises, with the measurement just before and just after, at the native step; signed max and min with their instant; the sequence of measurements beyond `--k` noises around the larger of the two; the following night minus the reference night. A day without measurement says so; a reference night that is not the previous one is named. Each day line starts with the short name of its series (`corr_x`, `pose_tilt`…): `| grep '^pose_tilt '` reads one, `| grep ' 12/10 '` one day. PNG **bounds**: the deviation over the batch, first → last exceedance light grey, sequence around the extreme dark grey, max and min marked.\n - `--smoothing N`: the deviation of each measurement is the median of the N measurements of the day centred on it (noise and `--k` unchanged; PNG: smoothed in blue, raw in grey): an isolated point no longer cuts the sequence around the extreme nor makes a first or a last exceedance.\n - `--fraction F`: the threshold of each day is F times its largest |deviation| (printed on its line, `threshold …`), instead of `--k` noises: when the noise at the native step is unrelated to the amplitude of the cycle (very noisy or very smooth pose).\n - Reading: the sequence around the extreme dates the cycle, the max and the min a go and a return (morning and afternoon); \"before\" and \"after\" give the bounds at the native step (at a cadence of 1 h or 4 h, an event goes from the measurement before to the one after). First exceedance at the start of the day (\"before -\") and last at its end every day: the night is not calm; change `--night`, or `--sensors` the targets that carry the cycle. Camera drifting all night: a short night just before the morning (`--night 3-5`: the level of the rest that precedes the start). Noisy series or isolated points: `--smoothing 5`. Threshold in noises that does not bite (never exceeded, or exceeded all day): `--fraction 0.3`, then read the sequence around the extreme, not the first and the last exceedance. A \"1 measurements\" line is a peak, not a cycle.\n\n### metrics\n\n```\n.venv/bin/python tools/scripts/metrics.py [--names A,B] [--step 1h] [--stat median|min|max] [--against temperature] [--smoothing 24h] [--metrics-only] [--start T] [--end T] [--out D]\n```\n\nThe system metrics of `metrics/` (one value per hour), never the identifiers (`SIM_CCID`, `ip*`):\n- the available metrics with their number of values over the window (\"empty\": none; all empty is an absent datum, not a stable temperature);\n- a table per `--step`: `temperature` (median of the `sensor_*_deg_c` components, the one the detectors read), each metric of `--names` (default: the `*_deg_c` and `BusVoltage`), then, unless `--metrics-only`, `tgt_corr_x`, `tgt_corr_y` (median over the targets of `corr` minus each target's own level, accepted measurements) and the raw camera pose (`cam_pan` … `cam_sigma0`); an empty cell is skipped, a text metric (`link`, `BatteryState`, `last_sync`) is returned as it is. `--step 1d --stat min` (or `max`): the minimum or the maximum of each day;\n- per column: filled steps, min and max with their instant; the correlation r and the slope of each column on `--against` (with `--smoothing 24h`, on its rolling mean, column `_smooth`: for a station where the temperature varies little and fast, indoors); the dated runs of steps without any metric;\n- a PNG: temperatures on one panel (median in black), each other metric on its own, then `tgt_corr_x`, `tgt_corr_y` and the pose, line cut on a gap.\n\nAn r does not say a cause: say it as a value, with the window where it is computed.\n\n### stations\n\n```\n.venv/bin/python tools/scripts/stations.py [...] [--columns temperature,cam_tilt,cam_rotation,cam_scale,tgt_corr_x,tgt_corr_y] [--step 1h] [--stat median|min|max] [--table T1/T2|no] [--start T] [--end T] [--out D]\n```\n\n**Several stations on the same timeline** (neighbouring stations, same building). Columns: `temperature` (as in `metrics.py`), `cam_pan` … `cam_sigma0` (raw pose), `tgt_corr_x`, `tgt_corr_y` (as in `metrics.py`), `rej_targets`, `rej_refs` (number of rejected targets, of rejected references, the largest of the step).\n- Prints per station the period, the cadence and the number of instants; the **gaps**: the runs of steps without measurement or without temperature, with the stations where they are missing (a gap common to several stations on a single line); the table by step (one `STATION:column` column each, tabs; `--table` as in `overview.py`); per column and per pair of stations, r of the values and r of the steps from one value to the next (a common movement shows on the steps, a common trend on the values), with n.\n- PNG **stations**: a panel per column, a line per station (raw temperature, the rest minus its median), and a band per station of the steps without measurement.\n- Take `--step` equal to the slowest cadence of the stations; over a month at `1h`, first `--table no`.\n\n### quality\n\n```\npython3 tools/scripts/quality.py [--calm T1/T2,T3/T4] [--common] [--table M] [--step 15min] [--threshold 0.5] [--sensors A,B] [--start T] [--end T]\n... --labels F [--numbers 3,7] [--margin 60] [--edges]\n... --labels F --outside [--min 1] [--except \"Thermal displacement\"]\n.venv/bin/python tools/scripts/quality.py --figure [--metrics flux,snr,dominance] [--labels F] [--zone T1/T2 ...] [--out D]\npython3 tools/scripts/quality.py --self-test\n```\n\nThe six **image quality metrics** (`peak`, `flux`, `sharpness`, `fwhm`, `dominance`, `snr`; definitions: `tools/DATA.md`), on the stations that have them (otherwise: \"No quality metrics\", and nothing else). Each measurement becomes a **ratio** to the **calm reference** of its sensor: the median of the metric over its measurements in the `--calm` windows, at the same UTC hour of the day (without `--calm`: the whole folder); 1 = like the reference, < 1 lower, > 1 higher; for `fwhm` and `dominance`, the rise says a degraded image; rejected measurements included.\n- Without options: the folder's maximal `peak`, then per sensor (`r` = reference) the rejected measurements, `pk/max` (median peak over the window divided by this maximum: at 1, the spot touches the image ceiling, its `peak` no longer moves and its `sharpness` follows the exposure: read `flux`, `snr` instead), and for each metric the median ratio and the extreme with its instant; then the median of the targets and of the references.\n- `--common`: per step, the median of the ratios of the targets / of the references for each metric (what affects the whole scene, visibility or turbulence; `--step 1d` shows on one screen on which days the reference holds).\n- `--table M`: per step, the ratio of `M` of each sensor (`*`: a rejected measurement), their median and how many pass `--threshold` (below, or above 1/`--threshold` for `fwhm`, `dominance`): a target that goes out and comes back; on a moment, `--table flux --sensors …` says which targets are hidden (flux cut) or veiled, from which instant to which instant: write them by their name.\n- `--labels F` (one JSON per line, `start`, `end`, `family`): per numbered label, the median ratio of the targets and of the references over the hour before, the range and the hour after (`tgt 0.96|0.26|0.79`, `--margin` minutes), then the sensors **affected** over the range (flux or snr below `--threshold`, or dominance above 1/`--threshold`), with their worst flux, from lowest to highest. `--edges`: per instant of the widened range, the number of affected sensors and the median of the targets of flux, snr, dominance (`<` within the range), to date the first and the last degraded instant.\n- `--outside`: the runs of instants that no label covers (outside `--except` families) where at least `--min` sensors are affected, with the sensors and their worst flux: candidates for forgotten labels, to check on `corr_x`, `corr_y`.\n- `--figure` (instead of the tables): PNG **quality-common** (a panel per metric, log scale: median of the targets in black, of the references in red, grey band from the 10th to the 90th percentile of the targets: a disturbance of the whole scene moves the median, an occultation of a few targets only the bottom of the band) and a PNG **quality-** per `--metrics` (a small chart per sensor, references in red); `--labels` greys each label in one colour per family, `--zone` ranges.\n\nReading: the metrics say **why** a measurement degrades, where `error_value` says only that it degrades; they prove a cause and name the affected targets. What they showed on LENZSPITZE (to be confirmed on each station): `flux` cut (close to 0) on a group of targets, the others intact, for one to a few measurements: these targets are hidden (the list is read on the flux each time, not on the usual list; a hidden target can stay under its error threshold, and its point is wrong); `flux` down over the whole scene, stronger on the distant targets: reduced visibility; `sharpness` down and `dominance` up, `flux` whole: the image shakes (turbulence); nothing moves: neither the image nor the view, to be looked for in the movement. A whole flux refutes an occultation. `fwhm`, truncated to the disc, moves little; on a spot at the ceiling (`pk/max` at 1), it goes down when the spot darkens.\n\n**The calm reference decides everything**: take `--calm` on calm hours of the **same image regime** as the range read. When the lighting or the exposure changes (after a gap, an intervention), a reference on the other side skews the ratios by a factor of two or three: `--common --step 1d` over the batch shows this change (medians of the targets and of the references far from 1 for whole days, then at 1); then take a reference on each side and read each side with its own. Calm days are often days of thermal cycle: a reading of the thermal against them is circular.\n\n### thumbnails\n\n```\n.venv/bin/python tools/scripts/thumbnails.py --sensors A,B --times T1,T2 [--radius 100] [--contrast [MIN,","stderr":"","interrupted":false,"isImage":false,"noOutputExpected":false,"persistedOutputPath":"/home/maxime/.claude/projects/-home-maxime-aimsight-app/4d470fcf-4228-4dc5-8c0d-b90f8d37cbb1/tool-results/bejht3h5f.txt","persistedOutputSize":71663},"tool_result_meta":[{"id":"toolu_01R2BCrcWoSiSdDurZJFrVcm","permission_decision":{"decision":"accept","source":"config","reason_type":"rule"}}]}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98msoa6AmhQwoppdAXa","type":"message","role":"assistant","content":[{"type":"tool_use","id":"toolu_01BxKZMSu2dUbZgguqqEx3fV","name":"Bash","input":{"command":"cd /home/maxime/aimsight-app; cat labeling/families.md labeling/reading-rules.md labeling/stations.md","description":"Read families, reading rules, stations"},"caller":{"type":"direct"}}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":2089,"cache_read_input_tokens":9875,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":2089},"output_tokens":41,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"4d470fcf-4228-4dc5-8c0d-b90f8d37cbb1","uuid":"a76404f1-d58f-4ccf-bab4-ad2dd7d08057","timestamp":"2026-11-17T20:31:05.891Z","request_id":"req_011Ch98msd9qgrTSbWA8QFUq","wire_tool_inputs":{"toolu_01BxKZMSu2dUbZgguqqEx3fV":{"command":"cd /home/maxime/aimsight-app; cat labeling/families.md labeling/reading-rules.md labeling/stations.md","description":"Read families, reading rules, stations"}}}
-{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_01BxKZMSu2dUbZgguqqEx3fV","type":"tool_result","content":"\nOutput too large (30.5KB). Full output saved to: /home/maxime/.claude/projects/-home-maxime-aimsight-app/4d470fcf-4228-4dc5-8c0d-b90f8d37cbb1/tool-results/ba8xg18ey.txt\n\nPreview (first 2KB):\n# The label families\n\nOne 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.\n\n| Key | Detector | What happens | For the client |\n|---|---|---|---|\n| `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 |\n| `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 |\n| `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 |\n| `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 |\n...\n","is_error":false}]},"parent_tool_use_id":null,"session_id":"4d470fcf-4228-4dc5-8c0d-b90f8d37cbb1","uuid":"ae88b1e4-3238-4788-9724-51a9cce7b853","timestamp":"2026-11-17T20:31:05.935Z","tool_use_result":{"stdout":"# The label families\n\nOne 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.\n\n| Key | Detector | What happens | For the client |\n|---|---|---|---|\n| `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 |\n| `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 |\n| `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 |\n| `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 |\n| `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 |\n| `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 |\n\nFor 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:\n\n| Variety | For the client |\n|---|---|\n| `Poor visibility reduced` | use the data over the range with care: they are less precise |\n| `Heat shimmer` | nothing to do: the small fast wiggles are not movement |\n| `Camera thermal movement` | nothing to do: this is not a movement of the structure |\n| `Brief obstruction` | ignore this single point on the curves |\n| `Sudden jump, back to normal` | look at the images: the cause is not established |\n| `Lasting shift` | check whether the structure moved: look at the images |\n| `Jump, not back yet` | check whether the structure moved: look at the images |\n| `Slow drift` | keep watching it |\n\n## The boundaries\n\n- **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.\n- **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.\n- **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 Displacement without a cause. The description says it is a reference, and that the targets move together because of it.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **Target issue or Displacement**: a changed configuration (moved sensors, changed starting position, setting) is Target issue; the jump that results is not a Displacement.\n\n## The phenomena\n\nWhat has been labelled so far, one line each: **name**: what is seen; how to tell it from its neighbours. The hypotheses to weigh for a moment of a range; the cases, their bounds and descriptions come from the labels, through `precedents.py`. A phenomenon not in this list is labelled too, without forcing a cause.\n\n### No data\n- **A gap common to several stations**: the measurements missing at the same minutes on every station measuring then; a cause outside the stations, not established. Read the other stations before the station's metrics.\n- **The station runs, the measurement is missing**: one station, powered and communicating (synchronization, image or `DB_not_uploaded` at the missing instant), misses a measurement.\n- **The station goes silent on its own, for a long time**: no measurements, no images, no metrics, for hours or days, without the signature of a lack of energy.\n- **The station shuts down for lack of energy**: the battery does not last the night; voltage below the knee before the gap, a restart with the solar charge.\n- **Mains cut: the station runs on its battery**: a station on mains stops, or comes back on a drawn-down battery, until the mains return.\n\n### Obstruction\n- **A pass-by hides the targets for the length of one measurement**: a train, a vehicle, passers-by: the hidden targets rejected for one acquisition, back at the next; a reference behind it makes the whole base jump. Insects give the same signature: only the image tells.\n- **A target left under the threshold latches onto a headlight, a reflection or another spot**: during a pass-by, one false point kept in the curve, without rejection; `dominance` rises on a recent camera.\n- **A vehicle or machine that stays in front of the targets**: the same sensors hidden for hours or days, sometimes a reference; one label per parking.\n- **An animal very close to the lens**: lit at night, it hides part or all of the scene for one or two measurements; a spider is not its web.\n- **A plant shaken by the wind in front of a target**: one target, at times, on windy days; it grows over weeks.\n- **An obstacle covers part of the spot**: an obstacle, or a mark on the glass in front of one spot, hides part of it for hours or weeks: the measured centre slides; the sliding is the artifact, the jump back is the return to normal.\n\n### Visibility\n- **Rain**: drops in front of the lens veil the spots during the hours of rain, at night above all; the references, higher up, may suffer less.\n- **The soiled glass**: after rain, drop marks veil part of the scene durably; under a single spot, it is an obstacle (Obstruction).\n- **Visibility drops over the whole scene, without an obstacle**: fog, condensation, a milky dawn: flux down on all sensors, `error_value` up, rejections; raw positions without a step.\n- **Part of the scene goes dark at night**: the distant spots, or a few neighbours at the edge of the group, lose their light, nothing in front.\n- **A reference loses its brightness, without an obstacle**: one or two references weaken and shrink, most often at night, then come back on their own; the centre does not move.\n- **Atmospheric turbulence**: by day, air heated above a road, ballast or rails makes the spots tremble: a fast noise, `error_value` up. Without the `error_value` rising, an agitation of the pose is the camera heating (Thermal displacement).\n- **The sun in the field or behind a spot**: the sun enters the field, or lights the background of a target or a reference as bright as it: rejections at the same hours on sunny days only.\n- **A faint spot lost when the light is missing**: a faint target crosses its threshold at the change from night to day, under an overcast sky or in a noisy night image; its rejections come with the light, not every day (else Target issue).\n\n### Target issue\n- **A target rejected at all its measurements**: never accepted, whatever the weather.\n- **A target right at the threshold, the whole batch**: its `error_value` keeps crossing the threshold, with many own rejections.\n- **A target rejected every night or every day**: under the station's ordinary regime (floodlight, daylight), at the same hours, whatever the weather.\n- **A target that degrades, and sometimes recovers**: seen worse and worse from a date on; back only after weeks, if ever, often at another level.\n- **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.\n\n### Thermal displacement\n- **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.\n- **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.\n- **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.\n- **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).\n\n### Displacement\n- **A step of the camera that the compensation does not erase**: the camera moves at once and a remainder passes into the curves; a step that leaves nothing beyond the noise is not labelled.\n- **The camera tilts little by little**: over weeks, the tilt rises and the compensation corrects some targets better than others; the targets do not move relative to each other.\n- **The base changes without a reference lost**: all references kept, the distance between them changes a little; all targets shift together without moving in the image.\n- **A real movement of the structure**: targets shift and stay, with references and pose stable and a good image; if the camera and references moved too, the amplitude is not established.\n- **Targets move slowly, alone, then come back**: one or a few targets, hours or days, without a camera movement or an obstructed view.\n- **A target or a small group jumps and stays shifted**: at once, to another level, without the camera moving or a visible cause.\n- **A step taken during a measurement outage**: on resumption, targets do not find their previous level.\n\n### Family of the cause\n- **A reference dropped: the base changes**: one reference above its threshold, dropped: all targets jump together, the reprojection error at zero; the family is that of what hindered the reference.\n- **Two references lost: the camera is blind**: two of three references dropped one after the other: every point of the range is invalid; the family of the cause.\n- **A compensation on two references**: a station built with two, or having lost one for good: the slightest difference between them passes into all the targets; the family of what disturbs them.\n- **A spider web in front of the lens**: Visibility when it veils the image, Obstruction when a thread hides a few spots; no signal at all is possible, only the images show it.\n\n## What is not labeled\n\n- 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.\n- 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.\n- 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).\n- The expert can say so with the key `None` (labeling tool: \"None (curves untouched)\"): such a label is not counted.\n# Reading rules\n\nWhat the data of a station mean: where each cause enters the measurement, what it touches, and the rules and false friends that the expert and the reviewed labels have established. What the files and columns are: `tools/DATA.md`. How to place a label: `labeling-rules.md`; the families and their boundaries: `families.md`, whose rules are not repeated here.\n\nCases are cited by label id (`NORDEND-80`, in `auto/.jsonl`; `precedents.py` finds others); `[expert]`: the expert's word, from a label that is not in `auto/`. Maintained by hand.\n\n## 1. How a measurement is made\n\n1. **The scene**: targets on the structure, references around it, assumed fixed.\n2. **The view**: the air between the camera and the targets, and what can pass or settle in front.\n3. **The image**: the lens, then the capture (IRON, or DIFF which combines several captures).\n4. **The pattern measurement**: each sensor is found in the image: `x`, `y`, `error_value`; on recent cameras, the image quality. Above `error_threshold`, the measurement is rejected.\n5. **The compensation**: a 2D similarity (translation, rotation, scale) fitted on the references (`global_ref`) gives the camera pose (`pan`, `tilt`, `rotation`, `scale`, `sigma0`) and, per reference, `reproj_err` and `inlier`.\n6. **The corrected curve**: `corr_x`, `corr_y`, the position of the target once the estimated camera movement is removed.\n\nA displayed value is the end of this chain: find the stage that gave way.\n\n## 2. Where each cause enters, and what it touches\n\n| Stage | Cause | What it touches | Time | Witnesses |\n|---|---|---|---|---|\n| View (air) | fog, rain, condensation: **reduced visibility** | a homogeneous drop in flux; `error_value` rises, rejections; raw positions without a step | hours | quality (`flux`), images |\n| View (air) | **heat haze** (turbulence) | a fast noise; only when the structure really heats up; not under a bridge | the hot hours | temperature, `error_value` by day versus night |\n| View (obstacle) | object, leaves, snow on a target: **occultation**; a passage | one or a few targets; on a recent camera, their flux cut, the neighbours intact (LENZSPITZE-9); a passage: one measurement | from one measurement to weeks | quality, images |\n| Target | problem target (badly oriented, dirty, glued) | one target, lastingly | days and more | `error_value` of the target alone |\n| Lens | **thermal deformation of the optics** (sun on the station) | the whole image deforms, which a similarity cannot represent | short: follows the sun on the station | housing temperature |\n| Camera and mount | **expansion of the mount**; wind, jolt, shock | raw positions of all sensors, references included, together; the compensation absorbs it (`corr` flat) or badly: `corr` follows the inflections of the camera movement | specific to the mount | camera pose, housing temperature |\n| References | **reference hidden or less well seen** | the transformation is redone without it: points shifted at once, often grouped in one part of the image, the shift growing with the distance to the references; back when it returns: reversible | the time of the nuisance | `error_value`, `reproj_err` of the references, `sigma0`, camera pose |\n| References | a reference moved | the `corr` of the targets shifted lastingly | lasting | `reproj_err` of the reference |\n| Structure | **thermal expansion of the structure** | `corr`, an amplitude specific to each target, references stable | the longest: slow heating, late cooling | no air temperature (section 3) |\n| Structure | real movement | `corr` of one or several targets, which lasts; references and pose stable, good image quality | lasting | all of the above, at calm |\n\n**A jump that returns** to normal is not serious: the return is what makes it benign. Saying \"jump\" is not enough; the question is its cause, quite often a reference hidden or less well seen.\n\n## 3. Thermal effects\n\n- **Three movement effects**: the lens, the mount, the structure, told apart by their heating and cooling times; the structure is the slowest. Heat haze is apart: a noise, not a movement.\n- **The cases cross**: a camera on a bridge has two structures, the one that carries it (the mount) and the one it monitors.\n- **In waves**: expansion, then contraction; often stronger in Y than in X, depending on the orientation.\n- **The kind of structure says whether a thermal movement is possible**: a bridge yes; a rock face, too massive, or a road, no: the movement is then that of the camera (`stations.md`). [expert, WILDSTRUBEL-102]\n- **The camera can move through a thermal effect at a different rhythm from the structure**, not having the same heating time. [expert]\n- **The temperature that counts is that of the camera housing, not that of the air around**, even sheltered. The temperatures available are those of the compute board (`sensor_*_deg_c`), inside the housing, heated by the sun and by the computing, as hourly means: a witness for the lens and the mount, not for the structure nor the air. `temperature_deg_c`, on a few stations: unknown sensor. [expert, BREITHORN-14]\n- **A change of regime is understood through the temperature**: look at it. [expert]\n- **The direction of a thermal movement is read on the housing temperature, not on the hour**; when the scale of the camera follows it, the effect is on the camera. [NORDEND-155, CLARIDEN-13]\n\n## 4. Gaps\n\n- **A gap is not necessarily an outage**: acquisition, transmission, ingestion and display are distinct layers.\n - At the end of a file, empty values can be only a synchronization delay (`last_sync`): a delay only if the other stations do not have their data yet either.\n - At the start of a file, empty values precede the first measurement: not an outage.\n - A gap surrounded by a normal voltage is not an energy problem.\n- **A gap is read with the other stations and the metrics** (the boundary \"A gap\" of `families.md`). [JUNGFRAU-52, NORDEND-50, WILDSTRUBEL-201, CLARIDEN-19]\n- **A power cut leaves a signature**: the voltage below the knee (about 12.8 V) just before or just after the gap; the temperature drops during the gap more than at the same hours on nights without a gap, which alone does not settle it (a common gap can do the same, an outage that comes back after sunrise shows nothing).\n- **A station on mains that comes back with its battery drawn down has lost the mains.**\n- **A `NaN` or `inf` value** in an export is an absence of measurement.\n\n## 5. Reading rules\n\n- **What moves in the image is read before the cause, on the raw positions against the overall movement** (`overview.py --rigid`): the targets do not move relative to each other, it is the camera [BREITHORN-2]; targets move alone, a movement is not excluded [CLARIDEN-14]; nothing moves and the curves jump, it is the base or the configuration [WILDSTRUBEL-136, CLARIDEN-38].\n- **A jump is judged against the neighbours**: if it brings the target back toward them, it is a return to normal, and the artifact was before; if it takes it away from them, it is to be treated quite differently. [expert]\n- **A level is also judged against the past of the target, over weeks**: a jump that brings it back to an old level is a return. [NORDEND-94, NORDEND-169]\n- **A high `error_value` is not a problem in itself: its variations count.** [expert]\n- **A very stable `error_value` says the targets stay well visible**: while they move, it rather suggests a poor compensation than an obstruction of the view. [expert]\n- **A rejected measurement is removed from the display, not a measurement just under the threshold**: a target left under the threshold keeps its jump. [expert, NIEDERHORN-13]\n- **At least three references are needed; dropping a single one is enough to distort everything**: a kind of triangulation. **The position of the targets rests on the network of references**: references badly seen, targets badly anchored. [expert]\n- **The reprojection error says how many references hold**: at zero, only two remain, a very bad sign, not a perfect measurement; absent, only one, and no measurement is possible. Except on a station built with two references, where it is always at zero. [JUNGFRAU-22, FLORIDA-4, expert]\n- **The pose of the camera is reliable only if the references hold**: a reference rejected, dropped or sliding against the targets distorts it; a single hindered target does not. [FLORIDA-58]\n- **A drift specific to a few targets that follows the camera, on the same dates, is the scene deforming with it**, not a second movement; it is separate only if it has its own dates. [NEBRASKA-6, NEBRASKA-5]\n- **Neighbouring cameras are read together**: the same movement, the same loss or the same gap on the cameras of one building have a common cause; what touches only one is on its line of sight. [MICHIGAN-3, BREITHORN-20]\n\n## 6. False friends\n\n- **Jumps of many targets, all in the same direction, are not a movement** when they fall at the reference switches: raw positions without a step, daily cycle that continues. [expert]\n- **A target that slides slowly away from its neighbours is not moving** when its `error_value` rises with the sliding and a step brings it back toward them. [expert]\n- **A rise over several days is not necessarily a real movement**: it may follow a lasting drop in temperature. [expert]\n- **Corrections stuck at zero are not a failure**: a twin of a reference. [expert]\n- **No signal does not mean no obstruction**: only the images show the web. [expert]\n- **A web is not the spider**: the web veils in part for hours or days; the spider hides everything for the length of one measurement. [expert]\n- **References that do not move in the rain do not contradict the rain**: higher up, they suffer it less. [NIEDERHORN-12]\n- **The step of a real movement is not its amplitude** when the camera and the references have moved too. [expert]\n- **A swarm of insects is not a train**: same signature; only the image tells them apart. [NIEDERHORN-66]\n- **In a tunnel, a temperature drop at the same moment does not make a thermal effect**: the bump of a group comes with the `error_value` and returns before the scale of the camera. [CLARIDEN-12, CLARIDEN-13]\n- **The return of the `error_value` is not the end of an obstruction**: after a mark on the glass, the curves stay shifted. [NORDEND-169]\n- **A spot on a thumbnail that follows the measurement is not necessarily there**: the frame follows a measurement perhaps latched onto the neighbour; only a fixed frame shows it. [FLORIDA-43]\n\n## 7. Non-negotiable rules\n\n- Judge nothing on a binary `inlier`: use continuous weights, residuals, influence.\n- Neither `sigma0` alone nor the number of references is ever a sufficient criterion.\n- The image quality of a target is not the quality of the reference network; a small residual is not a well-constrained transformation.\n- A common-mode movement is not a structural movement; coherent references are not physically fixed references: the camera cannot prove that a network moving as a block is fixed.\n\n## 8. Lessons from cases outside the labels\n\n- **When everything moves together, the measurements alone do not separate the structure from the camera** (Barcelona, a bridge whose vault subsided: the references, the camera and the structure moved; the expert called it a real movement, confirmed by other monitoring systems of the site). An unstable compensation then distorts the amplitude of a real movement: the movement is reported, its amplitude is not established. [expert]\n- **Two prisms too close interfere**: a 24 h cycle correlated between the two, or isolated peaks on one target at a time, too large for the structure, with no obstruction on the images; a neighbour much brighter than the others. On a recent camera, `dominance` shows it. [client report]\n- **Vegetation grows over days and weeks**: a partial, progressive occultation, not reversible from one measurement to the next like a passage; the hardest obstruction according to the expert. [client report]\n- **References masked (two of four, by vegetation)**: a 24 h cycle on pan, roll and tilt, badly compensated, is then not a movement of the camera but a base too weak for the transformation. [client report]\n- **A target of low contrast**: by day, square waves on one axis, back at night, `error_value` rising by day without reaching the threshold. [client report]\n- **Snow**: noise and apparent movements on all sensors and the camera, a brief loss of data, the signal quickly back. [client report]\n# The stations\n\nWhat each station is: its structure, its camera, its references, its neighbours. Context for reading a station's data, not a rule: what happens at a station is in its labels (`auto/.jsonl`, `precedents.py`). The kind of structure says whether a thermal movement of the structure is possible (`reading-rules.md`, section 3). Cases are cited by label id; `[expert]`: the expert's word. Maintained by hand: a new station gets its row when its first range is analysed.\n\n| Station | Structure | Camera | References | Neighbouring cameras |\n|---|---|---|---|---|\n| BREITHORN | in a building (a factory, indoors) [expert] | one measurement every four hours; COLJ19 and POUI19 much closer to the camera than the other targets [expert]; the camera nods forward over October, compensation incomplete [expert] | REFH22, REFPOU22 among the sensors at the bottom of the image | MICHIGAN and NEBRASKA, in the same building: a drift common to the three [BREITHORN-2] |\n| CLARIDEN | a tunnel under construction, with other measurement systems [expert] | images always dark; on mains | four references, D-302-C, PR-291, PR-293, PR-295; PR-284 is a local reference, read as a target; D-302-B and PR_BG on the same prism [CLARIDEN-38] | — |\n| FLORIDA | — | — | two references only, p1_r and r1_r, each with its twin target (Sellette 3, Pont Ernen) [expert] | its one-measurement gaps at night fall at the same instants as SNCF01's |\n| JUNGFRAU | a bridge, which rises as it cools [expert] | under the deck, fixed to the bridge | three references off the bridge, REF_D, REF_G, REF_CT | — |\n| LENZSPITZE | a railway seen from under a bridge, a work site and machines next to it | recent camera, with image quality; `x`, `y` relative in the export (`tools/DATA.md`); only `temperature_deg_c` is filled | nine references, i","stderr":"","interrupted":false,"isImage":false,"noOutputExpected":false,"persistedOutputPath":"/home/maxime/.claude/projects/-home-maxime-aimsight-app/4d470fcf-4228-4dc5-8c0d-b90f8d37cbb1/tool-results/ba8xg18ey.txt","persistedOutputSize":31201},"tool_result_meta":[{"id":"toolu_01BxKZMSu2dUbZgguqqEx3fV","permission_decision":{"decision":"accept","source":"config","reason_type":"rule"}}]}
-{"type":"assistant","message":{"model":"claude-opus-5-5","id":"msg_011Ch98nASC82gJfTkpisbfL","type":"message","role":"assistant","content":[{"type":"tool_use","id":"toolu_01LDmMbNhyNGFHDEFvb1PkCZ","name":"Read","input":{"file_path":"/home/maxime/.claude/projects/-home-maxime-aimsight-app/4d470fcf-4228-4dc5-8c0d-b90f8d37cbb1/tool-results/bejht3h5f.txt","allow_large":true},"caller":{"type":"direct"}}],"container":null,"stop_reason":null,"stop_sequence":null,"stop_details":null,"usage":{"input_tokens":2,"cache_creation_input_tokens":1940,"cache_read_input_tokens":11964,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":1940},"output_tokens":16,"service_tier":"standard","inference_geo":"global","speed":"standard"},"input_transformations":[],"diagnostics":null,"context_management":null},"parent_tool_use_id":null,"session_id":"4d470fcf-4228-4dc5-8c0d-b90f8d37cbb1","uuid":"e0c3b7dd-a82d-4232-b049-8f7935afa3ab","timestamp":"2026-11-17T20:31:08.544Z","request_id":"req_011Ch98nAEJE7TfLQhwAVyEw","wire_tool_inputs":{"toolu_01LDmMbNhyNGFHDEFvb1PkCZ":{"file_path":"/home/maxime/.claude/projects/-home-maxime-aimsight-app/4d470fcf-4228-4dc5-8c0d-b90f8d37cbb1/tool-results/bejht3h5f.txt","allow_large":true}}}
-{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_01LDmMbNhyNGFHDEFvb1PkCZ","type":"tool_result","content":"1\t# Reading the data\n2\t\n3\tThe guide to the reading harness: followed by the analyst; improved by the upgrader (agents repository), run by Optimizer's `optimize` skill, the only one that writes here.\n4\t\n5\tA camera tracks targets (reflectors) fixed on a structure; its own movement is compensated thanks to reference targets, assumed fixed. This movement, the **camera pose** (`pan`, `tilt`, `rotation` in degrees, `scale`, `sigma0` of the registration, in `camera/`), is read before the sensors: it explains a large part of what moves on the curves (D-073). This guide says how to read a station's data: what the curves and the images show, moment by moment. It does not say what they mean: family, known event, hypothesis and verdict are the business of whoever calls you.\n6\t\n7\t## Read first\n8\t\n9\t- `tools/DATA.md`: the files of a station and the meaning of each column, the image quality metrics, the camera images (**first**);\n10\t- `labeling/reading-rules.md`: what the data mean (the measurement chain, gaps, reading rules, false friends).\n11\t\n12\t## The tools\n13\t\n14\tRun them from the root of the calling repository, where `tools/`, `data/` and `labeling/` are links. They return values, never verdicts: you judge. `--out `: where whoever calls you stores your figures; they give it to you. The method (below) says in which order to run them; each section says what a tool returns and how to read it.\n15\t\n16\t| Tool | The question it answers |\n17\t|---|---|\n18\t| [`inventory.py`](#inventory) | What is there, what is missing: files, contents of each source, images, poses, cadence, sensors, rejections |\n19\t| [`summary.py`](#summary) | The usual level of each sensor, then one column by time step |\n20\t| [`plot.py`](#plot) | The series of chosen sensors and columns, as a PNG |\n21\t| [`overview.py`](#overview) | All the sensors together, against the camera pose: common movement, single sensors, residuals, rigid movement |\n22\t| [`ranges.py`](#ranges) | Dated ranges where each sensor leaves its level, at the native step |\n23\t| [`days.py`](#days) | What comes back from one day to the next: night levels, days superimposed by hour, bounds of each day |\n24\t| [`metrics.py`](#metrics) | The system metrics (temperature, voltage…) against the targets and the pose |\n25\t| [`stations.py`](#stations) | Several stations on the same timeline |\n26\t| [`quality.py`](#quality) | The six image quality metrics against a calm reference; labels; degraded instants no label covers |\n27\t| [`thumbnails.py`](#thumbnails) | Full-resolution thumbnails of the camera images, around sensors or of a zone |\n28\t| [`gif.py`](#gif) | A GIF of the camera images over a range, for a reply to the customer |\n29\t| [`ls … \\| grep`](#whole-image) | The whole camera image at a time |\n30\t\n31\t### inventory\n32\t\n33\t```\n34\tpython3 tools/scripts/inventory.py [--start T] [--end T] [--files]\n35\t```\n36\t\n37\tNames and counts, never values. Over the **whole period**:\n38\t- files by type: beyond 5 per type, the count, the first and the last (`--files`: the full list, only to look for a specific file);\n39\t- **what each source contains** over the window: the columns of the export, of the pose, of `quality/` and of `weather/` (the MeteoSwiss weather, hourly; a station without a Swiss position has none), with the number of rows that have a value (\"empty\" otherwise; an export column that not all sensors carry says how many carry it); the names of the system metrics of `metrics/`; the images and the difference images. The \"Export image quality (peak to snr)\" line says whether the six quality metrics are filled (then `quality.py`) or empty;\n40\t- images by runs of equal gaps between two images (within 5 min, over the window if given): one line per change of gap, a hole is dated by its two images;\n41\t- camera poses (count, period, measurement instants without registration), period, cadence, missing measurements, sensors (reference or target, error threshold, rejected measurements, distance from the camera and mm per px of `targets.csv`). When `pattern_type` is empty, a sensor is a reference if it carries `reproj_err` or `inlier` (the \"pattern_type empty for N sensors\" line says so);\n42\t- \"Duplicate readings\": an export (often named after the customer's project) whose readings are already in the others; with 0 different values, it changes nothing to the reading, otherwise the tools keep the one of the last file in name order.\n43\t\n44\tWith `--start`/`--end` (on a batch: those of the batch), a section for the window: the missing steps, dated (for all the sensors, or which ones are missing); by sensor, the rejected measurements, dated (runs of consecutive steps; rejected: `error_value` above the sensor's threshold, **references included**); then the **number of references retained by the compensation** (`inlier` = 1) at each instant and the dated runs where some are not, which ones and why (`r` rejected, `0` discarded by the compensation, `empty`; another mark is the value of `inlier`, e.g. `-1`). When `inlier` is empty over the window, the retained references are read from the filled `reproj_err` (the title says so).\n45\t\n46\tA run that ends the same day writes only the time of its end. Over a month, the output with `--start`/`--end` exceeds what a call displays: read each section through `grep` (`| grep -A40 '^Retained references'`, `| grep '^ PR04 '`).\n47\t\n48\t### summary\n49\t\n50\t```\n51\tpython3 tools/scripts/summary.py [--column C] [--stat median|min|max] [--step 1h] [--level period|window] [--sensors A,B] [--start T] [--end T] [--instants T1,T2] [--mark]\n52\t```\n53\t\n54\tThe usual level of each sensor (median, MAD, min, max) over the whole period, or over the `--start`/`--end` window with `--level window` (for a batch: a level change within the batch is not compared with weeks of other measurements); then a table by time step, the sensor header repeated every 24 lines.\n55\t- Columns: `error_value`, `corr_x`, `corr_y`, `relative_x`, `relative_y`, `x`, `y`, `sigma0`, `reproj_err`, `corr_x_mm`, `corr_y_mm` (the `corr` in mm, empty without a sure factor: `tools/DATA.md`, \"The targets\"), and the six image quality metrics `peak`, `flux`, `sharpness`, `fwhm`, `dominance`, `snr` (raw values; against a calm reference, `quality.py`).\n56\t- `--mark`: `*` after the value when a measurement of the step is rejected (`x`, `y`, `error_value` of a rejected measurement stay filled), `o` when one has inlier = 0.\n57\t- `--instants T1,T2`: only the steps that contain these instants (the values of all the sensors at a few chosen times).\n58\t- With `--step` equal to the cadence, `--level window --mark`: the per-instant, per-sensor table of one column, one column per run.\n59\t\n60\t### plot\n61\t\n62\t```\n63\t.venv/bin/python tools/scripts/plot.py [--sensors A,B] [--columns C1,C2] [--start T] [--end T] [--zone T1/T2 ...] [--out D]\n64\t```\n65\t\n66\tA PNG of the series, each `--zone` greyed; prints its path. Columns: those of `summary.py`, quality metrics included (raw values).\n67\t\n68\t### overview\n69\t\n70\t```\n71\t.venv/bin/python tools/scripts/overview.py [--columns x,y,sigma0] [--column error_value] [--step 15min] [--k 5] [--min 5] [--residuals corr_x,corr_y,error_value|no] [--outside T1/T2] [--others] [--rigid BASE [--without A,B] [--follow A,B]] [--table T1/T2|no] [--sensors A,B] [--start T] [--end T] [--out D]\n72\t```\n73\t\n74\tAll the sensors together, each against its median and its MAD over the window.\n75\t\n76\tPNGs:\n77\t- **common**: at the top, if the folder has `camera/`, the **camera pose** (raw values, one point per registration, the line cut at measurement instants without registration); the median across sensors of `x`, `y`, `sigma0`, the dispersion across sensors as a grey band; on the `x`, `y` panels, also **each global reference separately** (one line each) and the **median of the targets alone** (black line); at each step, the number of sensors whose `--column` exceeds its median by more than `--k` MAD. Ticks every 1 to 12 h depending on the window, every n days beyond 20 days.\n78\t- **multiples**: a small chart per sensor, one scale each: a step of a single sensor shows there.\n79\t- **residuals-corr_x**, **-corr_y**, **-error_value** (`--residuals`; `no`: none of these PNGs nor their tables): a small chart per sensor of the column minus the sensor's own level (its median over the window; with `--outside T1/T2`, that of the rest of the window, outside the moment read), one scale each, zero dotted: a deviation of a few hundredths on `corr`, hidden in the parallel bands of `plot.py`, shows there.\n80\t- **residuals-…-others** (`--others`): each sensor minus its own median **and minus the median of the other sensors at the same instant**: what all share (the remainder of the compensation of a common movement) cancels, what is specific remains.\n81\t- **rigid** (`--rigid BASE`): at each measurement, the overall movement of the targets since the instant `BASE` (translation, rotation, scale, estimated by medians: a target that jumps alone does not pull it; `--without A,B` removes targets from it) and, for each sensor, the **residual** `dx`, `dy` (raw position minus its position at `BASE` carried by this movement, in px). Panels: `dx`, `dy` of each global reference against the median and the 10th-90th percentile of the targets, `|residual|` of the targets (median, 90th percentile), fitted rotation and scale, `reproj_err` of the references; a rejected reference is a cross (the scale is that of the accepted measurements, a far cross is out of frame).\n82\t\n83\tPrinted:\n84\t- the **common median table**, one line per `--step`: the time, the deviation from the window median of `x`, `y`, `sigma0`, then `x_targets`, `y_targets` (median of the targets alone), then the raw camera pose `cam_pan`, `cam_tilt`, `cam_rotation`, `cam_scale`, `cam_sigma0` (empty without registration); the minimum and the maximum of each column with their instant; then those of `x`, `y` of each global reference (`(rejected)` when the measurement is, with the reference's number of rejected measurements); the measurement instants without pose (dated runs); the instants where at least `--min` sensors exceed together, with their names (`--min 1`: also a single sensor that leaves its level, absent from the default list of 5 sensors);\n85\t- `--residuals`: per sensor, the level, the own noise (median of the differences between two measurements), the min/max deviation per step with their instant, in units and in noises;\n86\t- `--others`: per sensor, the slope and the correlation r of the residual on the common median of `x`, `y`, `sigma0`;\n87\t- `--rigid`: the table by step (`rot_deg`, `scale`, `tx`, `ty`, `tgt_med`, `tgt_max`, `dx`, `dy` of each reference and of each sensor of `--follow A,B`: the step-by-step sequence of a target) and, per sensor, min, max and value at the last instant of `dx`, `dy`. Rejected measurements enter neither the fit, nor the band of the targets, `tgt_med`, `tgt_max`, nor the columns of the table (over several days, parked cars or night rejections no longer drown the rest); the per-sensor summary gives them separately (`; N rejected: min …, max …`, and `(rejected)` after a last value that is rejected).\n88\t\n89\tThe tables by step (common median, `--rigid`) repeat their header every 24 lines; `--table T1/T2` prints them only between T1 and T2 (`no`: not at all), levels, min, max, PNGs and the rest remaining over the whole window: over a one-month batch, first `--table no`, then `--table` on the day of a moment (same levels, which a shorter `--start`/`--end` window would not give). The default step is 15 min, the cadence of the measurements: a one-hour step flattens a peak of one to four steps, dates to the hour and erases an agitation of `x`, `y`; do not widen it to read a batch.\n90\t\n91\tReading, in this order:\n92\t1. **The camera pose first** (top panels, `cam_` columns), dated at the native step: when it rotates (`pan`, `tilt`, `rotation`), changes scale, when its registration degrades (`sigma0`) or is absent (line cut, instants without pose). Each moment of the sensors is read against it: during a movement or a registration gap, or camera still.\n93\t2. **Who moves in the image.** The pose is computed from the global references: a change of pose (or a rise of `sigma0`) is a camera movement only if **the targets also move in the image** (on the `x`, `y` panels, the lines of the references against the black line of the targets alone; `x_targets`, `y_targets`). Only references move, targets still: these references moved, and the pose and the `corr` of all the targets are skewed without raw movement of the targets; say which references and by how much. References and targets together: the camera or the scene; then look whether the `corr` come back.\n94\t3. **Rotation or scale: `--rigid`.** Then the deviation from the median no longer says who moves alone (each sensor deviates according to its place in the image; the rigid residual does not). Before writing \"everything moves together\", rerun with `--rigid BASE`, `BASE` a calm instant before the first movement: a reference whose residual stays far from the 10th-90th percentile of the targets, or a `reproj_err` of the references that does not come back, means the compensation remains skewed by these references and the steps of `corr` partly come from it (say which, by how much, until when); a rising `|residual|` of the targets says they do not move as a block.\n95\t4. **Then `x`, `y`, `sigma0`, before `corr`**: the median of `x`, `y` (raw position, references included), the references one by one, the targets alone and `sigma0` say what moves in the image. Date the start, the end, the return of a movement, or a level that does not come back, on the printed table (time, value), not on the PNG axis. A dip of `corr` after a movement of the raw median is the remainder of the compensation, not a movement of these sensors. The multiples of `error_value` show a lasting step of a sensor, the count the instants where many rise together.\n96\t5. **The residuals, on every batch, without waiting for a suspicion**: a single sensor that rises or falls, a `corr` that drifts by a few hundredths, a step specific to one sensor under a common movement show there; the table says by how much (in noises) and when. On a target whose `corr` goes down under a strong common movement, `--others` separates a remainder of the compensation from a movement of its own: a dip that remains is not a remainder shared by all; a high slope with r close to ±1 on common `y` says it is proportional to the common movement (gain specific to the sensor); without r or slope, it is independent of the movement.\n97\t\n98\t### ranges\n99\t\n100\t```\n101\tpython3 tools/scripts/ranges.py [--columns error_value,corr_x,corr_y] [--k 5] [--merge 1h] [--min-measurements 1] [--outside T1/T2] [--rolling N|DURATION] [--instants N] [--sensors A,B] [--start T] [--end T]\n102\t```\n103\t\n104\tDates the start and the end of a sensor's moment without rerunning ten tables. By column and by sensor, at the measurements (native step, never averaged): level (median of the window), own noise, **largest jump** from one measurement to the next (value, in noises, the two instants; `(rejected: …)` when one end is); then the **ranges** where the sensor deviates from its level by more than `--k` noises: start, end, number of measurements, extreme (signed, in units and in noises) and its instant. Two ranges of the same sign less than `--merge` apart make one; rejected measurements do not cut a range; column `rejected`: how many of the range's measurements are (and `rejected extreme`). A range that touches the edge of the window is dated at the edge.\n105\t- `--outside T1/T2`: level and noise computed outside an episode that skews the window median (the sensor spends half the batch there). Rerun with it around a long episode to date its return to the level: do not conclude \"does not come back\" without having read it.\n106\t- `--min-measurements N`: only the ranges of at least N measurements (and how many out of the total). Over several days, the one-step ranges number in the hundreds and drown the long steps: first `--min-measurements 6`, then without.\n107\t- `--rolling N` (N measurements on each side) or `--rolling 1d` (the measurements within a duration): the level of each measurement is the median of its neighbours, without it; a long drift or a step follows this local level, only the deviations shorter than the window remain (the level column and the noise do not change; with `--outside`, only the noise is computed outside the episode).\n108\t- `--instants N`: at the end, the instants where at least N sensors are out of level on one of the columns, with each sensor and its signed deviation in noises (`cx` corr_x, `cy` corr_y, `ev` error_value), the sensors rejected at that instant (among `--sensors`: removing the always-rejected sensors lightens the list), and each reference: `error_value` (`r` if rejected) / inlier.\n109\t- When the batch has a long drift or several steps (the ranges number in the hundreds, or one half of the batch is \"out of level\"), rerun with `--rolling` (a few measurements, or a few hours to a day depending on the cadence) and `--instants 2`: the brief deviations under the drift come out alone, and the list per instant says which sensors deviate together, which are rejected and what the references do; a deviation of all the targets with the references at the same instant is read against the camera pose.\n110\t\n111\tA noise of `0` (and \"-\" in noises, no range): the values are constant to rounding (deviations below 1e-9), like the `corr` of the references when the compensation retains only two (see Conventions); the same in `overview.py --residuals` and `days.py`.\n112\t\n113\t### days\n114\t\n115\t```\n116\t.venv/bin/python tools/scripts/days.py [--columns corr_x,corr_y,error_value] [--night 20-3] [--k 5] [--days 2] [--step 15min] [--sensors A,B] [--bounds [--smoothing N] [--fraction F]] [--start T] [--end T] [--out D]\n117\t```\n118\t\n119\tWhat comes back from one day to the next, on accepted measurements only. A night: the hours `--night` H1-H2 UTC, straddling midnight, dated from the day it starts; choose hours where the day cycle (`error_value`, camera pose) has subsided (**byhour** figure).\n120\t\n121\t1. **Level of each night**, by sensor and by column: median, MAD, number of measurements, own noise; from one night to the next, the **step** (difference of the medians, in units and in noises) and **where it falls** (\"between A and B\": where the night measurements of the two nights split best between the two levels; B at the start of the following night: the cut falls by day). Read it for any sensor that has already made a step or for which `--outside` is not enough (several levels in the batch): a step of a few noises is dated by its \"between A and B\", a step of `error_value` and one of `corr` at the same instant are linked, a slow drift reads from one night to the next.\n122\t2. **Superimposed days**: PNG **byhour-**, a small chart per sensor, hour of the day on the x axis, one curve per day, each measurement minus the level of the last night started (night greyed, frame from the 1st to the 99th percentile, the title says how many measurements fall outside it). Table: per `--step` slot of the hour of the day, the sensors whose deviation exceeds `--k` noises on the same side at least `--days` days, with the number of days and the median of these deviations. What comes back every day at the same hour, on one or several sensors, groups there, even when it lasts one to three measurements: one moment per hour of the day (say which sensors, how many days out of how many, the amplitude, what the camera pose does at that hour), not one moment per day, nor nothing because each step is short.\n123\t3. **Bounds of each day** (`--bounds`), for what comes back every day and is labelled day by day (thermal cycle, warming and cooling), rather than fixing the same hours for all the days: for the median of the targets of each column (with `--sensors`, the median of these sensors; with one, its own) and for the camera pose (`pan`, `tilt`, `rotation`, `scale`, `sigma0`, if `camera/` exists), the deviation from the level of the night that precedes each day (a day goes from the end of one night to the end of the next). Per day: number of measurements, the first and the last; first and last instant beyond `--k` noises, with the measurement just before and just after, at the native step; signed max and min with their instant; the sequence of measurements beyond `--k` noises around the larger of the two; the following night minus the reference night. A day without measurement says so; a reference night that is not the previous one is named. Each day line starts with the short name of its series (`corr_x`, `pose_tilt`…): `| grep '^pose_tilt '` reads one, `| grep ' 12/10 '` one day. PNG **bounds**: the deviation over the batch, first → last exceedance light grey, sequence around the extreme dark grey, max and min marked.\n124\t - `--smoothing N`: the deviation of each measurement is the median of the N measurements of the day centred on it (noise and `--k` unchanged; PNG: smoothed in blue, raw in grey): an isolated point no longer cuts the sequence around the extreme nor makes a first or a last exceedance.\n125\t - `--fraction F`: the threshold of each day is F times its largest |deviation| (printed on its line, `threshold …`), instead of `--k` noises: when the noise at the native step is unrelated to the amplitude of the cycle (very noisy or very smooth pose).\n126\t - Reading: the sequence around the extreme dates the cycle, the max and the min a go and a return (morning and afternoon); \"before\" and \"after\" give the bounds at the native step (at a cadence of 1 h or 4 h, an event goes from the measurement before to the one after). First exceedance at the start of the day (\"before -\") and last at its end every day: the night is not calm; change `--night`, or `--sensors` the targets that carry the cycle. Camera drifting all night: a short night just before the morning (`--night 3-5`: the level of the rest that precedes the start). Noisy series or isolated points: `--smoothing 5`. Threshold in noises that does not bite (never exceeded, or exceeded all day): `--fraction 0.3`, then read the sequence around the extreme, not the first and the last exceedance. A \"1 measurements\" line is a peak, not a cycle.\n127\t\n128\t### metrics\n129\t\n130\t```\n131\t.venv/bin/python tools/scripts/metrics.py [--names A,B] [--step 1h] [--stat median|min|max] [--against temperature] [--smoothing 24h] [--metrics-only] [--start T] [--end T] [--out D]\n132\t```\n133\t\n134\tThe system metrics of `metrics/` (one value per hour), never the identifiers (`SIM_CCID`, `ip*`):\n135\t- the available metrics with their number of values over the window (\"empty\": none; all empty is an absent datum, not a stable temperature);\n136\t- a table per `--step`: `temperature` (median of the `sensor_*_deg_c` components, the one the detectors read), each metric of `--names` (default: the `*_deg_c` and `BusVoltage`), then, unless `--metrics-only`, `tgt_corr_x`, `tgt_corr_y` (median over the targets of `corr` minus each target's own level, accepted measurements) and the raw camera pose (`cam_pan` … `cam_sigma0`); an empty cell is skipped, a text metric (`link`, `BatteryState`, `last_sync`) is returned as it is. `--step 1d --stat min` (or `max`): the minimum or the maximum of each day;\n137\t- per column: filled steps, min and max with their instant; the correlation r and the slope of each column on `--against` (with `--smoothing 24h`, on its rolling mean, column `_smooth`: for a station where the temperature varies little and fast, indoors); the dated runs of steps without any metric;\n138\t- a PNG: temperatures on one panel (median in black), each other metric on its own, then `tgt_corr_x`, `tgt_corr_y` and the pose, line cut on a gap.\n139\t\n140\tAn r does not say a cause: say it as a value, with the window where it is computed.\n141\t\n142\t### stations\n143\t\n144\t```\n145\t.venv/bin/python tools/scripts/stations.py [...] [--columns temperature,cam_tilt,cam_rotation,cam_scale,tgt_corr_x,tgt_corr_y] [--step 1h] [--stat median|min|max] [--table T1/T2|no] [--start T] [--end T] [--out D]\n146\t```\n147\t\n148\t**Several stations on the same timeline** (neighbouring stations, same building). Columns: `temperature` (as in `metrics.py`), `cam_pan` … `cam_sigma0` (raw pose), `tgt_corr_x`, `tgt_corr_y` (as in `metrics.py`), `rej_targets`, `rej_refs` (number of rejected targets, of rejected references, the largest of the step).\n149\t- Prints per station the period, the cadence and the number of instants; the **gaps**: the runs of steps without measurement or without temperature, with the stations where they are missing (a gap common to several stations on a single line); the table by step (one `STATION:column` column each, tabs; `--table` as in `overview.py`); per column and per pair of stations, r of the values and r of the steps from one value to the next (a common movement shows on the steps, a common trend on the values), with n.\n150\t- PNG **stations**: a panel per column, a line per station (raw temperature, the rest minus its median), and a band per station of the steps without measurement.\n151\t- Take `--step` equal to the slowest cadence of the stations; over a month at `1h`, first `--table no`.\n152\t\n153\t### quality\n154\t\n155\t```\n156\tpython3 tools/scripts/quality.py [--calm T1/T2,T3/T4] [--common] [--table M] [--step 15min] [--threshold 0.5] [--sensors A,B] [--start T] [--end T]\n157\t... --labels F [--numbers 3,7] [--margin 60] [--edges]\n158\t... --labels F --outside [--min 1] [--except \"Thermal displacement\"]\n159\t.venv/bin/python tools/scripts/quality.py --figure [--metrics flux,snr,dominance] [--labels F] [--zone T1/T2 ...] [--out D]\n160\tpython3 tools/scripts/quality.py --self-test\n161\t```\n162\t\n163\tThe six **image quality metrics** (`peak`, `flux`, `sharpness`, `fwhm`, `dominance`, `snr`; definitions: `tools/DATA.md`), on the stations that have them (otherwise: \"No quality metrics\", and nothing else). Each measurement becomes a **ratio** to the **calm reference** of its sensor: the median of the metric over its measurements in the `--calm` windows, at the same UTC hour of the day (without `--calm`: the whole folder); 1 = like the reference, < 1 lower, > 1 higher; for `fwhm` and `dominance`, the rise says a degraded image; rejected measurements included.\n164\t- Without options: the folder's maximal `peak`, then per sensor (`r` = reference) the rejected measurements, `pk/max` (median peak over the window divided by this maximum: at 1, the spot touches the image ceiling, its `peak` no longer moves and its `sharpness` follows the exposure: read `flux`, `snr` instead), and for each metric the median ratio and the extreme with its instant; then the median of the targets and of the references.\n165\t- `--common`: per step, the median of the ratios of the targets / of the references for each metric (what affects the whole scene, visibility or turbulence; `--step 1d` shows on one screen on which days the reference holds).\n166\t- `--table M`: per step, the ratio of `M` of each sensor (`*`: a rejected measurement), their median and how many pass `--threshold` (below, or above 1/`--threshold` for `fwhm`, `dominance`): a target that goes out and comes back; on a moment, `--table flux --sensors …` says which targets are hidden (flux cut) or veiled, from which instant to which instant: write them by their name.\n167\t- `--labels F` (one JSON per line, `start`, `end`, `family`): per numbered label, the median ratio of the targets and of the references over the hour before, the range and the hour after (`tgt 0.96|0.26|0.79`, `--margin` minutes), then the sensors **affected** over the range (flux or snr below `--threshold`, or dominance above 1/`--threshold`), with their worst flux, from lowest to highest. `--edges`: per instant of the widened range, the number of affected sensors and the median of the targets of flux, snr, dominance (`<` within the range), to date the first and the last degraded instant.\n168\t- `--outside`: the runs of instants that no label covers (outside `--except` families) where at least `--min` sensors are affected, with the sensors and their worst flux: candidates for forgotten labels, to check on `corr_x`, `corr_y`.\n169\t- `--figure` (instead of the tables): PNG **quality-common** (a panel per metric, log scale: median of the targets in black, of the references in red, grey band from the 10th to the 90th percentile of the targets: a disturbance of the whole scene moves the median, an occultation of a few targets only the bottom of the band) and a PNG **quality-** per `--metrics` (a small chart per sensor, references in red); `--labels` greys each label in one colour per family, `--zone` ranges.\n170\t\n171\tReading: the metrics say **why** a measurement degrades, where `error_value` says only that it degrades; they prove a cause and name the affected targets. What they showed on LENZSPITZE (to be confirmed on each station): `flux` cut (close to 0) on a group of targets, the others intact, for one to a few measurements: these targets are hidden (the list is read on the flux each time, not on the usual list; a hidden target can stay under its error threshold, and its point is wrong); `flux` down over the whole scene, stronger on the distant targets: reduced visibility; `sharpness` down and `dominance` up, `flux` whole: the image shakes (turbulence); nothing moves: neither the image nor the view, to be looked for in the movement. A whole flux refutes an occultation. `fwhm`, truncated to the disc, moves little; on a spot at the ceiling (`pk/max` at 1), it goes down when the spot darkens.\n172\t\n173\t**The calm reference decides everything**: take `--calm` on calm hours of the **same image regime** as the range read. When the lighting or the exposure changes (after a gap, an intervention), a reference on the other side skews the ratios by a factor of two or three: `--common --step 1d` over the batch shows this change (medians of the targets and of the references far from 1 for whole days, then at 1); then take a reference on each side and read each side with its own. Calm days are often days of thermal cycle: a reading of the thermal against them is circular.\n174\t\n175\t### thumbnails\n176\t\n177\t```\n178\t.venv/bin/python tools/scripts/thumbnails.py --sensors A,B --times T1,T2 [--radius 100] [--contrast [MIN,MAX]] [--fixed] [--zone X,Y,W,H] [--out D]\n179\t```\n180\t\n181\tA sheet of full-resolution thumbnails: one row per sensor, one column per time, centred on the sensor's raw position (`x`, `y`) at each time. Look at it with Read: a whole image read by Read is reduced, a small reflector becomes illegible in it.\n182\t- The centre of the frame is written under each thumbnail: when `x`, `y` jump, the frame moves by as much, and a spot that enters the frame seems to appear; `--fixed` keeps for each sensor the frame of the first time and marks with a red cross the `x`, `y` of each time.\n183\t- Unretouched pixels: the brightness compares from one thumbnail to the next; prints for each thumbnail the background (median), the 99th percentile and the peak (grey levels 0 to 255). Without an image at the requested time, takes the nearest and prints the gap (the actual time is in the title).\n184\t- A faint or deformed spot is invisible as it is: `--contrast MIN,MAX` puts all the thumbnails in grey with the same stretch (without value: from the 1st percentile to the sheet's maximum, crushed by a saturated pixel; then choose MIN,MAX from the printed background and peak, e.g. `10,40`); `--radius 30` to `50` magnifies. Compare the shape and the peak before, during and after an episode, at the same hour of the day.\n185\t- A frame that the image edge cuts is flagged (\"frame cut by the image edge (W × H px)\"): on some stations, `x`, `y` are not pixels (values close to 0) and the frame falls in the corner; then look at the scene through `--zone`.\n186\t- `--zone X,Y,W,H` (pixels of the original image: top left corner, width, height, as in `gif.py`): the same zone at each time, side by side (up to 4 per row), same stretch with `--contrast`; `--sensors` becomes optional, those given are marked with a cross and their name. For the scene around the targets (foreground object, headlights, lighting), prefer it to a large `--radius`.\n187\t- Each thumbnail is rendered pixel for pixel up to 1000 px a side, but Read reduces a wide PNG: with a large `--radius` or a large `--zone`, three or four times per sheet.\n188\t\n189\t### gif\n190\t\n191\t```\n192\t.venv/bin/python tools/scripts/gif.py --start T --end T [--width 720] [--duration 700] [--max 150] [--zone X,Y,W,H] [--out D]\n193\t```\n194\t\n195\tA GIF of the camera images between `--start` and `--end` inclusive, cropped to `--zone` if needed, set to `--width` px, UTC date and time at the bottom right; beyond `--max` images, `--max` at regular intervals; prints the time of each image, then the path and the size of the GIF. To attach the scene to a reply to the customer; Read does not read a GIF: to look, `thumbnails.py --zone`.\n196\t\n197\t### whole image\n198\t\n199\t```\n200\tls /images/ | grep TZ\n201\t```\n202\t\n203\tThen Read on the file found (Read takes no pattern): the whole camera image at that time (UTC), for the scene (occultation, lighting, weather).\n204\t\n205\t## Conventions\n206\t\n207\t- Instants: `2026-01-01T00:00Z`; a time without time zone is read as UTC; `--end` includes the minute given. On a batch, `--start` and `--end` of the batch.\n208\t- Bash is used only to run these tools, `ls`, `grep` and `date`, one command per call, without a `for` loop (a pipe to `grep` is allowed): permissions are granted command by command. If the current directory is not the root of the calling repository, `cd && ` counts as one command. Write no other script. Whoever calls you may add commands to this list.\n209\t- **An output too long for one call** (beyond a few hundred lines, cut at display): shorten it first with the tool's options (`--table no` then `--table T1/T2`, `--min-measurements`, `--sensors`, `--columns`, a shorter window), or read a section of it through a pipe to `grep` (`| grep -A40 '^Title'`, `| grep '^pose_tilt '`). If you have to reread it several times, store it in the output folder in the same call (` > /.txt`) and read that file with Read (`offset`, `limit`) or with `grep`: no `head`, `tail`, `sed`, `cut`. The tools create their output folder themselves: no `mkdir`.\n210\t- A sensor name that carries an apostrophe (`COLH20'''`, `REFP''21`) goes in double quotes in the shell: `--sensors \"COLH20'''\",COLI22`.\n211\t- **Each PNG is looked at with Read**: you read a chart better than a table, and a PNG you have not looked at has shown nothing.\n212\t- A rejected measurement (`error_value` above the threshold) is not a measurement: the station empties the `corr` of a rejected target, but leaves those of a rejected **reference**, often absurd; the tools empty them (`corr`, ranges, residuals, jumps cover only accepted measurements). When the compensation retains only **two references**, their `corr` is 0 (to 1e-13): it passes exactly through them; their noise prints as `0` and their deviations in noises as \"-\"; read nothing into these values, read the references through `x`, `y` (`overview.py --rigid`) and `error_value`. Its `x`, `y` remain: before citing a jump of `x`, `y`, check whether it is marked `(rejected)`; a rejected measurement is not cited as a movement.\n213\t\n214\t## The method\n215\t\n216\t1. **Inventory** (`inventory.py`): what is available, what is missing. A filled column that the tools do not show or a source that no tool reads (`images_diff/`) remains data: know that it exists. The image quality columns (`peak` to `snr`, recent cameras) are read through `quality.py`; `metrics/` through `metrics.py`: a cut of the measurements is read against the steps without metric and the voltage (`--names BusVoltage,BusCurrent,Power,BatteryPercent --metrics-only` on the cut). On a batch, rerun it with the batch's `--start`/`--end`: the absent steps and the rejections of the batch, dated; those of the whole period say nothing about the batch. Read the rejections of the **references** as much as those of the targets: a sensor rejected at the same hours every day makes a moment on its own (say its share of rejected measurements and its hours, day by day); when it is a reference, say with how many references the compensation then runs (the list of retained references). When several targets jump together by one step, or the compensation drops (no pose), look first in that list at which references were lost at that instant.\n217\t2. **Wide first**:\n218\t - `overview.py` on the batch, first (on a batch of more than a few days, `--table no`, then `--table T1/T2` on the days to read), read in the order of its Reading section: the pose, who moves in the image (`--rigid` as soon as the pose rotates or changes scale), `x`, `y`, `sigma0` before `corr`, the residuals on every batch.\n219\t - On a batch of more than two days, then `days.py`, before reading the isolated steps of `ranges.py`: first its **byhour** PNGs and table by slot, then its **night levels**; `days.py --bounds` for what comes back every day and is labelled day by day.\n220\t - Several neighbouring stations given by whoever calls you: `stations.py` (temperatures, poses, `corr` of the targets, common rejections and gaps, at the same hours) before comparing their moments.\n221\t - When the pose or the `corr` of the targets drift over several days, or move without day/night cycle: `metrics.py` on the batch, the temperature against `tgt_corr_x`, `tgt_corr_y` and the pose, on the PNG, then r and the slope.\n222\t - On a station that has the image quality metrics: `quality.py --common --step 1d` on the batch (choice of the calm reference), then `quality.py --figure` with this reference: the median `flux` of the targets and of the references dates the hours of reduced visibility, the grey band that dives alone the occultations; with a labels file, `--labels F --outside`.\n223\t - Then `plot.py` on all the sensors, `error_value` then `corr_x`, `corr_y` (or `relative_x`, `relative_y`), references and targets; `summary.py` on these columns with a wide step (6h or 1d).\n224\t3. **Then zoom**: `summary.py` at 15min (`--stat max` for the real peak of a sensor), and `plot.py` on the windows and the sensors that move.\n225\t4. **Each sensor against its own usual level** (its median and its MAD), never against an absolute threshold; on a batch, the level is computed on the batch (`--level window`, `overview.py`), not on the whole period.\n226\t5. **Each retained moment is dated and measured at the native 15 min step**: start, end and maximum read on the 15 min table (`overview.py` by default, `summary.py --step 15min`), never on an hourly table; also `overview.py --min 1` for single sensors; `ranges.py` on the batch (first `--min-measurements 6`) for, per sensor, start, end, extreme and largest jump at the native step (`--outside` around a long episode, `--rolling` and `--instants 2` under a long drift or several steps); the tables of `x`, `y` on the windows where they stir. On a station that has the quality metrics, for each moment: `quality.py --table flux --sensors …` (or `--labels F --numbers N --edges` on a label): which targets are hidden or veiled, from which instant to which instant.\n227\t6. **The images**: thumbnails (with `--contrast` for a faint target) spaced, one every 2 to 3 h, tighter where the curves move, always with an unaffected witness sensor, at a time before, during and after (at the same hour of the day if possible); when `x`, `y` of a sensor jump between two thumbnails (centre of the frame written under each), rerun with `--fixed` before saying that a spot appears or disappears; the whole image for the scene (occultation, lighting, weather).\n228\t\n229\t## What the reading returns\n230\t\n231\tOne line per moment. A moment: a sensor or a group of sensors that leaves its usual level during a window you can date.\n232\t\n233\t| Start | End | Sensors | Columns | What I see | Images |\n234\t|---|---|---|---|---|---|\n235\t\n236\t- **Sensors**: references or targets, how many, which ones.\n237\t- **What I see**: the shape (one-step peak, step, slow rise, agitation), the amplitude against the usual level (in MAD or in times the median), the return to normal or not, what the other sensors do, **what the camera does** at the same moment (pose moving, by how much, or still; registration absent; \"no `camera/`\" if the folder has none).\n238\t- **Images**: what the thumbnails and the whole image show at that moment, or \"no image\".\n239\t\n240\tTimes in UTC.\n241\t# The data of a station\n242\t\n243\tWhat the files of a station folder are, and what each column means. How to read them with the tools: `GUIDE.md`. What they mean for a label (causes, reading rules, false friends): `labeling/reading-rules.md`. Maintained by hand; `GUIDE.md` is the tool-builder's.\n244\t\n245\t## The displacements: the \"advanced\" export\n246\t\n247\t`displacement/_advanced__.csv`, the source of the analyses: one row per sensor and per measurement, at the native rate of the station (10 or 15 min), `time_utc` in explicit UTC.\n248\t\n249\t| Column | Meaning |\n250\t|---|---|\n251\t| `sensor_name` | the sensor (target or reference) |\n252\t| `pattern_type` | `global_ref`: a reference of the compensation; `ref`: a *local reference*, treated as a target, outside the compensation, without `reproj_err`; empty: a target |\n253\t| `x`, `y` | raw position in the image [px]. Not the centroid of the spot: the offset centroid − (`x`, `y`) is constant per sensor by day and differs between sensors; it changes at night, when the spot is saturated. Probably the position of the reference pattern |\n254\t| `relative_x`, `relative_y` | relative displacement before the camera compensation [px]; not `x − x0` |\n255\t| `corr_x`, `corr_y` | the position of the target once the estimated camera movement is removed: **the curves that are labelled**. In px, not mm (below) |\n256\t| `corr_x_mm`, `corr_y_mm` | `corr_x`, `corr_y` in mm: × the sensor's `mm_per_px` (`targets.csv`, below), computed by `data.load`; empty without a sure factor. The same curves in another unit: the noise threshold of a label is read in noises, whatever the unit; mm say how far a target moves, for the reader |\n257\t| `error_value` | recognition error of the pattern, not an uncertainty |\n258\t| `error_threshold` | specific to each sensor (0.3 to 0.7). Above it, the measurement is rejected: the row and its `error_value` stay, `corr_x` and `corr_y` are empty, not interpolated |\n259\t| `reproj_err`, `inlier` | references only: residual and contribution of each reference in the compensation |\n260\t| `sigma0` | residual of the fit on the references: one value per measurement, repeated on every row |\n261\t| `peak`, `flux`, `sharpness`, `fwhm`, `dominance`, `snr` | image quality of each sensor, recent cameras only (below) |\n262\t\n263\t- \"Rejected\" is a judgment of the AIMsight platform, not of the camera: the camera delivers all its measurements, and a client's platform that integrates the data receives them all.\n264\t- **Unit of `corr_x`, `corr_y`**: px. The hourly export's `horizontal_displacement` (mm) is a factor × the hourly mean of `corr_x` + a constant (likewise `vertical` and `corr_y`, correlation ≥ 0.99); the factor (mm per px) depends on the pattern and on the station.\n265\t- **LENZSPITZE**: its export gives `x`, `y` relative to the pattern; the extraction rewrites them in image px and fills `pattern_type`. Sensors 1023 and 8019 have no pattern: their `x`, `y` are empty. The tools' crosses may sit slightly off the spots there.\n266\t- `inventory.py` says, on a batch, which columns carry values.\n267\t\n268\t## The targets\n269\t\n270\t`targets.csv`, from the pumping: one line per sensor of the platform, `sensor_name`, `pattern_type`, `distance_mm` (from the camera) and `mm_per_px` (`distance_convertion_factor`, the factor of the dashboard's exports in mm), their current values. Read by `data.load_targets`, shown by `inventory.py` (sensor table).\n271\t- The references are not in it yet (pumped from the next pumping on): no distance, no mm for them. They are assumed fixed.\n272\t- `distance_mm` 1000: not filled in on the platform; the line is ignored.\n273\t- A name may have several lines (a target counted twice, an older configuration of the unit, another lens): when they disagree, `data.load_targets` keeps no value (`inventory.py`: `?(n)`) and that target has no mm; the distance stays when the lines agree on it.\n274\t- The distance says which targets are near and far. A far target moves few px for many mm: targets are compared with each other in mm, or in px with their distance. A camera that turns shifts every target by about the same px (the mm grow with the distance); a movement of the structure of the same mm gives px that shrink with the distance; a parallax shows between targets at different distances.\n275\t\n276\t## The camera pose\n277\t\n278\t`camera/_camera_.csv`, from the pumping only: the pose at each registration, `time_utc` in UTC, `median_|min_|max_` of `pan`, `tilt`, `rotation` [deg], `scale`, `sigma0`, one row per measurement (min = max). A measurement instant without a row: the camera was not registered.\n279\t\n280\t- Orders of magnitude: `pan`, `tilt` of a few hundredths of a degree, `scale` within 10⁻³ of 1; some stations show several degrees, not explained.\n281\t- **A positive `tilt` means the camera is nosing down** (the expert).\n282\t- Read by `overview.py` and `inventory.py`.\n283\t\n284\t## The weather\n285\t\n286\t`weather/_weather_.csv`, from the pumping, for a station with a Swiss position only: the hourly measurements of the nearest MeteoSwiss station, `time_utc` in UTC (start of the hour); `position`, `place`, `station`, `station_name`, `distance_km`, `height_m` say where; then `precipitation_mm`, `temperature_c`, `humidity_pct`, `wind_speed_kmh`, `wind_gust_kmh`, `wind_direction_deg`, `pressure_hpa`, `sunshine_min`, `global_radiation_wm2`, `snow_depth_cm` (empty: not measured there). The weather a few km away, not at the camera: what the images show prevails. Read by `data.load_weather`.\n287\t\n288\t## The hourly export\n289\t\n290\t`__to__1hour.csv`: one row per hour, targets only; per target `horizontal_displacement`, `vertical_displacement`, their `_min` / `_max`, `_error` (mean `error_value` of the hour), `_count_val` (measurements of the hour, rejected ones included).\n291\t\n292\t- **`timestamp` has no time zone: Swiss local time** (UTC+2 in summer), at the start of the hour.\n293\t\n294\t## Image quality of a target\n295\t\n296\tSix columns of the advanced export, computed by the GPU of recent cameras on the sensor's window in the DIFF image, in units of that image. Filled only where `inventory.py` says so (\"Export image quality\"); for older cameras, `~/optical_emulator` can recompute them from the DIFF images. \"Disc\": the neighbourhood of the peak, radius `min(H, W)/6` (at least 3 px); \"background\": the rest of the window.\n297\t\n298\t| Metric | Definition | What it measures | Reading |\n299\t|---|---|---|---|\n300\t| `peak` | `max(I)` | the brightness of the return | high, saturation; low, underexposure or missed flash. All targets dropping: the lighting; a single one: that target (fouling, misalignment) |\n301\t| `flux` | flux of the disc minus the background | the light of the target, background removed | reflectivity of the target (fouling, ageing, flash), not ambient light; drops well before `error_value` exceeds its threshold |\n302\t| `sharpness` | `Σ(I²) / (ΣI)²` | concentration of the energy (higher = sharper) | drops: drifting focus, turbulence, degrading target. Independent of the gain, not of the background: follow it over time on one target, do not compare cameras |\n303\t| `fwhm` | width at half height around the peak, background removed [px] | width of the spot | rises: defocus, turbulence, motion blur. Truncated to the disc: under strong defocus it flattens instead of rising |\n304\t| `dominance` | `(second peak − background) / (peak − background)`, 0 (clean) toward 1 (ambiguous) | does a single spot dominate the window? | high: a comparable second reflection, a stray bright point, or the target has gone and something else is the brightest: the correlation can latch onto the wrong pattern, which `error_value` does not see. One hot pixel outside the disc is enough |\n305\t| `snr` | `(peak − background) / bg_sigma` | the signal above the background noise | low: marginal return, even when `peak` looks normal. Independent of exposure and gain. The emulator marks `empty` below 8 |\n306\t\n307\t`peak` and `flux` give the brightness, `sharpness` and `fwhm` the sharpness, `dominance` and `snr` the validity: together they say **why** a measurement degrades, where `error_value` only says that it does. They describe the image of **one target**, not the health of the reference network.\n308\t\n309\t## Camera images: IRON and DIFF\n310\t\n311\t- **IRON** (`images/`): the ordinary image of the scene, JPG. The cause of an event is seen on it (condensation, rain, train, snow).\n312\t- **DIFF** (`images_diff/`): several captures combined to raise the contrast of the reflectors; **the image the displacement algorithms measure**, by default. Not a difference between two instants. 16-bit PNG.\n313\t- Acquisition modes (station manual): \"Single with infrared light\", one image per measurement; \"Differential\", several combined (`Stacking` 20 to 40 when light is difficult); option \"Work on IRON images\", to follow a texture without reflector.\n314\t- Not every station has DIFF images; the pumping keeps about one image per hour. The tools look only at IRON images; `inventory.py` counts the DIFF ones, which your own scripts may read. What is very close to the lens (a web) may stand out better on DIFF.\n315\t# The labeling rules\n316\t\n317\tHow to place a label: the only source of these rules for the aimsight-app `analyst` (before it, the Support-Agent `etiqueteur`) and for those who review their labels. The families, their boundaries and the catalogue of phenomena are in `families.md`; what the data mean, in `reading-rules.md`.\n318\t\n319\tSources in brackets: [instruction] the section \"Les étiquettes\" of `.claude/agents/etiqueteur.md`; [cross ] the cross review of 2026-11-04, `auto/revue-croisee/2026-11-04//revue.md`; [finishing ] its finishing pass, `auto/revue-croisee/2026-11-04/finition//revue.md`; [] the station review, `auto/revue/_/revue.md`; [consistency] that of BREITHORN, MICHIGAN and NEBRASKA; [expert] a label or an answer of the expert.\n320\t\n321\t## 1. What is labeled\n322\t\n323\t- **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]\n324\t- **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]\n325\t- **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]\n326\t- **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]\n327\t- **\"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]\n328\t- **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]\n329\t- **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]\n330\t- **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]\n331\t\n332\t## 2. The bounds\n333\t\n334\t- **`start` is the measurement just before the first touched point, `end` the measurement just after the last, never `start` = `end`**: a touched point moves or is missing; an anomaly of a single measurement goes from the point before to the point after (a passage at 11:00, 15 min rate: 10:45 → 11:15). [instruction, WILDSTRUBEL]\n335\t- **The bounds are measurement instants, at the minute of the measurement**: at a 15 min rate, it is the quarter hour; at 10 min or 5 min, the minute of the measurement, like the expert's label. [cross Obstruction, CLARIDEN, expert]\n336\t- **The bounds are read on the curves, not on the rejections**: a reference that drifts before being rejected, a target that comes back after the last rejection are touched; read the two or three measurements before the first rejection (the `error_value` of a reference and the pose often already move there), and, for a loss of references at night, the `corr_x` of the targets and of the neighboring references. [cross Visibility, FLORIDA, LENZSPITZE]\n337\t- **Each edge is checked sensor by sensor, in both columns, not on the median**: all sensors, not only those named; a `corr_x` peak can touch `corr_y` longer. [instruction, NORDEND, NEBRASKA, MICHIGAN]\n338\t- **A measurement that has come back halfway is still touched; one more measurement, already back, is too many**: read the value of the next step before closing, without rounding inward or outward. [instruction, BREITHORN, JUNGFRAU, CLARIDEN]\n339\t- **A range of rejections ends at the measurement following the last rejection of all touched targets**: the first rejected measurement is not the start either. [instruction, BREITHORN, NIEDERHORN, SNCF01]\n340\t- **A reference rejected at a bound counts as a touched point, unless it is rejected there as usual**: its usual rejections (by day, in the morning, a Target issue target) do not move the bound. [cross Obstruction, CLARIDEN]\n341\t- **At the edge of a gap, the bound is the first measurement after the gap, or the last before**: an event that starts at the resumption starts at that measurement, which is also the `end` of the No data; a single measurement inside an outage is bounded one rate step on either side. [cross Obstruction, WILDSTRUBEL, JUNGFRAU]\n342\t- **Before writing, a script checks the bounds**: `start` < `end`, they are measurement instants, and no sensor is touched there outside its usual rejections, references included. [cross Obstruction, WILDSTRUBEL]\n343\t- **The end of a nuisance specific to a target is read on its `corr_x` and `corr_y`, against its level before, over several nights**: not on the return of its `error_value`; without a return, the label runs to the end of the batch; without a level before, it ends where the curves stop changing. [cross Target issue, NORDEND]\n344\t- **A return ends where the curve stops coming back**: not at midnight; a plateau is not a return. [LENZSPITZE]\n345\t- **A label goes to the end of the batch only if points are still missing or moving there**: otherwise it ends at the return. [cross Displacement]\n346\t- **A lasting jump is bounded on the jump**: from the measurement before to the measurement after the one where the new level is reached; hidden in an outage, on the outage and the first measurement after; hidden under another label, at the first measurements where it is seen. [cross Displacement, expert]\n347\t- **The bounds of a thermal cycle are read day by day, on the turning points of the pose and of the `corr`**: never at midnight or at a fixed hour, except at the start and the end of the batch; when the pose is noisy, on its hourly median. [cross Thermal displacement, FLORIDA, SNCF01]\n348\t- **The camera cycle starts at the morning turning point**: the first instant when the tilt and the pan leave their end-of-night level without coming back, the later of the two; not the fast part of the movement, nor the first deviation of `days.py --bounds`; a deviation of a single rate step from the bound placed stays within the uncertainty. [cross Thermal displacement, NORDEND, finishing nordend]\n349\t- **It ends at the later of the two returns, the pose on its main axes and the curves at their night level**: an axis returns to the level where it then stays, not under a threshold set on the night, which may differ; the slow relaxation of a secondary axis (often the scale) does not push the end back, as in the expert's labels; without rest, the cycle ends at the next start and the labels follow one another. [cross Thermal displacement, NORDEND, WILDSTRUBEL, expert, finishing niederhorn, finishing wildstrubel]\n350\t- **A nuisance at night stops the cycle only if it distorts the pose**: a reference rejected, discarded, or that drifts against the targets (`overview.py --rigid`); a target bothered alone does not stop it. [finishing divers, finishing nordend]\n351\t- **A gap does not cut a cycle visible on both sides** (so the gaps of one or two measurements); otherwise, a gap or a jump at night stops it: the cycle ends at the rest of the pose if it comes before, otherwise at the last measurement before the gap or at the measurement before the jump. [finishing divers, finishing nordend]\n352\t- **Before extending a cycle over a night that moves, read the housing temperature and the references**: it must still drop there, or the pose follow its usual profile; a pose that moves at flat temperature, with a reference that drifts, is the nuisance of that reference, not the thermal return. [finishing divers]\n353\t- **The reference night of a cycle is chosen calm, not by civil day**: when the pose comes back all night, a start is dated at the turning point, not at the first deviation from that night. [SNCF01, cross Thermal displacement]\n354\t- **The phases of the structure are cut at the turning points**: when the trough is flat for several hours, the cut is placed in the flat and the two phases touch. [JUNGFRAU, cross Thermal displacement]\n355\t- **An event that touches the edge of the batch extends the label of the neighboring batch, if there is one**: it is not redone; otherwise, it starts or ends at the batch edge. [JUNGFRAU, cross Target issue]\n356\t\n357\t## 3. A single event\n358\t\n359\t- **One label, a single event**: two events, even close or mixed, make two labels; an event that repeats (a passage, the rain of each night, the thermal cycle of each day) makes one label each time. [instruction]\n360\t- **The outward and return of a drift are two labels**: after each slow drift, look for its return, and do not join a descent and its rise because the description says so. [instruction, CLARIDEN, cross Displacement]\n361\t- **The thermal cycle of the camera, outward and return, is a single event per day; the structure makes two, the expansion and the contraction**: this is what the expert does; the outward-and-return rule does not apply to the camera cycle. [cross Thermal displacement, expert]\n362\t- **An event in one piece over several days makes one label**: a change of speed does not cut it, nor a tilt that continues in the same direction; only a stop followed by a return, or a change of direction, cuts it. [instruction, BREITHORN, cross Displacement]\n363\t- **A return that exceeds the starting level remains the same event**: it does not start a new movement. [LENZSPITZE]\n364\t- **A lasting jump: the label bounds the jump, the return is another label**: the step is stated in the description; a step that returns within the day remains one label (a jump then the return); two steps separated by days of plateau make two labels, even in the same direction. [cross Displacement]\n365\t- **A bump that is only the trace of a slow camera movement follows the cutting of that movement**: it is not a separate event. [cross Displacement]\n366\t- **Two gaps separated by a single measurement that came back make a single No data label; separated by two measurements or more, two**: a single measurement does not make a resumption. [cross No data, SNCF01]\n367\t- **A measurement where a target is rejected alone just after a passage is the same event; a clean measurement between the two makes two labels**: the rejection that follows is the end of the passage. [cross Obstruction]\n368\t- **Two nuisance episodes separated by a few hours where targets stay shifted make only one**: the shifted targets are still touched. [NORDEND]\n369\t- **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]\n370\t- **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]\n371\t- **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]\n372\t- **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]\n373\t- **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]\n374\t\n375\t## 4. The family\n376\t\n377\t- **A single family per label, its key in `families.md`, following its boundaries**: `Visibility`, `Obstruction`, `Thermal displacement`, `Displacement`, `Target issue`, `No data`; no other key, nor old names. [instruction, MICHIGAN, WILDSTRUBEL]\n378\t- **We decide by the signature, not by coincidence**: a temperature drop at the same moment does not make a thermal, an `error_value` that moves a little does not make a Visibility. [cross Thermal displacement, cross Visibility]\n379\t- **A same target keeps the same family from one batch to the next, and a same phenomenon on neighboring stations the same family**: otherwise the defect of a target or a site reads as two causes. [NORDEND, consistency]\n380\t- **The sun at sunrise in the field and the lit background behind a spot are the same nuisance**: same family, same way of stating the cause. [cross Visibility]\n381\t\n382\t## 5. The description\n383\t\n384\t- **As the expert would write it, in English: what is seen, the cause and how it was known, the conclusion for the client**: which targets or references with their exact names, which magnitudes, the return or not; then nothing to do, data not to be believed, or movement to monitor. [instruction]\n385\t- **Qualitative, without numeric values, even in words**: \"a tenth\", \"half a pixel\", \"a few hundredths\", \"up to almost 1\" are numbers; say \"a little\", \"clearly\", \"strongly\". [instruction, FLORIDA, JUNGFRAU]\n386\t- **The targets named are those that move the most, read instant by instant, in the right column**: not the usual list; a rejected target does not \"jump\"; the direction is stated as it is that day. [instruction, CLARIDEN, NEBRASKA, FLORIDA, NIEDERHORN]\n387\t- **A sentence taken from a model is reread on the range of each label**: the hours, the weather, the targets, the image, the return, the overshoot; a precision true for a single label is not copied. [cross Visibility, cross Thermal displacement, SNCF01, LENZSPITZE, NORDEND, FLORIDA]\n388\t- **\"Nothing on the images\", \"image without obstacle\" are written only after looking at the image of the hour**: a passage is often seen in transparency; the image cited is that of the day when it exists. [instruction, CLARIDEN, MICHIGAN, FLORIDA, WILDSTRUBEL, cross Visibility, JUNGFRAU]\n389\t- **\"No image\" is written only at an instant when the camera usually takes an image, and after searching for the file**: a station that takes one only on the hour proves nothing at the half hour, and the hourly images often fall on the minute of the measurements. [cross No data, LENZSPITZE]\n390\t- **A fact given by the expert is written \"according to the expert\", in words, without his numbers**: not \"the map knows\". [instruction, BREITHORN, MICHIGAN, NIEDERHORN]\n391\t- **The temperature is \"the housing temperature\" (of the camera)**: the column being either `sensor_*_deg_c`, or, failing that, `temperature_deg_c`; never of the air, the building, the plant, the station, the components, the camera alone, nor the name of the column; without any metric, \"no temperature is available\". [instruction, cross Thermal displacement, LENZSPITZE, NORDEND, JUNGFRAU, consistency]\n392\t- **The weather is not drawn from the housing temperature**: \"cold and overcast day\" is seen on the images. [FLORIDA]\n393\t- **The moments of the day (morning, late afternoon, night) are judged on the images, never on the UTC hour**: the station can be anywhere. Every hour written is in UTC, no numeric local hour. [cross Visibility, label map, expert's reading rule]\n394\t- **A level \"back\" or \"a little below\" is compared over several days**: a single day after may be in the middle of a thermal cycle; a night level that changes from one night to another is compared with several nights; a target rejected at night, with the nearest neighboring night where it is measured, never across a step. [instruction, MICHIGAN, cross Visibility, WILDSTRUBEL, finishing niederhorn]\n395\t- **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]\n396\t- **\"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]\n397\t- **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]\n398\t- **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]\n399\t- **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]\n400\t- **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]\n401\t- **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]\n402\t- **A lasting jump states its step**: its duration, its return or not. [cross Displacement]\n403\t- **Each label of a sequence (outward, return, resumption) names the other**: \"return of the drift of…, labeled apart\", \"without return until the end of the batch\". [cross Displacement]\n404\t- **A Target issue says when the rejections stop before the end of the label**: the end is read on the curves, the rejections may stop before. [cross Target issue]\n405\t- **A No data states the metrics and the image of the instant**: present or not, checked, for each gap. [NIEDERHORN, cross No data]\n406\t\n407\t- **On a recent camera (image quality filled, `tools/scripts/quality.py`), an occultation is written only after reading the flux of the instant**: a cut flux proves it, a full flux denies it; the hidden targets are named from their flux, each time, and a hidden target that stayed under its threshold is stated (its point stays, wrong). The metrics: `tools/DATA.md`. [LENZSPITZE quality review, D-129]\n408\t- **\"Bigger spots\" is written only after comparison with a calm day of the same image regime and reading of the `fwhm`**: a spot that has lost its light can look swollen. [LENZSPITZE quality review, D-129]\n409\t- **A jump without rejection is in no list of rejections**: on a recent camera, `quality.py --labels --outside` gives the degraded instants outside the labels; `corr` is checked at each. [LENZSPITZE quality review, D-129]\n410\t\n411\t## 6. The stated cause\n412\t\n413\t- **A cause is stated in three ways only: seen, deduced, not established**: \"seen on the image (or the thumbnail) of HH:MM\", saying what is seen there; \"deduced from…\" (the signature, the other passages seen, the curves and the camera pose), saying why it is not seen; \"not established\", with its hypotheses; or \"according to the expert\". [instruction, cross Obstruction, cross Displacement]\n414\t- **A cause deduced from a known signature is stated \"deduced\", not \"not established\" followed by hypotheses**: the signature is a proof. [cross Visibility]\n415\t- **\"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]\n416\t- **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]\n417\t- **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]\n418\t- **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]\n419\t- **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]\n420\t\n421\tThe boundaries between families, and what is not labeled: `families.md`.\n422\tlog.jsonl\n423\tsession\n424\t"}]},"parent_tool_use_id":null,"session_id":"4d470fcf-4228-4dc5-8c0d-b90f8d37cbb1","uuid":"fb202600-a075-4ae4-821f-78f7f7ed02cb","timestamp":"2026-11-17T20:31:08.807Z","tool_use_result":{"type":"text","file":{"filePath":"/home/maxime/.claude/projects/-home-maxime-aimsight-app/4d470fcf-4228-4dc5-8c0d-b90f8d37cbb1/tool-results/bejht3h5f.txt","content":"# Reading the data\n\nThe guide to the reading harness: followed by the analyst; improved by the upgrader (agents repository), run by Optimizer's `optimize` skill, the only one that writes here.\n\nA camera tracks targets (reflectors) fixed on a structure; its own movement is compensated thanks to reference targets, assumed fixed. This movement, the **camera pose** (`pan`, `tilt`, `rotation` in degrees, `scale`, `sigma0` of the registration, in `camera/`), is read before the sensors: it explains a large part of what moves on the curves (D-073). This guide says how to read a station's data: what the curves and the images show, moment by moment. It does not say what they mean: family, known event, hypothesis and verdict are the business of whoever calls you.\n\n## Read first\n\n- `tools/DATA.md`: the files of a station and the meaning of each column, the image quality metrics, the camera images (**first**);\n- `labeling/reading-rules.md`: what the data mean (the measurement chain, gaps, reading rules, false friends).\n\n## The tools\n\nRun them from the root of the calling repository, where `tools/`, `data/` and `labeling/` are links. They return values, never verdicts: you judge. `--out