In the last quarter, I set myself the following objectives:

1. Improve device setup:
2. Improve data post-process and robustness:
3. Dash cam comparison

I worked a lot of (1) and (3) but didn't have that much time for (2)

Improve device setup

I built an enclosure for the device. It is now easier to transport with me all the wore that are now contained inside one box.

I also printed a small adapter which allow me to attach the IMU device to the computer holder on my bike. 

I didn't have the chance yet to get proper measurements on my bike as this was shaking too much and got miss-connection. Now that I glue the wire I hope to get better results the next time I am going out with the device.

Dash cam comparison

(See video attachment)

The Hero 9 black has an embedded IMU and GPS device that I use to measure the vibration data. Here how I proceeded to get the following video

How

1. Extract the telemetry data of the GoPro
   1. I must say I thought this would be easier but thanks to the following library I was able to extract the telemetry data without cost.
2. I use the library I presented in the V2 log to process the data the acceleration data of the GoPro
   1. Note: since the GoPro wasn't oriented on a particular axis, I simply used the norm of the acceleration data to measure the vibration component.
3. I used ffmpeg to extract image frames of the video
4. I used PIL, plotly to overlay the metric on every frame
5. Recombine the video using ffpeg

Review

• I am quite satisfied with the overlay of the metric and quality of the road on the video. I think the metric represents quite well in general the quality of the road. 
• I was quite surprised with the inaccuracy of the GPS components. To some extent, I thought I had made an error in the coordinate reference system at first, but I validated and both the GoPro and Plotly should be using wgs84. Maybe there is something else I forgot, very open to suggestions here.