From 6454ffef0f71eaefd698cad1d9b1a891e4bcf34f Mon Sep 17 00:00:00 2001 From: maxime Date: Mon, 16 Nov 2026 14:56:41 +0100 Subject: [PATCH] =?UTF-8?q?D=C3=A9p=C3=B4ts=20renomm=C3=A9s=20avec=20le=20?= =?UTF-8?q?pr=C3=A9fixe=20aimsight-=20:=20chemins=20et=20noms=20mis=20?= =?UTF-8?q?=C3=A0=20jour?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Opus 5.5 --- README.md | 6 +++--- extraction/README.md | 4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index c639127..9269684 100644 --- a/README.md +++ b/README.md @@ -6,8 +6,8 @@ The data of the AIMsight stations, in a single copy on the workstation, and thei - `extraction/`: the pumping, read-only on the platform; how to use it: `extraction/README.md`. VS Code tasks "pump" and "pump a range". - `.env`: the credentials of the database and of S3, at the root, never versioned. -The other repositories (Diagnostic-App, Optimizer) read the data through a link `data -> ~/aimsight-data/data`, ignored by git. Pumping is done from here only: the lock `out/pump.lock` holds for this folder alone. +The other repositories (aimsight-app, Optimizer) read the data through a link `data -> ~/aimsight-data/data`, ignored by git. Pumping is done from here only: the lock `out/pump.lock` holds for this folder alone. -The labels are in the neighbouring repository `~/labeling`. +The labels are in the neighbouring repository `~/aimsight-labeling`. -Extracted from Diagnostic-App on 2026-11-13 (commit 462ba9e); the earlier history of the pumping is in Support-Agent. +Extracted from aimsight-app on 2026-11-13 (commit 462ba9e); the earlier history of the pumping is in Support-Agent. diff --git a/extraction/README.md b/extraction/README.md index 3dddc38..068207f 100644 --- a/extraction/README.md +++ b/extraction/README.md @@ -6,7 +6,7 @@ - the **camera movements** (`pan`, `tilt`, `scale`, `rotation`, `sigma0`), as median and bounds (`median_`, `min_`, `max_`) per minute, only at the times the camera was realigned, one CSV per day in `camera/`; - the IRON **images** (`--images`, one per hour by default, `--every 10` or `--every 0` for more) in `images/`, and the differential ones (`--diff`) in `images_diff/`. -Formats: `~/labeling/knowledge/displacement-columns.md`. +Formats: `~/aimsight-labeling/knowledge/displacement-columns.md`. **Tracked stations**: `stations.txt`, one serial number per line. Without station nor dates, the script updates them all up to now: each station first fills its missing days between the first and the last pumped day (without displacements, or without any metric), then restarts from its last day, pumped again (it was perhaps incomplete); a station without a folder in `data/` gets the last 30 days. @@ -48,4 +48,4 @@ Claude may run `pump.sh` itself (user's agreement, 2026-11-12): read-only, small - A day failed on a timeout (`QueryCanceled: … statement timeout`): run it again alone with `--delay 300`. The slowness comes from the database, not from the volume. - An hour without an image can have its measurement: the image never reached S3 (empty `measurement_uuid`, unfinished upload). The script skips it and takes the next image of the slot if there is one. - A past day, pumped before the station had finished sending its data (outage, late synchronisation), stays incomplete: delete its files in `data//` and run again. -- LENZSPITZE: its exports have relative `x` / `y` and an empty `pattern_type`; `pump.sh` then runs `lenzspitze_absolute.py` (provisional; details in `~/labeling/knowledge/displacement-columns.md`). +- LENZSPITZE: its exports have relative `x` / `y` and an empty `pattern_type`; `pump.sh` then runs `lenzspitze_absolute.py` (provisional; details in `~/aimsight-labeling/knowledge/displacement-columns.md`).