Repository navigation
Accuracy check: compare only the time both devices were on - #44
Merged
Merged
Conversation
A flat battery or a charge mid-day passed the 500-step worn test, so the other device read as over-counting by everything after. Each device's off stretches now come from gaps in its own data; partly worn days are compared over the shared hours (or dropped under 12), and nights either device stopped inside are dropped for sleep, resting HR and HRV. Claude-Session: https://claude.ai/code/session_01P1t1aUqSUPd3whKXmgVm7w
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem. A device that ran flat or was put on the charger partway through a day still passed the 500-step "worn" test. The other device then read as over-counting by everything after that point. For example, if the ring dies at 15:00, the reference shows 9,000 steps against the ring's 4,000, and the check reports "ring counts 55% fewer".
The same happened to sleep: a watch going flat at 03:00 made the ring look like it over-reports sleep. These days also fed into the consistent-bias verdict, so they could produce a false correction.
Fix
AccuracyComparison.offGapsfinds each device's off stretches: more than 90 min with no heart rate, steps, sleep or SpO₂ from it.judgeable).amountWithin). The reference's records and the ring's 15-minute buckets are both cut to those shared hours.partly:,night_off:andshared:say which device was off and from when, and translate to pt-BR.Generated by Claude Code