Time logs overlap
The recording sessions overlap both in epoch, character written time and automatically generated file labels. I used MMR and android 7. My naming is the actual yr.month.day.hour of downloading the logs.
20.3.8.0_MetaWear_2020-03-08T07.05.34.551_ Accelerometer_1.5.0.csv
20.3.7.1_MetaWear_2020-03-06T18.51.15.607 Accelerometer_1.5.0.csv
20.3.6.18_MetaWear_2020-03-06T22.02.06.060 _Accelerometer_1.5.0.csv
This discussion has been closed.
Comments
If the values in the overlap are correct, what is the problem? What is the bug?
They are not correct. I only have one MMR to log with and as my manual stamps show the date on one is completely off. specifically your timestamp should be about 6 hours ahead of mine 20.3.7.1_MetaWear_2020-03-06T18.51.15.607 Accelerometer_1.5.0.csv
Post data and bug details or this thread will be closed.
I cannot think of any details that I have not already provided.
It looks like you started your logging session around 18.51.15.607 and logged for ~5.5 hours. So of course when you download the data, it would be the next day.
No. According to the csv millisecond epochs, I recorded two different sessions from one MMR at exactly the same time.
Can you back your claims with actual data? Can you show details of this? You haven't really pointed to anything specific. You just finally uploaded random files but we are not going to look through them for you...
I am using Metabase app, not my own app. The graph accomplishes the analysis. Those two line segments that almost completely eclipse each other on the Y axis are two 8 hour recordings done on completely different days. This is a bug that I a m reporting. I do not think it reoccurs often.
I did look at your data in more details. There is only one overlap in timestamps between two (out of three) of your time series. It occurred in this time frame:
A few possibilities:
1. The log wasn't cleared fully between downloads
2. Different devices were used to download the data
If you are able to replicate this with more details then we can look into this. Otherwise I am closing this thread but will relay the information to our engineering team.