13 lines
16 KiB
JSON
13 lines
16 KiB
JSON
{"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"}
|
|
{"id": "MICHIGAN-19", "start": "2026-10-08T00:00Z", "end": "2026-10-12T16:00Z", "family": "Displacement", "description": "From 8 to 12 October, the camera gradually nods forward: its tilt rises, its pan and its rotation decrease, and all the targets slide together in the image, shrinking slightly, without moving relative to each other. Until 9 October, on three references, the compensation absorbs most of this movement, but not all: from the 04:00 measurement on 8 October, when the camera takes a clearer step forward, the corr_x of COLH18', POUH18', POUH19N', COLH21', COLH19N' and COLH18S''' rises a little and stays up, the corr_y of POUH19N' goes down a little, and the corrections of the references REF42 and REFG43N move apart. Since the loss of REFPOU22 on 9 October at 12:00 (separate label, which also covers the jump of that measurement), the compensation runs on REF42 and REFG43N alone, which do not follow this movement as the targets do (the scale computed on them even rises): the corr_x of all the targets rises slowly and clearly until the end of the range, under the back-and-forth agitation of the two-reference compensation. Its stop and slight return from the evening of 12 October are labelled apart. Deduced from the curves, the camera pose and the raw positions of the targets; nothing on the images. 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, and restoring a third reference will make the curves reliable again.", "analysis": "MICHIGAN_2026-10-03T0000_2026-10-12T1600"}
|
|
{"id": "MICHIGAN-6", "start": "2026-10-15T20:00Z", "end": "2026-10-16T12:00Z", "family": "No data", "description": "No measurement for any sensor in the night of 15 to 16 October: three measurements are missing, all the curves are cut, then everything resumes at the same level. The station metrics are also missing over these hours (temperatures, voltage, synchronization); the voltage is normal just before and just after, the battery full: no sign of a power cut. The same gap affects the two other stations of the building (BREITHORN, 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": "MICHIGAN_2026-10-12T1600_2026-10-23T2000"}
|
|
{"id": "MICHIGAN-8", "start": "2026-10-17T12:00Z", "end": "2026-10-18T08:00Z", "family": "Displacement", "description": "All the targets become agitated together for three measurements: the corr_x goes down at 16:00 on 17 October, the corr_y plunges at 20:00, then corr_x and corr_y rise above their level on 18 October at 04:00, and everything returns. The camera pose computed on REF42 and REFG43N swings back and forth (tilt, rotation) without the raw positions of the targets moving clearly, and the gap between the two references changes a little: it is the two-reference compensation that carries this gap over to all the targets. The temperatures then drop in steps, but without a brief variation at the time of these deviations. Cause not established, nothing on the images. For the customer: this is not a movement of the structure, the points of this range are to be ignored.", "review": "2026-11-17", "analysis": "MICHIGAN_2026-10-12T1600_2026-10-23T2000"}
|
|
{"id": "MICHIGAN-9", "start": "2026-10-19T00:00Z", "end": "2026-10-19T12:00Z", "family": "Thermal displacement", "description": "On 19 October in the morning, the corr_y of all the targets plunges together for two measurements, the corr_x too at the second, then everything returns at noon. The camera housing temperature makes a brief drop at the same moment, at the end of the night, and the camera moves: it nods forward, rotates, its scale drops, the raw positions of all the targets and of the two references slide almost together; the targets do not move relative to each other. The compensation on two references only, REF42 and REFG43N, carries their small gap relative to the targets over to all the targets. The first affected measurement slightly precedes the temperature drop. Cause deduced from the curves and the camera housing temperature; nothing in front of the targets on the 08:00 image. For the customer: this is not a movement of the structure, nothing to do.", "review": "2026-11-17", "analysis": "MICHIGAN_2026-10-12T1600_2026-10-23T2000"}
|
|
{"id": "MICHIGAN-11", "start": "2026-10-25T16:00Z", "end": "2026-10-26T16:00Z", "family": "Thermal displacement", "description": "The corr_y of all the targets goes down together from the evening of 25 October until the morning of the 26th, the corr_x goes down in turn on the morning of the 26th, then everything returns in the afternoon. The camera housing temperature drops at the same moment and rises again on the afternoon of the 26th; the camera nods forward, its scale drops, the raw positions of all the targets and of the two references slide almost together, the targets do not move relative to each other. The compensation on REF42 and REFG43N alone carries their small gap relative to the targets over to all the targets. Cause deduced from the curves and the camera housing temperature; nothing in front of the targets on the 04:00 image on the 26th. For the customer: this is not a movement of the structure, nothing to do.", "review": "2026-11-17", "analysis": "MICHIGAN_2026-10-23T2000_2026-11-01T0000"}
|
|
{"id": "MICHIGAN-13", "start": "2026-10-28T00:00Z", "end": "2026-10-28T16:00Z", "family": "Thermal displacement", "description": "On 28 October in the morning, the corr_x of all the targets goes down a little at 04:00 and plunges at 08:00, the corr_y too, then the corr_x returns at noon and the corr_y at the next measurement. The camera housing temperature drops sharply at the same moment, at the end of the night, and rises again in late morning; the camera nods forward, its scale drops, the raw positions of all the targets and of the two references slide almost together, the targets do not move relative to each other. The compensation on REF42 and REFG43N alone carries their small gap relative to the targets over to all the targets. Cause deduced from the curves and the camera housing temperature; nothing in front of the targets on the 08:00 image. For the customer: this is not a movement of the structure, nothing to do; the point is to be ignored.", "review": "2026-11-17", "analysis": "MICHIGAN_2026-10-23T2000_2026-11-01T0000"}
|
|
{"id": "MICHIGAN-14", "start": "2026-10-28T16:00Z", "end": "2026-10-29T16:00Z", "family": "Thermal displacement", "description": "From the evening of 28 October to the morning of 29 October, the corr_x of all the targets goes down clearly, together, with the corr_y, then rises all at once at the noon measurement, but stays clearly under its previous level, and does not regain it until the end of the month; the corr_y, partly returned at noon, only returns at the next measurement. The camera housing temperature makes the strongest drop of the month at the same time and rises all at once in late morning of the 29th; the camera nods forward clearly and its scale drops, the raw positions of all the targets slide together, without moving relative to each other, and REFG43N moves slightly away from their movement; the error_value of a few targets rises, far from the threshold. The compensation on REF42 and REFG43N alone carries over and amplifies this gap on all the targets. Cause deduced from the curves and the camera housing temperature; nothing in front of the targets on the 08:00 image. For the customer: this is not a movement of the structure, nothing to do; the curves of this range are not to be trusted.", "review": "2026-11-17", "analysis": "MICHIGAN_2026-10-23T2000_2026-11-01T0000"}
|
|
{"id": "MICHIGAN-15", "start": "2026-10-29T16:00Z", "end": "2026-10-30T12:00Z", "family": "Thermal displacement", "description": "From the evening of 29 October to the morning of 30 October, the corr_y of all the targets already goes down a little at 20:00, then the corr_x goes back down clearly, together, with the corr_y touching its lowest in late morning, then everything rises again at noon. As the day before, the camera housing temperature drops at the same moment and rises again on the morning of the 30th; the camera nods forward and its scale drops, the raw positions of all the targets slide together, without moving relative to each other, and REFG43N moves slightly away from their movement; the error_value of a few targets rises, far from the threshold. The compensation on REF42 and REFG43N alone carries over and amplifies this gap on all the targets. Cause deduced from the curves and the camera housing temperature; nothing in front of the targets on the 04:00 image. For the customer: this is not a movement of the structure, nothing to do; the curves of this range are not to be trusted.", "review": "2026-11-17", "analysis": "MICHIGAN_2026-10-23T2000_2026-11-01T0000"}
|