Repeat Time stamps in data?

In accelerometer data I collected using a MetamotionC device (similar problem with MetamotionR data), I am having some trouble understanding the time stamps. The device was set to collect data at 12.5Hz, and the data for each second was broken up as follows in the output CSV file:

time (-05:00) elapsed (s) **** x-axis (g) y-axis (g) z-axis (g)
2019-12-04T15.55.05.657 0 -0.125 0.68 0.709
2019-12-04T15.55.05.657 0 -0.126 0.685 0.716
2019-12-04T15.55.05.657 0 -0.125 0.684 0.714
2019-12-04T15.55.05.889 0.232 -0.125 0.684 0.714
2019-12-04T15.55.05.889 0.232 -0.124 0.683 0.717
2019-12-04T15.55.05.889 0.232 -0.125 0.683 0.716
2019-12-04T15.55.06.121 0.464 -0.125 0.683 0.717
2019-12-04T15.55.06.121 0.464 -0.125 0.683 0.718
2019-12-04T15.55.06.121 0.464 -0.125 0.683 0.718
2019-12-04T15.55.06.362 0.705 -0.123 0.683 0.717
2019-12-04T15.55.06.362 0.705 -0.123 0.687 0.718
2019-12-04T15.55.06.362 0.705 -0.123 0.696 0.714
2019-12-04T15.55.06.602 0.945 -0.126 0.665 0.9
2019-12-04T15.55.06.602 0.945 -0.388 2.784 -0.178
2019-12-04T15.55.06.602 0.945 -0.912 2.465 0.99

I'm hoping someone call tell me why the time data is in groups of three data points with the same exact time stamp?

Comments

  • It's not. There's just not enough resolution in the timestamps at the highest Hz (frequency) so you just have to reconstruct it yourself.

  • Do you mean that I have to put all the times in manually every time I use it? 12.5 Hz is the lowest frequency option not the highest...

  • just write a script in python to update timestamps.

Sign In or Register to comment.