Difficult to determine accurate time information for recorded events.

kissake / unattended_data_collection

This is a project intended to support unattended data collection in a way that protects the data being collected. The initial project is aimed at audio recording using a Raspberry Pi Zero (simple, low hanging fruit), with the intention of being extensible for other uses.

GNU General Public License v3.0

0 stars 0 forks source link

Difficult to determine accurate time information for recorded events. #3

Closed kissake closed 2 years ago

kissake commented 2 years ago

Partly / largely as a result of issue #2, timestamps recorded with data is inaccurate. It will be valuable to be able to determine when recorded events occurred.

kissake commented 2 years ago

Short term mitigations for this might include:

Recording timestamps as time relative to boot time, combined with a counter incremented on each boot? (this prevents the time being presented as a full timestamp, which lessens its authoritative appearance)
Updating the documentation to indicate that in this situation (no WiFi) the user should announce the current date/time shortly after recording begins.
- A challenge related to this approach is issue #4, which causes latency between when the microphone is connected and recording begins.

kissake commented 2 years ago

This has been addressed to the extent possible at this time by changes to documentation, and changes to filename generation that highlight the time only when verified with NTP, and otherwise report other information that should be relatively accurate and should help to identify the time of recording with additional information.