InfiniTimeOrg / InfiniTimeOrg/InfiniTime
Sample heart rate proportional to variance / inverse to stable bpm?
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.4k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
Verification
- I searched for similar issues (including closed issues) and found none was relevant.
Introduce the issue
The heart rate sensor appears to keep a history of samples, and the header for the heart rate tracker now appears to try to estimate when to sample. Consider making a togglable option or scale to reduce the frequency of updates, except where variance is high in the event of strange heart activity.
EG: If the ppg samples variance is high, have the background sample rate increase. Similarly if the heart rate is decreasing or increasing, sample more often. I'd imagine variance is more of an important factor.
Preferred solution
No response
Version
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by locating the heart-rate tracker, PPG sample history, and background sampling entry points, then determine how variance and rising or falling heart rate could drive sampling; done means the adaptive behavior is defined, implemented, and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100