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>
DAILY_STORAGE_STATE classifies the end-of-day free space of /data and
DAYS_UNTIL_STORAGE_FULL divides it by the median daily fill over 7
days. The day color reads a state x horizon matrix drawn in
docs/storage/matrice-etat-horizon.drawio. Thresholds are arbitrary for
now (D-034, D-035); expert questions stay open. On WEISSHORN the disk
fills at 28.2 MiB/day and would be full around 06/02/2027.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
DAILY_LINK_STATE falls back on last_sync for exports without link,
treats the start of history as unknown, and records D-032. Document
the hourly counting flaws, the observed 15-minute cadence, and the
open questions for the specialist.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Explore WEISSHORN for the cellular domain, count lost sends and
messages, grade the daily RSRP and RSRQ medians on the published
Quectel grid, and record D-031.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
New data will be added per station without mixing with the working set.
All scripts now default to data/VERMONT/; docs and D-029 follow.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
D-028: CLAUDE.md names every folder and document with its size in
lines, says how to read without filling the context (outline of a long
file then one section, index of the decision log, CSV by script,
folders not to read), and gives the current state instead of a dated
history. It and D-026 now name final.py for the delivered script.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Record decision D-027: a server-side LLM agent layer next to the
unchanged deterministic rules, aimed at unknown anomalies and rule
edge cases. The agent annotates and never rewrites the day color.
Home-made harness (Messages API + Tool Runner), staged start with a
manual Energy pilot on VERMONT history. D-003 is partly replaced.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Energy code moves to src/energy/ and its docs to docs/energy/; shared code
(CSV loading, venv switch, browser, zoom script) goes to src/common/, and the
AIMsight originals to docs/aimsight/. Analyses are no longer numbered: two
Energy scripts remain, daily.py (delivered state and trend) and
all_analyses.py (comparison of the four). Calculations and pages unchanged (D-026).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
D-025: the support side gets the site's home page (one tile per
station: name, last voltage, curve) with a Status section on top. It
holds one notification per station whose last day of the window is
Orange or Red (src/day_color.py), the most serious first; Green
notifies nothing. Each notification, like the station tile, links to
the station's client view (out/maquette_user_energy.html).
maquettes/support/home.py writes out/maquette_support_home.html with
the standard library only (inline SVG, no plotly). Only VERMONT has
data; the other tiles keep the site's names and stay empty.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
CLAUDE.md records D-022/D-023 in the project state and the next mockup
steps (client Energy step by step, then the support side). D-022 lists
the open points of the Energy mockup: the guide is still in French,
the battery scale has no IR compensation, the energy save button is
for the site team to build, and a day in progress is not yet flagged
as provisional on the client side.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
D-024: to explain a day's color, show only that day and the day before,
the only days analyses 03 and 04 read for it. day_color.focus() selects
the data (standard library); src/focus_jour.py prints a traceable fact
summary and writes a 48 h BusVoltage figure (out/<STATION>_focus_<date>
.html and .json). Analysis 03 gains the night_end_h fact; the other
facts are unchanged. The client Energy mockup does not use this figure:
the user prefers numeric facts there.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
D-022: page mockups are HTML built from real data, in maquettes/user/
(client) and maquettes/support/; Figma only on request.
maquettes/user/energy.py renders the System Summary page with a
Diagnostic section: an Energy box with the day's color, a one-line
headline, a battery scale (zones from the collector's LiFePO4 OCV
table, no percentage shown), the trend against the day before, an
"Activate energy save mode" button on orange and red days (mockup
only, sends nothing), and two collapsibles: the full history (D-021
figure) and the guide (part 1 of the manual, rendered from Markdown).
D-023: everything meant for the monitoring site is in English,
including the titles, legends, axes and hovers of the 03/04 panels.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
D-020: the delivered energy diagnostic keeps analyses 03 and 04 only,
combined by the state x trend matrix of cas-d-usage-03-04.drawio into
one color per day (green / orange / red, grey when unknown), coded in
src/day_color.py (standard library). docs/guide/diagnostic-energetique.md
explains it: part 1 for the client, part 2 for support.
D-021: energy_plot.daily_figure builds the figure for the monitoring
site (panel 03 above panel 04, shared time axis), written by
analyse_01.py as out/<STATION>_daily.html and .json. battery_state no
longer imports energy_check, so analyses 03 and 04 ship on their own.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
src/analyse_04.py launches the common page; sheet 04 moves to
"prototype en place" with VERMONT results; CLAUDE.md, the analyses
rule, README and sheet 01 list the fourth panel and extend the
"no verdict" contract exception to analysis 04.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>