7.5 KiB
7.5 KiB
Displacement columns (next use case)
According to the FAQ, the columns of the CSV export are prefixed by the target (e.g. target_06_rch):
rch/rcv: displacement corrected for camera movement [mm]. This is the main signal.x/y: raw position in the image [px].rx/ry: relative displacement before camera correction. It is notx - x0.error: target recognition error, not an uncertainty. Default threshold: 0.7.camera_pan|tilt|rotation[deg],camera_scale,camera_sigma0(residual of the reference-network fit).inlier_{ch},reproj_err_{ch}: contribution and residual of each reference.- Sharpness, FWHM, Dominance, Peak Intensity, Flux, SNR: in the "advanced" export of recent cameras only (see below); definitions:
quality-metrics.md.
Exports received (PS des Coudres, D-045)
Two other formats, observed on the data (not documented in the FAQ):
- "advanced" (
<Station>_advanced_<start>_<end>.csv), the source of the analyses: one row per sensor and per measurement, at the native rate (15 min, 10 min depending on the station),time_utcin explicit UTC.sensor_name,pattern_type(global_reffor a compensation reference;reffor a local reference, treated as a target, outside the compensation, according to the station manual and withoutreproj_err, seen on NORDEND),x/y[px],error_value,error_threshold(specific to each sensor: 0.3 to 0.7);x/yare not the centroid of the spot in the image (NORDEND, 2026-10-16): by day (12:30 UTC, seven days), centroid − (x,y) is constant per sensor and differs from one sensor to another (PR17 −2.5 / −0.5 px, PR18 −3.1 / +1.6, PR16 −5.8 / −0.1, CTR02 −1.4 / −2.4, CTR04 −1.0 / −1.4). Centroid weighted above the median of a ±20 px frame, on a ±8 px window. At night, the spot is saturated and the offset changes (PR17 −0.7 to −1.3 px in x). Hypothesis:x,ydesignate the position of the reference pattern (station manual), not the spot itself.relative_x/relative_y(presumablyrx/ry),corr_x/corr_y(presumablyrch/rcv, but not in mm, see below);reproj_errandinlier: references only;sigma0: one value per measurement, repeated on each row; nocamera_pan|tilt|rotation|scale.peak,flux,sharpness,fwhm,dominance,snr: the image quality of each target, computed by the GPU of recent cameras (run.md); "Empty for most devices today" (handoff G,docs/aimsight/AIMsight_handoff_G_site_health.md). Filled on LENZSPITZE and NADELHORN, empty elsewhere (pumping of October 2026);inventory.pysays, on a batch, which columns carry values. For older cameras,~/optical_emulatorrecomputes them from the DIFF images inquality/(run.md), withstacking,exposure,gain,rotationand the imageflag, to be joined ontime_utcandsensor_name. Definitions and reading:quality-metrics.md. Flux, SNR and sharpness relate to the observability of a target in the image, to be separated from the health of the reference network (AIMsight_agentic_support_project_context.md, §5.5 and §5.6).- A rejected measurement (
error_value>error_threshold) keeps its row and itserror_value;corr_x/corr_yare empty, not interpolated. "Rejected" is a judgment by AIMsight, not a sorting by the camera: the camera delivers all its measurements, and the platform of a client that integrates the data receives them and can display them (the user, 2026-10-28).
- LENZSPITZE, relative
x/y(2026-11-04):x/ythere are the offset from the pattern's reference position (medians ~0 px),relative_x/relative_yare equal tocorr_x/corr_y,pattern_typeis empty. Provisional conversion, for this station only:~/aimsight-data/extraction/lenzspitze_absolute.pyrewritesdata/LENZSPITZE/displacement/in image px (pattern center fromlentzpitze_patterns.json+ the measured offset +330.5 / +15.8 px between the JSON frame and the IRON images +x/y) and fillspattern_type. To rerun after a re-pump. Limits: 1023 and 8019 have no pattern in the JSON, theirx/yare emptied (8019 classedglobal_ref, by itsreproj_err);relative_xin px is not reconstructed. To fix in due course: the frame of positions on the pumping side, andvisibility.py,thermal_displacement.py,categories.py, which testpattern_typedirectly instead ofdata.is_reference(empty, they see no reference). - Camera movements (
camera/<Station>_camera_<YYYYMMDD>.csv, pumping only, absent from the exports received): the camera pose at each registration,time_utcin UTC,median_|min_|max_ofpan,tilt,rotation[deg],scale,sigma0at the minute; one row per measurement (min = max), at the instants of the displacements. A measurement instant without a row: the camera was not registered (NORDEND: 101 instants out of 6,071, of which 49 on 29 and 30/07). Orders of magnitude:pan,tiltof a few hundredths of a degree,scalewithin 10⁻³ of 1; differences of several degrees on NORDEND (panup to 3.1°,tilt−2.8 to 4.0°), not explained. Sign: a positivetiltmeans the camera is nose-diving (the expert, 2026-11-03, BREITHORN: thetiltrises all October while the camera tilts). Read byoverview.pyandinventory.py(D-073). - Hourly (
<Station>_<start>_to_<end>_1hour.csv): one row per hour, targets only. Per target:horizontal_displacement,vertical_displacement, their_min/_max,_error,_count_val.timestampwithout time zone: Swiss time (UTC+2 in October), at the start of the hour. Verified:_error= mean of theerror_valueof the hour, to within 0.0006 (median).count_valcounts the measurements of the hour, rejected ones included.
- Unit of
corr_x/corr_y:horizontal_displacement= factor × hourly mean ofcorr_x+ constant offset (likewiseverticalandcorr_y, correlation ≥ 0.99). The factor depends on the pattern:target050.61,target1.6,target024.3,target036.85,target047.9. If the hourly is in mm (FAQ),corr_x/corr_yare not. According to the user (2026-10-16), they are surely in px, the factor then being mm per px. This is compatible with NORDEND: at the jump of PR17 (08/10 02:30),corr_ydrops by about 0.15, andrelative_y(in px) by 0.26 px against 0.08 px for the other sensors; over the window,corrof PR17 ≈ 0.8 × (relative− mean of therelativeof the global references), but a mean ignores the rotation and scale of the compensation. To confirm. The factor depends on the station: on NORDEND,vertical_displacementof PR17 = 55.5 × hourly mean ofcorr_y(r = 0.994, 244 hours), i.e. about 9 mm for its jump of 0.15.
Causes to tell apart for a displacement anomaly:
- real movement of the structure;
- camera movement;
- instability of the compensation (Barcelona case);
- local degradation of a target;
- parallax or unsuitable model.
The authoritative reference is AIMsight_reference_quality_event_explainer_roadmap.md (AIMsight documentation, stored in Support-Agent, docs/aimsight/). The non-negotiable rules that relate to it:
- build nothing on a binary
inlier: RANSAC will be replaced by a weighted estimator; use continuous weights,N_eff, residuals, influence; sigma0alone and the number of references are never sufficient criteria;- do not confuse the image quality of a target with the quality of the reference network, nor a small residual with a well-constrained transformation;
- do not confuse common-mode movement with structural movement, nor coherent references with physically fixed references.