-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Axivity AX3 drift in data after using export CSV #42
Comments
Apologies for the late response. The AX devices were explicitly designed to capture the raw output from an underlying sensor – which includes the fact that it will have a slightly variable rate output that will differ slightly to the rate the sensor is configured at. Other loggers typically decide to resample this output at a fixed rate on the device itself – but this can lead to aliasing/blocking artifacts, and it’s better to leave these sort of decisions to be performed later in software, if required. To allow later reconstruction of times, a real-time clock value (initially set when the device is configured, but free-running afterwards) is noted for each batch of data from the underlying sensor. A timestamp (and offset to the batch) is stored once per “sector” (every 40/80/120 samples depending on device/configuration). This results in some of the samples having a timestamp – these timestamps can be interpolated in software after the fact, and/or this can be used to resample the data. If you are using OmGUI’s CSV Export options, it is worth noting:
If you are recording over a longer period of time and/or if you are trying to synchronize with another device's time-stamped measurements, you may have to consider "clock drift" -- please see: |
Hi everyone, I am currently doing a research project using Axivity AX3 accelerometers more precisely a step algorithm validation study using video to determine the true values. During my data analysis i realized that there is some kind of drift in the data after exporting it as csv. More precisely, video and acceleration signal match as displayed in the GUI (graph) but there is an increasing time difference when i look at the data, which I exported with the Export Raw CSV option. The error is around 30 sec per hour of video, which is quite significant in my case.
Accelerometer settings: +-50Hz and +-8g.
OMGUI Version: Downloaded 11/2020
I will try to reinstall the Programm and see if my issue is fixed in a newer version.
If that does not work I will try to come up with a reproducible example for you.
The text was updated successfully, but these errors were encountered: