From cce2e039ed17cc3a952ddb5afc96ebc934bcf264 Mon Sep 17 00:00:00 2001 From: maxime Date: Thu, 12 Nov 2026 09:19:25 +0100 Subject: [PATCH] Base de connaissances reprise de Support-AI : corpus, import, instructions, tests Ajoute aussi WEISSHORN et MISSISSIPPI au test du corpus, et un message clair quand LibreDesk est injoignable. Co-Authored-By: Claude Opus 5.5 --- .gitignore | 7 + base_connaissances/__init__.py | 0 ...t-configuration-from-a-historical-image.md | 21 ++ ...and-post-processing-tools-are-available.md | 29 +++ ...border-suitable-other-home-made-targets.md | 14 ++ ...t-activate-a-relay-or-dry-contact-alarm.md | 9 + ...ht-be-installed-in-a-marine-environment.md | 13 + ...sight-measure-without-dedicated-targets.md | 9 + ...nt-triggered-or-high-speed-measurements.md | 11 + ...ents-acquired-before-ftp-was-configured.md | 9 + ...matically-scan-several-monitoring-areas.md | 10 + ...mbined-to-obtain-x-y-and-z-displacement.md | 9 + ...le-client-regarde-dans-les-deplacements.md | 10 + ...mera-operate-without-a-cloud-connection.md | 14 ++ ...tem-detect-excessive-camera-instability.md | 10 + ...ition-error-handled-in-data-exploration.md | 15 ++ .../how-can-i-access-the-camera-locally.md | 9 + ...ct-deformation-of-the-reference-network.md | 19 ++ ...-export-the-advanced-diagnostic-metrics.md | 11 + ...o-reference-position-used-for-rx-and-ry.md | 9 + ...ce-and-heat-shimmer-affect-measurements.md | 10 + ...points-can-one-aimsight-station-monitor.md | 9 + ...ow-should-reference-targets-be-selected.md | 18 ++ .../is-a-thermal-camera-option-available.md | 8 + ...dedicated-monitoring-software-available.md | 14 ++ ...iodic-metrological-maintenance-required.md | 11 + ...the-software-web-based-or-desktop-based.md | 7 + ...atterie-et-l-alimentation-de-la-station.md | 22 ++ ...haine-de-mesure-d-ou-vient-une-anomalie.md | 25 ++ ...ycle-thermique-les-vagues-de-la-journee.md | 8 + ...ce-qu-elles-veulent-dire-pour-le-client.md | 18 ++ .../les-metriques-systeme-de-la-station.md | 17 ++ ...les-trous-pourquoi-des-mesures-manquent.md | 12 + ...mera-does-not-start-what-should-i-check.md | 17 ++ ...ot-contain-a-timestamp-what-should-i-do.md | 11 + ...me-noisy-or-invalid-what-should-i-check.md | 37 +++ ...nger-being-measured-what-should-i-check.md | 30 +++ ...es-de-lecture-des-donnees-de-la-station.md | 9 + .../corpus/station-guide-access-modes.md | 39 +++ .../station-guide-acquisition-length.md | 5 + .../station-guide-acquisition-schedules.md | 10 + .../corpus/station-guide-acquisition-type.md | 8 + ...vailable-signals-and-diagnostic-metrics.md | 22 ++ .../station-guide-camera-management-panel.md | 27 ++ .../corpus/station-guide-camera-movement.md | 21 ++ .../corpus/station-guide-camera-operation.md | 6 + .../corpus/station-guide-camera-parameters.md | 15 ++ ...tation-guide-cellular-apn-configuration.md | 8 + .../corpus/station-guide-charging.md | 32 +++ ...een-single-and-differential-acquisition.md | 8 + ...de-contrast-enhanced-overlay-adjustment.md | 13 + .../station-guide-creating-a-schedule.md | 14 ++ .../station-guide-data-exploration-page.md | 29 +++ .../corpus/station-guide-demo-kit-contents.md | 9 + .../corpus/station-guide-disk.md | 6 + .../corpus/station-guide-dominance.md | 18 ++ .../corpus/station-guide-error-value.md | 20 ++ .../corpus/station-guide-exporting-graphs.md | 6 + ...on-guide-exposure-and-image-preparation.md | 22 ++ .../corpus/station-guide-flux.md | 22 ++ .../corpus/station-guide-fps-duration.md | 10 + .../corpus/station-guide-ftp.md | 6 + .../corpus/station-guide-fwhm-px.md | 19 ++ ...ge-display-and-reflector-identification.md | 7 + ...tion-guide-image-mode-and-target-preset.md | 15 ++ ...uide-interaction-during-target-creation.md | 7 + .../corpus/station-guide-interval-count.md | 8 + .../corpus/station-guide-live-plot.md | 28 +++ .../corpus/station-guide-live-view-page.md | 15 ++ ...tion-guide-marker-configuration-process.md | 13 + ...e-measurement-range-and-optical-options.md | 11 + .../station-guide-monitoring-station.md | 14 ++ .../corpus/station-guide-monitoring.md | 15 ++ .../corpus/station-guide-navigation-bar.md | 14 ++ ...ation-guide-navigation-within-the-plots.md | 15 ++ .../corpus/station-guide-network-settings.md | 25 ++ .../corpus/station-guide-output-options.md | 8 + .../station-guide-panning-and-resetting.md | 8 + .../station-guide-pattern-creation-page.md | 19 ++ .../corpus/station-guide-peak-intensity.md | 15 ++ .../corpus/station-guide-periodic-interval.md | 8 + ...-start-cellular-monitoring-installation.md | 62 +++++ ...tation-guide-raw-horizontal-vertical-px.md | 14 ++ ...e-reflective-targets-in-bright-sunlight.md | 11 + ...n-guide-relative-horizontal-vertical-mm.md | 11 + .../station-guide-rest-api-documentation.md | 8 + ...n-guide-saving-and-verifying-a-schedule.md | 15 ++ .../corpus/station-guide-sharpness.md | 15 ++ .../corpus/station-guide-snr.md | 19 ++ .../corpus/station-guide-status-leds.md | 9 + .../station-guide-system-settings-page.md | 20 ++ ...ge-quality-and-pattern-matching-metrics.md | 13 + ...on-guide-trace-selection-and-visibility.md | 8 + .../corpus/station-guide-troubleshooting.md | 17 ++ ...on-guide-typical-installation-procedure.md | 17 ++ ...orking-with-conventional-image-features.md | 57 +++++ .../station-guide-zooming-and-scaling.md | 9 + .../tensions-de-la-batterie-selon-son-etat.md | 12 + ...-not-receiving-data-what-should-i-check.md | 21 ++ ...t-connected-over-4g-what-should-i-check.md | 18 ++ ...the-columns-in-the-csv-export-represent.md | 31 +++ ...-y-rx-and-ry-represent-in-exported-data.md | 9 + ...-movement-represent-in-data-exploration.md | 16 ++ .../what-does-the-error-value-represent.md | 17 ++ ...s-shape-or-becomes-partially-obstructed.md | 16 ++ ...changes-orientation-after-commissioning.md | 12 + ...f-the-internet-or-4g-connection-is-lost.md | 27 ++ ...the-delivery-time-for-multiple-stations.md | 8 + ...at-is-the-error-column-in-exported-data.md | 17 ++ .../corpus/what-is-the-error-threshold.md | 10 + ...attery-autonomy-if-external-power-fails.md | 8 + .../what-is-the-maximum-operating-distance.md | 14 ++ ...ck-before-leaving-the-installation-site.md | 33 +++ ...-targets-may-potentially-move-or-settle.md | 20 ++ ...here-should-reference-targets-be-placed.md | 29 +++ ...ich-data-transfer-methods-are-available.md | 12 + ...gnals-are-available-in-data-exploration.md | 34 +++ .../which-file-formats-can-aimsight-export.md | 12 + .../which-licensing-models-are-available.md | 12 + .../which-timezone-is-used-for-timestamps.md | 17 ++ base_connaissances/decoupage.py | 110 +++++++++ base_connaissances/importer.py | 131 ++++++++++ base_connaissances/instructions.md | 18 ++ .../plans/2026-11-12-support-libredesk.md | 231 ++++++++++++++++++ .../2026-11-12-support-libredesk-design.md | 133 ++++++++++ tests/faux_libredesk.py | 48 ++++ tests/test_corpus.py | 63 +++++ tests/test_decoupage.py | 63 +++++ tests/test_garde_fou_base.py | 23 ++ tests/test_importer.py | 93 +++++++ 130 files changed, 2784 insertions(+) create mode 100644 .gitignore create mode 100644 base_connaissances/__init__.py create mode 100644 base_connaissances/corpus/aimsight-cloud-optional-service-how-can-i-apply-a-target-configuration-from-a-historical-image.md create mode 100644 base_connaissances/corpus/aimsight-cloud-optional-service-which-additional-diagnostic-and-post-processing-tools-are-available.md create mode 100644 base_connaissances/corpus/are-white-enamel-targets-with-a-black-border-suitable-other-home-made-targets.md create mode 100644 base_connaissances/corpus/can-aimsight-activate-a-relay-or-dry-contact-alarm.md create mode 100644 base_connaissances/corpus/can-aimsight-be-installed-in-a-marine-environment.md create mode 100644 base_connaissances/corpus/can-aimsight-measure-without-dedicated-targets.md create mode 100644 base_connaissances/corpus/can-aimsight-perform-event-triggered-or-high-speed-measurements.md create mode 100644 base_connaissances/corpus/can-i-retrieve-measurements-acquired-before-ftp-was-configured.md create mode 100644 base_connaissances/corpus/can-the-camera-automatically-scan-several-monitoring-areas.md create mode 100644 base_connaissances/corpus/can-two-cameras-be-combined-to-obtain-x-y-and-z-displacement.md create mode 100644 base_connaissances/corpus/ce-que-le-client-regarde-dans-les-deplacements.md create mode 100644 base_connaissances/corpus/does-the-camera-operate-without-a-cloud-connection.md create mode 100644 base_connaissances/corpus/does-the-system-detect-excessive-camera-instability.md create mode 100644 base_connaissances/corpus/how-are-targets-with-excessive-recognition-error-handled-in-data-exploration.md create mode 100644 base_connaissances/corpus/how-can-i-access-the-camera-locally.md create mode 100644 base_connaissances/corpus/how-can-i-detect-deformation-of-the-reference-network.md create mode 100644 base_connaissances/corpus/how-can-i-export-the-advanced-diagnostic-metrics.md create mode 100644 base_connaissances/corpus/how-can-i-redefine-the-zero-reference-position-used-for-rx-and-ry.md create mode 100644 base_connaissances/corpus/how-do-atmospheric-turbulence-and-heat-shimmer-affect-measurements.md create mode 100644 base_connaissances/corpus/how-many-points-can-one-aimsight-station-monitor.md create mode 100644 base_connaissances/corpus/how-should-reference-targets-be-selected.md create mode 100644 base_connaissances/corpus/is-a-thermal-camera-option-available.md create mode 100644 base_connaissances/corpus/is-dedicated-monitoring-software-available.md create mode 100644 base_connaissances/corpus/is-periodic-metrological-maintenance-required.md create mode 100644 base_connaissances/corpus/is-the-software-web-based-or-desktop-based.md create mode 100644 base_connaissances/corpus/la-batterie-et-l-alimentation-de-la-station.md create mode 100644 base_connaissances/corpus/la-chaine-de-mesure-d-ou-vient-une-anomalie.md create mode 100644 base_connaissances/corpus/le-cycle-thermique-les-vagues-de-la-journee.md create mode 100644 base_connaissances/corpus/les-familles-d-anomalies-et-ce-qu-elles-veulent-dire-pour-le-client.md create mode 100644 base_connaissances/corpus/les-metriques-systeme-de-la-station.md create mode 100644 base_connaissances/corpus/les-trous-pourquoi-des-mesures-manquent.md create mode 100644 base_connaissances/corpus/my-aimsight-camera-does-not-start-what-should-i-check.md create mode 100644 base_connaissances/corpus/my-exported-csv-file-does-not-contain-a-timestamp-what-should-i-do.md create mode 100644 base_connaissances/corpus/my-measurements-suddenly-become-noisy-or-invalid-what-should-i-check.md create mode 100644 base_connaissances/corpus/one-target-is-no-longer-being-measured-what-should-i-check.md create mode 100644 base_connaissances/corpus/pieges-de-lecture-des-donnees-de-la-station.md create mode 100644 base_connaissances/corpus/station-guide-access-modes.md create mode 100644 base_connaissances/corpus/station-guide-acquisition-length.md create mode 100644 base_connaissances/corpus/station-guide-acquisition-schedules.md create mode 100644 base_connaissances/corpus/station-guide-acquisition-type.md create mode 100644 base_connaissances/corpus/station-guide-available-signals-and-diagnostic-metrics.md create mode 100644 base_connaissances/corpus/station-guide-camera-management-panel.md create mode 100644 base_connaissances/corpus/station-guide-camera-movement.md create mode 100644 base_connaissances/corpus/station-guide-camera-operation.md create mode 100644 base_connaissances/corpus/station-guide-camera-parameters.md create mode 100644 base_connaissances/corpus/station-guide-cellular-apn-configuration.md create mode 100644 base_connaissances/corpus/station-guide-charging.md create mode 100644 base_connaissances/corpus/station-guide-choosing-between-single-and-differential-acquisition.md create mode 100644 base_connaissances/corpus/station-guide-contrast-enhanced-overlay-adjustment.md create mode 100644 base_connaissances/corpus/station-guide-creating-a-schedule.md create mode 100644 base_connaissances/corpus/station-guide-data-exploration-page.md create mode 100644 base_connaissances/corpus/station-guide-demo-kit-contents.md create mode 100644 base_connaissances/corpus/station-guide-disk.md create mode 100644 base_connaissances/corpus/station-guide-dominance.md create mode 100644 base_connaissances/corpus/station-guide-error-value.md create mode 100644 base_connaissances/corpus/station-guide-exporting-graphs.md create mode 100644 base_connaissances/corpus/station-guide-exposure-and-image-preparation.md create mode 100644 base_connaissances/corpus/station-guide-flux.md create mode 100644 base_connaissances/corpus/station-guide-fps-duration.md create mode 100644 base_connaissances/corpus/station-guide-ftp.md create mode 100644 base_connaissances/corpus/station-guide-fwhm-px.md create mode 100644 base_connaissances/corpus/station-guide-image-display-and-reflector-identification.md create mode 100644 base_connaissances/corpus/station-guide-image-mode-and-target-preset.md create mode 100644 base_connaissances/corpus/station-guide-interaction-during-target-creation.md create mode 100644 base_connaissances/corpus/station-guide-interval-count.md create mode 100644 base_connaissances/corpus/station-guide-live-plot.md create mode 100644 base_connaissances/corpus/station-guide-live-view-page.md create mode 100644 base_connaissances/corpus/station-guide-marker-configuration-process.md create mode 100644 base_connaissances/corpus/station-guide-measurement-range-and-optical-options.md create mode 100644 base_connaissances/corpus/station-guide-monitoring-station.md create mode 100644 base_connaissances/corpus/station-guide-monitoring.md create mode 100644 base_connaissances/corpus/station-guide-navigation-bar.md create mode 100644 base_connaissances/corpus/station-guide-navigation-within-the-plots.md create mode 100644 base_connaissances/corpus/station-guide-network-settings.md create mode 100644 base_connaissances/corpus/station-guide-output-options.md create mode 100644 base_connaissances/corpus/station-guide-panning-and-resetting.md create mode 100644 base_connaissances/corpus/station-guide-pattern-creation-page.md create mode 100644 base_connaissances/corpus/station-guide-peak-intensity.md create mode 100644 base_connaissances/corpus/station-guide-periodic-interval.md create mode 100644 base_connaissances/corpus/station-guide-quick-start-cellular-monitoring-installation.md create mode 100644 base_connaissances/corpus/station-guide-raw-horizontal-vertical-px.md create mode 100644 base_connaissances/corpus/station-guide-reflective-targets-in-bright-sunlight.md create mode 100644 base_connaissances/corpus/station-guide-relative-horizontal-vertical-mm.md create mode 100644 base_connaissances/corpus/station-guide-rest-api-documentation.md create mode 100644 base_connaissances/corpus/station-guide-saving-and-verifying-a-schedule.md create mode 100644 base_connaissances/corpus/station-guide-sharpness.md create mode 100644 base_connaissances/corpus/station-guide-snr.md create mode 100644 base_connaissances/corpus/station-guide-status-leds.md create mode 100644 base_connaissances/corpus/station-guide-system-settings-page.md create mode 100644 base_connaissances/corpus/station-guide-target-image-quality-and-pattern-matching-metrics.md create mode 100644 base_connaissances/corpus/station-guide-trace-selection-and-visibility.md create mode 100644 base_connaissances/corpus/station-guide-troubleshooting.md create mode 100644 base_connaissances/corpus/station-guide-typical-installation-procedure.md create mode 100644 base_connaissances/corpus/station-guide-working-with-conventional-image-features.md create mode 100644 base_connaissances/corpus/station-guide-zooming-and-scaling.md create mode 100644 base_connaissances/corpus/tensions-de-la-batterie-selon-son-etat.md create mode 100644 base_connaissances/corpus/the-camera-is-online-but-i-am-not-receiving-data-what-should-i-check.md create mode 100644 base_connaissances/corpus/the-camera-is-running-but-is-not-connected-over-4g-what-should-i-check.md create mode 100644 base_connaissances/corpus/what-do-the-columns-in-the-csv-export-represent.md create mode 100644 base_connaissances/corpus/what-do-x-y-rx-and-ry-represent-in-exported-data.md create mode 100644 base_connaissances/corpus/what-does-camera-movement-represent-in-data-exploration.md create mode 100644 base_connaissances/corpus/what-does-the-error-value-represent.md create mode 100644 base_connaissances/corpus/what-happens-if-a-target-changes-shape-or-becomes-partially-obstructed.md create mode 100644 base_connaissances/corpus/what-happens-if-the-camera-moves-or-changes-orientation-after-commissioning.md create mode 100644 base_connaissances/corpus/what-happens-to-alarms-if-the-internet-or-4g-connection-is-lost.md create mode 100644 base_connaissances/corpus/what-is-the-delivery-time-for-multiple-stations.md create mode 100644 base_connaissances/corpus/what-is-the-error-column-in-exported-data.md create mode 100644 base_connaissances/corpus/what-is-the-error-threshold.md create mode 100644 base_connaissances/corpus/what-is-the-expected-battery-autonomy-if-external-power-fails.md create mode 100644 base_connaissances/corpus/what-is-the-maximum-operating-distance.md create mode 100644 base_connaissances/corpus/what-should-i-check-before-leaving-the-installation-site.md create mode 100644 base_connaissances/corpus/what-should-i-do-if-all-targets-may-potentially-move-or-settle.md create mode 100644 base_connaissances/corpus/where-should-reference-targets-be-placed.md create mode 100644 base_connaissances/corpus/which-data-transfer-methods-are-available.md create mode 100644 base_connaissances/corpus/which-diagnostic-signals-are-available-in-data-exploration.md create mode 100644 base_connaissances/corpus/which-file-formats-can-aimsight-export.md create mode 100644 base_connaissances/corpus/which-licensing-models-are-available.md create mode 100644 base_connaissances/corpus/which-timezone-is-used-for-timestamps.md create mode 100644 base_connaissances/decoupage.py create mode 100644 base_connaissances/importer.py create mode 100644 base_connaissances/instructions.md create mode 100644 docs/superpowers/plans/2026-11-12-support-libredesk.md create mode 100644 docs/superpowers/specs/2026-11-12-support-libredesk-design.md create mode 100644 tests/faux_libredesk.py create mode 100644 tests/test_corpus.py create mode 100644 tests/test_decoupage.py create mode 100644 tests/test_garde_fou_base.py create mode 100644 tests/test_importer.py diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..6d4bce8 --- /dev/null +++ b/.gitignore @@ -0,0 +1,7 @@ +.env +instance-de-test/.env +instance-de-test/config.toml +instance-de-test/uploads/ +__pycache__/ +cases/ +.superpowers/ diff --git a/base_connaissances/__init__.py b/base_connaissances/__init__.py new file mode 100644 index 0000000..e69de29 diff --git a/base_connaissances/corpus/aimsight-cloud-optional-service-how-can-i-apply-a-target-configuration-from-a-historical-image.md b/base_connaissances/corpus/aimsight-cloud-optional-service-how-can-i-apply-a-target-configuration-from-a-historical-image.md new file mode 100644 index 0000000..11d657a --- /dev/null +++ b/base_connaissances/corpus/aimsight-cloud-optional-service-how-can-i-apply-a-target-configuration-from-a-historical-image.md @@ -0,0 +1,21 @@ +# (AIMsight Cloud — optional service) How can I apply a target configuration from a historical image? + +The general Pattern Configuration workflow is shared by the local station interface and AIMsight +Cloud. The Cloud interface additionally allows patterns to be defined from a stored image and +the affected measurements to be reprocessed. +After selecting the image at the required date and configuring the targets, the Actions button and +Update Strategy dropdown determine how the new reference is applied: +• Reinitialize — Uses the selected image and configuration as a new reference and restarts +the corresponding displacement values from zero. This is typically used when reconfiguring +all targets, for example after a significant movement or repositioning of the camera station. +• Reinitialize with motion compensation — Preserves the reference network and cameramotion correction while reinitializing an individual target. A typical case is a prism that was +accidentally moved and then placed back at a slightly different position. +• Continuous — Applies the updated pattern or reference while preserving continuity of the +existing measurement trace. The displacement curve therefore does not return to zero +when the new reference is introduced. This is useful when a pattern must be updated or +refined without creating a discontinuity in the history. +Before applying the action, verify the date of the selected image, the target zones, the reference +network, and the intended result. The selected strategy determines both the measurement zero +and the continuity of the reprocessed data. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/aimsight-cloud-optional-service-which-additional-diagnostic-and-post-processing-tools-are-available.md b/base_connaissances/corpus/aimsight-cloud-optional-service-which-additional-diagnostic-and-post-processing-tools-are-available.md new file mode 100644 index 0000000..d74c658 --- /dev/null +++ b/base_connaissances/corpus/aimsight-cloud-optional-service-which-additional-diagnostic-and-post-processing-tools-are-available.md @@ -0,0 +1,29 @@ +# (AIMsight Cloud — optional service) Which additional diagnostic and post-processing tools are available? + +Image acquisition and processing are performed on the station. Depending on the selected +licensing model, these functions are enabled through either a standalone local software licence +or an active AIMsight Cloud subscription. AIMsight Cloud additionally keeps measurements, +diagnostic information, and — when image archiving is enabled — the associated images +together in one historical view. +This is particularly useful when reviewing an unexpected measurement. From the measurement +history, the user can open the image corresponding to a selected point or period with a simple +click and inspect what the camera actually saw. This can help distinguish structural movement +from causes such as an obstruction, vegetation, a vehicle, changed illumination, contamination, a +shifted prism, or camera movement. +The Cloud interface also exposes recognition-quality information for each target, including Error +Value, Sharpness, FWHM, Dominance, Peak Intensity, Flux, and SNR, together with cameramotion and reference-network metrics where available. Measurements, quality indicators, and +visual evidence can therefore be reviewed in the same context rather than as separate files. +The visualization and post-processing tools support tasks such as: +• navigating through the measurement history and opening the corresponding archived +image; +• comparing target traces and camera-motion information; +• highlighting or filtering periods with excessive recognition error; +• applying offsets, rolling filters, or other available post-processing options; +• reviewing the consistency of the reference network; and +• reprocessing measurements when the target configuration or reference system must be +changed. +These functions improve traceability and make abnormal measurements easier to understand. A +station equipped with a local software licence can continue to acquire and process data +independently if the Cloud connection is temporarily unavailable. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/are-white-enamel-targets-with-a-black-border-suitable-other-home-made-targets.md b/base_connaissances/corpus/are-white-enamel-targets-with-a-black-border-suitable-other-home-made-targets.md new file mode 100644 index 0000000..f884f0c --- /dev/null +++ b/base_connaissances/corpus/are-white-enamel-targets-with-a-black-border-suitable-other-home-made-targets.md @@ -0,0 +1,14 @@ +# Are white enamel targets with a black border suitable? Other home-made targets? + +They can be used at relatively short distances, but they are less effective than more directional +reflective targets such as: +• prisms; +• retroreflectors; +• reflective tape; +• AIMsight markers. +Measurement availability, particularly at night, may therefore be lower with simple painted or +enamel targets. +Target selection should be based on the required measurement accuracy, distance, lighting +conditions, and expected measurement availability. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/can-aimsight-activate-a-relay-or-dry-contact-alarm.md b/base_connaissances/corpus/can-aimsight-activate-a-relay-or-dry-contact-alarm.md new file mode 100644 index 0000000..75d3c62 --- /dev/null +++ b/base_connaissances/corpus/can-aimsight-activate-a-relay-or-dry-contact-alarm.md @@ -0,0 +1,9 @@ +# Can AIMsight activate a relay or dry-contact alarm? + +As an option, the camera can be equipped with an output that can be used to control a relay or, +depending on the electrical requirements, another local alarm device. +This makes it possible to implement local alarm actions that do not depend solely on a remote +cloud or cellular connection. +The electrical interface and relay configuration should be verified for the specific installation. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/can-aimsight-be-installed-in-a-marine-environment.md b/base_connaissances/corpus/can-aimsight-be-installed-in-a-marine-environment.md new file mode 100644 index 0000000..d26838e --- /dev/null +++ b/base_connaissances/corpus/can-aimsight-be-installed-in-a-marine-environment.md @@ -0,0 +1,13 @@ +# Can AIMsight be installed in a marine environment? + +The standard enclosure and camera supports are primarily aluminium and are suitable for +temporary monitoring campaigns such as a several-month port installation. +For marine installations: +• stainless-steel fasteners can be used; +• the camera sun/rain shield should be installed; +• the front optical surface may require periodic cleaning depending on exposure. +For recurrent offshore use or permanent marine installations, a dedicated marinized +configuration can be considered, potentially including stainless-steel components and +automated window-cleaning solutions. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/can-aimsight-measure-without-dedicated-targets.md b/base_connaissances/corpus/can-aimsight-measure-without-dedicated-targets.md new file mode 100644 index 0000000..69f5559 --- /dev/null +++ b/base_connaissances/corpus/can-aimsight-measure-without-dedicated-targets.md @@ -0,0 +1,9 @@ +# Can AIMsight measure without dedicated targets? + +Yes, depending on the application, AIMsight can track suitable natural image features. +However, dedicated reflective targets generally provide substantially better robustness and +measurement availability, particularly when lighting or weather conditions vary. +For safety-critical alarm applications, natural-feature tracking should therefore be evaluated +carefully before being relied upon as the sole measurement method. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/can-aimsight-perform-event-triggered-or-high-speed-measurements.md b/base_connaissances/corpus/can-aimsight-perform-event-triggered-or-high-speed-measurements.md new file mode 100644 index 0000000..caef466 --- /dev/null +++ b/base_connaissances/corpus/can-aimsight-perform-event-triggered-or-high-speed-measurements.md @@ -0,0 +1,11 @@ +# Can AIMsight perform event-triggered or high-speed measurements? + +Yes. +AIMsight can operate using: +• scheduled acquisitions; +• periodic monitoring; +• continuous or dynamic acquisition; +• externally triggered or event-based acquisition. +The appropriate configuration depends on the required measurement rate and application. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/can-i-retrieve-measurements-acquired-before-ftp-was-configured.md b/base_connaissances/corpus/can-i-retrieve-measurements-acquired-before-ftp-was-configured.md new file mode 100644 index 0000000..d07b5e9 --- /dev/null +++ b/base_connaissances/corpus/can-i-retrieve-measurements-acquired-before-ftp-was-configured.md @@ -0,0 +1,9 @@ +# Can I retrieve measurements acquired before FTP was configured? + +Manually triggered local dynamic acquisitions are stored in the local database and can be +retrieved using the Data Exploration tab. +Periodic monitoring acquisitions are not intended to provide permanent onboard backup storage. +Local storage is managed to avoid filling the station’s internal storage once data have been +transferred to the configured remote destination. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/can-the-camera-automatically-scan-several-monitoring-areas.md b/base_connaissances/corpus/can-the-camera-automatically-scan-several-monitoring-areas.md new file mode 100644 index 0000000..7690324 --- /dev/null +++ b/base_connaissances/corpus/can-the-camera-automatically-scan-several-monitoring-areas.md @@ -0,0 +1,10 @@ +# Can the camera automatically scan several monitoring areas? + +A motorized scanning concept has been considered, particularly for crack monitoring on large +structures where each monitored area has its own reference points. +However, AIMsight does not currently aim to provide scanning while simultaneously maintaining +total-station-like absolute angular accuracy. +For applications requiring continuous high-accuracy angular scanning, a total station remains the +more appropriate instrument architecture. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/can-two-cameras-be-combined-to-obtain-x-y-and-z-displacement.md b/base_connaissances/corpus/can-two-cameras-be-combined-to-obtain-x-y-and-z-displacement.md new file mode 100644 index 0000000..1dd19fd --- /dev/null +++ b/base_connaissances/corpus/can-two-cameras-be-combined-to-obtain-x-y-and-z-displacement.md @@ -0,0 +1,9 @@ +# Can two cameras be combined to obtain X, Y, and Z displacement? + +Yes. +Two cameras viewing the monitored structure from sufficiently different directions can be +combined to reconstruct three-dimensional displacement. +Measurements are currently available independently from the two systems, and their outputs can +be combined using relatively simple post-processing. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/ce-que-le-client-regarde-dans-les-deplacements.md b/base_connaissances/corpus/ce-que-le-client-regarde-dans-les-deplacements.md new file mode 100644 index 0000000..0f77abe --- /dev/null +++ b/base_connaissances/corpus/ce-que-le-client-regarde-dans-les-deplacements.md @@ -0,0 +1,10 @@ +# Ce que le client regarde dans les déplacements + +- Le client regarde les déplacements horizontaux et verticaux, en mm (la page Time Series de la plateforme). Les erreurs de mesure (Error Value) l'intéressent peu. +- Les erreurs sont traitées en amont : chaque cible a son seuil d'erreur (Error Threshold). Une mesure au-dessus est jugée non valable : elle n'est pas interprétée comme un déplacement et peut être masquée dans les courbes, mais elle reste dans les données livrées. +- Les mouvements normaux reviennent. Une cible bouge avec la météo, la température et le soleil, de façon périodique (jour et nuit) ou saisonnière, puis revient à sa place. La plupart des courbes fluctuent ainsi sans rien révéler. +- Deux choses comptent vraiment pour lui : + - un saut : un décalage soudain de la courbe, qui dure. Un saut qui revient ensuite à la normale est le plus souvent bénin ; la question est sa cause ; + - une tendance : une hausse ou une baisse lente, faite de petits décalages. Elle peut annoncer une dégradation de l'ouvrage ou du chantier (un affaissement, par exemple). + +Source : Savoir métier AIMsight diff --git a/base_connaissances/corpus/does-the-camera-operate-without-a-cloud-connection.md b/base_connaissances/corpus/does-the-camera-operate-without-a-cloud-connection.md new file mode 100644 index 0000000..ffa106d --- /dev/null +++ b/base_connaissances/corpus/does-the-camera-operate-without-a-cloud-connection.md @@ -0,0 +1,14 @@ +# Does the camera operate without a Cloud connection? + +Yes, provided that the station includes a local software licence enabling standalone operation. +With this licence, image acquisition and processing run directly on the station. The local web +interface remains accessible over Ethernet, and measurements can be stored locally without a +connection to AIMsight Cloud. Functions requiring external communication — such as remote +access, data transmission, and Cloud notifications — remain unavailable while the connection is +down. +The station can also be supplied without a standalone local licence. In this configuration, its +operation depends on an active AIMsight Cloud subscription. The applicable licensing model and +the functions available without a Cloud connection are specified in the project quotation or +agreement. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/does-the-system-detect-excessive-camera-instability.md b/base_connaissances/corpus/does-the-system-detect-excessive-camera-instability.md new file mode 100644 index 0000000..117712a --- /dev/null +++ b/base_connaissances/corpus/does-the-system-detect-excessive-camera-instability.md @@ -0,0 +1,10 @@ +# Does the system detect excessive camera instability? + +Yes. +The processed data include an indicator of camera stability based on the history of estimated +camera-angle variations. +Camera-angle changes and, where appropriate, excessive raw pixel movement toward the edge +of a processing region can be used to identify an unstable installation before it affects +measurement quality or availability. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/how-are-targets-with-excessive-recognition-error-handled-in-data-exploration.md b/base_connaissances/corpus/how-are-targets-with-excessive-recognition-error-handled-in-data-exploration.md new file mode 100644 index 0000000..f3ba4c1 --- /dev/null +++ b/base_connaissances/corpus/how-are-targets-with-excessive-recognition-error-handled-in-data-exploration.md @@ -0,0 +1,15 @@ +# How are targets with excessive recognition error handled in Data Exploration? + +The Data Exploration tools can use the Error Value to identify and handle measurements affected +by poor target recognition. +Available processing and visualization options include: +• Highlighting periods or areas where the Error Value is too high. +• Hiding data points whose Error Value exceeds the selected threshold. +• Replacing rejected or hidden data points with interpolated values where appropriate. +• Overriding the default Error Threshold with a user-defined value. +• Applying additional filtering or smoothing, such as a rolling median, to the resulting data +where appropriate. +The original Error Value remains useful for distinguishing actual displacement from periods +where the target was not reliably visible. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/how-can-i-access-the-camera-locally.md b/base_connaissances/corpus/how-can-i-access-the-camera-locally.md new file mode 100644 index 0000000..8233eb6 --- /dev/null +++ b/base_connaissances/corpus/how-can-i-access-the-camera-locally.md @@ -0,0 +1,9 @@ +# How can I access the camera locally? + +The station provides its own web interface. +A computer connected locally to the station through Ethernet can access the interface using a +standard web browser. +Remote access can also be provided through AIMsight’s secure VPN infrastructure when an +Internet connection is available. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/how-can-i-detect-deformation-of-the-reference-network.md b/base_connaissances/corpus/how-can-i-detect-deformation-of-the-reference-network.md new file mode 100644 index 0000000..ac4a6e6 --- /dev/null +++ b/base_connaissances/corpus/how-can-i-detect-deformation-of-the-reference-network.md @@ -0,0 +1,19 @@ +# How can I detect deformation of the reference network? + +Camera-motion estimation provides a reprojection error called sigma0, which is available in the +system metrics. +Sigma0 measures how well the observed displacement of the different reference targets can be +explained by the estimated global camera motion. +An abnormal increase in sigma0 can therefore indicate that the reference network is deforming in +a way that can no longer be explained by simple camera movement. A low value indicates that +the observed movements of the reference targets remain consistent with a common camera +movement. +It is useful for monitoring the consistency and stability of the reference network and can be +used to trigger further investigation if necessary. +Sigma0 and the per-target Error Value provide complementary information: +• Error Value checks whether an individual target is still visible and resembles its reference +image; +• sigma0 checks whether the reference targets remain geometrically consistent with the +estimated camera movement. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/how-can-i-export-the-advanced-diagnostic-metrics.md b/base_connaissances/corpus/how-can-i-export-the-advanced-diagnostic-metrics.md new file mode 100644 index 0000000..fa0f47a --- /dev/null +++ b/base_connaissances/corpus/how-can-i-export-the-advanced-diagnostic-metrics.md @@ -0,0 +1,11 @@ +# How can I export the advanced diagnostic metrics? + +Select the HDF5 (.h5) format in the acquisition schedule. This format can include the complete +set of signals computed by the station, including the displacement results and advanced targetquality metrics such as Error Value, Sharpness, FWHM, Dominance, Peak Intensity, Flux, and +SNR, together with camera-related information. +The other export formats are intentionally simplified. Depending on the selected format and +output, they contain either displacement results only or a reduced set of quality metrics. +Use HDF5 when complete diagnostic traceability or advanced post-processing is required. Use +CSV or Parquet when a smaller and simpler dataset is preferable for routine integration. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/how-can-i-redefine-the-zero-reference-position-used-for-rx-and-ry.md b/base_connaissances/corpus/how-can-i-redefine-the-zero-reference-position-used-for-rx-and-ry.md new file mode 100644 index 0000000..5281f3d --- /dev/null +++ b/base_connaissances/corpus/how-can-i-redefine-the-zero-reference-position-used-for-rx-and-ry.md @@ -0,0 +1,9 @@ +# How can I redefine the zero/reference position used for rx and ry? + +The displacement reference can be redefined by redefining the target/reference patterns. +This establishes a new measurement reference. In the local interface, saving the configuration +again replaces the reference patterns and defines a new zero. When AIMsight Cloud is included, +additional update strategies determine whether reprocessed data restart from zero or retain +trace continuity; see the Cloud-specific question in the Software and licensing section. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/how-do-atmospheric-turbulence-and-heat-shimmer-affect-measurements.md b/base_connaissances/corpus/how-do-atmospheric-turbulence-and-heat-shimmer-affect-measurements.md new file mode 100644 index 0000000..3e258ac --- /dev/null +++ b/base_connaissances/corpus/how-do-atmospheric-turbulence-and-heat-shimmer-affect-measurements.md @@ -0,0 +1,10 @@ +# How do atmospheric turbulence and heat shimmer affect measurements? + +Atmospheric turbulence can produce apparent image motion due to variations in temperature +and humidity along the optical path. This is commonly visible as heat haze or heat shimmer. +AIMsight reduces this effect by combining a series of images, typically approximately 20 to 40 +images, for each measurement. +If this averaging is insufficient, measurements can also be repeated over a longer period and +averaged to further reduce atmospheric noise. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/how-many-points-can-one-aimsight-station-monitor.md b/base_connaissances/corpus/how-many-points-can-one-aimsight-station-monitor.md new file mode 100644 index 0000000..b357e50 --- /dev/null +++ b/base_connaissances/corpus/how-many-points-can-one-aimsight-station-monitor.md @@ -0,0 +1,9 @@ +# How many points can one AIMsight station monitor? + +AIMsight supports multi-point displacement monitoring. +There is no fixed hard limit on the number of tracked points. Existing applications use more than +100 simultaneously tracked points on a single station. +The practical number depends on acquisition frequency, processing-area size, and the required +processing performance. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/how-should-reference-targets-be-selected.md b/base_connaissances/corpus/how-should-reference-targets-be-selected.md new file mode 100644 index 0000000..8fcc902 --- /dev/null +++ b/base_connaissances/corpus/how-should-reference-targets-be-selected.md @@ -0,0 +1,18 @@ +# How should reference targets be selected? + +Where possible, use several reference targets distributed over the image rather than relying on a +single target. +A distributed reference network makes camera-motion estimation more robust and provides +redundancy if an individual target becomes obstructed, damaged, or moves. +Reference targets should preferably: +• be clearly visible; +• provide good image contrast; +• remain visible under the expected illumination conditions; +• be distributed over the monitored image; +• be sufficiently far from the camera where appropriate; +• not all belong to a small local area that could deform as a single block. +When no completely stable point is available, a larger reference network can still be used +because camera-motion estimation is based on a robust fit and its consistency can be monitored +using sigma0. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/is-a-thermal-camera-option-available.md b/base_connaissances/corpus/is-a-thermal-camera-option-available.md new file mode 100644 index 0000000..75f12e1 --- /dev/null +++ b/base_connaissances/corpus/is-a-thermal-camera-option-available.md @@ -0,0 +1,8 @@ +# Is a thermal-camera option available? + +A thermal-camera configuration can be considered for applications requiring it. +Thermal-camera specifications and cost depend on the required resolution, optics, measurement +rate, and application. A project-specific configuration and quotation should therefore be +requested. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/is-dedicated-monitoring-software-available.md b/base_connaissances/corpus/is-dedicated-monitoring-software-available.md new file mode 100644 index 0000000..c633b37 --- /dev/null +++ b/base_connaissances/corpus/is-dedicated-monitoring-software-available.md @@ -0,0 +1,14 @@ +# Is dedicated monitoring software available? + +Yes. +AIMsight offers Cloud-based monitoring software. The station can also be supplied with a local +software licence enabling standalone measurement operation. +The embedded web interface can be accessed: +• locally using Ethernet and a web browser; +• remotely through the secure AIMsight VPN, when the station has an Internet connection and +the remote-access service is enabled. +AIMsight Cloud is a subscription service. It is optional for a station equipped with the standalone +local software licence. A station supplied without that local licence depends on an active +AIMsight Cloud subscription. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/is-periodic-metrological-maintenance-required.md b/base_connaissances/corpus/is-periodic-metrological-maintenance-required.md new file mode 100644 index 0000000..b6a47ab --- /dev/null +++ b/base_connaissances/corpus/is-periodic-metrological-maintenance-required.md @@ -0,0 +1,11 @@ +# Is periodic metrological maintenance required? + +No routine metrological recalibration is currently required as part of normal operation. +A verification procedure can be performed when required to confirm measurement-system +behavior. +AIMsight SA +Route de Cité-Ouest 2 +1196 Gland, Switzerland +info@aimsight.ch + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/is-the-software-web-based-or-desktop-based.md b/base_connaissances/corpus/is-the-software-web-based-or-desktop-based.md new file mode 100644 index 0000000..8d3a823 --- /dev/null +++ b/base_connaissances/corpus/is-the-software-web-based-or-desktop-based.md @@ -0,0 +1,7 @@ +# Is the software web-based or desktop-based? + +The normal station interface and cloud monitoring workflows are web-based. +Additional local or external processing workflows can also be implemented depending on the +project architecture and integration requirements. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/la-batterie-et-l-alimentation-de-la-station.md b/base_connaissances/corpus/la-batterie-et-l-alimentation-de-la-station.md new file mode 100644 index 0000000..59c9686 --- /dev/null +++ b/base_connaissances/corpus/la-batterie-et-l-alimentation-de-la-station.md @@ -0,0 +1,22 @@ +# La batterie et l'alimentation de la station + +Matériel : +- Batterie LiFePO4 de 12,8 V nominal (4 cellules en série), environ 7 ou 21 Ah selon la station. +- Panneau solaire 12 V, ~100 W conseillé, ou secteur. Tension d'entrée maximale : 26 V. +- Sur secteur, la batterie reste connectée et sert d'onduleur. +- Après une décharge profonde (sous 12 V), la station reste éteinte jusqu'à ce que la batterie remonte vers 12,6 V, puis redémarre. +- La station consomme environ 5 W en continu (environ 120 Wh par jour). En cas de déficit, le remède attendu est de réactiver la veille profonde (sleep) entre les mesures ; le mode continu (LED allumées) augmente la consommation. + +Tension et état de charge (tension à vide ; repères approximatifs, qui varient selon la batterie et le chargeur) : +- ≥ 13,6 V : pleine ; au-dessus, c'est le chargeur qui tient la tension. +- 12,9 à 13,4 V : 40 à 90 % ; c'est le plateau, où la tension dit peu de choses sur la charge. +- 12,5 à 12,8 V : 20 à 30 % ; c'est le coude. +- Sous 12,5 V : moins de 20 %, la tension chute vite ; sous 12 V, décharge profonde. + +Ce qu'il faut en retenir : +- La tension instantanée ne dit pas l'état de charge : le jour, le chargeur la tire vers le haut ; sous la consommation, elle est un peu plus basse que la tension à vide. Le meilleur indicateur est le minimum de fin de nuit. +- Sur le plateau, la tension de nuit reste plate entre 30 et 90 % de charge ; elle ne chute qu'au coude, donc tard. +- Une tension d'environ 14 V ou plus dans la journée indique en général que la batterie a été remplie. Les jours nuageux, elle plafonne vers 13,4 V : la batterie charge sans se remplir. +- Une batterie pleine ne garantit rien si l'apport s'arrête : une station débranchée tient environ 15 h (7 Ah) à 46 h (21 Ah) à 5 W en continu. + +Source : Savoir métier AIMsight diff --git a/base_connaissances/corpus/la-chaine-de-mesure-d-ou-vient-une-anomalie.md b/base_connaissances/corpus/la-chaine-de-mesure-d-ou-vient-une-anomalie.md new file mode 100644 index 0000000..919a506 --- /dev/null +++ b/base_connaissances/corpus/la-chaine-de-mesure-d-ou-vient-une-anomalie.md @@ -0,0 +1,25 @@ +# La chaîne de mesure : d'où vient une anomalie + +Une valeur affichée est le bout d'une chaîne. Pour expliquer une anomalie, on cherche l'étage qui a lâché. + +1. La scène : des cibles sur l'ouvrage, et des références autour, supposées fixes. +2. La vue : l'air entre la caméra et les cibles, et ce qui peut passer ou se poser devant. +3. L'image : l'objectif, puis la prise (image classique, ou image différentielle qui combine plusieurs prises pour renforcer le contraste des réflecteurs). +4. La mesure du motif : chaque cible est retrouvée dans l'image, avec son erreur de reconnaissance (Error Value, qui n'est pas une incertitude). Au-dessus du seuil, la mesure est jugée non valable (elle reste dans les données livrées, mais n'est pas interprétée comme un déplacement). +5. La compensation : le mouvement de la caméra (pan, tilt, rotation, échelle) est estimé sur les références, avec son résidu sigma0. +6. La courbe corrigée : la position de la cible une fois retiré le mouvement estimé de la caméra. + +Où chaque cause entre : +- Visibilité réduite (brouillard, pluie, buée) : le retour lumineux baisse sur toute la scène, l'Error Value monte, des mesures sont rejetées, pendant des heures. Ce n'est pas un mouvement. +- Turbulence (air chaud, heat haze) : un bruit rapide sur les courbes, aux heures chaudes. +- Occultation : un objet, des feuilles ou de la neige devant une ou quelques cibles, les voisines intactes ; d'une seule mesure (un passage) à des semaines. +- Cible à problème (mal orientée, sale, décollée) : une seule cible, durablement. +- Dilatation du support ou de l'objectif au soleil, vent, choc : toute l'image bouge ensemble ; la compensation l'absorbe en général. +- Référence cachée ou moins bien vue : la compensation est refaite sans elle ; des points sautent d'un coup, souvent groupés dans une partie de l'image, et reviennent quand la référence revient. +- Référence qui a bougé : les courbes des cibles sont décalées durablement. +- Dilatation thermique de l'ouvrage : des vagues propres à chaque cible, au rythme le plus lent (chauffe lente, refroidissement tardif). +- Mouvement réel de l'ouvrage : une ou plusieurs cibles décalées durablement, alors que les références, la pose de la caméra et la qualité d'image restent bonnes. + +Trois effets thermiques de mouvement se distinguent par leur rythme : l'objectif, le support, l'ouvrage (le plus lent). La turbulence est à part : un bruit, pas un mouvement. + +Source : Savoir métier AIMsight diff --git a/base_connaissances/corpus/le-cycle-thermique-les-vagues-de-la-journee.md b/base_connaissances/corpus/le-cycle-thermique-les-vagues-de-la-journee.md new file mode 100644 index 0000000..e82d104 --- /dev/null +++ b/base_connaissances/corpus/le-cycle-thermique-les-vagues-de-la-journee.md @@ -0,0 +1,8 @@ +# Le cycle thermique : les vagues de la journée + +- Des ouvrages bougent dans la journée par dilatation thermique, et redescendent la nuit par contraction. On voit alors des vagues sur les courbes. Ces vagues sont tout à fait normales. +- Sur les positions brutes, presque toutes les stations montrent une vague de 24 h, toutes les cibles ensemble : c'est la caméra ou son mât qui se courbe avec la chaleur. La compensation par les références enlève cette vague : elle n'apparaît pas sur les courbes corrigées que regarde le client. +- Quand une vague reste sur les courbes corrigées (de l'ordre du millimètre), les cibles bougent vraiment par rapport aux références : dilatation de l'ouvrage, ou compensation incomplète. +- Une vague thermique revient chaque jour à la même position à température égale. Une hausse ou une baisse qui ne revient pas n'est pas une vague thermique. + +Source : Savoir métier AIMsight diff --git a/base_connaissances/corpus/les-familles-d-anomalies-et-ce-qu-elles-veulent-dire-pour-le-client.md b/base_connaissances/corpus/les-familles-d-anomalies-et-ce-qu-elles-veulent-dire-pour-le-client.md new file mode 100644 index 0000000..3d6f685 --- /dev/null +++ b/base_connaissances/corpus/les-familles-d-anomalies-et-ce-qu-elles-veulent-dire-pour-le-client.md @@ -0,0 +1,18 @@ +# Les familles d'anomalies et ce qu'elles veulent dire pour le client + +Une anomalie, c'est ce qui apparaît sur les courbes corrigées : elles bougent (un pic, un saut, une dérive, du bruit) ou elles manquent (un trou). On la range dans une famille selon sa cause. + +- Visibilité (Visibility) : on voit moins bien, une gêne diffuse entre la caméra et la scène. L'image est faible ou floue (pluie, brouillard, buée, lumière, objectif sale), ou elle tremble (turbulence). Pour le client : ne pas croire les courbes sur cette période ; ce n'est pas un mouvement. +- Obstruction : un objet cache une ou quelques cibles, un instant ou longtemps (train, véhicule, engin, plante, neige sur la cible, toile d'araignée). Pour le client : ignorer la courbe des cibles cachées sur cette période. +- Déplacement thermique (Thermal displacement) : l'ouvrage, ou la caméra et son support, bougent avec la température, et reviennent à la même position à température égale. Pour le client : normal, rien à faire. +- Déplacement (Displacement) : un saut qui dure, une dérive lente, ou un changement des courbes sans cause établie. Pour le client : à vérifier (regarder les images, surveiller), sans alarmer ni rien cacher. +- Cible à problème (Target issue) : une cible rejetée presque toujours, mal orientée, mal installée, mal configurée ou sale. Pour le client : intervenir sur la cible ; ignorer sa courbe en attendant. +- Pas de données (No data) : aucune mesure pour aucune cible (acquisition, alimentation, transmission). Pour le client : les courbes manquent sur la période ; la cause dit s'il faut agir. + +Quelques frontières : +- Toute la scène gênée, c'est Visibilité ; quelques cibles cachées par un objet, le reste intact, c'est Obstruction. +- Un saut puis un retour prend la famille de sa cause, vue sur les images (un véhicule qui passe : Obstruction ; le reflet du soleil sur la scène : Visibilité). Sans cause établie : Déplacement. +- Un trou aux mêmes minutes sur plusieurs stations vient d'une cause commune (transmission ou réception), pas d'une coupure de la station. +- Une configuration changée (cibles déplacées, réglage) explique le saut qui en vient : ce n'est pas un mouvement de l'ouvrage. + +Source : Savoir métier AIMsight diff --git a/base_connaissances/corpus/les-metriques-systeme-de-la-station.md b/base_connaissances/corpus/les-metriques-systeme-de-la-station.md new file mode 100644 index 0000000..e6b10d9 --- /dev/null +++ b/base_connaissances/corpus/les-metriques-systeme-de-la-station.md @@ -0,0 +1,17 @@ +# Les métriques système de la station + +AIMsight suit la santé de chaque station par des métriques système. Elles servent au support pour diagnostiquer l'alimentation ou une coupure ; le client n'y a pas forcément accès, il ne faut donc pas le renvoyer vers elles. Elles donnent, en moyennes horaires (une valeur vide signifie qu'il n'y a pas de mesure) : +- BusVoltage (V) : tension du bus, proche de la tension de la batterie. +- BusCurrent (mA) : courant consommé par la station. +- Power (mW) : puissance consommée. +- ShuntVoltage (mV) : tension aux bornes du shunt de mesure (courant × 0,1 Ω). +- sensor_*_deg_c (°C) : températures de la carte de calcul (selon la version de la station). + +À savoir : +- Power, BusCurrent et ShuntVoltage sont une seule et même mesure : la consommation de la station. Le courant augmente quand la tension baisse, alors que la puissance reste constante ; pour la consommation, raisonner en puissance. +- L'apport d'énergie (panneau ou secteur) n'est pas mesuré : on ne le voit qu'à travers la réaction de la batterie. +- La température de la carte suit l'ensoleillement (amplitude faible les jours nuageux) et chute quand la station est éteinte, puisque son propre échauffement (~5 W) s'arrête. +- Certaines stations donnent aussi une tension corrigée de la résistance interne, la pente de la tension, et un état et un pourcentage de charge estimés. +- Les stations n'ont pas toutes la même version du logiciel embarqué : noms et champs peuvent changer d'une station à l'autre. + +Source : Savoir métier AIMsight diff --git a/base_connaissances/corpus/les-trous-pourquoi-des-mesures-manquent.md b/base_connaissances/corpus/les-trous-pourquoi-des-mesures-manquent.md new file mode 100644 index 0000000..b837a7d --- /dev/null +++ b/base_connaissances/corpus/les-trous-pourquoi-des-mesures-manquent.md @@ -0,0 +1,12 @@ +# Les trous : pourquoi des mesures manquent + +- Un trou n'est pas forcément une coupure. Acquisition, transmission, réception et affichage sont des étapes distinctes. + - En fin de période, des valeurs vides peuvent n'être qu'un retard de synchronisation. + - En début de période, des valeurs vides précèdent simplement la première mesure. + - Des trous simultanés sur plusieurs stations pointent vers une cause commune hors de la station (transmission ou réception). + - Un trou entouré d'une tension normale n'est pas un problème d'énergie. +- Une coupure d'alimentation laisse une signature : la tension de la batterie est basse (sous ~12,8 V) juste avant ou juste après le trou, et la température de la station chute pendant le trou, plus qu'aux mêmes heures les autres nuits. +- Des mesures jugées non valables (au-dessus du seuil d'erreur) peuvent aussi laisser des trous dans les courbes, mais seulement sur ces cibles ; elles restent dans les données livrées, et leur cause est celle de l'erreur (visibilité, obstacle, cible à problème). +- Une valeur NaN ou inf dans un export compte comme une absence de mesure. + +Source : Savoir métier AIMsight diff --git a/base_connaissances/corpus/my-aimsight-camera-does-not-start-what-should-i-check.md b/base_connaissances/corpus/my-aimsight-camera-does-not-start-what-should-i-check.md new file mode 100644 index 0000000..9605a36 --- /dev/null +++ b/base_connaissances/corpus/my-aimsight-camera-does-not-start-what-should-i-check.md @@ -0,0 +1,17 @@ +# My AIMsight camera does not start. What should I check? + +First check that the internal battery is connected. Depending on transport or storage conditions, +the battery may have been disconnected and must be connected before commissioning. +Then connect the external power supply and check the charging / power LED. +If the LED does not turn on: +• check that the external power supply is connected; +• check the power connectors and cabling; +• for a mains-powered installation, verify that the power supply is energized; +• for a solar-powered installation, verify the solar-panel connection and that sufficient +charging voltage is available. +If the unit appears to be powered but cannot be reached remotely, try connecting to it locally +over Ethernet. This helps distinguish a startup or power problem from a 4G or remoteconnectivity problem. +If there is no charging indication and the system remains unreachable after checking the power +supply and battery connection, contact AIMsight support. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/my-exported-csv-file-does-not-contain-a-timestamp-what-should-i-do.md b/base_connaissances/corpus/my-exported-csv-file-does-not-contain-a-timestamp-what-should-i-do.md new file mode 100644 index 0000000..36807a4 --- /dev/null +++ b/base_connaissances/corpus/my-exported-csv-file-does-not-contain-a-timestamp-what-should-i-do.md @@ -0,0 +1,11 @@ +# My exported CSV file does not contain a timestamp. What should I do? + +Time information is required for most external data-processing workflows. +If the selected CSV export does not contain a timestamp, check the export type and +configuration being used. +Where required, the export configuration can be adapted so that each measurement contains an +explicit timestamp suitable for external processing. +For data integration, the timestamp convention should always be defined explicitly rather than +inferred from the file creation time. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/my-measurements-suddenly-become-noisy-or-invalid-what-should-i-check.md b/base_connaissances/corpus/my-measurements-suddenly-become-noisy-or-invalid-what-should-i-check.md new file mode 100644 index 0000000..ee331a0 --- /dev/null +++ b/base_connaissances/corpus/my-measurements-suddenly-become-noisy-or-invalid-what-should-i-check.md @@ -0,0 +1,37 @@ +# My measurements suddenly become noisy or invalid. What should I check? + +Useful checks include: +• whether the target remains visible and inside its processing area; +• water, condensation, dirt, or contamination on the target or camera window; +• partial or complete target obstruction; +• significant changes in illumination; +• atmospheric turbulence or heat shimmer; +• excessive camera movement; and +• sigma0 if reference targets are being used. +The diagnostic signals can help narrow down the likely cause: +• An increasing Error Value indicates that the target image no longer matches its reference +reliably. This can result from obstruction, changed appearance, poor visibility, or incorrect +registration. +• Decreasing Sharpness together with increasing FWHM suggests that the target image is +becoming more diffuse, for example because of defocus, vibration, motion blur, or +atmospheric turbulence. +• Decreasing Peak Intensity, Flux, and SNR suggests reduced illumination, partial +obstruction, contamination, reflector misalignment, or generally poorer target visibility. +• Increasing Dominance indicates that another bright feature is competing with the tracked +reflector and that the risk of selecting the wrong image feature is increasing. +• Similar apparent movement across several targets, accompanied by a change in Camera +Movement, points toward movement or instability of the camera support. +• An increase in sigma0 indicates that the reference targets are becoming less consistent with +a single global camera movement and may indicate deformation of the reference network. +The corresponding camera image remains essential for confirming the interpretation. When +AIMsight Cloud and image archiving are enabled, the image associated with a selected +measurement or period can be opened directly from the history view. The image and the trends +in Error Value, Sharpness, FWHM, Dominance, Peak Intensity, Flux, SNR, Camera Movement, +and sigma0 together provide the most effective way to distinguish between: +• a visibility or target-recognition problem; +• optical degradation or atmospheric disturbance; +• camera instability; +• deformation of the reference network; and +• actual structural movement. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/one-target-is-no-longer-being-measured-what-should-i-check.md b/base_connaissances/corpus/one-target-is-no-longer-being-measured-what-should-i-check.md new file mode 100644 index 0000000..baf58f6 --- /dev/null +++ b/base_connaissances/corpus/one-target-is-no-longer-being-measured-what-should-i-check.md @@ -0,0 +1,30 @@ +# One target is no longer being measured. What should I check? + +First inspect the corresponding camera image and the target’s Error Value. +Check: +• whether the target is still visible; +• whether the target is still inside its processing area; +• whether the Error Value has increased above the configured Error Threshold; +• whether the target is partially or completely obstructed; +• whether the target is dirty, damaged, or covered by water, dust, snow, vegetation, or +another object; +• whether a reflective target or prism has changed orientation; +• whether illumination conditions have changed significantly; +• image focus and exposure; +• whether the camera itself has moved significantly; +• whether the physical target has undergone a displacement larger than the configured +processing area. +If several targets become invalid simultaneously, also check: +• camera movement; +• focus or contamination of the camera window; +• illumination conditions; +• communication with the camera; +• the reference-network fit and sigma0. +If the Error Value exceeds the threshold, the measurement is normally rejected rather than +interpreted as a valid displacement. +The current image, the target-recognition metrics, Camera Movement, and sigma0 are generally +the fastest way to distinguish an optical or visibility problem, camera instability, referencenetwork deformation, and an actual displacement. When AIMsight Cloud is included, a +measurement can be opened together with its corresponding archived image, making it easier to +identify the cause of an abnormal value without first retrieving image files separately. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/pieges-de-lecture-des-donnees-de-la-station.md b/base_connaissances/corpus/pieges-de-lecture-des-donnees-de-la-station.md new file mode 100644 index 0000000..56a8522 --- /dev/null +++ b/base_connaissances/corpus/pieges-de-lecture-des-donnees-de-la-station.md @@ -0,0 +1,9 @@ +# Pièges de lecture des données de la station + +- Les niveaux de tension ne se transposent pas d'une station à l'autre : deux stations en bonne santé peuvent avoir des nuits à 12,9 V et à 13,15 V. Le niveau moyen vaut ~14,25 V sur secteur et ~13,4 V en solaire. Comparer une station à son propre passé. +- Le cycle jour/nuit domine : une période d'observation doit couvrir un nombre entier de jours. Sur trois jours, deux jours nuageux font baisser une station saine autant qu'un vrai déficit. +- La fin de nuit porte le bilan de la veille : le minimum du matin résulte de la charge du jour précédent et de la nuit. Pour juger la charge d'un jour, lire la fin de nuit du lendemain. +- Pendant une coupure, ce sont justement les valeurs les plus basses qui manquent : toute moyenne est alors biaisée vers le haut. +- Les exports ne viennent pas tous de la même version du logiciel : vérifier les métriques présentes avant de comparer deux stations. + +Source : Savoir métier AIMsight diff --git a/base_connaissances/corpus/station-guide-access-modes.md b/base_connaissances/corpus/station-guide-access-modes.md new file mode 100644 index 0000000..62f814a --- /dev/null +++ b/base_connaissances/corpus/station-guide-access-modes.md @@ -0,0 +1,39 @@ +# Station Guide — Access Modes + +The AIMsight station provides three complementary access modes: +• Local access to the station: when the station includes a standalone local software licence, +a computer connected directly to the station by Ethernet, or connected to the same local +network, can access the web interface hosted on the station. This mode does not require an +Internet connection or an AIMsight Cloud subscription. Acquisition, image processing, and +local data storage remain fully autonomous. +To connect directly, use the supplied Ethernet cable and open the station interface in a web +browser. The system has been tested with Mozilla Firefox, Microsoft Edge, and Google +Chrome. By default, the station uses the static IP address 192.168.1.2. Enter this address in +the browser address bar. If the station cannot be reached, refer to the Network Settings +section (see page 21). +• Remote access to the station interface: when the station has an Internet connection and +the remote-access service is enabled, AIMsight can provide secure remote access to the +station’s local web interface. The user sees the same interface and functions as when +connected locally and can, for example, check the station status, adjust its configuration, or +review data stored on the station. +The station establishes an encrypted connection to a secure gateway managed by +AIMsight. This normally avoids the need for a public IP address or for incoming ports to be +opened on the customer’s network. Because this remains a direct connection to the station, +the station must be powered on and connected to the Internet. This service does not by +itself create a Cloud archive: the information being viewed remains stored on the station. +• AIMsight Cloud: when this optional service is enabled, the station transfers its +measurements and, depending on the configuration, associated images and quality metrics +to the AIMsight platform. Authorized users can then access the project data through a web +browser without connecting directly to the station. +AIMsight Cloud can centralize and archive measurements, provide access to their history +and associated images, display target-recognition quality metrics, and provide alarm, +visualization, and post-processing tools. Data that have already been transferred remain +accessible if the station is temporarily offline. AIMsight Cloud is typically provided as a +subscription service. +NOTE +Standalone operation requires a local software licence. The station can also be supplied +without this licence; in that configuration, its operation depends on an active AIMsight Cloud +subscription. The applicable licensing model and the functions available without a Cloud +connection are specified in the project quotation or agreement. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-acquisition-length.md b/base_connaissances/corpus/station-guide-acquisition-length.md new file mode 100644 index 0000000..5da46a3 --- /dev/null +++ b/base_connaissances/corpus/station-guide-acquisition-length.md @@ -0,0 +1,5 @@ +# Station Guide — Acquisition Length + +For Time Series acquisitions, Parameter Mode provides two configuration methods. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-acquisition-schedules.md b/base_connaissances/corpus/station-guide-acquisition-schedules.md new file mode 100644 index 0000000..13ee844 --- /dev/null +++ b/base_connaissances/corpus/station-guide-acquisition-schedules.md @@ -0,0 +1,10 @@ +# Station Guide — Acquisition Schedules + +The Schedules page allows acquisitions to be triggered automatically without operator +intervention. Each schedule defines when an acquisition starts, which acquisition and camera +parameters are used, which target preset is processed, and where the resulting data is stored or +transmitted. +Saved schedules run automatically while the station is powered and the required resources, such +as storage capacity and network connectivity, are available. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-acquisition-type.md b/base_connaissances/corpus/station-guide-acquisition-type.md new file mode 100644 index 0000000..d0f9b40 --- /dev/null +++ b/base_connaissances/corpus/station-guide-acquisition-type.md @@ -0,0 +1,8 @@ +# Station Guide — Acquisition Type + +• Time Series: records a sequence of measurements for a defined duration or number of +samples. Use this mode to track displacement over time. +• Single Image: captures one image at each trigger. Use this mode for periodic visual +documentation or image-based inspection. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-available-signals-and-diagnostic-metrics.md b/base_connaissances/corpus/station-guide-available-signals-and-diagnostic-metrics.md new file mode 100644 index 0000000..345e39b --- /dev/null +++ b/base_connaissances/corpus/station-guide-available-signals-and-diagnostic-metrics.md @@ -0,0 +1,22 @@ +# Station Guide — Available Signals and Diagnostic Metrics + +The Data Exploration page provides access to the measured displacements together with the +complete set of diagnostic signals that can be computed by the station. These signals describe +image quality, target visibility, registration reliability, and estimated camera movement. +The information button next to the signal selector provides a short description of each available +signal. +The advanced metrics can also be exported by scheduled acquisitions when the HDF5 format is +selected. Other export formats are intentionally simplified and contain either displacement results +only or a reduced set of quality metrics. +The following sections provide additional guidance on the practical interpretation of each signal. +NOTE +The diagnostic metrics are most useful when interpreted as trends and in combination with +the corresponding camera images. A change in one metric does not necessarily indicate a +measurement failure, but several concurrent changes can help identify the likely cause of an +abnormal measurement. +When the optional AIMsight Cloud service and image archiving are enabled, the image +corresponding to a selected point or period in the measurement history can be opened +directly from the visualization interface. This makes it possible to compare displacement +signals, quality metrics, and the actual visual conditions at the time of the measurement. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-camera-management-panel.md b/base_connaissances/corpus/station-guide-camera-management-panel.md new file mode 100644 index 0000000..e8d32b2 --- /dev/null +++ b/base_connaissances/corpus/station-guide-camera-management-panel.md @@ -0,0 +1,27 @@ +# Station Guide — Camera Management Panel + +You can display the “Camera Management” side panel from any page by clicking the camera +icon in the top-right corner of the interface. +The camera button and the top navigation bar change color to indicate the acquisition status: +• grey when idle +• green during an acquisition +Live View images are not considered an acquisition. +1. Live processing toggle: enables image acquisition at the specified frame rate and the +processing of the raw images into displacement measurements +2. Framerate slider: sets the camera acquisition frame rate +3. FPS Production: displays the current image-acquisition rate +4. FPS Processing: displays the processing rate in each thread. For continuous monitoring, +verify that processing is fast enough to keep up with image capture. +5. Processing Queue: displays the number of image blocks waiting to be processed. For +continuous monitoring, the frame rate should be kept low enough for the queue to remain +close to empty. +6. Continuous acquisition mode: can be enabled for maximum frame-rate stability, at the +expense of battery life +7. RTSP Stream: streams the live video feed on port 8554 +NOTE +For short burst-mode measurements, the system can capture data at a much higher frame +rate than the real-time processing rate. In such cases, the maximum measurement duration +without data loss is limited by the queue size and is typically on the order of 60 seconds. +The actual duration should always be verified with the final settings. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-camera-movement.md b/base_connaissances/corpus/station-guide-camera-movement.md new file mode 100644 index 0000000..c7f3048 --- /dev/null +++ b/base_connaissances/corpus/station-guide-camera-movement.md @@ -0,0 +1,21 @@ +# Station Guide — Camera Movement + +“Camera Movement” represents the estimated global movement of the camera obtained from +the reference targets. +The reference network is used to identify movement common to the observed scene, such as +apparent translation, rotation, or scale change caused by movement of the camera or its support. +When camera-motion correction is enabled, this common movement is removed from the +reported relative target displacements. +Practical use: Camera Movement helps distinguish actual structural displacement from apparent +displacement caused by movement of the monitoring station itself. +It is also useful for identifying: +• movement or instability of the camera support; +• disturbances affecting the complete field of view; +• significant thermal or mechanical changes in the mounting system; and +• situations where camera-motion correction contributes substantially to the final +displacement result. +The reliability of this correction depends on the number, distribution, visibility, and measurement +quality of the available reference targets. Camera Movement should therefore be interpreted +together with the individual target-quality metrics. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-camera-operation.md b/base_connaissances/corpus/station-guide-camera-operation.md new file mode 100644 index 0000000..17250b8 --- /dev/null +++ b/base_connaissances/corpus/station-guide-camera-operation.md @@ -0,0 +1,6 @@ +# Station Guide — Camera Operation + +Turn the camera on by pressing the power button on the back of the camera. Once the system is +running, the power button lights up blue. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-camera-parameters.md b/base_connaissances/corpus/station-guide-camera-parameters.md new file mode 100644 index 0000000..29dac78 --- /dev/null +++ b/base_connaissances/corpus/station-guide-camera-parameters.md @@ -0,0 +1,15 @@ +# Station Guide — Camera Parameters + +• Exposure (us): exposure time in microseconds; for example, 1000 corresponds to 1 ms. +• Stacking: number of images combined to produce one result, particularly in Differential +mode. Increasing stacking can improve contrast and detection range, but increases the time +required for each measurement and reduces the effective measurement rate. +• Gain (dB): electronic amplification of the camera signal. Higher gain can brighten low-light +images but also increases image noise. +• Continuous Mode: activated by switching “keep LEDs on during acquisition” on. Enable this +mode for maximum frame-rate and frame-rate stability, at the expense of battery life / +increased power consumption. It is not compatible with differential imaging. +Scheduled parameters may temporarily override parameters used for manual acquisition or live +viewing. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-cellular-apn-configuration.md b/base_connaissances/corpus/station-guide-cellular-apn-configuration.md new file mode 100644 index 0000000..e94e3c8 --- /dev/null +++ b/base_connaissances/corpus/station-guide-cellular-apn-configuration.md @@ -0,0 +1,8 @@ +# Station Guide — Cellular APN Configuration + +The APN is supplied by the mobile-network operator or SIM-card provider; it is not specific to +the AIMsight station. Enter the operator’s APN in the Cellular Network section and click Apply +Network Settings. If the APN is unknown, request it directly from the operator. After applying the +settings, wait for the Link status to change to Up. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-charging.md b/base_connaissances/corpus/station-guide-charging.md new file mode 100644 index 0000000..36a1c67 --- /dev/null +++ b/base_connaissances/corpus/station-guide-charging.md @@ -0,0 +1,32 @@ +# Station Guide — Charging + +CAUTION +The system tolerates a maximum input voltage of 26 V on both the power-supply connector +and the optional passive PoE input. Never connect a standard IEEE PoE source (802.3af, +802.3at or 802.3bt), as the standard PoE voltages of 48 V and above may damage the +charge controller. +CAUTION +The centre pin of the barrel connector is positive. If you are not using an AIMsight-supplied +power solution, always verify the connector polarity before connection, especially when +using third-party adapters such solar panels with MC4 connectors or adapters. +For mains-powered operation, connect the supplied power supply to an electrical outlet, then +connect it to the camera. This operating mode is recommended for charging the battery between +mobile deployments or when power is available at the monitoring site. In this configuration, the +battery remains connected and acts as an internal backup power source (UPS) in case of a +temporary power interruption. +For autonomous field operation, the camera can be connected to a solar panel. We recommend +using a standard 12 V solar panel; in most cases, a generic 100 W panel provides sufficient +charging capacity. Install the panel in a location with good sun exposure and orient it +appropriately for the site conditions. +The battery charges automatically whenever a suitable external power source is connected. +Charging performance depends on the available input power, battery state of charge, and +ambient conditions. For reliable operation, ensure that the external power source remains within +the specified voltage range and is capable of supplying adequate current. +NOTE +After a deep discharge (battery voltage below 12 V), the camera may not restart immediately. +To prevent repeated restart attempts caused by an insufficient charge level, the system +remains off until the battery voltage reaches approximately 12.6 V before powering up again. +While charging, verify that the charge-status LED is red. Once the battery has recovered to +the required voltage, the system will start automatically, provided that it is switched on. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-choosing-between-single-and-differential-acquisition.md b/base_connaissances/corpus/station-guide-choosing-between-single-and-differential-acquisition.md new file mode 100644 index 0000000..82eb370 --- /dev/null +++ b/base_connaissances/corpus/station-guide-choosing-between-single-and-differential-acquisition.md @@ -0,0 +1,8 @@ +# Station Guide — Choosing Between Single and Differential Acquisition + +Use Single with infrared light for dynamic measurements where acquisition speed is important. +Use Differential for quasi-static monitoring when increased contrast and robustness are more +important than measurement rate. Differential acquisition combines multiple images; increasing +Stacking generally improves contrast and range but lowers the effective acquisition frequency. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-contrast-enhanced-overlay-adjustment.md b/base_connaissances/corpus/station-guide-contrast-enhanced-overlay-adjustment.md new file mode 100644 index 0000000..78d57de --- /dev/null +++ b/base_connaissances/corpus/station-guide-contrast-enhanced-overlay-adjustment.md @@ -0,0 +1,13 @@ +# Station Guide — Contrast-enhanced Overlay Adjustment + +A brightness-range slider below the image controls which pixels of the contrast-enhanced layer +remain visible: +• moving the slider to the left retains more pixels and can reveal relatively weak reflectors; +• moving it to the right progressively retains only the brightest pixels, helping isolate the +strongest reflectors. At the extreme setting, only a very small fraction of the brightest pixels +may remain visible. +Adjustment may be necessary because apparent reflector brightness depends on target type, +orientation, distance, and lighting conditions. The setting affects display only and has no effect +on target definition or processing. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-creating-a-schedule.md b/base_connaissances/corpus/station-guide-creating-a-schedule.md new file mode 100644 index 0000000..f334953 --- /dev/null +++ b/base_connaissances/corpus/station-guide-creating-a-schedule.md @@ -0,0 +1,14 @@ +# Station Guide — Creating a Schedule + +Click New Schedule and configure the following fields: +• Schedule Name: a descriptive name, for example Hourly Monitoring. +• Trigger Type: the rule that determines when the acquisition starts. +• Acquisition Type: the type of acquisition to perform. +• Parameter Mode: the method used to define acquisition length and sample count. +• Image Type: the image-acquisition mode. +• Pattern Preset: the target configuration to process. +• Camera Parameters: the optical and acquisition parameters applied by the schedule. +• Output Options: the storage and transmission destinations. +Click Save Schedule after completing the configuration. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-data-exploration-page.md b/base_connaissances/corpus/station-guide-data-exploration-page.md new file mode 100644 index 0000000..b0b4c70 --- /dev/null +++ b/base_connaissances/corpus/station-guide-data-exploration-page.md @@ -0,0 +1,29 @@ +# Station Guide — Data Exploration Page + +This page is used to display and review stored measurements. The table lists the measurement +databases available in the camera’s local storage. +In addition to the principal displacement signals, Data Exploration provides access to diagnostic +metrics describing target visibility, image quality, registration quality, and camera movement. +Together with the corresponding camera images, these signals provide powerful tools for +understanding abnormal measurements and assessing measurement reliability. +Select Acquisition: choose the acquisition you want to review. Each acquisition is organized +chronologically, from oldest to most recent, based on the recording date and time. +To retrieve acquisitions from a specific day and around the same period, expand the drop-down +menu. The collapsible panel displays all acquisitions performed during that session and provides +access to the full list of recordings for more precise selection and review. +Example of selecting an acquisition +The plot options section has two categories: +• Filters: remove camera motion from the measurement, remove the offset from the data +points, or apply a rolling median +• Obstruction handling: highlight areas where the error value is too high, hide data points +whose error value exceeds the threshold, replace hidden data points with interpolated +values, and override the error threshold with a user-defined value +Selected Plot Options +Measurement results for the acquisition dated 12.03.2026 +The “Update !” button queries the selected database and displays the latest data. This can be +automated by enabling the “Auto Update” switch. +When “Auto Update” is enabled, the latest measurement data is queried and plotted periodically. +The refresh period is defined by the “Interval” setting, in seconds. +The “Time Range” setting determines the time window queried and displayed in the chart. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-demo-kit-contents.md b/base_connaissances/corpus/station-guide-demo-kit-contents.md new file mode 100644 index 0000000..dc85cb4 --- /dev/null +++ b/base_connaissances/corpus/station-guide-demo-kit-contents.md @@ -0,0 +1,9 @@ +# Station Guide — Demo Kit Contents + +1. Monitoring Station +2. Monitoring prisms (for long-distance measurements, typically from 20 m to more than 100 +m) +3. Adhesive reflectors (for measurements in the 1 m to 20 m range) +4. Power supply + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-disk.md b/base_connaissances/corpus/station-guide-disk.md new file mode 100644 index 0000000..1a1a6df --- /dev/null +++ b/base_connaissances/corpus/station-guide-disk.md @@ -0,0 +1,6 @@ +# Station Guide — Disk + +Enable Disk to retain the acquisition in the station’s internal storage. Monitor available capacity, +especially for frequent schedules, long time series, or image-heavy acquisitions. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-dominance.md b/base_connaissances/corpus/station-guide-dominance.md new file mode 100644 index 0000000..88be142 --- /dev/null +++ b/base_connaissances/corpus/station-guide-dominance.md @@ -0,0 +1,18 @@ +# Station Guide — Dominance + +“Dominance” indicates whether the tracked reflector remains clearly brighter than the other +bright features present in its processing region. +Values close to 0 indicate that the tracked target is clearly dominant. Values approaching 1 +indicate that another bright feature is becoming comparable with the tracked target. +Practical use: A rising Dominance value can indicate: +• another reflector entering the tracking region; +• a reflection or another bright feature becoming significant; +• the tracked target becoming weaker relative to an existing secondary feature; or +• an increased risk of the registration algorithm selecting the wrong image feature. +Dominance should therefore be interpreted as an indication of potential competition between +image features rather than simply as the brightness of a second object. +It is particularly useful when interpreted together with the Error Value and SNR. A high +Dominance value accompanied by increasing registration error or decreasing SNR indicates +increasingly difficult tracking conditions. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-error-value.md b/base_connaissances/corpus/station-guide-error-value.md new file mode 100644 index 0000000..51f463f --- /dev/null +++ b/base_connaissances/corpus/station-guide-error-value.md @@ -0,0 +1,20 @@ +# Station Guide — Error Value + +The “Error Value” measures how well the current image of the tracked target matches its +reference image after compensating for the measured displacement. +Values close to 0 indicate good agreement with the reference. Increasing values indicate that the +current target image differs increasingly from the image used as its reference. +Practical use: This is the main general-purpose registration-quality indicator. An increase can be +caused by: +• partial or complete obstruction of the target; +• poor target visibility; +• blur or atmospheric disturbance; +• changes in illumination or target appearance; +• loss of the target; or +• incorrect image registration. +Because several different phenomena can increase the Error Value, the other image-quality +statistics are useful for identifying the likely cause. +The obstruction filters use this indicator to reject measurements exceeding the configured “Error +Threshold”. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-exporting-graphs.md b/base_connaissances/corpus/station-guide-exporting-graphs.md new file mode 100644 index 0000000..f9054ea --- /dev/null +++ b/base_connaissances/corpus/station-guide-exporting-graphs.md @@ -0,0 +1,6 @@ +# Station Guide — Exporting Graphs + +Click the download or disk icon on the left side of the toolbar to save the current graph as a PNG +image. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-exposure-and-image-preparation.md b/base_connaissances/corpus/station-guide-exposure-and-image-preparation.md new file mode 100644 index 0000000..8faf5c5 --- /dev/null +++ b/base_connaissances/corpus/station-guide-exposure-and-image-preparation.md @@ -0,0 +1,22 @@ +# Station Guide — Exposure and Image Preparation + +• Exposure: Aim for high contrast in the marker or reflector regions. Ideally, the reflector +images should be bright, with brightness values above about 200 when hovering over them, +and surrounded by a dark background. This is usually achieved with short exposure times, +typically in the 0.1 ms to 10 ms range. When in doubt, use a shorter exposure time. +• Plot brightness slider: adjusts only the display brightness of the image plot to help you +assess exposure. It does not change the actual camera exposure time. +• Recapture: clicking “Recapture” triggers a new image acquisition using the latest settings +and updates the displayed image-processing zones and their names. +• Image Type: for dynamic acquisitions using reflective targets as position markers, select +“Single with infrared light”. The other options are mainly intended to optimize image +acquisition in quasi-static monitoring scenarios. The differential image shows a contrastenhanced view of the reflectors in the scene and is used by the displacement-measurement +algorithms by default. +“Single with infrared light” captures one infrared-illuminated image per measurement and is +best suited to dynamic measurements. “Differential” combines several images to increase target +contrast and improve quasi-static tracking. In difficult lighting conditions or with targets that are +not sufficiently reflective, use Differential mode with a higher Stacking value, typically between +20 and 40. Higher stacking improves detection range but reduces the effective measurement +rate. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-flux.md b/base_connaissances/corpus/station-guide-flux.md new file mode 100644 index 0000000..3a21f05 --- /dev/null +++ b/base_connaissances/corpus/station-guide-flux.md @@ -0,0 +1,22 @@ +# Station Guide — Flux + +“Flux” represents the total target signal measured within the target region after compensating for +the estimated image background. +Unlike Peak Intensity, Flux uses information from multiple pixels and is therefore less sensitive to +variations affecting only the brightest pixel. +Practical use: Flux is useful for following gradual changes in the amount of light received from +the target. +A decreasing trend can be caused by: +• weaker illumination; +• contamination of the reflector or optical path; +• gradual reflector degradation; +• partial obstruction; +• target misalignment; or +• reduced target visibility. +Flux can therefore reveal progressive changes before they become severe enough to cause +registration failure. +It should nevertheless be interpreted as a target-signal indicator rather than as a direct +measurement of reflector reflectivity, since illumination and acquisition conditions also influence +it. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-fps-duration.md b/base_connaissances/corpus/station-guide-fps-duration.md new file mode 100644 index 0000000..1650c37 --- /dev/null +++ b/base_connaissances/corpus/station-guide-fps-duration.md @@ -0,0 +1,10 @@ +# Station Guide — FPS + Duration + +• FPS: requested acquisition frequency in images or measurements per second. +• Duration (seconds): total acquisition duration in seconds. +For example, 10 FPS for 5 seconds requests approximately 50 images or measurement samples. +The actual rate must remain compatible with the processing capacity of the station. For recurring +schedules, verify that processing does not accumulate and that an acquisition can finish before +the next trigger. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-ftp.md b/base_connaissances/corpus/station-guide-ftp.md new file mode 100644 index 0000000..c9567f8 --- /dev/null +++ b/base_connaissances/corpus/station-guide-ftp.md @@ -0,0 +1,6 @@ +# Station Guide — FTP + +Enable FTP to upload results automatically to the FTP or SFTP server configured in System +Settings. Upload requires a valid server configuration and an active network connection. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-fwhm-px.md b/base_connaissances/corpus/station-guide-fwhm-px.md new file mode 100644 index 0000000..dc0cd49 --- /dev/null +++ b/base_connaissances/corpus/station-guide-fwhm-px.md @@ -0,0 +1,19 @@ +# Station Guide — FWHM [px] + +“FWHM” provides an estimate of the apparent width of the target image, expressed in pixels. +A compact, well-focused reflector generally has a smaller apparent width. A blurred or spread +target produces a larger value. +Practical use: An increasing FWHM trend can indicate: +• progressive defocus; +• atmospheric turbulence; +• motion blur; +• vibration; or +• another form of optical degradation. +FWHM complements Sharpness by providing a more intuitive measure of image spreading in +pixel units. It is particularly useful for following gradual changes in focus or atmospheric image +quality. +Because the width is estimated within the target processing region, it should primarily be +interpreted as a trend rather than as an exact physical measurement of the optical point-spread +function. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-image-display-and-reflector-identification.md b/base_connaissances/corpus/station-guide-image-display-and-reflector-identification.md new file mode 100644 index 0000000..724f1c6 --- /dev/null +++ b/base_connaissances/corpus/station-guide-image-display-and-reflector-identification.md @@ -0,0 +1,7 @@ +# Station Guide — Image Display and Reflector Identification + +Depending on the selected image type and the installed software version, the targetconfiguration graph may display the current monochrome image together with a contrastenhanced representation of reflective areas. This overlay helps identify and position tracking +zones around reflective tape, stickers, or prisms. It is a visual aid only: changing the overlay does +not change the geometry of the tracking zone or the reference pattern that is saved. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-image-mode-and-target-preset.md b/base_connaissances/corpus/station-guide-image-mode-and-target-preset.md new file mode 100644 index 0000000..46926a9 --- /dev/null +++ b/base_connaissances/corpus/station-guide-image-mode-and-target-preset.md @@ -0,0 +1,15 @@ +# Station Guide — Image Mode and Target Preset + +• Single with infrared light: captures one infrared-illuminated image per measurement and is +generally suited to dynamic measurements requiring a higher acquisition rate. +• Differential: combines multiple images to improve the contrast of reflective targets and is +generally suited to quasi-static monitoring or difficult detection conditions. +Pattern Preset selects the target configuration used to calculate displacement. When (use active +preset) is selected, the schedule uses the preset active at execution time. A later change to the +active preset may therefore change which targets the schedule processes. Select a named +preset when the schedule must always use a fixed target configuration. +CAUTION +Before enabling an automatic schedule, verify that the reference patterns have been saved +correctly and that the reference image represents the required displacement zero. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-interaction-during-target-creation.md b/base_connaissances/corpus/station-guide-interaction-during-target-creation.md new file mode 100644 index 0000000..b328023 --- /dev/null +++ b/base_connaissances/corpus/station-guide-interaction-during-target-creation.md @@ -0,0 +1,7 @@ +# Station Guide — Interaction During Target Creation + +To create a processing zone, select Draw rectangle and draw a rectangle around the target. +Zoom is useful for inspecting the image but must not be confused with the zone-drawing tool. +After creation, click the colored border of a zone to select, move, or resize it. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-interval-count.md b/base_connaissances/corpus/station-guide-interval-count.md new file mode 100644 index 0000000..4e3734a --- /dev/null +++ b/base_connaissances/corpus/station-guide-interval-count.md @@ -0,0 +1,8 @@ +# Station Guide — Interval + Count + +• Interval: time between two images or measurements. +• Count: total number of images or measurements to acquire. +Use this mode when an exact sample count is more important than the overall acquisition +duration. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-live-plot.md b/base_connaissances/corpus/station-guide-live-plot.md new file mode 100644 index 0000000..27ae712 --- /dev/null +++ b/base_connaissances/corpus/station-guide-live-plot.md @@ -0,0 +1,28 @@ +# Station Guide — Live Plot + +The Live Plot tab allows you to view data acquisition in real time by clicking the record button in +the upper-right corner. +The following graph types are available: +• Relative Horizontal: relative horizontal displacement of the marker, converted into +millimeters +• Relative Vertical: relative vertical displacement of the marker, converted into millimeters +• Raw Horizontal: raw horizontal position of the target in the image, in pixels +• Raw Vertical: raw vertical position of the target in the image, in pixels +• Error value: error metric comparing the current image of the target to the reference image +in order to detect obstructions +The “Time Range” setting determines the time window queried and displayed in the chart. +Although it can be changed during an acquisition, it is generally better to set it at the beginning. +In the upper-left corner, the plot-options menu gives access to three groups of settings: +• plot updates +• plot scale +• obstruction handling +These options allow you to override the error threshold and use features such as auto period, +lock y, and highlight + filter/hide to visualize or suppress high-error periods. +Example of a real-time acquisition showing target signals together with station motion +Example of the same acquisition after compensation for station motion +These figures show a live acquisition. The first plot includes both target signals and camera +motion, which can distort the actual measurements. The second plot displays only the corrected +target movements, with camera motion removed. This option can be configured in Data +Exploration (see page 12) + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-live-view-page.md b/base_connaissances/corpus/station-guide-live-view-page.md new file mode 100644 index 0000000..ecde4ce --- /dev/null +++ b/base_connaissances/corpus/station-guide-live-view-page.md @@ -0,0 +1,15 @@ +# Station Guide — Live View Page + +Use the Live View page to adjust the camera framing. +• LED toggle: turns the IR LED light on and off. If the LED option is disabled, the reflective +strips will not be illuminated and will therefore be harder to identify. +• Exposure time slider: sets the exposure time manually, or move it fully left to enable “autoexposure” mode. +• PNG / JPG buttons: download the current camera image in full resolution. +Auto-exposure is useful for checking the framing, but the images used for displacement +monitoring should generally be darker. See the marker-configuration guidance below. +Live View page +On this page you can also view the color image captured by the camera by selecting Trigger +camera on the right-hand side of the Vision camera section. +Live View page + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-marker-configuration-process.md b/base_connaissances/corpus/station-guide-marker-configuration-process.md new file mode 100644 index 0000000..615da6f --- /dev/null +++ b/base_connaissances/corpus/station-guide-marker-configuration-process.md @@ -0,0 +1,13 @@ +# Station Guide — Marker Configuration Process + +Select the Draw rectangle tool in the graph toolbar, then click and drag in the image to draw a +tracking zone around the target or reflector. The selected area should fully encompass the +marker and include a margin larger than the expected range of motion. Each rectangle creates a +corresponding measurement-channel row in the configuration table below the image. +If another graph-interaction mode is active, such as Zoom or Pan, select Draw rectangle again +before creating a new target. Existing zones can be selected by clicking precisely on their +colored border, then moved or resized. +Larger image-processing areas allow tracking over greater motion ranges, but they also slow +down image processing. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-measurement-range-and-optical-options.md b/base_connaissances/corpus/station-guide-measurement-range-and-optical-options.md new file mode 100644 index 0000000..fe55e63 --- /dev/null +++ b/base_connaissances/corpus/station-guide-measurement-range-and-optical-options.md @@ -0,0 +1,11 @@ +# Station Guide — Measurement Range and Optical Options + +With 25 mm prisms, differential-mode measurements are possible at distances of up to +approximately 200 m, subject to alignment, atmospheric conditions, background, target +reflectivity, and exposure settings. +Narrower-field-of-view lenses are available. They provide improved angular resolution and +therefore better displacement precision at long range, at the cost of a smaller field of view and +more demanding alignment. Refer to the applicable lens data sheet for the exact focal length, +field of view, and expected precision. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-monitoring-station.md b/base_connaissances/corpus/station-guide-monitoring-station.md new file mode 100644 index 0000000..a80e706 --- /dev/null +++ b/base_connaissances/corpus/station-guide-monitoring-station.md @@ -0,0 +1,14 @@ +# Station Guide — Monitoring Station + +The AIMsight monitoring station is housed in a rugged enclosure designed for field deployment +and flexible mounting. The bottom of the enclosure includes five 1/4 in tapped mounting holes, +compatible with standard camera-support equipment. On the front face, the station features two +status LEDs, the main near-infrared camera, the installation location for the optional color +camera, and the IR LED illumination system. On the rear face, the enclosure provides the powersupply barrel connector for mains or solar operation, the antenna connectors, and the Ethernet +RJ45 connector with a lockable IP67 connector system. For optimal protection, either screw the +protective cap in place or use compatible lockable cables. The rear panel also includes the +power button, with a blue LED indicating that the system is powered on. +From left to right: bottom view showing the mounting interface, front view showing the optical window and +status indicators, and rear view showing the power, antenna, and Ethernet connections. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-monitoring.md b/base_connaissances/corpus/station-guide-monitoring.md new file mode 100644 index 0000000..a86c1d4 --- /dev/null +++ b/base_connaissances/corpus/station-guide-monitoring.md @@ -0,0 +1,15 @@ +# Station Guide — Monitoring + +Enable Monitoring to transmit results to the AIMsight monitoring platform. Depending on the +installed software version, the following options may be available: +• Send measurement to monitoring: sends the acquisition result to the platform. +• Parquet: sends or stores the measurements as a structured Parquet file. +• Send datapoints to monitoring: sends individual measurement points. +• Aggregated: sends aggregated data instead of all raw points. +• Send trigger camera photo to monitoring: sends a context-camera photograph captured at +the trigger time. +The precise behavior and interaction of Parquet, Send datapoints to monitoring, and +Aggregated depend on the installed software version and should be verified with the embedded +API or interface documentation. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-navigation-bar.md b/base_connaissances/corpus/station-guide-navigation-bar.md new file mode 100644 index 0000000..98f4d35 --- /dev/null +++ b/base_connaissances/corpus/station-guide-navigation-bar.md @@ -0,0 +1,14 @@ +# Station Guide — Navigation Bar + +The navigation bar at the top of the screen allows you to navigate between pages and panels +and to control image acquisition and processing. +• Clicking “Live View” or the AIMsight Optical Monitoring logo opens the Live View page. +• The “Pattern Creation” page allows you to define measurement channels by selecting +areas in the image. See Pattern Creation Page (page page 7). +• The “Live Plot” toggle enables or disables live image processing. +• “Data Exploration” allows you to access, view, and download all measurements stored in +the local measurement database (see page 12). +• Clicking the camera icon displays the Camera Management panel (see page 10). +• The current camera ID is displayed in the drop-down menu. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-navigation-within-the-plots.md b/base_connaissances/corpus/station-guide-navigation-within-the-plots.md new file mode 100644 index 0000000..c001fc6 --- /dev/null +++ b/base_connaissances/corpus/station-guide-navigation-within-the-plots.md @@ -0,0 +1,15 @@ +# Station Guide — Navigation Within the Plots + +The same graph-interaction interface is used for time-series plots and for the patternconfiguration graph, where the displayed image—optionally a composite image—is overlaid with +the defined processing zones. A navigation toolbar appears when you hover over a graph. +From left to right, the available tools generally allow you to: +• download the current plot; +• zoom to a region by clicking and dragging; +• pan across the graph; +• draw a rectangle to create a new marker; +• delete a selected marker; +• zoom in or out; +• autoscale the view; +• return to the initial view using the Home icon. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-network-settings.md b/base_connaissances/corpus/station-guide-network-settings.md new file mode 100644 index 0000000..26f7871 --- /dev/null +++ b/base_connaissances/corpus/station-guide-network-settings.md @@ -0,0 +1,25 @@ +# Station Guide — Network Settings + +This section describes the Network Settings interface of the AIMsight Monitoring software. It +allows configuration of how the device communicates with external systems and local networks. +The interface is divided into two main sections: +• Ethernet (wired network) +• Cellular network (mobile connection) +The Ethernet section manages the physical connection through an Ethernet cable. Two +configuration modes are available: +• automatic (DHCP) +• manual (static IP) +Automatic configuration is recommended whenever possible. +• Automatic configuration (DHCP): by default, the camera is configured as a DHCP server +and automatically assigns an IP address to the connected computer. The computer must be +configured to obtain an IP address automatically, and no external network infrastructure is +required. +• Manual configuration: the IP address is configured manually. +Recommended manual configuration: +• IP address: 192.168.1.10 +• Subnet mask: 255.255.255.0 +CAUTION +The PC must be configured within the same network range as the camera (192.168.1.X) and +must use a unique IP address to prevent IP conflicts. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-output-options.md b/base_connaissances/corpus/station-guide-output-options.md new file mode 100644 index 0000000..26668d7 --- /dev/null +++ b/base_connaissances/corpus/station-guide-output-options.md @@ -0,0 +1,8 @@ +# Station Guide — Output Options + +Output destinations are independent. Enable each required destination explicitly. +When the HDF5 (.h5) format is selected, scheduled acquisitions can include the complete set of +advanced diagnostic signals described in page 14. Other export formats are intentionally +simplified and contain either displacement results only or a reduced set of quality metrics. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-panning-and-resetting.md b/base_connaissances/corpus/station-guide-panning-and-resetting.md new file mode 100644 index 0000000..69abe6b --- /dev/null +++ b/base_connaissances/corpus/station-guide-panning-and-resetting.md @@ -0,0 +1,8 @@ +# Station Guide — Panning and Resetting + +• In Pan mode, represented by the arrows icon, click and drag to move the view. +• Double-click inside the graph to reset the pan. +• To pan along one axis only, click and drag from the central part of that axis. +• Double-click an individual axis to autoscale that axis only. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-pattern-creation-page.md b/base_connaissances/corpus/station-guide-pattern-creation-page.md new file mode 100644 index 0000000..10a0a6e --- /dev/null +++ b/base_connaissances/corpus/station-guide-pattern-creation-page.md @@ -0,0 +1,19 @@ +# Station Guide — Pattern Creation Page + +This page allows you to configure image acquisition parameters and image processing, including +the definition of the markers tracked by the camera. +The Preset bar at the top of the page allows several target configurations, each with its own +acquisition settings and processing zones, to be stored in addition to the main or default +configuration. +Defining a target establishes the reference pattern that the system searches for in each +subsequent image to calculate target motion. In the local web interface, the reference pattern is +extracted from the image currently displayed when Save Configuration is clicked. That image +defines the zero position from which all subsequent relative or differential displacements are +calculated. The corresponding date and time are recorded as the Reference date in the +measurement-channel definition. +Before saving, verify that the displayed image is representative, that all targets are clearly visible, +and that no temporary object obscures a tracking zone. Saving the configuration again extracts +new reference patterns from the currently displayed image and therefore redefines the +displacement zero. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-peak-intensity.md b/base_connaissances/corpus/station-guide-peak-intensity.md new file mode 100644 index 0000000..cf96694 --- /dev/null +++ b/base_connaissances/corpus/station-guide-peak-intensity.md @@ -0,0 +1,15 @@ +# Station Guide — Peak Intensity + +“Peak Intensity” is the maximum pixel value measured in the target image. +Practical use: It provides a simple indication of major changes in illumination or target response. +A decreasing value can indicate: +• insufficient illumination; +• partial obstruction; +• contamination or reduced reflector response; or +• a missed or weakened illumination flash. +Very high values, particularly when they repeatedly reach the maximum available image +intensity, can indicate clipping or saturation. +Because Peak Intensity depends on a single pixel, it is sensitive to local variations and should +preferably be interpreted together with Flux and SNR. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-periodic-interval.md b/base_connaissances/corpus/station-guide-periodic-interval.md new file mode 100644 index 0000000..f8c3954 --- /dev/null +++ b/base_connaissances/corpus/station-guide-periodic-interval.md @@ -0,0 +1,8 @@ +# Station Guide — Periodic Interval + +Periodic Interval starts an acquisition at a regular interval selected in the Interval field, for +example every 15 minutes, every hour, or once per day. Use this mode for monitoring that +requires measurements at a constant repetition interval. Custom intervals can also be defined +using the syntax described in the page reached when clicking the information button. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-quick-start-cellular-monitoring-installation.md b/base_connaissances/corpus/station-guide-quick-start-cellular-monitoring-installation.md new file mode 100644 index 0000000..da71854 --- /dev/null +++ b/base_connaissances/corpus/station-guide-quick-start-cellular-monitoring-installation.md @@ -0,0 +1,62 @@ +# Station Guide — Quick Start — Cellular Monitoring Installation + +Use this checklist to bring a monitoring station online through the cellular network: +1. With the system powered off, install an activated 3FF / Micro SIM card with a suitable +mobile-data plan. +2. Connect the supplied cellular antenna using the supplied SMA cable(s). +3. Connect the power supply. +4. Turn the system on and wait for it to boot. +5. Connect locally to the web interface, normally at 192.168.1.2, using the supplied Ethernet +cable. +6. Open Settings / Network Settings. +7. Enter the APN provided by the SIM-card operator in the Cellular Network section. +8. Click Apply Network Settings. +9. Wait for the modem to register on the network. The Link status in the Cellular Network +section should change to Up. +When the link status is Up, the station is connected through the cellular network and can be +reached remotely according to the SIM subscription, network routing, and monitoring-platform +configuration. +The cellular module uses a 3FF / Micro SIM card. The SIM card must be activated and +configured with a mobile data plan suitable for the intended use. A static IP address is not +required. +CAUTION +Make sure that the SIM card data allowance is high enough for the planned operation. If raw, +full-quality images or videos are transmitted over the 4G connection, the data volume can +quickly become very large. +1. Power OFF the system and wait until the modem is completely off. +2. Carefully access and lift the modem module. If a SIM card is already installed, remove it +from the SIM card slot. +3. Insert the Micro SIM card into the SIM card slot in the correct orientation. Make sure the +SIM card is fully seated. +4. Reinstall the modem module onto the AIMsight board. Before powering the product back +on, carefully check that the modem pins are correctly aligned with the AIMsight board +connection pins. Do not power on the product if the modem is offset, tilted, only +partially inserted, or misaligned. Incorrect alignment may prevent normal operation and +may damage the modem or the AIMsight board. +5. Check that the internal antenna connectors are installed and connected correctly. +6. Connect the supplied cellular antenna to the station using the supplied SMA cable(s). +7. Mount the cellular antenna in a clear location with good sky exposure whenever possible, +away from metallic structures, metal surfaces, metal enclosures, other obstructions, other +transmitting antennas, and radio equipment, to reduce signal degradation and improve +reception. +8. Ensure that the antenna is installed for operation at least 20 cm away from the operator +and other persons during normal use. +9. Power the system on again and wait for the modem to start. +10. Go to the System / Network Configuration page, set the correct APN for your SIM card/ +operator, and check the cellular connection status in System Settings (see page 18). +After entering or changing the APN, click Apply Network Settings. Allow time for network +registration, then verify that the Link status under Cellular Network changes to Up. +SIM card installation or replacement procedure: 1. power the system off; 2. access and lift the modem +module to reach the SIM card slot underneath; 3. insert the SIM card in the correct orientation; 4., 5. +reinstall the modem module, ensuring that the modem pins are correctly aligned with the AIMsight board +connection pins; 6. check that the antenna connections are properly installed. +CAUTION +Use only the supplied or approved antenna and cable assembly. Changes to the antenna, +cable, connector, or mounting arrangement may reduce performance and can affect +regulatory compliance. +CAUTION +Do not install or operate the cellular antenna close to the body. The antenna is intended for +fixed or mobile installation only and must be used with a minimum separation distance of 20 +cm from any person during normal operation. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-raw-horizontal-vertical-px.md b/base_connaissances/corpus/station-guide-raw-horizontal-vertical-px.md new file mode 100644 index 0000000..49f5b70 --- /dev/null +++ b/base_connaissances/corpus/station-guide-raw-horizontal-vertical-px.md @@ -0,0 +1,14 @@ +# Station Guide — Raw Horizontal / Vertical [px] + +“Raw Horizontal” and “Raw Vertical” represent the horizontal and vertical position of the +tracked target in the image, expressed in pixels. +These values are provided before conversion to millimetres and before camera-motion +correction. +Practical use: Raw position is mainly useful for diagnostics. It allows the underlying image-based +measurement to be inspected independently of the distance calibration and camera-motion +correction. +Comparing raw and corrected values can help determine whether an observed variation +originates from the tracked target, from movement of the camera, or from the applied geometric +conversion. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-reflective-targets-in-bright-sunlight.md b/base_connaissances/corpus/station-guide-reflective-targets-in-bright-sunlight.md new file mode 100644 index 0000000..2f0f1ad --- /dev/null +++ b/base_connaissances/corpus/station-guide-reflective-targets-in-bright-sunlight.md @@ -0,0 +1,11 @@ +# Station Guide — Reflective Targets in Bright Sunlight + +Detection range depends strongly on target type, target size, orientation, sunlight, background, +and acquisition settings. Pieces of reflective tape larger than approximately 25 mm × 25 mm can +typically be detected up to about 40 m under suitable conditions. Small circular adhesive +reflectors generally have a shorter useful range. +For greater distances, difficult lighting, or poorly reflecting targets, use 25 mm surveying prisms +where practical. Differential acquisition with a higher Stacking value, typically 20 to 40, can also +improve target contrast and detection range for quasi-static measurements. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-relative-horizontal-vertical-mm.md b/base_connaissances/corpus/station-guide-relative-horizontal-vertical-mm.md new file mode 100644 index 0000000..89934d3 --- /dev/null +++ b/base_connaissances/corpus/station-guide-relative-horizontal-vertical-mm.md @@ -0,0 +1,11 @@ +# Station Guide — Relative Horizontal / Vertical [mm] + +“Relative Horizontal” and “Relative Vertical” represent the horizontal and vertical displacement +of the tracked target relative to its reference position, expressed in millimetres. +When camera-motion correction is enabled, the estimated global movement of the camera is +removed from these values. +Practical use: These are the principal displacement values used for structural monitoring and +interpretation. They represent target movement after applying the configured image calibration +and, when enabled, camera-motion compensation. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-rest-api-documentation.md b/base_connaissances/corpus/station-guide-rest-api-documentation.md new file mode 100644 index 0000000..df0b90c --- /dev/null +++ b/base_connaissances/corpus/station-guide-rest-api-documentation.md @@ -0,0 +1,8 @@ +# Station Guide — REST API Documentation + +REST API functionality has been added to the station software. Because the available options are +numerous and may evolve in response to customer requirements, the current API documentation +is embedded directly in the web interface rather than duplicated in this manual. Open Settings / +System Settings, locate the API Tokens row, and click the API Documentation button. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-saving-and-verifying-a-schedule.md b/base_connaissances/corpus/station-guide-saving-and-verifying-a-schedule.md new file mode 100644 index 0000000..009a866 --- /dev/null +++ b/base_connaissances/corpus/station-guide-saving-and-verifying-a-schedule.md @@ -0,0 +1,15 @@ +# Station Guide — Saving and Verifying a Schedule + +After clicking Save Schedule, verify: +• the schedule name and enabled state; +• the next planned trigger time; +• the acquisition type, length, and requested rate; +• the selected target preset; +• exposure, stacking, and gain; +• the enabled output destinations; +• available internal storage; +• network availability when FTP or Monitoring is enabled. +Run a test acquisition with the same settings before leaving the schedule unattended. Confirm +that the measurements are valid and appear at every selected destination. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-sharpness.md b/base_connaissances/corpus/station-guide-sharpness.md new file mode 100644 index 0000000..55be2dc --- /dev/null +++ b/base_connaissances/corpus/station-guide-sharpness.md @@ -0,0 +1,15 @@ +# Station Guide — Sharpness + +“Sharpness” indicates how concentrated the target image is. A well-focused, compact target +generally produces a higher value, while a more diffuse target produces a lower value. +Practical use: A decreasing Sharpness trend can indicate deterioration of image quality caused +by: +• defocus; +• atmospheric turbulence or heat shimmer; +• vibration; or +• changes in the appearance of the target. +Sharpness is most useful as a relative indicator over time for a given target. It should not be +interpreted as an absolute optical measurement or used for direct comparison between different +camera, lens, exposure, or target configurations. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-snr.md b/base_connaissances/corpus/station-guide-snr.md new file mode 100644 index 0000000..25188a7 --- /dev/null +++ b/base_connaissances/corpus/station-guide-snr.md @@ -0,0 +1,19 @@ +# Station Guide — SNR + +“SNR” compares the target peak above the local background with the variations measured in +that background. +A high value indicates that the target is clearly distinguishable from its surroundings. A +decreasing value means that the target is becoming less distinct relative to background +variations. +Practical use: A low or decreasing SNR can indicate: +• insufficient target illumination; +• increased image or background noise; +• adverse visibility conditions; +• obstruction; +• reduced target response; or +• interfering image structures around the target. +SNR complements Peak Intensity because it accounts for the actual background conditions. A +target can retain relatively high absolute brightness while becoming more difficult to distinguish +if the surrounding image becomes brighter or more variable. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-status-leds.md b/base_connaissances/corpus/station-guide-status-leds.md new file mode 100644 index 0000000..7bab012 --- /dev/null +++ b/base_connaissances/corpus/station-guide-status-leds.md @@ -0,0 +1,9 @@ +# Station Guide — Status LEDs + +The front status LEDs are disabled by default because visible illumination may be undesirable in +monitoring applications and can draw attention to the station. On systems equipped with the +optional color camera, the front LEDs should also remain disabled to preserve night-image +quality. The blue LED integrated in the rear power button indicates that the system is powered +on. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-system-settings-page.md b/base_connaissances/corpus/station-guide-system-settings-page.md new file mode 100644 index 0000000..a2f9275 --- /dev/null +++ b/base_connaissances/corpus/station-guide-system-settings-page.md @@ -0,0 +1,20 @@ +# Station Guide — System Settings Page + +The System Settings section of the AIMsight Monitoring interface allows configuration of display +options, time synchronization, and external data export. +This section is divided into three main blocks: +• Web Interface Settings +• FTP Server Configuration +• API Tokens +The first block defines display preferences and access-control settings. +• Distance units: defines the units used for measurements in the software +• Internal time: shows the internal system clock +• “NTP NOT synced” indicates that the device is not currently synchronized with an external +NTP server +• Set Date: allows manual adjustment of the system time when NTP synchronization is +unavailable +The FTP server configuration section allows automatic export of recorded data to a remote +server using the FTP protocol. When configured, the system automatically uploads measurement +data or images to a central server at defined intervals or upon specific events. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-target-image-quality-and-pattern-matching-metrics.md b/base_connaissances/corpus/station-guide-target-image-quality-and-pattern-matching-metrics.md new file mode 100644 index 0000000..328d814 --- /dev/null +++ b/base_connaissances/corpus/station-guide-target-image-quality-and-pattern-matching-metrics.md @@ -0,0 +1,13 @@ +# Station Guide — Target Image Quality and Pattern-Matching Metrics + +These metrics are calculated independently for each processed target image. They describe +how clearly the target is visible, how stable its image appearance remains, and how reliably the +current target image can be matched with its reference pattern. +They are primarily diagnostic indicators intended to explain changes in measurement quality and +help identify their likely cause. Most metrics should be interpreted as trends over time and in +combination with the corresponding image and other available indicators, rather than as +standalone pass/fail criteria. +The Error Value is a specific exception: when an Error Threshold is configured, it is also used to +identify and reject measurements for which pattern matching is considered unreliable. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-trace-selection-and-visibility.md b/base_connaissances/corpus/station-guide-trace-selection-and-visibility.md new file mode 100644 index 0000000..2334501 --- /dev/null +++ b/base_connaissances/corpus/station-guide-trace-selection-and-visibility.md @@ -0,0 +1,8 @@ +# Station Guide — Trace Selection and Visibility + +When several measurement channels are displayed, use the legend on the right side of the graph +to control their visibility: +• single-click a legend entry to show or hide that trace; +• double-click a legend entry to isolate that trace and hide the others. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-troubleshooting.md b/base_connaissances/corpus/station-guide-troubleshooting.md new file mode 100644 index 0000000..951eedf --- /dev/null +++ b/base_connaissances/corpus/station-guide-troubleshooting.md @@ -0,0 +1,17 @@ +# Station Guide — Troubleshooting + +If the system is not operating as expected, first verify the basic connections and settings: +• power supply +• Ethernet connection +• network configuration +Ensure that the camera is properly powered on and that the computer or network device is +correctly configured. +If the issue persists: +• check the camera IP configuration +• confirm that the device is within the same network range as the host system +• restart the camera and the software to clear temporary communication issues +For remote-access problems, ensure that the internet connection is active and that the project +has been correctly defined on the AIMsight monitoring platform. +If the problem continues after these checks, contact support. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-typical-installation-procedure.md b/base_connaissances/corpus/station-guide-typical-installation-procedure.md new file mode 100644 index 0000000..d1f112d --- /dev/null +++ b/base_connaissances/corpus/station-guide-typical-installation-procedure.md @@ -0,0 +1,17 @@ +# Station Guide — Typical Installation Procedure + +• Mount the camera on a sturdy tripod rated for at least 5 kg. +• Check the live view and adjust the framing (Live View Page, see page 6). +• Check the battery charge level (Camera Management Panel, see page 10). +• Install the reflectors on the structure and place reference reflectors on points considered +fixed. +• Select the reflectors in the image, assign names to them, and configure the channel +parameters (Pattern Creation Page, see page 7). +• Set the measurement frame rate (Camera Management Panel, see page 10). +• Enable image processing and verify that it keeps up with image acquisition (Camera +Management Panel, see page 10). +• Check the measurement data (Data Exploration Page, see page 12). +• Start a new acquisition, perform the load test, and review the results (Data Exploration +Page, see page 12). + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-working-with-conventional-image-features.md b/base_connaissances/corpus/station-guide-working-with-conventional-image-features.md new file mode 100644 index 0000000..e969b1c --- /dev/null +++ b/base_connaissances/corpus/station-guide-working-with-conventional-image-features.md @@ -0,0 +1,57 @@ +# Station Guide — Working with Conventional Image Features + +When reflectors are unavailable or difficult to install, sufficiently contrasted and stable visual +features may also be tracked. If the installed software provides the Work on IRON images option, +enable it to work with conventional images rather than the contrast-enhanced reflector +representation. Verify that the selected texture remains visible and stable under all expected +measurement conditions. +Once a zone has been drawn, a new row appears in the “Marker Configuration” table. +Define the marker parameters in the “Marker Configuration” table: +• Name: name of the position marker, that is, the name of the measurement channel +• Type: assigns the marker to a group or type. Reference targets are considered fixed points, +while markers in “Target Group(s)” are tracked. Proper selection of reference targets is +essential because they are used to compensate for camera motion. +• Global reference: a point considered fixed in the monitored scene. Global-reference points +are used to estimate and compensate for movement of the monitoring station itself. +• Local reference: identifies a measurement point as belonging to the local-reference group. +This designation is used for classification and display purposes only. Unlike a Global +reference, a local reference is not treated as a fixed point and is not used to compensate for +movements of the monitoring station. No additional processing is applied; local references +are handled in the same way as other measurement-point groups. +• Error Threshold (optional): threshold above which a measurement is considered invalid. +This is used to detect obstructions, for example when a marker is hidden by a vehicle or +vegetation. By default, the error threshold is 0.7. +• Pattern Size: adjusts the size of the image-processing area around the marker +• Resolution (optional): processing resolution, expressed as a fraction of a pixel. The default +value is 100, corresponding to one hundredth of a pixel. Lower values reduce processing +time. +• Distance: straight-line distance in millimeters between the front of the camera and the +marker. This is used to calculate the correct pixel-to-distance conversion factor. +An error in the entered distance produces a proportional scale error. For example, a coarse +distance error of 1%—such as entering 99 m or 101 m instead of 100 m—produces an error of +approximately 0.1 mm on a measured displacement of 10 mm. +• Reference date: records the time at which the reference pattern defining the zero position +was set +To adjust the position of the marker area, first select it by clicking its border. You can then drag +its corners to reshape it or drag inside the area to move it. It is generally best to keep the marker +centered within the target region. +The “Recapture” button allows you to take a new image and verify that the marker zones are +correctly defined. +Once the settings have been established, save the pattern configuration by clicking “Save +Configuration”. The reference patterns are then extracted from the image currently displayed. +This image becomes the zero for each channel, and subsequent displacements are calculated +relative to the positions saved at that moment. To redefine the zero, display or recapture an +appropriate new image, verify all zones and parameters, and save the configuration again. +The “Store Locally” toggle must be enabled if the system is to keep measurements in onboard +memory. +If the system has internet access through either Ethernet or the onboard 4G module, it can also +be configured to forward measurements to the AIMsight database by enabling “Send to Server”. +The “Send to Monitoring” option must be enabled to transmit measurements in real time to the +monitoring platform. When activated, the system continuously sends data to the remote +supervision interface, allowing live tracking and analysis. +The “Send to FTP Server” option must be enabled to upload the measurements automatically to +an external FTP server. This allows the data to be archived and accessed later for analysis or +backup purposes. +Target Configuration + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/station-guide-zooming-and-scaling.md b/base_connaissances/corpus/station-guide-zooming-and-scaling.md new file mode 100644 index 0000000..38b09c8 --- /dev/null +++ b/base_connaissances/corpus/station-guide-zooming-and-scaling.md @@ -0,0 +1,9 @@ +# Station Guide — Zooming and Scaling + +• In Zoom mode, represented by the magnifying-glass icon, click and drag to enlarge a +region. +• Double-click inside the graph to reset the view and autoscale both axes. +• To zoom one axis only, click and drag near that axis. +• To act on both axes simultaneously, begin the drag near the point where the axes meet. + +Source : AIMsight Station Guide, rév. 1.5 diff --git a/base_connaissances/corpus/tensions-de-la-batterie-selon-son-etat.md b/base_connaissances/corpus/tensions-de-la-batterie-selon-son-etat.md new file mode 100644 index 0000000..f992541 --- /dev/null +++ b/base_connaissances/corpus/tensions-de-la-batterie-selon-son-etat.md @@ -0,0 +1,12 @@ +# Tensions de la batterie selon son état + +Ordres de grandeur de la tension de la batterie (moyennes horaires). Ce sont des repères approximatifs : ils varient d'une station à l'autre (capacité de la batterie, chargeur, ensoleillement, température). Comparer une station à son propre passé plutôt qu'à ces valeurs. +- En charge : environ 13,1 à 13,8 V, en montée lente le matin. Les jours nuageux, elle plafonne vers 13,4 V : la batterie charge sans se remplir. +- Pleine charge : vers 14,0 à 14,3 V, plate pendant quelques heures un jour ensoleillé. Le soir, la tension retombe vite (vers 13,2 V). +- Sur secteur : vers 14,1 à 14,2 V jour et nuit, sans cycle jour/nuit. +- En décharge (la nuit) : d'abord un plateau vers 13,0 à 13,2 V avec une baisse très lente, puis un coude de 12,8 à 12,5 V ; sous 12,5 V, la tension chute beaucoup plus vite. +- Coupure et redémarrage : sous 12 V environ, la station s'éteint, et ne redémarre que lorsque la batterie est remontée vers 12,6 V. En moyennes horaires, les derniers instants avant une coupure ne sont pas visibles. +- Sur secteur, quand le secteur est coupé : la tension passe de ~14,2 V à ~13,1 V, baisse lentement, puis atteint le coude et décroche. +- Autonomie : environ 5 jours avec une mesure toutes les 15 min (veille entre les mesures) ; de 15 h (7 Ah) à 46 h (21 Ah) environ à 5 W en continu. Une batterie de plus petite capacité se vide plus vite. + +Source : Savoir métier AIMsight diff --git a/base_connaissances/corpus/the-camera-is-online-but-i-am-not-receiving-data-what-should-i-check.md b/base_connaissances/corpus/the-camera-is-online-but-i-am-not-receiving-data-what-should-i-check.md new file mode 100644 index 0000000..4d06a8e --- /dev/null +++ b/base_connaissances/corpus/the-camera-is-online-but-i-am-not-receiving-data-what-should-i-check.md @@ -0,0 +1,21 @@ +# The camera is online, but I am not receiving data. What should I check? + +An online camera does not necessarily mean that measurements are being acquired or exported +correctly. Acquisition and data transfer should be checked separately. +First verify measurement acquisition: +• Is the required acquisition schedule enabled? +• Has the scheduled acquisition time been reached? +• Can a measurement be triggered manually? +• Are valid target measurements being produced? +• Are the expected measurements visible in the local interface or Data Exploration tools? +Then verify data transfer: +• Is the required FTP, optional AIMsight Cloud, or other export destination configured? +• Is the destination server reachable? +• Are the hostname, address, port, and path correct? +• Are authentication credentials valid? +• Is the expected export format enabled? +• Is the station’s Internet connection operational if the destination is remote? +If data are available locally but do not reach the external destination, the problem is most likely +related to communication or export configuration rather than measurement acquisition. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/the-camera-is-running-but-is-not-connected-over-4g-what-should-i-check.md b/base_connaissances/corpus/the-camera-is-running-but-is-not-connected-over-4g-what-should-i-check.md new file mode 100644 index 0000000..4dca43e --- /dev/null +++ b/base_connaissances/corpus/the-camera-is-running-but-is-not-connected-over-4g-what-should-i-check.md @@ -0,0 +1,18 @@ +# The camera is running but is not connected over 4G. What should I check? + +A 4G connection may take a few minutes to become available after the station starts. +Check the following: +• Make sure the cellular antenna is correctly connected. +• Check the cellular signal level in the camera interface, if available. +• If the camera is installed indoors, underground, or behind substantial concrete or metallic +structures, cellular reception may be weak even if a connection is occasionally available. +• If possible, relocate the antenna to a location with better reception or use an appropriate +antenna extension / external antenna. +• Check whether the camera can be reached locally over Ethernet. If local access works, the +camera itself is operating and the problem is limited to remote connectivity. +• If cellular signal is sufficient but the connection remains unavailable, the modem/SIM +configuration should be checked. +For installations with persistently poor cellular coverage, Ethernet or another external +communication solution may be preferable. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/what-do-the-columns-in-the-csv-export-represent.md b/base_connaissances/corpus/what-do-the-columns-in-the-csv-export-represent.md new file mode 100644 index 0000000..7f6f435 --- /dev/null +++ b/base_connaissances/corpus/what-do-the-columns-in-the-csv-export-represent.md @@ -0,0 +1,31 @@ +# What do the columns in the CSV export represent? + +Measurement columns are prefixed with the corresponding target or channel name, for example +target_06_rch. +The most relevant columns for normal displacement monitoring are rch and rcv. +The remaining columns are retained for traceability and advanced post-processing, including the +possibility of recomputing camera-motion compensation using a different reference network. +• x: Absolute target X position in the image [px]. +• y: Absolute target Y position in the image [px]. +• rx: Relative X displacement before camera-motion correction. +• ry: Relative Y displacement before camera-motion correction. +• rch: Camera-corrected horizontal displacement [mm]. +• rcv: Camera-corrected vertical displacement [mm]. +• error: Target recognition error. This metric compares the current image of the target with its +reference image and is used to detect obstructions, visibility problems, or other changes in +target appearance. +• rcx, rcy: Intermediate camera-corrected values used for processing and post-processing. +They are normally not required when using the final rch and rcv displacement results. +Global camera-transformation values are prefixed with camera: +• camera_pan: Estimated camera pan angle [deg]. +• camera_tilt: Estimated camera tilt angle [deg]. +• camera_rotation: Estimated camera roll angle [deg]. +• camera_scale: Estimated image scale factor, where 1.0 means no scaling. +• camera_sigma0: Residual error of the reference-network fit. An increase can indicate +reduced consistency or deformation of the reference network. +Additional reference-network statistics may include: +• inlier_{channel}: Information on whether/how the reference channel contributed to the +robust camera-motion fit. +• reproj_err_{channel}: Reprojection residual associated with the reference channel. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/what-do-x-y-rx-and-ry-represent-in-exported-data.md b/base_connaissances/corpus/what-do-x-y-rx-and-ry-represent-in-exported-data.md new file mode 100644 index 0000000..cfd3032 --- /dev/null +++ b/base_connaissances/corpus/what-do-x-y-rx-and-ry-represent-in-exported-data.md @@ -0,0 +1,9 @@ +# What do x, y, rx, and ry represent in exported data? + +x and y are the raw target positions in image pixels. They can be useful, for example, to +visualize the apparent trajectory of a target within the image. +rx and ry are the relative displacements calculated by AIMsight, expressed in the configured +distance units. +They should therefore not be calculated simply as x - x_initial and y - y_initial. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/what-does-camera-movement-represent-in-data-exploration.md b/base_connaissances/corpus/what-does-camera-movement-represent-in-data-exploration.md new file mode 100644 index 0000000..37322a6 --- /dev/null +++ b/base_connaissances/corpus/what-does-camera-movement-represent-in-data-exploration.md @@ -0,0 +1,16 @@ +# What does Camera Movement represent in Data Exploration? + +Camera Movement represents the estimated changes in camera orientation calculated from the +reference targets. +These values can reveal small changes in station orientation caused, for example, by: +• Thermal effects on the camera support. +• Mechanical movement or relaxation of the mounting system. +• Wind-induced movement. +• Accidental displacement of the station. +Camera Movement is used internally to compensate for station motion so that the reported +displacement primarily represents movement of the monitored targets relative to the reference +network. +The Camera Movement plots are also useful for diagnosing installation stability and identifying +changes in the camera support over time. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/what-does-the-error-value-represent.md b/base_connaissances/corpus/what-does-the-error-value-represent.md new file mode 100644 index 0000000..da1e614 --- /dev/null +++ b/base_connaissances/corpus/what-does-the-error-value-represent.md @@ -0,0 +1,17 @@ +# What does the Error Value represent? + +The Error Value corresponds to the target recognition error. +For each monitored target, the current image of the target is compared with the reference image +recorded when the target was configured. +The error value therefore indicates how much the current appearance of the target differs from +its reference appearance. +A higher error value can indicate: +• Partial or complete obstruction of the target. +• Vegetation, vehicles, equipment, or other objects temporarily hiding the target. +• Dirt, water, snow, or contamination on the target. +• Significant changes in illumination. +• Damage or modification of the target. +• Any other significant change in its appearance compared with the original configuration. +A low error value indicates that the target still closely matches its reference image. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/what-happens-if-a-target-changes-shape-or-becomes-partially-obstructed.md b/base_connaissances/corpus/what-happens-if-a-target-changes-shape-or-becomes-partially-obstructed.md new file mode 100644 index 0000000..ffb7779 --- /dev/null +++ b/base_connaissances/corpus/what-happens-if-a-target-changes-shape-or-becomes-partially-obstructed.md @@ -0,0 +1,16 @@ +# What happens if a target changes shape or becomes partially obstructed? + +Target recognition operates in parallel with displacement measurement. +For each monitored target, the current image is compared with the reference image used when +the target was configured. This produces a recognition error. +The recognition error increases if, for example: +• the target becomes dirty; +• the target is partially obstructed; +• part of a reflective target becomes detached; +• its appearance changes significantly. +Above a configurable recognition-error threshold, the displacement measurement is considered +invalid. +An alarm can also be configured based on the number of rejected targets, making it possible to +detect problems such as poor visibility, contamination, or damaged targets. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/what-happens-if-the-camera-moves-or-changes-orientation-after-commissioning.md b/base_connaissances/corpus/what-happens-if-the-camera-moves-or-changes-orientation-after-commissioning.md new file mode 100644 index 0000000..6c1ba3c --- /dev/null +++ b/base_connaissances/corpus/what-happens-if-the-camera-moves-or-changes-orientation-after-commissioning.md @@ -0,0 +1,12 @@ +# What happens if the camera moves or changes orientation after commissioning? + +The effect depends on the size of the processing areas defined around the tracked targets and +on the selected optics. +Larger processing areas allow targets to remain tracked after larger camera movements, at the +cost of additional processing time. +If a target reaches the edge of its processing area, the processing area must normally be +redefined. The same applies if the monitored target itself undergoes a very large displacement. +Camera-orientation changes are also available in the processed measurement data and can be +monitored to identify excessive station movement before it affects measurement availability. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/what-happens-to-alarms-if-the-internet-or-4g-connection-is-lost.md b/base_connaissances/corpus/what-happens-to-alarms-if-the-internet-or-4g-connection-is-lost.md new file mode 100644 index 0000000..fc7977c --- /dev/null +++ b/base_connaissances/corpus/what-happens-to-alarms-if-the-internet-or-4g-connection-is-lost.md @@ -0,0 +1,27 @@ +# What happens to alarms if the Internet or 4G connection is lost? + +Loss of remote connectivity does not necessarily mean that the measurement station itself has +stopped operating. +When the station includes a local software licence, acquisition and local processing can continue +while the camera is disconnected from the Internet, provided that the station remains powered. A +station supplied without a standalone local licence depends on an active AIMsight Cloud +subscription, as specified in the project quotation or agreement. +Alarm behavior then depends on the type of alarm and how it is implemented. +Local alarm actions, such as an alarm evaluated directly on the station and connected to a local +output or relay, can operate independently of the Internet connection when the station has the +required local software licence and is configured accordingly. +Remote alarm notifications, such as cloud notifications, SMS, email, or alarms transmitted to an +external system, require the corresponding communication path to be available. They cannot be +relied upon during a loss of 4G or Ethernet connectivity. +Cloud notifications and Cloud-based alarm supervision require the optional AIMsight Cloud +service. +For applications where alarm transmission is safety-critical, the communication architecture +should therefore be designed accordingly. Possible measures include: +• a local relay or digital alarm output; +• redundant communication paths; +• communication-loss monitoring; +• an external system supervising station availability. +Loss of communication should itself be treated as a condition worth monitoring in critical +applications. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/what-is-the-delivery-time-for-multiple-stations.md b/base_connaissances/corpus/what-is-the-delivery-time-for-multiple-stations.md new file mode 100644 index 0000000..e7e9d9e --- /dev/null +++ b/base_connaissances/corpus/what-is-the-delivery-time-for-multiple-stations.md @@ -0,0 +1,8 @@ +# What is the delivery time for multiple stations? + +We strive to keep standard versions available off-the-shelf. Delivery time depends on quantity, +optics, accessories, and system configuration. +Current lead time should therefore be confirmed when requesting a quotation rather than +considered a fixed product specification. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/what-is-the-error-column-in-exported-data.md b/base_connaissances/corpus/what-is-the-error-column-in-exported-data.md new file mode 100644 index 0000000..9832052 --- /dev/null +++ b/base_connaissances/corpus/what-is-the-error-column-in-exported-data.md @@ -0,0 +1,17 @@ +# What is the error column in exported data? + +The error column is a target recognition error, not a displacement uncertainty or accuracy +estimate. +It compares the current appearance of a target with the reference image recorded during +configuration. +The value typically increases when: +• The target is partially or completely obstructed. +• Vegetation, vehicles, people, animals or equipment pass in front of the target. +• The target becomes dirty, wet, covered, or damaged. +• Illumination changes significantly. +• The appearance of the target otherwise differs substantially from its reference image. +Measurements for which the recognition error exceeds the configured Error Threshold can be +rejected as invalid. +The default Error Threshold is 0.7 unless a different value has been configured. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/what-is-the-error-threshold.md b/base_connaissances/corpus/what-is-the-error-threshold.md new file mode 100644 index 0000000..82c80a2 --- /dev/null +++ b/base_connaissances/corpus/what-is-the-error-threshold.md @@ -0,0 +1,10 @@ +# What is the Error Threshold? + +The Error Threshold defines the recognition-error value above which a measurement is +considered invalid. +By default, the threshold is 0.7. This mechanism is primarily used to reject measurements when a +target is obstructed or its appearance has changed too much for the measurement to be +considered reliable. +The threshold can be overridden with a user-defined value when required by the application. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/what-is-the-expected-battery-autonomy-if-external-power-fails.md b/base_connaissances/corpus/what-is-the-expected-battery-autonomy-if-external-power-fails.md new file mode 100644 index 0000000..0e43506 --- /dev/null +++ b/base_connaissances/corpus/what-is-the-expected-battery-autonomy-if-external-power-fails.md @@ -0,0 +1,8 @@ +# What is the expected battery autonomy if external power fails? + +With a typical monitoring cycle of approximately one measurement every 15 minutes, the +internal battery provides an indicative autonomy of approximately five days. +Actual autonomy depends on the acquisition configuration, communication activity, +environmental conditions, and battery condition. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/what-is-the-maximum-operating-distance.md b/base_connaissances/corpus/what-is-the-maximum-operating-distance.md new file mode 100644 index 0000000..e74ec07 --- /dev/null +++ b/base_connaissances/corpus/what-is-the-maximum-operating-distance.md @@ -0,0 +1,14 @@ +# What is the maximum operating distance? + +Operating distance depends on: +• required measurement accuracy; +• lens and field of view; +• target size and type; +• atmospheric conditions; +• illumination; +• required measurement availability. +At short range, AIMsight can achieve micron-level resolution. +At long range, it can operate in applications traditionally addressed using total stations. A test +installation has been operated with monitored points at approximately 1.6 km. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/what-should-i-check-before-leaving-the-installation-site.md b/base_connaissances/corpus/what-should-i-check-before-leaving-the-installation-site.md new file mode 100644 index 0000000..165487f --- /dev/null +++ b/base_connaissances/corpus/what-should-i-check-before-leaving-the-installation-site.md @@ -0,0 +1,33 @@ +# What should I check before leaving the installation site? + +Before leaving the site, perform at least the following commissioning checks: +• Communication: verify that the station is accessible through either 4G or Ethernet, +according to the intended installation configuration. +• Power supply: verify that the external power supply is operating correctly, whether mains +or solar. +• Battery: verify that the internal battery is connected and charging. +• Charging indication: check the charging / power LED. +• Camera access: verify access to the camera web interface. +• Image: check image quality, focus, exposure, and field of view. +• Targets: verify that all required targets or prisms are clearly visible in the image. +• References: verify that all selected reference targets are clearly visible. +• Target identification: verify that the configured processing areas correspond to the +intended physical targets. +• Distances: verify that the distances from the camera to the monitored targets are known +and correctly entered where required for displacement conversion. +• Reference configuration: verify that a sufficient and appropriate set of reference targets +has been configured. +• Reference fit: verify that the reference-network fit and sigma0 are reasonable. +• Acquisition: trigger at least one measurement and confirm that valid measurements are +produced. +• Schedule: verify that the required periodic acquisition schedule is enabled. +• Data transfer: verify that data reach the intended server, FTP destination, optional AIMsight +Cloud platform, or API consumer. +• Timestamps: verify that exported data contain the required timestamp information and that +the timezone is understood. +• Alarms: where alarms are required, verify their configuration and perform a functional test +whenever practical. +Whenever possible, allow at least one complete scheduled measurement and data-transfer cycle +to run before leaving the site. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/what-should-i-do-if-all-targets-may-potentially-move-or-settle.md b/base_connaissances/corpus/what-should-i-do-if-all-targets-may-potentially-move-or-settle.md new file mode 100644 index 0000000..02c4ca8 --- /dev/null +++ b/base_connaissances/corpus/what-should-i-do-if-all-targets-may-potentially-move-or-settle.md @@ -0,0 +1,20 @@ +# What should I do if all targets may potentially move or settle? + +If no target can be considered perfectly stable, several targets can be configured as references. +In some applications, all targets, or preferably a suitable set of relatively distant targets, can be +used. +Camera motion is estimated using a robust fit over the complete reference network. The +algorithm therefore tolerates the displacement of a limited number of individual reference targets +without immediately interpreting their displacement as camera motion. +The system consequently remains sensitive to differential settlement or deformation within the +monitored area. +For a real structural displacement to be entirely absorbed into the camera-motion correction, the +complete reference network would have to deform according to a very specific geometry that is +indistinguishable from a camera rotation. +For example, in a simple configuration, all targets would have to settle simultaneously by +approximately an amount proportional to their distance from the camera: a target twice as far +from the camera would have to settle approximately twice as much. +Such a displacement pattern is generally sufficiently unlikely that using a distributed set of +potentially moving targets as references remains a robust solution in practice. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/where-should-reference-targets-be-placed.md b/base_connaissances/corpus/where-should-reference-targets-be-placed.md new file mode 100644 index 0000000..12f3b9a --- /dev/null +++ b/base_connaissances/corpus/where-should-reference-targets-be-placed.md @@ -0,0 +1,29 @@ +# Where should reference targets be placed? + +Reference targets are used to estimate and compensate for movements of the camera itself. +Their placement therefore has a direct influence on the quality of this compensation. +Whenever possible, references should be installed on elements that can reasonably be +considered stable and distributed across the image, ideally surrounding or framing the area +containing the measurement points. A good horizontal and vertical distribution makes it easier to +distinguish camera pan, tilt and roll and avoids extrapolating the correction from references +concentrated in a small part of the image. +It is also preferable to place the references at a distance comparable to or greater than that of +the measurement points, ideally in the background. More distant references are less sensitive to +parallax effects caused by small translational movements of the camera support. +Conversely, references located significantly in the foreground may show a relatively large +apparent displacement following a small lateral movement of the camera. If this information is +then used to correct points located much farther away, the camera movement may be +overcompensated. +In practice, preference should therefore be given to: +• supports whose stability can reasonably be assumed; +• references located as far from the camera as practical, preferably in the background of the +monitored area; +• references distributed around the measurement area rather than grouped in a single part of +the image; +• references that will remain reliably visible over time, with limited risk of obstruction by +vegetation, vehicles, equipment or other objects. +If no perfectly fixed references are available, several measurement points can also be used +together as a reference network. Camera movement is then estimated robustly from the overall +network, while the system remains sensitive to differential movements between individual points. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/which-data-transfer-methods-are-available.md b/base_connaissances/corpus/which-data-transfer-methods-are-available.md new file mode 100644 index 0000000..2bab020 --- /dev/null +++ b/base_connaissances/corpus/which-data-transfer-methods-are-available.md @@ -0,0 +1,12 @@ +# Which data-transfer methods are available? + +FTP can be configured directly by the end user through the camera interface. +AIMsight also provides an API for functions including: +• triggering acquisitions; +• controlling the system; +• retrieving measurement data. +AIMsight Cloud is an additional optional destination when it is included in the project +configuration and licence. Additional transfer mechanisms can be implemented where required +for specific integrations. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/which-diagnostic-signals-are-available-in-data-exploration.md b/base_connaissances/corpus/which-diagnostic-signals-are-available-in-data-exploration.md new file mode 100644 index 0000000..361cdd2 --- /dev/null +++ b/base_connaissances/corpus/which-diagnostic-signals-are-available-in-data-exploration.md @@ -0,0 +1,34 @@ +# Which diagnostic signals are available in Data Exploration? + +In addition to the principal displacement values, Data Exploration provides signals describing +target visibility, image quality, registration reliability, and camera movement. These indicators are +calculated by the station and are intended to be interpreted together with the corresponding +images and as trends over time. +The principal signals are: +• Relative Horizontal / Vertical: the main target-displacement results in millimetres, after +calibration and, when enabled, camera-motion correction. +• Raw Horizontal / Vertical: the target position in the image in pixels, before conversion to +millimetres and before camera-motion correction. +• Error Value: the difference between the current target image and its reference after +registration. It is the main general-purpose recognition-quality indicator and is used by the +obstruction filters. +• Sharpness: indicates how concentrated the target image is. A decreasing trend can +suggest defocus, vibration, atmospheric disturbance, or another loss of image quality. +• FWHM: estimates the apparent width of the target image in pixels. An increasing trend can +indicate image spreading caused by defocus, turbulence, motion blur, or vibration. +• Dominance: indicates whether another bright feature is becoming comparable with the +tracked reflector. A value approaching 1 indicates an increasing risk of competition between +image features. +• Peak Intensity: the maximum pixel value in the target image. It helps identify major changes +in illumination or target response, as well as possible saturation. +• Flux: the total target signal after estimating the image background. It is useful for detecting +gradual changes in illumination, reflector condition, alignment, or obstruction. +• SNR: compares the target signal with variations in the local background. A decreasing value +means that the target is becoming less distinct from its surroundings. +• Camera Movement: the global movement estimated from the reference targets and used to +compensate for movement of the camera or its support. +No single metric should normally be treated as a universal pass/fail criterion. The combination of +several trends is generally more informative. The Available Signals and Diagnostic Metrics +section of the station manual provides the complete definitions and interpretation guidance. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/which-file-formats-can-aimsight-export.md b/base_connaissances/corpus/which-file-formats-can-aimsight-export.md new file mode 100644 index 0000000..85c8aee --- /dev/null +++ b/base_connaissances/corpus/which-file-formats-can-aimsight-export.md @@ -0,0 +1,12 @@ +# Which file formats can AIMsight export? + +AIMsight can generate: +• HDF5 (.h5) files containing the complete acquisition and advanced diagnostic signals; +• CSV files; +• Parquet files; +• images; +• video streams. +Additional export formats can be implemented where required as an integration or development +service. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/which-licensing-models-are-available.md b/base_connaissances/corpus/which-licensing-models-are-available.md new file mode 100644 index 0000000..a258581 --- /dev/null +++ b/base_connaissances/corpus/which-licensing-models-are-available.md @@ -0,0 +1,12 @@ +# Which licensing models are available? + +Both subscription-based and local software licence models are available, depending on the +selected configuration. +A standalone local software licence allows the station to acquire, process, and store +measurements without an active AIMsight Cloud subscription. Alternatively, the station can be +supplied without this licence and operated as part of an active AIMsight Cloud subscription. +AIMsight Cloud can also complement a locally licensed station by providing centralized data +access, image archiving, alarms, visualization, and post-processing. The project quotation or +agreement specifies the applicable licence, subscription, and included services. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/corpus/which-timezone-is-used-for-timestamps.md b/base_connaissances/corpus/which-timezone-is-used-for-timestamps.md new file mode 100644 index 0000000..0480106 --- /dev/null +++ b/base_connaissances/corpus/which-timezone-is-used-for-timestamps.md @@ -0,0 +1,17 @@ +# Which timezone is used for timestamps? + +When AIMsight data are combined with measurements from other sensors or external acquisition +systems, the time basis must be handled explicitly. +In particular, verify: +• which timestamp field is being used; +• whether timestamps are expressed in UTC or local time; +• the station timezone configuration; +• whether daylight-saving-time conversion is performed by the station, server, or external +processing software; +• timestamp precision; +• which instant the timestamp represents for the selected acquisition mode. +For automated processing, using an unambiguous timestamp convention such as UTC is +recommended. +Do not rely solely on the CSV file creation or modification time as the measurement timestamp. + +Source : AIMsight FAQ, rév. 1.5 diff --git a/base_connaissances/decoupage.py b/base_connaissances/decoupage.py new file mode 100644 index 0000000..7ea0c07 --- /dev/null +++ b/base_connaissances/decoupage.py @@ -0,0 +1,110 @@ +"""Du texte d'un PDF (sortie de `pdftotext`, sans `-layout`) ou d'un Markdown aux extraits de la base de connaissances +de LibreDesk ; écriture et lecture du corpus (un fichier Markdown par extrait).""" +import re +import unicodedata +from dataclasses import dataclass +from pathlib import Path + +ENTREE = re.compile(r"(.+?)\s*(?:\.\s?){3,}[\s⁠]*(\d+)") # « titre . . . . page » ; pdftotext met parfois U+2060 +PUCE = re.compile(r"\s*�\s*") + + +def slug(titre: str) -> str: + sans_accents = unicodedata.normalize("NFKD", titre).encode("ascii", "ignore").decode() + return re.sub(r"-+", "-", re.sub(r"[^a-z0-9]", "-", sans_accents.lower())).strip("-") + + +@dataclass(frozen=True) +class Extrait: + titre: str + contenu: str + source: str + + @property + def cle(self) -> str: + return slug(self.titre) + ".md" + + +def _parasite(ligne: str, parasites: list[str]) -> bool: + """En-tête, pied de page ou numéro de page.""" + nette = ligne.strip() + return nette in parasites or bool(re.fullmatch(r"\d+", nette)) + + +def _table_des_matieres(lignes: list[str], parasites: list[str]) -> tuple[list[str], int]: + """Les titres de la table des matières et l'indice de sa dernière ligne. Un titre peut continuer sur la ligne + suivante, et plusieurs entrées peuvent être collées sur une ligne.""" + titres, debut, fin = [], "", -1 + for i, ligne in enumerate(lignes): + entrees = list(ENTREE.finditer(ligne)) + if not entrees: + if (fin >= 0 or titres) and not _parasite(ligne, parasites): + debut = f"{debut} {ligne.strip()}".strip() + continue + for k, m in enumerate(entrees): + titre = m.group(1).strip() + if k == 0 and debut: + titre = f"{debut} {titre}" + titres.append(" ".join(titre.split())) + debut, fin = ligne[entrees[-1].end():].strip(), i + return titres, fin + + +def decouper_pdf(texte: str, parasites: list[str], source: str = "") -> list[Extrait]: + """Un extrait par entrée de la table des matières qui a un corps ; les titres de chapitre (sans corps) n'en donnent + pas.""" + lignes = texte.splitlines() + titres, fin = _table_des_matieres(lignes, parasites) + connus = set(titres) + corps = [ligne.strip() for ligne in lignes[fin + 1:] if ligne.strip() and not _parasite(ligne, parasites)] + sections: list[tuple[str, list[str]]] = [] + i = 0 + while i < len(corps): + # Un titre long peut être coupé sur deux ou trois lignes dans le corps. + n = next((n for n in (1, 2, 3) if " ".join(corps[i:i + n]) in connus), 0) + if n: + sections.append((" ".join(corps[i:i + n]), [])) + i += n + continue + if sections: + sections[-1][1].append(corps[i]) + i += 1 + extraits = [] + for titre, corps in sections: + contenu = PUCE.sub("\n- ", "\n".join(corps)).strip() + if contenu: + extraits.append(Extrait(titre, contenu, source)) + return extraits + + +def decouper_markdown(texte: str, source: str, max_car: int = 6000) -> list[Extrait]: + """Un extrait par fichier ; au-delà de `max_car`, un par section `## `.""" + lignes = texte.strip().splitlines() + if lignes and lignes[0].startswith("# "): + titre, corps = lignes[0][2:].strip(), "\n".join(lignes[1:]).strip() + else: + titre, corps = Path(source).stem, "\n".join(lignes).strip() + if len(corps) <= max_car: + return [Extrait(titre, corps, source)] + sections: list[tuple[str, list[str]]] = [(titre, [])] + for ligne in corps.splitlines(): + if ligne.startswith("## "): + sections.append((f"{titre} — {ligne[3:].strip()}", [])) + else: + sections[-1][1].append(ligne) + return [Extrait(t, "\n".join(c).strip(), source) for t, c in sections if "\n".join(c).strip()] + + +def ecrire_corpus(extraits: list[Extrait], dossier: Path) -> None: + dossier.mkdir(parents=True, exist_ok=True) + for e in extraits: + (dossier / e.cle).write_text(f"# {e.titre}\n\n{e.contenu}\n\nSource : {e.source}\n") + + +def lire_corpus(dossier: Path) -> list[Extrait]: + extraits = [] + for f in sorted(dossier.glob("*.md")): + tete, reste = f.read_text().rstrip("\n").split("\n\n", 1) + contenu, source = reste.rsplit("\n\nSource : ", 1) + extraits.append(Extrait(tete.removeprefix("# ").strip(), contenu.strip(), source.strip())) + return extraits diff --git a/base_connaissances/importer.py b/base_connaissances/importer.py new file mode 100644 index 0000000..3a890e6 --- /dev/null +++ b/base_connaissances/importer.py @@ -0,0 +1,131 @@ +"""Pousse le corpus dans la base de connaissances de LibreDesk (les « extraits », privés, lus par l'IA seulement). + +Idempotent : apparie par titre, crée l'absent, met à jour ce qui a changé, ne touche pas le reste. Ne supprime jamais : +un extrait de LibreDesk absent du corpus est seulement signalé. Ne parle qu'aux routes des extraits. Simulation par +défaut : rien n'est écrit sans --ecrire. Il faut une clé d'administrateur (les routes exigent ai:manage). + +LIBREDESK_URL=… LIBREDESK_ADMIN_KEY=… LIBREDESK_ADMIN_SECRET=… python -m base_connaissances.importer [--ecrire] +""" +import html as html_lib +import json +import os +import re +import sys +import urllib.error +import urllib.parse +import urllib.request +from dataclasses import dataclass, field +from pathlib import Path + +from base_connaissances.decoupage import Extrait, lire_corpus + +CORPUS = Path(__file__).resolve().parent / "corpus" +PUCE = re.compile(r"^\s*- ") + + +def html(e: Extrait) -> str: + """Paragraphes séparés par une ligne vide →

(lignes jointes par
), lignes « - » →