Files
aimsight-libredesk/snippets/textes/which-timezone-is-used-for-timestamps.md
T
maximeandClaude Opus 5.5 10ed887417 Noms plus clairs : snippets/, scripts de test numérotés, verifier_ollama.py
- base_connaissances/ → snippets/ (corpus/ → textes/, instructions.md → consignes_redaction.md, decoupage.py → fichiers.py, importer.py → envoyer.py) ; python3 -m snippets.envoyer.
- instance-de-test/ : 1_demarrer.sh, 2_creer_boite_et_cle.py, 3_brancher_ia.py, 4_essayer_brouillons.py, voir_empreintes.sh, connexion_admin.py.
- ollama/verifier.py → ollama/verifier_ollama.py ; tests, tâches VS Code et docs alignés.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-12 10:27:06 +01:00

18 lines
792 B
Markdown

# 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