Closed senden9 closed 1 year ago
The unit in TimeVector3
should be seconds, so it should be fine
Not sure why it calculates 0 Hz, the calculation is here https://github.com/gyroflow/gyroflow/blob/master/src/core/gyro_source.rs#L802-L805 so I would add debug prints here to see which values it uses
Thanks for answering my question and the hint to the frequency calculation!
Hi!
Background
I am currently implementing a parser for VideoIMUCapture-Android. For the start I planed to just use accelerometer and gyro data from the rich data format provided.
Problem
Gyroflow compiled against my custom version of telemetry-parser can open my data-file but complains that has a data-rate of 0 Hz. The data rate should in fact be 100Hz. I have a 21 second long test-video and gyro2bb detects 2154 samples.
Question
I assume that the time-scale is somehow screwed up. What is the time scale that TimeVector3 expects for its
t
value? Because it is float and not noted future I assumed seconds.More Background / rubber duck programming attempt
I know, the next part could be a bit confusing without the code but maybe there are some useful details in in.
Here is the CSV that gets created when I call
gyro2bb
over on my sample file.I have no idea what the
time
column here should be but because it jumps from 0 to 9793 to 19586 it looks currently it is the time in nano seconds since the beginning of the recording.If I take a look at the first 3 samples that get into my
SampleInfo
I see 144346.848063549, 144346.857856309 and 144346.867649903 as first 3 time stamps. That is a between the first and the second timestamp I see a 0.00979276 seconds difference, between the second and the third timestamp the difference is 0.009793594 seconds. This gives 102HzThis is why I assume my time units are maybe screwed up when gyroscope calculates a data rate of 0 Hz from a file with 2154 samples in about 21 seconds.