Hi, you are welcome to drop us a note directly via info@movesense.com if you want to discuss the device use in more detail. In general, there is no secret sauce at all: the sensor API is open and you get full access to raw data (ECG, 9-axis IMU at different sample rates). If you want to run your own algorithms on board, you can modify the sensor firmware (C++) with our developer tools.

Companies that use Movesense sensors as a platform to develop their own commercial products naturally have their own ways of analyzing and visualizing the data they measure with the sensor. In commercial projects, companies rarely publish the algorithms they have developed, but some such cases can be found in the Movesense community.

As it comes to sensor accuracy & scientific projects, here is a list of publications and validation studies: https://www.movesense.com/publications/

Best regards, Terho Lahtinen /Movesense

Thanks for dropping by! Yeah it's hard to think of a way to analyze and present the data that would be both 100% "transparent" and useful for all applications. Realistically, With all the data available from these sensors, that's probably not possible :-)

Interesting, thanks for sharing, it looks like it has similar core sensors to the Polar H10, but I'm not sure how it compares overall

Well, the MD I linked to in [2] above, claims that it's more precise for HRV IIRC. Something about sample rates and filters and skewing of the waveform impacting HRV measurements since they depend on precisely locating waveform peaks. (he has a bunch of posts about the Movessense sensor, so I might not have linked the best one)