Patterns by sensor_name (a property, or a window redrawn from a DIFF image as the device's pattern editor does), re-measured with optical's emulator, camera correction as the cloud's process_shifts (one measurement at a time, or the series), written in the files of data/ (displacement/, camera/, targets.csv; images/, metrics/, weather/ linked to data_diff/), with run.yaml and diagnostics/ beside the stations. configs/cloud.yaml, empty, reproduces data/JUNGFRAU 2026-10-12..16: corr_x/y within 0.03 px, the same rejections, the camera pose within 5e-4 deg; 16 s. configs/jungfrau_example.yaml: PM_G back to 0.7, BL_C's window redrawn. .gitignore: data_diff/, runs/, remeasure/. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
3.0 KiB
3.0 KiB
aimsight-data
The data of the AIMsight stations, in a single copy on the workstation, and their pumping.
data/<SERIAL>/: filled by the pumping, out of git (metrics/,displacement/,camera/,images/,weather/for a station with a Swiss position…). A lost folder is pumped again.data_diff/<SERIAL>/: the differential images, full size, with their index and the patterns, to measure them again, and the metrics, IRON images, weather andtargets.csvas indata/(extraction/pump_diff.sh), out of git; it never touchesdata/. Shared by every configuration. Design:docs/superpowers/specs/2026-11-19-configurations-design.md.configs/<name>.yaml: a configuration, what differs from the cloud (patterns bysensor_name: a property, or a window redrawn from a DIFF image; the camera correction: algorithm, mode, focal distance, one measurement at a time or the series), in git;cloud.yaml, empty, is the cloud and reproducesdata/(JUNGFRAU 2026-10-12..16:corr_x/ywithin 0.03 px, the same rejections, the camera pose within 5e-4 deg);jungfrau_example.yaml, a model.runs/<name>/<SERIAL>/: the result of a configuration, out of git, the tree ofdata/(displacement/,camera/,targets.csv;images/,metrics/,weather/linked todata_diff/): a repository reads it by pointing itsdatalink at~/aimsight-data/runs/<name>instead of~/aimsight-data/data. Beside the stations,run.yaml(the configuration as resolved, optical's commit) anddiagnostics/(the patterns used, the emulator's rows: edge margin, second spot).processing/run_config.sh <config> [SERIAL...] [--from D] [--to E]: computesruns/<name>/(optical's emulator and camera correction, from$OPTICAL, default~/optical; 16 s for 5 days of JUNGFRAU);--checkwithout data. Design:docs/superpowers/specs/2026-11-19-run-config-design.md. A window redrawn on a target restarts its displacement at zero at the image it is cut from (x_refis kept, the template is new): cut it from an image at the start of the period studied.extraction/: the pumping, read-only on the platform; how to use it:extraction/README.md. VS Code tasks "pump" and "pump a range".extraction/pumping.py: the tracked stations, launching the pumping and its state, for the callers (aimsight-app, page Stations).weather/: the weather measured by MeteoSwiss at a place over a past range (weather/meteoswiss.py), written intodata/<SERIAL>/weather/at each pumping (extraction/weather.py); its doc inweather/README.md..env: the credentials of the database and of S3, at the root, never versioned.
The other repositories (aimsight-app, Optimizer) read the data through a link data -> ~/aimsight-data/data, ignored by git. The methods that bring data in live here; the app only calls them. Pumping is done from here only: the lock out/pump.lock holds for this folder alone.
The labels are in the neighbouring repository ~/aimsight-labeling.
Extracted from aimsight-app on 2026-11-13 (commit 462ba9e); the earlier history of the pumping is in Support-Agent.