This commit is contained in:
maxime committed 2026-11-18 10:51:31 +01:00
1 parent 8e4ebca342
commit 58b630f2d5
112 files changed
+3172 -295

No files matched your search

+1
View File
@@ -4,6 +4,7 @@
"allow": [
"Bash(python3 scripts/validate.py:*)",
"Bash(python3 scripts/ids.py:*)",
"Bash(python3 scripts/cases.py:*)",
"Bash(python3 scripts/precedents.py:*)",
"Bash(docker start ollama-bge-m3)"
],
+58
View File
@@ -0,0 +1,58 @@
---
name: cases
description: Builds or refreshes the cases of auto/cases/ (the phenomena, false friends and lessons, one JSON file each) from the labels of auto/ and, on the first run, from the phenomena, false friends and lessons of families.md and reading-rules.md. Use when the user asks to build, refresh or update the cases (/cases).
---
# The cases
A case generalizes labels: the signature of a phenomenon, how to confirm it, how to tell it from its neighbours, what the client is told. The agents read the cases through `python3 scripts/cases.py` (search, `--list`); the labels themselves are no longer searched. The design, binding: `docs/superpowers/specs/2026-11-18-cases-design.md` (sections "A case" and "The skill").
## Rules
- Never read nor write `manual/` (the user's alone). Touch only `auto/cases/`, and, at the seed, the three markdown sections below; aimsight-app writes in `auto/` at the same time.
- Never write `review`, never commit. Remove `review` from a case only when you change its `kind`, `family`, `name`, `signature`, `checks`, a `tell_apart` or `client`; adding a source or a neighbour link keeps it.
- A case is general: English, words without numeric values, no station or target name in its text (where it was seen is in `sources`). A case `id` is a short English slug, equal to its file name, and never changes.
- Never delete a case that has a non-label source (`user`, `expert`, `client report`): hand-written knowledge leaves only by the user's hand.
- A new case needs labels from at least two stations (the station of a label is its id before the last `-`), or a non-label source.
## Read first
The design (sections above), `families.md` and `reading-rules.md` in full, and `python3 scripts/cases.py --list`.
## Seed: when `--list` prints no case
1. One case per bullet of:
- `families.md`, section "The phenomena": `kind` `phenomenon`; `family` the key of its `###` heading, `null` under "Family of the cause";
- `reading-rules.md` §6 "False friends": `kind` `false friend`; `family` `null` unless the bullet is about one family;
- `reading-rules.md` §8 "Lessons from cases outside the labels": `kind` `lesson`.
2. Fields: `sources` = `user` plus its bracketed sources (`[NORDEND-169]` → `NORDEND-169`, `[expert]` → `expert`, `[client report]` → `client report`), dropping a label id that `auto/` no longer has; `name` the bullet's bold name; `signature` the bullet's text, reworded only to say what is seen (move a station name of the text to `sources` if it is a label, otherwise make it general); `neighbours` the entries the bullet says how to tell apart, linked both ways with the same `tell_apart`; `checks` only when the bullet names a tool or a column; `client` only when the bullet says what the client is told and it differs from the family's line; no `review`. Write each to `auto/cases/<id>.json`, indented by two spaces.
3. Replace the body of each of the three sections (keep its heading) by one paragraph:
- phenomena: "They are the cases: `auto/cases/` (`kind` phenomenon), listed by `python3 scripts/cases.py --list`, searched by `python3 scripts/cases.py "<what you see>"`. A phenomenon not among them is labelled too, without forcing a cause."
- false friends: "They are the cases: `auto/cases/` (`kind` false friend), listed by `python3 scripts/cases.py --list`, searched by `python3 scripts/cases.py "<what you see>"`."
- lessons: the same with `kind` lesson.
4. `python3 scripts/validate.py` until it says 0 errors for the cases; `python3 scripts/cases.py --index`.
5. Report the cases written (`--list`) and every bullet that did not become its own case (merged, and into which), then **stop**: the pass over the labels is the next `/cases`, once the user has read the seed.
## Refresh: when cases exist
1. `python3 scripts/cases.py --pending .index/cases-work` clears the files of an earlier refresh there, writes one `<family>.jsonl` per family with labels to read, and prints the counts and the label ids deleted since the last record.
2. **One subagent per family file**, all in one message (Agent tool, `general-purpose`), each with this prompt, its `<slug>` filled in:
> You attach AIMsight displacement labels to cases. Work in `/home/maxime/aimsight-labeling`. Never read `manual/`. Read in full `families.md` and `reading-rules.md`; run `python3 scripts/cases.py --list` (every case); read the case files `auto/cases/*.json` of family `<family>` and those whose `family` is `null`, and any other case the list makes relevant. Then read every label of `.index/cases-work/<slug>.jsonl`.
> For each label, say which cases it illustrates: existing ids, ids of cases you propose, or none. A label may illustrate several cases (rain that also makes the references switch; a false friend it shows).
> Propose a new case only for a pattern no case covers, general (English, words without numbers, no station or target name), with the labels that show it; give it `id` (short English slug), `kind` (`phenomenon`, `false friend`, `lesson`), `name`, `family` (a key of `families.md` or null), `signature` (what is seen: what moves, what does not), `checks` (the reading tools or images that confirm it), `neighbours` (existing or proposed case ids, each with `tell_apart`), and `client` only if it differs from the family's line.
> Propose a change to an existing case (a sharper signature, a check, a neighbour, a client line) only with the labels that justify it.
> A pattern you see at one station only goes to `single_station`, not to a new case.
> Write only this JSON to `.index/cases-work/<slug>.answer.json`:
> `{"assignments": {"<label id>": ["<case id>"]}, "new_cases": [{"id": "", "kind": "", "name": "", "family": null, "signature": "", "checks": [], "neighbours": [{"case": "", "tell_apart": ""}], "client": "", "labels": ["<label id>"]}], "changes": [{"case": "<case id>", "field": "signature | checks | neighbours | client | name", "value": "", "labels": ["<label id>"]}], "single_station": [{"pattern": "", "labels": ["<label id>"]}]}`
> Every label of the file appears in `assignments`. Answer in one line: the number of labels, of new cases, of changes.
3. **Guard and merge** (you, from the answer files of the families `--pending` just wrote):
- drop a new case whose `labels` span fewer than two stations: remove it from those labels' `assignments`, and add its pattern to the `stations.md` suggestions;
- merge new cases that two subagents proposed for the same thing (one id, the union of their labels; rewrite the assignments to that id);
- write each new case to `auto/cases/<id>.json` with `sources` = its labels, without `labels` and without `review`;
- link neighbours both ways (the reverse link reuses the `tell_apart`); a neighbour id that does not exist is dropped;
- apply `changes` (several on the same field: write one text that holds them), removing `review` as the rules say.
4. **Record**: merge the `assignments` of those answers into `.index/cases-work/assignments.json` as `{"assignments": {...}}`, then `python3 scripts/cases.py --record .index/cases-work/assignments.json`.
5. **Check**: `python3 scripts/validate.py cases` until 0 errors (fix the cases, never the labels); `python3 scripts/cases.py --index`.
6. **Report**, in the chat: the cases added; the cases whose text changed (their `review` removed: to validate again by editing the JSON); the cases that only gained sources; the cases deleted; the labels left without a case (`--pending` run again lists them); the `stations.md` suggestions (the user writes `stations.md` by hand); the `skipped` labels of the record.
+5 -5
View File
@@ -2,14 +2,14 @@
labeling: the AIMsight displacement labels and the knowledge to place them, in a single copy on the workstation (`README.md`). aimsight-app reads and writes there, Optimizer only reads, both through a link `labeling -> ~/aimsight-labeling`; the support agent writes its folders in `auto/support/`; commits are made here.
- **The labels**: `manual/<STATION>.jsonl` (the expert, for him alone), `auto/<STATION>.jsonl` (the agents; `review` = the date the user validated the label in aimsight-app, nothing else writes it), one per line, `{"id", "start", "end", "family", "description", ...}`. The aimsight-app analyses: `auto/analyses/<STATION>_<start>_<end>/`. The support agent's folders: `auto/support/<YYYY-MM-DD>_<subject>/`.
- **The knowledge**, one source per kind (`README.md`), maintained by hand: `families.md` (the families, their boundaries, the catalogue of phenomena), `labeling-rules.md` (bounds, a single event, description, stated cause), `reading-rules.md` (what the data mean), `stations.md` (the installations); the cases are the labels, through `precedents.py`; what the data are: `tools/DATA.md`. A piece of knowledge lives in one of them only.
- **The tools**, standard library: `python3 scripts/validate.py [STATION | file.jsonl]` (the rules), `python3 scripts/ids.py [STATION]` (the stable id of new labels), `python3 scripts/client.py` (what the client is told of a detectors' event, from `families.md`; its check), `python3 scripts/precedents.py "<text>" [--exclude STATION START END] [--family F] [--k N]` (the RAG; it starts the Ollama container `ollama-bge-m3` by itself if it does not answer; `--check` without it).
- **The labels**: `manual/<STATION>.jsonl` (the expert, for him alone), `auto/<STATION>.jsonl` (the agents; `review` = the date the user validated the label in aimsight-app, nothing else writes it), one per line, `{"id", "start", "end", "family", "description", ...}`. The aimsight-app analyses: `auto/analyses/<STATION>_<start>_<end>/`. The support agent's folders: `auto/support/<YYYY-MM-DD>_<subject>/`. The cases: `auto/cases/<id>.json`, built by the `cases` skill (`/cases`) from the labels; `review` there is written by the user in the JSON.
- **The knowledge**, one source per kind (`README.md`), maintained by hand: `families.md` (the families, their boundaries), `labeling-rules.md` (bounds, a single event, description, stated cause), `reading-rules.md` (what the data mean), `stations.md` (the installations); the phenomena, false friends and lessons are the cases, `auto/cases/`, through `cases.py`; the labels themselves through `precedents.py`; what the data are: `tools/DATA.md`. A piece of knowledge lives in one of them only.
- **The tools**, standard library: `python3 scripts/validate.py [STATION | file.jsonl | cases]` (the rules), `python3 scripts/ids.py [STATION]` (the stable id of new labels), `python3 scripts/client.py` (what the client is told of a detectors' event, from `families.md`; its check), `python3 scripts/cases.py "<text>" [--family F] [--k N]` (the RAG of the cases; it starts the Ollama container `ollama-bge-m3` by itself if it does not answer; `--list` and `--check` without it), `python3 scripts/precedents.py "<text>" [--exclude STATION START END] [--family F] [--k N]` (the RAG of the labels; `--check` without Ollama).
- **For aimsight-app**, which calls them and holds no rule of its own: `validate.check(label, proposed)` (the rules of one label, before it is written in `auto/`), `ids.assign`, `client.message` and `client.action` (the "For the client" columns of `families.md`, per family and per variety). A rename here needs the change there.
- **Verify**: `python3 scripts/validate.py` (0 errors expected) and `python3 scripts/precedents.py --check`.
- **Verify**: `python3 scripts/validate.py` (0 errors expected), `python3 scripts/validate.py --check`, `python3 scripts/cases.py --check` and `python3 scripts/precedents.py --check`.
Rules:
- **`manual/` is the expert's, for him alone**: no agent and no process reads or writes there; the whole project (analyst, precedents, benchmark, optimization) uses only `auto/`.
- **`manual/` is the expert's, for him alone**: no agent and no process reads or writes there; the whole project (analyst, cases, precedents, benchmark, optimization) uses only `auto/`.
- A label added to `auto/` goes through `ids.py` then `validate.py`; an id never changes.
- Every time is in UTC; descriptions in words, without numeric values; written in English from now on.
- No rule specific to a station, a target or a date in the rules and the families.
+9 -6
View File
@@ -5,18 +5,21 @@ The AIMsight displacement labels and all the domain knowledge to place them, in
- `manual/<STATION>.jsonl`: the expert's labels, for him alone: no process and no agent uses them; `auto/<STATION>.jsonl`: those of the Support-Agent `etiqueteur` and those submitted by the aimsight-app `analyst`; `review` is the date the user validated a label in aimsight-app (quality over quantity: only the analyses discussed and validated there), and any change removes it; the agents' reviews of 2026-11-04 and 2026-11-05 were removed on 2026-11-17 (in the history); one label per line, `{"id", "start", "end", "family", "description", ...}`, UTC times, `family` = the family.
- `auto/analyses/<STATION>_<start>_<end>/`: the analyses launched from the Data page of aimsight-app (`work/` outside git).
- `auto/support/<YYYY-MM-DD>_<subject>/`: the folders of the `support` agent (agents repository): the request, the answer, the analyst's work when it was called (`work/` outside git).
- The knowledge, one source per kind, maintained by hand by the user; the analyst reads the four files in full:
- `auto/cases/<id>.json`: the cases, the phenomena, false friends and lessons drawn from the labels, one JSON file each (`docs/superpowers/specs/2026-11-18-cases-design.md`); built and refreshed by the `cases` skill (`/cases`, `.claude/skills/cases/`), which never writes `review` nor commits; `review` is the date the user validated a case, written by the user in its JSON, removed by the skill when it changes the case's text; `auto/cases/.read.json`, the skill's state (which case each label went to).
- The knowledge, one source per kind, maintained by hand by the user, but for the cases; the analyst reads the four files in full and searches the cases:
| Kind of knowledge | Source |
|---|---|
| The cases | the labels of `auto/`, through `precedents.py` |
| The families, their boundaries, the catalogue of phenomena | `families.md` |
| The cases: phenomena, false friends, lessons | `auto/cases/`, through `cases.py` |
| The labels themselves, as precedents | `auto/<STATION>.jsonl`, through `precedents.py` |
| The families and their boundaries | `families.md` |
| How to place a label | `labeling-rules.md` |
| What the data mean: measurement chain, gaps, reading rules, false friends | `reading-rules.md` |
| What the data mean: measurement chain, gaps, reading rules | `reading-rules.md` |
| The installation of each station | `stations.md` |
| What the data are: files, columns, image quality, images | `tools/DATA.md` (tools repository) |
- `scripts/`: `validate.py` (the labels against the rules; `check` for one label), `ids.py` (the stable id of each), `client.py` (what the client is told of a detectors' event).
- `scripts/precedents.py`: the RAG of the labels. The labels of `auto/` closest in meaning to a text, with their provenance (validated by the user or not); `--exclude STATION START END` leaves out the analyzed range. bge-m3 model of the Ollama container `ollama-bge-m3` (started by the script itself if it does not answer; port 11435); the `.index/` index, outside git, updates itself at every call (only new or modified labels go through the model; ~8 min to redo everything on CPU).
- `scripts/`: `validate.py` (the labels and the cases against the rules; `check` for one label), `ids.py` (the stable id of each), `client.py` (what the client is told of a detectors' event).
- `scripts/cases.py`: the RAG of the cases. The cases closest in meaning to a text, each in full with its provenance (validated by the user or not) and its label sources dated; `--list` every case, one line each, without Ollama; `--pending` and `--record`, the bookkeeping of a refresh by the skill. bge-m3 model of the Ollama container `ollama-bge-m3` (started by the script itself if it does not answer; port 11435); the `.index/` index, outside git, updates itself at every call (only new or modified cases go through the model). The labels also feed the cases.
- `scripts/precedents.py`: the RAG of the labels. The labels of `auto/` closest in meaning to a text, with their provenance (validated by the user or not); `--exclude STATION START END` leaves out the analyzed range; its own index in `.index/`. An agent uses it, the case search, or both.
aimsight-app and Optimizer reach it through a link `labeling -> ~/aimsight-labeling`, ignored by git: aimsight-app reads and writes there (labels, analyses), Optimizer only reads; commits are made here. The scripts run from here (`python3 scripts/validate.py`) or through the link (`python3 labeling/scripts/validate.py`). Descriptions are written in English from now on.
+10
View File
@@ -0,0 +1,10 @@
{"id": "ALASKA-1", "start": "2026-11-05T02:45Z", "end": "2026-11-05T05:00Z", "family": "Perturbation", "description": "At night, the corr_y of almost all the targets jumps upward together for one measurement at 03:00, then again a little at 04:45 (05, 04, 03, 02, 08, 09 the most), and comes back at the next measurement each time. In the raw image the targets do not move against each other (rigid fit on the targets), while the reference ref_av_02 shifts slightly alone against them, its error_value at its level; the reference ref_av_01 is seen a little less well (error_value up, far from its threshold). The station runs its compensation on these two references only: their small relative shift passes into all the targets. Zone image of 03:00: night without obstacle, spots of the targets and of both references sharp. Cause of the reference shift not established. It is not a movement of the structure: points to ignore.", "review": "2026-11-18", "analysis": "ALASKA_2026-11-04T2358_2026-11-16T1217"}
{"id": "ALASKA-2", "start": "2026-11-05T08:45Z", "end": "2026-11-05T09:15Z", "family": "Perturbation", "description": "In the morning, for one measurement, the corr_y of the far target 10 jumps strongly upward, those of its neighbours 11 and 09 clearly, then all come back at the next measurement; their corr_x and that of 08 move a little. Their error_value rises at that measurement, those of 08 too, the other targets and the two references stay at their level; in the raw image only 10, and a little 11 and 09, move against the other prisms: these targets move alone in the image, the camera and the base do not. On the image of 09:00 nothing is seen in front of these four close-set spots at the end of the row of piers. Cause not established, probably a brief passage in front of the far targets (a bird) not caught on the image. Jump then return: points to ignore.", "review": "2026-11-18", "analysis": "ALASKA_2026-11-04T2358_2026-11-16T1217"}
{"id": "ALASKA-3", "start": "2026-11-05T23:45Z", "end": "2026-11-06T07:30Z", "family": "Perturbation", "description": "Agitation of the corrected curves during the night: all the targets jump together for one measurement at a time, in corr_x at midnight and at 00:45 (06, 07, 08, 11, 05 the most), then in corr_y at 03:45 (the near targets 01 to 05) and at 07:15 (the far targets 05 to 11), each time coming back at the next measurement. In the raw image the targets do not move against each other; the references ref_av_01 and ref_av_02 shift slightly against them in turn, without their error_value rising: the compensation, on these two references only, passes their difference into all the targets. Zone image of midnight: night without obstacle, spots sharp. Humid, calm night. Cause of the reference shifts not established. It is not a movement of the structure: points to ignore.", "review": "2026-11-18", "analysis": "ALASKA_2026-11-04T2358_2026-11-16T1217"}
{"id": "ALASKA-4", "start": "2026-11-05T23:45Z", "end": "2026-11-08T10:00Z", "family": "Thermal displacement", "description": "Target 04 alone sits higher in corr_x during the cold spell, strongly on the nights and mornings of 6 to 8 November, most on the night of 7 to 8 November, the coldest; the other targets do not follow. In the raw image 04 shifts sideways against all the other prisms (rigid fit on the targets): at its cold position at night, it moves back during the warmer hours, and returns for good to its warm position on 8 November in the morning when the housing temperature rises again, where it stays during the mild days that follow; on the next cold spell it does the same again. Its error_value stays at its level and the thumbnails of 7 November at 23:00 and 8 November at 05:00 show its spot sharp, nothing in front. Movement of target 04, or of its support, with the temperature, back at equal temperature: nothing to do.", "review": "2026-11-18", "analysis": "ALASKA_2026-11-04T2358_2026-11-16T1217"}
{"id": "ALASKA-5", "start": "2026-11-07T04:45Z", "end": "2026-11-07T10:45Z", "family": "Perturbation", "description": "At the end of the night and in the morning, the corr_y of all the targets jumps upward together for one measurement at 05:00 and at 06:30, then corr_x and corr_y together at 10:00 (05, 07, 08, 10 the most), each time back at the next measurement; at 09:30 and 10:30 a few targets still jump. In the raw image the targets do not move against each other; the references ref_av_01 and ref_av_02 shift slightly against them, their error_value at its level: the compensation, on these two references only, carries their difference into all the targets. Zone image of 05:00: night without obstacle; of 10:00: clear sunny morning, spots sharp. The neighbouring camera WYOMING, which looks at the same piers, shows a jump of its far references at 05:00. Cause not established. It is not a movement of the structure: points to ignore.", "review": "2026-11-18", "analysis": "ALASKA_2026-11-04T2358_2026-11-16T1217"}
{"id": "ALASKA-6", "start": "2026-11-07T22:45Z", "end": "2026-11-08T09:00Z", "family": "Perturbation", "description": "Agitation of the corrected curves during the cold, humid night of 7 to 8 November and at dawn: all the targets jump together for one measurement at a time, in corr_y downward at 23:15 (the far targets 10, 11, 08 the most) and at 03:15, in corr_x at 23:45, 04:30, 05:30 and 06:45, then strongly upward in corr_y with corr_x down at 08:30 (06, 02, 04, 03 the most), each time back at the next measurement or the one after. In the raw image the targets do not move against each other; the references shift slightly against them, ref_av_02 in particular, and the error_value of ref_av_01 is up all night, of the near targets 01, 02, 06, 07 at dawn, far from their thresholds. The compensation runs on these two references only and passes their difference into all the targets. Zone images of 23:00, 03:00, 07:00 and 08:00: no obstacle, no veil visible, spots sharp. The neighbouring camera WYOMING has a sudden shift of its far prisms at dawn the same morning. Cause not established (the cold air above the river is possible). It is not a movement of the structure: points to ignore.", "review": "2026-11-18", "analysis": "ALASKA_2026-11-04T2358_2026-11-16T1217"}
{"id": "ALASKA-7", "start": "2026-11-10T08:15Z", "end": "2026-11-10T09:00Z", "family": "No data", "description": "Two measurements missing for all sensors in the morning. WYOMING misses the same two measurements, and CLARIDEN, LENZSPITZE and NADELHORN measurements at the same minutes: a common cause outside the station (transmission or reception of the data), not a station failure; it is not established. The station runs: the voltage is normal before and after, its synchronizations resume at the next measurement, the images of 08:00 and 09:00 exist (one image per hour). Nothing to do on the station.", "review": "2026-11-18", "analysis": "ALASKA_2026-11-04T2358_2026-11-16T1217"}
{"id": "ALASKA-8", "start": "2026-11-12T12:00Z", "end": "2026-11-13T00:00Z", "family": "Visibility", "description": "Rainy day: the error_value of the two references ref_av_01 and ref_av_02 rises strongly from late morning to the evening, far under their threshold, with that of most targets; nothing is rejected. The image of 13:00 is veiled and grainy, the spots haloed. The poorly seen references distort the compensation, which runs on them two only: at 12:30 the far targets jump upward, then at 12:45 and 13:00 the corr_y of all the targets plunges strongly together (02, 04, 03, 02_g, 01 the most, the far targets clearly too, 01 and 06 in corr_x), and comes back at the next measurement; from 16:30 to 17:00 the near targets 04, 02_g, 02, 03, 01 dip again in corr_y, their own spots poorly seen, and a few targets still jump once at 23:15 and 23:45. Rain seen on the image of 13:00 and measured all day at Genève-Cointrin. Do not trust the curves over the range; it is not a movement.", "review": "2026-11-18", "analysis": "ALASKA_2026-11-04T2358_2026-11-16T1217"}
{"id": "ALASKA-9", "start": "2026-11-13T19:15Z", "end": "2026-11-15T10:00Z", "family": "Perturbation", "description": "During the cold days of 13 to 15 November, the corr_y of all the targets rises slowly together, of the same order in mm on all the targets, and stays high until the morning of the 15th (04 the most, then 02, 05, 06, 03), coming back during the day of the 15th; on top of it, the targets jump together for one measurement at a time, in corr_x upward at 17:30 on the 14th, both columns at 21:00 (the far target 11 strongly in corr_x), then in corr_y at 22:15 (01, 02, 03, 05 the most) and repeatedly through the night of 14 to 15 November, until 06:30. In the raw image the targets do not move against each other: it is the reference ref_av_02 that slides upward against them and jitters, ref_av_01 too at 21:00, their error_value at its level or barely up; the compensation, on these two references only, carries this into all the targets: the base changes. The night images show no obstacle in front of the spots; from 23:00 the night background is brighter and objects lit by the infrared light pass very close to the lens at 03:00 and 04:00, while rain is measured at Genève-Cointrin from 22:00. Cause of the reference slide not established. It is not a movement of the structure: points to ignore.", "review": "2026-11-18", "analysis": "ALASKA_2026-11-04T2358_2026-11-16T1217"}
{"id": "ALASKA-10", "start": "2026-11-14T03:00Z", "end": "2026-11-15T09:30Z", "family": "Thermal displacement", "description": "Target 04 alone sits higher in corr_x again during the cold spell of 14 and 15 November, as on 6 to 8 November: beyond its noise at night and in the morning, most on the morning of the 15th; the other targets do not follow. In the raw image 04 is back at its cold position against the other prisms (rigid fit on the targets) and returns to its warm position on the 15th around midday when the housing temperature rises clearly. Its error_value stays at its level and the thumbnails of 14 November at 05:00 and 15 November at 08:00 show its spot sharp, nothing in front. Movement of target 04, or of its support, with the temperature, back at equal temperature: nothing to do.", "review": "2026-11-18", "analysis": "ALASKA_2026-11-04T2358_2026-11-16T1217"}
+19 -19
View File
@@ -1,24 +1,24 @@
{"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"}
{"id": "BREITHORN-14", "start": "2026-10-19T00:00Z", "end": "2026-10-19T12:00Z", "family": "Thermal displacement", "description": "On 19 October in the morning, over two measurements, the camera rotation and scale suddenly deviate and its tilt takes a step; several targets deviate at the same time in opposite directions (COLH20 and the reference REFPOU22 upward in corr_y, COLI21 downward in corr_x and in corr_y), then return at noon. Nothing obstructs the view on the images, the error_value change little: this is the camera movement, incompletely compensated. It falls at the trough of the camera housing temperature, read in the metrics, and comes back when it rises: thermal effect on the camera, according to the expert: it is the housing temperature that matters, not the air temperature. Nothing to fear for the structure, nothing to do; do not trust these two points.", "review": "2026-11-17", "analysis": "BREITHORN_2026-10-13T0000_2026-10-22T1600"}
{"id": "BREITHORN-41", "start": "2026-10-21T16:00Z", "end": "2026-10-22T08:00Z", "family": "Obstruction", "description": "On the night of 21 to 22 October, COLI22, partly hidden, and POUI22 deviate clearly in corr_x and in corr_y, far beyond their ordinary noise, for three measurements, then return in the morning; COLI24, next to them, is rejected over the same measurements. On the 20:00 UTC image, the cab of a parked vehicle is in front of these bottom-left targets and the spot of COLI24 is no longer visible; the image of the morning is clear again. The references and the other targets hold. Seen on the image: a parked vehicle hides the targets. The structure does not move: ignore these targets over the range.", "analysis": "BREITHORN_2026-10-13T0000_2026-10-22T1600"}
{"id": "BREITHORN-32", "start": "2026-10-22T16:00Z", "end": "2026-10-23T08:00Z", "family": "Obstruction", "description": "On the night of 22 to 23 October, the curve of COLI24 is missing (measurements rejected); COLI22, partly hidden and kept under its threshold, goes down clearly in corr_y and in corr_x, and POUI22 deviates a little in corr_x and, at the first measurement of the night, in corr_y. Seen on the contrast-stretched thumbnails of 20:00 and 04:00 UTC: the dark outline of a vehicle, lights off, stands in front of the bottom left of the scene, where the cars of the other nights park; the spot of COLI24 is hidden and that of COLI22 reduced. The references and the other targets do not move. Everything comes back in the morning, the vehicle gone on the 08:00 image. The structure does not move: ignore these targets over the range.", "analysis": "BREITHORN_2026-10-22T1600_2026-11-01T0000"}
{"id": "BREITHORN-18", "start": "2026-10-23T16:00Z", "end": "2026-10-24T16:00Z", "family": "Obstruction", "description": "From the evening of 23 October to noon on 24 October, a car is parked in front of the bottom of the scene, seen on the images (grille and headlight, then headlights on). The curve of COLI24 is missing throughout; COLI22, first partly hidden, makes a very large jump in corr_x (its measured center slides over the visible part of its spot) and POUI22 jumps in corr_x, then COLI22, POUI22 and POUI24 are rejected on the morning of the 24th. The references hold. The structure does not move: ignore these targets over the range.", "review": "2026-11-17", "analysis": "BREITHORN_2026-10-22T1600_2026-11-01T0000"}
{"id": "BREITHORN-20", "start": "2026-10-25T20:00Z", "end": "2026-10-26T08:00Z", "family": "Obstruction", "description": "On the night of 25 to 26 October, an oblique structure, seen on the images in front of the bottom of the scene, hides the references REFH22 and REFPOU22, and COLH20''', COLI22 and POUI24 (measurements rejected, curves absent); POUI22, partly hidden, jumps in corr_x and in corr_y. The compensation only runs on two references: the basis changes, several targets (COLI20, POUI20, POUH21, COLJ19) shift a little in corr_x. Very bad sign for the measurement: data of the range not to be trusted; everything comes back in the morning.", "review": "2026-11-17", "analysis": "BREITHORN_2026-10-22T1600_2026-11-01T0000"}
{"id": "BREITHORN-33", "start": "2026-10-26T12:00Z", "end": "2026-10-26T20:00Z", "family": "Obstruction", "description": "On the evening of 26 October, a car with its headlights on, seen on the 16:00 UTC image, is parked in front of the bottom of the scene: the reference REFH22 is rejected and the compensation runs on three references; the curves of COLI24 and POUI24 are missing, and POUI22, partly hidden and kept under its threshold, makes a very large jump in corr_y and a jump in corr_x. COLI22 and COLH20 shift a little, through the change of references. The car is gone on the 20:00 image, where the oblique structure of the night takes over (labelled apart). The structure does not move: ignore these targets over the range.", "analysis": "BREITHORN_2026-10-22T1600_2026-11-01T0000"}
{"id": "BREITHORN-34", "start": "2026-10-26T16:00Z", "end": "2026-10-27T08:00Z", "family": "Obstruction", "description": "On the night of 26 to 27 October, an oblique structure, seen on the images of 20:00 and 00:00 UTC in front of the bottom of the scene, follows the car of the evening (labelled apart). At 20:00 it hides the reference REFH22, COLI24 and POUI22 (measurements rejected, curves absent) and POUI24, partly hidden, jumps strongly in corr_x; at 00:00 and 04:00 it hides the reference REFPOU22, COLH20''' and still POUI22. The compensation runs on three references: REFG44N and REFI'21 shift a little in corr_x, the targets hardly. Everything comes back in the morning, the view clear on the 08:00 image. Ignore these targets over the range; the structure does not move.", "analysis": "BREITHORN_2026-10-22T1600_2026-11-01T0000"}
{"id": "BREITHORN-24", "start": "2026-10-28T00:00Z", "end": "2026-10-28T12:00Z", "family": "Thermal displacement", "description": "On 28 October in the morning, over two measurements, the camera rotation and scale deviate then return at noon; at the same time, several targets deviate in opposite directions in corr_y (COLH20, COLI24, POUI22 and the reference REFPOU22 upward, POUI24 and the references REFG44N and REFI'21 downward), and return with the camera. Nothing obstructs the view on the images: this is the camera movement, incompletely compensated. It falls at the trough of the camera housing temperature, read in the metrics, and comes back when it rises: thermal effect on the camera, according to the expert: it is the housing temperature that matters, not the air temperature. Nothing to fear for the structure, nothing to do; do not trust these points.", "review": "2026-11-17", "analysis": "BREITHORN_2026-10-22T1600_2026-11-01T0000"}
{"id": "BREITHORN-35", "start": "2026-10-28T16:00Z", "end": "2026-10-29T16:00Z", "family": "Thermal displacement", "description": "From the evening of 28 October to noon on the 29th, the camera rotation and scale deviate again, for longer and more strongly, then return in the afternoon; several targets deviate with it in opposite directions in corr_y (COLH20, COLI24, POUI22 and the reference REFPOU22 upward; COLI21, COLH20''', POUI24 and the references REFG44N, REFI'21 and REFH22 downward), COLI22 goes down in corr_x, and at the last cold measurement POUI24 and POUH21 jump in corr_x; everything returns in the afternoon. The error_value rise a little on REFH22, COLH20 and COLH20''', without rejection. Nothing obstructs the view on the images, and the spots of POUI24 and POUH21 are in place at their jump: this is the camera movement, incompletely compensated. It follows the coldest night of the batch for the camera housing, read in the metrics, and comes back when it warms up: thermal effect on the camera, according to the expert: it is the housing temperature that matters, not the air temperature. Nothing to fear for the structure, nothing to do; do not trust these points.", "analysis": "BREITHORN_2026-10-22T1600_2026-11-01T0000"}
{"id": "BREITHORN-26", "start": "2026-10-29T16:00Z", "end": "2026-10-30T04:00Z", "family": "Obstruction", "description": "On the night of 29 to 30 October, a car with a headlight on, seen on the images, is parked in front of the bottom of the scene: the curve of COLI24 is missing (measurements rejected); POUI22 makes a large jump in corr_x, COLH20''' jumps in corr_x then in corr_y, COLI22 deviates a little, all partly hidden; they return in the morning. The references hold. Ignore these targets over the range, the structure does not move.", "review": "2026-11-17", "analysis": "BREITHORN_2026-10-22T1600_2026-11-01T0000"}
{"id": "BREITHORN-27", "start": "2026-10-29T16:00Z", "end": "2026-10-30T12:00Z", "family": "Thermal displacement", "description": "From the evening of 29 October to the morning of the 30th, the camera rotation and scale deviate a third time, then return at noon; COLH20, COLI24 and the reference REFPOU22 rise in corr_y, POUI24, COLI21 and the references REFG44N and REFI'21 go down, then everything returns. Nothing obstructs these targets on the images (the car of the same night only hides the bottom of the scene): this is the camera movement, incompletely compensated. It follows the cooling of the camera housing, read in the metrics, and comes back when it warms up: thermal effect on the camera, according to the expert: it is the housing temperature that matters, not the air temperature. Nothing to fear for the structure, nothing to do; do not trust these points.", "review": "2026-11-17", "analysis": "BREITHORN_2026-10-22T1600_2026-11-01T0000"}
{"id": "BREITHORN-42", "start": "2026-10-03T00:00Z", "end": "2026-10-04T20:00Z", "family": "Obstruction", "description": "From the morning of 3 October to the late afternoon of 4 October, the reference REFPOU22 is rejected together with the targets COLH20''' and POUI22: on the thumbnails and the images of those hours, the three spots are hidden behind an object with light reflections in vertical bands, a vehicle parked in front of the bottom of the scene. With one reference fewer, the compensation runs on the three others, and the corr_x of the reference REFH22 shifts clearly beyond its noise as soon as REFPOU22 is lost, stays shifted for the whole parking, then comes back to its level at the evening measurement of the 4th, when the three spots return without offset. The other targets keep their level within the noise. A change of the compensation basis caused by the hidden reference, not a movement: the structure does not move, nothing to do.", "analysis": "BREITHORN_2026-10-03T0000_2026-10-13T0000"}
{"id": "BREITHORN-43", "start": "2026-10-03T00:00Z", "end": "2026-10-13T04:00Z", "family": "Displacement", "description": "From the start of the data to 13 October, the targets drift slowly and steadily with the camera pose, step by step, as the camera gradually tilts (tilt increasing, pan and rotation decreasing): COLJ19 and POUI19 the most, mostly in corr_x (POUI19 hardly in corr_y), COLH20, COLI20, COLI21 and POUI20 in the same direction, in corr_x and corr_y; COLI24 and POUI22 drift in the opposite direction in corr_y. Their position in the image hardly moves apart from the camera movement and their error_value stays stable. Cause given by the expert: the camera is nodding forward and the compensation of its movement is not complete. Deduced from the distances of the targets to the camera: the drift of each target grows as it is closer, a parallax. COLJ19 and POUI19, the nearest according to the expert and to their distances, drift the most; the targets at middle distance (COLH20, COLI20, POUI20) less; POUH21, at the distance of the references, does not drift; the farthest (COLI24, POUI22) go the other way in corr_y. As it nods, the camera does not only turn, it also shifts a little; a shift moves near targets much more in the image than far ones, and the compensation, fitted on references at middle distance, corrects only the targets at their distance: those nearer keep a remainder in one direction, those farther in the other. The parallax explains most of the drift, not all of it: COLI21, which drifts as much as targets much nearer, COLH20''' in corr_x, and the corr_y of COLI24 and POUI22, stronger than the parallax gives, remain 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: this is not a movement of the structure, the targets keep their places relative to each other and only their view from a camera that shifts changes; the camera tilt is to be monitored.", "review": "2026-11-18", "analysis": "BREITHORN_2026-10-03T0000_2026-11-01T0000"}
{"id": "BREITHORN-44", "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 the targets drift with it: POUI19 and COLJ19 the most, mostly in corr_x (POUI19 hardly in corr_y), COLI20, COLI21, COLH20 and POUI20 in the same direction, in corr_x and corr_y; COLI24 and POUI22 drift in the opposite direction in corr_y; COLI22, COLH20''' and POUI24 drift too, more noisily, between their own rejections. Their position in the image hardly moves apart from the camera movement and their error_value stays stable. Cause given by the expert: the camera is nodding forward and the compensation of its movement is not complete. Deduced from the distances of the targets to the camera: the drift of each target grows as it is closer, a parallax. COLJ19 and POUI19, the nearest according to the expert and to their distances, drift the most; the targets at middle distance (COLH20, COLI20, POUI20) less; POUH21, at the distance of the references, does not drift; the farthest (COLI24, POUI22) go the other way in corr_y. As it nods, the camera does not only turn, it also shifts a little; a shift moves near targets much more in the image than far ones, and the compensation, fitted on references at middle distance, corrects only the targets at their distance: those nearer keep a remainder in one direction, those farther in the other. The parallax explains most of the drift, not all of it: COLI21, which drifts as much as targets much nearer, COLH20''' in corr_x, and the corr_y of COLI24 and POUI22, stronger than the parallax gives, remain 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: this is not a movement of the structure, the targets keep their places relative to each other and only their view from a camera that shifts changes; the camera tilt is to be monitored.", "review": "2026-11-18", "analysis": "BREITHORN_2026-10-03T0000_2026-11-01T0000"}
{"id": "BREITHORN-42", "start": "2026-10-03T00:00Z", "end": "2026-10-04T20:00Z", "family": "Obstruction", "description": "From the morning of 3 October to the late afternoon of 4 October, the reference REFPOU22 is rejected together with the targets COLH20''' and POUI22: on the thumbnails and the images of those hours, the three spots are hidden behind an object with light reflections in vertical bands, a vehicle parked in front of the bottom of the scene. With one reference fewer, the compensation runs on the three others, and the corr_x of the reference REFH22 shifts clearly beyond its noise as soon as REFPOU22 is lost, stays shifted for the whole parking, then comes back to its level at the evening measurement of the 4th, when the three spots return without offset. The other targets keep their level within the noise. A change of the compensation basis caused by the hidden reference, not a movement: the structure does not move, nothing to do.", "review": "2026-11-18", "analysis": "BREITHORN_2026-10-03T0000_2026-10-13T0000"}
{"id": "BREITHORN-3", "start": "2026-10-04T12:00Z", "end": "2026-10-04T20:00Z", "family": "Obstruction", "description": "For the duration of one measurement, on 4 October in the late afternoon, all the targets jump together in corr_x and in corr_y, then return at the next measurement. At that measurement, POUI24 is rejected in turn (curve absent), COLI22 jumps clearly in corr_y, and the reference REFH22, half hidden, rises clearly in error_value without being discarded, which distorts the basis of all the targets; COLH20''', POUI22 and REFPOU22 remain hidden by the vehicle parked since the day before. On the image of that hour, the banded reflections have disappeared and a light shines under POUI22: the obstacle has changed position in front of the bottom of the scene. The jumps are not a movement: point to ignore, nothing to do.", "review": "2026-11-17", "analysis": "BREITHORN_2026-10-03T0000_2026-10-13T0000"}
{"id": "BREITHORN-29", "start": "2026-10-05T00:00Z", "end": "2026-10-05T12:00Z", "family": "Thermal displacement", "description": "On 5 October in the morning, over two measurements, the camera scale and rotation deviate, then return at noon; at the same time the reference REFPOU22 and COLH20 rise clearly in corr_y while the references REFG44N and REFI'21 go down, then everything returns at noon. The images of 08:00 and 16:00 are alike, nothing obstructs the view; the error_value change little (the reference REFG44N rises a little, far from its threshold). This falls at the trough of the camera housing temperature, read in the metrics, and comes back when it rises: the same signature as the reviewed cold mornings of later in October. Thermal effect on the camera, incompletely compensated, according to the expert it is the housing temperature that matters, not the air temperature. Nothing to fear for the structure, nothing to do; do not trust these points.", "analysis": "BREITHORN_2026-10-03T0000_2026-10-13T0000"}
{"id": "BREITHORN-30", "start": "2026-10-05T20:00Z", "end": "2026-10-06T12:00Z", "family": "Thermal displacement", "description": "From midnight to the morning of 6 October, over three measurements, the camera scale and rotation deviate, most at 08:00, then return at noon; the reference REFPOU22 and COLH20 rise clearly in corr_y, the references REFG44N and REFI'21 go down a little, then everything returns at noon. Nothing obstructs the targets on the 08:00 image (only a small light at the far left of the scene, away from the spots); the error_value change little. This falls when the camera housing temperature drops, read in the metrics, and comes back when it rises: the same signature as the reviewed cold mornings of later in October. Thermal effect on the camera, incompletely compensated, according to the expert it is the housing temperature that matters. Nothing to fear for the structure, nothing to do; do not trust these points.", "analysis": "BREITHORN_2026-10-03T0000_2026-10-13T0000"}
{"id": "BREITHORN-29", "start": "2026-10-05T00:00Z", "end": "2026-10-05T12:00Z", "family": "Thermal displacement", "description": "On 5 October in the morning, over two measurements, the camera scale and rotation deviate, then return at noon; at the same time the reference REFPOU22 and COLH20 rise clearly in corr_y while the references REFG44N and REFI'21 go down, then everything returns at noon. The images of 08:00 and 16:00 are alike, nothing obstructs the view; the error_value change little (the reference REFG44N rises a little, far from its threshold). This falls at the trough of the camera housing temperature, read in the metrics, and comes back when it rises: the same signature as the reviewed cold mornings of later in October. Thermal effect on the camera, incompletely compensated, according to the expert it is the housing temperature that matters, not the air temperature. Nothing to fear for the structure, nothing to do; do not trust these points.", "review": "2026-11-18", "analysis": "BREITHORN_2026-10-03T0000_2026-10-13T0000"}
{"id": "BREITHORN-30", "start": "2026-10-05T20:00Z", "end": "2026-10-06T12:00Z", "family": "Thermal displacement", "description": "From midnight to the morning of 6 October, over three measurements, the camera scale and rotation deviate, most at 08:00, then return at noon; the reference REFPOU22 and COLH20 rise clearly in corr_y, the references REFG44N and REFI'21 go down a little, then everything returns at noon. Nothing obstructs the targets on the 08:00 image (only a small light at the far left of the scene, away from the spots); the error_value change little. This falls when the camera housing temperature drops, read in the metrics, and comes back when it rises: the same signature as the reviewed cold mornings of later in October. Thermal effect on the camera, incompletely compensated, according to the expert it is the housing temperature that matters. Nothing to fear for the structure, nothing to do; do not trust these points.", "review": "2026-11-18", "analysis": "BREITHORN_2026-10-03T0000_2026-10-13T0000"}
{"id": "BREITHORN-5", "start": "2026-10-07T08:00Z", "end": "2026-10-07T16:00Z", "family": "Obstruction", "description": "For the duration of one measurement, on 7 October at noon, the reference REFI'21 is rejected: on the image, a vehicle with reflective strips passes on the left of the scene and hides the group of REFI'21. The compensation runs on three references, the basis changes: several targets (POUI19, COLJ19, COLI20, COLI22, COLI24, POUI24) jump a little, mostly in corr_y, then return at the next measurement. This is not a movement: point to ignore.", "review": "2026-11-17", "analysis": "BREITHORN_2026-10-03T0000_2026-10-13T0000"}
{"id": "BREITHORN-6", "start": "2026-10-07T16:00Z", "end": "2026-10-08T04:00Z", "family": "Obstruction", "description": "On the night of 7 to 8 October, COLI24 is rejected from the evening, then COLI22 and POUI22 too around midnight (curves absent); POUI22 jumps in the evening and POUI24, half hidden, jumps clearly in corr_y around midnight. On the thumbnails, these spots are hidden or reduced, and a vehicle is visible in front of the bottom of the scene. Everything comes back in the morning. The structure does not move: ignore these targets over the range.", "review": "2026-11-17", "analysis": "BREITHORN_2026-10-03T0000_2026-10-13T0000"}
{"id": "BREITHORN-7", "start": "2026-10-08T20:00Z", "end": "2026-10-09T08:00Z", "family": "Obstruction", "description": "On the night of 8 to 9 October, the curves of COLI22, COLI24 and POUI22 are missing (measurements rejected) and the reference REFH22 is rejected too; POUI24, half hidden, jumps in corr_x and in corr_y. On the thumbnails, these spots are hidden and a parked vehicle is visible in front of the bottom of the scene, the image veiled by its light. The compensation runs on three references without making the other targets jump. Everything comes back in the morning: ignore these targets over the range, the structure does not move.", "review": "2026-11-17", "analysis": "BREITHORN_2026-10-03T0000_2026-10-13T0000"}
{"id": "BREITHORN-9", "start": "2026-10-10T00:00Z", "end": "2026-10-10T08:00Z", "family": "Obstruction", "description": "For the duration of one measurement, on 10 October in the morning, all the targets jump together, mostly in corr_y, then return at the next measurement; COLI22, COLI24, POUI22 and POUI24 are rejected (curves absent). On the image of that hour, a vehicle is in front of the bottom of the scene, these spots are hidden and the whole image is veiled by its light; the reference REFH22, hampered, rises clearly in error_value without being discarded, which distorts the basis of all the targets. This is not a movement: point to ignore.", "review": "2026-11-17", "analysis": "BREITHORN_2026-10-03T0000_2026-10-13T0000"}
{"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.", "review": "2026-11-18", "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"}
{"id": "BREITHORN-14", "start": "2026-10-19T00:00Z", "end": "2026-10-19T12:00Z", "family": "Thermal displacement", "description": "On 19 October in the morning, over two measurements, the camera rotation and scale suddenly deviate and its tilt takes a step; several targets deviate at the same time in opposite directions (COLH20 and the reference REFPOU22 upward in corr_y, COLI21 downward in corr_x and in corr_y), then return at noon. Nothing obstructs the view on the images, the error_value change little: this is the camera movement, incompletely compensated. It falls at the trough of the camera housing temperature, read in the metrics, and comes back when it rises: thermal effect on the camera, according to the expert: it is the housing temperature that matters, not the air temperature. Nothing to fear for the structure, nothing to do; do not trust these two points.", "review": "2026-11-17", "analysis": "BREITHORN_2026-10-13T0000_2026-10-22T1600"}
{"id": "BREITHORN-41", "start": "2026-10-21T16:00Z", "end": "2026-10-22T08:00Z", "family": "Obstruction", "description": "On the night of 21 to 22 October, COLI22, partly hidden, and POUI22 deviate clearly in corr_x and in corr_y, far beyond their ordinary noise, for three measurements, then return in the morning; COLI24, next to them, is rejected over the same measurements. On the 20:00 UTC image, the cab of a parked vehicle is in front of these bottom-left targets and the spot of COLI24 is no longer visible; the image of the morning is clear again. The references and the other targets hold. Seen on the image: a parked vehicle hides the targets. The structure does not move: ignore these targets over the range.", "review": "2026-11-18", "analysis": "BREITHORN_2026-10-13T0000_2026-10-22T1600"}
{"id": "BREITHORN-32", "start": "2026-10-22T16:00Z", "end": "2026-10-23T08:00Z", "family": "Obstruction", "description": "On the night of 22 to 23 October, the curve of COLI24 is missing (measurements rejected); COLI22, partly hidden and kept under its threshold, goes down clearly in corr_y and in corr_x, and POUI22 deviates a little in corr_x and, at the first measurement of the night, in corr_y. Seen on the contrast-stretched thumbnails of 20:00 and 04:00 UTC: the dark outline of a vehicle, lights off, stands in front of the bottom left of the scene, where the cars of the other nights park; the spot of COLI24 is hidden and that of COLI22 reduced. The references and the other targets do not move. Everything comes back in the morning, the vehicle gone on the 08:00 image. The structure does not move: ignore these targets over the range.", "review": "2026-11-18", "analysis": "BREITHORN_2026-10-22T1600_2026-11-01T0000"}
{"id": "BREITHORN-18", "start": "2026-10-23T16:00Z", "end": "2026-10-24T16:00Z", "family": "Obstruction", "description": "From the evening of 23 October to noon on 24 October, a car is parked in front of the bottom of the scene, seen on the images (grille and headlight, then headlights on). The curve of COLI24 is missing throughout; COLI22, first partly hidden, makes a very large jump in corr_x (its measured center slides over the visible part of its spot) and POUI22 jumps in corr_x, then COLI22, POUI22 and POUI24 are rejected on the morning of the 24th. The references hold. The structure does not move: ignore these targets over the range.", "review": "2026-11-17", "analysis": "BREITHORN_2026-10-22T1600_2026-11-01T0000"}
{"id": "BREITHORN-20", "start": "2026-10-25T20:00Z", "end": "2026-10-26T08:00Z", "family": "Obstruction", "description": "On the night of 25 to 26 October, an oblique structure, seen on the images in front of the bottom of the scene, hides the references REFH22 and REFPOU22, and COLH20''', COLI22 and POUI24 (measurements rejected, curves absent); POUI22, partly hidden, jumps in corr_x and in corr_y. The compensation only runs on two references: the basis changes, several targets (COLI20, POUI20, POUH21, COLJ19) shift a little in corr_x. Very bad sign for the measurement: data of the range not to be trusted; everything comes back in the morning.", "review": "2026-11-17", "analysis": "BREITHORN_2026-10-22T1600_2026-11-01T0000"}
{"id": "BREITHORN-33", "start": "2026-10-26T12:00Z", "end": "2026-10-26T20:00Z", "family": "Obstruction", "description": "On the evening of 26 October, a car with its headlights on, seen on the 16:00 UTC image, is parked in front of the bottom of the scene: the reference REFH22 is rejected and the compensation runs on three references; the curves of COLI24 and POUI24 are missing, and POUI22, partly hidden and kept under its threshold, makes a very large jump in corr_y and a jump in corr_x. COLI22 and COLH20 shift a little, through the change of references. The car is gone on the 20:00 image, where the oblique structure of the night takes over (labelled apart). The structure does not move: ignore these targets over the range.", "review": "2026-11-18", "analysis": "BREITHORN_2026-10-22T1600_2026-11-01T0000"}
{"id": "BREITHORN-34", "start": "2026-10-26T16:00Z", "end": "2026-10-27T08:00Z", "family": "Obstruction", "description": "On the night of 26 to 27 October, an oblique structure, seen on the images of 20:00 and 00:00 UTC in front of the bottom of the scene, follows the car of the evening (labelled apart). At 20:00 it hides the reference REFH22, COLI24 and POUI22 (measurements rejected, curves absent) and POUI24, partly hidden, jumps strongly in corr_x; at 00:00 and 04:00 it hides the reference REFPOU22, COLH20''' and still POUI22. The compensation runs on three references: REFG44N and REFI'21 shift a little in corr_x, the targets hardly. Everything comes back in the morning, the view clear on the 08:00 image. Ignore these targets over the range; the structure does not move.", "review": "2026-11-18", "analysis": "BREITHORN_2026-10-22T1600_2026-11-01T0000"}
{"id": "BREITHORN-24", "start": "2026-10-28T00:00Z", "end": "2026-10-28T12:00Z", "family": "Thermal displacement", "description": "On 28 October in the morning, over two measurements, the camera rotation and scale deviate then return at noon; at the same time, several targets deviate in opposite directions in corr_y (COLH20, COLI24, POUI22 and the reference REFPOU22 upward, POUI24 and the references REFG44N and REFI'21 downward), and return with the camera. Nothing obstructs the view on the images: this is the camera movement, incompletely compensated. It falls at the trough of the camera housing temperature, read in the metrics, and comes back when it rises: thermal effect on the camera, according to the expert: it is the housing temperature that matters, not the air temperature. Nothing to fear for the structure, nothing to do; do not trust these points.", "review": "2026-11-17", "analysis": "BREITHORN_2026-10-22T1600_2026-11-01T0000"}
{"id": "BREITHORN-35", "start": "2026-10-28T16:00Z", "end": "2026-10-29T16:00Z", "family": "Thermal displacement", "description": "From the evening of 28 October to noon on the 29th, the camera rotation and scale deviate again, for longer and more strongly, then return in the afternoon; several targets deviate with it in opposite directions in corr_y (COLH20, COLI24, POUI22 and the reference REFPOU22 upward; COLI21, COLH20''', POUI24 and the references REFG44N, REFI'21 and REFH22 downward), COLI22 goes down in corr_x, and at the last cold measurement POUI24 and POUH21 jump in corr_x; everything returns in the afternoon. The error_value rise a little on REFH22, COLH20 and COLH20''', without rejection. Nothing obstructs the view on the images, and the spots of POUI24 and POUH21 are in place at their jump: this is the camera movement, incompletely compensated. It follows the coldest night of the batch for the camera housing, read in the metrics, and comes back when it warms up: thermal effect on the camera, according to the expert: it is the housing temperature that matters, not the air temperature. Nothing to fear for the structure, nothing to do; do not trust these points.", "review": "2026-11-18", "analysis": "BREITHORN_2026-10-22T1600_2026-11-01T0000"}
{"id": "BREITHORN-26", "start": "2026-10-29T16:00Z", "end": "2026-10-30T04:00Z", "family": "Obstruction", "description": "On the night of 29 to 30 October, a car with a headlight on, seen on the images, is parked in front of the bottom of the scene: the curve of COLI24 is missing (measurements rejected); POUI22 makes a large jump in corr_x, COLH20''' jumps in corr_x then in corr_y, COLI22 deviates a little, all partly hidden; they return in the morning. The references hold. Ignore these targets over the range, the structure does not move.", "review": "2026-11-17", "analysis": "BREITHORN_2026-10-22T1600_2026-11-01T0000"}
{"id": "BREITHORN-27", "start": "2026-10-29T16:00Z", "end": "2026-10-30T12:00Z", "family": "Thermal displacement", "description": "From the evening of 29 October to the morning of the 30th, the camera rotation and scale deviate a third time, then return at noon; COLH20, COLI24 and the reference REFPOU22 rise in corr_y, POUI24, COLI21 and the references REFG44N and REFI'21 go down, then everything returns. Nothing obstructs these targets on the images (the car of the same night only hides the bottom of the scene): this is the camera movement, incompletely compensated. It follows the cooling of the camera housing, read in the metrics, and comes back when it warms up: thermal effect on the camera, according to the expert: it is the housing temperature that matters, not the air temperature. Nothing to fear for the structure, nothing to do; do not trust these points.", "review": "2026-11-17", "analysis": "BREITHORN_2026-10-22T1600_2026-11-01T0000"}
+19 -35
View File
@@ -1,47 +1,31 @@
{"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"}
{"id": "CLARIDEN-17", "start": "2026-10-16T14:20Z", "end": "2026-10-16T14:40Z", "family": "No data", "description": "One measurement is missing, for all sensors, a few hours after the resumption of the 16th: the curves have a short gap; normal voltage around it. The same gap falls at the same moment on the other stations measuring at that time (FLORIDA, LENZSPITZE, NORDEND, SNCF01): a common cause outside the station (transmission or reception of the data), not a failure of the station; it is not established. The curves are missing over the range; nothing to do on the station.", "review": "2026-11-17", "analysis": "CLARIDEN_2026-10-11T0000_2026-10-20T0400"}
{"id": "CLARIDEN-53", "start": "2026-10-17T16:00Z", "end": "2026-10-20T00:30Z", "family": "Displacement", "description": "From the 17th to the 19th, the camera slowly tilts the other way: its tilt goes down, more and more after the restart that follows the outage of the 18th; it partly comes back during the 19th, then suddenly jumps back on the 20th (labeled separately). The raw positions of all sensors, references included, move together vertically in the image with it. The compensation does not render this movement evenly. The corrected vertical curves of D-302-B and PR_BG (same prism) rise. Those of D-303-B, D-304-B, P-301-B, D-306-B, D-303-C and D-304-C go down, and D-301-C rises a little horizontally. They follow the tilt step by step, come back partly with it on the 19th, and return at once at the camera jump of the 20th. The recognition error stays at its level, and the image of the 19th shows nothing in front of the targets. The housing temperature drops a little on the 18th and is low at the restart after the outage; but the tilt keeps going down after the housing has warmed again, and it does not come back at equal temperature: link not established. This is not a movement of the structure but the remainder of an incomplete compensation of the camera movement; the camera is to be monitored.", "analysis": "CLARIDEN_2026-10-11T0000_2026-10-20T0400"}
{"id": "CLARIDEN-54", "start": "2026-10-18T06:30Z", "end": "2026-10-18T06:50Z", "family": "Displacement", "description": "For one measurement, the corrected horizontal curves of the targets of row A (D-304-A, D-302_A, D-303-A, D-300-A, P-298-A, D-301-A) and of D-302-B and PR_BG (same prism) jump together, then come back at the next one. The raw positions of the targets do not move; the references PR-291, PR-293 and PR-295 shift slightly horizontally against them, and the camera pose jumps (pan, scale): the compensation is skewed for one measurement. The recognition error stays at its level. There is no image at that instant; the image of the next hour shows work lights at the far end of the tunnel and 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-55", "start": "2026-10-18T08:50Z", "end": "2026-10-18T09:30Z", "family": "Visibility", "description": "For three measurements, the corrected curves of many targets make a bump that comes back: first the targets of row A (D-300-A, D-301-A, D-302_A, D-303-A, D-304-A, P-298-A) rise vertically; over the next two measurements, the recognition error of most targets and of the references PR-293 and PR-295 rises, D-302-B and PR_BG (same prism) rise strongly vertically, D-301-C goes down strongly horizontally, and P-301-B and D-303-B move horizontally. All come back at the following measurement. The camera pose jumps at the same time (tilt, scale), and the housing temperature drops. The image of the first measurement shows nothing in front of the targets. The signature is that of the other view obstruction episodes at the station: the error rises on most sensors, and the edges are sharp. Reduced visibility is deduced from it; the cause is not seen. Points to ignore.", "analysis": "CLARIDEN_2026-10-11T0000_2026-10-20T0400"}
{"id": "CLARIDEN-56", "start": "2026-10-18T13:50Z", "end": "2026-10-18T23:30Z", "family": "No data", "description": "No measurement or image for almost ten hours, nor station metric. On resumption, the battery is depleted and the voltage low, then they rise: signature of a power cut. The curves are missing over the range; check the power supply if it repeats.", "analysis": "CLARIDEN_2026-10-11T0000_2026-10-20T0400"}
{"id": "CLARIDEN-57", "start": "2026-10-19T09:00Z", "end": "2026-10-19T10:10Z", "family": "No data", "description": "Four measurements are missing within one hour, for all sensors, between isolated measurements: the curves have gaps; normal voltage around them. The same gap falls at the same moment on the other stations measuring at that time (FLORIDA, JUNGFRAU, LENZSPITZE, NIEDERHORN, NORDEND, SNCF01): a common cause outside the station (transmission or reception of the data), not a failure of the station; it is not established. The curves are missing over the range; nothing to do on the station.", "analysis": "CLARIDEN_2026-10-11T0000_2026-10-20T0400"}
{"id": "CLARIDEN-58", "start": "2026-10-19T20:40Z", "end": "2026-10-19T21:30Z", "family": "No data", "description": "Three measurements are missing in less than an hour, for all sensors: the curves have a gap; normal voltage around it. The same gap falls at the same moment on the other stations measuring at that time (FLORIDA, JUNGFRAU, LENZSPITZE, NIEDERHORN, NORDEND, SNCF01): a common cause outside the station (transmission or reception of the data), not a failure of the station; it is not established. The curves are missing over the range; nothing to do on the station. The hourly metrics of BREITHORN, MICHIGAN and NEBRASKA are also missing at 21:00.", "analysis": "CLARIDEN_2026-10-11T0000_2026-10-20T0400"}
{"id": "CLARIDEN-59", "start": "2026-10-20T00:10Z", "end": "2026-10-20T00:40Z", "family": "Displacement", "description": "On the 20th, over two measurements, the whole scene, references included, suddenly shifts in the image, mostly vertically: the camera has moved (its tilt jumps). The compensation absorbs most of it, but the corrected curves of several targets jump. Vertically, D-303-C, D-304-C, D-304-B, D-303-B and P-301-B go back up to the level they had before the slow tilting of the camera of the 17th to the 19th (labeled separately): this jump erases its remainder. D-306-B jumps up clearly, beyond its earlier level, and stays there. D-302-B and PR_BG (same prism) jump horizontally and stay there. The recognition error of D-302-B and D-303-B changes level at the same moment. Work lights are visible at the far end of the tunnel on the images of the hour before and the hour after; nothing is in front of the targets. The cause of the camera movement is not established. The lasting jumps of D-306-B and D-302-B are not an established movement of the structure: to be checked; the camera is to be monitored.", "analysis": "CLARIDEN_2026-10-11T0000_2026-10-20T0400"}
{"id": "CLARIDEN-2", "start": "2026-10-01T06:15Z", "end": "2026-10-01T08:45Z", "family": "Visibility", "description": "The recognition error of most targets rises together, first a little, then clearly around 07:50-08:00, and comes back down; at the same time the corrected curves of several targets make a bump that comes back: D-301-C horizontally, D-302-B and PR_BG (same prism) vertically, D-306-B, D-303-B, P-301-B, then around 08:00 D-301-A, D-302_A, D-304-A. The scene deforms a little (scale and rotation of the targets, references PR-291 and PR-293 moving away from the targets), without camera movement. Nothing on the 07:00 and 08:00 images, which are dark as always. Diffuse obstruction of the view in the tunnel, cause not established (the tunnel air?); same signature as the episodes of 2, 6, 18, 22 and 31 October. The structure does not move: do not trust the curves over the range.", "review": "2026-11-17", "analysis": "CLARIDEN_2026-10-01T0000_2026-10-11T0000"}
{"id": "CLARIDEN-3", "start": "2026-10-01T17:45Z", "end": "2026-10-02T02:30Z", "family": "Displacement", "description": "The low targets of row B go down vertically from 18:00: D-306-B above all, which keeps going down into the night then stays low until the gap of 3 October, D-304-B and D-303-B (which, for its part, gradually rises until the 3rd). Raw positions almost motionless, no camera movement, ordinary recognition error, no image showing a cause. 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", "analysis": "CLARIDEN_2026-10-01T0000_2026-10-11T0000"}
{"id": "CLARIDEN-44", "start": "2026-10-02T03:40Z", "end": "2026-10-03T03:00Z", "family": "Displacement", "description": "D-303-B comes back up vertically after its descent of the evening of the 1st (labeled separately): first during the morning of the 2nd, then after a pause over the day, again in the evening and the night, until it reaches its level from before the descent in the night of the 2nd to the 3rd, and stays there until the gap of the 3rd. D-306-B and D-304-B, which went down with it, do not come back. Ordinary recognition error, apart from the view obstruction of the evening of the 2nd (labeled separately); nothing on the thumbnails of the 2nd at 12:00 and the 3rd at 08:00. The camera tilt decreases slowly over these days, and D-303-B follows the tilt of the camera only in part (see the 6th and the 8th): this may explain a small part of the rise, not all of it. Cause not established, in a tunnel under construction: return of the descent of the 1st; to be checked with the other measurements of the site.", "analysis": "CLARIDEN_2026-10-01T0000_2026-10-11T0000"}
{"id": "CLARIDEN-45", "start": "2026-10-02T21:30Z", "end": "2026-10-02T23:00Z", "family": "Visibility", "description": "The recognition error of most targets rises together for one hour, and the corrected curves of D-304-B (vertical) above all, of D-301-C (horizontal), D-302-B and PR_BG, P-301-B, D-304-C make a bump that comes back; D-304-B is still shifted at the last measurement, before 23:00. The camera housing temperature drops clearly at the same time. Nothing visible on the 22:00 image. Diffuse obstruction of the view, cause not established, perhaps a change in the tunnel air. The structure does not move: curves to ignore over the range.", "analysis": "CLARIDEN_2026-10-01T0000_2026-10-11T0000"}
{"id": "CLARIDEN-45", "start": "2026-10-02T21:30Z", "end": "2026-10-02T23:00Z", "family": "Visibility", "description": "The recognition error of most targets rises together for one hour, and the corrected curves of D-304-B (vertical) above all, of D-301-C (horizontal), D-302-B and PR_BG, P-301-B, D-304-C make a bump that comes back; D-304-B is still shifted at the last measurement, before 23:00. The camera housing temperature drops clearly at the same time. Nothing visible on the 22:00 image. Diffuse obstruction of the view, cause not established, perhaps a change in the tunnel air. The structure does not move: curves to ignore over the range.", "review": "2026-11-18", "analysis": "CLARIDEN_2026-10-01T0000_2026-10-11T0000"}
{"id": "CLARIDEN-6", "start": "2026-10-03T07:40Z", "end": "2026-10-03T08:00Z", "family": "No data", "description": "One measurement is missing, for all sensors: the curves have a short gap. Cause not established.", "review": "2026-11-17", "analysis": "CLARIDEN_2026-10-01T0000_2026-10-11T0000"}
{"id": "CLARIDEN-46", "start": "2026-10-03T09:40Z", "end": "2026-10-03T17:00Z", "family": "Displacement", "description": "P-301-B alone: its vertical corrected curve, a little low since the view obstruction of the evening of the 2nd, jumps up within two measurements around 09:50, together with a clear rise of its own recognition error, stays above its usual level until the early afternoon, then slowly comes back down until the late afternoon. Its raw position moves in the image while the neighbouring targets and the camera stay still; its horizontal curve hardly moves. The thumbnails of 08:00, 12:00 and 16:00 show the same sharp spot, nothing in front. Cause not established: something changes in the appearance or the position of this target only; not an established movement of the structure, to be checked; ignore this curve over the range.", "analysis": "CLARIDEN_2026-10-01T0000_2026-10-11T0000"}
{"id": "CLARIDEN-7", "start": "2026-10-03T17:30Z", "end": "2026-10-03T17:45Z", "family": "Visibility", "description": "Last measurement before the gap of 3 October: the same one-measurement bump on D-301-C, D-302-B and PR_BG, D-304-B, D-304-C, P-301-B, with the recognition error of many targets rising. Same signature as the episodes of view obstruction at the station; cause not established, perhaps linked to the station shutdown that follows. Point to ignore.", "review": "2026-11-17", "analysis": "CLARIDEN_2026-10-01T0000_2026-10-11T0000"}
{"id": "CLARIDEN-8", "start": "2026-10-03T17:45Z", "end": "2026-10-05T10:30Z", "family": "No data", "description": "No measurement or image for almost two days, for all sensors, and the station metrics are missing too: the entire station stopped. Voltage and battery normal before and after the gap, so not the signature of a power cut; on resumption, the camera has moved and a blurred object is very close to the lens (10:30 image), which suggests an intervention on the station. Cause not established: the curves are missing over the range.", "review": "2026-11-17", "analysis": "CLARIDEN_2026-10-01T0000_2026-10-11T0000"}
{"id": "CLARIDEN-9", "start": "2026-10-03T17:45Z", "end": "2026-10-05T10:45Z", "family": "Displacement", "description": "After the gap of 3 to 5 October, many targets resume at a different level, and do not return to the previous one until the end of the batch: D-304-C and D-303-C above all, in both directions, then D-302_A and D-301-A, P-299-B, D-300-C, D-303-B and D-304-B horizontally, D-301-C vertically; D-306-B, for its part, returns to its level from before its descent of the evening of the 1st. The raw positions of D-304-C and D-303-C have moved in the image relative to the other targets, the recognition error of several targets (D-302-C, D-301-C, D-303-C, D-304-C, D-301-A, D-306-B) also changes level, and the camera scale is no longer the same: the appearance of these targets and the camera pose changed during the shutdown. On resumption, a blurred object is very close to the lens (10:30 image). Cause not established: intervention or changed setting during the shutdown, or real movement; to be checked before trusting these new levels.", "review": "2026-11-17", "analysis": "CLARIDEN_2026-10-01T0000_2026-10-11T0000"}
{"id": "CLARIDEN-10", "start": "2026-10-05T10:30Z", "end": "2026-10-05T11:20Z", "family": "Obstruction", "description": "First measurement after the gap: the whole scene, references included, is shifted by several pixels in the image and the camera is tilted, then it returns within twenty minutes; the compensation absorbs it poorly for the duration of one measurement, and the corrected curves of many targets jump then return (D-303-C, D-302-B and PR_BG, D-306-B, D-304-B, P-299-C above all; D-303-B stays slightly shifted until 11:10). D-304-C is rejected. The 10:30 image shows a large blurred object very close to the lens, on the right, which hides D-304-C, and a worker in reflective clothing in the tunnel, at the top left: work is going on around the camera. Points to ignore; the structure does not move.", "review": "2026-11-17", "analysis": "CLARIDEN_2026-10-01T0000_2026-10-11T0000"}
{"id": "CLARIDEN-11", "start": "2026-10-05T12:10Z", "end": "2026-10-05T12:30Z", "family": "Obstruction", "description": "For the duration of one measurement, the whole right-hand row C (D-300-C, D-301-C, D-303-C, D-304-C, P-298-C, P-299-C) and the reference D-302-C are rejected, their recognition error almost at 1; the compensation runs without D-302-C and the targets that stayed under the threshold jump then return at the next measurement (D-306-B above all vertically, D-303-B, D-304-B, P-299-B, P-301-B, D-302-B and PR_BG). No image at 12:20: the cause is not seen, but the signature is that of something passing in front of the right-hand part of the scene. Point to ignore.", "review": "2026-11-17", "analysis": "CLARIDEN_2026-10-01T0000_2026-10-11T0000"}
{"id": "CLARIDEN-73", "start": "2026-10-06T13:00Z", "end": "2026-10-06T13:30Z", "family": "Displacement", "description": "Around 13:10 the whole scene, references included, shifts by a step vertically in the image: the camera tilt makes a step, which it keeps. The compensation absorbs it for all the targets except D-303-B, whose raw position follows only part of the shift: its vertical corrected curve drops by a step and stays low into the evening (D-303-C and D-304-C at most slightly). Ordinary recognition error. Over the following days, D-303-B keeps following the camera tilt in the same partial way (the drift labeled from the evening of the 6th; the opposite camera step of the 8th leaves it only a remainder within the noise). Cause of the camera step not established; the step of D-303-B is the remainder of the camera movement, not a movement of the structure: the camera is to be monitored.", "analysis": "CLARIDEN_2026-10-01T0000_2026-10-11T0000"}
{"id": "CLARIDEN-12", "start": "2026-10-06T18:00Z", "end": "2026-10-06T22:10Z", "family": "Visibility", "description": "For four hours, the corrected curves of the same group of targets take a step that starts and ends sharply: D-301-C horizontally above all, D-302-B and PR_BG (same prism) horizontally then vertically, D-304-B vertically, and at times P-301-B, D-303-B, D-302_A, D-301-A, D-304-C. The recognition error of the references PR-293, PR-295, PR-296 and of a few targets rises a little; the references move away from each other in the image. The camera housing temperature drops clearly over these hours. Nothing visible on the 20:00 image. View obstruction of cause not established, probably the tunnel air (colder); the curves and the recognition error return at 22:00, before the camera scale. The structure does not move: curves to ignore over the range.", "analysis": "CLARIDEN_2026-10-01T0000_2026-10-11T0000"}
{"id": "CLARIDEN-23", "start": "2026-10-20T04:00Z", "end": "2026-10-25T18:00Z", "family": "Displacement", "description": "Slow drift of targets of row C, then stabilization at a new level: D-301-C rises horizontally from the 20th, D-304-C and D-303-C rise vertically mostly from the 22nd. No camera movement, ordinary recognition error. The rise of D-301-C starts before the work seen around the station on the 22nd (workers and a frame): no link established. The position in the image of D-301-C, D-304-C and D-303-C moves clearly 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. Partial return from the 26th to the 29th, 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", "analysis": "CLARIDEN_2026-10-20T0400_2026-11-01T0010"}
{"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-74", "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. Afterwards D-301-C comes back down a little over the following days, too little to be labeled, and D-303-B stays at its new level. 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.", "review": "2026-11-18", "analysis": "CLARIDEN_2026-10-01T0000_2026-11-01T0000"}
{"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.", "review": "2026-11-18", "analysis": "CLARIDEN_2026-10-11T0000_2026-10-20T0400"}
{"id": "CLARIDEN-17", "start": "2026-10-16T14:20Z", "end": "2026-10-16T14:40Z", "family": "No data", "description": "One measurement is missing, for all sensors, a few hours after the resumption of the 16th: the curves have a short gap; normal voltage around it. The same gap falls at the same moment on the other stations measuring at that time (FLORIDA, LENZSPITZE, NORDEND, SNCF01): a common cause outside the station (transmission or reception of the data), not a failure of the station; it is not established. The curves are missing over the range; nothing to do on the station.", "review": "2026-11-17", "analysis": "CLARIDEN_2026-10-11T0000_2026-10-20T0400"}
{"id": "CLARIDEN-55", "start": "2026-10-18T08:50Z", "end": "2026-10-18T09:30Z", "family": "Visibility", "description": "For three measurements, the corrected curves of many targets make a bump that comes back: first the targets of row A (D-300-A, D-301-A, D-302_A, D-303-A, D-304-A, P-298-A) rise vertically; over the next two measurements, the recognition error of most targets and of the references PR-293 and PR-295 rises, D-302-B and PR_BG (same prism) rise strongly vertically, D-301-C goes down strongly horizontally, and P-301-B and D-303-B move horizontally. All come back at the following measurement. The camera pose jumps at the same time (tilt, scale), and the housing temperature drops. The image of the first measurement shows nothing in front of the targets. The signature is that of the other view obstruction episodes at the station: the error rises on most sensors, and the edges are sharp. Reduced visibility is deduced from it; the cause is not seen. Points to ignore.", "review": "2026-11-18", "analysis": "CLARIDEN_2026-10-11T0000_2026-10-20T0400"}
{"id": "CLARIDEN-56", "start": "2026-10-18T13:50Z", "end": "2026-10-18T23:30Z", "family": "No data", "description": "No measurement or image for almost ten hours, nor station metric. On resumption, the battery is depleted and the voltage low, then they rise: signature of a power cut. The curves are missing over the range; check the power supply if it repeats.", "review": "2026-11-18", "analysis": "CLARIDEN_2026-10-11T0000_2026-10-20T0400"}
{"id": "CLARIDEN-57", "start": "2026-10-19T09:00Z", "end": "2026-10-19T10:10Z", "family": "No data", "description": "Four measurements are missing within one hour, for all sensors, between isolated measurements: the curves have gaps; normal voltage around them. The same gap falls at the same moment on the other stations measuring at that time (FLORIDA, JUNGFRAU, LENZSPITZE, NIEDERHORN, NORDEND, SNCF01): a common cause outside the station (transmission or reception of the data), not a failure of the station; it is not established. The curves are missing over the range; nothing to do on the station.", "review": "2026-11-18", "analysis": "CLARIDEN_2026-10-11T0000_2026-10-20T0400"}
{"id": "CLARIDEN-58", "start": "2026-10-19T20:40Z", "end": "2026-10-19T21:30Z", "family": "No data", "description": "Three measurements are missing in less than an hour, for all sensors: the curves have a gap; normal voltage around it. The same gap falls at the same moment on the other stations measuring at that time (FLORIDA, JUNGFRAU, LENZSPITZE, NIEDERHORN, NORDEND, SNCF01): a common cause outside the station (transmission or reception of the data), not a failure of the station; it is not established. The curves are missing over the range; nothing to do on the station. The hourly metrics of BREITHORN, MICHIGAN and NEBRASKA are also missing at 21:00.", "review": "2026-11-18", "analysis": "CLARIDEN_2026-10-11T0000_2026-10-20T0400"}
{"id": "CLARIDEN-23", "start": "2026-10-20T04:00Z", "end": "2026-10-25T18:00Z", "family": "Displacement", "description": "Slow drift of targets of row C, then stabilization at a new level: D-301-C rises horizontally from the 20th, D-304-C and D-303-C rise vertically mostly from the 22nd. No camera movement, ordinary recognition error. The rise of D-301-C starts before the work seen around the station on the 22nd (workers and a frame): no link established. The position in the image of D-301-C, D-304-C and D-303-C moves clearly 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. D-304-C and D-303-C then come back down a little from the 26th to the 29th, without returning to their level from before: too small to be labeled. 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-18", "analysis": "CLARIDEN_2026-10-20T0400_2026-11-01T0010"}
{"id": "CLARIDEN-24", "start": "2026-10-20T06:10Z", "end": "2026-10-20T06:30Z", "family": "No data", "description": "One measurement is missing, for all sensors: the curves have a short gap; the station nevertheless synchronizes at that moment, normal voltage. The same moment is also missing at LENZSPITZE, and at no other station: a common cause outside the station is possible, not established. Nothing to do.", "review": "2026-11-17", "analysis": "CLARIDEN_2026-10-20T0400_2026-11-01T0010"}
{"id": "CLARIDEN-60", "start": "2026-10-20T20:40Z", "end": "2026-10-20T21:40Z", "family": "No data", "description": "Five measurements are missing within one hour, for all sensors: the curves have a gap. The station is nevertheless running (continuous synchronizations, 21:00 image, normal voltage): the measurement is not made or not recorded. The 21:00 measurement is also missing at NIEDERHORN, and at no other station: a common cause is possible, not established. Nothing to do.", "analysis": "CLARIDEN_2026-10-20T0400_2026-11-01T0010"}
{"id": "CLARIDEN-61", "start": "2026-10-22T06:30Z", "end": "2026-10-22T08:50Z", "family": "Visibility", "description": "In two phases, from 06:40 to 06:50 then from 07:50 to 08:30, the recognition error of several targets and of the references D-302-C and PR-293 rises, and the corrected curves of the usual group make a bump that comes back: D-301-C horizontally, D-302-B and PR_BG vertically, P-301-B, D-304-B, D-304-C, and at the start D-302_A, P-298-A, D-304-A, D-303-A; between the two, D-302-B and PR_BG move once more. The camera housing temperature drops during these hours. The 08:00 image shows lights at the far end of the tunnel (machine or vehicle), nothing in front of the targets. Diffuse view obstruction of cause not established, the same as in the other episodes at the station. Curves to ignore over the range; the structure does not move.", "analysis": "CLARIDEN_2026-10-20T0400_2026-11-01T0010"}
{"id": "CLARIDEN-62", "start": "2026-10-22T08:50Z", "end": "2026-10-22T17:00Z", "family": "Displacement", "description": "The low targets of row B rise vertically during the day: D-306-B above all, D-302-B and PR_BG, D-304-B, D-303-B; the recognition error of a few of them rises a little. Workers are visible in the tunnel on the 12:00 image, and a frame appears very close to the camera at the top of the image at 13:00 (it stays there until the end of the batch): work around the station. The position in the image of D-306-B rises a little relative to the other targets, in the direction of its curve. The link between this work and the rise is not established. Evening descent, 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-20T0400_2026-11-01T0010"}
{"id": "CLARIDEN-29", "start": "2026-10-22T17:00Z", "end": "2026-10-23T10:30Z", "family": "Displacement", "description": "The low targets of row B go back down vertically, all at once on the evening of the 22nd then more slowly on the morning of the 23rd, to below their level from before their rise of the day: D-306-B above all, D-304-B, D-303-B, D-302-B and PR_BG. No camera movement; the frame installed on the 22nd stays at the top of the image (19:00 image), nothing else. The position in the image of D-306-B also goes down relative to the other targets. This is the return of the rise of the day, labeled separately, and it goes beyond it. 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", "analysis": "CLARIDEN_2026-10-20T0400_2026-11-01T0010"}
{"id": "CLARIDEN-30", "start": "2026-10-24T01:00Z", "end": "2026-10-24T05:00Z", "family": "Displacement", "description": "The low targets of row B (D-306-B above all, D-304-B, D-303-B) partly rise again vertically in the night of the 24th, toward their level from before the descent of the evening of the 22nd, without reaching it. No camera movement. 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", "analysis": "CLARIDEN_2026-10-20T0400_2026-11-01T0010"}
{"id": "CLARIDEN-31", "start": "2026-10-24T18:20Z", "end": "2026-10-25T19:10Z", "family": "Displacement", "description": "The left targets of row A (D-302_A, D-303-A, D-304-A, D-301-A, P-299-A) and D-304-B, D-306-B, P-301-B fidget in jolts (around 18:30 and 21:30 on the 24th, 07:00 and 15:30 on the 25th): the vertical rises, the horizontal goes down; the recognition error of these targets and of the reference D-302-C rises during the first jolts, and the references PR-291 and PR-293 move slightly away from the targets in the image. Everything calms down on the evening of the 25th. After the agitation, the horizontal of the A targets stays shifted until the end of the batch. Workers are visible on the image of the 24th at 15:00 and the frame is still at the top of the image. Cause not established: shift to be checked.", "review": "2026-11-17", "analysis": "CLARIDEN_2026-10-20T0400_2026-11-01T0010"}
{"id": "CLARIDEN-32", "start": "2026-10-25T18:00Z", "end": "2026-10-29T04:00Z", "family": "Displacement", "description": "After their rise of the 20th to the 25th, D-304-C and D-303-C slowly go back down vertically from the 26th to the 29th, without returning to their level from before the rise, then stabilize. No camera movement, nothing in front of the targets on the images of the 28th at 19:00 and 20:00. Their position in the image also partly returns toward that of the other targets. This is the partial return of the rise of the 20th to the 25th, 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", "analysis": "CLARIDEN_2026-10-20T0400_2026-11-01T0010"}
{"id": "CLARIDEN-63", "start": "2026-10-25T19:10Z", "end": "2026-10-29T04:00Z", "family": "Displacement", "description": "After their rise in jolts of the 24th and 25th, the left targets of row A slowly go back down vertically from the 26th to the 29th, back to about their level from before the jolts: D-304-A, D-303-A, D-302_A and D-301-A above all, P-299-A and P-298-A less; their horizontal stays shifted. Their position in the image comes back with their curves, relative to the other targets; no camera step, ordinary recognition error. Same dates as the partial return of D-304-C and D-303-C, labeled separately. This is the return of the agitation of the 24th and 25th, 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-20T0400_2026-11-01T0010"}
{"id": "CLARIDEN-64", "start": "2026-10-26T14:30Z", "end": "2026-10-26T15:10Z", "family": "No data", "description": "Three measurements are missing in less than an hour, for all sensors: the curves have a gap; normal voltage around it. The same gap falls at the same moment on the other stations measuring at that time (FLORIDA, JUNGFRAU, LENZSPITZE, NIEDERHORN, NORDEND, SNCF01), and their metrics are also missing at the same minutes: a common cause outside the station (transmission or reception of the data), not a failure of the station; it is not established. The curves are missing over the range; nothing to do on the station. The hourly metrics of BREITHORN, MICHIGAN and NEBRASKA are also missing at 15:00.", "analysis": "CLARIDEN_2026-10-20T0400_2026-11-01T0010"}
{"id": "CLARIDEN-60", "start": "2026-10-20T20:40Z", "end": "2026-10-20T21:40Z", "family": "No data", "description": "Five measurements are missing within one hour, for all sensors: the curves have a gap. The station is nevertheless running (continuous synchronizations, 21:00 image, normal voltage): the measurement is not made or not recorded. The 21:00 measurement is also missing at NIEDERHORN, and at no other station: a common cause is possible, not established. Nothing to do.", "review": "2026-11-18", "analysis": "CLARIDEN_2026-10-20T0400_2026-11-01T0010"}
{"id": "CLARIDEN-61", "start": "2026-10-22T06:30Z", "end": "2026-10-22T08:50Z", "family": "Visibility", "description": "In two phases, from 06:40 to 06:50 then from 07:50 to 08:30, the recognition error of several targets and of the references D-302-C and PR-293 rises, and the corrected curves of the usual group make a bump that comes back: D-301-C horizontally, D-302-B and PR_BG vertically, P-301-B, D-304-B, D-304-C, and at the start D-302_A, P-298-A, D-304-A, D-303-A; between the two, D-302-B and PR_BG move once more. The camera housing temperature drops during these hours. The 08:00 image shows lights at the far end of the tunnel (machine or vehicle), nothing in front of the targets. Diffuse view obstruction of cause not established, the same as in the other episodes at the station. Curves to ignore over the range; the structure does not move.", "review": "2026-11-18", "analysis": "CLARIDEN_2026-10-20T0400_2026-11-01T0010"}
{"id": "CLARIDEN-64", "start": "2026-10-26T14:30Z", "end": "2026-10-26T15:10Z", "family": "No data", "description": "Three measurements are missing in less than an hour, for all sensors: the curves have a gap; normal voltage around it. The same gap falls at the same moment on the other stations measuring at that time (FLORIDA, JUNGFRAU, LENZSPITZE, NIEDERHORN, NORDEND, SNCF01), and their metrics are also missing at the same minutes: a common cause outside the station (transmission or reception of the data), not a failure of the station; it is not established. The curves are missing over the range; nothing to do on the station. The hourly metrics of BREITHORN, MICHIGAN and NEBRASKA are also missing at 15:00.", "review": "2026-11-18", "analysis": "CLARIDEN_2026-10-20T0400_2026-11-01T0010"}
{"id": "CLARIDEN-34", "start": "2026-10-27T09:00Z", "end": "2026-10-27T09:30Z", "family": "No data", "description": "Two measurements are missing, for all sensors: the curves have a short gap; normal voltage around it. The same gap falls at the same moment on the other stations measuring at that time (FLORIDA, JUNGFRAU, LENZSPITZE, NORDEND): a common cause outside the station (transmission or reception of the data), not a failure of the station; it is not established. The curves are missing over the range; nothing to do on the station.", "review": "2026-11-17", "analysis": "CLARIDEN_2026-10-20T0400_2026-11-01T0010"}
{"id": "CLARIDEN-35", "start": "2026-10-27T12:00Z", "end": "2026-10-27T12:20Z", "family": "Target issue", "description": "For the duration of one measurement, the target PR-284 jumps by several pixels horizontally and vertically, then returns: the measured position has left its spot, with a high recognition error but under the threshold, so kept in the curve. Since 24 October around 14:20, the spot of PR-284 is clearly weaker (thumbnails of the 24th at 12:00 and 16:00, of the 27th at 12:00) and its recognition error has stayed high. False point to ignore; look at the state of the target PR-284 if the false points repeat.", "review": "2026-11-17", "analysis": "CLARIDEN_2026-10-20T0400_2026-11-01T0010"}
{"id": "CLARIDEN-36", "start": "2026-10-28T19:20Z", "end": "2026-10-28T20:10Z", "family": "Displacement", "description": "On the evening of the 28th, the low targets of row B go down by a step vertically, D-306-B above all, then D-304-B, and stay at this new level until the end of the batch; D-303-B and D-304-B also go down a little horizontally. The position in the image of D-306-B goes down a little relative to the other targets, no camera movement, nothing on the 19:00 and 20:00 images (the frame at the top of the image is still there). 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", "analysis": "CLARIDEN_2026-10-20T0400_2026-11-01T0010"}
{"id": "CLARIDEN-37", "start": "2026-10-29T14:50Z", "end": "2026-10-29T15:10Z", "family": "No data", "description": "One measurement is missing, for all sensors: the curves have a short gap; the station nevertheless synchronizes at that moment, normal voltage. The same gap falls at the same moment on the other stations measuring at that time (LENZSPITZE, NORDEND, SNCF01): a common cause outside the station (transmission or reception of the data), not a failure of the station; it is not established. The curves are missing over the range; nothing to do on the station.", "review": "2026-11-17", "analysis": "CLARIDEN_2026-10-20T0400_2026-11-01T0010"}
{"id": "CLARIDEN-65", "start": "2026-10-29T23:50Z", "end": "2026-10-30T00:10Z", "family": "Target issue", "description": "At midnight, D-302-B jumps vertically and a little horizontally and stays at this new level until the end of the batch; PR_BG, on the same prism, jumps in the opposite direction. The raw positions of the two sensors do not move, only their starting position has changed (the relative displacement jumps without any movement in the image): a configuration or processing change of these two sensors, not a movement of the structure. Check their configuration with the operator; do not read this jump as a movement, nor compare their curves before and after.", "analysis": "CLARIDEN_2026-10-20T0400_2026-11-01T0010"}
{"id": "CLARIDEN-66", "start": "2026-10-30T17:00Z", "end": "2026-10-30T17:50Z", "family": "No data", "description": "Four measurements are missing in less than an hour, for all sensors: the curves have a gap. The station's own record stops too: its minute-by-minute synchronizations are missing over the same half hour, while the 17:00 image exists and the voltage stays normal before and after, so it is not a lack of energy. The other stations measuring at that time (ALASKA, FLORIDA, JUNGFRAU, LENZSPITZE, NADELHORN, NORDEND, SNCF01, WYOMING) have their measurements: the cause is specific to the station, not established. The curves are missing over the range; nothing to do unless it repeats.", "analysis": "CLARIDEN_2026-10-20T0400_2026-11-01T0010"}
{"id": "CLARIDEN-68", "start": "2026-10-31T09:20Z", "end": "2026-10-31T15:00Z", "family": "Thermal displacement", "description": "The camera housing temperature rises a little in the late morning of the 31st, and the camera scale rises with it while the pan goes down, until early afternoon; they come back when the housing cools, mostly during the view obstruction of the early afternoon, labeled separately. The compensation absorbs most of it, but a few corrected curves follow a little over these hours and come back with it: D-301-C horizontally, D-304-C, D-303-C and D-304-B vertically. Only a light at the far end of the tunnel on the 12:00 image, nothing in front of the targets. Camera movement by thermal effect, deduced from its pose against the housing temperature; normal, nothing to do.", "analysis": "CLARIDEN_2026-10-20T0400_2026-11-01T0010"}
{"id": "CLARIDEN-69", "start": "2026-10-31T13:50Z", "end": "2026-10-31T15:10Z", "family": "Visibility", "description": "For one hour, the corrected curves of the usual group make a bump that comes back: D-301-C (horizontal), D-302-B and PR_BG (vertical), D-301-A, D-300-A, D-304-B, D-304-C, D-302_A, and for a moment the reference PR-295; the recognition error of a few sensors rises during the episode. Same signature as the other episodes of view obstruction at the station; cause not established. Curves to ignore over the range.", "analysis": "CLARIDEN_2026-10-20T0400_2026-11-01T0010"}
{"id": "CLARIDEN-70", "start": "2026-10-31T18:40Z", "end": "2026-10-31T20:00Z", "family": "Visibility", "description": "For the duration of a few measurements, the corrected curves of D-301-C, P-301-B, P-299-A, D-302-B and PR_BG, D-303-B make a bump that comes back, and the reference PR-295, which is seen less well from 18:50, leaves its level; it is rejected at 19:50 (its curve is missing at that measurement), without the targets moving because of it. View obstruction of cause not established; points to ignore.", "analysis": "CLARIDEN_2026-10-20T0400_2026-11-01T0010"}
{"id": "CLARIDEN-71", "start": "2026-10-31T22:20Z", "end": "2026-11-01T00:00Z", "family": "Visibility", "description": "The reference PR-295 is seen poorly: its spot is weaker (23:00 thumbnail), it is rejected at times and, between two rejections, it is poorly measured; the compensation changes basis, and at 22:50 many targets jump together then return, without any movement of their raw positions. Until 23:50, the curves of D-301-C, P-301-B, D-302-B and PR_BG stay shifted, then briefly cross to the other side, with the recognition error of several targets rising. The camera housing temperature drops clearly at that hour. Cause of the obstruction not established (same signature as the other episodes). The jumps are not a movement: curves to ignore over the range.", "analysis": "CLARIDEN_2026-10-20T0400_2026-11-01T0010"}
{"id": "CLARIDEN-65", "start": "2026-10-29T23:50Z", "end": "2026-10-30T00:10Z", "family": "Target issue", "description": "At midnight, D-302-B jumps vertically and a little horizontally and stays at this new level until the end of the batch; PR_BG, on the same prism, jumps in the opposite direction. The raw positions of the two sensors do not move, only their starting position has changed (the relative displacement jumps without any movement in the image): a configuration or processing change of these two sensors, not a movement of the structure. Check their configuration with the operator; do not read this jump as a movement, nor compare their curves before and after.", "review": "2026-11-18", "analysis": "CLARIDEN_2026-10-20T0400_2026-11-01T0010"}
{"id": "CLARIDEN-66", "start": "2026-10-30T17:00Z", "end": "2026-10-30T17:50Z", "family": "No data", "description": "Four measurements are missing in less than an hour, for all sensors: the curves have a gap. The station's own record stops too: its minute-by-minute synchronizations are missing over the same half hour, while the 17:00 image exists and the voltage stays normal before and after, so it is not a lack of energy. The other stations measuring at that time (ALASKA, FLORIDA, JUNGFRAU, LENZSPITZE, NADELHORN, NORDEND, SNCF01, WYOMING) have their measurements: the cause is specific to the station, not established. The curves are missing over the range; nothing to do unless it repeats.", "review": "2026-11-18", "analysis": "CLARIDEN_2026-10-20T0400_2026-11-01T0010"}
{"id": "CLARIDEN-68", "start": "2026-10-31T09:20Z", "end": "2026-10-31T15:00Z", "family": "Thermal displacement", "description": "The camera housing temperature rises a little in the late morning of the 31st, and the camera scale rises with it while the pan goes down, until early afternoon; they come back when the housing cools, mostly during the view obstruction of the early afternoon, labeled separately. The compensation absorbs most of it, but a few corrected curves follow a little over these hours and come back with it: D-301-C horizontally, D-304-C, D-303-C and D-304-B vertically. Only a light at the far end of the tunnel on the 12:00 image, nothing in front of the targets. Camera movement by thermal effect, deduced from its pose against the housing temperature; normal, nothing to do.", "review": "2026-11-18", "analysis": "CLARIDEN_2026-10-20T0400_2026-11-01T0010"}
{"id": "CLARIDEN-69", "start": "2026-10-31T13:50Z", "end": "2026-10-31T15:10Z", "family": "Visibility", "description": "For one hour, the corrected curves of the usual group make a bump that comes back: D-301-C (horizontal), D-302-B and PR_BG (vertical), D-301-A, D-300-A, D-304-B, D-304-C, D-302_A, and for a moment the reference PR-295; the recognition error of a few sensors rises during the episode. Same signature as the other episodes of view obstruction at the station; cause not established. Curves to ignore over the range.", "review": "2026-11-18", "analysis": "CLARIDEN_2026-10-20T0400_2026-11-01T0010"}
{"id": "CLARIDEN-70", "start": "2026-10-31T18:40Z", "end": "2026-10-31T20:00Z", "family": "Visibility", "description": "For the duration of a few measurements, the corrected curves of D-301-C, P-301-B, P-299-A, D-302-B and PR_BG, D-303-B make a bump that comes back, and the reference PR-295, which is seen less well from 18:50, leaves its level; it is rejected at 19:50 (its curve is missing at that measurement), without the targets moving because of it. View obstruction of cause not established; points to ignore.", "review": "2026-11-18", "analysis": "CLARIDEN_2026-10-20T0400_2026-11-01T0010"}
{"id": "CLARIDEN-71", "start": "2026-10-31T22:20Z", "end": "2026-11-01T00:00Z", "family": "Visibility", "description": "The reference PR-295 is seen poorly: its spot is weaker (23:00 thumbnail), it is rejected at times and, between two rejections, it is poorly measured; the compensation changes basis, and at 22:50 many targets jump together then return, without any movement of their raw positions. Until 23:50, the curves of D-301-C, P-301-B, D-302-B and PR_BG stay shifted, then briefly cross to the other side, with the recognition error of several targets rising. The camera housing temperature drops clearly at that hour. Cause of the obstruction not established (same signature as the other episodes). The jumps are not a movement: curves to ignore over the range.", "review": "2026-11-18", "analysis": "CLARIDEN_2026-10-20T0400_2026-11-01T0010"}
+49 -49
View File
@@ -3,9 +3,37 @@
{"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-106", "start": "2026-10-04T08:45Z", "end": "2026-10-04T16:30Z", "family": "Visibility", "description": "By day (04/10), sunny day (cast shadows on the wall on the image of 12:00): the corrected curves of the low targets fluctuate from one measurement to the next beyond their noise, mostly CV.4 (corr_x and corr_y), F4.2, BG.2, BG.3, with one-measurement jumps that come back at once; late in the morning, BG.3, F4.2, BG.2 and the P targets jump together in corr_x for one measurement; CV.2 and CV.4 are rejected at times (missing points). At night everything is calm again. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast, which makes the spots tremble (a fast noise, by day only, with the recognition error of these low targets rising), nothing in front of the targets on the images. Do not trust the small movements of these curves over the range; this is not a movement of the structure.", "review": "2026-11-18", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-9", "start": "2026-10-04T09:00Z", "end": "2026-10-05T06:30Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (04/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 all night, until the start of the next morning. 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-04T0000_2026-10-14T0645"}
{"id": "SNCF01-10", "start": "2026-10-05T06:30Z", "end": "2026-10-06T07:15Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (05/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 all night, until the start of the next morning. 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-04T0000_2026-10-14T0645"}
{"id": "SNCF01-107", "start": "2026-10-05T07:00Z", "end": "2026-10-05T15:15Z", "family": "Visibility", "description": "By day (05/10), sunny day (cast shadows on the image of 12:00): the corrected curves of the low targets fluctuate from one measurement to the next beyond their noise, the most strongly of the batch: CV.4 and CV.2 in both columns, F4.2, BG.3, and in late morning the corr_y of P1, P2, P3 jump together for one or two measurements; CV.2, CV.4 and F4.2 are rejected at times (missing points). Calm again before nightfall; the train of 16:00 is labelled apart. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast, which makes the spots tremble (a fast noise, by day only, with the recognition error of these low targets rising), nothing in front of the targets on the images. Do not trust the small movements of these curves over the range; this is not a movement of the structure.", "review": "2026-11-18", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-12", "start": "2026-10-05T15:45Z", "end": "2026-10-05T16:15Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 and some of the P) are rejected and their curves are missing; the references are affected too (BG.3.1 and R1 rejected), the compensation retains none of them, and the targets that stayed under the threshold (BG.2, BG.3, F4.5 and some P) jump in corr_x and corr_y for the time of the measurement. Everything comes back at the next measurement. Cause: a passage in front of the targets and the references, a train passing, blurred, in front of the wall and the targets, seen on the 16:00 image. The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-108", "start": "2026-10-06T07:00Z", "end": "2026-10-06T13:15Z", "family": "Visibility", "description": "By day (06/10), sunny morning (cast shadows on the image of 12:00): the corrected curves of the low targets fluctuate beyond their noise, mostly CV.4 in corr_x, F4.2 in both columns and CV.2, with one-measurement jumps that come back at once; CV.2 and CV.4 are rejected at times (missing points). The other targets stay within their noise; calm again from early afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast, which makes the spots tremble (a fast noise, by day only, with the recognition error of these low targets rising), nothing in front of the targets on the images. Do not trust the small movements of these curves over the range; this is not a movement of the structure.", "review": "2026-11-18", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-109", "start": "2026-10-06T07:15Z", "end": "2026-10-07T03:00Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (06/10), sunny day (cast shadows on the image of 12:00): from the morning, the pan and the tilt of the camera drop strongly and its scale rises, until early afternoon; they come back slowly in the afternoon, the evening and the first half of the night. The compensation absorbs only part of it: corr_x of P7 rises clearly, with corr_y of P6 and P7, while corr_x of P1 drops and that of P5 rises; the curves come back to their night level late in the evening, the pose in the night. 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-18", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-110", "start": "2026-10-07T07:30Z", "end": "2026-10-08T04:15Z", "family": "Thermal displacement", "description": "Weak daytime thermal cycle (07/10), overcast day (image of 12:00): in the morning, the pan and the tilt of the camera drop a little and its scale rises a little, then the camera stays in that position all afternoon; it comes back in the evening and all night, beyond its position of the previous night, until early on the 8th. The corrected curves follow, less than on the sunny days: corr_x of P5 and P7 rises, corr_y of P7 and P6 too, corr_x of P1 drops; P7 comes back late in the evening, P5 only after midnight. The three train passages of the day (13:00, 16:00, 19:45) are labelled apart. 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-18", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-111", "start": "2026-10-07T12:45Z", "end": "2026-10-07T13:15Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 except F4.5 and F4.6, and all the P) are rejected and their curves are missing; the references are affected too (R1 rejected, BG.3.1 just under its threshold and left out), the compensation retains none of them; the targets that stayed under the threshold jump a little beyond their noise, BG.3 in corr_x, F4.5 and F4.6 in corr_y. Everything comes back at the next measurement. Cause seen: a train passing in front of the wall and the targets, blurred, on the image of 13:00. The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-18", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-18", "start": "2026-10-07T15:45Z", "end": "2026-10-07T16:15Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 and some of the P) are rejected and their curves are missing; the references are affected too (BG.3.1 and R1 rejected), the compensation retains none of them, and the targets that stayed under the threshold (BG.2, BG.3, F4.5 and some P) jump in corr_x and corr_y for the time of the measurement. Everything comes back at the next measurement. Cause: a passage in front of the targets and the references, a train passing in front of the targets, seen on the 16:00 image. The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-19", "start": "2026-10-07T19:30Z", "end": "2026-10-07T20:00Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 and some of the P) are rejected and their curves are missing; the references are affected too (BG.3.1 rejected), the compensation retains none of them, and the targets that stayed under the threshold (BG.2, BG.3, F4.5 and some P) jump in corr_x and corr_y for the time of the measurement. Everything comes back at the next measurement. Cause: a passage in front of the targets and the references, no image at that moment; deduced from the signature, the same as that of the trains seen on the images of the other passages. The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-20", "start": "2026-10-08T06:45Z", "end": "2026-10-08T16:30Z", "family": "Visibility", "description": "By day (08/10): the corrected curves of all targets fluctuate much more than at night, from one measurement to the next, especially CV.2, CV.4, F4.2, BG.3, CV.6, CV.9, with one-measurement jumps that come back at once, and CV.2, CV.4 (sometimes F4.2) are rejected at times, their curves having gaps; their recognition error varies strongly by day. At night everything becomes calm again. Deduced cause: heat shimmer from the air heated above the tracks (a fast noise over the whole scene, by day only), not visible on the images; the 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.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-21", "start": "2026-10-08T08:15Z", "end": "2026-10-09T04:30Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (08/10), weak by day and prolonged at night: from the morning, the pan and the tilt of the camera drop a little and its scale rises; in the evening, the camera rises beyond its position of the previous night and comes back to it only on the morning of the 9th. The corrected curves follow, poorly compensated: corr_y of P5, P6, P7, P4 moves away from its night level during the day; in the evening and at night, corr_x of P1, P5, P6, P7 exceeds its level of the previous night in the other direction, until the morning of the 9th. 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-04T0000_2026-10-14T0645"}
{"id": "SNCF01-22", "start": "2026-10-09T01:45Z", "end": "2026-10-09T02:15Z", "family": "No data", "description": "One measurement is missing, for all sensors, around two in the morning: all curves have a gap; no image at that moment. The power metrics of the station are empty over the whole month. This one-measurement night gap, around 02:00 UTC, falls at the same measurement on FLORIDA and SNCF01 on 09, 14 and 15/10, and only on them; other stations have the same night gap around the same hour on 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": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-23", "start": "2026-10-09T07:00Z", "end": "2026-10-10T06:00Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (09/10), with no return in the evening: in the morning, the pan and the tilt of the camera drop and its scale rises, then the camera stays in that position all afternoon and evening; it comes back only slowly during the night, on the morning of the 10th. The corrected curves follow, poorly compensated: corr_x of P1, P2, P5, P6, P7 moves away from its night level during the day, stays away in the evening and comes back only on the morning of the 10th. 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-04T0000_2026-10-14T0645"}
{"id": "SNCF01-25", "start": "2026-10-10T01:45Z", "end": "2026-10-10T02:15Z", "family": "No data", "description": "One measurement is missing, for all sensors, around two in the morning: all curves have a gap; the image of that moment exists nonetheless. The power metrics of the station are empty over the whole month. This one-measurement night gap, around 02:00 UTC, falls at the same measurement on FLORIDA and SNCF01 on 09, 14 and 15/10, and only on them (that night, on SNCF01 alone); other stations have the same night gap around the same hour on 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": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-26", "start": "2026-10-10T07:00Z", "end": "2026-10-11T08:30Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (10/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 all night, until the start of the next morning. 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-04T0000_2026-10-14T0645"}
{"id": "SNCF01-112", "start": "2026-10-10T07:00Z", "end": "2026-10-10T13:00Z", "family": "Visibility", "description": "By day (10/10), sunny morning (cast shadows on the image of 12:00): the corrected curves of the low targets fluctuate beyond their noise, mostly CV.4 in both columns, CV.9 and CV.2 in corr_y, F4.2 and F4.5, and in mid-morning BG.3, P2, P3 jump together in corr_x for one measurement; they come back at once. Calm again from early afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast, which makes the spots tremble (a fast noise, by day only, with the recognition error of these low targets rising), nothing in front of the targets on the images. Do not trust the small movements of these curves over the range; this is not a movement of the structure.", "review": "2026-11-18", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-113", "start": "2026-10-11T10:00Z", "end": "2026-10-11T15:30Z", "family": "Visibility", "description": "By day (11/10), overcast day (image of 12:00), the weakest agitation of the batch that still crosses the noise: CV.4 in corr_y, F4.2, CV.2, and P1, P2 in corr_y make a few one-measurement jumps just beyond their noise, coming back at once; the train of 14:15 is labelled apart. Calm at night. Deduced cause: a weak shimmer of the air above the tracks by day, the same signature as on the sunny days, much weaker; nothing in front of the targets on the images. Do not trust the small movements of these curves over the range; this is not a movement of the structure.", "review": "2026-11-18", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-114", "start": "2026-10-11T08:30Z", "end": "2026-10-12T02:45Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (11/10), overcast day (image of 12:00): from the morning, the pan and the tilt of the camera drop and its scale rises, until early afternoon; they come back in the late afternoon, the evening and the first half of the night, beyond their position of the previous night. The compensation absorbs part of it: corr_x of P7 rises clearly, with corr_y of P6 and P5, while corr_x of P1 drops; the curves are back at their night level in the evening, the pose in the night. The train of 14:15 is labelled apart. 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-18", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-115", "start": "2026-10-11T14:00Z", "end": "2026-10-11T14:30Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 and all the P) are rejected and their curves are missing; the references are affected too (BG.3.1 and R1 rejected), the compensation retains none of them, and the targets that stayed under the threshold, BG.2, BG.3 and F4.5, jump strongly in corr_x and corr_y for the time of the measurement. Everything comes back at the next measurement. Cause: a passage in front of the targets and the references; the camera takes its image on the hour, none at that measurement; deduced from the signature, the same as that of the trains seen on the images of the other passages. The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-18", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-116", "start": "2026-10-12T06:30Z", "end": "2026-10-12T07:00Z", "family": "Obstruction", "description": "One single measurement, early in the morning: CV.8 and F4.2 go above their threshold (CV.6 too), their curves are missing, and the recognition error of most CV and F4 targets and of the reference BG.3.1 rises; CV.4, left under its threshold with its recognition error dropping, jumps clearly in corr_x for that measurement, and comes back at the next one. The references hold, the other targets stay within their noise. Cause deduced from the signature: a partial passage in front of the low targets, CV.4 latching onto a light or a reflection; no image at that measurement (the camera takes one on the hour). The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-18", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-117", "start": "2026-10-12T07:30Z", "end": "2026-10-12T14:45Z", "family": "Visibility", "description": "By day (12/10), sunny day (cast shadows on the image of 12:00): the corrected curves of the low targets fluctuate beyond their noise, mostly CV.4 in both columns, F4.2, CV.2, F4.5, F4.6, and in mid-morning BG.3, F4.2, F4.6, P2, P3, P4, P6 jump together in corr_x for one measurement; they come back at once; CV.2 and CV.4 are rejected at times (missing points). Calm again in the afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast, which makes the spots tremble (a fast noise, by day only, with the recognition error of these low targets rising), nothing in front of the targets on the images. Do not trust the small movements of these curves over the range; this is not a movement of the structure.", "review": "2026-11-18", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-33", "start": "2026-10-12T08:00Z", "end": "2026-10-14T04:00Z", "family": "Thermal displacement", "description": "Thermal cycle of 12 and 13/10, as one single episode: on the 12th, from the morning, the pan and the tilt of the camera drop and its scale rises; during the night from 12 to 13, the camera comes back only in part, and the corrected curves do not come back: corr_x of P1, P5, P6, P7 and corr_y of P4, P5, P6, P7 stay away from their night level all night, while the recognition error of the P rises a little; on the 13th, a second daytime dip is added to it, then everything comes back on the evening of the 13th and during the night, on the morning of the 14th. Deduced cause: the camera and its mount move with the heat of the day (camera pose); the night without return is not explained, no temperature being available. Nothing to do.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-118", "start": "2026-10-12T15:45Z", "end": "2026-10-12T16:15Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 and all the P) are rejected and their curves are missing; the references are affected too (BG.3.1 and R1 rejected), the compensation retains none of them, and the targets that stayed under the threshold, BG.2, BG.3 and F4.5, jump strongly in corr_x and corr_y for the time of the measurement. Everything comes back at the next measurement. Cause seen: a train passing in front of the wall and the targets, blurred, on the image of 16:00. The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-18", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-35", "start": "2026-10-13T01:45Z", "end": "2026-10-13T02:15Z", "family": "No data", "description": "One measurement is missing, for all sensors, around two in the morning: all curves have a gap; no image at that moment. The power metrics of the station are empty over the whole month. This one-measurement night gap, around 02:00 UTC, falls at the same measurement on FLORIDA and SNCF01 on 09, 14 and 15/10, and only on them (that night, on SNCF01 alone); other stations have the same night gap around the same hour on 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": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-119", "start": "2026-10-13T07:45Z", "end": "2026-10-13T14:00Z", "family": "Visibility", "description": "By day (13/10), sun and clouds (image of 12:00): the corrected curves of the low targets fluctuate beyond their noise, mostly CV.4 in corr_x, F4.2, F4.6, CV.2, and around midday P1, P2 and F4.2 jump together in corr_x for one measurement; they come back at once. Calm again in the afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast, which makes the spots tremble (a fast noise, by day only, with the recognition error of these low targets rising), nothing in front of the targets on the images. Do not trust the small movements of these curves over the range; this is not a movement of the structure.", "review": "2026-11-18", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-37", "start": "2026-10-14T01:15Z", "end": "2026-10-14T01:45Z", "family": "No data", "description": "One measurement is missing, for all sensors, around two in the morning: all curves have a gap. The power metrics of the station are empty over the whole month. This one-measurement night gap, around 02:00 UTC, falls at the same measurement on FLORIDA and SNCF01 on 09, 14 and 15/10, and only on them; other stations have the same night gap around the same hour on 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": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"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"}
{"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.", "review": "2026-11-18", "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.", "review": "2026-11-18", "analysis": "SNCF01_2026-10-14T0645_2026-10-22T1030"}
{"id": "SNCF01-41", "start": "2026-10-15T01:45Z", "end": "2026-10-15T02:45Z", "family": "No data", "description": "Two measurements are missing half an hour apart, with a single measurement between them, for all sensors, around two in the morning: all curves have a gap; the image of two o'clock exists nonetheless. The power metrics of the station are empty over the whole month. This one-measurement night gap, around 02:00 UTC, falls at the same measurement on FLORIDA and SNCF01 on 09, 14 and 15/10, and only on them; other stations have the same night gap around the same hour on 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": "SNCF01_2026-10-14T0645_2026-10-22T1030"}
{"id": "SNCF01-42", "start": "2026-10-15T05:15Z", "end": "2026-10-15T05:45Z", "family": "Displacement", "description": "One-measurement jump that lasts: on the 15th in the early morning, from one measurement to the next, the raw positions of all sensors, references included, jump together in the image (the tilt of the camera makes a step, which the pose then keeps), and the recognition error of P4, P7 and of the references R1, R2 goes up a notch. The compensation does not absorb it entirely: corr_y of P4, P5, P7, CV.1 and of the reference R1 drops at once, that of R2 rises, and these levels mostly remain on the following days. No image at that moment; cause not established (a jolt of the camera or of its mount, deduced from the pose). Relative to the overall movement, the targets move together with the camera, without moving relative to one another; the references R1 and R2 do not quite follow it, hence the remainder on the corrected curves. This is not an established movement of the structure: to be watched, on the camera and mount side.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-14T0645_2026-10-22T1030"}
{"id": "SNCF01-43", "start": "2026-10-15T08:15Z", "end": "2026-10-15T15:45Z", "family": "Visibility", "description": "By day (15/10): the corrected curves of all targets fluctuate much more than at night, from one measurement to the next, especially CV.2, CV.4, F4.2, BG.3, CV.6, CV.9, with one-measurement jumps that come back at once, and CV.2, CV.4 (sometimes F4.2) are rejected at times, their curves having gaps; their recognition error varies strongly by day. At night everything becomes calm again. Deduced cause: heat shimmer from the air heated above the tracks (a fast noise over the whole scene, by day only), not visible on the images; the 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.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-14T0645_2026-10-22T1030"}
@@ -16,73 +44,45 @@
{"id": "SNCF01-48", "start": "2026-10-16T11:30Z", "end": "2026-10-16T12:00Z", "family": "Obstruction", "description": "CV.4 makes a very large jump in corr_x and corr_y for the time of one measurement, its raw position jumping by several pixels, while CV.2 is rejected; everything comes back at the next measurement. Cause: probably a passage hiding these low targets, the system locking onto another spot; deduced (no image at that moment). The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-14T0645_2026-10-22T1030"}
{"id": "SNCF01-49", "start": "2026-10-16T13:30Z", "end": "2026-10-16T14:00Z", "family": "No data", "description": "One measurement is missing for all sensors, all curves have a gap; no image at that moment. The power metrics of the station are empty over the whole month. The same gap occurs at the same time on the other stations that measure at that time (FLORIDA, JUNGFRAU, NORDEND): a common cause outside the station (transmission or reception of the data), not a station failure; it is not established. The curves are missing over the range; nothing to do on the station.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-14T0645_2026-10-22T1030"}
{"id": "SNCF01-50", "start": "2026-10-16T14:15Z", "end": "2026-10-16T14:45Z", "family": "No data", "description": "One measurement is missing for all sensors, all curves have a gap; no image at that moment. The power metrics of the station are empty over the whole month. The same gap occurs at the same time on the other stations that measure at that time (CLARIDEN, FLORIDA, LENZSPITZE, NORDEND): a common cause outside the station (transmission or reception of the data), not a station failure; it is not established. The curves are missing over the range; nothing to do on the station.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-14T0645_2026-10-22T1030"}
{"id": "SNCF01-100", "start": "2026-10-16T15:45Z", "end": "2026-10-16T16:15Z", "family": "Obstruction", "description": "One single measurement: the CV, F4 and P targets are rejected and their curves are missing; the references BG.3.1 and R1 are rejected too, the compensation retains none of them, and the targets that stayed under their threshold, BG.2, BG.3 and F4.5, jump strongly in corr_x and corr_y for the time of the measurement, as does the reference R2. Everything comes back at the next measurement. Cause: a train passing in front of the targets and the references, seen blurred across the whole lower scene on the 16:00 image. The structure is not moving: point to ignore, nothing to do.", "analysis": "SNCF01_2026-10-14T0645_2026-10-22T1030"}
{"id": "SNCF01-100", "start": "2026-10-16T15:45Z", "end": "2026-10-16T16:15Z", "family": "Obstruction", "description": "One single measurement: the CV, F4 and P targets are rejected and their curves are missing; the references BG.3.1 and R1 are rejected too, the compensation retains none of them, and the targets that stayed under their threshold, BG.2, BG.3 and F4.5, jump strongly in corr_x and corr_y for the time of the measurement, as does the reference R2. Everything comes back at the next measurement. Cause: a train passing in front of the targets and the references, seen blurred across the whole lower scene on the 16:00 image. The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-18", "analysis": "SNCF01_2026-10-14T0645_2026-10-22T1030"}
{"id": "SNCF01-52", "start": "2026-10-17T07:30Z", "end": "2026-10-18T07:45Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (17/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 all night, until the start of the next morning; the rejections of F4.2 that night, labelled separately, do not affect the references and do not distort the pose. 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-53", "start": "2026-10-17T08:00Z", "end": "2026-10-17T16:45Z", "family": "Visibility", "description": "By day (17/10): the corrected curves of all targets fluctuate much more than at night, from one measurement to the next, especially CV.2, CV.4, F4.2, BG.3, CV.6, CV.9, with one-measurement jumps that come back at once, and CV.2, CV.4 (sometimes F4.2) are rejected at times, their curves having gaps; their recognition error varies strongly by day. At night everything becomes calm again. Deduced cause: heat shimmer from the air heated above the tracks (a fast noise over the whole scene, by day only), not visible on the images; the 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.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-14T0645_2026-10-22T1030"}
{"id": "SNCF01-54", "start": "2026-10-17T09:45Z", "end": "2026-10-17T10:15Z", "family": "Obstruction", "description": "CV.2 makes a very large jump in corr_x and corr_y for the time of one measurement, its raw position jumping by several pixels: another spot was taken for the target; CV.4 is rejected; everything comes back at the next measurement. Cause: a blurry, bright object passes in front of the bottom of the scene and hides CV.2 and CV.1, seen on the 10:00 image (thumbnails). The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-14T0645_2026-10-22T1030"}
{"id": "SNCF01-101", "start": "2026-10-18T07:45Z", "end": "2026-10-18T15:45Z", "family": "Visibility", "description": "By day (18/10): the corrected curves of all targets fluctuate much more than at night, from one measurement to the next, especially CV.2, CV.4, F4.2, BG.3, CV.6, CV.9, with one-measurement jumps that come back at once, and CV.2, CV.4 (sometimes F4.2) are rejected at times, their curves having gaps; their recognition error varies strongly by day. At night everything becomes calm again. Deduced cause: heat shimmer from the air heated above the tracks (a fast noise over the whole scene, by day only), not visible on the images; the 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-101", "start": "2026-10-18T07:45Z", "end": "2026-10-18T15:45Z", "family": "Visibility", "description": "By day (18/10): the corrected curves of all targets fluctuate much more than at night, from one measurement to the next, especially CV.2, CV.4, F4.2, BG.3, CV.6, CV.9, with one-measurement jumps that come back at once, and CV.2, CV.4 (sometimes F4.2) are rejected at times, their curves having gaps; their recognition error varies strongly by day. At night everything becomes calm again. Deduced cause: heat shimmer from the air heated above the tracks (a fast noise over the whole scene, by day only), not visible on the images; the 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.", "review": "2026-11-18", "analysis": "SNCF01_2026-10-14T0645_2026-10-22T1030"}
{"id": "SNCF01-56", "start": "2026-10-18T07:45Z", "end": "2026-10-19T00:00Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (18/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 evening. 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-59", "start": "2026-10-18T20:00Z", "end": "2026-10-18T20:30Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 and some of the P) are rejected and their curves are missing; the references are affected too (BG.3.1 and R1 rejected), the compensation retains none of them, and the targets that stayed under the threshold (BG.2, BG.3, F4.5 and some P) jump in corr_x and corr_y for the time of the measurement. Everything comes back at the next measurement. Cause: a passage in front of the targets and the references, no image at that moment; deduced from the signature, the same as that of the trains seen on the images of the other passages. The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-14T0645_2026-10-22T1030"}
{"id": "SNCF01-102", "start": "2026-10-19T07:15Z", "end": "2026-10-20T12:45Z", "family": "Displacement", "description": "On 19/10, an overcast day (images of 08:00 and 13:00, no sun on the wall), the camera moves in the morning and does not come back: its pan and tilt drop and its scale rises, then stay at their new level in the afternoon and at night, until the outage of 20/10. At the same time the targets move apart from each other in the image (residual relative to the overall movement): corr_x of P5, P6 and P7 rises and that of P2 drops clearly, and corr_y of P5 rises, through the afternoon and the night, while the residual of the compensation rises from late morning and the recognition error of the reference R1 from the late afternoon. No return before the outage; after it, on 21/10, P2 and P5 are still near their new levels. Not the daily thermal cycle: no sun, the pose does not come back, no temperature is available. Cause not established (a camera or reference movement that the compensation does not follow, or a movement of the scene). Movement of the structure not established: to monitor; part of the month-long drift labelled separately.", "analysis": "SNCF01_2026-10-14T0645_2026-10-22T1030"}
{"id": "SNCF01-102", "start": "2026-10-19T07:15Z", "end": "2026-10-20T12:45Z", "family": "Displacement", "description": "On 19/10, an overcast day (images of 08:00 and 13:00, no sun on the wall), the camera moves in the morning and does not come back: its pan and tilt drop and its scale rises, then stay at their new level in the afternoon and at night, until the outage of 20/10. At the same time the targets move apart from each other in the image (residual relative to the overall movement): corr_x of P5, P6 and P7 rises and that of P2 drops clearly, and corr_y of P5 rises, through the afternoon and the night, while the residual of the compensation rises from late morning and the recognition error of the reference R1 from the late afternoon. No return before the outage; after it, on 21/10, P2 and P5 are still near their new levels. Not the daily thermal cycle: no sun, the pose does not come back, no temperature is available. Cause not established (a camera or reference movement that the compensation does not follow, or a movement of the scene). Movement of the structure not established: to monitor; part of the month-long drift labelled separately.", "review": "2026-11-18", "analysis": "SNCF01_2026-10-14T0645_2026-10-22T1030"}
{"id": "SNCF01-61", "start": "2026-10-19T09:00Z", "end": "2026-10-19T10:15Z", "family": "No data", "description": "Several consecutive measurements are missing for all sensors, for an hour, all curves are missing; no image either. The power metrics of the station are empty over the whole month. The same gap occurs at the same time on the other stations that measure at that time (CLARIDEN, FLORIDA, JUNGFRAU, LENZSPITZE, NIEDERHORN, NORDEND): a common cause outside the station (transmission or reception of the data), not a station failure; it is not established. The curves are missing over the range; nothing to do on the station.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-14T0645_2026-10-22T1030"}
{"id": "SNCF01-63", "start": "2026-10-19T20:45Z", "end": "2026-10-19T21:15Z", "family": "No data", "description": "One measurement is missing for all sensors, all curves have a gap; no image at that moment. The power metrics of the station are empty over the whole month. The same gap occurs at the same time on the other stations that measure at that time (CLARIDEN, FLORIDA, JUNGFRAU, LENZSPITZE, NIEDERHORN, NORDEND): a common cause outside the station (transmission or reception of the data), not a station failure; it is not established. The curves are missing over the range; nothing to do on the station. The hourly metrics of BREITHORN, MICHIGAN and NEBRASKA are also missing at 21:00.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-14T0645_2026-10-22T1030"}
{"id": "SNCF01-103", "start": "2026-10-20T04:45Z", "end": "2026-10-20T08:00Z", "family": "Visibility", "description": "At night on 20/10, before dawn, the reference R1 is less well seen: its recognition error rises a notch at once and stays high until mid-morning, and its measured position slides alone in the image (the targets do not move relative to the overall movement). The compensation follows it: corr_y of P7, P6 and P5 rises together clearly for a few hours, while the reference R2 moves the other way, then everything comes back as the position of R1 returns, around eight. The train passage of that morning, labelled separately, falls inside. Nothing in front of R1 on the night images of 05:00, 06:00 and 07:00 (its spot whole, same place); the night is one of poor visibility for several faint targets (CV.6 rejected all night, F4.2 at times). Cause deduced: the reference less well seen in the night of poor visibility, not an obstacle. Do not trust the small shift of these curves over the range; this is not a movement of the structure.", "analysis": "SNCF01_2026-10-14T0645_2026-10-22T1030"}
{"id": "SNCF01-104", "start": "2026-10-20T05:30Z", "end": "2026-10-20T06:00Z", "family": "Obstruction", "description": "One single measurement: the CV, F4 and P targets are rejected and their curves are missing; the references BG.3.1 and R1 are rejected too, the compensation retains none of them, and the targets that stayed under their threshold, BG.2, BG.3, F4.5 and F4.6, jump strongly in corr_x and corr_y for the time of the measurement, as does the reference R2. Everything comes back at the next measurement. Cause: a passage in front of the targets and the references, deduced from the signature, the same as that of the train seen on the 16:00 image of 16/10 (no image at that minute). It falls inside the episode of the reference R1 of that morning, labelled separately. The structure is not moving: point to ignore, nothing to do.", "analysis": "SNCF01_2026-10-14T0645_2026-10-22T1030"}
{"id": "SNCF01-103", "start": "2026-10-20T04:45Z", "end": "2026-10-20T08:00Z", "family": "Visibility", "description": "At night on 20/10, before dawn, the reference R1 is less well seen: its recognition error rises a notch at once and stays high until mid-morning, and its measured position slides alone in the image (the targets do not move relative to the overall movement). The compensation follows it: corr_y of P7, P6 and P5 rises together clearly for a few hours, while the reference R2 moves the other way, then everything comes back as the position of R1 returns, around eight. The train passage of that morning, labelled separately, falls inside. Nothing in front of R1 on the night images of 05:00, 06:00 and 07:00 (its spot whole, same place); the night is one of poor visibility for several faint targets (CV.6 rejected all night, F4.2 at times). Cause deduced: the reference less well seen in the night of poor visibility, not an obstacle. Do not trust the small shift of these curves over the range; this is not a movement of the structure.", "review": "2026-11-18", "analysis": "SNCF01_2026-10-14T0645_2026-10-22T1030"}
{"id": "SNCF01-104", "start": "2026-10-20T05:30Z", "end": "2026-10-20T06:00Z", "family": "Obstruction", "description": "One single measurement: the CV, F4 and P targets are rejected and their curves are missing; the references BG.3.1 and R1 are rejected too, the compensation retains none of them, and the targets that stayed under their threshold, BG.2, BG.3, F4.5 and F4.6, jump strongly in corr_x and corr_y for the time of the measurement, as does the reference R2. Everything comes back at the next measurement. Cause: a passage in front of the targets and the references, deduced from the signature, the same as that of the train seen on the 16:00 image of 16/10 (no image at that minute). It falls inside the episode of the reference R1 of that morning, labelled separately. The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-18", "analysis": "SNCF01_2026-10-14T0645_2026-10-22T1030"}
{"id": "SNCF01-66", "start": "2026-10-20T12:45Z", "end": "2026-10-21T10:00Z", "family": "No data", "description": "Measurements are missing intermittently, then an outage of about twenty hours. No measurement for any sensor, all curves are missing; no image either. The power metrics of the station are empty over the whole month: the cause is not established (acquisition, power or transmission). If long outages repeat, check the power and the transmission of the station.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-14T0645_2026-10-22T1030"}
{"id": "SNCF01-67", "start": "2026-10-21T10:00Z", "end": "2026-10-21T15:45Z", "family": "Visibility", "description": "By day (21/10): the corrected curves of all targets fluctuate much more than at night, from one measurement to the next, especially CV.2, CV.4, F4.2, BG.3, CV.6, CV.9, with one-measurement jumps that come back at once, and CV.2, CV.4 (sometimes F4.2) are rejected at times, their curves having gaps; their recognition error varies strongly by day. At night everything becomes calm again. Deduced cause: heat shimmer from the air heated above the tracks (a fast noise over the whole scene, by day only), not visible on the images; the 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.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-14T0645_2026-10-22T1030"}
{"id": "SNCF01-105", "start": "2026-10-21T10:00Z", "end": "2026-10-21T19:30Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (21/10, sunny, between two measurement outages): in late morning the pan of the camera drops and its scale rises, then the camera comes back in the afternoon and its tilt rises in the evening. The compensation absorbs most of it, but not all: in the late afternoon and the evening, with the tilt rising, corr_x of P5 and P7 dips clearly below its level of the morning, then they come back at the isolated measurement after the gap. 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.", "analysis": "SNCF01_2026-10-14T0645_2026-10-22T1030"}
{"id": "SNCF01-105", "start": "2026-10-21T10:00Z", "end": "2026-10-21T19:30Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (21/10, sunny, between two measurement outages): in late morning the pan of the camera drops and its scale rises, then the camera comes back in the afternoon and its tilt rises in the evening. The compensation absorbs most of it, but not all: in the late afternoon and the evening, with the tilt rising, corr_x of P5 and P7 dips clearly below its level of the morning, then they come back at the isolated measurement after the gap. 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-18", "analysis": "SNCF01_2026-10-14T0645_2026-10-22T1030"}
{"id": "SNCF01-69", "start": "2026-10-21T19:30Z", "end": "2026-10-22T10:30Z", "family": "No data", "description": "Night outage, one single isolated measurement at the start. No measurement for any sensor, all curves are missing; no image either. The power metrics of the station are empty over the whole month: the cause is not established (acquisition, power or transmission). If long outages repeat, check the power and the transmission of the station.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-14T0645_2026-10-22T1030"}
{"id": "SNCF01-106", "start": "2026-10-04T08:45Z", "end": "2026-10-04T16:30Z", "family": "Visibility", "description": "By day (04/10), sunny day (cast shadows on the wall on the image of 12:00): the corrected curves of the low targets fluctuate from one measurement to the next beyond their noise, mostly CV.4 (corr_x and corr_y), F4.2, BG.2, BG.3, with one-measurement jumps that come back at once; late in the morning, BG.3, F4.2, BG.2 and the P targets jump together in corr_x for one measurement; CV.2 and CV.4 are rejected at times (missing points). At night everything is calm again. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast, which makes the spots tremble (a fast noise, by day only, with the recognition error of these low targets rising), nothing in front of the targets on the images. Do not trust the small movements of these curves over the range; this is not a movement of the structure.", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-9", "start": "2026-10-04T09:00Z", "end": "2026-10-05T06:30Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (04/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 all night, until the start of the next morning. 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-04T0000_2026-10-14T0645"}
{"id": "SNCF01-10", "start": "2026-10-05T06:30Z", "end": "2026-10-06T07:15Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (05/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 all night, until the start of the next morning. 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-04T0000_2026-10-14T0645"}
{"id": "SNCF01-107", "start": "2026-10-05T07:00Z", "end": "2026-10-05T15:15Z", "family": "Visibility", "description": "By day (05/10), sunny day (cast shadows on the image of 12:00): the corrected curves of the low targets fluctuate from one measurement to the next beyond their noise, the most strongly of the batch: CV.4 and CV.2 in both columns, F4.2, BG.3, and in late morning the corr_y of P1, P2, P3 jump together for one or two measurements; CV.2, CV.4 and F4.2 are rejected at times (missing points). Calm again before nightfall; the train of 16:00 is labelled apart. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast, which makes the spots tremble (a fast noise, by day only, with the recognition error of these low targets rising), nothing in front of the targets on the images. Do not trust the small movements of these curves over the range; this is not a movement of the structure.", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-12", "start": "2026-10-05T15:45Z", "end": "2026-10-05T16:15Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 and some of the P) are rejected and their curves are missing; the references are affected too (BG.3.1 and R1 rejected), the compensation retains none of them, and the targets that stayed under the threshold (BG.2, BG.3, F4.5 and some P) jump in corr_x and corr_y for the time of the measurement. Everything comes back at the next measurement. Cause: a passage in front of the targets and the references, a train passing, blurred, in front of the wall and the targets, seen on the 16:00 image. The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-108", "start": "2026-10-06T07:00Z", "end": "2026-10-06T13:15Z", "family": "Visibility", "description": "By day (06/10), sunny morning (cast shadows on the image of 12:00): the corrected curves of the low targets fluctuate beyond their noise, mostly CV.4 in corr_x, F4.2 in both columns and CV.2, with one-measurement jumps that come back at once; CV.2 and CV.4 are rejected at times (missing points). The other targets stay within their noise; calm again from early afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast, which makes the spots tremble (a fast noise, by day only, with the recognition error of these low targets rising), nothing in front of the targets on the images. Do not trust the small movements of these curves over the range; this is not a movement of the structure.", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-109", "start": "2026-10-06T07:15Z", "end": "2026-10-07T03:00Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (06/10), sunny day (cast shadows on the image of 12:00): from the morning, the pan and the tilt of the camera drop strongly and its scale rises, until early afternoon; they come back slowly in the afternoon, the evening and the first half of the night. The compensation absorbs only part of it: corr_x of P7 rises clearly, with corr_y of P6 and P7, while corr_x of P1 drops and that of P5 rises; the curves come back to their night level late in the evening, the pose in the night. 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.", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-110", "start": "2026-10-07T07:30Z", "end": "2026-10-08T04:15Z", "family": "Thermal displacement", "description": "Weak daytime thermal cycle (07/10), overcast day (image of 12:00): in the morning, the pan and the tilt of the camera drop a little and its scale rises a little, then the camera stays in that position all afternoon; it comes back in the evening and all night, beyond its position of the previous night, until early on the 8th. The corrected curves follow, less than on the sunny days: corr_x of P5 and P7 rises, corr_y of P7 and P6 too, corr_x of P1 drops; P7 comes back late in the evening, P5 only after midnight. The three train passages of the day (13:00, 16:00, 19:45) are labelled apart. 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.", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-111", "start": "2026-10-07T12:45Z", "end": "2026-10-07T13:15Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 except F4.5 and F4.6, and all the P) are rejected and their curves are missing; the references are affected too (R1 rejected, BG.3.1 just under its threshold and left out), the compensation retains none of them; the targets that stayed under the threshold jump a little beyond their noise, BG.3 in corr_x, F4.5 and F4.6 in corr_y. Everything comes back at the next measurement. Cause seen: a train passing in front of the wall and the targets, blurred, on the image of 13:00. The structure is not moving: point to ignore, nothing to do.", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-18", "start": "2026-10-07T15:45Z", "end": "2026-10-07T16:15Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 and some of the P) are rejected and their curves are missing; the references are affected too (BG.3.1 and R1 rejected), the compensation retains none of them, and the targets that stayed under the threshold (BG.2, BG.3, F4.5 and some P) jump in corr_x and corr_y for the time of the measurement. Everything comes back at the next measurement. Cause: a passage in front of the targets and the references, a train passing in front of the targets, seen on the 16:00 image. The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-19", "start": "2026-10-07T19:30Z", "end": "2026-10-07T20:00Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 and some of the P) are rejected and their curves are missing; the references are affected too (BG.3.1 rejected), the compensation retains none of them, and the targets that stayed under the threshold (BG.2, BG.3, F4.5 and some P) jump in corr_x and corr_y for the time of the measurement. Everything comes back at the next measurement. Cause: a passage in front of the targets and the references, no image at that moment; deduced from the signature, the same as that of the trains seen on the images of the other passages. The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-20", "start": "2026-10-08T06:45Z", "end": "2026-10-08T16:30Z", "family": "Visibility", "description": "By day (08/10): the corrected curves of all targets fluctuate much more than at night, from one measurement to the next, especially CV.2, CV.4, F4.2, BG.3, CV.6, CV.9, with one-measurement jumps that come back at once, and CV.2, CV.4 (sometimes F4.2) are rejected at times, their curves having gaps; their recognition error varies strongly by day. At night everything becomes calm again. Deduced cause: heat shimmer from the air heated above the tracks (a fast noise over the whole scene, by day only), not visible on the images; the 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.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-21", "start": "2026-10-08T08:15Z", "end": "2026-10-09T04:30Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (08/10), weak by day and prolonged at night: from the morning, the pan and the tilt of the camera drop a little and its scale rises; in the evening, the camera rises beyond its position of the previous night and comes back to it only on the morning of the 9th. The corrected curves follow, poorly compensated: corr_y of P5, P6, P7, P4 moves away from its night level during the day; in the evening and at night, corr_x of P1, P5, P6, P7 exceeds its level of the previous night in the other direction, until the morning of the 9th. 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-04T0000_2026-10-14T0645"}
{"id": "SNCF01-22", "start": "2026-10-09T01:45Z", "end": "2026-10-09T02:15Z", "family": "No data", "description": "One measurement is missing, for all sensors, around two in the morning: all curves have a gap; no image at that moment. The power metrics of the station are empty over the whole month. This one-measurement night gap, around 02:00 UTC, falls at the same measurement on FLORIDA and SNCF01 on 09, 14 and 15/10, and only on them; other stations have the same night gap around the same hour on 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": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-23", "start": "2026-10-09T07:00Z", "end": "2026-10-10T06:00Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (09/10), with no return in the evening: in the morning, the pan and the tilt of the camera drop and its scale rises, then the camera stays in that position all afternoon and evening; it comes back only slowly during the night, on the morning of the 10th. The corrected curves follow, poorly compensated: corr_x of P1, P2, P5, P6, P7 moves away from its night level during the day, stays away in the evening and comes back only on the morning of the 10th. 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-04T0000_2026-10-14T0645"}
{"id": "SNCF01-25", "start": "2026-10-10T01:45Z", "end": "2026-10-10T02:15Z", "family": "No data", "description": "One measurement is missing, for all sensors, around two in the morning: all curves have a gap; the image of that moment exists nonetheless. The power metrics of the station are empty over the whole month. This one-measurement night gap, around 02:00 UTC, falls at the same measurement on FLORIDA and SNCF01 on 09, 14 and 15/10, and only on them (that night, on SNCF01 alone); other stations have the same night gap around the same hour on 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": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-26", "start": "2026-10-10T07:00Z", "end": "2026-10-11T08:30Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (10/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 all night, until the start of the next morning. 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-04T0000_2026-10-14T0645"}
{"id": "SNCF01-112", "start": "2026-10-10T07:00Z", "end": "2026-10-10T13:00Z", "family": "Visibility", "description": "By day (10/10), sunny morning (cast shadows on the image of 12:00): the corrected curves of the low targets fluctuate beyond their noise, mostly CV.4 in both columns, CV.9 and CV.2 in corr_y, F4.2 and F4.5, and in mid-morning BG.3, P2, P3 jump together in corr_x for one measurement; they come back at once. Calm again from early afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast, which makes the spots tremble (a fast noise, by day only, with the recognition error of these low targets rising), nothing in front of the targets on the images. Do not trust the small movements of these curves over the range; this is not a movement of the structure.", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-113", "start": "2026-10-11T10:00Z", "end": "2026-10-11T15:30Z", "family": "Visibility", "description": "By day (11/10), overcast day (image of 12:00), the weakest agitation of the batch that still crosses the noise: CV.4 in corr_y, F4.2, CV.2, and P1, P2 in corr_y make a few one-measurement jumps just beyond their noise, coming back at once; the train of 14:15 is labelled apart. Calm at night. Deduced cause: a weak shimmer of the air above the tracks by day, the same signature as on the sunny days, much weaker; nothing in front of the targets on the images. Do not trust the small movements of these curves over the range; this is not a movement of the structure.", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-114", "start": "2026-10-11T08:30Z", "end": "2026-10-12T02:45Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (11/10), overcast day (image of 12:00): from the morning, the pan and the tilt of the camera drop and its scale rises, until early afternoon; they come back in the late afternoon, the evening and the first half of the night, beyond their position of the previous night. The compensation absorbs part of it: corr_x of P7 rises clearly, with corr_y of P6 and P5, while corr_x of P1 drops; the curves are back at their night level in the evening, the pose in the night. The train of 14:15 is labelled apart. 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.", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-115", "start": "2026-10-11T14:00Z", "end": "2026-10-11T14:30Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 and all the P) are rejected and their curves are missing; the references are affected too (BG.3.1 and R1 rejected), the compensation retains none of them, and the targets that stayed under the threshold, BG.2, BG.3 and F4.5, jump strongly in corr_x and corr_y for the time of the measurement. Everything comes back at the next measurement. Cause: a passage in front of the targets and the references; the camera takes its image on the hour, none at that measurement; deduced from the signature, the same as that of the trains seen on the images of the other passages. The structure is not moving: point to ignore, nothing to do.", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-116", "start": "2026-10-12T06:30Z", "end": "2026-10-12T07:00Z", "family": "Obstruction", "description": "One single measurement, early in the morning: CV.8 and F4.2 go above their threshold (CV.6 too), their curves are missing, and the recognition error of most CV and F4 targets and of the reference BG.3.1 rises; CV.4, left under its threshold with its recognition error dropping, jumps clearly in corr_x for that measurement, and comes back at the next one. The references hold, the other targets stay within their noise. Cause deduced from the signature: a partial passage in front of the low targets, CV.4 latching onto a light or a reflection; no image at that measurement (the camera takes one on the hour). The structure is not moving: point to ignore, nothing to do.", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-117", "start": "2026-10-12T07:30Z", "end": "2026-10-12T14:45Z", "family": "Visibility", "description": "By day (12/10), sunny day (cast shadows on the image of 12:00): the corrected curves of the low targets fluctuate beyond their noise, mostly CV.4 in both columns, F4.2, CV.2, F4.5, F4.6, and in mid-morning BG.3, F4.2, F4.6, P2, P3, P4, P6 jump together in corr_x for one measurement; they come back at once; CV.2 and CV.4 are rejected at times (missing points). Calm again in the afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast, which makes the spots tremble (a fast noise, by day only, with the recognition error of these low targets rising), nothing in front of the targets on the images. Do not trust the small movements of these curves over the range; this is not a movement of the structure.", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-33", "start": "2026-10-12T08:00Z", "end": "2026-10-14T04:00Z", "family": "Thermal displacement", "description": "Thermal cycle of 12 and 13/10, as one single episode: on the 12th, from the morning, the pan and the tilt of the camera drop and its scale rises; during the night from 12 to 13, the camera comes back only in part, and the corrected curves do not come back: corr_x of P1, P5, P6, P7 and corr_y of P4, P5, P6, P7 stay away from their night level all night, while the recognition error of the P rises a little; on the 13th, a second daytime dip is added to it, then everything comes back on the evening of the 13th and during the night, on the morning of the 14th. Deduced cause: the camera and its mount move with the heat of the day (camera pose); the night without return is not explained, no temperature being available. Nothing to do.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-118", "start": "2026-10-12T15:45Z", "end": "2026-10-12T16:15Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 and all the P) are rejected and their curves are missing; the references are affected too (BG.3.1 and R1 rejected), the compensation retains none of them, and the targets that stayed under the threshold, BG.2, BG.3 and F4.5, jump strongly in corr_x and corr_y for the time of the measurement. Everything comes back at the next measurement. Cause seen: a train passing in front of the wall and the targets, blurred, on the image of 16:00. The structure is not moving: point to ignore, nothing to do.", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-35", "start": "2026-10-13T01:45Z", "end": "2026-10-13T02:15Z", "family": "No data", "description": "One measurement is missing, for all sensors, around two in the morning: all curves have a gap; no image at that moment. The power metrics of the station are empty over the whole month. This one-measurement night gap, around 02:00 UTC, falls at the same measurement on FLORIDA and SNCF01 on 09, 14 and 15/10, and only on them (that night, on SNCF01 alone); other stations have the same night gap around the same hour on 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": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-119", "start": "2026-10-13T07:45Z", "end": "2026-10-13T14:00Z", "family": "Visibility", "description": "By day (13/10), sun and clouds (image of 12:00): the corrected curves of the low targets fluctuate beyond their noise, mostly CV.4 in corr_x, F4.2, F4.6, CV.2, and around midday P1, P2 and F4.2 jump together in corr_x for one measurement; they come back at once. Calm again in the afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast, which makes the spots tremble (a fast noise, by day only, with the recognition error of these low targets rising), nothing in front of the targets on the images. Do not trust the small movements of these curves over the range; this is not a movement of the structure.", "analysis": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-37", "start": "2026-10-14T01:15Z", "end": "2026-10-14T01:45Z", "family": "No data", "description": "One measurement is missing, for all sensors, around two in the morning: all curves have a gap. The power metrics of the station are empty over the whole month. This one-measurement night gap, around 02:00 UTC, falls at the same measurement on FLORIDA and SNCF01 on 09, 14 and 15/10, and only on them; other stations have the same night gap around the same hour on 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": "SNCF01_2026-10-04T0000_2026-10-14T0645"}
{"id": "SNCF01-70", "start": "2026-10-22T10:30Z", "end": "2026-10-22T13:30Z", "family": "No data", "description": "Between two outages, on 22/10 in late morning, measurements are missing intermittently: only a few isolated measurements arrive. No measurement for any sensor between them, all curves are missing; no image either. The power metrics of the station are empty over the whole month: the cause is not established (acquisition, power or transmission). If long outages repeat, check the power and the transmission of the station.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-120", "start": "2026-10-22T10:30Z", "end": "2026-10-22T15:30Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (22/10), over a few measurements between outages, under an overcast sky (13:30 and 14:00 images): the pan of the camera is low and its scale high until early afternoon, at their extreme at 13:30, then they begin to come back at the isolated 15:30 measurement, the tilt staying low. The corrected curves keep it: the corr_x of P5 and P7 and the corr_y of P6 stay clearly above their level of the previous evening all day, flat, and P7 starts to come back at 15:30, when the corrections of the references also shift a little. Deduced cause: the camera and its mount move with the heat of the day (camera pose), the compensation absorbing only part of it; the structure, a masonry wall, is not supposed to move like that. No temperature is available to confirm it. Normal, nothing to do.", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-120", "start": "2026-10-22T10:30Z", "end": "2026-10-22T15:30Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (22/10), over a few measurements between outages, under an overcast sky (13:30 and 14:00 images): the pan of the camera is low and its scale high until early afternoon, at their extreme at 13:30, then they begin to come back at the isolated 15:30 measurement, the tilt staying low. The corrected curves keep it: the corr_x of P5 and P7 and the corr_y of P6 stay clearly above their level of the previous evening all day, flat, and P7 starts to come back at 15:30, when the corrections of the references also shift a little. Deduced cause: the camera and its mount move with the heat of the day (camera pose), the compensation absorbing only part of it; 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-18", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-73", "start": "2026-10-22T15:00Z", "end": "2026-10-25T08:30Z", "family": "No data", "description": "One measurement is missing on 22/10 in the afternoon, then, after a single isolated measurement, an outage of nearly three days, until the morning of 25/10. No measurement for any sensor, all curves are missing; no image either. The power metrics of the station are empty over the whole month: the cause is not established (acquisition, power or transmission). If long outages repeat, check the power and the transmission of the station.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-121", "start": "2026-10-25T08:30Z", "end": "2026-10-25T13:15Z", "family": "Visibility", "description": "By day (25/10, from the resumption of the measurements), in the sun (sunny morning with passing clouds on the images of 09:00 to 13:00, sharp shadows on the wall): the corrected curves of the targets fluctuate from one measurement to the next much more than at night, with one-measurement jumps that come back at once, above all CV.4, F4.2, F4.6, CV.9 and P1, and the noisy F4.3;; CV.2 and CV.4 are rejected at times, their curves having gaps. The recognition error of most sensors, the references included, varies strongly from one measurement to the next, which it does not do at night nor on the overcast days (22/10, 26/10), when the curves stay calm. The jumps stop after 13:00, when the sky clouds over (14:00 image). Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast making the spots tremble (a fast noise over the whole scene, sunny hours only), not a nuisance seen on the images. Do not trust the small movements of these curves by day; this is not a movement of the structure.", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-121", "start": "2026-10-25T08:30Z", "end": "2026-10-25T13:15Z", "family": "Visibility", "description": "By day (25/10, from the resumption of the measurements), in the sun (sunny morning with passing clouds on the images of 09:00 to 13:00, sharp shadows on the wall): the corrected curves of the targets fluctuate from one measurement to the next much more than at night, with one-measurement jumps that come back at once, above all CV.4, F4.2, F4.6, CV.9 and P1, and the noisy F4.3;; CV.2 and CV.4 are rejected at times, their curves having gaps. The recognition error of most sensors, the references included, varies strongly from one measurement to the next, which it does not do at night nor on the overcast days (22/10, 26/10), when the curves stay calm. The jumps stop after 13:00, when the sky clouds over (14:00 image). Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast making the spots tremble (a fast noise over the whole scene, sunny hours only), not a nuisance seen on the images. Do not trust the small movements of these curves by day; this is not a movement of the structure.", "review": "2026-11-18", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-75", "start": "2026-10-25T08:30Z", "end": "2026-10-25T22:15Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (25/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 and the evening; measurements resumed in the morning after the outage. 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-22T1030_2026-11-01T0000"}
{"id": "SNCF01-122", "start": "2026-10-25T23:30Z", "end": "2026-10-26T00:00Z", "family": "Obstruction", "description": "At night (25/10 23:45), for the time of one measurement, the CV targets (CV.1, CV.2, CV.4, CV.5, CV.8, CV.9) and F4.2 are rejected together, their curves are missing; the recognition error of the references BG.3.1 and R1 and of P5 and P7 rises without crossing the threshold, and P7, left under its threshold, jumps clearly in corr_x for that measurement: its point is wrong. The other targets do not move; everything comes back at the next measurement. Cause: probably a passage in front of this part of the scene, deduced from the signature (no image at that moment, the images being on the hour). The structure is not moving: point to ignore, nothing to do.", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-123", "start": "2026-10-26T08:15Z", "end": "2026-10-26T22:00Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (26/10), under an overcast sky (12:00 image): from the morning, the pan and the tilt of the camera drop and its scale rises, less than on the sunny days, with no return before the 22:00 outage: the pan keeps dropping in the evening. The corrected curves keep part of it: the corr_x of P7 and P5 move clearly away from their night level during the day, P7 most at 10:00 when the tilt drops at once; in the evening they move further, during the episode labelled separately (Visibility). 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.", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-122", "start": "2026-10-25T23:30Z", "end": "2026-10-26T00:00Z", "family": "Obstruction", "description": "At night (25/10 23:45), for the time of one measurement, the CV targets (CV.1, CV.2, CV.4, CV.5, CV.8, CV.9) and F4.2 are rejected together, their curves are missing; the recognition error of the references BG.3.1 and R1 and of P5 and P7 rises without crossing the threshold, and P7, left under its threshold, jumps clearly in corr_x for that measurement: its point is wrong. The other targets do not move; everything comes back at the next measurement. Cause: probably a passage in front of this part of the scene, deduced from the signature (no image at that moment, the images being on the hour). The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-18", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-123", "start": "2026-10-26T08:15Z", "end": "2026-10-26T22:00Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (26/10), under an overcast sky (12:00 image): from the morning, the pan and the tilt of the camera drop and its scale rises, less than on the sunny days, with no return before the 22:00 outage: the pan keeps dropping in the evening. The corrected curves keep part of it: the corr_x of P7 and P5 move clearly away from their night level during the day, P7 most at 10:00 when the tilt drops at once; in the evening they move further, during the episode labelled separately (Visibility). 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-18", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-78", "start": "2026-10-26T14:30Z", "end": "2026-10-26T15:15Z", "family": "No data", "description": "Two measurements are missing for all sensors, all curves are missing; no image either. The power metrics of the station are empty over the whole month. The same gap occurs at the same time on the other stations that measure at that time (CLARIDEN, FLORIDA, JUNGFRAU, LENZSPITZE, NIEDERHORN, NORDEND), and their metrics are also missing at the same minutes: a common cause outside the station (transmission or reception of the data), not a station failure; it is not established. The curves are missing over the range; nothing to do on the station. The hourly metrics of BREITHORN, MICHIGAN and NEBRASKA are also missing at 15:00.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-124", "start": "2026-10-26T15:15Z", "end": "2026-10-26T22:00Z", "family": "Visibility", "description": "In late afternoon and in the evening (26/10), from the resumption after the common gap of 15:00 until the 22:00 outage: the corr_x of P5 and P6 and the corr_y of P6 rise steadily and clearly, while the corr_y of P4, P3, P1 and the corr_x of P1 go down, instead of coming back as on the other evenings; the camera pose does not come back either (the pan drops, the scale rises again) and the registration residual is at its highest of the range. From 17:00 the recognition error of the reference R2, of BG.3.1 and of P1, P3, CV.1, F4.2 rises markedly; F4.2 then CV.8 are rejected for a while, and at 18:15 most CV and F4 targets rise together. The night images of 16:00 to 21:00 show nothing clear, the scene as on the night before. After the outage, on 28/10, the curves are back at their level. Cause not established: references less well seen (a visibility drop over the scene is likely) that skew the compensation. Do not trust the curves over the range.", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-124", "start": "2026-10-26T15:15Z", "end": "2026-10-26T22:00Z", "family": "Visibility", "description": "In late afternoon and in the evening (26/10), from the resumption after the common gap of 15:00 until the 22:00 outage: the corr_x of P5 and P6 and the corr_y of P6 rise steadily and clearly, while the corr_y of P4, P3, P1 and the corr_x of P1 go down, instead of coming back as on the other evenings; the camera pose does not come back either (the pan drops, the scale rises again) and the registration residual is at its highest of the range. From 17:00 the recognition error of the reference R2, of BG.3.1 and of P1, P3, CV.1, F4.2 rises markedly; F4.2 then CV.8 are rejected for a while, and at 18:15 most CV and F4 targets rise together. The night images of 16:00 to 21:00 show nothing clear, the scene as on the night before. After the outage, on 28/10, the curves are back at their level. Cause not established: references less well seen (a visibility drop over the scene is likely) that skew the compensation. Do not trust the curves over the range.", "review": "2026-11-18", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-80", "start": "2026-10-26T22:00Z", "end": "2026-10-28T07:15Z", "family": "No data", "description": "Outage of more than a day, with a single isolated measurement on 27/10 at 14:00. No measurement for any sensor, all curves are missing; no image either. The power metrics of the station are empty over the whole month: the cause is not established (acquisition, power or transmission). If long outages repeat, check the power and the transmission of the station.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-82", "start": "2026-10-28T07:30Z", "end": "2026-10-28T22:45Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (28/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 and the evening; measurements resumed in the morning after the outage. 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-22T1030_2026-11-01T0000"}
{"id": "SNCF01-125", "start": "2026-10-28T08:00Z", "end": "2026-10-28T14:45Z", "family": "Visibility", "description": "By day (28/10), in the sun (full sun on the 12:00 image, sharp shadows on the wall): the corrected curves of the targets fluctuate from one measurement to the next much more than at night, with one-measurement jumps that come back at once, above all CV.4 and CV.2, then P2, P3 and CV.1;; CV.2 and CV.4 are rejected at times, their curves having gaps. The recognition error of most sensors, the references included, varies strongly from one measurement to the next, which it does not do at night nor on the overcast days (22/10, 26/10), when the curves stay calm. The jumps start in mid-morning, once the sun is on the scene, and stop in mid-afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast making the spots tremble (a fast noise over the whole scene, sunny hours only), not a nuisance seen on the images. Do not trust the small movements of these curves by day; this is not a movement of the structure.", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-125", "start": "2026-10-28T08:00Z", "end": "2026-10-28T14:45Z", "family": "Visibility", "description": "By day (28/10), in the sun (full sun on the 12:00 image, sharp shadows on the wall): the corrected curves of the targets fluctuate from one measurement to the next much more than at night, with one-measurement jumps that come back at once, above all CV.4 and CV.2, then P2, P3 and CV.1;; CV.2 and CV.4 are rejected at times, their curves having gaps. The recognition error of most sensors, the references included, varies strongly from one measurement to the next, which it does not do at night nor on the overcast days (22/10, 26/10), when the curves stay calm. The jumps start in mid-morning, once the sun is on the scene, and stop in mid-afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast making the spots tremble (a fast noise over the whole scene, sunny hours only), not a nuisance seen on the images. Do not trust the small movements of these curves by day; this is not a movement of the structure.", "review": "2026-11-18", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-83", "start": "2026-10-28T10:15Z", "end": "2026-10-28T10:45Z", "family": "Obstruction", "description": "CV.2 makes a very large jump in corr_x and corr_y for the time of one measurement, its raw position jumping by several pixels: another spot was taken for the target; CV.4 is rejected; everything comes back at the next measurement. Cause: probably a passage, like on 17/10 at 10:00; deduced (no image at that moment). The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-84", "start": "2026-10-28T21:00Z", "end": "2026-10-28T21:30Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 and some of the P) are rejected and their curves are missing; the references are affected too (BG.3.1 and R1 rejected), the compensation retains none of them, and the targets that stayed under the threshold (BG.2, BG.3, F4.5 and some P) jump in corr_x and corr_y for the time of the measurement. Everything comes back at the next measurement. Cause: a passage in front of the targets and the references, no image at that moment; deduced from the signature, the same as that of the trains seen on the images of the other passages. The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-85", "start": "2026-10-28T22:30Z", "end": "2026-10-28T23:00Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 and some of the P) are rejected and their curves are missing; the references are affected too (BG.3.1 and R1 rejected), the compensation retains none of them, and the targets that stayed under the threshold (BG.2, BG.3, F4.5 and some P) jump in corr_x and corr_y for the time of the measurement. Everything comes back at the next measurement. Cause: a passage in front of the targets and the references, no image at that moment; deduced from the signature, the same as that of the trains seen on the images of the other passages. The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-126", "start": "2026-10-29T07:45Z", "end": "2026-10-29T23:15Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (29/10), sunny day (12:00 image): from the morning, the pan and the tilt of the camera drop and its scale rises, then they slowly come back in the afternoon and the evening, the pan reaching its night level late in the evening. The corrected curves follow the same cycle, poorly compensated: the corr_y of P5 and P6 and the corr_x of P7, P6 and P5 move clearly away from their night level during the day, then come back gradually in the evening. 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.", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-127", "start": "2026-10-29T10:45Z", "end": "2026-10-29T15:30Z", "family": "Visibility", "description": "By day (29/10), in the sun (full sun on the 12:00 image, sharp shadows on the wall): the corrected curves of the targets fluctuate from one measurement to the next much more than at night, with one-measurement jumps that come back at once, above all CV.4, F4.2, CV.6, BG.3 and BG.2;; CV.2 and CV.4 are rejected at times, their curves having gaps. The recognition error of most sensors, the references included, varies strongly from one measurement to the next, which it does not do at night nor on the overcast days (22/10, 26/10), when the curves stay calm. The jumps start late in the morning and stop in mid-afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast making the spots tremble (a fast noise over the whole scene, sunny hours only), not a nuisance seen on the images. Do not trust the small movements of these curves by day; this is not a movement of the structure.", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-126", "start": "2026-10-29T07:45Z", "end": "2026-10-29T23:15Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (29/10), sunny day (12:00 image): from the morning, the pan and the tilt of the camera drop and its scale rises, then they slowly come back in the afternoon and the evening, the pan reaching its night level late in the evening. The corrected curves follow the same cycle, poorly compensated: the corr_y of P5 and P6 and the corr_x of P7, P6 and P5 move clearly away from their night level during the day, then come back gradually in the evening. 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-18", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-127", "start": "2026-10-29T10:45Z", "end": "2026-10-29T15:30Z", "family": "Visibility", "description": "By day (29/10), in the sun (full sun on the 12:00 image, sharp shadows on the wall): the corrected curves of the targets fluctuate from one measurement to the next much more than at night, with one-measurement jumps that come back at once, above all CV.4, F4.2, CV.6, BG.3 and BG.2;; CV.2 and CV.4 are rejected at times, their curves having gaps. The recognition error of most sensors, the references included, varies strongly from one measurement to the next, which it does not do at night nor on the overcast days (22/10, 26/10), when the curves stay calm. The jumps start late in the morning and stop in mid-afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast making the spots tremble (a fast noise over the whole scene, sunny hours only), not a nuisance seen on the images. Do not trust the small movements of these curves by day; this is not a movement of the structure.", "review": "2026-11-18", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-88", "start": "2026-10-29T14:45Z", "end": "2026-10-29T15:15Z", "family": "No data", "description": "One measurement is missing for all sensors, all curves have a gap, although the 15:00 image exists. The power metrics of the station are empty over the whole month. The same gap occurs at the same time on the other stations that measure at that time (CLARIDEN, LENZSPITZE, NORDEND): a common cause outside the station (transmission or reception of the data), not a station failure; it is not established. The curves are missing over the range; nothing to do on the station.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-89", "start": "2026-10-30T08:00Z", "end": "2026-10-31T07:45Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (30/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 all night, until the start of the next morning. 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-22T1030_2026-11-01T0000"}
{"id": "SNCF01-128", "start": "2026-10-30T09:15Z", "end": "2026-10-30T15:30Z", "family": "Visibility", "description": "By day (30/10), in the sun (full sun on the 12:00 image, sharp shadows on the wall): the corrected curves of the targets fluctuate from one measurement to the next much more than at night, with one-measurement jumps that come back at once, above all CV.2, then F4.2, CV.6, F4.6, F4.5 and CV.4;; CV.2 and CV.4 are rejected at times, their curves having gaps. The recognition error of most sensors, the references included, varies strongly from one measurement to the next, which it does not do at night nor on the overcast days (22/10, 26/10), when the curves stay calm. The jumps start in mid-morning and stop in mid-afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast making the spots tremble (a fast noise over the whole scene, sunny hours only), not a nuisance seen on the images. Do not trust the small movements of these curves by day; this is not a movement of the structure.", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-128", "start": "2026-10-30T09:15Z", "end": "2026-10-30T15:30Z", "family": "Visibility", "description": "By day (30/10), in the sun (full sun on the 12:00 image, sharp shadows on the wall): the corrected curves of the targets fluctuate from one measurement to the next much more than at night, with one-measurement jumps that come back at once, above all CV.2, then F4.2, CV.6, F4.6, F4.5 and CV.4;; CV.2 and CV.4 are rejected at times, their curves having gaps. The recognition error of most sensors, the references included, varies strongly from one measurement to the next, which it does not do at night nor on the overcast days (22/10, 26/10), when the curves stay calm. The jumps start in mid-morning and stop in mid-afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast making the spots tremble (a fast noise over the whole scene, sunny hours only), not a nuisance seen on the images. Do not trust the small movements of these curves by day; this is not a movement of the structure.", "review": "2026-11-18", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-91", "start": "2026-10-30T17:45Z", "end": "2026-10-30T18:15Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 and some of the P) are rejected and their curves are missing; the references are affected too (BG.3.1 and R1 rejected), the compensation retains none of them, and the targets that stayed under the threshold (BG.2, BG.3, F4.5 and some P) jump in corr_x and corr_y for the time of the measurement. Everything comes back at the next measurement. Cause: a passage in front of the targets and the references, a lit train passing: on the 18:00 night image, most of the spots have disappeared and large bright spots appear. The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-92", "start": "2026-10-30T18:15Z", "end": "2026-10-30T18:45Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 and some of the P) are rejected and their curves are missing; the references are affected too (BG.3.1 and R1 rejected), the compensation retains none of them, and the targets that stayed under the threshold (BG.2, BG.3, F4.5 and some P) jump in corr_x and corr_y for the time of the measurement. Everything comes back at the next measurement. Cause: a passage in front of the targets and the references, no image at that moment; deduced from the signature, the same as that of the trains seen on the images of the other passages. The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-17", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-129", "start": "2026-10-30T21:15Z", "end": "2026-10-30T22:00Z", "family": "Obstruction", "description": "Two measurements, at night (30/10): at 21:30, CV.2 is rejected, its curve is missing; the recognition error of the reference BG.3.1 rises markedly without crossing its threshold, the camera pose jumps (pan), and P3 clearly, P1 and BG.3 a little, jump in corr_x for the time of the measurement. At 21:45, F4.2 is rejected alone, its curve is missing; everything then comes back. Cause: probably a passage in front of the bottom of the scene and the reference BG.3.1, deduced from the signature, weaker than that of the trains (no image at that moment, the images being on the hour). The structure is not moving: point to ignore, nothing to do.", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-130", "start": "2026-10-31T07:45Z", "end": "2026-11-01T00:00Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (31/10), sunny day (12:00 and 13:00 images): from the morning, the pan and the tilt of the camera drop and its scale rises; at 12:30 the tilt also makes a step, labelled separately (Displacement). In the afternoon and the evening the pan and the scale come back slowly, the tilt only partly. The corrected curves follow the cycle, poorly compensated: the corr_y of P6, P5 and P4 and the corr_x of P7 and P5 move clearly away from their night level during the day; in the evening P7 comes back, but the corr_y of P6 and P5 stays clearly above its level of the previous nights until the end of the range. Deduced cause: the camera and its mount move with the heat of the day (camera pose), plus the step of the camera; the structure, a masonry wall, is not supposed to move like that. No temperature is available to confirm it. Normal, nothing to do; see the step of 12:30.", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-131", "start": "2026-10-31T08:15Z", "end": "2026-10-31T16:00Z", "family": "Visibility", "description": "By day (31/10), in the sun (full sun on the 12:00 and 13:00 images, sharp shadows on the wall): the corrected curves of the targets fluctuate from one measurement to the next much more than at night, with one-measurement jumps that come back at once, above all CV.4, P2, CV.2 and P1, then BG.3 and F4.2;; CV.2 and CV.4 are rejected at times, their curves having gaps. The recognition error of most sensors, the references included, varies strongly from one measurement to the next, which it does not do at night nor on the overcast days (22/10, 26/10), when the curves stay calm. The jumps start in the morning and stop in late afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast making the spots tremble (a fast noise over the whole scene, sunny hours only), not a nuisance seen on the images. Do not trust the small movements of these curves by day; this is not a movement of the structure.", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-132", "start": "2026-10-31T12:15Z", "end": "2026-10-31T12:45Z", "family": "Displacement", "description": "Step of the camera at 12:30 on 31/10, in full sun (12:00 and 13:00 images): the tilt of the camera jumps at once, far more steeply than in its daily cycle, and all the sensors, references and targets, shift together in the image; the targets move relative to each other only a little. The compensation does not erase it all: the corr_y of P6, P7, P5 and P3 steps up clearly at that measurement and stays there all afternoon. The tilt does not come back to its earlier night level, and the corr_y of P6 and P5 stays clearly above its level of the previous nights until the end of the range; at 17:00 the corrections of the references BG.3.1, R1 and R2 also shift relative to each other and stay. Cause not established (the camera or its mount moving in the sun is likely). It is not a movement of the structure; the camera is to be monitored, and the level of the following nights checked.", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-129", "start": "2026-10-30T21:15Z", "end": "2026-10-30T22:00Z", "family": "Obstruction", "description": "Two measurements, at night (30/10): at 21:30, CV.2 is rejected, its curve is missing; the recognition error of the reference BG.3.1 rises markedly without crossing its threshold, the camera pose jumps (pan), and P3 clearly, P1 and BG.3 a little, jump in corr_x for the time of the measurement. At 21:45, F4.2 is rejected alone, its curve is missing; everything then comes back. Cause: probably a passage in front of the bottom of the scene and the reference BG.3.1, deduced from the signature, weaker than that of the trains (no image at that moment, the images being on the hour). The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-18", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-130", "start": "2026-10-31T07:45Z", "end": "2026-11-01T00:00Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (31/10), sunny day (12:00 and 13:00 images): from the morning, the pan and the tilt of the camera drop and its scale rises; at 12:30 the tilt also makes a step, labelled separately (Displacement). In the afternoon and the evening the pan and the scale come back slowly, the tilt only partly. The corrected curves follow the cycle, poorly compensated: the corr_y of P6, P5 and P4 and the corr_x of P7 and P5 move clearly away from their night level during the day; in the evening P7 comes back, but the corr_y of P6 and P5 stays clearly above its level of the previous nights until the end of the range. Deduced cause: the camera and its mount move with the heat of the day (camera pose), plus the step of the camera; the structure, a masonry wall, is not supposed to move like that. No temperature is available to confirm it. Normal, nothing to do; see the step of 12:30.", "review": "2026-11-18", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-131", "start": "2026-10-31T08:15Z", "end": "2026-10-31T16:00Z", "family": "Visibility", "description": "By day (31/10), in the sun (full sun on the 12:00 and 13:00 images, sharp shadows on the wall): the corrected curves of the targets fluctuate from one measurement to the next much more than at night, with one-measurement jumps that come back at once, above all CV.4, P2, CV.2 and P1, then BG.3 and F4.2;; CV.2 and CV.4 are rejected at times, their curves having gaps. The recognition error of most sensors, the references included, varies strongly from one measurement to the next, which it does not do at night nor on the overcast days (22/10, 26/10), when the curves stay calm. The jumps start in the morning and stop in late afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast making the spots tremble (a fast noise over the whole scene, sunny hours only), not a nuisance seen on the images. Do not trust the small movements of these curves by day; this is not a movement of the structure.", "review": "2026-11-18", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
{"id": "SNCF01-132", "start": "2026-10-31T12:15Z", "end": "2026-10-31T12:45Z", "family": "Displacement", "description": "Step of the camera at 12:30 on 31/10, in full sun (12:00 and 13:00 images): the tilt of the camera jumps at once, far more steeply than in its daily cycle, and all the sensors, references and targets, shift together in the image; the targets move relative to each other only a little. The compensation does not erase it all: the corr_y of P6, P7, P5 and P3 steps up clearly at that measurement and stays there all afternoon. The tilt does not come back to its earlier night level, and the corr_y of P6 and P5 stays clearly above its level of the previous nights until the end of the range; at 17:00 the corrections of the references BG.3.1, R1 and R2 also shift relative to each other and stay. Cause not established (the camera or its mount moving in the sun is likely). It is not a movement of the structure; the camera is to be monitored, and the level of the following nights checked.", "review": "2026-11-18", "analysis": "SNCF01_2026-10-22T1030_2026-11-01T0000"}
@@ -0,0 +1,121 @@
# Labels: ALASKA, 2026-11-04T23:58Z → 2026-11-16T12:17Z (UTC)
Station context (not in `stations.md`, read from the data and the images): a camera under a bridge over a river (Geneva; MeteoSwiss Genève / Cointrin, 4.9 km, 411 m), looking along a row of piers carrying 12 targets (01 at 20 m to 11 at 231 m, 02 and 02_g on the same pier at 41 m), the far ones crowded at the end of the row (08–11 about 15 px apart). **Two references only**, `ref_av_01` and `ref_av_02`, on the far bank, to the right of the row and about 350 px apart: their `corr` is 0 by construction, `reproj_err` 0 from 2026-11-05 ~08:00 (tiny non-zero values before, no effect). Old camera: no image-quality columns (`quality.py` not applicable). Cadence 15 min, one IRON image per hour. Hints: none. No existing label in `labeling/auto/ALASKA.jsonl` (the file does not exist). The neighbouring camera WYOMING looks at the same piers (its reviewed labels coincide at several instants, below).
Method of the threshold. The own noise of every target (median |step|) is dominated by a **common jitter**: at each measurement all targets move together by a few noises (near targets more px, far targets more mm), because the two-reference compensation carries any small shift between the two references into all targets (`overview.py --rigid`: the references move against the rigid fit of the targets, the targets' residuals stay small). Literally, at least one target exceeds 5 noises (rolling ±8 measurements) at 60 instants of corr_y and 38 of corr_x, mostly one or two near targets in the tail of this jitter. To keep labels significant and the treatment the same everywhere, I labelled (scripts `scripts/common_dist.py`, `scripts/touched.py`):
- every moment where the **median of the targets** exceeds 5 noises (19 instants corr_y, 6 corr_x; the 99th percentile of the median is 5.7 noises), grouped into agitation episodes (same night, same mechanism; bounds on any target beyond 5 noises next to them);
- a target or group that clearly leaves the others (10 on 05/11, 04 on the cold spells), slow excursions beyond 5 noises lasting hours (13–15/11), the rain episode, and the No data.
What stays under (median below 5, a few targets at 5–7 noises) is listed in section 2.
## 1. My labels
### 2026-11-05T02:45Z → 2026-11-05T05:00Z
- **Phenomenon of the catalogue**: "A compensation on two references" (family of the cause; cause not established → Displacement, "The base changes without a reference lost").
- **Precedents**: MICHIGAN-8 (reviewed: agitation of all targets from the two-reference compensation, Displacement); FLORIDA-72 (reviewed: one-measurement jump, reference shifted alone, Displacement); WYOMING-9/-13/-17 (reviewed, neighbouring camera: far references jump alone, Displacement). Found by keyword search (see Difficulties).
- **Family**: Displacement: no cause seen (night image clean, reference error_value far from threshold, no rejection); not Visibility (no veil, error_value not up on most sensors).
- **Measured**: 03:00 corr_y median of targets +6.1 noises (9 targets 5–6.4 noises: 01–08, 02_g), 04:45 +5.0 (02, 03, 04, 05, 08, 09); back at the next measurement. Rigid residual of `ref_av_02` dy +0.14–0.15 px at 03:00–03:15, targets' median residual 0.02–0.03 px. `ref_av_01` error_value 0.048 at 03:00 (level 0.024). Pose without step. In mm: a few tenths of a mm on near targets to about 2 mm on far ones.
- **Images**: zone 1700,950,850,400 at 03:00: night, all spots sharp, nothing in front.
- **Confidence**: medium: the mechanism is clear, the threshold barely exceeded.
### 2026-11-05T08:45Z → 2026-11-05T09:15Z
- **Phenomenon of the catalogue**: "A pass-by hides the targets for the length of one measurement" (signature) vs "jump then return without cause"; kept Displacement.
- **Precedents**: WYOMING-10, WYOMING-18 (reviewed: one-measurement disturbance of two neighbouring targets, Obstruction deduced, no image at that instant). Here an image exists at the same minute and shows nothing, so the passage is not deduced.
- **Family**: Displacement (jump then return, cause not established); Obstruction would need the object seen or a deduction an existing image contradicts.
- **Measured**: corr_y of 10 +27 noises (+0.68 px, about 14 mm), 11 +16, 09 +12; corr_x of the far targets +3–4 noises; error_value of 10 0.075 (level 0.025), 08, 09, 11 up too; references at their level. Rigid residual dy of 10 +0.47 px, 11 +0.18, 09 +0.09: these targets move alone in the image. Back at 09:15.
- **Images**: thumbnails `--fixed` of 08–11, 06, the references at 08:00, 09:00, 10:00: spots intact, nothing in front at 09:00 (dawn lighting changing).
- **Confidence**: high on the event and bounds; cause unknown.
### 2026-11-05T23:45Z → 2026-11-06T07:30Z
- **Phenomenon of the catalogue**: "A compensation on two references".
- **Precedents**: MICHIGAN-8 (agitation over several measurements as one label), FLORIDA-72.
- **Family**: Displacement, as above.
- **Measured**: corr_x median +6.9 noises at 00:00 (06, 07, 08, 11 at +8), +5.4 at 00:45; corr_y +4.4 at 02:00 (4 near targets +5), −5.3 at 03:45 (01–05 at −6), −5.2 at 07:15 (05–11, 11 at −6.5). Rigid: `ref_av_01` dx −0.15 px at 00:00, `ref_av_02` dx +0.12 at 00:45, `ref_av_01` dy +0.11 at 07:15; references' error_value at level (0.021–0.030). Humid calm night (93–94 %).
- **Images**: zone at 00:00: clean night.
- **Confidence**: medium (agitation in 4 separate jumps; I grouped it as one night episode).
### 2026-11-05T23:45Z → 2026-11-08T10:00Z
- **Phenomenon of the catalogue**: "The structure expands and contracts with the temperature" (each target its amplitude, references stable), here a single target.
- **Precedents**: none useful for a single target following the temperature over days (WYOMING-1…8 are thermal labels of the camera and of a reference, another mechanism).
- **Family**: Thermal displacement: 04 follows the housing temperature as a trend and comes back at equal temperature (cold: 05–08/11 and 13–15/11 high; mild 08–12/11 low). Not Displacement "targets move slowly alone then come back" because the temperature explains it in both directions on both cold spells; medium confidence for that reason.
- **Measured**: corr_x of 04 vs its window level: ranges ≥ 5 noises on 06/11 00:00–00:45 (common), 02:30–03:00, 05:45–07:00, 07/11 03:30–06:15 (+8.0), 07:30–07:45, 20:45 → 08/11 03:30 (+11.3 noises at 23:45, +0.44 px ≈ 3.5 mm), 04:45–09:45 (+9.1). Night levels (`days.py`): 07/11 +0.195 px against −0.06…−0.12 on 08–12/11. Rigid residual dx of 04 (base 05/11 00:00): ≈0 on cold nights, −0.12…−0.19 by day, stuck at −0.2 px from 08/11 12:00 to 12/11; 03, 05 within ±0.05. Housing temperature 20.7–25 °C on the cold nights, 25–27 °C on 09–12/11. error_value of 04 at level (~0.11). The 01 night level also rises on 07/11 (+4 noises), not beyond.
- **Images**: thumbnails `--fixed` of 04 and 05 at 07/11 23:00, 08/11 05:00, 10/11 23:00: spots sharp, nothing in front, no shape change.
- **Confidence**: medium: clear in the data, the thermal link is a trend on two cold spells (r not computed per target), cause (support of the prism, pier) not seen.
### 2026-11-07T04:45Z → 2026-11-07T10:45Z
- **Phenomenon of the catalogue**: "A compensation on two references".
- **Precedents**: WYOMING-9 (reviewed, 07/11 04:45→05:15: far references jump alone, Displacement) at the same instant; MICHIGAN-8.
- **Family**: Displacement.
- **Measured**: corr_y median +7.2 noises at 05:00 (all 12 targets, 07 and 10 +9), +5.7 at 06:30 (11 targets), −4.4 at 09:30 (04–07), corr_x +5.8 and corr_y +6.8 at 10:00 (22 sensor-columns beyond 5), 10 +6 at 10:30. Rigid: `ref_av_01` dy −0.11 at 05:00, `ref_av_02` dy +0.14 and `ref_av_01` dx −0.08 at 10:00. References' error_value 0.024–0.030 (level).
- **Images**: zone at 05:00 (clean night) and 10:00 (sunny morning, spots sharp, no sun on the spots).
- **Confidence**: medium.
### 2026-11-07T22:45Z → 2026-11-08T09:00Z
- **Phenomenon of the catalogue**: "A compensation on two references".
- **Precedents**: WYOMING-11 (reviewed, 08/11 06:45→08:30, dawn after the coldest clear night, far prisms shift together, Displacement); MICHIGAN-8.
- **Family**: Displacement; considered Visibility (ref_av_01 error_value up all night ×2–3, near targets' error_value rising at dawn) but the boundary asks error_value rising on most sensors or a veil seen: neither (5–6 of 14 sensors, far from thresholds, images clean).
- **Measured**: 23:00 11 corr_x −5; 23:15 corr_y median −6.5 (10 −10.7, 11 −10); 23:45 corr_x +4.7 (5 targets +6); 03:15 corr_y −5.2 (07 −7.9); 04:30 corr_x −4.9; 05:30 corr_x +5.2; 06:45 mixed; 08:30 corr_y median +8.8 (06 +9.7, 02 +9.5) with corr_x −6.5; 08:45 02, 03, 04, 02_g +5–6; 09:00 back. Rigid: `ref_av_01` dy +0.21 at 23:15, `ref_av_02` dx/dy +0.16/+0.27 at 08:30 (pan at its maximum of the range at 08:30: the pose follows the references). Air 0–3 °C, humidity 95 % (Genève-Cointrin), housing 20.7 °C minimum at ~06:00.
- **Images**: zone at 23:00, 03:00, 07:00, 08:00: no veil, no obstacle, spots sharp; whole scene at dawn normal.
- **Confidence**: medium.
### 2026-11-10T08:15Z → 2026-11-10T09:00Z
- **Phenomenon of the catalogue**: "A gap common to several stations".
- **Precedents**: WYOMING-12 (reviewed, same bounds, same wording). It says "a synchronization falls in the gap" for WYOMING; for ALASKA `last_sync` shows syncs at 08:00, 08:15 then 09:00, none inside: I wrote "synchronizations resume at the next measurement".
- **Family**: No data (no measurement of any sensor).
- **Measured**: 08:30 and 08:45 absent for all 14 sensors; WYOMING the same two; CLARIDEN misses 08:30, LENZSPITZE 08:25–08:35, NADELHORN 08:25–08:30 and 08:40–08:45; FLORIDA, JUNGFRAU, NORDEND complete. BusVoltage 14.09 V (08:00), 14.01 V (09:00); `link` up.
- **Images**: 08:00 and 09:00 exist; none expected at 08:30 (hourly).
- **Confidence**: high.
### 2026-11-12T12:00Z → 2026-11-13T00:00Z
- **Phenomenon of the catalogue**: "Rain" plus "A compensation on two references" (the references poorly seen distort the base).
- **Precedents**: FLORIDA-65 (reviewed: night of rain, two references, one label for the episode); JUNGFRAU-116 (reviewed: references poorly seen in rain, targets slip, Visibility).
- **Family**: Visibility: veil seen on the image, error_value up on references and most targets.
- **Measured**: error_value of `ref_av_01` up to 0.59, `ref_av_02` 0.44 (levels 0.024, 0.023) from 11:15 to ~19:30 and again 21:30–23:45, 10–13 sensors above their usual band; 02 rejected at 12:00. corr_y: 12:15 a few targets ±5–6; 12:30 07–11 +5…+8; 12:45 median −8.0; 13:00 median −15.7 (02 −19.9 noises ≈ −5.6 mm, 04 −20.2, 11 −14.3 ≈ −7.7 mm); 13:15 back. 15:45–17:00 04 corr_y −11.6 (rigid dy −0.38 px: its own spot), 16:30–17:00 01, 02, 02_g, 03, 06 −6…−8; 19:45 09 −5.6; 23:15 02, 04 −5.7; 23:45 04 corr_x −5.1. Rigid at 13:00: `ref_av_02` dy −0.44 px. Rain 0.5–1.5 mm/h all day at Genève-Cointrin.
- **Images**: zone at 13:00: veiled grainy background, haloed spots (against 11/11 03:00 and 09/11 08:00 clean).
- **Confidence**: high on cause and core; the label spans the whole rainy afternoon and evening (one continuous nuisance, three bursts of exceedances).
### 2026-11-13T19:15Z → 2026-11-15T10:00Z
- **Phenomenon of the catalogue**: "The base changes without a reference lost" (slow part) and "A compensation on two references" (jumps).
- **Precedents**: WYOMING-17 (reviewed, 14/11 20:45→21:15, the same jump at 21:00); NEBRASKA-6 (reviewed, long common drift from the base, Displacement); MICHIGAN-8.
- **Family**: Displacement: targets do not move in the image; the base (ref_av_02 against the targets) changes; no established cause. Not Thermal: on the cold morning of 08/11 the common corr_y was low, not high, so it does not come back at equal temperature. Not Visibility: references' error_value at level or barely up, images without veil on the spots.
- **Measured**: slow common corr_y rise (hourly medians +1…+2 mm on 03–06, 04 most), ranges ≥ 5 noises: 04 13/11 19:30–19:45 and 23:15 → 14/11 09:30 (25 measurements, +8.1), 02/05/06 14/11 02:00–05:30 (+6.5…+7.6), single instants of 6–9 targets at 02:00, 03:15, 07:00, 09:30, 10:45; 04 19:15–22:15 (+11.5). Jumps: 17:30 corr_x median +6.0 (9 targets); 21:00 11 corr_x −14 noises (≈ −4 mm), 08–11 −6…−8, corr_y far targets −8…−10, both references' rigid residuals 0.24–0.33 px; 22:15 corr_y median +9.8 (02 +12); 23:00, 00:30, 01:15 (+6.7), 02:45 (−5.6), 04:00 (+7.9), 04:15, 06:00–06:30 (+5…+6); 15/11 06:45 02 +6, 09:30–09:45 04 corr_y +5.5; afterwards nothing beyond. Rigid: `ref_av_02` dy positive (+0.1…+0.38) through 14–15/11. Housing 20.2–22 °C; rain from 22:00 on 14/11 to 10:00 on 15/11 at Genève-Cointrin.
- **Images**: zone at 14/11 17:00, 21:00, 22:00, 15/11 04:00 (spots sharp, ref_av_02 a little smaller at 04:00); near-lens zone 0,0,1600,1100 with contrast at 21:00, 23:00, 01:00–07:00: background brighter from 23:00 (rain backscatter likely), lit objects close to the lens at 03:00 (blob) and 04:00 (streaks), far from the references.
- **Confidence**: medium: one label for a two-day episode mixing a slow base shift and many jumps; split by a reviewer is possible (WYOMING labelled 21:00 alone).
### 2026-11-14T03:00Z → 2026-11-15T09:30Z
- **Phenomenon of the catalogue**: as the 05–08/11 label of 04.
- **Precedents**: none useful.
- **Family**: Thermal displacement, same reasoning, same target, same family (labeling-rules 4).
- **Measured**: 04 corr_x ranges ≥ 5 noises: 14/11 03:15, 05:15, 09:45–10:30, 17:30, 21:15–21:45, 23:00–23:45, 15/11 01:00–02:00 (+9.2), 03:30, 04:45–09:15 (+8.9 at 08:00). Rigid dx of 04 ≈ 0…+0.06 on 13/11 06:00 → 15/11 06:00, then −0.14 at 12:00, −0.2 at 18:00 (warm position again); housing 20.2–22 °C then 29 °C on 15/11 ~13:00.
- **Images**: thumbnails `--fixed` 04/05 at 14/11 05:00, 15/11 08:00, 15/11 14:00: spot sharp.
- **Confidence**: medium.
## 2. What I left without a label
- **Common jitter under the median threshold** (all targets together, median of targets below 5 noises, a few targets 5–7): 09/11 06:45 (05, 09, 11 +5…+6); 10/11 04:30 (rain peak, 02 and 03 rejected, 05, 06, 08, 09 corr_x +5…+7, median +4.9: borderline); 10/11 06:30 and 13:00 (two targets −5…−7 corr_x); 11/11 14:30–17:30 (near targets 01, 02, 02_g, 03 ±5…+7 corr_y repeatedly, median up to −4.8 at 16:00: borderline, same mechanism); 14/11 12:00, 12:45 (2–3 targets +5…+6 corr_x); 15/11 21:00 (01, 02, 03 −6 in the evening rain and wind); 16/11 08:30 (05, 07, 09, 10 +5…+6). About 35 other instants where one target, mostly 01 or 02_g (the noisiest), touches 5–6 noises alone.
- **Rain night of 10/11 01:00–05:00**: error_value up on 10–14 sensors, 02 and 03 rejected at 04:30 (missing points, not labelled), corr at most the borderline 04:30 above.
- **Rain night of 15–16/11 (19:00 → 02:00, strong wind)**: error_value up on 9–11 sensors around 20:15; corr only 15/11 21:00 above.
- **Camera thermal cycle**: pan, scale follow the housing temperature (r −0.67 and +0.82 over the range), x raw of all sensors swings by up to 1.4 px on warm afternoons (05, 07, 08, 10, 11, 14, 15/11); compensated (corr flat at those hours), not labelled.
- **Slow tilt rise** 0.03 → 0.055° over the range: compensated.
- **Near targets' error_value ramps on cold nights** (01, 02, 03 on 07–08/11 and 13–14/11; 02 rejected 08/11 10:15, 14/11 21:15; 03 rejected 13/11 15:15): without effect beyond the noise apart from what is labelled.
- **Pose missing 16/11 00:30 → 12:15** (48 instants without registration in `camera/`) while the `corr` are present and calm: probably the camera file of 16/11 cut by the pumping; no effect on the curves.
- **reproj_err** tiny non-zero until 05/11 ~08:00 then exactly 0: a change of computation, no effect.
## 3. The documentation
- Helpful: `families.md` "A compensation on two references" and "The base changes without a reference lost"; `reading-rules.md` 5 (rigid reading first, neighbouring cameras read together); `overview.py --rigid` was decisive (references moving against the targets, target 04 moving alone, 10 moving alone). `labeling-rules.md` 4 (same target, same family across batches) for the two 04 labels. The weather (Genève-Cointrin) separated the rain days.
- Precedents: WYOMING's reviewed labels (neighbouring camera, same piers) fall at the same instants as three of my moments (05:00 on 07/11, dawn of 08/11, 21:00 on 14/11) and support Displacement for reference-driven jumps; WYOMING-12 for the common gap (I could not repeat its "synchronization in the gap" for ALASKA). FLORIDA-65 and JUNGFRAU-116 for rain on references.
- Missing / unclear: the 5-noise rule with the station's own noise does not fit a two-reference station whose noise is a common jitter with heavy tails: literally, 60 instants (corr_y) and 38 (corr_x) would be labelled, most of them one near target in the tail. I applied the threshold to the median of the targets (stated above); a rule on how to treat a common-mode jitter would help. The rules also do not say whether a night of intermittent jumps of the same mechanism is one agitation or one label per jump (FLORIDA labels each jump, MICHIGAN-8 groups three): I grouped per night.
- `stations.md` has no row for ALASKA (bridge over a river, two references on the far bank, neighbour WYOMING); worth adding.
- The housing temperature is `temperature_deg_c` only (all `sensor_*_deg_c` empty), which `metrics.py` uses as `temperature`.
## Difficulties
- `precedents.py` could not run: the Ollama container `ollama-bge-m3` is up but has no published port nor IP (`docker inspect`: Ports {}, no address), so `http://10.0.2.140:11435` refuses the connection. I did not restart it (shared service). Fallback: keyword search (`grep`) on `labeling/auto/*.jsonl` ("two references", WYOMING labels, the 10/11 gap). The precedents cited come from that search, not from the RAG.
## Sources read
- `instructions/analyst.md`, `tools/GUIDE.md`, `tools/DATA.md`, `labeling/families.md`, `labeling/labeling-rules.md`, `labeling/reading-rules.md`, `labeling/stations.md` (in full).
- `labeling/auto/ALASKA.jsonl`: absent. Keyword search in `labeling/auto/*.jsonl` (labels of MICHIGAN, NEBRASKA, BREITHORN, FLORIDA, JUNGFRAU, NORDEND, LENZSPITZE, WYOMING).
- Data: `data/ALASKA/` (displacement, camera, metrics, weather, targets.csv, images), and the displacement exports of 10/11 of the other stations (minutes of the gap).
- Tools: `inventory.py`, `overview.py` (default, `--rigid`, `--follow`), `ranges.py` (k 5, `--rolling 8`, `--instants 3`, `--min-measurements`), `summary.py`, `plot.py`, `days.py`, `metrics.py`, `stations.py` (ALASKA, WYOMING), `thumbnails.py` (sensors, `--fixed`, zones, `--contrast`), whole images of 05/11 09:00 and 15/11 04:00.
- Own scripts: `scripts/weather.py`, `scripts/devtable.py`, `scripts/common_dist.py`, `scripts/touched.py`, `scripts/slowfig.py`; outputs in `work/`.
@@ -0,0 +1,10 @@
{"start": "2026-11-05T02:45Z", "end": "2026-11-05T05:00Z", "family": "Perturbation", "description": "At night, the corr_y of almost all the targets jumps upward together for one measurement at 03:00, then again a little at 04:45 (05, 04, 03, 02, 08, 09 the most), and comes back at the next measurement each time. In the raw image the targets do not move against each other (rigid fit on the targets), while the reference ref_av_02 shifts slightly alone against them, its error_value at its level; the reference ref_av_01 is seen a little less well (error_value up, far from its threshold). The station runs its compensation on these two references only: their small relative shift passes into all the targets. Zone image of 03:00: night without obstacle, spots of the targets and of both references sharp. Cause of the reference shift not established. It is not a movement of the structure: points to ignore.", "review": "2026-11-18"}
{"start": "2026-11-05T08:45Z", "end": "2026-11-05T09:15Z", "family": "Perturbation", "description": "In the morning, for one measurement, the corr_y of the far target 10 jumps strongly upward, those of its neighbours 11 and 09 clearly, then all come back at the next measurement; their corr_x and that of 08 move a little. Their error_value rises at that measurement, those of 08 too, the other targets and the two references stay at their level; in the raw image only 10, and a little 11 and 09, move against the other prisms: these targets move alone in the image, the camera and the base do not. On the image of 09:00 nothing is seen in front of these four close-set spots at the end of the row of piers. Cause not established, probably a brief passage in front of the far targets (a bird) not caught on the image. Jump then return: points to ignore.", "review": "2026-11-18"}
{"start": "2026-11-05T23:45Z", "end": "2026-11-06T07:30Z", "family": "Perturbation", "description": "Agitation of the corrected curves during the night: all the targets jump together for one measurement at a time, in corr_x at midnight and at 00:45 (06, 07, 08, 11, 05 the most), then in corr_y at 03:45 (the near targets 01 to 05) and at 07:15 (the far targets 05 to 11), each time coming back at the next measurement. In the raw image the targets do not move against each other; the references ref_av_01 and ref_av_02 shift slightly against them in turn, without their error_value rising: the compensation, on these two references only, passes their difference into all the targets. Zone image of midnight: night without obstacle, spots sharp. Humid, calm night. Cause of the reference shifts not established. It is not a movement of the structure: points to ignore.", "review": "2026-11-18"}
{"start": "2026-11-05T23:45Z", "end": "2026-11-08T10:00Z", "family": "Thermal displacement", "description": "Target 04 alone sits higher in corr_x during the cold spell, strongly on the nights and mornings of 6 to 8 November, most on the night of 7 to 8 November, the coldest; the other targets do not follow. In the raw image 04 shifts sideways against all the other prisms (rigid fit on the targets): at its cold position at night, it moves back during the warmer hours, and returns for good to its warm position on 8 November in the morning when the housing temperature rises again, where it stays during the mild days that follow; on the next cold spell it does the same again. Its error_value stays at its level and the thumbnails of 7 November at 23:00 and 8 November at 05:00 show its spot sharp, nothing in front. Movement of target 04, or of its support, with the temperature, back at equal temperature: nothing to do.", "review": "2026-11-18"}
{"start": "2026-11-07T04:45Z", "end": "2026-11-07T10:45Z", "family": "Perturbation", "description": "At the end of the night and in the morning, the corr_y of all the targets jumps upward together for one measurement at 05:00 and at 06:30, then corr_x and corr_y together at 10:00 (05, 07, 08, 10 the most), each time back at the next measurement; at 09:30 and 10:30 a few targets still jump. In the raw image the targets do not move against each other; the references ref_av_01 and ref_av_02 shift slightly against them, their error_value at its level: the compensation, on these two references only, carries their difference into all the targets. Zone image of 05:00: night without obstacle; of 10:00: clear sunny morning, spots sharp. The neighbouring camera WYOMING, which looks at the same piers, shows a jump of its far references at 05:00. Cause not established. It is not a movement of the structure: points to ignore.", "review": "2026-11-18"}
{"start": "2026-11-07T22:45Z", "end": "2026-11-08T09:00Z", "family": "Perturbation", "description": "Agitation of the corrected curves during the cold, humid night of 7 to 8 November and at dawn: all the targets jump together for one measurement at a time, in corr_y downward at 23:15 (the far targets 10, 11, 08 the most) and at 03:15, in corr_x at 23:45, 04:30, 05:30 and 06:45, then strongly upward in corr_y with corr_x down at 08:30 (06, 02, 04, 03 the most), each time back at the next measurement or the one after. In the raw image the targets do not move against each other; the references shift slightly against them, ref_av_02 in particular, and the error_value of ref_av_01 is up all night, of the near targets 01, 02, 06, 07 at dawn, far from their thresholds. The compensation runs on these two references only and passes their difference into all the targets. Zone images of 23:00, 03:00, 07:00 and 08:00: no obstacle, no veil visible, spots sharp. The neighbouring camera WYOMING has a sudden shift of its far prisms at dawn the same morning. Cause not established (the cold air above the river is possible). It is not a movement of the structure: points to ignore.", "review": "2026-11-18"}
{"start": "2026-11-10T08:15Z", "end": "2026-11-10T09:00Z", "family": "No data", "description": "Two measurements missing for all sensors in the morning. WYOMING misses the same two measurements, and CLARIDEN, LENZSPITZE and NADELHORN measurements at the same minutes: a common cause outside the station (transmission or reception of the data), not a station failure; it is not established. The station runs: the voltage is normal before and after, its synchronizations resume at the next measurement, the images of 08:00 and 09:00 exist (one image per hour). Nothing to do on the station.", "review": "2026-11-18"}
{"start": "2026-11-12T12:00Z", "end": "2026-11-13T00:00Z", "family": "Visibility", "description": "Rainy day: the error_value of the two references ref_av_01 and ref_av_02 rises strongly from late morning to the evening, far under their threshold, with that of most targets; nothing is rejected. The image of 13:00 is veiled and grainy, the spots haloed. The poorly seen references distort the compensation, which runs on them two only: at 12:30 the far targets jump upward, then at 12:45 and 13:00 the corr_y of all the targets plunges strongly together (02, 04, 03, 02_g, 01 the most, the far targets clearly too, 01 and 06 in corr_x), and comes back at the next measurement; from 16:30 to 17:00 the near targets 04, 02_g, 02, 03, 01 dip again in corr_y, their own spots poorly seen, and a few targets still jump once at 23:15 and 23:45. Rain seen on the image of 13:00 and measured all day at Genève-Cointrin. Do not trust the curves over the range; it is not a movement.", "review": "2026-11-18"}
{"start": "2026-11-13T19:15Z", "end": "2026-11-15T10:00Z", "family": "Perturbation", "description": "During the cold days of 13 to 15 November, the corr_y of all the targets rises slowly together, of the same order in mm on all the targets, and stays high until the morning of the 15th (04 the most, then 02, 05, 06, 03), coming back during the day of the 15th; on top of it, the targets jump together for one measurement at a time, in corr_x upward at 17:30 on the 14th, both columns at 21:00 (the far target 11 strongly in corr_x), then in corr_y at 22:15 (01, 02, 03, 05 the most) and repeatedly through the night of 14 to 15 November, until 06:30. In the raw image the targets do not move against each other: it is the reference ref_av_02 that slides upward against them and jitters, ref_av_01 too at 21:00, their error_value at its level or barely up; the compensation, on these two references only, carries this into all the targets: the base changes. The night images show no obstacle in front of the spots; from 23:00 the night background is brighter and objects lit by the infrared light pass very close to the lens at 03:00 and 04:00, while rain is measured at Genève-Cointrin from 22:00. Cause of the reference slide not established. It is not a movement of the structure: points to ignore.", "review": "2026-11-18"}
{"start": "2026-11-14T03:00Z", "end": "2026-11-15T09:30Z", "family": "Thermal displacement", "description": "Target 04 alone sits higher in corr_x again during the cold spell of 14 and 15 November, as on 6 to 8 November: beyond its noise at night and in the morning, most on the morning of the 15th; the other targets do not follow. In the raw image 04 is back at its cold position against the other prisms (rigid fit on the targets) and returns to its warm position on the 15th around midday when the housing temperature rises clearly. Its error_value stays at its level and the thumbnails of 14 November at 05:00 and 15 November at 08:00 show its spot sharp, nothing in front. Movement of target 04, or of its support, with the temperature, back at equal temperature: nothing to do.", "review": "2026-11-18"}
Binary file not shown.

After

Width:  |  Height:  |  Size: 605 KiB

@@ -0,0 +1,52 @@
# ALASKA: brief jumps from the two references, one rainy day, one target that follows the cold
You asked for a full reading of 5 to 16 November, with no hints.
## In short
The bridge does not move. The corrected curves can be trusted most of the time. The exceptions are the rainy afternoon of 12 November, some nights when every target jumps together for one measurement at a time, and the cold days of 13 to 15 November. Target 04 alone shifts slightly on cold nights. This looks like a temperature effect on that target or on its support.
## What happened
**All targets jump together for one measurement (5, 6, 7–8 and 14–15 November, mostly at night).** Every target jumps in the same direction at the same moment. It lasts one measurement, and the curves are back at the next one. In the image the targets keep their positions relative to each other. What moves is one of the two reference points on the far bank, by a fraction of a pixel. The station corrects the camera's movement from these two points only, so any small shift between them is passed on to every target. That amounts to about one mm on the near targets and up to a few mm on the far ones. On 13 to 15 November, one reference also slid slowly. As a result, the vertical curves of all the targets sat 1 to 2 mm higher for two days, then came back. The images show nothing in front of the reference points. The neighbouring camera WYOMING, which looks at the same piers, shows the same jumps at several of the same instants. The jumps themselves are confirmed. Their cause is unknown (cold, humid air above the river is possible). They are not a movement of the bridge.
![References against the targets](references_vs_targets.png)
Top two panels: the green and orange lines (the two references) move away from the black line (the targets) at the moments of the jumps.
**Rain on 12 November, from late morning to the evening.** The image is veiled and the reference points are poorly seen. At 13:00 the vertical curves of all the targets drop together by 4 to 8 mm, then come back. The near targets dip again around 16:30. The cause, rain, is confirmed.
![12 November](ALASKA_corr_y_mm-error_value_01-02-04-06-08-10-11_20261112T0900Z_20261113T0100Z.png)
The deep dip at 13:00 comes at the same time as the measurement error rises on every target (bottom panel).
**Target 10 at 09:00 on 5 November.** For one measurement, the far target 10 jumps by about 14 mm, and its neighbours 09 and 11 jump less. All are back at the next measurement. The image of that minute shows nothing in front of them. The cause is unknown; a bird passing is possible.
**Target 04 follows the cold (6–8 and 14–15 November).** In the cold spells, target 04 alone sits 2 to 3 mm further sideways at night. It returns when it gets milder. Its spot stays sharp and nothing is in front of it. A temperature effect on the target or its support is likely.
![Target 04 and the temperature](target04_temperature.png)
Orange line (04), top panel: high during the two cold spells (housing temperature low, third panel) and low in the mild days between them.
**Two missing measurements on 10 November, 08:30 and 08:45.** WYOMING is missing the same ones, and other stations are missing measurements at those minutes too. The cause is outside the station (data transmission or reception). The station itself kept running.
## What to do
Nothing on site. With only two reference points, every small movement of one of them shows up on all the curves. A third reference on the far bank would make the correction much steadier.
## Not established
- Why the references shift on some nights (cold air or mist over the water, rain). It would take images taken at the same moment as the jumps, or a comparison with WYOMING night by night.
- Whether target 04 itself moves with the temperature or its support does. A visit to that pier would settle it.
## Labels
| Start (UTC) | End (UTC) | Family | Targets | In a few words |
|---|---|---|---|---|
| 2026-11-05 02:45 | 2026-11-05 05:00 | Displacement | all | jumps from the references, night |
| 2026-11-05 08:45 | 2026-11-05 09:15 | Displacement | 10, 11, 09 | one-measurement jump of the far targets |
| 2026-11-05 23:45 | 2026-11-06 07:30 | Displacement | all | night agitation from the references |
| 2026-11-05 23:45 | 2026-11-08 10:00 | Thermal displacement | 04 | 04 shifted during the cold spell |
| 2026-11-07 04:45 | 2026-11-07 10:45 | Displacement | all | jumps from the references, morning |
| 2026-11-07 22:45 | 2026-11-08 09:00 | Displacement | all | agitation in the cold night and at dawn |
| 2026-11-10 08:15 | 2026-11-10 09:00 | No data | all | gap shared with other stations |
| 2026-11-12 12:00 | 2026-11-13 00:00 | Visibility | all | rain, references poorly seen |
| 2026-11-13 19:15 | 2026-11-15 10:00 | Displacement | all | reference slides; curves high and jumping |
| 2026-11-14 03:00 | 2026-11-15 09:30 | Thermal displacement | 04 | 04 shifted during the cold spell |
@@ -0,0 +1,6 @@
{
"station": "ALASKA",
"start": "2026-11-04T23:58Z",
"end": "2026-11-16T12:17Z",
"hints": ""
}
@@ -0,0 +1,31 @@
"""Distribution of the common deviation: per instant, the median over the targets of the corr deviation (rolling +-N
measurements, in own noises) and the number of targets beyond K noises; lists the instants beyond K on the median.
usage: common_dist.py FOLDER START END COL [N] [K]"""
import sys, statistics as st
sys.path.insert(0, "tools/scripts")
import data
folder, start, end, col = sys.argv[1:5]
N = int(sys.argv[5]) if len(sys.argv) > 5 else 8
K = float(sys.argv[6]) if len(sys.argv) > 6 else 5
D = data.load(folder); S, E = data.parse_time(start), data.parse_time(end)
tg = [s for s in D if not data.is_reference(D[s])]
dev = {}
for s in tg:
vals = [(m["t"], m[col]) for m in D[s] if S <= m["t"] <= E]
v = [x for _, x in vals if x is not None]
noise = st.median(abs(a - b) for a, b in zip(v[1:], v[:-1]))
for i, (t, x) in enumerate(vals):
if x is None: continue
nb = [y for _, y in vals[max(0, i - N):i] + vals[i + 1:i + 1 + N] if y is not None]
dev.setdefault(t, {})[s] = (x - st.median(nb)) / noise
med = {t: st.median(d.values()) for t, d in dev.items()}
a = sorted(abs(x) for x in med.values())
n = len(a)
print(col, "instants", n, "|median dev| percentiles 50/90/99/99.9:", [round(a[int(p * (n - 1))], 1) for p in (.5, .9, .99, .999)])
for k in (3, 4, 5, 6, 8, 10):
print(f" instants with |median dev| > {k}: {sum(x > k for x in a)}; with >=1 target beyond {k}: {sum(any(abs(v) > k for v in d.values()) for d in dev.values())}")
print("instants with |median| >", K)
for t in sorted(med):
if abs(med[t]) > K:
d = dev[t]; mx = max(d, key=lambda s: abs(d[s]))
print(" ", data.iso(t), f"median {med[t]:+.1f}", f"n>{K}: {sum(abs(v) > K for v in d.values())}", f"max {mx} {d[mx]:+.1f}")
@@ -0,0 +1,40 @@
"""Per instant, each target's corr_x / corr_y deviation from a rolling median level (+-N measurements, itself excluded),
in its own noise (median |step| over the window), plus raw x, y medians and error_value of the refs.
usage: devtable.py FOLDER START END [N] [COL] [SHOW_START SHOW_END]"""
import sys, statistics as st
sys.path.insert(0, "tools/scripts")
import data
folder, start, end = sys.argv[1:4]
N = int(sys.argv[4]) if len(sys.argv) > 4 else 8
col = sys.argv[5] if len(sys.argv) > 5 else "corr_y"
s0 = data.parse_time(sys.argv[6]) if len(sys.argv) > 6 else None
s1 = data.parse_time(sys.argv[7]) if len(sys.argv) > 7 else None
D = data.load(folder)
S, E = data.parse_time(start), data.parse_time(end)
tg = [s for s in D if not data.is_reference(D[s])]
refs = [s for s in D if data.is_reference(D[s])]
series = {}
for s in tg:
ms = [m for m in D[s] if S <= m["t"] <= E]
vals = [(m["t"], m[col]) for m in ms]
v = [x for _, x in vals if x is not None]
noise = st.median(abs(a - b) for a, b in zip(v[1:], v[:-1]))
dev = {}
for i, (t, x) in enumerate(vals):
if x is None: dev[t] = None; continue
nb = [y for _, y in vals[max(0, i - N):i] + vals[i + 1:i + 1 + N] if y is not None]
dev[t] = (x - st.median(nb)) / noise
series[s] = dev
times = sorted({m["t"] for m in D[tg[0]] if S <= m["t"] <= E})
print("time " + " ".join(f"{s:>5}" for s in tg) + " | ev " + " ".join(refs))
for t in times:
if s0 and (t < s0 or t > s1): continue
row = []
for s in tg:
d = series[s].get(t)
row.append(" rej" if d is None else f"{d:5.1f}")
ev = []
for r in refs:
m = next((m for m in D[r] if m["t"] == t), None)
ev.append(f"{m['error_value']:.3f}" if m else "-")
print(data.iso(t), " ".join(row), " |", " ".join(ev))
@@ -0,0 +1,28 @@
"""Hourly median of corr_x_mm, corr_y_mm per target (minus its median over the window) against the housing temperature
and the pose scale. usage: slowfig.py FOLDER START END OUT.png [SENSORS]"""
import sys, statistics as st
from collections import defaultdict
sys.path.insert(0, "tools/scripts")
import data
import matplotlib; matplotlib.use("Agg"); import matplotlib.pyplot as plt
folder, start, end, out = sys.argv[1:5]
S, E = data.parse_time(start), data.parse_time(end)
D = data.load(folder)
sens = sys.argv[5].split(",") if len(sys.argv) > 5 else [s for s in D if not data.is_reference(D[s])]
fig, ax = plt.subplots(4, 1, figsize=(14, 12), sharex=True)
for s in sens:
for k, col in enumerate(("corr_x_mm", "corr_y_mm")):
h = defaultdict(list)
for m in D[s]:
if S <= m["t"] <= E and m[col] is not None:
h[m["t"].replace(minute=0, second=0, microsecond=0)].append(m[col])
ts = sorted(h); v = [st.median(h[t]) for t in ts]; md = st.median(v)
ax[k].plot(ts, [x - md for x in v], label=s, lw=1)
for k, c in enumerate(("corr_x_mm hourly median - level", "corr_y_mm hourly median - level")):
ax[k].set_ylabel(c); ax[k].grid(alpha=.3)
ax[0].legend(ncol=6, fontsize=7)
T = [(t, v) for t, v in data.load_temperature(folder) if S <= t <= E]
ax[2].plot([t for t, _ in T], [v for _, v in T], "k"); ax[2].set_ylabel("housing temperature"); ax[2].grid(alpha=.3)
C = [p for p in data.load_camera(folder) if S <= p["t"] <= E]
ax[3].plot([p["t"] for p in C], [p.get("scale") for p in C], lw=.6); ax[3].set_ylabel("cam scale"); ax[3].grid(alpha=.3)
fig.tight_layout(); fig.savefig(out, dpi=80); print(out)
@@ -0,0 +1,28 @@
"""For windows T1/T2, list the instants where targets exceed K noises (rolling +-N level) on corr_x or corr_y:
count, median of corr_x and corr_y deviations, and the sensors. usage: touched.py FOLDER START END T1/T2 [T1/T2 ...]"""
import sys, statistics as st
sys.path.insert(0, "tools/scripts")
import data
folder, start, end = sys.argv[1:4]; wins = sys.argv[4:]; N, K = 8, 5
D = data.load(folder); S, E = data.parse_time(start), data.parse_time(end)
tg = [s for s in D if not data.is_reference(D[s])]
dev = {}
for col in ("corr_x", "corr_y"):
for s in tg:
vals = [(m["t"], m[col]) for m in D[s] if S <= m["t"] <= E]
v = [x for _, x in vals if x is not None]
noise = st.median(abs(a - b) for a, b in zip(v[1:], v[:-1]))
for i, (t, x) in enumerate(vals):
if x is None: continue
nb = [y for _, y in vals[max(0, i - N):i] + vals[i + 1:i + 1 + N] if y is not None]
dev.setdefault(t, {}).setdefault(col, {})[s] = (x - st.median(nb)) / noise
for w in wins:
a, b = map(data.parse_time, w.split("/"))
print("==", w)
for t in sorted(dev):
if not a <= t <= b: continue
d = dev[t]; out = []
for col in ("corr_x", "corr_y"):
out += [f"{s}.{col[-1]}{d[col][s]:+.0f}" for s in tg if s in d.get(col, {}) and abs(d[col][s]) > K]
mx = st.median(d["corr_x"].values()); my = st.median(d["corr_y"].values())
print(" ", data.iso(t), f"med x {mx:+.1f} y {my:+.1f}", len(out), " ".join(out))
@@ -0,0 +1,13 @@
"""Summarise the hourly weather of a station over a range: precipitation, temperature, humidity, wind, sun, snow."""
import csv, glob, sys
folder, start, end = sys.argv[1:4]
rows = []
for f in sorted(glob.glob(f"{folder}/weather/*.csv")):
for r in csv.DictReader(open(f)):
if start <= r["time_utc"] <= end:
rows.append(r)
print("station:", rows[0]["station_name"], "distance_km:", rows[0]["distance_km"], "height_m:", rows[0]["height_m"])
print("time prec T hum wind gust sun rad snow")
for r in rows:
print(r["time_utc"], r["precipitation_mm"].rjust(4), r["temperature_c"].rjust(5), r["humidity_pct"].rjust(5),
r["wind_speed_kmh"].rjust(5), r["wind_gust_kmh"].rjust(5), r["sunshine_min"].rjust(3), r["global_radiation_wm2"].rjust(4), r["snow_depth_cm"])
Binary file not shown.

After

Width:  |  Height:  |  Size: 293 KiB

@@ -1,7 +1,7 @@
{"start": "2026-10-03T00:00Z", "end": "2026-10-04T20:00Z", "family": "Obstruction", "description": "From the morning of 3 October to the late afternoon of 4 October, the reference REFPOU22 is rejected together with the targets COLH20''' and POUI22: on the thumbnails and the images of those hours, the three spots are hidden behind an object with light reflections in vertical bands, a vehicle parked in front of the bottom of the scene. With one reference fewer, the compensation runs on the three others, and the corr_x of the reference REFH22 shifts clearly beyond its noise as soon as REFPOU22 is lost, stays shifted for the whole parking, then comes back to its level at the evening measurement of the 4th, when the three spots return without offset. The other targets keep their level within the noise. A change of the compensation basis caused by the hidden reference, not a movement: the structure does not move, nothing to do."}
{"start": "2026-10-03T00:00Z", "end": "2026-10-04T20:00Z", "family": "Obstruction", "description": "From the morning of 3 October to the late afternoon of 4 October, the reference REFPOU22 is rejected together with the targets COLH20''' and POUI22: on the thumbnails and the images of those hours, the three spots are hidden behind an object with light reflections in vertical bands, a vehicle parked in front of the bottom of the scene. With one reference fewer, the compensation runs on the three others, and the corr_x of the reference REFH22 shifts clearly beyond its noise as soon as REFPOU22 is lost, stays shifted for the whole parking, then comes back to its level at the evening measurement of the 4th, when the three spots return without offset. The other targets keep their level within the noise. A change of the compensation basis caused by the hidden reference, not a movement: the structure does not move, nothing to do.", "review": "2026-11-18"}
{"start": "2026-10-04T12:00Z", "end": "2026-10-04T20:00Z", "family": "Obstruction", "description": "For the duration of one measurement, on 4 October in the late afternoon, all the targets jump together in corr_x and in corr_y, then return at the next measurement. At that measurement, POUI24 is rejected in turn (curve absent), COLI22 jumps clearly in corr_y, and the reference REFH22, half hidden, rises clearly in error_value without being discarded, which distorts the basis of all the targets; COLH20''', POUI22 and REFPOU22 remain hidden by the vehicle parked since the day before. On the image of that hour, the banded reflections have disappeared and a light shines under POUI22: the obstacle has changed position in front of the bottom of the scene. The jumps are not a movement: point to ignore, nothing to do.", "review": "2026-11-17"}
{"start": "2026-10-05T00:00Z", "end": "2026-10-05T12:00Z", "family": "Thermal displacement", "description": "On 5 October in the morning, over two measurements, the camera scale and rotation deviate, then return at noon; at the same time the reference REFPOU22 and COLH20 rise clearly in corr_y while the references REFG44N and REFI'21 go down, then everything returns at noon. The images of 08:00 and 16:00 are alike, nothing obstructs the view; the error_value change little (the reference REFG44N rises a little, far from its threshold). This falls at the trough of the camera housing temperature, read in the metrics, and comes back when it rises: the same signature as the reviewed cold mornings of later in October. Thermal effect on the camera, incompletely compensated, according to the expert it is the housing temperature that matters, not the air temperature. Nothing to fear for the structure, nothing to do; do not trust these points."}
{"start": "2026-10-05T20:00Z", "end": "2026-10-06T12:00Z", "family": "Thermal displacement", "description": "From midnight to the morning of 6 October, over three measurements, the camera scale and rotation deviate, most at 08:00, then return at noon; the reference REFPOU22 and COLH20 rise clearly in corr_y, the references REFG44N and REFI'21 go down a little, then everything returns at noon. Nothing obstructs the targets on the 08:00 image (only a small light at the far left of the scene, away from the spots); the error_value change little. This falls when the camera housing temperature drops, read in the metrics, and comes back when it rises: the same signature as the reviewed cold mornings of later in October. Thermal effect on the camera, incompletely compensated, according to the expert it is the housing temperature that matters. Nothing to fear for the structure, nothing to do; do not trust these points."}
{"start": "2026-10-05T00:00Z", "end": "2026-10-05T12:00Z", "family": "Thermal displacement", "description": "On 5 October in the morning, over two measurements, the camera scale and rotation deviate, then return at noon; at the same time the reference REFPOU22 and COLH20 rise clearly in corr_y while the references REFG44N and REFI'21 go down, then everything returns at noon. The images of 08:00 and 16:00 are alike, nothing obstructs the view; the error_value change little (the reference REFG44N rises a little, far from its threshold). This falls at the trough of the camera housing temperature, read in the metrics, and comes back when it rises: the same signature as the reviewed cold mornings of later in October. Thermal effect on the camera, incompletely compensated, according to the expert it is the housing temperature that matters, not the air temperature. Nothing to fear for the structure, nothing to do; do not trust these points.", "review": "2026-11-18"}
{"start": "2026-10-05T20:00Z", "end": "2026-10-06T12:00Z", "family": "Thermal displacement", "description": "From midnight to the morning of 6 October, over three measurements, the camera scale and rotation deviate, most at 08:00, then return at noon; the reference REFPOU22 and COLH20 rise clearly in corr_y, the references REFG44N and REFI'21 go down a little, then everything returns at noon. Nothing obstructs the targets on the 08:00 image (only a small light at the far left of the scene, away from the spots); the error_value change little. This falls when the camera housing temperature drops, read in the metrics, and comes back when it rises: the same signature as the reviewed cold mornings of later in October. Thermal effect on the camera, incompletely compensated, according to the expert it is the housing temperature that matters. Nothing to fear for the structure, nothing to do; do not trust these points.", "review": "2026-11-18"}
{"start": "2026-10-07T08:00Z", "end": "2026-10-07T16:00Z", "family": "Obstruction", "description": "For the duration of one measurement, on 7 October at noon, the reference REFI'21 is rejected: on the image, a vehicle with reflective strips passes on the left of the scene and hides the group of REFI'21. The compensation runs on three references, the basis changes: several targets (POUI19, COLJ19, COLI20, COLI22, COLI24, POUI24) jump a little, mostly in corr_y, then return at the next measurement. This is not a movement: point to ignore.", "review": "2026-11-17"}
{"start": "2026-10-07T16:00Z", "end": "2026-10-08T04:00Z", "family": "Obstruction", "description": "On the night of 7 to 8 October, COLI24 is rejected from the evening, then COLI22 and POUI22 too around midnight (curves absent); POUI22 jumps in the evening and POUI24, half hidden, jumps clearly in corr_y around midnight. On the thumbnails, these spots are hidden or reduced, and a vehicle is visible in front of the bottom of the scene. Everything comes back in the morning. The structure does not move: ignore these targets over the range.", "review": "2026-11-17"}
{"start": "2026-10-08T20:00Z", "end": "2026-10-09T08:00Z", "family": "Obstruction", "description": "On the night of 8 to 9 October, the curves of COLI22, COLI24 and POUI22 are missing (measurements rejected) and the reference REFH22 is rejected too; POUI24, half hidden, jumps in corr_x and in corr_y. On the thumbnails, these spots are hidden and a parked vehicle is visible in front of the bottom of the scene, the image veiled by its light. The compensation runs on three references without making the other targets jump. Everything comes back in the morning: ignore these targets over the range, the structure does not move.", "review": "2026-11-17"}
@@ -1,8 +1,30 @@
# Requalification of the long labels: BREITHORN
Measured 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).
Measured with `tools/scripts/ranges.py --columns corr_x,corr_y` (k 5, merge 12h) on each label's range, with level = median of the range and noise = the sensor's own noise (work/ranges_*.txt, work/ranges_all_*.txt). Parallax: `scripts/parallax.py` and `scripts/parallax_fit.py` (work/parallax.txt, work/parallax_fit.txt).
- **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.
- **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.
- **BREITHORN-2**: corrected (parallax). The drift goes beyond the threshold: on corr_x, POUI19 reaches +11.1 noises (12/10 12:00, about +0.3 mm) and COLJ19 +7.7 noises. The description now gives the parallax as the deduced cause and names POUI22 (opposite in corr_y).
- **BREITHORN-13**: corrected (parallax, plus the period analysts' correction). The drift goes beyond the threshold: on corr_x, COLH20 reaches +12.6 noises (about +0.8 mm), COLJ19 +8.2 and POUI19 +7.3. COLI22, COLH20''' and POUI24 are named, as are COLI24 and POUI22 (opposite in corr_y).
Not 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.
## Parallax (asked by the user, 2026-11-18)
`targets.csv` gives the targets' distances: COLJ19 8.9 m and POUI19 9.4 m; COLI20, POUI20, COLH20 and COLH20''' 20–23 m; POUH21 and COLI21 30 m; COLI22 and POUI22 40 m; COLI24 and POUI24 60 m. The references are at 31–50 m (mean of 1/d ≈ 1/40 m). If the camera shifts sideways by T, a point moves by f·T/d in the image. The similarity fitted on the references removes f·T/d_ref, so each target keeps a remainder ∝ p = 1/d − 1/d_ref:
- a large remainder on the near targets;
- none at the references' distance;
- a remainder of the opposite sign beyond it.
Change of corr from the start to the end of each range (median of the first 6 accepted measurements against the last 6), regressed on p:
- 03/10 → 13/10: corr_x r = +0.82, corr_y r = +0.53.
- 13/10 → 16/10 (pause and slight return, no label): corr_x r = −0.86, the same parallax with the opposite sign.
- 16/10 → 01/11: corr_x r = +0.78, corr_y r = +0.27.
Fitted model: a lateral shift (tx, ty) plus a shift along the axis (radial from the image centre), each × p. It explains 70 %, 67 % and 61 % of the drift of the targets in the three ranges (the lateral shift alone: 60 %, 66 %, 54 %). With f ≈ d / mm_per_px ≈ 2700 px, the camera would shift laterally by about 0.7 mm (x) and 0.4 mm (y) up to 13/10, and about 0.9 mm and 0.5 mm from 17/10 on. This is a rough model.
What it explains: COLJ19 and POUI19 drifting the most, the 20 m group drifting less, POUH21 (30 m, ≈ d_ref) not drifting, the far targets turning the other way, and the sign flip during the pause.
What it does not explain (remainders of several noises):
- COLI21 (30 m): +0.06/+0.04 px up to 13/10, +0.075/+0.11 px from 17/10, about 7–10 noises.
- COLH20''' in corr_x: the opposite sign of what the model gives.
- The corr_y of COLI24 and POUI22: the right sign, about four to five times stronger than the model.
- COLI20 in corr_y after 17/10.
These stay "not established" in the descriptions. A remainder of the rotation that depends on the position in the image is possible, but I did not test it.
@@ -1,2 +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."}
{"start": "2026-10-03T00:00Z", "end": "2026-10-13T04:00Z", "family": "Displacement", "description": "From the start of the data to 13 October, the targets drift slowly and steadily with the camera pose, step by step, as the camera gradually tilts (tilt increasing, pan and rotation decreasing): COLJ19 and POUI19 the most, mostly in corr_x (POUI19 hardly in corr_y), COLH20, COLI20, COLI21 and POUI20 in the same direction, in corr_x and corr_y; COLI24 and POUI22 drift in the opposite direction in corr_y. Their position in the image hardly moves apart from the camera movement and their error_value stays stable. Cause given by the expert: the camera is nodding forward and the compensation of its movement is not complete. Deduced from the distances of the targets to the camera: the drift of each target grows as it is closer, a parallax. COLJ19 and POUI19, the nearest according to the expert and to their distances, drift the most; the targets at middle distance (COLH20, COLI20, POUI20) less; POUH21, at the distance of the references, does not drift; the farthest (COLI24, POUI22) go the other way in corr_y. As it nods, the camera does not only turn, it also shifts a little; a shift moves near targets much more in the image than far ones, and the compensation, fitted on references at middle distance, corrects only the targets at their distance: those nearer keep a remainder in one direction, those farther in the other. The parallax explains most of the drift, not all of it: COLI21, which drifts as much as targets much nearer, COLH20''' in corr_x, and the corr_y of COLI24 and POUI22, stronger than the parallax gives, remain 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: this is not a movement of the structure, the targets keep their places relative to each other and only their view from a camera that shifts changes; the camera tilt is to be monitored.", "review": "2026-11-18"}
{"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 the targets drift with it: POUI19 and COLJ19 the most, mostly in corr_x (POUI19 hardly in corr_y), COLI20, COLI21, COLH20 and POUI20 in the same direction, in corr_x and corr_y; COLI24 and POUI22 drift in the opposite direction in corr_y; COLI22, COLH20''' and POUI24 drift too, more noisily, between their own rejections. Their position in the image hardly moves apart from the camera movement and their error_value stays stable. Cause given by the expert: the camera is nodding forward and the compensation of its movement is not complete. Deduced from the distances of the targets to the camera: the drift of each target grows as it is closer, a parallax. COLJ19 and POUI19, the nearest according to the expert and to their distances, drift the most; the targets at middle distance (COLH20, COLI20, POUI20) less; POUH21, at the distance of the references, does not drift; the farthest (COLI24, POUI22) go the other way in corr_y. As it nods, the camera does not only turn, it also shifts a little; a shift moves near targets much more in the image than far ones, and the compensation, fitted on references at middle distance, corrects only the targets at their distance: those nearer keep a remainder in one direction, those farther in the other. The parallax explains most of the drift, not all of it: COLI21, which drifts as much as targets much nearer, COLH20''' in corr_x, and the corr_y of COLI24 and POUI22, stronger than the parallax gives, remain 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: this is not a movement of the structure, the targets keep their places relative to each other and only their view from a camera that shifts changes; the camera tilt is to be monitored.", "review": "2026-11-18"}
@@ -1,7 +1,13 @@
# BREITHORN long labels: requalification
2 labels: 1 kept, 1 corrected, 0 removed.
2 labels: 0 kept as they are, 2 corrected, 0 removed. Both drifts go beyond the noise.
- **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.
- **BREITHORN-2** (corrected): its cause is now explained by parallax. The targets are between about 9 m and 60 m from the camera, and the references between 31 m and 50 m. As the camera nods it also shifts a little (about 0.7 mm sideways and 0.4 mm vertically from the fit). The compensation, fitted on the references, cannot correct targets at other distances:
- the nearest targets drift the most (POUI19 about 0.6 mm, COLJ19 about 0.3 mm in corr_x);
- POUH21, at the references' distance, does not drift;
- the farthest targets go the other way in corr_y (COLI24 about −1.7 mm, POUI22 about −1.3 mm).
BREITHORN-2 is kept as it is: POUI19 drifts by about 0.3 mm, about 11 noises.
Parallax explains about 60 to 70 % of the drift. COLI21 (about 0.8 mm in corr_x) and COLH20''' remain unexplained.
- **BREITHORN-13** (corrected): the same parallax (camera shift of about 0.9 mm sideways and 0.5 mm vertically). COLI22, COLH20''' and POUI24 are now named, as are COLI24 and POUI22, which go the other way in corr_y (about −1.6 and −0.9 mm). The largest movements are COLI21 (about 1.0 mm in corr_x and 1.4 mm in corr_y), COLI20 (about 0.7–0.8 mm) and POUI19 (about 0.7 mm in corr_x). COLI21, COLH20''' and the corr_y of the far targets remain unexplained.
Both labels lose their review field.
@@ -0,0 +1,28 @@
"""Drift of each target over a range against its distance: parallax check.
Drift = median of the last N accepted measurements minus median of the first N (corr_x, corr_y, px and mm)."""
import sys, statistics as st
sys.path.insert(0, "tools/scripts")
import data
F = "data/BREITHORN"
M = data.load(F); T = data.load_targets(F)
refs = [s for s in M if data.is_reference(M[s])]
inv_ref = st.mean(1000 / T[s]["distance_mm"] for s in refs if T.get(s, {}).get("distance_mm"))
print("references:", {s: T[s]["distance_mm"] / 1000 for s in refs}, "mean 1/d_ref = %.4f /m" % inv_ref)
N = 6
for a, b in [(sys.argv[i], sys.argv[i + 1]) for i in range(1, len(sys.argv), 2)]:
A, B = data.parse_time(a), data.parse_time(b)
print(f"\n== {a} -> {b} (parallax term p = 1/d - mean 1/d_ref, /m)")
print(f"{'sensor':10} {'d_m':>5} {'p':>7} {'dcx_px':>8} {'dcy_px':>8} {'dcx_mm':>7} {'dcy_mm':>7} {'n':>3}")
rows = []
for s in sorted(M, key=lambda s: T.get(s, {}).get("distance_mm") or 0):
if s in refs: continue
w = [m for m in data.filter_window(M[s], A, B) if m["corr_x"] is not None]
if len(w) < 2 * N: print(s, "too few"); continue
d = T[s]["distance_mm"] / 1000; p = 1 / d - inv_ref
dd = {c: st.median(m[c] for m in w[-N:]) - st.median(m[c] for m in w[:N]) for c in ("corr_x", "corr_y", "corr_x_mm", "corr_y_mm")}
rows.append((p, dd["corr_x"], dd["corr_y"]))
print(f"{s:10} {d:5.1f} {p:7.4f} {dd['corr_x']:+8.4f} {dd['corr_y']:+8.4f} {dd['corr_x_mm']:+7.3f} {dd['corr_y_mm']:+7.3f} {len(w):3d}")
for k, c in ((1, "corr_x"), (2, "corr_y")):
xs = [r[0] for r in rows]; ys = [r[k] for r in rows]
r = st.correlation(xs, ys); sl = st.linear_regression(xs, ys)
print(f"{c}: r with p = {r:+.2f}, slope {sl.slope:+.3f} px*m, intercept {sl.intercept:+.4f} px")
@@ -0,0 +1,44 @@
"""Fit of the target drifts by a camera translation: lateral (tx, ty) and along the optical axis (tz, radial from the
image centre), each scaled by p = 1/d - mean 1/d_ref (what the similarity fitted on the references leaves)."""
import sys, statistics as st
sys.path.insert(0, "tools/scripts")
import data
F = "data/BREITHORN"; M = data.load(F); T = data.load_targets(F)
refs = [s for s in M if data.is_reference(M[s])]
inv_ref = st.mean(1000 / T[s]["distance_mm"] for s in refs)
allx = [m["x"] for s in M for m in M[s] if m["x"] is not None]; ally = [m["y"] for s in M for m in M[s] if m["y"] is not None]
print("image x range %.0f-%.0f, y range %.0f-%.0f" % (min(allx), max(allx), min(ally), max(ally)))
cx, cy = float(sys.argv[1]), float(sys.argv[2]); N = 6
def solve(A, b): # normal equations
n = len(A[0]); G = [[sum(r[i]*r[j] for r in A) for j in range(n)] for i in range(n)]; h = [sum(r[i]*y for r, y in zip(A, b)) for i in range(n)]
for i in range(n):
piv = G[i][i]
for j in range(i+1, n):
f = G[j][i]/piv; G[j] = [a - f*c for a, c in zip(G[j], G[i])]; h[j] -= f*h[i]
x = [0]*n
for i in reversed(range(n)): x[i] = (h[i] - sum(G[i][j]*x[j] for j in range(i+1, n)))/G[i][i]
return x
for a, b in [(sys.argv[i], sys.argv[i+1]) for i in range(3, len(sys.argv), 2)]:
A0, B0 = data.parse_time(a), data.parse_time(b); rows = []
for s in M:
if s in refs: continue
w = [m for m in data.filter_window(M[s], A0, B0) if m["corr_x"] is not None]
if len(w) < 2*N: continue
p = 1000/T[s]["distance_mm"] - inv_ref; x = st.median(m["x"] for m in w); y = st.median(m["y"] for m in w)
dx = st.median(m["corr_x"] for m in w[-N:]) - st.median(m["corr_x"] for m in w[:N])
dy = st.median(m["corr_y"] for m in w[-N:]) - st.median(m["corr_y"] for m in w[:N])
rows.append((s, p, x, y, dx, dy))
A = []; bb = []
for s, p, x, y, dx, dy in rows:
A.append([p, 0, p*(x-cx)]); bb.append(dx); A.append([0, p, p*(y-cy)]); bb.append(dy)
tx, ty, tz = solve(A, bb)
lat = solve([[r[0], r[1]] for r in A], bb)
print(f"\n== {a} -> {b}: tx {tx:+.3f} ty {ty:+.3f} px*m, tz {tz:+.6f} m (radial)")
print(f"{'sensor':10} {'d':>5} {'x':>6} {'y':>6} {'dcx':>8} {'fit':>8} {'dcy':>8} {'fit':>8} {'res_x':>7} {'res_y':>7}")
sr = st0 = 0
for s, p, x, y, dx, dy in sorted(rows, key=lambda r: -r[1]):
fx = p*tx + p*tz*(x-cx); fy = p*ty + p*tz*(y-cy)
sr += (dx-fx)**2 + (dy-fy)**2; st0 += dx**2 + dy**2
print(f"{s:10} {1/(p+inv_ref):5.1f} {x:6.0f} {y:6.0f} {dx:+8.4f} {fx:+8.4f} {dy:+8.4f} {fy:+8.4f} {dx-fx:+7.4f} {dy-fy:+7.4f}")
srl = sum((r[4]-r[1]*lat[0])**2 + (r[5]-r[1]*lat[1])**2 for r in rows)
print(f"share of the drift explained: lateral+axial {1-sr/st0:.2f}, lateral only {1-srl/st0:.2f}")
@@ -0,0 +1,17 @@
import json
D="labeling/auto/analyses/BREITHORN_2026-10-03T0000_2026-11-01T0000"
inp=[json.loads(l) for l in open(D+"/work/existing.jsonl")]
common=("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: this is not a movement of the structure, the targets keep their places relative to each other and only their view from a camera that shifts changes; the camera tilt is to be monitored.")
parallax=("Cause given by the expert: the camera is nodding forward and the compensation of its movement is not complete. "
"Deduced from the distances of the targets to the camera: the drift of each target grows as it is closer, a parallax. COLJ19 and POUI19, the nearest according to the expert and to their distances, drift the most; the targets at middle distance (COLH20, COLI20, POUI20) less; POUH21, at the distance of the references, does not drift; the farthest (COLI24, POUI22) go the other way in corr_y. "
"As it nods, the camera does not only turn, it also shifts a little; a shift moves near targets much more in the image than far ones, and the compensation, fitted on references at middle distance, corrects only the targets at their distance: those nearer keep a remainder in one direction, those farther in the other. "
"The parallax explains most of the drift, not all of it: COLI21, which drifts as much as targets much nearer, COLH20''' in corr_x, and the corr_y of COLI24 and POUI22, stronger than the parallax gives, remain not established. ")
a={k:v for k,v in inp[0].items() if k not in ("id","review")}
a["description"]=("From the start of the data to 13 October, the targets drift slowly and steadily with the camera pose, step by step, as the camera gradually tilts (tilt increasing, pan and rotation decreasing): COLJ19 and POUI19 the most, mostly in corr_x (POUI19 hardly in corr_y), COLH20, COLI20, COLI21 and POUI20 in the same direction, in corr_x and corr_y; COLI24 and POUI22 drift in the opposite direction in corr_y. Their position in the image hardly moves apart from the camera movement and their error_value stays stable. "
+ parallax + "The temperature of the camera housing drops slightly over the range, link not established. " + common)
b={k:v for k,v in inp[1].items() if k not in ("id","review")}
b["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 the targets drift with it: POUI19 and COLJ19 the most, mostly in corr_x (POUI19 hardly in corr_y), COLI20, COLI21, COLH20 and POUI20 in the same direction, in corr_x and corr_y; COLI24 and POUI22 drift in the opposite direction in corr_y; COLI22, COLH20''' and POUI24 drift too, more noisily, between their own rejections. Their position in the image hardly moves apart from the camera movement and their error_value stays stable. "
+ parallax + "The resumption coincides with the drop in the camera housing temperature, but the drift does not come back when it rises: link not established. " + common)
with open(D+"/labels.jsonl","w") as f:
for x in (a,b): f.write(json.dumps(x,ensure_ascii=False)+"\n")
@@ -1,5 +1,5 @@
{"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"}
{"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."}
{"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.", "review": "2026-11-18"}
{"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"}
{"start": "2026-10-19T00:00Z", "end": "2026-10-19T12:00Z", "family": "Thermal displacement", "description": "On 19 October in the morning, over two measurements, the camera rotation and scale suddenly deviate and its tilt takes a step; several targets deviate at the same time in opposite directions (COLH20 and the reference REFPOU22 upward in corr_y, COLI21 downward in corr_x and in corr_y), then return at noon. Nothing obstructs the view on the images, the error_value change little: this is the camera movement, incompletely compensated. It falls at the trough of the camera housing temperature, read in the metrics, and comes back when it rises: thermal effect on the camera, according to the expert: it is the housing temperature that matters, not the air temperature. Nothing to fear for the structure, nothing to do; do not trust these two points.", "review": "2026-11-17"}
{"start": "2026-10-21T16:00Z", "end": "2026-10-22T08:00Z", "family": "Obstruction", "description": "On the night of 21 to 22 October, COLI22, partly hidden, and POUI22 deviate clearly in corr_x and in corr_y, far beyond their ordinary noise, for three measurements, then return in the morning; COLI24, next to them, is rejected over the same measurements. On the 20:00 UTC image, the cab of a parked vehicle is in front of these bottom-left targets and the spot of COLI24 is no longer visible; the image of the morning is clear again. The references and the other targets hold. Seen on the image: a parked vehicle hides the targets. The structure does not move: ignore these targets over the range."}
{"start": "2026-10-21T16:00Z", "end": "2026-10-22T08:00Z", "family": "Obstruction", "description": "On the night of 21 to 22 October, COLI22, partly hidden, and POUI22 deviate clearly in corr_x and in corr_y, far beyond their ordinary noise, for three measurements, then return in the morning; COLI24, next to them, is rejected over the same measurements. On the 20:00 UTC image, the cab of a parked vehicle is in front of these bottom-left targets and the spot of COLI24 is no longer visible; the image of the morning is clear again. The references and the other targets hold. Seen on the image: a parked vehicle hides the targets. The structure does not move: ignore these targets over the range.", "review": "2026-11-18"}
@@ -1,9 +1,9 @@
{"start": "2026-10-22T16:00Z", "end": "2026-10-23T08:00Z", "family": "Obstruction", "description": "On the night of 22 to 23 October, the curve of COLI24 is missing (measurements rejected); COLI22, partly hidden and kept under its threshold, goes down clearly in corr_y and in corr_x, and POUI22 deviates a little in corr_x and, at the first measurement of the night, in corr_y. Seen on the contrast-stretched thumbnails of 20:00 and 04:00 UTC: the dark outline of a vehicle, lights off, stands in front of the bottom left of the scene, where the cars of the other nights park; the spot of COLI24 is hidden and that of COLI22 reduced. The references and the other targets do not move. Everything comes back in the morning, the vehicle gone on the 08:00 image. The structure does not move: ignore these targets over the range."}
{"start": "2026-10-22T16:00Z", "end": "2026-10-23T08:00Z", "family": "Obstruction", "description": "On the night of 22 to 23 October, the curve of COLI24 is missing (measurements rejected); COLI22, partly hidden and kept under its threshold, goes down clearly in corr_y and in corr_x, and POUI22 deviates a little in corr_x and, at the first measurement of the night, in corr_y. Seen on the contrast-stretched thumbnails of 20:00 and 04:00 UTC: the dark outline of a vehicle, lights off, stands in front of the bottom left of the scene, where the cars of the other nights park; the spot of COLI24 is hidden and that of COLI22 reduced. The references and the other targets do not move. Everything comes back in the morning, the vehicle gone on the 08:00 image. The structure does not move: ignore these targets over the range.", "review": "2026-11-18"}
{"start": "2026-10-23T16:00Z", "end": "2026-10-24T16:00Z", "family": "Obstruction", "description": "From the evening of 23 October to noon on 24 October, a car is parked in front of the bottom of the scene, seen on the images (grille and headlight, then headlights on). The curve of COLI24 is missing throughout; COLI22, first partly hidden, makes a very large jump in corr_x (its measured center slides over the visible part of its spot) and POUI22 jumps in corr_x, then COLI22, POUI22 and POUI24 are rejected on the morning of the 24th. The references hold. The structure does not move: ignore these targets over the range.", "review": "2026-11-17"}
{"start": "2026-10-25T20:00Z", "end": "2026-10-26T08:00Z", "family": "Obstruction", "description": "On the night of 25 to 26 October, an oblique structure, seen on the images in front of the bottom of the scene, hides the references REFH22 and REFPOU22, and COLH20''', COLI22 and POUI24 (measurements rejected, curves absent); POUI22, partly hidden, jumps in corr_x and in corr_y. The compensation only runs on two references: the basis changes, several targets (COLI20, POUI20, POUH21, COLJ19) shift a little in corr_x. Very bad sign for the measurement: data of the range not to be trusted; everything comes back in the morning.", "review": "2026-11-17"}
{"start": "2026-10-26T12:00Z", "end": "2026-10-26T20:00Z", "family": "Obstruction", "description": "On the evening of 26 October, a car with its headlights on, seen on the 16:00 UTC image, is parked in front of the bottom of the scene: the reference REFH22 is rejected and the compensation runs on three references; the curves of COLI24 and POUI24 are missing, and POUI22, partly hidden and kept under its threshold, makes a very large jump in corr_y and a jump in corr_x. COLI22 and COLH20 shift a little, through the change of references. The car is gone on the 20:00 image, where the oblique structure of the night takes over (labelled apart). The structure does not move: ignore these targets over the range."}
{"start": "2026-10-26T16:00Z", "end": "2026-10-27T08:00Z", "family": "Obstruction", "description": "On the night of 26 to 27 October, an oblique structure, seen on the images of 20:00 and 00:00 UTC in front of the bottom of the scene, follows the car of the evening (labelled apart). At 20:00 it hides the reference REFH22, COLI24 and POUI22 (measurements rejected, curves absent) and POUI24, partly hidden, jumps strongly in corr_x; at 00:00 and 04:00 it hides the reference REFPOU22, COLH20''' and still POUI22. The compensation runs on three references: REFG44N and REFI'21 shift a little in corr_x, the targets hardly. Everything comes back in the morning, the view clear on the 08:00 image. Ignore these targets over the range; the structure does not move."}
{"start": "2026-10-26T12:00Z", "end": "2026-10-26T20:00Z", "family": "Obstruction", "description": "On the evening of 26 October, a car with its headlights on, seen on the 16:00 UTC image, is parked in front of the bottom of the scene: the reference REFH22 is rejected and the compensation runs on three references; the curves of COLI24 and POUI24 are missing, and POUI22, partly hidden and kept under its threshold, makes a very large jump in corr_y and a jump in corr_x. COLI22 and COLH20 shift a little, through the change of references. The car is gone on the 20:00 image, where the oblique structure of the night takes over (labelled apart). The structure does not move: ignore these targets over the range.", "review": "2026-11-18"}
{"start": "2026-10-26T16:00Z", "end": "2026-10-27T08:00Z", "family": "Obstruction", "description": "On the night of 26 to 27 October, an oblique structure, seen on the images of 20:00 and 00:00 UTC in front of the bottom of the scene, follows the car of the evening (labelled apart). At 20:00 it hides the reference REFH22, COLI24 and POUI22 (measurements rejected, curves absent) and POUI24, partly hidden, jumps strongly in corr_x; at 00:00 and 04:00 it hides the reference REFPOU22, COLH20''' and still POUI22. The compensation runs on three references: REFG44N and REFI'21 shift a little in corr_x, the targets hardly. Everything comes back in the morning, the view clear on the 08:00 image. Ignore these targets over the range; the structure does not move.", "review": "2026-11-18"}
{"start": "2026-10-28T00:00Z", "end": "2026-10-28T12:00Z", "family": "Thermal displacement", "description": "On 28 October in the morning, over two measurements, the camera rotation and scale deviate then return at noon; at the same time, several targets deviate in opposite directions in corr_y (COLH20, COLI24, POUI22 and the reference REFPOU22 upward, POUI24 and the references REFG44N and REFI'21 downward), and return with the camera. Nothing obstructs the view on the images: this is the camera movement, incompletely compensated. It falls at the trough of the camera housing temperature, read in the metrics, and comes back when it rises: thermal effect on the camera, according to the expert: it is the housing temperature that matters, not the air temperature. Nothing to fear for the structure, nothing to do; do not trust these points.", "review": "2026-11-17"}
{"start": "2026-10-28T16:00Z", "end": "2026-10-29T16:00Z", "family": "Thermal displacement", "description": "From the evening of 28 October to noon on the 29th, the camera rotation and scale deviate again, for longer and more strongly, then return in the afternoon; several targets deviate with it in opposite directions in corr_y (COLH20, COLI24, POUI22 and the reference REFPOU22 upward; COLI21, COLH20''', POUI24 and the references REFG44N, REFI'21 and REFH22 downward), COLI22 goes down in corr_x, and at the last cold measurement POUI24 and POUH21 jump in corr_x; everything returns in the afternoon. The error_value rise a little on REFH22, COLH20 and COLH20''', without rejection. Nothing obstructs the view on the images, and the spots of POUI24 and POUH21 are in place at their jump: this is the camera movement, incompletely compensated. It follows the coldest night of the batch for the camera housing, read in the metrics, and comes back when it warms up: thermal effect on the camera, according to the expert: it is the housing temperature that matters, not the air temperature. Nothing to fear for the structure, nothing to do; do not trust these points."}
{"start": "2026-10-28T16:00Z", "end": "2026-10-29T16:00Z", "family": "Thermal displacement", "description": "From the evening of 28 October to noon on the 29th, the camera rotation and scale deviate again, for longer and more strongly, then return in the afternoon; several targets deviate with it in opposite directions in corr_y (COLH20, COLI24, POUI22 and the reference REFPOU22 upward; COLI21, COLH20''', POUI24 and the references REFG44N, REFI'21 and REFH22 downward), COLI22 goes down in corr_x, and at the last cold measurement POUI24 and POUH21 jump in corr_x; everything returns in the afternoon. The error_value rise a little on REFH22, COLH20 and COLH20''', without rejection. Nothing obstructs the view on the images, and the spots of POUI24 and POUH21 are in place at their jump: this is the camera movement, incompletely compensated. It follows the coldest night of the batch for the camera housing, read in the metrics, and comes back when it warms up: thermal effect on the camera, according to the expert: it is the housing temperature that matters, not the air temperature. Nothing to fear for the structure, nothing to do; do not trust these points.", "review": "2026-11-18"}
{"start": "2026-10-29T16:00Z", "end": "2026-10-30T04:00Z", "family": "Obstruction", "description": "On the night of 29 to 30 October, a car with a headlight on, seen on the images, is parked in front of the bottom of the scene: the curve of COLI24 is missing (measurements rejected); POUI22 makes a large jump in corr_x, COLH20''' jumps in corr_x then in corr_y, COLI22 deviates a little, all partly hidden; they return in the morning. The references hold. Ignore these targets over the range, the structure does not move.", "review": "2026-11-17"}
{"start": "2026-10-29T16:00Z", "end": "2026-10-30T12:00Z", "family": "Thermal displacement", "description": "From the evening of 29 October to the morning of the 30th, the camera rotation and scale deviate a third time, then return at noon; COLH20, COLI24 and the reference REFPOU22 rise in corr_y, POUI24, COLI21 and the references REFG44N and REFI'21 go down, then everything returns. Nothing obstructs these targets on the images (the car of the same night only hides the bottom of the scene): this is the camera movement, incompletely compensated. It follows the cooling of the camera housing, read in the metrics, and comes back when it warms up: thermal effect on the camera, according to the expert: it is the housing temperature that matters, not the air temperature. Nothing to fear for the structure, nothing to do; do not trust these points.", "review": "2026-11-17"}
@@ -1,13 +1,9 @@
{"start": "2026-10-01T06:15Z", "end": "2026-10-01T08:45Z", "family": "Visibility", "description": "The recognition error of most targets rises together, first a little, then clearly around 07:50-08:00, and comes back down; at the same time the corrected curves of several targets make a bump that comes back: D-301-C horizontally, D-302-B and PR_BG (same prism) vertically, D-306-B, D-303-B, P-301-B, then around 08:00 D-301-A, D-302_A, D-304-A. The scene deforms a little (scale and rotation of the targets, references PR-291 and PR-293 moving away from the targets), without camera movement. Nothing on the 07:00 and 08:00 images, which are dark as always. Diffuse obstruction of the view in the tunnel, cause not established (the tunnel air?); same signature as the episodes of 2, 6, 18, 22 and 31 October. The structure does not move: do not trust the curves over the range.", "review": "2026-11-17"}
{"start": "2026-10-01T17:45Z", "end": "2026-10-02T02:30Z", "family": "Displacement", "description": "The low targets of row B go down vertically from 18:00: D-306-B above all, which keeps going down into the night then stays low until the gap of 3 October, D-304-B and D-303-B (which, for its part, gradually rises until the 3rd). Raw positions almost motionless, no camera movement, ordinary recognition error, no image showing a cause. 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"}
{"start": "2026-10-02T03:40Z", "end": "2026-10-03T03:00Z", "family": "Displacement", "description": "D-303-B comes back up vertically after its descent of the evening of the 1st (labeled separately): first during the morning of the 2nd, then after a pause over the day, again in the evening and the night, until it reaches its level from before the descent in the night of the 2nd to the 3rd, and stays there until the gap of the 3rd. D-306-B and D-304-B, which went down with it, do not come back. Ordinary recognition error, apart from the view obstruction of the evening of the 2nd (labeled separately); nothing on the thumbnails of the 2nd at 12:00 and the 3rd at 08:00. The camera tilt decreases slowly over these days, and D-303-B follows the tilt of the camera only in part (see the 6th and the 8th): this may explain a small part of the rise, not all of it. Cause not established, in a tunnel under construction: return of the descent of the 1st; to be checked with the other measurements of the site."}
{"start": "2026-10-02T21:30Z", "end": "2026-10-02T23:00Z", "family": "Visibility", "description": "The recognition error of most targets rises together for one hour, and the corrected curves of D-304-B (vertical) above all, of D-301-C (horizontal), D-302-B and PR_BG, P-301-B, D-304-C make a bump that comes back; D-304-B is still shifted at the last measurement, before 23:00. The camera housing temperature drops clearly at the same time. Nothing visible on the 22:00 image. Diffuse obstruction of the view, cause not established, perhaps a change in the tunnel air. The structure does not move: curves to ignore over the range."}
{"start": "2026-10-02T21:30Z", "end": "2026-10-02T23:00Z", "family": "Visibility", "description": "The recognition error of most targets rises together for one hour, and the corrected curves of D-304-B (vertical) above all, of D-301-C (horizontal), D-302-B and PR_BG, P-301-B, D-304-C make a bump that comes back; D-304-B is still shifted at the last measurement, before 23:00. The camera housing temperature drops clearly at the same time. Nothing visible on the 22:00 image. Diffuse obstruction of the view, cause not established, perhaps a change in the tunnel air. The structure does not move: curves to ignore over the range.", "review": "2026-11-18"}
{"start": "2026-10-03T07:40Z", "end": "2026-10-03T08:00Z", "family": "No data", "description": "One measurement is missing, for all sensors: the curves have a short gap. Cause not established.", "review": "2026-11-17"}
{"start": "2026-10-03T09:40Z", "end": "2026-10-03T17:00Z", "family": "Displacement", "description": "P-301-B alone: its vertical corrected curve, a little low since the view obstruction of the evening of the 2nd, jumps up within two measurements around 09:50, together with a clear rise of its own recognition error, stays above its usual level until the early afternoon, then slowly comes back down until the late afternoon. Its raw position moves in the image while the neighbouring targets and the camera stay still; its horizontal curve hardly moves. The thumbnails of 08:00, 12:00 and 16:00 show the same sharp spot, nothing in front. Cause not established: something changes in the appearance or the position of this target only; not an established movement of the structure, to be checked; ignore this curve over the range."}
{"start": "2026-10-03T17:30Z", "end": "2026-10-03T17:45Z", "family": "Visibility", "description": "Last measurement before the gap of 3 October: the same one-measurement bump on D-301-C, D-302-B and PR_BG, D-304-B, D-304-C, P-301-B, with the recognition error of many targets rising. Same signature as the episodes of view obstruction at the station; cause not established, perhaps linked to the station shutdown that follows. Point to ignore.", "review": "2026-11-17"}
{"start": "2026-10-03T17:45Z", "end": "2026-10-05T10:30Z", "family": "No data", "description": "No measurement or image for almost two days, for all sensors, and the station metrics are missing too: the entire station stopped. Voltage and battery normal before and after the gap, so not the signature of a power cut; on resumption, the camera has moved and a blurred object is very close to the lens (10:30 image), which suggests an intervention on the station. Cause not established: the curves are missing over the range.", "review": "2026-11-17"}
{"start": "2026-10-03T17:45Z", "end": "2026-10-05T10:45Z", "family": "Displacement", "description": "After the gap of 3 to 5 October, many targets resume at a different level, and do not return to the previous one until the end of the batch: D-304-C and D-303-C above all, in both directions, then D-302_A and D-301-A, P-299-B, D-300-C, D-303-B and D-304-B horizontally, D-301-C vertically; D-306-B, for its part, returns to its level from before its descent of the evening of the 1st. The raw positions of D-304-C and D-303-C have moved in the image relative to the other targets, the recognition error of several targets (D-302-C, D-301-C, D-303-C, D-304-C, D-301-A, D-306-B) also changes level, and the camera scale is no longer the same: the appearance of these targets and the camera pose changed during the shutdown. On resumption, a blurred object is very close to the lens (10:30 image). Cause not established: intervention or changed setting during the shutdown, or real movement; to be checked before trusting these new levels.", "review": "2026-11-17"}
{"start": "2026-10-05T10:30Z", "end": "2026-10-05T11:20Z", "family": "Obstruction", "description": "First measurement after the gap: the whole scene, references included, is shifted by several pixels in the image and the camera is tilted, then it returns within twenty minutes; the compensation absorbs it poorly for the duration of one measurement, and the corrected curves of many targets jump then return (D-303-C, D-302-B and PR_BG, D-306-B, D-304-B, P-299-C above all; D-303-B stays slightly shifted until 11:10). D-304-C is rejected. The 10:30 image shows a large blurred object very close to the lens, on the right, which hides D-304-C, and a worker in reflective clothing in the tunnel, at the top left: work is going on around the camera. Points to ignore; the structure does not move.", "review": "2026-11-17"}
{"start": "2026-10-05T12:10Z", "end": "2026-10-05T12:30Z", "family": "Obstruction", "description": "For the duration of one measurement, the whole right-hand row C (D-300-C, D-301-C, D-303-C, D-304-C, P-298-C, P-299-C) and the reference D-302-C are rejected, their recognition error almost at 1; the compensation runs without D-302-C and the targets that stayed under the threshold jump then return at the next measurement (D-306-B above all vertically, D-303-B, D-304-B, P-299-B, P-301-B, D-302-B and PR_BG). No image at 12:20: the cause is not seen, but the signature is that of something passing in front of the right-hand part of the scene. Point to ignore.", "review": "2026-11-17"}
{"start": "2026-10-06T13:00Z", "end": "2026-10-06T13:30Z", "family": "Displacement", "description": "Around 13:10 the whole scene, references included, shifts by a step vertically in the image: the camera tilt makes a step, which it keeps. The compensation absorbs it for all the targets except D-303-B, whose raw position follows only part of the shift: its vertical corrected curve drops by a step and stays low into the evening (D-303-C and D-304-C at most slightly). Ordinary recognition error. Over the following days, D-303-B keeps following the camera tilt in the same partial way (the drift labeled from the evening of the 6th; the opposite camera step of the 8th leaves it only a remainder within the noise). Cause of the camera step not established; the step of D-303-B is the remainder of the camera movement, not a movement of the structure: the camera is to be monitored."}
{"start": "2026-10-06T18:00Z", "end": "2026-10-06T22:10Z", "family": "Visibility", "description": "For four hours, the corrected curves of the same group of targets take a step that starts and ends sharply: D-301-C horizontally above all, D-302-B and PR_BG (same prism) horizontally then vertically, D-304-B vertically, and at times P-301-B, D-303-B, D-302_A, D-301-A, D-304-C. The recognition error of the references PR-293, PR-295, PR-296 and of a few targets rises a little; the references move away from each other in the image. The camera housing temperature drops clearly over these hours. Nothing visible on the 20:00 image. View obstruction of cause not established, probably the tunnel air (colder); the curves and the recognition error return at 22:00, before the camera scale. The structure does not move: curves to ignore over the range."}
@@ -66,3 +66,7 @@ The blue curve (D-303-B) and the red one (the tilt, upside down) move together.
| 2026-10-05 12:10 | 2026-10-05 12:30 | Obstruction | D-306-B, row B, via row C and D-302-C | Something passes in front, one point |
| 2026-10-06 13:00 | 2026-10-06 13:30 | Displacement | D-303-B | Camera tilt step, D-303-B keeps a step down |
| 2026-10-06 18:00 | 2026-10-06 22:10 | Visibility | D-301-C, D-302-B, PR_BG, D-304-B | View obstruction for four hours |
## Update 2026-11-18: Displacement labels pruned
At your request, only the significant displacements of CLARIDEN were kept: the small ones that come back later were removed from this analysis. The labels.jsonl here is the current list, and the table above is out of date for Displacement. Which labels were removed and why: `CLARIDEN_2026-10-01T0000_2026-11-01T0000/analysis.md`.
@@ -1,6 +1,41 @@
# Requalification of the long labels: CLARIDEN
# CLARIDEN, October: Displacement labels requalified (significant only)
- **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.
- **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.
Request of the user (2026-11-18): too many small displacements, most going back the other way later; keep only the significant ones, on all CLARIDEN series.
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 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).
## Method
- `scripts/disp_size.py` (`work/disp_size.txt`): per label and per target, the extreme of the 1 h rolling median of `corr_x_mm` / `corr_y_mm` from the level of the 6 h before, in mm and in own noises (median step), the net change at the end, and the month spread (P5–P95) of each target. PR-284 and PR_BG are discarded as noisy, with a large mm/px.
- `scripts/short_native.py` (`work/short_native.txt`): the native-step extreme of the short labels.
- `scripts/month_plot.py` (`work/month_displacements.png`): hourly medians of the targets concerned over October, with the labels, the camera tilt and the housing temperature.
- Criterion: kept if a clean target moves by ≥ about 0.4 mm and ≥ 10 noises on its 1 h median, and keeps that level for days. Removed if the event is a wave that comes back, a remainder of a camera jump of one measurement, or ≤ about 8 noises.
## Per label
| id | decision | evidence |
|---|---|---|
| CLARIDEN-14 | kept, corrected (pointer to 72 replaced) | D-301-C x +1.1 mm (19 n), D-303-B y +0.36 mm (12 n), kept afterwards |
| CLARIDEN-23 | kept, corrected (pointer to 32 replaced) | D-304-C y +0.48 mm (14 n), D-303-C y +0.42 mm (11 n), D-301-C x about +0.5 mm, kept |
| CLARIDEN-3 | removed | D-303-B −0.25 mm, D-306-B −0.11 mm (13 n, but 0.1 mm), back with 44; D-302-B +0.7 mm is its own two-level jump |
| CLARIDEN-44 | removed | return of 3; D-301-C −0.84 mm is a one-hour spike (net −0.07 mm) |
| CLARIDEN-46 | removed | P-301-B y +0.39 mm, 6.9 n native, back the same day |
| CLARIDEN-73 | removed | D-303-B y −0.19 mm, 7.3 n native |
| CLARIDEN-72 | removed | partial return of 14: D-301-C −0.28 mm (5 n); its big D-302-B value is that target's own steps of 11/10 and 14/10 |
| CLARIDEN-50 | removed | one measurement, D-301-A y −0.43 mm, 5.9 n |
| CLARIDEN-53 | removed | ≤ 5.2 n on the 1 h median, ≤ 0.2 mm |
| CLARIDEN-54 | removed | one measurement, D-302_A x +0.37 mm, 5.3 n |
| CLARIDEN-59 | removed | D-306-B y +0.05 mm, 6.4 n |
| CLARIDEN-62 | removed | D-303-B +0.17 mm (5.8 n), back with 29 |
| CLARIDEN-29 | removed | D-306-B −0.11 mm, D-304-B −0.2 mm; wave with 62/30 |
| CLARIDEN-30 | removed | D-306-B +0.05 mm (5.4 n) |
| CLARIDEN-31 | removed | D-306-B +0.13 mm, D-304-B +0.26 mm, D-304-A +0.38 mm (6 n), back with 63 |
| CLARIDEN-32 | removed | partial return of 23, D-304-C −0.25 mm (7 n) |
| CLARIDEN-63 | removed | same dates and targets as 32 (−0.26 mm, 7 n) |
| CLARIDEN-36 | removed | D-306-B −0.06 mm, 7.8 n |
| CLARIDEN-1 | kept as is | P-300-B rejected at 4070/4070 instants |
The labels removed or corrected are in the labels.jsonl of the analysis that owns them: `CLARIDEN_2026-10-01T0000_2026-10-11T0000` (12 → 8), `CLARIDEN_2026-10-11T0000_2026-10-20T0400` (11 → 6), `CLARIDEN_2026-10-20T0400_2026-11-01T0010` (21 → 14, 23 corrected), and this one (14 corrected). `labeling/auto/CLARIDEN.jsonl` follows them since 2026-11-18 (the three period analyses submitted again: 46 → 30 labels, 2 Displacement; CLARIDEN-23 keeps its id; then CLARIDEN-9 restored: 31 labels, 3 Displacement).
## Not labeled, for the record
- D-302-B / PR_BG: two-level jumps (about 0.75 mm) on 1/10, 5/10, 11/10, 14/10, specific to that prism.
- Across the 3→5/10 outage: D-304-C about −1.5 mm, D-303-C about −0.6 mm, with a change of camera tilt: CLARIDEN-9 (analysis `CLARIDEN_2026-10-01T0000_2026-10-11T0000`), deleted before this pass, restored on 2026-11-18 at the user's request, unchanged.
## Sources read
Previous turn (docs, inventory, ranges); this turn: `labeling/auto/CLARIDEN.jsonl`, the labels.jsonl of the four CLARIDEN analyses, `app/server/analysis.py` (how labels are submitted), `tools/scripts/data.py` (loader), data/CLARIDEN through the scripts above.
@@ -1,2 +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."}
{"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. Afterwards D-301-C comes back down a little over the following days, too little to be labeled, and D-303-B stays at its new level. 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.", "review": "2026-11-18"}
@@ -1,5 +1,19 @@
# CLARIDEN long labels: requalification
# CLARIDEN, October: Displacement labels pruned
2 labels: 1 kept, 1 corrected, 0 removed.
Only the significant displacements are kept: those that move a clean target by several tenths of a mm and that it keeps, against a month where the targets wander back and forth by a few tenths of a mm.
- **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.
**Kept (2 Displacement labels)**
- **CLARIDEN-14** (06/10 → 11/10): row C drift, D-301-C horizontally about +1.1 mm (≈19 noises), D-303-B vertically about +0.35 mm (≈12 noises), which keep their new level. It follows the slow tilt of the camera. Corrected: it pointed to a return label that is now removed.
- **CLARIDEN-23** (20/10 → 25/10): second row C drift, D-301-C +0.5 mm, D-304-C about +0.5 mm (≈14 noises), D-303-C about +0.4 mm (≈11 noises), kept afterwards. Corrected the same way (its partial return is no longer labeled).
**Removed (16)**: all small (about 5 to 7 noises at the native step, or a wave of 0.1–0.3 mm), or going back the other way within hours or days:
- 01→03/10: CLARIDEN-3 (row B dip, D-303-B −0.25 mm, D-306-B −0.1 mm) and CLARIDEN-44 (its return); CLARIDEN-46 (P-301-B, +0.4 mm, 7 n, back the same day).
- CLARIDEN-73 (06/10 camera step, D-303-B 7 n, 0.2 mm), CLARIDEN-72 (partial return of 14, D-301-C −0.3 mm).
- One-measurement drops at the camera jumps: CLARIDEN-50 (11/10, 6 n), CLARIDEN-54 (18/10, 5 n), CLARIDEN-59 (20/10, 6 n, D-306-B 0.05 mm).
- CLARIDEN-53 (17→20/10 tilt, ≤ 5 n, 0.2 mm).
- 22→29/10, row B and row A going up and down: CLARIDEN-62, 29, 30 (D-304-B, D-303-B ±0.2 mm), CLARIDEN-31 (row A jolts, D-304-A +0.4 mm, 6 n), CLARIDEN-32 and CLARIDEN-63 (partial returns, 0.25 mm, 7 n), CLARIDEN-36 (step of D-306-B, 0.06 mm, 8 n).
**To know**
- The other families (Visibility, Obstruction, No data, Target issue, Thermal) are untouched.
- D-302-B (with PR_BG, on the same prism) jumps between two levels about 0.75 mm apart (1/10, 5/10, 11/10, 14/10). These jumps belong to that target, not to the structure. No label covers them now. They look like the configuration jump labeled as Target issue on 29/10 (CLARIDEN-65).
- Across the outage of 3→5/10, D-304-C (about −1.5 mm) and D-303-C (about −0.6 mm) come back at a new level, and the camera tilt changed at the same time. This is the largest shift of the month: CLARIDEN-9 covers it, deleted before this pass and restored on 2026-11-18 at your request (unchanged, its review kept).
@@ -0,0 +1,41 @@
"""Size of each Displacement label of CLARIDEN: per target, deviation of the 1 h rolling median of corr (px, mm)
from the level of the 6 h before the label, extreme within the label, net change at its end, in mm and in noises;
plus the month spread of each target (P5-P95 of its 1 h median) for scale."""
import sys, json, statistics as st
from datetime import timedelta
sys.path.insert(0, "tools/scripts")
import data
D = data.load("data/CLARIDEN")
S, E = data.parse_time("2026-09-25T00:00Z"), data.parse_time("2026-11-05T00:00Z")
tg = {s: [m for m in ms if S <= m["t"] <= E] for s, ms in D.items() if not data.is_reference(ms) and s not in ("P-300-B", "PR-283")}
def roll(ms, c):
out = []
for i, m in enumerate(ms):
w = [x[c] for x in ms[max(0, i-3):i+3] if x[c] is not None]
if m[c] is not None and len(w) >= 3: out.append((m["t"], st.median(w)))
return out
noise, R, spread = {}, {}, {}
for s, ms in tg.items():
for c in ("corr_x_mm", "corr_y_mm"):
v = [m[c] for m in ms if m[c] is not None]
if len(v) < 100: continue
noise[s, c] = st.median(abs(a-b) for a, b in zip(v, v[1:])) or 1e-9
R[s, c] = roll(ms, c)
h = sorted(x for _, x in R[s, c]); spread[s, c] = h[int(.95*len(h))] - h[int(.05*len(h))]
labels = [json.loads(l) for l in open("labeling/auto/CLARIDEN.jsonl")]
for L in labels:
if L["family"] != "Displacement": continue
a, b = data.parse_time(L["start"]), data.parse_time(L["end"])
rows = []
for (s, c), r in R.items():
pre = [x for t, x in r if a - timedelta(hours=6) <= t <= a]
ins = [(t, x) for t, x in r if a <= t <= b]
if len(pre) < 6 or len(ins) < 2: continue
lv = st.median(pre)
t0, ex = max(ins, key=lambda p: abs(p[1]-lv))
net = ins[-1][1] - lv
rows.append((abs(ex-lv)/noise[s, c], s, c[5], ex-lv, (ex-lv)/noise[s, c], net, spread[s, c]))
rows.sort(reverse=True)
print(f"{L['id']} {L['start']}->{L['end']} ({(b-a).total_seconds()/3600:.1f} h)")
for r in rows[:4]:
print(f" {r[1]:8s} {r[2]} ext {r[3]:+.3f} mm ({r[4]:+.1f} n) net {r[5]:+.3f} mm month spread {r[6]:.3f} mm")
@@ -0,0 +1,30 @@
"""Hourly medians of corr_x_mm / corr_y_mm of the targets that carry the CLARIDEN Displacement labels, over October,
with every Displacement label shaded and named, and the camera tilt and housing temperature."""
import sys, json, statistics as st
from collections import defaultdict
sys.path.insert(0, "tools/scripts")
import data
import matplotlib; matplotlib.use("Agg"); import matplotlib.pyplot as plt
D = data.load("data/CLARIDEN")
S, E = data.parse_time("2026-10-01T00:00Z"), data.parse_time("2026-11-01T00:00Z")
series = [("D-302-B","corr_y_mm"),("D-301-C","corr_x_mm"),("D-303-B","corr_y_mm"),("D-303-C","corr_y_mm"),
("D-304-C","corr_y_mm"),("D-306-B","corr_y_mm"),("D-304-B","corr_y_mm"),("P-301-B","corr_y_mm"),("D-304-A","corr_y_mm")]
def hourly(pairs):
h = defaultdict(list)
for t, v in pairs:
if v is not None and S <= t <= E: h[t.replace(minute=0, second=0)].append(v)
k = sorted(h); return k, [st.median(h[x]) for x in k]
cam = data.load_camera("data/CLARIDEN"); tmp = data.load_temperature("data/CLARIDEN")
fig, ax = plt.subplots(len(series)+2, 1, figsize=(18, 2.0*(len(series)+2)), sharex=True)
labels = [json.loads(l) for l in open("labeling/auto/CLARIDEN.jsonl")]
for i, (s, c) in enumerate(series):
t, v = hourly((m["t"], m[c]) for m in D[s]); ax[i].plot(t, v, lw=.8); ax[i].set_ylabel(f"{s}\n{c[5]} mm", fontsize=8)
t, v = hourly((p["t"], p.get("tilt")) for p in cam); ax[-2].plot(t, v, "k", lw=.8); ax[-2].set_ylabel("tilt")
t, v = hourly(tmp); ax[-1].plot(t, v, "r", lw=.8); ax[-1].set_ylabel("housing °C")
for L in labels:
if L["family"] not in ("Displacement", "No data"): continue
a, b = data.parse_time(L["start"]), data.parse_time(L["end"])
for x in ax: x.axvspan(a, b, color="orange" if L["family"] == "Displacement" else "grey", alpha=.2, lw=0)
if L["family"] == "Displacement": ax[0].text(a, ax[0].get_ylim()[1], L["id"].split("-")[1], fontsize=7, va="top")
for x in ax: x.grid(alpha=.3)
plt.tight_layout(); out = sys.argv[1]; plt.savefig(out, dpi=80); print(out)
@@ -0,0 +1,25 @@
"""Native-step extreme of the short CLARIDEN Displacement labels: per target, the largest deviation of corr_x_mm /
corr_y_mm within the label from the median of the 6 h before, in mm and in the target's own noise (median step)."""
import sys, json, statistics as st
from datetime import timedelta
sys.path.insert(0, "tools/scripts")
import data
D = data.load("data/CLARIDEN")
ids = sys.argv[1].split(",")
for l in open("labeling/auto/CLARIDEN.jsonl"):
L = json.loads(l)
if L["id"] not in ids: continue
a, b = data.parse_time(L["start"]), data.parse_time(L["end"]); rows = []
for s, ms in D.items():
if data.is_reference(ms) or s in ("P-300-B", "PR-283"): continue
for c in ("corr_x_mm", "corr_y_mm"):
v = [m[c] for m in ms if m[c] is not None and a - timedelta(days=2) <= m["t"] <= b + timedelta(days=2)]
if len(v) < 50: continue
n = st.median(abs(x - y) for x, y in zip(v, v[1:])) or 1e-9
pre = [m[c] for m in ms if m[c] is not None and a - timedelta(hours=6) <= m["t"] < a]
ins = [m[c] for m in ms if m[c] is not None and a < m["t"] < b]
if len(pre) < 6 or not ins: continue
lv = st.median(pre); d = max(ins, key=lambda x: abs(x - lv)) - lv
rows.append((abs(d) / n, s, c[5], d))
rows.sort(reverse=True)
print(L["id"], L["start"], "->", L["end"], "; ".join(f"{s} {c} {d:+.2f} mm ({k:.1f} n)" for k, s, c, d in rows[:3]))
@@ -1,11 +1,6 @@
{"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."}
{"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."}
{"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."}
{"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.", "review": "2026-11-18"}
{"start": "2026-10-16T14:20Z", "end": "2026-10-16T14:40Z", "family": "No data", "description": "One measurement is missing, for all sensors, a few hours after the resumption of the 16th: the curves have a short gap; normal voltage around it. The same gap falls at the same moment on the other stations measuring at that time (FLORIDA, LENZSPITZE, NORDEND, SNCF01): a common cause outside the station (transmission or reception of the data), not a failure of the station; it is not established. The curves are missing over the range; nothing to do on the station.", "review": "2026-11-17"}
{"start": "2026-10-17T16:00Z", "end": "2026-10-20T00:30Z", "family": "Displacement", "description": "From the 17th to the 19th, the camera slowly tilts the other way: its tilt goes down, more and more after the restart that follows the outage of the 18th; it partly comes back during the 19th, then suddenly jumps back on the 20th (labeled separately). The raw positions of all sensors, references included, move together vertically in the image with it. The compensation does not render this movement evenly. The corrected vertical curves of D-302-B and PR_BG (same prism) rise. Those of D-303-B, D-304-B, P-301-B, D-306-B, D-303-C and D-304-C go down, and D-301-C rises a little horizontally. They follow the tilt step by step, come back partly with it on the 19th, and return at once at the camera jump of the 20th. The recognition error stays at its level, and the image of the 19th shows nothing in front of the targets. The housing temperature drops a little on the 18th and is low at the restart after the outage; but the tilt keeps going down after the housing has warmed again, and it does not come back at equal temperature: link not established. This is not a movement of the structure but the remainder of an incomplete compensation of the camera movement; the camera is to be monitored."}
{"start": "2026-10-18T06:30Z", "end": "2026-10-18T06:50Z", "family": "Displacement", "description": "For one measurement, the corrected horizontal curves of the targets of row A (D-304-A, D-302_A, D-303-A, D-300-A, P-298-A, D-301-A) and of D-302-B and PR_BG (same prism) jump together, then come back at the next one. The raw positions of the targets do not move; the references PR-291, PR-293 and PR-295 shift slightly horizontally against them, and the camera pose jumps (pan, scale): the compensation is skewed for one measurement. The recognition error stays at its level. There is no image at that instant; the image of the next hour shows work lights at the far end of the tunnel and nothing in front of the targets. Cause not established; points to ignore, not a movement of the structure."}
{"start": "2026-10-18T08:50Z", "end": "2026-10-18T09:30Z", "family": "Visibility", "description": "For three measurements, the corrected curves of many targets make a bump that comes back: first the targets of row A (D-300-A, D-301-A, D-302_A, D-303-A, D-304-A, P-298-A) rise vertically; over the next two measurements, the recognition error of most targets and of the references PR-293 and PR-295 rises, D-302-B and PR_BG (same prism) rise strongly vertically, D-301-C goes down strongly horizontally, and P-301-B and D-303-B move horizontally. All come back at the following measurement. The camera pose jumps at the same time (tilt, scale), and the housing temperature drops. The image of the first measurement shows nothing in front of the targets. The signature is that of the other view obstruction episodes at the station: the error rises on most sensors, and the edges are sharp. Reduced visibility is deduced from it; the cause is not seen. Points to ignore."}
{"start": "2026-10-18T13:50Z", "end": "2026-10-18T23:30Z", "family": "No data", "description": "No measurement or image for almost ten hours, nor station metric. On resumption, the battery is depleted and the voltage low, then they rise: signature of a power cut. The curves are missing over the range; check the power supply if it repeats."}
{"start": "2026-10-19T09:00Z", "end": "2026-10-19T10:10Z", "family": "No data", "description": "Four measurements are missing within one hour, for all sensors, between isolated measurements: the curves have gaps; normal voltage around them. The same gap falls at the same moment on the other stations measuring at that time (FLORIDA, JUNGFRAU, LENZSPITZE, NIEDERHORN, NORDEND, SNCF01): a common cause outside the station (transmission or reception of the data), not a failure of the station; it is not established. The curves are missing over the range; nothing to do on the station."}
{"start": "2026-10-19T20:40Z", "end": "2026-10-19T21:30Z", "family": "No data", "description": "Three measurements are missing in less than an hour, for all sensors: the curves have a gap; normal voltage around it. The same gap falls at the same moment on the other stations measuring at that time (FLORIDA, JUNGFRAU, LENZSPITZE, NIEDERHORN, NORDEND, SNCF01): a common cause outside the station (transmission or reception of the data), not a failure of the station; it is not established. The curves are missing over the range; nothing to do on the station. The hourly metrics of BREITHORN, MICHIGAN and NEBRASKA are also missing at 21:00."}
{"start": "2026-10-20T00:10Z", "end": "2026-10-20T00:40Z", "family": "Displacement", "description": "On the 20th, over two measurements, the whole scene, references included, suddenly shifts in the image, mostly vertically: the camera has moved (its tilt jumps). The compensation absorbs most of it, but the corrected curves of several targets jump. Vertically, D-303-C, D-304-C, D-304-B, D-303-B and P-301-B go back up to the level they had before the slow tilting of the camera of the 17th to the 19th (labeled separately): this jump erases its remainder. D-306-B jumps up clearly, beyond its earlier level, and stays there. D-302-B and PR_BG (same prism) jump horizontally and stay there. The recognition error of D-302-B and D-303-B changes level at the same moment. Work lights are visible at the far end of the tunnel on the images of the hour before and the hour after; nothing is in front of the targets. The cause of the camera movement is not established. The lasting jumps of D-306-B and D-302-B are not an established movement of the structure: to be checked; the camera is to be monitored."}
{"start": "2026-10-18T08:50Z", "end": "2026-10-18T09:30Z", "family": "Visibility", "description": "For three measurements, the corrected curves of many targets make a bump that comes back: first the targets of row A (D-300-A, D-301-A, D-302_A, D-303-A, D-304-A, P-298-A) rise vertically; over the next two measurements, the recognition error of most targets and of the references PR-293 and PR-295 rises, D-302-B and PR_BG (same prism) rise strongly vertically, D-301-C goes down strongly horizontally, and P-301-B and D-303-B move horizontally. All come back at the following measurement. The camera pose jumps at the same time (tilt, scale), and the housing temperature drops. The image of the first measurement shows nothing in front of the targets. The signature is that of the other view obstruction episodes at the station: the error rises on most sensors, and the edges are sharp. Reduced visibility is deduced from it; the cause is not seen. Points to ignore.", "review": "2026-11-18"}
{"start": "2026-10-18T13:50Z", "end": "2026-10-18T23:30Z", "family": "No data", "description": "No measurement or image for almost ten hours, nor station metric. On resumption, the battery is depleted and the voltage low, then they rise: signature of a power cut. The curves are missing over the range; check the power supply if it repeats.", "review": "2026-11-18"}
{"start": "2026-10-19T09:00Z", "end": "2026-10-19T10:10Z", "family": "No data", "description": "Four measurements are missing within one hour, for all sensors, between isolated measurements: the curves have gaps; normal voltage around them. The same gap falls at the same moment on the other stations measuring at that time (FLORIDA, JUNGFRAU, LENZSPITZE, NIEDERHORN, NORDEND, SNCF01): a common cause outside the station (transmission or reception of the data), not a failure of the station; it is not established. The curves are missing over the range; nothing to do on the station.", "review": "2026-11-18"}
{"start": "2026-10-19T20:40Z", "end": "2026-10-19T21:30Z", "family": "No data", "description": "Three measurements are missing in less than an hour, for all sensors: the curves have a gap; normal voltage around it. The same gap falls at the same moment on the other stations measuring at that time (FLORIDA, JUNGFRAU, LENZSPITZE, NIEDERHORN, NORDEND, SNCF01): a common cause outside the station (transmission or reception of the data), not a failure of the station; it is not established. The curves are missing over the range; nothing to do on the station. The hourly metrics of BREITHORN, MICHIGAN and NEBRASKA are also missing at 21:00.", "review": "2026-11-18"}
@@ -53,3 +53,7 @@ Check the camera mount and its fixing: its tilt wanders a little over days and j
| 2026-10-19 09:00 | 2026-10-19 10:10 | No data | all | common gaps |
| 2026-10-19 20:40 | 2026-10-19 21:30 | No data | all | common gaps |
| 2026-10-20 00:10 | 2026-10-20 00:40 | Displacement | D-306-B, D-302-B/PR_BG, D-303-C, D-304-C, D-304-B, D-303-B, P-301-B | camera jump; most come back, D-306-B and D-302-B keep a jump |
## Update 2026-11-18: Displacement labels pruned
At your request, only the significant displacements of CLARIDEN were kept: the small ones that come back later were removed from this analysis. The labels.jsonl here is the current list, and the table above is out of date for Displacement. Which labels were removed and why: `CLARIDEN_2026-10-01T0000_2026-11-01T0000/analysis.md`.
@@ -1,21 +1,14 @@
{"start": "2026-10-20T04:00Z", "end": "2026-10-25T18:00Z", "family": "Displacement", "description": "Slow drift of targets of row C, then stabilization at a new level: D-301-C rises horizontally from the 20th, D-304-C and D-303-C rise vertically mostly from the 22nd. No camera movement, ordinary recognition error. The rise of D-301-C starts before the work seen around the station on the 22nd (workers and a frame): no link established. The position in the image of D-301-C, D-304-C and D-303-C moves clearly 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. Partial return from the 26th to the 29th, 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"}
{"start": "2026-10-20T04:00Z", "end": "2026-10-25T18:00Z", "family": "Displacement", "description": "Slow drift of targets of row C, then stabilization at a new level: D-301-C rises horizontally from the 20th, D-304-C and D-303-C rise vertically mostly from the 22nd. No camera movement, ordinary recognition error. The rise of D-301-C starts before the work seen around the station on the 22nd (workers and a frame): no link established. The position in the image of D-301-C, D-304-C and D-303-C moves clearly 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. D-304-C and D-303-C then come back down a little from the 26th to the 29th, without returning to their level from before: too small to be labeled. 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-18"}
{"start": "2026-10-20T06:10Z", "end": "2026-10-20T06:30Z", "family": "No data", "description": "One measurement is missing, for all sensors: the curves have a short gap; the station nevertheless synchronizes at that moment, normal voltage. The same moment is also missing at LENZSPITZE, and at no other station: a common cause outside the station is possible, not established. Nothing to do.", "review": "2026-11-17"}
{"start": "2026-10-20T20:40Z", "end": "2026-10-20T21:40Z", "family": "No data", "description": "Five measurements are missing within one hour, for all sensors: the curves have a gap. The station is nevertheless running (continuous synchronizations, 21:00 image, normal voltage): the measurement is not made or not recorded. The 21:00 measurement is also missing at NIEDERHORN, and at no other station: a common cause is possible, not established. Nothing to do."}
{"start": "2026-10-22T06:30Z", "end": "2026-10-22T08:50Z", "family": "Visibility", "description": "In two phases, from 06:40 to 06:50 then from 07:50 to 08:30, the recognition error of several targets and of the references D-302-C and PR-293 rises, and the corrected curves of the usual group make a bump that comes back: D-301-C horizontally, D-302-B and PR_BG vertically, P-301-B, D-304-B, D-304-C, and at the start D-302_A, P-298-A, D-304-A, D-303-A; between the two, D-302-B and PR_BG move once more. The camera housing temperature drops during these hours. The 08:00 image shows lights at the far end of the tunnel (machine or vehicle), nothing in front of the targets. Diffuse view obstruction of cause not established, the same as in the other episodes at the station. Curves to ignore over the range; the structure does not move."}
{"start": "2026-10-22T08:50Z", "end": "2026-10-22T17:00Z", "family": "Displacement", "description": "The low targets of row B rise vertically during the day: D-306-B above all, D-302-B and PR_BG, D-304-B, D-303-B; the recognition error of a few of them rises a little. Workers are visible in the tunnel on the 12:00 image, and a frame appears very close to the camera at the top of the image at 13:00 (it stays there until the end of the batch): work around the station. The position in the image of D-306-B rises a little relative to the other targets, in the direction of its curve. The link between this work and the rise is not established. Evening descent, 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."}
{"start": "2026-10-22T17:00Z", "end": "2026-10-23T10:30Z", "family": "Displacement", "description": "The low targets of row B go back down vertically, all at once on the evening of the 22nd then more slowly on the morning of the 23rd, to below their level from before their rise of the day: D-306-B above all, D-304-B, D-303-B, D-302-B and PR_BG. No camera movement; the frame installed on the 22nd stays at the top of the image (19:00 image), nothing else. The position in the image of D-306-B also goes down relative to the other targets. This is the return of the rise of the day, labeled separately, and it goes beyond it. 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"}
{"start": "2026-10-24T01:00Z", "end": "2026-10-24T05:00Z", "family": "Displacement", "description": "The low targets of row B (D-306-B above all, D-304-B, D-303-B) partly rise again vertically in the night of the 24th, toward their level from before the descent of the evening of the 22nd, without reaching it. No camera movement. 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"}
{"start": "2026-10-24T18:20Z", "end": "2026-10-25T19:10Z", "family": "Displacement", "description": "The left targets of row A (D-302_A, D-303-A, D-304-A, D-301-A, P-299-A) and D-304-B, D-306-B, P-301-B fidget in jolts (around 18:30 and 21:30 on the 24th, 07:00 and 15:30 on the 25th): the vertical rises, the horizontal goes down; the recognition error of these targets and of the reference D-302-C rises during the first jolts, and the references PR-291 and PR-293 move slightly away from the targets in the image. Everything calms down on the evening of the 25th. After the agitation, the horizontal of the A targets stays shifted until the end of the batch. Workers are visible on the image of the 24th at 15:00 and the frame is still at the top of the image. Cause not established: shift to be checked.", "review": "2026-11-17"}
{"start": "2026-10-25T18:00Z", "end": "2026-10-29T04:00Z", "family": "Displacement", "description": "After their rise of the 20th to the 25th, D-304-C and D-303-C slowly go back down vertically from the 26th to the 29th, without returning to their level from before the rise, then stabilize. No camera movement, nothing in front of the targets on the images of the 28th at 19:00 and 20:00. Their position in the image also partly returns toward that of the other targets. This is the partial return of the rise of the 20th to the 25th, 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"}
{"start": "2026-10-25T19:10Z", "end": "2026-10-29T04:00Z", "family": "Displacement", "description": "After their rise in jolts of the 24th and 25th, the left targets of row A slowly go back down vertically from the 26th to the 29th, back to about their level from before the jolts: D-304-A, D-303-A, D-302_A and D-301-A above all, P-299-A and P-298-A less; their horizontal stays shifted. Their position in the image comes back with their curves, relative to the other targets; no camera step, ordinary recognition error. Same dates as the partial return of D-304-C and D-303-C, labeled separately. This is the return of the agitation of the 24th and 25th, 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."}
{"start": "2026-10-26T14:30Z", "end": "2026-10-26T15:10Z", "family": "No data", "description": "Three measurements are missing in less than an hour, for all sensors: the curves have a gap; normal voltage around it. The same gap falls at the same moment on the other stations measuring at that time (FLORIDA, JUNGFRAU, LENZSPITZE, NIEDERHORN, NORDEND, SNCF01), and their metrics are also missing at the same minutes: a common cause outside the station (transmission or reception of the data), not a failure of the station; it is not established. The curves are missing over the range; nothing to do on the station. The hourly metrics of BREITHORN, MICHIGAN and NEBRASKA are also missing at 15:00."}
{"start": "2026-10-20T20:40Z", "end": "2026-10-20T21:40Z", "family": "No data", "description": "Five measurements are missing within one hour, for all sensors: the curves have a gap. The station is nevertheless running (continuous synchronizations, 21:00 image, normal voltage): the measurement is not made or not recorded. The 21:00 measurement is also missing at NIEDERHORN, and at no other station: a common cause is possible, not established. Nothing to do.", "review": "2026-11-18"}
{"start": "2026-10-22T06:30Z", "end": "2026-10-22T08:50Z", "family": "Visibility", "description": "In two phases, from 06:40 to 06:50 then from 07:50 to 08:30, the recognition error of several targets and of the references D-302-C and PR-293 rises, and the corrected curves of the usual group make a bump that comes back: D-301-C horizontally, D-302-B and PR_BG vertically, P-301-B, D-304-B, D-304-C, and at the start D-302_A, P-298-A, D-304-A, D-303-A; between the two, D-302-B and PR_BG move once more. The camera housing temperature drops during these hours. The 08:00 image shows lights at the far end of the tunnel (machine or vehicle), nothing in front of the targets. Diffuse view obstruction of cause not established, the same as in the other episodes at the station. Curves to ignore over the range; the structure does not move.", "review": "2026-11-18"}
{"start": "2026-10-26T14:30Z", "end": "2026-10-26T15:10Z", "family": "No data", "description": "Three measurements are missing in less than an hour, for all sensors: the curves have a gap; normal voltage around it. The same gap falls at the same moment on the other stations measuring at that time (FLORIDA, JUNGFRAU, LENZSPITZE, NIEDERHORN, NORDEND, SNCF01), and their metrics are also missing at the same minutes: a common cause outside the station (transmission or reception of the data), not a failure of the station; it is not established. The curves are missing over the range; nothing to do on the station. The hourly metrics of BREITHORN, MICHIGAN and NEBRASKA are also missing at 15:00.", "review": "2026-11-18"}
{"start": "2026-10-27T09:00Z", "end": "2026-10-27T09:30Z", "family": "No data", "description": "Two measurements are missing, for all sensors: the curves have a short gap; normal voltage around it. The same gap falls at the same moment on the other stations measuring at that time (FLORIDA, JUNGFRAU, LENZSPITZE, NORDEND): a common cause outside the station (transmission or reception of the data), not a failure of the station; it is not established. The curves are missing over the range; nothing to do on the station.", "review": "2026-11-17"}
{"start": "2026-10-27T12:00Z", "end": "2026-10-27T12:20Z", "family": "Target issue", "description": "For the duration of one measurement, the target PR-284 jumps by several pixels horizontally and vertically, then returns: the measured position has left its spot, with a high recognition error but under the threshold, so kept in the curve. Since 24 October around 14:20, the spot of PR-284 is clearly weaker (thumbnails of the 24th at 12:00 and 16:00, of the 27th at 12:00) and its recognition error has stayed high. False point to ignore; look at the state of the target PR-284 if the false points repeat.", "review": "2026-11-17"}
{"start": "2026-10-28T19:20Z", "end": "2026-10-28T20:10Z", "family": "Displacement", "description": "On the evening of the 28th, the low targets of row B go down by a step vertically, D-306-B above all, then D-304-B, and stay at this new level until the end of the batch; D-303-B and D-304-B also go down a little horizontally. The position in the image of D-306-B goes down a little relative to the other targets, no camera movement, nothing on the 19:00 and 20:00 images (the frame at the top of the image is still there). 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"}
{"start": "2026-10-29T14:50Z", "end": "2026-10-29T15:10Z", "family": "No data", "description": "One measurement is missing, for all sensors: the curves have a short gap; the station nevertheless synchronizes at that moment, normal voltage. The same gap falls at the same moment on the other stations measuring at that time (LENZSPITZE, NORDEND, SNCF01): a common cause outside the station (transmission or reception of the data), not a failure of the station; it is not established. The curves are missing over the range; nothing to do on the station.", "review": "2026-11-17"}
{"start": "2026-10-29T23:50Z", "end": "2026-10-30T00:10Z", "family": "Target issue", "description": "At midnight, D-302-B jumps vertically and a little horizontally and stays at this new level until the end of the batch; PR_BG, on the same prism, jumps in the opposite direction. The raw positions of the two sensors do not move, only their starting position has changed (the relative displacement jumps without any movement in the image): a configuration or processing change of these two sensors, not a movement of the structure. Check their configuration with the operator; do not read this jump as a movement, nor compare their curves before and after."}
{"start": "2026-10-30T17:00Z", "end": "2026-10-30T17:50Z", "family": "No data", "description": "Four measurements are missing in less than an hour, for all sensors: the curves have a gap. The station's own record stops too: its minute-by-minute synchronizations are missing over the same half hour, while the 17:00 image exists and the voltage stays normal before and after, so it is not a lack of energy. The other stations measuring at that time (ALASKA, FLORIDA, JUNGFRAU, LENZSPITZE, NADELHORN, NORDEND, SNCF01, WYOMING) have their measurements: the cause is specific to the station, not established. The curves are missing over the range; nothing to do unless it repeats."}
{"start": "2026-10-31T09:20Z", "end": "2026-10-31T15:00Z", "family": "Thermal displacement", "description": "The camera housing temperature rises a little in the late morning of the 31st, and the camera scale rises with it while the pan goes down, until early afternoon; they come back when the housing cools, mostly during the view obstruction of the early afternoon, labeled separately. The compensation absorbs most of it, but a few corrected curves follow a little over these hours and come back with it: D-301-C horizontally, D-304-C, D-303-C and D-304-B vertically. Only a light at the far end of the tunnel on the 12:00 image, nothing in front of the targets. Camera movement by thermal effect, deduced from its pose against the housing temperature; normal, nothing to do."}
{"start": "2026-10-31T13:50Z", "end": "2026-10-31T15:10Z", "family": "Visibility", "description": "For one hour, the corrected curves of the usual group make a bump that comes back: D-301-C (horizontal), D-302-B and PR_BG (vertical), D-301-A, D-300-A, D-304-B, D-304-C, D-302_A, and for a moment the reference PR-295; the recognition error of a few sensors rises during the episode. Same signature as the other episodes of view obstruction at the station; cause not established. Curves to ignore over the range."}
{"start": "2026-10-31T18:40Z", "end": "2026-10-31T20:00Z", "family": "Visibility", "description": "For the duration of a few measurements, the corrected curves of D-301-C, P-301-B, P-299-A, D-302-B and PR_BG, D-303-B make a bump that comes back, and the reference PR-295, which is seen less well from 18:50, leaves its level; it is rejected at 19:50 (its curve is missing at that measurement), without the targets moving because of it. View obstruction of cause not established; points to ignore."}
{"start": "2026-10-31T22:20Z", "end": "2026-11-01T00:00Z", "family": "Visibility", "description": "The reference PR-295 is seen poorly: its spot is weaker (23:00 thumbnail), it is rejected at times and, between two rejections, it is poorly measured; the compensation changes basis, and at 22:50 many targets jump together then return, without any movement of their raw positions. Until 23:50, the curves of D-301-C, P-301-B, D-302-B and PR_BG stay shifted, then briefly cross to the other side, with the recognition error of several targets rising. The camera housing temperature drops clearly at that hour. Cause of the obstruction not established (same signature as the other episodes). The jumps are not a movement: curves to ignore over the range."}
{"start": "2026-10-29T23:50Z", "end": "2026-10-30T00:10Z", "family": "Target issue", "description": "At midnight, D-302-B jumps vertically and a little horizontally and stays at this new level until the end of the batch; PR_BG, on the same prism, jumps in the opposite direction. The raw positions of the two sensors do not move, only their starting position has changed (the relative displacement jumps without any movement in the image): a configuration or processing change of these two sensors, not a movement of the structure. Check their configuration with the operator; do not read this jump as a movement, nor compare their curves before and after.", "review": "2026-11-18"}
{"start": "2026-10-30T17:00Z", "end": "2026-10-30T17:50Z", "family": "No data", "description": "Four measurements are missing in less than an hour, for all sensors: the curves have a gap. The station's own record stops too: its minute-by-minute synchronizations are missing over the same half hour, while the 17:00 image exists and the voltage stays normal before and after, so it is not a lack of energy. The other stations measuring at that time (ALASKA, FLORIDA, JUNGFRAU, LENZSPITZE, NADELHORN, NORDEND, SNCF01, WYOMING) have their measurements: the cause is specific to the station, not established. The curves are missing over the range; nothing to do unless it repeats.", "review": "2026-11-18"}
{"start": "2026-10-31T09:20Z", "end": "2026-10-31T15:00Z", "family": "Thermal displacement", "description": "The camera housing temperature rises a little in the late morning of the 31st, and the camera scale rises with it while the pan goes down, until early afternoon; they come back when the housing cools, mostly during the view obstruction of the early afternoon, labeled separately. The compensation absorbs most of it, but a few corrected curves follow a little over these hours and come back with it: D-301-C horizontally, D-304-C, D-303-C and D-304-B vertically. Only a light at the far end of the tunnel on the 12:00 image, nothing in front of the targets. Camera movement by thermal effect, deduced from its pose against the housing temperature; normal, nothing to do.", "review": "2026-11-18"}
{"start": "2026-10-31T13:50Z", "end": "2026-10-31T15:10Z", "family": "Visibility", "description": "For one hour, the corrected curves of the usual group make a bump that comes back: D-301-C (horizontal), D-302-B and PR_BG (vertical), D-301-A, D-300-A, D-304-B, D-304-C, D-302_A, and for a moment the reference PR-295; the recognition error of a few sensors rises during the episode. Same signature as the other episodes of view obstruction at the station; cause not established. Curves to ignore over the range.", "review": "2026-11-18"}
{"start": "2026-10-31T18:40Z", "end": "2026-10-31T20:00Z", "family": "Visibility", "description": "For the duration of a few measurements, the corrected curves of D-301-C, P-301-B, P-299-A, D-302-B and PR_BG, D-303-B make a bump that comes back, and the reference PR-295, which is seen less well from 18:50, leaves its level; it is rejected at 19:50 (its curve is missing at that measurement), without the targets moving because of it. View obstruction of cause not established; points to ignore.", "review": "2026-11-18"}
{"start": "2026-10-31T22:20Z", "end": "2026-11-01T00:00Z", "family": "Visibility", "description": "The reference PR-295 is seen poorly: its spot is weaker (23:00 thumbnail), it is rejected at times and, between two rejections, it is poorly measured; the compensation changes basis, and at 22:50 many targets jump together then return, without any movement of their raw positions. Until 23:50, the curves of D-301-C, P-301-B, D-302-B and PR_BG stay shifted, then briefly cross to the other side, with the recognition error of several targets rising. The camera housing temperature drops clearly at that hour. Cause of the obstruction not established (same signature as the other episodes). The jumps are not a movement: curves to ignore over the range.", "review": "2026-11-18"}
@@ -81,3 +81,7 @@ No weather is available for this station (a tunnel without a weather folder).
| 2026-10-31 13:50 | 2026-10-31 15:10 | Visibility | D-301-C, D-302-B, PR_BG | view obstruction |
| 2026-10-31 18:40 | 2026-10-31 20:00 | Visibility | D-301-C, P-299-A, PR-295 | view obstruction |
| 2026-10-31 22:20 | 2026-11-01 00:00 | Visibility | PR-295, many targets | reference seen badly, targets jump |
## Update 2026-11-18: Displacement labels pruned
At your request, only the significant displacements of CLARIDEN were kept: the small ones that come back later were removed from this analysis. The labels.jsonl here is the current list, and the table above is out of date for Displacement. Which labels were removed and why: `CLARIDEN_2026-10-01T0000_2026-11-01T0000/analysis.md`.
@@ -1,12 +1,12 @@
{"start": "2026-10-04T08:45Z", "end": "2026-10-04T16:30Z", "family": "Visibility", "description": "By day (04/10), sunny day (cast shadows on the wall on the image of 12:00): the corrected curves of the low targets fluctuate from one measurement to the next beyond their noise, mostly CV.4 (corr_x and corr_y), F4.2, BG.2, BG.3, with one-measurement jumps that come back at once; late in the morning, BG.3, F4.2, BG.2 and the P targets jump together in corr_x for one measurement; CV.2 and CV.4 are rejected at times (missing points). At night everything is calm again. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast, which makes the spots tremble (a fast noise, by day only, with the recognition error of these low targets rising), nothing in front of the targets on the images. Do not trust the small movements of these curves over the range; this is not a movement of the structure."}
{"start": "2026-10-04T08:45Z", "end": "2026-10-04T16:30Z", "family": "Visibility", "description": "By day (04/10), sunny day (cast shadows on the wall on the image of 12:00): the corrected curves of the low targets fluctuate from one measurement to the next beyond their noise, mostly CV.4 (corr_x and corr_y), F4.2, BG.2, BG.3, with one-measurement jumps that come back at once; late in the morning, BG.3, F4.2, BG.2 and the P targets jump together in corr_x for one measurement; CV.2 and CV.4 are rejected at times (missing points). At night everything is calm again. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast, which makes the spots tremble (a fast noise, by day only, with the recognition error of these low targets rising), nothing in front of the targets on the images. Do not trust the small movements of these curves over the range; this is not a movement of the structure.", "review": "2026-11-18"}
{"start": "2026-10-04T09:00Z", "end": "2026-10-05T06:30Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (04/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 all night, until the start of the next morning. 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"}
{"start": "2026-10-05T06:30Z", "end": "2026-10-06T07:15Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (05/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 all night, until the start of the next morning. 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"}
{"start": "2026-10-05T07:00Z", "end": "2026-10-05T15:15Z", "family": "Visibility", "description": "By day (05/10), sunny day (cast shadows on the image of 12:00): the corrected curves of the low targets fluctuate from one measurement to the next beyond their noise, the most strongly of the batch: CV.4 and CV.2 in both columns, F4.2, BG.3, and in late morning the corr_y of P1, P2, P3 jump together for one or two measurements; CV.2, CV.4 and F4.2 are rejected at times (missing points). Calm again before nightfall; the train of 16:00 is labelled apart. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast, which makes the spots tremble (a fast noise, by day only, with the recognition error of these low targets rising), nothing in front of the targets on the images. Do not trust the small movements of these curves over the range; this is not a movement of the structure."}
{"start": "2026-10-05T07:00Z", "end": "2026-10-05T15:15Z", "family": "Visibility", "description": "By day (05/10), sunny day (cast shadows on the image of 12:00): the corrected curves of the low targets fluctuate from one measurement to the next beyond their noise, the most strongly of the batch: CV.4 and CV.2 in both columns, F4.2, BG.3, and in late morning the corr_y of P1, P2, P3 jump together for one or two measurements; CV.2, CV.4 and F4.2 are rejected at times (missing points). Calm again before nightfall; the train of 16:00 is labelled apart. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast, which makes the spots tremble (a fast noise, by day only, with the recognition error of these low targets rising), nothing in front of the targets on the images. Do not trust the small movements of these curves over the range; this is not a movement of the structure.", "review": "2026-11-18"}
{"start": "2026-10-05T15:45Z", "end": "2026-10-05T16:15Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 and some of the P) are rejected and their curves are missing; the references are affected too (BG.3.1 and R1 rejected), the compensation retains none of them, and the targets that stayed under the threshold (BG.2, BG.3, F4.5 and some P) jump in corr_x and corr_y for the time of the measurement. Everything comes back at the next measurement. Cause: a passage in front of the targets and the references, a train passing, blurred, in front of the wall and the targets, seen on the 16:00 image. The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-17"}
{"start": "2026-10-06T07:00Z", "end": "2026-10-06T13:15Z", "family": "Visibility", "description": "By day (06/10), sunny morning (cast shadows on the image of 12:00): the corrected curves of the low targets fluctuate beyond their noise, mostly CV.4 in corr_x, F4.2 in both columns and CV.2, with one-measurement jumps that come back at once; CV.2 and CV.4 are rejected at times (missing points). The other targets stay within their noise; calm again from early afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast, which makes the spots tremble (a fast noise, by day only, with the recognition error of these low targets rising), nothing in front of the targets on the images. Do not trust the small movements of these curves over the range; this is not a movement of the structure."}
{"start": "2026-10-06T07:15Z", "end": "2026-10-07T03:00Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (06/10), sunny day (cast shadows on the image of 12:00): from the morning, the pan and the tilt of the camera drop strongly and its scale rises, until early afternoon; they come back slowly in the afternoon, the evening and the first half of the night. The compensation absorbs only part of it: corr_x of P7 rises clearly, with corr_y of P6 and P7, while corr_x of P1 drops and that of P5 rises; the curves come back to their night level late in the evening, the pose in the night. 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."}
{"start": "2026-10-07T07:30Z", "end": "2026-10-08T04:15Z", "family": "Thermal displacement", "description": "Weak daytime thermal cycle (07/10), overcast day (image of 12:00): in the morning, the pan and the tilt of the camera drop a little and its scale rises a little, then the camera stays in that position all afternoon; it comes back in the evening and all night, beyond its position of the previous night, until early on the 8th. The corrected curves follow, less than on the sunny days: corr_x of P5 and P7 rises, corr_y of P7 and P6 too, corr_x of P1 drops; P7 comes back late in the evening, P5 only after midnight. The three train passages of the day (13:00, 16:00, 19:45) are labelled apart. 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."}
{"start": "2026-10-07T12:45Z", "end": "2026-10-07T13:15Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 except F4.5 and F4.6, and all the P) are rejected and their curves are missing; the references are affected too (R1 rejected, BG.3.1 just under its threshold and left out), the compensation retains none of them; the targets that stayed under the threshold jump a little beyond their noise, BG.3 in corr_x, F4.5 and F4.6 in corr_y. Everything comes back at the next measurement. Cause seen: a train passing in front of the wall and the targets, blurred, on the image of 13:00. The structure is not moving: point to ignore, nothing to do."}
{"start": "2026-10-06T07:00Z", "end": "2026-10-06T13:15Z", "family": "Visibility", "description": "By day (06/10), sunny morning (cast shadows on the image of 12:00): the corrected curves of the low targets fluctuate beyond their noise, mostly CV.4 in corr_x, F4.2 in both columns and CV.2, with one-measurement jumps that come back at once; CV.2 and CV.4 are rejected at times (missing points). The other targets stay within their noise; calm again from early afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast, which makes the spots tremble (a fast noise, by day only, with the recognition error of these low targets rising), nothing in front of the targets on the images. Do not trust the small movements of these curves over the range; this is not a movement of the structure.", "review": "2026-11-18"}
{"start": "2026-10-06T07:15Z", "end": "2026-10-07T03:00Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (06/10), sunny day (cast shadows on the image of 12:00): from the morning, the pan and the tilt of the camera drop strongly and its scale rises, until early afternoon; they come back slowly in the afternoon, the evening and the first half of the night. The compensation absorbs only part of it: corr_x of P7 rises clearly, with corr_y of P6 and P7, while corr_x of P1 drops and that of P5 rises; the curves come back to their night level late in the evening, the pose in the night. 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-18"}
{"start": "2026-10-07T07:30Z", "end": "2026-10-08T04:15Z", "family": "Thermal displacement", "description": "Weak daytime thermal cycle (07/10), overcast day (image of 12:00): in the morning, the pan and the tilt of the camera drop a little and its scale rises a little, then the camera stays in that position all afternoon; it comes back in the evening and all night, beyond its position of the previous night, until early on the 8th. The corrected curves follow, less than on the sunny days: corr_x of P5 and P7 rises, corr_y of P7 and P6 too, corr_x of P1 drops; P7 comes back late in the evening, P5 only after midnight. The three train passages of the day (13:00, 16:00, 19:45) are labelled apart. 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-18"}
{"start": "2026-10-07T12:45Z", "end": "2026-10-07T13:15Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 except F4.5 and F4.6, and all the P) are rejected and their curves are missing; the references are affected too (R1 rejected, BG.3.1 just under its threshold and left out), the compensation retains none of them; the targets that stayed under the threshold jump a little beyond their noise, BG.3 in corr_x, F4.5 and F4.6 in corr_y. Everything comes back at the next measurement. Cause seen: a train passing in front of the wall and the targets, blurred, on the image of 13:00. The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-18"}
{"start": "2026-10-07T15:45Z", "end": "2026-10-07T16:15Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 and some of the P) are rejected and their curves are missing; the references are affected too (BG.3.1 and R1 rejected), the compensation retains none of them, and the targets that stayed under the threshold (BG.2, BG.3, F4.5 and some P) jump in corr_x and corr_y for the time of the measurement. Everything comes back at the next measurement. Cause: a passage in front of the targets and the references, a train passing in front of the targets, seen on the 16:00 image. The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-17"}
{"start": "2026-10-07T19:30Z", "end": "2026-10-07T20:00Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 and some of the P) are rejected and their curves are missing; the references are affected too (BG.3.1 rejected), the compensation retains none of them, and the targets that stayed under the threshold (BG.2, BG.3, F4.5 and some P) jump in corr_x and corr_y for the time of the measurement. Everything comes back at the next measurement. Cause: a passage in front of the targets and the references, no image at that moment; deduced from the signature, the same as that of the trains seen on the images of the other passages. The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-17"}
{"start": "2026-10-08T06:45Z", "end": "2026-10-08T16:30Z", "family": "Visibility", "description": "By day (08/10): the corrected curves of all targets fluctuate much more than at night, from one measurement to the next, especially CV.2, CV.4, F4.2, BG.3, CV.6, CV.9, with one-measurement jumps that come back at once, and CV.2, CV.4 (sometimes F4.2) are rejected at times, their curves having gaps; their recognition error varies strongly by day. At night everything becomes calm again. Deduced cause: heat shimmer from the air heated above the tracks (a fast noise over the whole scene, by day only), not visible on the images; the 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.", "review": "2026-11-17"}
@@ -15,14 +15,14 @@
{"start": "2026-10-09T07:00Z", "end": "2026-10-10T06:00Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (09/10), with no return in the evening: in the morning, the pan and the tilt of the camera drop and its scale rises, then the camera stays in that position all afternoon and evening; it comes back only slowly during the night, on the morning of the 10th. The corrected curves follow, poorly compensated: corr_x of P1, P2, P5, P6, P7 moves away from its night level during the day, stays away in the evening and comes back only on the morning of the 10th. 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"}
{"start": "2026-10-10T01:45Z", "end": "2026-10-10T02:15Z", "family": "No data", "description": "One measurement is missing, for all sensors, around two in the morning: all curves have a gap; the image of that moment exists nonetheless. The power metrics of the station are empty over the whole month. This one-measurement night gap, around 02:00 UTC, falls at the same measurement on FLORIDA and SNCF01 on 09, 14 and 15/10, and only on them (that night, on SNCF01 alone); other stations have the same night gap around the same hour on 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"}
{"start": "2026-10-10T07:00Z", "end": "2026-10-11T08:30Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (10/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 all night, until the start of the next morning. 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"}
{"start": "2026-10-10T07:00Z", "end": "2026-10-10T13:00Z", "family": "Visibility", "description": "By day (10/10), sunny morning (cast shadows on the image of 12:00): the corrected curves of the low targets fluctuate beyond their noise, mostly CV.4 in both columns, CV.9 and CV.2 in corr_y, F4.2 and F4.5, and in mid-morning BG.3, P2, P3 jump together in corr_x for one measurement; they come back at once. Calm again from early afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast, which makes the spots tremble (a fast noise, by day only, with the recognition error of these low targets rising), nothing in front of the targets on the images. Do not trust the small movements of these curves over the range; this is not a movement of the structure."}
{"start": "2026-10-11T10:00Z", "end": "2026-10-11T15:30Z", "family": "Visibility", "description": "By day (11/10), overcast day (image of 12:00), the weakest agitation of the batch that still crosses the noise: CV.4 in corr_y, F4.2, CV.2, and P1, P2 in corr_y make a few one-measurement jumps just beyond their noise, coming back at once; the train of 14:15 is labelled apart. Calm at night. Deduced cause: a weak shimmer of the air above the tracks by day, the same signature as on the sunny days, much weaker; nothing in front of the targets on the images. Do not trust the small movements of these curves over the range; this is not a movement of the structure."}
{"start": "2026-10-11T08:30Z", "end": "2026-10-12T02:45Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (11/10), overcast day (image of 12:00): from the morning, the pan and the tilt of the camera drop and its scale rises, until early afternoon; they come back in the late afternoon, the evening and the first half of the night, beyond their position of the previous night. The compensation absorbs part of it: corr_x of P7 rises clearly, with corr_y of P6 and P5, while corr_x of P1 drops; the curves are back at their night level in the evening, the pose in the night. The train of 14:15 is labelled apart. 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."}
{"start": "2026-10-11T14:00Z", "end": "2026-10-11T14:30Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 and all the P) are rejected and their curves are missing; the references are affected too (BG.3.1 and R1 rejected), the compensation retains none of them, and the targets that stayed under the threshold, BG.2, BG.3 and F4.5, jump strongly in corr_x and corr_y for the time of the measurement. Everything comes back at the next measurement. Cause: a passage in front of the targets and the references; the camera takes its image on the hour, none at that measurement; deduced from the signature, the same as that of the trains seen on the images of the other passages. The structure is not moving: point to ignore, nothing to do."}
{"start": "2026-10-12T06:30Z", "end": "2026-10-12T07:00Z", "family": "Obstruction", "description": "One single measurement, early in the morning: CV.8 and F4.2 go above their threshold (CV.6 too), their curves are missing, and the recognition error of most CV and F4 targets and of the reference BG.3.1 rises; CV.4, left under its threshold with its recognition error dropping, jumps clearly in corr_x for that measurement, and comes back at the next one. The references hold, the other targets stay within their noise. Cause deduced from the signature: a partial passage in front of the low targets, CV.4 latching onto a light or a reflection; no image at that measurement (the camera takes one on the hour). The structure is not moving: point to ignore, nothing to do."}
{"start": "2026-10-12T07:30Z", "end": "2026-10-12T14:45Z", "family": "Visibility", "description": "By day (12/10), sunny day (cast shadows on the image of 12:00): the corrected curves of the low targets fluctuate beyond their noise, mostly CV.4 in both columns, F4.2, CV.2, F4.5, F4.6, and in mid-morning BG.3, F4.2, F4.6, P2, P3, P4, P6 jump together in corr_x for one measurement; they come back at once; CV.2 and CV.4 are rejected at times (missing points). Calm again in the afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast, which makes the spots tremble (a fast noise, by day only, with the recognition error of these low targets rising), nothing in front of the targets on the images. Do not trust the small movements of these curves over the range; this is not a movement of the structure."}
{"start": "2026-10-10T07:00Z", "end": "2026-10-10T13:00Z", "family": "Visibility", "description": "By day (10/10), sunny morning (cast shadows on the image of 12:00): the corrected curves of the low targets fluctuate beyond their noise, mostly CV.4 in both columns, CV.9 and CV.2 in corr_y, F4.2 and F4.5, and in mid-morning BG.3, P2, P3 jump together in corr_x for one measurement; they come back at once. Calm again from early afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast, which makes the spots tremble (a fast noise, by day only, with the recognition error of these low targets rising), nothing in front of the targets on the images. Do not trust the small movements of these curves over the range; this is not a movement of the structure.", "review": "2026-11-18"}
{"start": "2026-10-11T10:00Z", "end": "2026-10-11T15:30Z", "family": "Visibility", "description": "By day (11/10), overcast day (image of 12:00), the weakest agitation of the batch that still crosses the noise: CV.4 in corr_y, F4.2, CV.2, and P1, P2 in corr_y make a few one-measurement jumps just beyond their noise, coming back at once; the train of 14:15 is labelled apart. Calm at night. Deduced cause: a weak shimmer of the air above the tracks by day, the same signature as on the sunny days, much weaker; nothing in front of the targets on the images. Do not trust the small movements of these curves over the range; this is not a movement of the structure.", "review": "2026-11-18"}
{"start": "2026-10-11T08:30Z", "end": "2026-10-12T02:45Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (11/10), overcast day (image of 12:00): from the morning, the pan and the tilt of the camera drop and its scale rises, until early afternoon; they come back in the late afternoon, the evening and the first half of the night, beyond their position of the previous night. The compensation absorbs part of it: corr_x of P7 rises clearly, with corr_y of P6 and P5, while corr_x of P1 drops; the curves are back at their night level in the evening, the pose in the night. The train of 14:15 is labelled apart. 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-18"}
{"start": "2026-10-11T14:00Z", "end": "2026-10-11T14:30Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 and all the P) are rejected and their curves are missing; the references are affected too (BG.3.1 and R1 rejected), the compensation retains none of them, and the targets that stayed under the threshold, BG.2, BG.3 and F4.5, jump strongly in corr_x and corr_y for the time of the measurement. Everything comes back at the next measurement. Cause: a passage in front of the targets and the references; the camera takes its image on the hour, none at that measurement; deduced from the signature, the same as that of the trains seen on the images of the other passages. The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-18"}
{"start": "2026-10-12T06:30Z", "end": "2026-10-12T07:00Z", "family": "Obstruction", "description": "One single measurement, early in the morning: CV.8 and F4.2 go above their threshold (CV.6 too), their curves are missing, and the recognition error of most CV and F4 targets and of the reference BG.3.1 rises; CV.4, left under its threshold with its recognition error dropping, jumps clearly in corr_x for that measurement, and comes back at the next one. The references hold, the other targets stay within their noise. Cause deduced from the signature: a partial passage in front of the low targets, CV.4 latching onto a light or a reflection; no image at that measurement (the camera takes one on the hour). The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-18"}
{"start": "2026-10-12T07:30Z", "end": "2026-10-12T14:45Z", "family": "Visibility", "description": "By day (12/10), sunny day (cast shadows on the image of 12:00): the corrected curves of the low targets fluctuate beyond their noise, mostly CV.4 in both columns, F4.2, CV.2, F4.5, F4.6, and in mid-morning BG.3, F4.2, F4.6, P2, P3, P4, P6 jump together in corr_x for one measurement; they come back at once; CV.2 and CV.4 are rejected at times (missing points). Calm again in the afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast, which makes the spots tremble (a fast noise, by day only, with the recognition error of these low targets rising), nothing in front of the targets on the images. Do not trust the small movements of these curves over the range; this is not a movement of the structure.", "review": "2026-11-18"}
{"start": "2026-10-12T08:00Z", "end": "2026-10-14T04:00Z", "family": "Thermal displacement", "description": "Thermal cycle of 12 and 13/10, as one single episode: on the 12th, from the morning, the pan and the tilt of the camera drop and its scale rises; during the night from 12 to 13, the camera comes back only in part, and the corrected curves do not come back: corr_x of P1, P5, P6, P7 and corr_y of P4, P5, P6, P7 stay away from their night level all night, while the recognition error of the P rises a little; on the 13th, a second daytime dip is added to it, then everything comes back on the evening of the 13th and during the night, on the morning of the 14th. Deduced cause: the camera and its mount move with the heat of the day (camera pose); the night without return is not explained, no temperature being available. Nothing to do.", "review": "2026-11-17"}
{"start": "2026-10-12T15:45Z", "end": "2026-10-12T16:15Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 and all the P) are rejected and their curves are missing; the references are affected too (BG.3.1 and R1 rejected), the compensation retains none of them, and the targets that stayed under the threshold, BG.2, BG.3 and F4.5, jump strongly in corr_x and corr_y for the time of the measurement. Everything comes back at the next measurement. Cause seen: a train passing in front of the wall and the targets, blurred, on the image of 16:00. The structure is not moving: point to ignore, nothing to do."}
{"start": "2026-10-12T15:45Z", "end": "2026-10-12T16:15Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 and all the P) are rejected and their curves are missing; the references are affected too (BG.3.1 and R1 rejected), the compensation retains none of them, and the targets that stayed under the threshold, BG.2, BG.3 and F4.5, jump strongly in corr_x and corr_y for the time of the measurement. Everything comes back at the next measurement. Cause seen: a train passing in front of the wall and the targets, blurred, on the image of 16:00. The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-18"}
{"start": "2026-10-13T01:45Z", "end": "2026-10-13T02:15Z", "family": "No data", "description": "One measurement is missing, for all sensors, around two in the morning: all curves have a gap; no image at that moment. The power metrics of the station are empty over the whole month. This one-measurement night gap, around 02:00 UTC, falls at the same measurement on FLORIDA and SNCF01 on 09, 14 and 15/10, and only on them (that night, on SNCF01 alone); other stations have the same night gap around the same hour on 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"}
{"start": "2026-10-13T07:45Z", "end": "2026-10-13T14:00Z", "family": "Visibility", "description": "By day (13/10), sun and clouds (image of 12:00): the corrected curves of the low targets fluctuate beyond their noise, mostly CV.4 in corr_x, F4.2, F4.6, CV.2, and around midday P1, P2 and F4.2 jump together in corr_x for one measurement; they come back at once. Calm again in the afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast, which makes the spots tremble (a fast noise, by day only, with the recognition error of these low targets rising), nothing in front of the targets on the images. Do not trust the small movements of these curves over the range; this is not a movement of the structure."}
{"start": "2026-10-13T07:45Z", "end": "2026-10-13T14:00Z", "family": "Visibility", "description": "By day (13/10), sun and clouds (image of 12:00): the corrected curves of the low targets fluctuate beyond their noise, mostly CV.4 in corr_x, F4.2, F4.6, CV.2, and around midday P1, P2 and F4.2 jump together in corr_x for one measurement; they come back at once. Calm again in the afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast, which makes the spots tremble (a fast noise, by day only, with the recognition error of these low targets rising), nothing in front of the targets on the images. Do not trust the small movements of these curves over the range; this is not a movement of the structure.", "review": "2026-11-18"}
{"start": "2026-10-14T01:15Z", "end": "2026-10-14T01:45Z", "family": "No data", "description": "One measurement is missing, for all sensors, around two in the morning: all curves have a gap. The power metrics of the station are empty over the whole month. This one-measurement night gap, around 02:00 UTC, falls at the same measurement on FLORIDA and SNCF01 on 09, 14 and 15/10, and only on them; other stations have the same night gap around the same hour on 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"}
@@ -1,6 +1,6 @@
{"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"}
{"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."}
{"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."}
{"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.", "review": "2026-11-18"}
{"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.", "review": "2026-11-18"}
{"start": "2026-10-15T01:45Z", "end": "2026-10-15T02:45Z", "family": "No data", "description": "Two measurements are missing half an hour apart, with a single measurement between them, for all sensors, around two in the morning: all curves have a gap; the image of two o'clock exists nonetheless. The power metrics of the station are empty over the whole month. This one-measurement night gap, around 02:00 UTC, falls at the same measurement on FLORIDA and SNCF01 on 09, 14 and 15/10, and only on them; other stations have the same night gap around the same hour on 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"}
{"start": "2026-10-15T05:15Z", "end": "2026-10-15T05:45Z", "family": "Displacement", "description": "One-measurement jump that lasts: on the 15th in the early morning, from one measurement to the next, the raw positions of all sensors, references included, jump together in the image (the tilt of the camera makes a step, which the pose then keeps), and the recognition error of P4, P7 and of the references R1, R2 goes up a notch. The compensation does not absorb it entirely: corr_y of P4, P5, P7, CV.1 and of the reference R1 drops at once, that of R2 rises, and these levels mostly remain on the following days. No image at that moment; cause not established (a jolt of the camera or of its mount, deduced from the pose). Relative to the overall movement, the targets move together with the camera, without moving relative to one another; the references R1 and R2 do not quite follow it, hence the remainder on the corrected curves. This is not an established movement of the structure: to be watched, on the camera and mount side.", "review": "2026-11-17"}
{"start": "2026-10-15T08:15Z", "end": "2026-10-15T15:45Z", "family": "Visibility", "description": "By day (15/10): the corrected curves of all targets fluctuate much more than at night, from one measurement to the next, especially CV.2, CV.4, F4.2, BG.3, CV.6, CV.9, with one-measurement jumps that come back at once, and CV.2, CV.4 (sometimes F4.2) are rejected at times, their curves having gaps; their recognition error varies strongly by day. At night everything becomes calm again. Deduced cause: heat shimmer from the air heated above the tracks (a fast noise over the whole scene, by day only), not visible on the images; the 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.", "review": "2026-11-17"}
@@ -11,19 +11,19 @@
{"start": "2026-10-16T11:30Z", "end": "2026-10-16T12:00Z", "family": "Obstruction", "description": "CV.4 makes a very large jump in corr_x and corr_y for the time of one measurement, its raw position jumping by several pixels, while CV.2 is rejected; everything comes back at the next measurement. Cause: probably a passage hiding these low targets, the system locking onto another spot; deduced (no image at that moment). The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-17"}
{"start": "2026-10-16T13:30Z", "end": "2026-10-16T14:00Z", "family": "No data", "description": "One measurement is missing for all sensors, all curves have a gap; no image at that moment. The power metrics of the station are empty over the whole month. The same gap occurs at the same time on the other stations that measure at that time (FLORIDA, JUNGFRAU, NORDEND): a common cause outside the station (transmission or reception of the data), not a station failure; it is not established. The curves are missing over the range; nothing to do on the station.", "review": "2026-11-17"}
{"start": "2026-10-16T14:15Z", "end": "2026-10-16T14:45Z", "family": "No data", "description": "One measurement is missing for all sensors, all curves have a gap; no image at that moment. The power metrics of the station are empty over the whole month. The same gap occurs at the same time on the other stations that measure at that time (CLARIDEN, FLORIDA, LENZSPITZE, NORDEND): a common cause outside the station (transmission or reception of the data), not a station failure; it is not established. The curves are missing over the range; nothing to do on the station.", "review": "2026-11-17"}
{"start": "2026-10-16T15:45Z", "end": "2026-10-16T16:15Z", "family": "Obstruction", "description": "One single measurement: the CV, F4 and P targets are rejected and their curves are missing; the references BG.3.1 and R1 are rejected too, the compensation retains none of them, and the targets that stayed under their threshold, BG.2, BG.3 and F4.5, jump strongly in corr_x and corr_y for the time of the measurement, as does the reference R2. Everything comes back at the next measurement. Cause: a train passing in front of the targets and the references, seen blurred across the whole lower scene on the 16:00 image. The structure is not moving: point to ignore, nothing to do."}
{"start": "2026-10-16T15:45Z", "end": "2026-10-16T16:15Z", "family": "Obstruction", "description": "One single measurement: the CV, F4 and P targets are rejected and their curves are missing; the references BG.3.1 and R1 are rejected too, the compensation retains none of them, and the targets that stayed under their threshold, BG.2, BG.3 and F4.5, jump strongly in corr_x and corr_y for the time of the measurement, as does the reference R2. Everything comes back at the next measurement. Cause: a train passing in front of the targets and the references, seen blurred across the whole lower scene on the 16:00 image. The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-18"}
{"start": "2026-10-17T07:30Z", "end": "2026-10-18T07:45Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (17/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 all night, until the start of the next morning; the rejections of F4.2 that night, labelled separately, do not affect the references and do not distort the pose. 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"}
{"start": "2026-10-17T08:00Z", "end": "2026-10-17T16:45Z", "family": "Visibility", "description": "By day (17/10): the corrected curves of all targets fluctuate much more than at night, from one measurement to the next, especially CV.2, CV.4, F4.2, BG.3, CV.6, CV.9, with one-measurement jumps that come back at once, and CV.2, CV.4 (sometimes F4.2) are rejected at times, their curves having gaps; their recognition error varies strongly by day. At night everything becomes calm again. Deduced cause: heat shimmer from the air heated above the tracks (a fast noise over the whole scene, by day only), not visible on the images; the 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.", "review": "2026-11-17"}
{"start": "2026-10-17T09:45Z", "end": "2026-10-17T10:15Z", "family": "Obstruction", "description": "CV.2 makes a very large jump in corr_x and corr_y for the time of one measurement, its raw position jumping by several pixels: another spot was taken for the target; CV.4 is rejected; everything comes back at the next measurement. Cause: a blurry, bright object passes in front of the bottom of the scene and hides CV.2 and CV.1, seen on the 10:00 image (thumbnails). The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-17"}
{"start": "2026-10-18T07:45Z", "end": "2026-10-18T15:45Z", "family": "Visibility", "description": "By day (18/10): the corrected curves of all targets fluctuate much more than at night, from one measurement to the next, especially CV.2, CV.4, F4.2, BG.3, CV.6, CV.9, with one-measurement jumps that come back at once, and CV.2, CV.4 (sometimes F4.2) are rejected at times, their curves having gaps; their recognition error varies strongly by day. At night everything becomes calm again. Deduced cause: heat shimmer from the air heated above the tracks (a fast noise over the whole scene, by day only), not visible on the images; the 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."}
{"start": "2026-10-18T07:45Z", "end": "2026-10-18T15:45Z", "family": "Visibility", "description": "By day (18/10): the corrected curves of all targets fluctuate much more than at night, from one measurement to the next, especially CV.2, CV.4, F4.2, BG.3, CV.6, CV.9, with one-measurement jumps that come back at once, and CV.2, CV.4 (sometimes F4.2) are rejected at times, their curves having gaps; their recognition error varies strongly by day. At night everything becomes calm again. Deduced cause: heat shimmer from the air heated above the tracks (a fast noise over the whole scene, by day only), not visible on the images; the 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.", "review": "2026-11-18"}
{"start": "2026-10-18T07:45Z", "end": "2026-10-19T00:00Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (18/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 evening. 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"}
{"start": "2026-10-18T20:00Z", "end": "2026-10-18T20:30Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 and some of the P) are rejected and their curves are missing; the references are affected too (BG.3.1 and R1 rejected), the compensation retains none of them, and the targets that stayed under the threshold (BG.2, BG.3, F4.5 and some P) jump in corr_x and corr_y for the time of the measurement. Everything comes back at the next measurement. Cause: a passage in front of the targets and the references, no image at that moment; deduced from the signature, the same as that of the trains seen on the images of the other passages. The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-17"}
{"start": "2026-10-19T07:15Z", "end": "2026-10-20T12:45Z", "family": "Displacement", "description": "On 19/10, an overcast day (images of 08:00 and 13:00, no sun on the wall), the camera moves in the morning and does not come back: its pan and tilt drop and its scale rises, then stay at their new level in the afternoon and at night, until the outage of 20/10. At the same time the targets move apart from each other in the image (residual relative to the overall movement): corr_x of P5, P6 and P7 rises and that of P2 drops clearly, and corr_y of P5 rises, through the afternoon and the night, while the residual of the compensation rises from late morning and the recognition error of the reference R1 from the late afternoon. No return before the outage; after it, on 21/10, P2 and P5 are still near their new levels. Not the daily thermal cycle: no sun, the pose does not come back, no temperature is available. Cause not established (a camera or reference movement that the compensation does not follow, or a movement of the scene). Movement of the structure not established: to monitor; part of the month-long drift labelled separately."}
{"start": "2026-10-19T07:15Z", "end": "2026-10-20T12:45Z", "family": "Displacement", "description": "On 19/10, an overcast day (images of 08:00 and 13:00, no sun on the wall), the camera moves in the morning and does not come back: its pan and tilt drop and its scale rises, then stay at their new level in the afternoon and at night, until the outage of 20/10. At the same time the targets move apart from each other in the image (residual relative to the overall movement): corr_x of P5, P6 and P7 rises and that of P2 drops clearly, and corr_y of P5 rises, through the afternoon and the night, while the residual of the compensation rises from late morning and the recognition error of the reference R1 from the late afternoon. No return before the outage; after it, on 21/10, P2 and P5 are still near their new levels. Not the daily thermal cycle: no sun, the pose does not come back, no temperature is available. Cause not established (a camera or reference movement that the compensation does not follow, or a movement of the scene). Movement of the structure not established: to monitor; part of the month-long drift labelled separately.", "review": "2026-11-18"}
{"start": "2026-10-19T09:00Z", "end": "2026-10-19T10:15Z", "family": "No data", "description": "Several consecutive measurements are missing for all sensors, for an hour, all curves are missing; no image either. The power metrics of the station are empty over the whole month. The same gap occurs at the same time on the other stations that measure at that time (CLARIDEN, FLORIDA, JUNGFRAU, LENZSPITZE, NIEDERHORN, NORDEND): a common cause outside the station (transmission or reception of the data), not a station failure; it is not established. The curves are missing over the range; nothing to do on the station.", "review": "2026-11-17"}
{"start": "2026-10-19T20:45Z", "end": "2026-10-19T21:15Z", "family": "No data", "description": "One measurement is missing for all sensors, all curves have a gap; no image at that moment. The power metrics of the station are empty over the whole month. The same gap occurs at the same time on the other stations that measure at that time (CLARIDEN, FLORIDA, JUNGFRAU, LENZSPITZE, NIEDERHORN, NORDEND): a common cause outside the station (transmission or reception of the data), not a station failure; it is not established. The curves are missing over the range; nothing to do on the station. The hourly metrics of BREITHORN, MICHIGAN and NEBRASKA are also missing at 21:00.", "review": "2026-11-17"}
{"start": "2026-10-20T04:45Z", "end": "2026-10-20T08:00Z", "family": "Visibility", "description": "At night on 20/10, before dawn, the reference R1 is less well seen: its recognition error rises a notch at once and stays high until mid-morning, and its measured position slides alone in the image (the targets do not move relative to the overall movement). The compensation follows it: corr_y of P7, P6 and P5 rises together clearly for a few hours, while the reference R2 moves the other way, then everything comes back as the position of R1 returns, around eight. The train passage of that morning, labelled separately, falls inside. Nothing in front of R1 on the night images of 05:00, 06:00 and 07:00 (its spot whole, same place); the night is one of poor visibility for several faint targets (CV.6 rejected all night, F4.2 at times). Cause deduced: the reference less well seen in the night of poor visibility, not an obstacle. Do not trust the small shift of these curves over the range; this is not a movement of the structure."}
{"start": "2026-10-20T05:30Z", "end": "2026-10-20T06:00Z", "family": "Obstruction", "description": "One single measurement: the CV, F4 and P targets are rejected and their curves are missing; the references BG.3.1 and R1 are rejected too, the compensation retains none of them, and the targets that stayed under their threshold, BG.2, BG.3, F4.5 and F4.6, jump strongly in corr_x and corr_y for the time of the measurement, as does the reference R2. Everything comes back at the next measurement. Cause: a passage in front of the targets and the references, deduced from the signature, the same as that of the train seen on the 16:00 image of 16/10 (no image at that minute). It falls inside the episode of the reference R1 of that morning, labelled separately. The structure is not moving: point to ignore, nothing to do."}
{"start": "2026-10-20T04:45Z", "end": "2026-10-20T08:00Z", "family": "Visibility", "description": "At night on 20/10, before dawn, the reference R1 is less well seen: its recognition error rises a notch at once and stays high until mid-morning, and its measured position slides alone in the image (the targets do not move relative to the overall movement). The compensation follows it: corr_y of P7, P6 and P5 rises together clearly for a few hours, while the reference R2 moves the other way, then everything comes back as the position of R1 returns, around eight. The train passage of that morning, labelled separately, falls inside. Nothing in front of R1 on the night images of 05:00, 06:00 and 07:00 (its spot whole, same place); the night is one of poor visibility for several faint targets (CV.6 rejected all night, F4.2 at times). Cause deduced: the reference less well seen in the night of poor visibility, not an obstacle. Do not trust the small shift of these curves over the range; this is not a movement of the structure.", "review": "2026-11-18"}
{"start": "2026-10-20T05:30Z", "end": "2026-10-20T06:00Z", "family": "Obstruction", "description": "One single measurement: the CV, F4 and P targets are rejected and their curves are missing; the references BG.3.1 and R1 are rejected too, the compensation retains none of them, and the targets that stayed under their threshold, BG.2, BG.3, F4.5 and F4.6, jump strongly in corr_x and corr_y for the time of the measurement, as does the reference R2. Everything comes back at the next measurement. Cause: a passage in front of the targets and the references, deduced from the signature, the same as that of the train seen on the 16:00 image of 16/10 (no image at that minute). It falls inside the episode of the reference R1 of that morning, labelled separately. The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-18"}
{"start": "2026-10-20T12:45Z", "end": "2026-10-21T10:00Z", "family": "No data", "description": "Measurements are missing intermittently, then an outage of about twenty hours. No measurement for any sensor, all curves are missing; no image either. The power metrics of the station are empty over the whole month: the cause is not established (acquisition, power or transmission). If long outages repeat, check the power and the transmission of the station.", "review": "2026-11-17"}
{"start": "2026-10-21T10:00Z", "end": "2026-10-21T15:45Z", "family": "Visibility", "description": "By day (21/10): the corrected curves of all targets fluctuate much more than at night, from one measurement to the next, especially CV.2, CV.4, F4.2, BG.3, CV.6, CV.9, with one-measurement jumps that come back at once, and CV.2, CV.4 (sometimes F4.2) are rejected at times, their curves having gaps; their recognition error varies strongly by day. At night everything becomes calm again. Deduced cause: heat shimmer from the air heated above the tracks (a fast noise over the whole scene, by day only), not visible on the images; the 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.", "review": "2026-11-17"}
{"start": "2026-10-21T10:00Z", "end": "2026-10-21T19:30Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (21/10, sunny, between two measurement outages): in late morning the pan of the camera drops and its scale rises, then the camera comes back in the afternoon and its tilt rises in the evening. The compensation absorbs most of it, but not all: in the late afternoon and the evening, with the tilt rising, corr_x of P5 and P7 dips clearly below its level of the morning, then they come back at the isolated measurement after the gap. 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."}
{"start": "2026-10-21T10:00Z", "end": "2026-10-21T19:30Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (21/10, sunny, between two measurement outages): in late morning the pan of the camera drops and its scale rises, then the camera comes back in the afternoon and its tilt rises in the evening. The compensation absorbs most of it, but not all: in the late afternoon and the evening, with the tilt rising, corr_x of P5 and P7 dips clearly below its level of the morning, then they come back at the isolated measurement after the gap. 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-18"}
{"start": "2026-10-21T19:30Z", "end": "2026-10-22T10:30Z", "family": "No data", "description": "Night outage, one single isolated measurement at the start. No measurement for any sensor, all curves are missing; no image either. The power metrics of the station are empty over the whole month: the cause is not established (acquisition, power or transmission). If long outages repeat, check the power and the transmission of the station.", "review": "2026-11-17"}
@@ -1,26 +1,26 @@
{"start": "2026-10-22T10:30Z", "end": "2026-10-22T13:30Z", "family": "No data", "description": "Between two outages, on 22/10 in late morning, measurements are missing intermittently: only a few isolated measurements arrive. No measurement for any sensor between them, all curves are missing; no image either. The power metrics of the station are empty over the whole month: the cause is not established (acquisition, power or transmission). If long outages repeat, check the power and the transmission of the station.", "review": "2026-11-17"}
{"start": "2026-10-22T10:30Z", "end": "2026-10-22T15:30Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (22/10), over a few measurements between outages, under an overcast sky (13:30 and 14:00 images): the pan of the camera is low and its scale high until early afternoon, at their extreme at 13:30, then they begin to come back at the isolated 15:30 measurement, the tilt staying low. The corrected curves keep it: the corr_x of P5 and P7 and the corr_y of P6 stay clearly above their level of the previous evening all day, flat, and P7 starts to come back at 15:30, when the corrections of the references also shift a little. Deduced cause: the camera and its mount move with the heat of the day (camera pose), the compensation absorbing only part of it; the structure, a masonry wall, is not supposed to move like that. No temperature is available to confirm it. Normal, nothing to do."}
{"start": "2026-10-22T10:30Z", "end": "2026-10-22T15:30Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (22/10), over a few measurements between outages, under an overcast sky (13:30 and 14:00 images): the pan of the camera is low and its scale high until early afternoon, at their extreme at 13:30, then they begin to come back at the isolated 15:30 measurement, the tilt staying low. The corrected curves keep it: the corr_x of P5 and P7 and the corr_y of P6 stay clearly above their level of the previous evening all day, flat, and P7 starts to come back at 15:30, when the corrections of the references also shift a little. Deduced cause: the camera and its mount move with the heat of the day (camera pose), the compensation absorbing only part of it; 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-18"}
{"start": "2026-10-22T15:00Z", "end": "2026-10-25T08:30Z", "family": "No data", "description": "One measurement is missing on 22/10 in the afternoon, then, after a single isolated measurement, an outage of nearly three days, until the morning of 25/10. No measurement for any sensor, all curves are missing; no image either. The power metrics of the station are empty over the whole month: the cause is not established (acquisition, power or transmission). If long outages repeat, check the power and the transmission of the station.", "review": "2026-11-17"}
{"start": "2026-10-25T08:30Z", "end": "2026-10-25T13:15Z", "family": "Visibility", "description": "By day (25/10, from the resumption of the measurements), in the sun (sunny morning with passing clouds on the images of 09:00 to 13:00, sharp shadows on the wall): the corrected curves of the targets fluctuate from one measurement to the next much more than at night, with one-measurement jumps that come back at once, above all CV.4, F4.2, F4.6, CV.9 and P1, and the noisy F4.3;; CV.2 and CV.4 are rejected at times, their curves having gaps. The recognition error of most sensors, the references included, varies strongly from one measurement to the next, which it does not do at night nor on the overcast days (22/10, 26/10), when the curves stay calm. The jumps stop after 13:00, when the sky clouds over (14:00 image). Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast making the spots tremble (a fast noise over the whole scene, sunny hours only), not a nuisance seen on the images. Do not trust the small movements of these curves by day; this is not a movement of the structure."}
{"start": "2026-10-25T08:30Z", "end": "2026-10-25T13:15Z", "family": "Visibility", "description": "By day (25/10, from the resumption of the measurements), in the sun (sunny morning with passing clouds on the images of 09:00 to 13:00, sharp shadows on the wall): the corrected curves of the targets fluctuate from one measurement to the next much more than at night, with one-measurement jumps that come back at once, above all CV.4, F4.2, F4.6, CV.9 and P1, and the noisy F4.3;; CV.2 and CV.4 are rejected at times, their curves having gaps. The recognition error of most sensors, the references included, varies strongly from one measurement to the next, which it does not do at night nor on the overcast days (22/10, 26/10), when the curves stay calm. The jumps stop after 13:00, when the sky clouds over (14:00 image). Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast making the spots tremble (a fast noise over the whole scene, sunny hours only), not a nuisance seen on the images. Do not trust the small movements of these curves by day; this is not a movement of the structure.", "review": "2026-11-18"}
{"start": "2026-10-25T08:30Z", "end": "2026-10-25T22:15Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (25/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 and the evening; measurements resumed in the morning after the outage. 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"}
{"start": "2026-10-25T23:30Z", "end": "2026-10-26T00:00Z", "family": "Obstruction", "description": "At night (25/10 23:45), for the time of one measurement, the CV targets (CV.1, CV.2, CV.4, CV.5, CV.8, CV.9) and F4.2 are rejected together, their curves are missing; the recognition error of the references BG.3.1 and R1 and of P5 and P7 rises without crossing the threshold, and P7, left under its threshold, jumps clearly in corr_x for that measurement: its point is wrong. The other targets do not move; everything comes back at the next measurement. Cause: probably a passage in front of this part of the scene, deduced from the signature (no image at that moment, the images being on the hour). The structure is not moving: point to ignore, nothing to do."}
{"start": "2026-10-26T08:15Z", "end": "2026-10-26T22:00Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (26/10), under an overcast sky (12:00 image): from the morning, the pan and the tilt of the camera drop and its scale rises, less than on the sunny days, with no return before the 22:00 outage: the pan keeps dropping in the evening. The corrected curves keep part of it: the corr_x of P7 and P5 move clearly away from their night level during the day, P7 most at 10:00 when the tilt drops at once; in the evening they move further, during the episode labelled separately (Visibility). 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."}
{"start": "2026-10-25T23:30Z", "end": "2026-10-26T00:00Z", "family": "Obstruction", "description": "At night (25/10 23:45), for the time of one measurement, the CV targets (CV.1, CV.2, CV.4, CV.5, CV.8, CV.9) and F4.2 are rejected together, their curves are missing; the recognition error of the references BG.3.1 and R1 and of P5 and P7 rises without crossing the threshold, and P7, left under its threshold, jumps clearly in corr_x for that measurement: its point is wrong. The other targets do not move; everything comes back at the next measurement. Cause: probably a passage in front of this part of the scene, deduced from the signature (no image at that moment, the images being on the hour). The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-18"}
{"start": "2026-10-26T08:15Z", "end": "2026-10-26T22:00Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (26/10), under an overcast sky (12:00 image): from the morning, the pan and the tilt of the camera drop and its scale rises, less than on the sunny days, with no return before the 22:00 outage: the pan keeps dropping in the evening. The corrected curves keep part of it: the corr_x of P7 and P5 move clearly away from their night level during the day, P7 most at 10:00 when the tilt drops at once; in the evening they move further, during the episode labelled separately (Visibility). 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-18"}
{"start": "2026-10-26T14:30Z", "end": "2026-10-26T15:15Z", "family": "No data", "description": "Two measurements are missing for all sensors, all curves are missing; no image either. The power metrics of the station are empty over the whole month. The same gap occurs at the same time on the other stations that measure at that time (CLARIDEN, FLORIDA, JUNGFRAU, LENZSPITZE, NIEDERHORN, NORDEND), and their metrics are also missing at the same minutes: a common cause outside the station (transmission or reception of the data), not a station failure; it is not established. The curves are missing over the range; nothing to do on the station. The hourly metrics of BREITHORN, MICHIGAN and NEBRASKA are also missing at 15:00.", "review": "2026-11-17"}
{"start": "2026-10-26T15:15Z", "end": "2026-10-26T22:00Z", "family": "Visibility", "description": "In late afternoon and in the evening (26/10), from the resumption after the common gap of 15:00 until the 22:00 outage: the corr_x of P5 and P6 and the corr_y of P6 rise steadily and clearly, while the corr_y of P4, P3, P1 and the corr_x of P1 go down, instead of coming back as on the other evenings; the camera pose does not come back either (the pan drops, the scale rises again) and the registration residual is at its highest of the range. From 17:00 the recognition error of the reference R2, of BG.3.1 and of P1, P3, CV.1, F4.2 rises markedly; F4.2 then CV.8 are rejected for a while, and at 18:15 most CV and F4 targets rise together. The night images of 16:00 to 21:00 show nothing clear, the scene as on the night before. After the outage, on 28/10, the curves are back at their level. Cause not established: references less well seen (a visibility drop over the scene is likely) that skew the compensation. Do not trust the curves over the range."}
{"start": "2026-10-26T15:15Z", "end": "2026-10-26T22:00Z", "family": "Visibility", "description": "In late afternoon and in the evening (26/10), from the resumption after the common gap of 15:00 until the 22:00 outage: the corr_x of P5 and P6 and the corr_y of P6 rise steadily and clearly, while the corr_y of P4, P3, P1 and the corr_x of P1 go down, instead of coming back as on the other evenings; the camera pose does not come back either (the pan drops, the scale rises again) and the registration residual is at its highest of the range. From 17:00 the recognition error of the reference R2, of BG.3.1 and of P1, P3, CV.1, F4.2 rises markedly; F4.2 then CV.8 are rejected for a while, and at 18:15 most CV and F4 targets rise together. The night images of 16:00 to 21:00 show nothing clear, the scene as on the night before. After the outage, on 28/10, the curves are back at their level. Cause not established: references less well seen (a visibility drop over the scene is likely) that skew the compensation. Do not trust the curves over the range.", "review": "2026-11-18"}
{"start": "2026-10-26T22:00Z", "end": "2026-10-28T07:15Z", "family": "No data", "description": "Outage of more than a day, with a single isolated measurement on 27/10 at 14:00. No measurement for any sensor, all curves are missing; no image either. The power metrics of the station are empty over the whole month: the cause is not established (acquisition, power or transmission). If long outages repeat, check the power and the transmission of the station.", "review": "2026-11-17"}
{"start": "2026-10-28T07:30Z", "end": "2026-10-28T22:45Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (28/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 and the evening; measurements resumed in the morning after the outage. 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"}
{"start": "2026-10-28T08:00Z", "end": "2026-10-28T14:45Z", "family": "Visibility", "description": "By day (28/10), in the sun (full sun on the 12:00 image, sharp shadows on the wall): the corrected curves of the targets fluctuate from one measurement to the next much more than at night, with one-measurement jumps that come back at once, above all CV.4 and CV.2, then P2, P3 and CV.1;; CV.2 and CV.4 are rejected at times, their curves having gaps. The recognition error of most sensors, the references included, varies strongly from one measurement to the next, which it does not do at night nor on the overcast days (22/10, 26/10), when the curves stay calm. The jumps start in mid-morning, once the sun is on the scene, and stop in mid-afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast making the spots tremble (a fast noise over the whole scene, sunny hours only), not a nuisance seen on the images. Do not trust the small movements of these curves by day; this is not a movement of the structure."}
{"start": "2026-10-28T08:00Z", "end": "2026-10-28T14:45Z", "family": "Visibility", "description": "By day (28/10), in the sun (full sun on the 12:00 image, sharp shadows on the wall): the corrected curves of the targets fluctuate from one measurement to the next much more than at night, with one-measurement jumps that come back at once, above all CV.4 and CV.2, then P2, P3 and CV.1;; CV.2 and CV.4 are rejected at times, their curves having gaps. The recognition error of most sensors, the references included, varies strongly from one measurement to the next, which it does not do at night nor on the overcast days (22/10, 26/10), when the curves stay calm. The jumps start in mid-morning, once the sun is on the scene, and stop in mid-afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast making the spots tremble (a fast noise over the whole scene, sunny hours only), not a nuisance seen on the images. Do not trust the small movements of these curves by day; this is not a movement of the structure.", "review": "2026-11-18"}
{"start": "2026-10-28T10:15Z", "end": "2026-10-28T10:45Z", "family": "Obstruction", "description": "CV.2 makes a very large jump in corr_x and corr_y for the time of one measurement, its raw position jumping by several pixels: another spot was taken for the target; CV.4 is rejected; everything comes back at the next measurement. Cause: probably a passage, like on 17/10 at 10:00; deduced (no image at that moment). The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-17"}
{"start": "2026-10-28T21:00Z", "end": "2026-10-28T21:30Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 and some of the P) are rejected and their curves are missing; the references are affected too (BG.3.1 and R1 rejected), the compensation retains none of them, and the targets that stayed under the threshold (BG.2, BG.3, F4.5 and some P) jump in corr_x and corr_y for the time of the measurement. Everything comes back at the next measurement. Cause: a passage in front of the targets and the references, no image at that moment; deduced from the signature, the same as that of the trains seen on the images of the other passages. The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-17"}
{"start": "2026-10-28T22:30Z", "end": "2026-10-28T23:00Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 and some of the P) are rejected and their curves are missing; the references are affected too (BG.3.1 and R1 rejected), the compensation retains none of them, and the targets that stayed under the threshold (BG.2, BG.3, F4.5 and some P) jump in corr_x and corr_y for the time of the measurement. Everything comes back at the next measurement. Cause: a passage in front of the targets and the references, no image at that moment; deduced from the signature, the same as that of the trains seen on the images of the other passages. The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-17"}
{"start": "2026-10-29T07:45Z", "end": "2026-10-29T23:15Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (29/10), sunny day (12:00 image): from the morning, the pan and the tilt of the camera drop and its scale rises, then they slowly come back in the afternoon and the evening, the pan reaching its night level late in the evening. The corrected curves follow the same cycle, poorly compensated: the corr_y of P5 and P6 and the corr_x of P7, P6 and P5 move clearly away from their night level during the day, then come back gradually in the evening. 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."}
{"start": "2026-10-29T10:45Z", "end": "2026-10-29T15:30Z", "family": "Visibility", "description": "By day (29/10), in the sun (full sun on the 12:00 image, sharp shadows on the wall): the corrected curves of the targets fluctuate from one measurement to the next much more than at night, with one-measurement jumps that come back at once, above all CV.4, F4.2, CV.6, BG.3 and BG.2;; CV.2 and CV.4 are rejected at times, their curves having gaps. The recognition error of most sensors, the references included, varies strongly from one measurement to the next, which it does not do at night nor on the overcast days (22/10, 26/10), when the curves stay calm. The jumps start late in the morning and stop in mid-afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast making the spots tremble (a fast noise over the whole scene, sunny hours only), not a nuisance seen on the images. Do not trust the small movements of these curves by day; this is not a movement of the structure."}
{"start": "2026-10-29T07:45Z", "end": "2026-10-29T23:15Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (29/10), sunny day (12:00 image): from the morning, the pan and the tilt of the camera drop and its scale rises, then they slowly come back in the afternoon and the evening, the pan reaching its night level late in the evening. The corrected curves follow the same cycle, poorly compensated: the corr_y of P5 and P6 and the corr_x of P7, P6 and P5 move clearly away from their night level during the day, then come back gradually in the evening. 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-18"}
{"start": "2026-10-29T10:45Z", "end": "2026-10-29T15:30Z", "family": "Visibility", "description": "By day (29/10), in the sun (full sun on the 12:00 image, sharp shadows on the wall): the corrected curves of the targets fluctuate from one measurement to the next much more than at night, with one-measurement jumps that come back at once, above all CV.4, F4.2, CV.6, BG.3 and BG.2;; CV.2 and CV.4 are rejected at times, their curves having gaps. The recognition error of most sensors, the references included, varies strongly from one measurement to the next, which it does not do at night nor on the overcast days (22/10, 26/10), when the curves stay calm. The jumps start late in the morning and stop in mid-afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast making the spots tremble (a fast noise over the whole scene, sunny hours only), not a nuisance seen on the images. Do not trust the small movements of these curves by day; this is not a movement of the structure.", "review": "2026-11-18"}
{"start": "2026-10-29T14:45Z", "end": "2026-10-29T15:15Z", "family": "No data", "description": "One measurement is missing for all sensors, all curves have a gap, although the 15:00 image exists. The power metrics of the station are empty over the whole month. The same gap occurs at the same time on the other stations that measure at that time (CLARIDEN, LENZSPITZE, NORDEND): a common cause outside the station (transmission or reception of the data), not a station failure; it is not established. The curves are missing over the range; nothing to do on the station.", "review": "2026-11-17"}
{"start": "2026-10-30T08:00Z", "end": "2026-10-31T07:45Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (30/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 all night, until the start of the next morning. 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"}
{"start": "2026-10-30T09:15Z", "end": "2026-10-30T15:30Z", "family": "Visibility", "description": "By day (30/10), in the sun (full sun on the 12:00 image, sharp shadows on the wall): the corrected curves of the targets fluctuate from one measurement to the next much more than at night, with one-measurement jumps that come back at once, above all CV.2, then F4.2, CV.6, F4.6, F4.5 and CV.4;; CV.2 and CV.4 are rejected at times, their curves having gaps. The recognition error of most sensors, the references included, varies strongly from one measurement to the next, which it does not do at night nor on the overcast days (22/10, 26/10), when the curves stay calm. The jumps start in mid-morning and stop in mid-afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast making the spots tremble (a fast noise over the whole scene, sunny hours only), not a nuisance seen on the images. Do not trust the small movements of these curves by day; this is not a movement of the structure."}
{"start": "2026-10-30T09:15Z", "end": "2026-10-30T15:30Z", "family": "Visibility", "description": "By day (30/10), in the sun (full sun on the 12:00 image, sharp shadows on the wall): the corrected curves of the targets fluctuate from one measurement to the next much more than at night, with one-measurement jumps that come back at once, above all CV.2, then F4.2, CV.6, F4.6, F4.5 and CV.4;; CV.2 and CV.4 are rejected at times, their curves having gaps. The recognition error of most sensors, the references included, varies strongly from one measurement to the next, which it does not do at night nor on the overcast days (22/10, 26/10), when the curves stay calm. The jumps start in mid-morning and stop in mid-afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast making the spots tremble (a fast noise over the whole scene, sunny hours only), not a nuisance seen on the images. Do not trust the small movements of these curves by day; this is not a movement of the structure.", "review": "2026-11-18"}
{"start": "2026-10-30T17:45Z", "end": "2026-10-30T18:15Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 and some of the P) are rejected and their curves are missing; the references are affected too (BG.3.1 and R1 rejected), the compensation retains none of them, and the targets that stayed under the threshold (BG.2, BG.3, F4.5 and some P) jump in corr_x and corr_y for the time of the measurement. Everything comes back at the next measurement. Cause: a passage in front of the targets and the references, a lit train passing: on the 18:00 night image, most of the spots have disappeared and large bright spots appear. The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-17"}
{"start": "2026-10-30T18:15Z", "end": "2026-10-30T18:45Z", "family": "Obstruction", "description": "One single measurement: most targets (the CV, the F4 and some of the P) are rejected and their curves are missing; the references are affected too (BG.3.1 and R1 rejected), the compensation retains none of them, and the targets that stayed under the threshold (BG.2, BG.3, F4.5 and some P) jump in corr_x and corr_y for the time of the measurement. Everything comes back at the next measurement. Cause: a passage in front of the targets and the references, no image at that moment; deduced from the signature, the same as that of the trains seen on the images of the other passages. The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-17"}
{"start": "2026-10-30T21:15Z", "end": "2026-10-30T22:00Z", "family": "Obstruction", "description": "Two measurements, at night (30/10): at 21:30, CV.2 is rejected, its curve is missing; the recognition error of the reference BG.3.1 rises markedly without crossing its threshold, the camera pose jumps (pan), and P3 clearly, P1 and BG.3 a little, jump in corr_x for the time of the measurement. At 21:45, F4.2 is rejected alone, its curve is missing; everything then comes back. Cause: probably a passage in front of the bottom of the scene and the reference BG.3.1, deduced from the signature, weaker than that of the trains (no image at that moment, the images being on the hour). The structure is not moving: point to ignore, nothing to do."}
{"start": "2026-10-31T07:45Z", "end": "2026-11-01T00:00Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (31/10), sunny day (12:00 and 13:00 images): from the morning, the pan and the tilt of the camera drop and its scale rises; at 12:30 the tilt also makes a step, labelled separately (Displacement). In the afternoon and the evening the pan and the scale come back slowly, the tilt only partly. The corrected curves follow the cycle, poorly compensated: the corr_y of P6, P5 and P4 and the corr_x of P7 and P5 move clearly away from their night level during the day; in the evening P7 comes back, but the corr_y of P6 and P5 stays clearly above its level of the previous nights until the end of the range. Deduced cause: the camera and its mount move with the heat of the day (camera pose), plus the step of the camera; the structure, a masonry wall, is not supposed to move like that. No temperature is available to confirm it. Normal, nothing to do; see the step of 12:30."}
{"start": "2026-10-31T08:15Z", "end": "2026-10-31T16:00Z", "family": "Visibility", "description": "By day (31/10), in the sun (full sun on the 12:00 and 13:00 images, sharp shadows on the wall): the corrected curves of the targets fluctuate from one measurement to the next much more than at night, with one-measurement jumps that come back at once, above all CV.4, P2, CV.2 and P1, then BG.3 and F4.2;; CV.2 and CV.4 are rejected at times, their curves having gaps. The recognition error of most sensors, the references included, varies strongly from one measurement to the next, which it does not do at night nor on the overcast days (22/10, 26/10), when the curves stay calm. The jumps start in the morning and stop in late afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast making the spots tremble (a fast noise over the whole scene, sunny hours only), not a nuisance seen on the images. Do not trust the small movements of these curves by day; this is not a movement of the structure."}
{"start": "2026-10-31T12:15Z", "end": "2026-10-31T12:45Z", "family": "Displacement", "description": "Step of the camera at 12:30 on 31/10, in full sun (12:00 and 13:00 images): the tilt of the camera jumps at once, far more steeply than in its daily cycle, and all the sensors, references and targets, shift together in the image; the targets move relative to each other only a little. The compensation does not erase it all: the corr_y of P6, P7, P5 and P3 steps up clearly at that measurement and stays there all afternoon. The tilt does not come back to its earlier night level, and the corr_y of P6 and P5 stays clearly above its level of the previous nights until the end of the range; at 17:00 the corrections of the references BG.3.1, R1 and R2 also shift relative to each other and stay. Cause not established (the camera or its mount moving in the sun is likely). It is not a movement of the structure; the camera is to be monitored, and the level of the following nights checked."}
{"start": "2026-10-30T21:15Z", "end": "2026-10-30T22:00Z", "family": "Obstruction", "description": "Two measurements, at night (30/10): at 21:30, CV.2 is rejected, its curve is missing; the recognition error of the reference BG.3.1 rises markedly without crossing its threshold, the camera pose jumps (pan), and P3 clearly, P1 and BG.3 a little, jump in corr_x for the time of the measurement. At 21:45, F4.2 is rejected alone, its curve is missing; everything then comes back. Cause: probably a passage in front of the bottom of the scene and the reference BG.3.1, deduced from the signature, weaker than that of the trains (no image at that moment, the images being on the hour). The structure is not moving: point to ignore, nothing to do.", "review": "2026-11-18"}
{"start": "2026-10-31T07:45Z", "end": "2026-11-01T00:00Z", "family": "Thermal displacement", "description": "Daytime thermal cycle (31/10), sunny day (12:00 and 13:00 images): from the morning, the pan and the tilt of the camera drop and its scale rises; at 12:30 the tilt also makes a step, labelled separately (Displacement). In the afternoon and the evening the pan and the scale come back slowly, the tilt only partly. The corrected curves follow the cycle, poorly compensated: the corr_y of P6, P5 and P4 and the corr_x of P7 and P5 move clearly away from their night level during the day; in the evening P7 comes back, but the corr_y of P6 and P5 stays clearly above its level of the previous nights until the end of the range. Deduced cause: the camera and its mount move with the heat of the day (camera pose), plus the step of the camera; the structure, a masonry wall, is not supposed to move like that. No temperature is available to confirm it. Normal, nothing to do; see the step of 12:30.", "review": "2026-11-18"}
{"start": "2026-10-31T08:15Z", "end": "2026-10-31T16:00Z", "family": "Visibility", "description": "By day (31/10), in the sun (full sun on the 12:00 and 13:00 images, sharp shadows on the wall): the corrected curves of the targets fluctuate from one measurement to the next much more than at night, with one-measurement jumps that come back at once, above all CV.4, P2, CV.2 and P1, then BG.3 and F4.2;; CV.2 and CV.4 are rejected at times, their curves having gaps. The recognition error of most sensors, the references included, varies strongly from one measurement to the next, which it does not do at night nor on the overcast days (22/10, 26/10), when the curves stay calm. The jumps start in the morning and stop in late afternoon. Deduced cause: heat shimmer, the air heated by the sun above the tracks and the ballast making the spots tremble (a fast noise over the whole scene, sunny hours only), not a nuisance seen on the images. Do not trust the small movements of these curves by day; this is not a movement of the structure.", "review": "2026-11-18"}
{"start": "2026-10-31T12:15Z", "end": "2026-10-31T12:45Z", "family": "Displacement", "description": "Step of the camera at 12:30 on 31/10, in full sun (12:00 and 13:00 images): the tilt of the camera jumps at once, far more steeply than in its daily cycle, and all the sensors, references and targets, shift together in the image; the targets move relative to each other only a little. The compensation does not erase it all: the corr_y of P6, P7, P5 and P3 steps up clearly at that measurement and stays there all afternoon. The tilt does not come back to its earlier night level, and the corr_y of P6 and P5 stays clearly above its level of the previous nights until the end of the range; at 17:00 the corrections of the references BG.3.1, R1 and R2 also shift relative to each other and stay. Cause not established (the camera or its mount moving in the sun is likely). It is not a movement of the structure; the camera is to be monitored, and the level of the following nights checked.", "review": "2026-11-18"}
+23
View File
@@ -0,0 +1,23 @@
{
"id": "animal-close-to-lens",
"kind": "phenomenon",
"name": "An animal very close to the lens",
"family": "Obstruction",
"signature": "Lit at night, it hides part or all of the scene for one or two measurements.",
"checks": [
"the image of the instant"
],
"neighbours": [
{
"case": "pass-by-hides-targets-one-measurement",
"tell_apart": "something passing in the scene, or an animal lit very close to the lens hiding part or all of it"
},
{
"case": "spider-web-in-front-of-lens",
"tell_apart": "the animal hides for one or two measurements; its web veils for hours or days"
}
],
"sources": [
"user"
]
}
+19
View File
@@ -0,0 +1,19 @@
{
"id": "atmospheric-turbulence",
"kind": "phenomenon",
"name": "Atmospheric turbulence",
"family": "Visibility",
"signature": "By day, air heated above a road, ballast or rails makes the spots tremble: a fast noise, with `error_value` rising.",
"checks": [
"`error_value` rises with the agitation"
],
"neighbours": [
{
"case": "camera-moves-thermal-effect",
"tell_apart": "a fast noise with the `error_value` rising is turbulence; an agitation of the pose without it is the camera heating"
}
],
"sources": [
"user"
]
}
@@ -0,0 +1,23 @@
{
"id": "base-changes-without-reference-lost",
"kind": "phenomenon",
"name": "The base changes without a reference lost",
"family": "Perturbation",
"signature": "All references are kept, the distance between them changes a little; all targets shift together without moving in the image, then the distances and the targets come back; a base that stays changed is a Displacement.",
"checks": [
"overview.py --rigid: the references against the targets"
],
"neighbours": [
{
"case": "reference-dropped-base-changes",
"tell_apart": "all references kept with their distances changing a little, or one reference dropped"
},
{
"case": "reference-shifted-alone-then-back",
"tell_apart": "the distances between all references for hours, or one reference alone for a measurement or two"
}
],
"sources": [
"user"
]
}
@@ -0,0 +1,23 @@
{
"id": "camera-drifts-housing-cools-no-daily-cycle",
"kind": "phenomenon",
"name": "The camera drifts away when the temperature of its housing drops, without a daily cycle",
"family": "Thermal displacement",
"signature": "Sheltered (a building, a tunnel), the camera drifts in jerks with the housing temperature and comes back when it warms.",
"checks": [
"metrics.py: the pose against the housing temperature"
],
"neighbours": [
{
"case": "camera-moves-thermal-effect",
"tell_apart": "a cycle every day with the housing temperature, or a sheltered camera drifting in jerks when its housing cools, without a daily cycle"
},
{
"case": "ff-tunnel-temperature-drop-not-thermal",
"tell_apart": "a bump of a group with the `error_value`, returning before the scale of the camera, is not the thermal drift"
}
],
"sources": [
"user"
]
}
@@ -0,0 +1,22 @@
{
"id": "camera-jolt-back-at-next-measurement",
"kind": "phenomenon",
"name": "A jolt of the camera, back at the next measurement",
"family": "Perturbation",
"signature": "The pose jumps for one measurement and the raw positions of all sensors, references included, jump together, then come back at the next measurement; the compensation leaves a remainder on the curves for that point only.",
"checks": [
"overview.py: the pose at the jolt"
],
"neighbours": [
{
"case": "camera-step-not-erased",
"tell_apart": "the camera comes back at the next measurement, or keeps its new position"
}
],
"sources": [
"LENZSPITZE-84",
"NORDEND-243",
"NORDEND-278",
"NORDEND-80"
]
}
@@ -0,0 +1,28 @@
{
"id": "camera-moves-thermal-effect",
"kind": "phenomenon",
"name": "The camera moves through a thermal effect",
"family": "Thermal displacement",
"signature": "The camera 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.",
"checks": [
"metrics.py: the pose against the housing temperature",
"days.py --bounds: the cycle of each day"
],
"neighbours": [
{
"case": "atmospheric-turbulence",
"tell_apart": "a fast noise with the `error_value` rising is turbulence; an agitation of the pose without it is the camera heating"
},
{
"case": "camera-drifts-housing-cools-no-daily-cycle",
"tell_apart": "a cycle every day with the housing temperature, or a sheltered camera drifting in jerks when its housing cools, without a daily cycle"
},
{
"case": "structure-expands-and-contracts",
"tell_apart": "the camera pose follows the housing temperature, or the structure moves with its own slow rhythm, the references stable"
}
],
"sources": [
"user"
]
}
+24
View File
@@ -0,0 +1,24 @@
{
"id": "camera-step-not-erased",
"kind": "phenomenon",
"name": "A step of the camera that the compensation does not erase",
"family": "Displacement",
"signature": "The camera moves at once and keeps its new position, and a remainder stays in the curves; a step that leaves nothing beyond the noise is not labelled.",
"checks": [
"overview.py: the pose at the step",
"overview.py --rigid: what remains on each target"
],
"neighbours": [
{
"case": "camera-tilts-little-by-little",
"tell_apart": "the camera moves at once, or little by little over weeks"
},
{
"case": "camera-jolt-back-at-next-measurement",
"tell_apart": "the camera keeps its new position, or comes back at the next measurement"
}
],
"sources": [
"user"
]
}
@@ -0,0 +1,19 @@
{
"id": "camera-tilts-little-by-little",
"kind": "phenomenon",
"name": "The camera tilts little by little",
"family": "Displacement",
"signature": "Over weeks, the tilt rises and the compensation corrects some targets better than others; the targets do not move relative to each other.",
"checks": [
"overview.py --rigid: the targets keep their relative positions"
],
"neighbours": [
{
"case": "camera-step-not-erased",
"tell_apart": "the camera moves at once, or little by little over weeks"
}
],
"sources": [
"user"
]
}
@@ -0,0 +1,21 @@
{
"id": "compensation-on-two-references",
"kind": "phenomenon",
"name": "A compensation on two references",
"family": null,
"signature": "A station built with two references, or having lost one for good: the slightest difference between them passes into all the targets; the family is that of what disturbs them.",
"checks": [],
"neighbours": [
{
"case": "two-references-lost-camera-blind",
"tell_apart": "a lasting compensation on two references passes their slightest difference into the targets; losing two of three leaves the camera blind"
},
{
"case": "lesson-references-masked-by-vegetation",
"tell_apart": "two references for good, or references masked by vegetation leaving a base too weak"
}
],
"sources": [
"user"
]
}
@@ -0,0 +1,27 @@
{
"id": "faint-spot-lost-without-light",
"kind": "phenomenon",
"name": "A faint spot lost when the light is missing",
"family": "Visibility",
"signature": "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.",
"checks": [
"the images at dawn"
],
"neighbours": [
{
"case": "sun-in-field-or-behind-spot",
"tell_apart": "rejections at the same hours on sunny days only, or at the change from night to day, overcast days included"
},
{
"case": "target-rejected-every-night-or-day",
"tell_apart": "rejections that come with the light and not every day, or every day under the ordinary regime"
},
{
"case": "lesson-low-contrast-target",
"tell_apart": "a faint target crossing its threshold with the light, or square waves by day without reaching it"
}
],
"sources": [
"user"
]
}
@@ -0,0 +1,18 @@
{
"id": "ff-common-jumps-at-reference-switches",
"kind": "false friend",
"name": "Jumps of many targets, all in the same direction, are not a movement when they fall at the reference switches",
"family": null,
"signature": "The raw positions take no step and the daily cycle continues.",
"checks": [],
"neighbours": [
{
"case": "real-movement-of-structure",
"tell_apart": "jumps at the reference switches, with no step of the raw positions and the daily cycle going on, are not a movement"
}
],
"sources": [
"user",
"expert"
]
}
@@ -0,0 +1,13 @@
{
"id": "ff-corrections-stuck-at-zero",
"kind": "false friend",
"name": "Corrections stuck at zero are not a failure",
"family": null,
"signature": "A target twinned with a reference: the same prism serves as target and reference.",
"checks": [],
"neighbours": [],
"sources": [
"user",
"expert"
]
}
@@ -0,0 +1,18 @@
{
"id": "ff-error-return-not-end-of-obstruction",
"kind": "false friend",
"name": "The return of the `error_value` is not the end of an obstruction",
"family": "Obstruction",
"signature": "After a mark on the glass, the curves stay shifted.",
"checks": [],
"neighbours": [
{
"case": "obstacle-covers-part-of-spot",
"tell_apart": "the curves can stay shifted after the `error_value` came back"
}
],
"sources": [
"user",
"NORDEND-169"
]
}
+18
View File
@@ -0,0 +1,18 @@
{
"id": "ff-insects-not-a-train",
"kind": "false friend",
"name": "A swarm of insects is not a train",
"family": "Obstruction",
"signature": "Same signature; only the image tells them apart.",
"checks": [],
"neighbours": [
{
"case": "pass-by-hides-targets-one-measurement",
"tell_apart": "insects give the same signature as a passage: only the image tells them apart"
}
],
"sources": [
"user",
"NIEDERHORN-66"
]
}
@@ -0,0 +1,18 @@
{
"id": "ff-no-signal-no-obstruction",
"kind": "false friend",
"name": "No signal does not mean no obstruction",
"family": null,
"signature": "Only the images show the web.",
"checks": [],
"neighbours": [
{
"case": "spider-web-in-front-of-lens",
"tell_apart": "a web may leave no signal: only the images show it"
}
],
"sources": [
"user",
"expert"
]
}
@@ -0,0 +1,18 @@
{
"id": "ff-references-calm-in-rain",
"kind": "false friend",
"name": "References that do not move in the rain do not contradict the rain",
"family": "Visibility",
"signature": "Higher up, they suffer it less.",
"checks": [],
"neighbours": [
{
"case": "rain",
"tell_apart": "calm references do not deny the rain: higher up, they suffer it less"
}
],
"sources": [
"user",
"NIEDERHORN-141"
]
}
@@ -0,0 +1,18 @@
{
"id": "ff-rise-over-days-not-movement",
"kind": "false friend",
"name": "A rise over several days is not necessarily a real movement",
"family": null,
"signature": "It may follow a lasting drop in temperature.",
"checks": [],
"neighbours": [
{
"case": "rise-over-days-as-temperature-drops",
"tell_apart": "a rise over several days may follow a lasting drop in temperature"
}
],
"sources": [
"user",
"expert"
]
}
+18
View File
@@ -0,0 +1,18 @@
{
"id": "ff-step-is-not-amplitude",
"kind": "false friend",
"name": "The step of a real movement is not its amplitude when the camera and the references have moved too",
"family": "Displacement",
"signature": "The step seen on the curves mixes the movement with what the compensation could not separate.",
"checks": [],
"neighbours": [
{
"case": "real-movement-of-structure",
"tell_apart": "when the camera and the references moved too, the step seen is not the amplitude"
}
],
"sources": [
"user",
"expert"
]
}
@@ -0,0 +1,18 @@
{
"id": "ff-target-sliding-with-error-rising",
"kind": "false friend",
"name": "A target that slides slowly away from its neighbours is not moving when its `error_value` rises with the sliding",
"family": null,
"signature": "A step then brings it back toward them.",
"checks": [],
"neighbours": [
{
"case": "obstacle-covers-part-of-spot",
"tell_apart": "a slow sliding with the `error_value` rising, brought back by a step, is the obstacle, not a movement"
}
],
"sources": [
"user",
"expert"
]
}
@@ -0,0 +1,18 @@
{
"id": "ff-thumbnail-spot-follows-measurement",
"kind": "false friend",
"name": "A spot on a thumbnail that follows the measurement is not necessarily there",
"family": null,
"signature": "The frame follows a measurement perhaps latched onto the neighbour; only a fixed frame shows it.",
"checks": [],
"neighbours": [
{
"case": "target-latches-onto-another-light",
"tell_apart": "a thumbnail framed on the measurement may show the neighbour it latched onto; only a fixed frame shows where the spot is"
}
],
"sources": [
"user",
"expert"
]
}
@@ -0,0 +1,18 @@
{
"id": "ff-tunnel-temperature-drop-not-thermal",
"kind": "false friend",
"name": "In a tunnel, a temperature drop at the same moment does not make a thermal effect",
"family": null,
"signature": "The bump of a group comes with the `error_value` and returns before the scale of the camera.",
"checks": [],
"neighbours": [
{
"case": "camera-drifts-housing-cools-no-daily-cycle",
"tell_apart": "a bump of a group with the `error_value`, returning before the scale of the camera, is not the thermal drift"
}
],
"sources": [
"user",
"CLARIDEN-12"
]
}
+18
View File
@@ -0,0 +1,18 @@
{
"id": "ff-web-is-not-the-spider",
"kind": "false friend",
"name": "A web is not the spider",
"family": null,
"signature": "The web veils in part for hours or days; the spider hides everything for the length of one measurement.",
"checks": [],
"neighbours": [
{
"case": "spider-web-in-front-of-lens",
"tell_apart": "the web veils in part for hours or days; the spider hides everything for one measurement"
}
],
"sources": [
"user",
"expert"
]
}
@@ -0,0 +1,19 @@
{
"id": "gap-common-to-several-stations",
"kind": "phenomenon",
"name": "A gap common to several stations",
"family": "No data",
"signature": "The measurements are missing at the same minutes on every station measuring then: a cause outside the stations, not established.",
"checks": [
"stations.py on the stations measuring then: the gaps common to several stations, before the station's own metrics"
],
"neighbours": [
{
"case": "station-runs-measurement-missing",
"tell_apart": "the same minutes missing on every station measuring then, or one station missing a measurement while powered and communicating"
}
],
"sources": [
"user"
]
}
@@ -0,0 +1,19 @@
{
"id": "lesson-everything-moves-together",
"kind": "lesson",
"name": "When everything moves together, the measurements alone do not separate the structure from the camera",
"family": "Displacement",
"signature": "The references, the camera and the structure moved together (a bridge whose vault subsided, confirmed by other monitoring systems of the site); an unstable compensation then distorts the amplitude of a real movement.",
"checks": [],
"neighbours": [
{
"case": "real-movement-of-structure",
"tell_apart": "references and pose stable, or everything moving together, the amplitude then not established"
}
],
"client": "The movement is reported, its amplitude is not established.",
"sources": [
"user",
"expert"
]
}
@@ -0,0 +1,18 @@
{
"id": "lesson-low-contrast-target",
"kind": "lesson",
"name": "A target of low contrast",
"family": null,
"signature": "By day, square waves on one axis, back at night, with `error_value` rising by day without reaching the threshold.",
"checks": [],
"neighbours": [
{
"case": "faint-spot-lost-without-light",
"tell_apart": "a faint target crossing its threshold with the light, or square waves by day without reaching it"
}
],
"sources": [
"user",
"client report"
]
}
@@ -0,0 +1,18 @@
{
"id": "lesson-references-masked-by-vegetation",
"kind": "lesson",
"name": "References masked by vegetation",
"family": null,
"signature": "With two of four references masked, a daily cycle on pan, roll and tilt, badly compensated, is not a movement of the camera but a base too weak for the transformation.",
"checks": [],
"neighbours": [
{
"case": "compensation-on-two-references",
"tell_apart": "two references for good, or references masked by vegetation leaving a base too weak"
}
],
"sources": [
"user",
"client report"
]
}
+18
View File
@@ -0,0 +1,18 @@
{
"id": "lesson-snow",
"kind": "lesson",
"name": "Snow",
"family": null,
"signature": "Noise and apparent movements on all sensors and on the camera, a brief loss of data, the signal quickly back.",
"checks": [],
"neighbours": [
{
"case": "visibility-drops-whole-scene",
"tell_apart": "a veil with rejections and no step of the raw positions, or noise and apparent movements on all sensors and on the camera"
}
],
"sources": [
"user",
"client report"
]
}
@@ -0,0 +1,20 @@
{
"id": "lesson-two-prisms-too-close",
"kind": "lesson",
"name": "Two prisms too close interfere",
"family": null,
"signature": "A daily 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.",
"checks": [
"`dominance`, on a recent camera"
],
"neighbours": [
{
"case": "target-latches-onto-another-light",
"tell_apart": "one false point during a passage, or a bright neighbour interfering, with a daily cycle or isolated peaks"
}
],
"sources": [
"user",
"client report"
]
}
+18
View File
@@ -0,0 +1,18 @@
{
"id": "lesson-vegetation-grows",
"kind": "lesson",
"name": "Vegetation grows over days and weeks",
"family": "Obstruction",
"signature": "A partial, progressive occultation, not reversible from one measurement to the next like a passage; the hardest obstruction according to the expert.",
"checks": [],
"neighbours": [
{
"case": "plant-shaken-by-wind",
"tell_apart": "shaken at times by the wind, or a progressive occultation over days and weeks"
}
],
"sources": [
"user",
"client report"
]
}
@@ -0,0 +1,19 @@
{
"id": "mains-cut-station-on-battery",
"kind": "phenomenon",
"name": "Mains cut: the station runs on its battery",
"family": "No data",
"signature": "A station on mains stops, or comes back on a drawn-down battery, until the mains return.",
"checks": [
"metrics.py: battery and voltage around the gap"
],
"neighbours": [
{
"case": "station-shuts-down-lack-of-energy",
"tell_apart": "a solar battery that does not last the night, or a station on mains that stops or comes back on a drawn-down battery"
}
],
"sources": [
"user"
]
}
@@ -0,0 +1,29 @@
{
"id": "obstacle-covers-part-of-spot",
"kind": "phenomenon",
"name": "An obstacle covers part of the spot",
"family": "Obstruction",
"signature": "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.",
"checks": [],
"neighbours": [
{
"case": "plant-shaken-by-wind",
"tell_apart": "one target hidden at times on windy days, or a spot partly covered for hours or weeks with its centre sliding"
},
{
"case": "soiled-glass",
"tell_apart": "a mark in front of a single spot is an obstacle; drop marks veiling part of the scene are the soiled glass"
},
{
"case": "ff-error-return-not-end-of-obstruction",
"tell_apart": "the curves can stay shifted after the `error_value` came back"
},
{
"case": "ff-target-sliding-with-error-rising",
"tell_apart": "a slow sliding with the `error_value` rising, brought back by a step, is the obstacle, not a movement"
}
],
"sources": [
"user"
]
}
@@ -0,0 +1,19 @@
{
"id": "part-of-scene-dark-at-night",
"kind": "phenomenon",
"name": "Part of the scene goes dark at night",
"family": "Visibility",
"signature": "The distant spots, or a few neighbours at the edge of the group, lose their light, with nothing in front.",
"checks": [
"the night image"
],
"neighbours": [
{
"case": "visibility-drops-whole-scene",
"tell_apart": "the flux down on all sensors, or only distant spots or a few at the edge of the group losing their light at night"
}
],
"sources": [
"user"
]
}
@@ -0,0 +1,31 @@
{
"id": "pass-by-hides-targets-one-measurement",
"kind": "phenomenon",
"name": "A pass-by hides the targets for the length of one measurement",
"family": "Obstruction",
"signature": "A train, a vehicle or passers-by: the hidden targets are rejected for one acquisition and back at the next; a reference behind it makes the whole base jump. Insects give the same signature: only the image tells.",
"checks": [
"the image of the instant"
],
"neighbours": [
{
"case": "vehicle-or-machine-stays",
"tell_apart": "back at the next measurement, or the same sensors hidden for hours or days"
},
{
"case": "target-latches-onto-another-light",
"tell_apart": "the hidden targets rejected, or one false point kept in the curve without rejection"
},
{
"case": "animal-close-to-lens",
"tell_apart": "something passing in the scene, or an animal lit very close to the lens hiding part or all of it"
},
{
"case": "ff-insects-not-a-train",
"tell_apart": "insects give the same signature as a passage: only the image tells them apart"
}
],
"sources": [
"user"
]
}
+21
View File
@@ -0,0 +1,21 @@
{
"id": "plant-shaken-by-wind",
"kind": "phenomenon",
"name": "A plant shaken by the wind in front of a target",
"family": "Obstruction",
"signature": "One target, at times, on windy days; the plant grows over weeks.",
"checks": [],
"neighbours": [
{
"case": "obstacle-covers-part-of-spot",
"tell_apart": "one target hidden at times on windy days, or a spot partly covered for hours or weeks with its centre sliding"
},
{
"case": "lesson-vegetation-grows",
"tell_apart": "shaken at times by the wind, or a progressive occultation over days and weeks"
}
],
"sources": [
"user"
]
}
+23
View File
@@ -0,0 +1,23 @@
{
"id": "rain",
"kind": "phenomenon",
"name": "Rain",
"family": "Visibility",
"signature": "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.",
"checks": [
"the images of the night"
],
"neighbours": [
{
"case": "soiled-glass",
"tell_apart": "drops during the hours of rain, or marks that stay after it"
},
{
"case": "ff-references-calm-in-rain",
"tell_apart": "calm references do not deny the rain: higher up, they suffer it less"
}
],
"sources": [
"user"
]
}
@@ -0,0 +1,35 @@
{
"id": "real-movement-of-structure",
"kind": "phenomenon",
"name": "A real movement of the structure",
"family": "Displacement",
"signature": "Targets shift and stay, with the references and the pose stable and a good image; if the camera and the references moved too, the amplitude is not established.",
"checks": [
"overview.py --rigid: the targets move in the image, the references do not"
],
"neighbours": [
{
"case": "rise-over-days-as-temperature-drops",
"tell_apart": "a rise that comes back at equal temperature, or targets that shift and stay"
},
{
"case": "targets-move-slowly-alone-and-return",
"tell_apart": "targets that shift and stay, or targets that come back"
},
{
"case": "ff-common-jumps-at-reference-switches",
"tell_apart": "jumps at the reference switches, with no step of the raw positions and the daily cycle going on, are not a movement"
},
{
"case": "ff-step-is-not-amplitude",
"tell_apart": "when the camera and the references moved too, the step seen is not the amplitude"
},
{
"case": "lesson-everything-moves-together",
"tell_apart": "references and pose stable, or everything moving together, the amplitude then not established"
}
],
"sources": [
"user"
]
}
@@ -0,0 +1,27 @@
{
"id": "reference-dropped-base-changes",
"kind": "phenomenon",
"name": "A reference dropped: the base changes",
"family": null,
"signature": "One reference above its threshold is dropped: all the targets jump together, the reprojection error at zero; the family is that of what hindered the reference.",
"checks": [
"inventory.py --start --end: the retained references at that instant"
],
"neighbours": [
{
"case": "reference-loses-brightness",
"tell_apart": "a reference that weakens but stays retained, its centre still, or a reference dropped with all the targets jumping together"
},
{
"case": "base-changes-without-reference-lost",
"tell_apart": "all references kept with their distances changing a little, or one reference dropped"
},
{
"case": "two-references-lost-camera-blind",
"tell_apart": "one reference dropped makes a common jump; two dropped one after the other leave every point invalid"
}
],
"sources": [
"user"
]
}
@@ -0,0 +1,20 @@
{
"id": "reference-loses-brightness",
"kind": "phenomenon",
"name": "A reference loses its brightness, without an obstacle",
"family": "Visibility",
"signature": "One or two references weaken and shrink, most often at night, then come back on their own; their centre does not move.",
"checks": [
"the `error_value` of the references",
"the night image"
],
"neighbours": [
{
"case": "reference-dropped-base-changes",
"tell_apart": "a reference that weakens but stays retained, its centre still, or a reference dropped with all the targets jumping together"
}
],
"sources": [
"user"
]
}
@@ -0,0 +1,24 @@
{
"id": "reference-shifted-alone-then-back",
"kind": "phenomenon",
"name": "A reference measured shifted alone, then back",
"family": "Perturbation",
"signature": "One reference is measured shifted alone in the image, without being rejected; the base changes and the targets jump according to their place in the image, then everything comes back; the targets do not move in the raw image.",
"checks": [
"overview.py --rigid: the reference against the targets"
],
"neighbours": [
{
"case": "base-changes-without-reference-lost",
"tell_apart": "one reference alone for a measurement or two, or the distances between all references for hours"
}
],
"sources": [
"ALASKA-1",
"JUNGFRAU-110",
"JUNGFRAU-112",
"LENZSPITZE-105",
"LENZSPITZE-106",
"WYOMING-9"
]
}
@@ -0,0 +1,23 @@
{
"id": "rise-over-days-as-temperature-drops",
"kind": "phenomenon",
"name": "A rise over several days with the drop in temperature",
"family": "Thermal displacement",
"signature": "The temperature keeps falling for days and the structure keeps rising; it comes back at equal temperature (otherwise Displacement).",
"checks": [
"metrics.py: the level at equal temperature"
],
"neighbours": [
{
"case": "real-movement-of-structure",
"tell_apart": "a rise that comes back at equal temperature, or targets that shift and stay"
},
{
"case": "ff-rise-over-days-not-movement",
"tell_apart": "a rise over several days may follow a lasting drop in temperature"
}
],
"sources": [
"user"
]
}
@@ -0,0 +1,19 @@
{
"id": "sensor-configuration-changed",
"kind": "phenomenon",
"name": "The configuration of a sensor has changed",
"family": "Target issue",
"signature": "A sensor moved or reset: its curve changes with nothing moving in the image; the jump is not a Displacement.",
"checks": [
"the raw positions `x`, `y`: nothing moves in the image"
],
"neighbours": [
{
"case": "target-jumps-and-stays-shifted",
"tell_apart": "the curve changes with nothing moving in the image, or the raw position of the target departs to another level"
}
],
"sources": [
"user"
]
}
+20
View File
@@ -0,0 +1,20 @@
{
"id": "single-point-back-at-once",
"kind": "phenomenon",
"name": "A single point of one or a few targets, back at once",
"family": "Perturbation",
"signature": "For one measurement, one target or a few neighbours jump on their corrected curves, then come back at the next; the references and the camera stay calm and nothing is seen in front of them.",
"checks": [],
"neighbours": [
{
"case": "target-jumps-and-stays-shifted",
"tell_apart": "back at the next measurement, or staying at the new level"
}
],
"sources": [
"ALASKA-2",
"LENZSPITZE-98",
"NIEDERHORN-144",
"NORDEND-271"
]
}
+23
View File
@@ -0,0 +1,23 @@
{
"id": "soiled-glass",
"kind": "phenomenon",
"name": "The soiled glass",
"family": "Visibility",
"signature": "After rain, drop marks veil part of the scene durably; under a single spot, it is an obstacle (Obstruction).",
"checks": [
"the images after the rain"
],
"neighbours": [
{
"case": "obstacle-covers-part-of-spot",
"tell_apart": "a mark in front of a single spot is an obstacle; drop marks veiling part of the scene are the soiled glass"
},
{
"case": "rain",
"tell_apart": "drops during the hours of rain, or marks that stay after it"
}
],
"sources": [
"user"
]
}
@@ -0,0 +1,27 @@
{
"id": "spider-web-in-front-of-lens",
"kind": "phenomenon",
"name": "A spider web in front of the lens",
"family": null,
"signature": "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.",
"checks": [
"the images of the period"
],
"neighbours": [
{
"case": "animal-close-to-lens",
"tell_apart": "the animal hides for one or two measurements; its web veils for hours or days"
},
{
"case": "ff-no-signal-no-obstruction",
"tell_apart": "a web may leave no signal: only the images show it"
},
{
"case": "ff-web-is-not-the-spider",
"tell_apart": "the web veils in part for hours or days; the spider hides everything for one measurement"
}
],
"sources": [
"user"
]
}
+19
View File
@@ -0,0 +1,19 @@
{
"id": "station-goes-silent-long",
"kind": "phenomenon",
"name": "The station goes silent on its own, for a long time",
"family": "No data",
"signature": "No measurements, no images, no metrics, for hours or days, without the signature of a lack of energy.",
"checks": [
"metrics.py: voltage and battery before the gap and at the restart"
],
"neighbours": [
{
"case": "station-shuts-down-lack-of-energy",
"tell_apart": "a voltage below the knee before the gap and a restart with the solar charge mark the lack of energy; without them, the station went silent on its own"
}
],
"sources": [
"user"
]
}
@@ -0,0 +1,19 @@
{
"id": "station-runs-measurement-missing",
"kind": "phenomenon",
"name": "The station runs, the measurement is missing",
"family": "No data",
"signature": "One station, powered and communicating, misses a measurement: a synchronization, an image or `DB_not_uploaded` falls at the missing instant.",
"checks": [
"the station metrics at the missing instant: synchronization, image, `DB_not_uploaded`"
],
"neighbours": [
{
"case": "gap-common-to-several-stations",
"tell_apart": "the same minutes missing on every station measuring then, or one station missing a measurement while powered and communicating"
}
],
"sources": [
"user"
]
}
@@ -0,0 +1,23 @@
{
"id": "station-shuts-down-lack-of-energy",
"kind": "phenomenon",
"name": "The station shuts down for lack of energy",
"family": "No data",
"signature": "The battery does not last the night: the voltage falls below the knee before the gap, and the station restarts with the solar charge.",
"checks": [
"metrics.py: voltage and battery before the gap and at the restart"
],
"neighbours": [
{
"case": "station-goes-silent-long",
"tell_apart": "a voltage below the knee before the gap and a restart with the solar charge mark the lack of energy; without them, the station went silent on its own"
},
{
"case": "mains-cut-station-on-battery",
"tell_apart": "a solar battery that does not last the night, or a station on mains that stops or comes back on a drawn-down battery"
}
],
"sources": [
"user"
]
}
@@ -0,0 +1,19 @@
{
"id": "step-during-measurement-outage",
"kind": "phenomenon",
"name": "A step taken during a measurement outage",
"family": "Displacement",
"signature": "On resumption, targets do not find their previous level.",
"checks": [
"ranges.py --outside the outage: the level before and after"
],
"neighbours": [
{
"case": "target-jumps-and-stays-shifted",
"tell_apart": "a jump seen between two measurements, or a new level found on resumption after an outage"
}
],
"sources": [
"user"
]
}
@@ -0,0 +1,19 @@
{
"id": "structure-expands-and-contracts",
"kind": "phenomenon",
"name": "The structure expands and contracts with the temperature",
"family": "Thermal displacement",
"signature": "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.",
"checks": [
"overview.py --rigid: the references stay stable"
],
"neighbours": [
{
"case": "camera-moves-thermal-effect",
"tell_apart": "the camera pose follows the housing temperature, or the structure moves with its own slow rhythm, the references stable"
}
],
"sources": [
"user"
]
}
@@ -0,0 +1,24 @@
{
"id": "sun-in-field-or-behind-spot",
"kind": "phenomenon",
"name": "The sun in the field or behind a spot",
"family": "Visibility",
"signature": "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.",
"checks": [
"days.py: the same hours day after day",
"the image of the hour"
],
"neighbours": [
{
"case": "faint-spot-lost-without-light",
"tell_apart": "rejections at the same hours on sunny days only, or at the change from night to day, overcast days included"
},
{
"case": "target-rejected-every-night-or-day",
"tell_apart": "only on sunny days, or every day at the same hours whatever the weather"
}
],
"sources": [
"user"
]
}
@@ -0,0 +1,23 @@
{
"id": "target-at-threshold-whole-batch",
"kind": "phenomenon",
"name": "A target right at the threshold, the whole batch",
"family": "Target issue",
"signature": "Its `error_value` keeps crossing the threshold, with many own rejections.",
"checks": [
"the `error_value` of the target against its threshold"
],
"neighbours": [
{
"case": "target-rejected-at-all-measurements",
"tell_apart": "never accepted, or an `error_value` that keeps crossing the threshold with many rejections"
},
{
"case": "target-degrades-sometimes-recovers",
"tell_apart": "at the threshold over the whole batch, or worse and worse from a date on"
}
],
"sources": [
"user"
]
}
@@ -0,0 +1,17 @@
{
"id": "target-degrades-sometimes-recovers",
"kind": "phenomenon",
"name": "A target that degrades, and sometimes recovers",
"family": "Target issue",
"signature": "Seen worse and worse from a date on; back only after weeks, if ever, often at another level.",
"checks": [],
"neighbours": [
{
"case": "target-at-threshold-whole-batch",
"tell_apart": "at the threshold over the whole batch, or worse and worse from a date on"
}
],
"sources": [
"user"
]
}
@@ -0,0 +1,27 @@
{
"id": "target-jumps-and-stays-shifted",
"kind": "phenomenon",
"name": "A target or a small group jumps and stays shifted",
"family": "Displacement",
"signature": "At once, to another level, without the camera moving or a visible cause.",
"checks": [
"overview.py --rigid: the raw position of the target departs alone"
],
"neighbours": [
{
"case": "sensor-configuration-changed",
"tell_apart": "the curve changes with nothing moving in the image, or the raw position of the target departs to another level"
},
{
"case": "step-during-measurement-outage",
"tell_apart": "a jump seen between two measurements, or a new level found on resumption after an outage"
},
{
"case": "single-point-back-at-once",
"tell_apart": "staying at the new level, or back at the next measurement"
}
],
"sources": [
"user"
]
}
@@ -0,0 +1,27 @@
{
"id": "target-latches-onto-another-light",
"kind": "phenomenon",
"name": "A target left under the threshold latches onto a headlight, a reflection or another spot",
"family": "Obstruction",
"signature": "During a pass-by, one false point is kept in the curve, without rejection.",
"checks": [
"`dominance` rises, on a recent camera"
],
"neighbours": [
{
"case": "pass-by-hides-targets-one-measurement",
"tell_apart": "the hidden targets rejected, or one false point kept in the curve without rejection"
},
{
"case": "lesson-two-prisms-too-close",
"tell_apart": "one false point during a passage, or a bright neighbour interfering, with a daily cycle or isolated peaks"
},
{
"case": "ff-thumbnail-spot-follows-measurement",
"tell_apart": "a thumbnail framed on the measurement may show the neighbour it latched onto; only a fixed frame shows where the spot is"
}
],
"sources": [
"user"
]
}
@@ -0,0 +1,19 @@
{
"id": "target-rejected-at-all-measurements",
"kind": "phenomenon",
"name": "A target rejected at all its measurements",
"family": "Target issue",
"signature": "Never accepted, whatever the weather.",
"checks": [
"inventory.py: the rejected measurements of the target"
],
"neighbours": [
{
"case": "target-at-threshold-whole-batch",
"tell_apart": "never accepted, or an `error_value` that keeps crossing the threshold with many rejections"
}
],
"sources": [
"user"
]
}
@@ -0,0 +1,23 @@
{
"id": "target-rejected-every-night-or-day",
"kind": "phenomenon",
"name": "A target rejected every night or every day",
"family": "Target issue",
"signature": "Under the station's ordinary regime (floodlight, daylight), at the same hours, whatever the weather.",
"checks": [
"inventory.py: its rejections, day by day"
],
"neighbours": [
{
"case": "sun-in-field-or-behind-spot",
"tell_apart": "only on sunny days, or every day at the same hours whatever the weather"
},
{
"case": "faint-spot-lost-without-light",
"tell_apart": "rejections that come with the light and not every day, or every day under the ordinary regime"
}
],
"sources": [
"user"
]
}
Loaded 100 of 112 files, more files were not shown because too many files have changed in this diff. Show more