30 labels written by an agent from E-001 to E-011, decoded with the anonymization registry and appended to labeling/<STATION>.jsonl, so the labeling tool shows them with the others; no source field. The tool accepts only data/ stations again.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The labeling tool now accepts event folders (Add, Save), and a Save of a label's text drops its "revue" mark.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- inventaire.py: what each source contains on the window (filled or empty columns, metric names, images), names and counts only
- analyser-lot: step 0 on the data, own scripts in <lot>/outils/, section 3 "Outils"
- tool-builder (the optimiser, rewritten): after the analyst, optimises or adds reading tools, never removes; no control yet
- /aiguiser skill, reader, corrector and voir.py removed; its sessions and spec stay as history
- docs: D-097, specs, CLAUDE.md, run.md, README, plan point 56; the shared files also carry another session's pending edits (D-096 entry, plan points 57 to 67)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A form at the top of the Status page: station dropdown (folders of data/), start and end dates
(end excluded, as --au), and an Analyse button that builds the page for that selection and opens it.
The code is in detectors-view/data-loader/chargeur.py: the form, and its local server (port 8766)
that serves out/ and data/ like the common one, plus /analyse, which runs status.py each time.
python3 detectors-view/status.py without arguments, or detectors-view/status.sh, opens the form
alone; with a station folder it builds the page as before, now opened through the loader server.
common.page.open_served takes another port and server script.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A click on a status label shows, below the figure, its details (name, times, sensors, sentence,
then References and Targets per sensor) and, on the right, the timelapse of its camera images,
as in detecteurs.py. Clicks in the details keep the selection; a click elsewhere clears them.
detecteurs.py shares its pieces instead of status.py copying them: the timelapse JavaScript
(TIMELAPSE_JS, the image slider stays in IMAGES_JS), the player HTML and CSS, camera() for the
images and sensor positions, and groupes() with French or English texts. The player's few
messages are now in English (before / DURING / after, no image, GIF export error).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The click keeps only the status's sensors and highlights its bands; the time range, including a
zoom made by hand, stays as it is.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Merging the two thermal phases into Thermal movements only holds for phases on the same targets;
the user has not decided yet. hierarchie-des-status.md keeps the merge; status.py, CLAUDE.md and
D-095 say it is suspended. Occultation and the target filter are unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
detectors-view/hierarchie-des-status.md, validated by the user: No visibility hides Reduced
visibility, Faulty target hides Target hidden, No data hides everything, No visibility hides Target
hidden; the two thermal phases form one status, Thermal movements. A hidden status is cut, not
removed, and only when the stronger one covers all its sensors. status.py transcribes it.
Hiding or isolating targets in the sensor legend keeps only the statuses that touch a visible
target, or all sensors. Discarded labels become transparent, without text, hover or click:
restyling x or base of the label row made Plotly retype its axis as linear.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
One label per detector event at its time, in its category colour, overlapping events on lower rows.
A click zooms on the event (half its duration on each side, 1 h to 6 h), keeps only its sensors and
highlights its band; a second click shows everything again. The range is set on every x axis: in
the same relayout as the band opacities, the axes matching the bottom one did not follow.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
detectors-view/status.py, a pseudo-final version of the site's Explore page: the curves with the
legend on the right, each detector event as a transparent band over them (one colour per category,
legend above), without Shift to check and Slow drift as in the Status line.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- /boucle becomes /events-learner: skill and scripts in
.claude/skills/events-learner/, sessions in events-learner/, spec
vues-deplacements/contexte/events-learner.md, end page
out/events-learner_<session>.html, commits "Learn <STATION> ...";
history keeps /boucle, the review page reads both.
- No benchmark-fin.txt: the end benchmark is the last kept
modification's, on the same events as the start.
- The spec keeps only the why; the how lives in the skill and agents.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- event-builder: called at every batch, reads the whole analysis and
decides on its own, against the event base, what is new; an event
keeps the bounds of the event, not of the batch (plus 6 h).
- the "Nouveautés" section leaves the analysis and the upgrader's
output; the summary lists contradictions with the base.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- analyste: the most precise analysis of the batch, detectors allowed as
a tool; reading, labels, known events, novelties in analyse.md; skill
critiquer-lot renamed analyser-lot.
- detectors-critic: compares the detectors to the analysis event by
event, without looking at the data; verdict and at most two
suggestions in critique.md, read by the detectors-upgrader.
- /boucle step 2, builder, review page, /new-event and score.py import
follow.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- detectors-upgrader: makes the detectors better on the batch from the
analyst's critique; adds, removes or modifies, removing first; targets
the significant events missed or badly bounded, not a perfect match.
- detectors-control: the guard against overfitting; never looks at the
batch, judges the diff and the benchmark on the event base, decides,
and sends its remarks back to the upgrader.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The event base is the analyst's knowledge base, read before or during
its reading; a known event is a lead to check on the data, not a
conclusion. No measurement of the analyst's progress.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Catch-up: E-004, E-006, E-007, E-008, E-010, E-011 in the map; new
section 5 "Faux amis"; rejected E-009 no longer cited.
- /review-event and /new-event: what the event teaches goes into the
map at validation, shown to the expert with the fiche.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- read-event: map and index first, then the card of close events only,
then their data with the reading tools; never all cards at once.
Diagnostic agent, critiquer-lot and builder point to it; the index
header too. Signature length: about 250 characters, a guideline.
- "Cas" becomes "event": events/E-xxx/event.md, skills new-event,
review-event, anonymize-event.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The diagnostic agent is kept in case it is needed again, under a name that
says what it is; entry point still .claude/agents/diagnostic.md; paths updated
in skills, agents, spec, contexts, the living plan and CLAUDE.md; reports and
history keep old paths. Also: two stale tool paths in the living plan.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The reading tools leave agents/diagnostic/outils/ for a root folder of their
own; paths updated in skills, agents, detectors, scripts, case fiches,
support/, contexts and CLAUDE.md; graphique, vignettes and gif find the repo
root one level up; history keeps old paths.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The case base leaves agents/diagnostic/cas/ for a root folder of its own,
with the event map and its graph; paths updated in skills, agents, scripts,
case fiches, contexts, the living plan and CLAUDE.md; history keeps old paths.
Also: plan point 51, an analyst that improves from session to session.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The same ameliorateur agent runs after the releveur; its scope now depends
on the process named in its request.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Détecteur degradee : une cible rejetée la plupart du temps, jour après jour,
quand les autres sont vues (catégorie cible_degradee, grisée, comptée par la
boucle). Page detecteurs.py : error_value moyenne de tous les capteurs à chaque
instant, du vert au rouge, sous les barres.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- End-of-session page for /boucle: the session's curves, the analyst's
labels against the detectors' events per category, a plain score table
and the benchmark (comparaison.py, D-066)
- Detectors moved to vues-deplacements/detectors/ (D-067)
- Detectors must detect everything; what the client sees is a separate
layer (D-068)
- Benchmark: each case keeps its labels from creation (etiquettes.json),
benchmark.py scores the detectors on every case, history in
vues-deplacements/benchmark/historique.csv; run by /boucle at each lot,
after each change and at the end, read by the upgrader and validator;
labels for C-001..C-005 from one analyst pass corrected by their files,
C-006..C-008 from lot 01 (D-069)
- Fixes from the releveur's notes: /boucle arguments and other sessions,
branch name in the spec, detector name in categories.py output, learned
case header, anonymiser.py (camera/, no empty CSVs, --etiquettes),
ensemble.py (clock-aligned steps, title), plages.py (same-sign merge),
labeling request written into /nouveau-cas
- Also carries the other session's uncommitted D-065 edits in the same
files; data/, .gitignore, pomper.py and stations.py are left out
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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>