The station manual says the DIFF image is the contrast-enhanced view of the
reflectors that the displacement algorithm measures, not a difference between
two instants. The reading tools only look at IRON images, so run.md describes
--diff as an option instead of putting it in the pump command.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Camera pan, tilt, scale, rotation and sigma0, one row per camera measurement,
read like the platform viewer (cam_movements aggregate), one CSV per day in
camera/. Tried on NORDEND 30/07: 70 poses out of 95 instants, sigma0 on the
same 7 as the advanced export. run.md holds the command to copy into the
app's dev container.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Two days (29-30/07) pumped by the user in the app's dev container: system
metrics, displacements and camera images match the received exports, and
the journal gives the same events. The container mounts ~ on /workspaces,
so the script now writes straight into Support-Agent's data/ (no copies).
Add --delai for days that exceed the 60 s query timeout, and report the
root database error instead of pandas' wrapper.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Each batch now leaves etiquettes.json next to the critique: the analyst's
own reading, written before the detectors' output, one entry per moment,
checked by critiquer-lot/etiquettes.py against the event map and the
station's sensors. Groundwork for a future learned model.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
pomper.py now also pumps every system metric of a station, in the format of
the System page download (hourly mean, text lists, empty hour), one CSV per
metric and per day; displacements are written one file per day, today is
never pumped, and a rerun only fetches missing days. Fix image resume: an
image already on disk now counts for its time slot. load_stations merges
several files of the same metric instead of failing on a duplicate.
Not run against the database: first run by the user, with point 27.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Each /boucle subagent now ends its output with a Difficultés section;
at the end of a session the orchestrator calls the releveur once, which
locates the instruction or file at fault and records it in
docs/ameliorations-processus.md, without fixing anything.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The agent now serves one precise case, reads the project's displacement
knowledge and the whole case base, starts from the detectors' events
without judging them, and no longer has conclusions imposed on it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Plan points 18 to 26, 30, 39, 40 and the point 37 housekeeping:
- greyed zones per target, vertical scale without the zones to ignore, Fit all,
mm by default with a px switch, Support view, Expand (one row per category);
- cleaned curves: cut in the zones to ignore, raw data kept there in thin grey;
- target02 to target05 count as targets; smoothing questions answered;
- categories.py sorts in slices with 3 days of history by default;
- the pumping script points to ~/monitoring-dashboard and skips diff images;
- CLAUDE.md back under 200 lines; a case page is named after its case.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Event map regrouped into six families, 33 events including hypothetical ones, with the journal categories (section 4)
- categories.py turns detector episodes into categorised events: absorption of brief jumps, merging, catégorique phrases
- Journal tab: one "What happened" row coloured by family, cards, and an Images button playing the event's timelapse
- Plan: user-validated points marked, points 39 and 40 added; anomaly definition clarified in D-056
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The Displacements tab now puts the list on the left and the curves on
the right, kept on screen while the list scrolls. Hovering a row keeps
only its target in color and draws it on the curves, with fixed scales:
a jump gets its 2 hours highlighted, the 24 h levels before and after
and an arrow with the jump in mm; a trend gets its period, the
Theil-Sen line, the daily levels, its start and end and the drift as
an arrow. #focus=j0-0, t0 or e0 opens with a row hovered, for captures.
Documented in the detection note: on NORDEND, PR17 and PR06 clear the
thresholds by a wide margin, the next curves fall short (PR03 nearest).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The jumps and trends now sit in a Displacements tab after Diagnosis
(#tab=displacements), no longer in a separate sidebar page; a click on
a row opens the Diagnosis tab on that target.
Documented: what the client looks at (jumps and trends, not errors,
handled upstream) in docs/displacement/domaine/ce-que-regarde-le-client.md;
the expert's reading of NORDEND in the case journey; the experimental
way of working in vues-deplacements/CLAUDE.md; D-055, the spec, the
note, the README and the project map.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Mechanical anomaly detection on the hourly displacements in mm, data
unchanged: for each target and axis, the largest gap between the median
of the next 24 h and the previous 24 h, kept above 3 times the target's
daily swing (provisional). Jumps within 6 h form one event, so a common
jump is not several anomalies. Grey curves for all targets, colour for
those that jumped; a click opens Explore, Diagnosis.
Note on the idea, first trial and leads in
vues-deplacements/contexte/detection-d-anomalies.md.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- docs/displacement/domaine/incident-de-barcelone.md: the AIMsight
regression case is data/CLARIDEN/ (case C-004); what the data show,
the documentation's reading (reference/compensation instability)
against the expert's (real movement of the structure, confirmed by
other instruments, amplitude likely overestimated), open questions.
- nouveau-cas: platform zips date images in UTC, exports cover local
days; keep every image of the range, even at 10 min.
- colonnes-des-deplacements: native cadence is 15 or 10 min.
- CLAUDE.md: four cases in the base, displacement data of NORDEND,
WILDSTRUBEL and CLARIDEN.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copy the station's displacement export and images into the case folder,
with coded sensor names; the station takes the case number instead of
S01, and graphique.py / vignettes.py drop --alias (D-050).
Rewrite C-001 as the expert's diagnosis of this event only: summary,
symptom, verdict, signature with commands, diagnosis, evidence. Drop
exclusions, expected output, unknowns and test history; matching no
longer uses exclusions (D-051). The corr_x jumps at the reference
switches are judged negligible.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add the anonymiser-cas skill: a growing registry gives stable codes
(S01, R1, C1), a stdlib script rewrites a case and renames its files,
and graphique.py / vignettes.py take --alias to plot with codes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Two analysis reports delivered to the client (GN-1.472, GN-5.054, May 2026)
go to docs/aimsight/ unchanged. Their diagnoses are summarized in
docs/displacement/domaine/cas-annotes-par-l-expert.md as reference truth
for displacement, without data: not in the diagnostic agent's case base.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Reports become a folder with rapport.md and its figures: a verdict, one
short section per anomaly (series plot with shaded window, full-resolution
image crops around the sensors), constant behaviour in one line each.
graphique.py gains --zone and --sortie; new vignettes.py crops images at
the sensors' raw x/y. Old reports removed; the blind rescan of PS des
Coudres finds the single anomaly flagged by the specialist (REF_G/REF_D).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Inclusive --fin at the displayed minute, UTC for naive time_utc, neutral examples,
5-significant-digit values, 'vide' vs '-' cells, no empty or gap-bridging plots,
timestamped report names, and an up-to-date CLAUDE.md next step.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Images extracted by hand, one per full hour from 2026-10-13 12:00 to
2026-10-14 11:00 UTC, renamed <UTC time>_<original number>.jpg. UTC is
confirmed by the user and matches sunset and sunrise. They cover the
second night episode on REF_G and REF_D.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Exports go to data/<STATION>/displacement/, out of reach of the system
metrics loader. The 15-min "advanced" export (UTC) is the analysis source;
the hourly export is kept for the corr_x/corr_y conversion factors.
Document both formats and record the open questions in the framing doc.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The user's preferred name. The module becomes src/energy/power_source.py
and the sheet docs/energy/analyses/daily_power_source.md; the
calculation and the results are unchanged (D-043).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A station is on mains when its BusVoltage mean over the 3 days before
the day is >= 14.0 V (solar never exceeds 13.50 V on VERMONT; mains
stays >= 14.08 V). On mains, the mains loss decides the day color
instead of the state x trend matrix: red as soon as an hour falls under
13.4 V (top of the OCV plateau; mains-on hours stay >= 13.65 V, mains-off
hours are 13.1-13.3 V). On MISSISSIPPI the day turns red 1-2 h after the
loss instead of 29-40 h with the matrix; WEISSHORN and NORDEND (mains)
raise no false alert, VERMONT (solar) is unchanged (D-043).
The matrix drawio gets the mains case, the site figure a third panel,
and the support notification and the client Energy block header show
"On mains" / "Not on mains" / "Mains unknown".
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Temperature joins the mockups' list of domains (D-041): a Red
notification on the support Home, and a one-line block on the client
view ("Hottest (24 h) 43 °C · limit 97.5 °C") for the stations that
measure the GPU. src/temperature/final.py writes the site figure; the
comparison page reuses its panel. Short two-layer guide in
docs/temperature/guide/.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
DAILY_GPU_TEMPERATURE_LIMIT: red when an hourly GPU mean reached 97.5 °C
(T.gpu, Jetson Nano Thermal Design Guide) in the last 24 hours, green
otherwise, gray without measurement. Working sets WEISSHORN and NORDEND;
all measured days are green. D-040 replaces D-036; the exploration note
moves to docs/temperature/domaine/point-de-depart.md.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The mockups now walk a list of domains (D-039): the support Home loads
every station in data/ and notifies each station x domain that is Orange
or Red; the client view becomes maquettes/user/summary.py, one System
Summary page per station with one block per measured domain. Storage
shows a free-space scale and the estimated full date; Cellular shows the
day's sends in words and a four-class signal scale.
HEADLINE moves into each day_color.py, with a Green sentence for the
client view. src/storage/final.py and src/cellular/final.py write the
site figures in English; the comparison pages reuse their panels. Each
domain gets a short two-layer guide in docs/<domaine>/guide/.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Docker Engine in WSL (mirrored networking), Python 3.14 and plotly,
--network=host to reach the camera over Ethernet (D-038).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>