Logs go back in time
Posted: Mon May 29, 2017 11:07 pm
Using the latest mk3 firmware (2.11.0 I believe). Had the initial log timestamps go back in time a few ticks. Found this because it really made RaceRender screw up.
The first four timestamps are as follows:
1495205968458
1495205968378
1495205968448
1495205968458
Note how it goes back in time for two ticks then forward to the first timestamp.
Arguably this might not be a bug since while the data is out of order chronologically it's still valid as the timestamp is present, but I think it can throw off some data analysis tools and might want to be addressed if possible. This came up because the timestamps above caused RaceRender v3.5.7 to have extreme problems processing this log (removing the first three log lines fixed the issue).
Here's the google drive link to the log as I wasn't able to attach it.
https://drive.google.com/file/d/0BxW92Z ... sp=sharing
The first four timestamps are as follows:
1495205968458
1495205968378
1495205968448
1495205968458
Note how it goes back in time for two ticks then forward to the first timestamp.
Arguably this might not be a bug since while the data is out of order chronologically it's still valid as the timestamp is present, but I think it can throw off some data analysis tools and might want to be addressed if possible. This came up because the timestamps above caused RaceRender v3.5.7 to have extreme problems processing this log (removing the first three log lines fixed the issue).
Here's the google drive link to the log as I wasn't able to attach it.
https://drive.google.com/file/d/0BxW92Z ... sp=sharing