You are reading a single comment by @HughB and its replies.
Click here to read the full conversation.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
@HughB
Tested Run 0.06 and Recorder 0.09
Unfortunately due to the Recorder settings CRASH issue my test is invalid.
The GPS on Run will have taken fixes every 1 second and stated I had done 4.2m which I know was about right. I did almost 8k steps. The recorder was unfortunately set at 10 second intervals (and I could not have changed it due to the bug reported) so downloading the recorder GPX file and loading it into view ranger says I only did 3.56 miles. But when you look at route it is not following the path as it is skipping points. To be expected. If we want these to come out the same then I think Run and Recorder MUST use the same recording resolution. There is an argument for an interface to the recorder that says start the recorrder client=run, use these parameters for the recording.
I also recorded heart rate data as I wanted to compare against an Amizfit Bip and see exactly where heart rate is failing. But my data is going to be fairly useless. I was attempting to test for my max heart rate and recorded 174 on the Amizfit at one point.
A few question arise: For Heart rate in the recorder do we use the confidence value at all, do we take a rolling avarage say ? On Bangle 1 I came to the conclusion that confidence was a waste of time and it was better ignored and heart rate averaged.
What does source mean in the CSV output ?
I have attached the CSV file if it will help anyone. Really dissappointed that the settings was every 10 seconds. I had set it that was before but really think the client app should be passing the settings across to the recorder. Going to be next weekend before I can do a really thorough test like this again.
2 Attachments