Activity detection related parameters

[viesti]

Platform your question concerns:

• Android
• iOS
• Other
• Platform is not relevant for this question

SDK version:
6.4.0

Firmware version
2.0.8

Customer app url
https://apps.apple.com/fi/app/endor-global/id6744930227

Device:

• Grit X2 Pro
• Vantage V3
• Vantage M3
• Polar OH1
• Polar Verity Sense
• Polar H10
• Polar H9
• Polar 360
• Other
• Device is not relevant for this question

Description:

We are observing that for some users, a lot of activity is detected via 247 HR, by looking at highActivity trigger. We suspect that the activity detection might not be adaptive, and users with high average heart rate get reported more activity.

We currently have static values assigned to FTU data, and should probably improve on that.

But it would be interesting to know how FTU configuration is used, if at all, in activity detection. Which FTU attributes are used and if so, how?

Another question is that if we see change based on history of HR data (or other data we gather), should the FTU be called again? For example, there is typicalDay attribute in FTU, this might change say based on the workplace of use (say from mostlySitting to mostlyMoving).

It would be good to understand which analyses use FTU data and how, so we can provide good values for FTU and possibly perform FTU again if user profile changes (maybe even automatically).

Currently we use the following analyses from Polar 360 device: sleep, nightly recharge, steps, and 247 HR.
We also gather HR and skin temperature via offline recording, and stream PPI during specific sessions.