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>
Read takes no file pattern: find the image with ls | grep first. A cd to
the repository root counts as one command.
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>
- Visibility: v0 kept after a measured trial of a simpler version (archived); two levels, Reduced and No visibility
- Thermal: a 24-hour sinusoid confirms the daily wave, split into thermal expansion and contraction events
- Jumps tested from the first measurement; turbulence never kept over a shift to check (CLARIDEN)
- Data gaps say whether camera images exist; Displacements trends become slow drift events
- Threshold registry moved to vues-deplacements/contexte/seuils-du-journal.md; plan points 11 to 17, 38 and 41 validated
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>