ruvnet / ruvnet/RuView

Test environment setup for validated HR/BR/pose accuracy — ADR-079 follow-up

Open
#685 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
Rust
Stars
94.4k
Forks
12.5k
Avg merge
21h 27m
Merged PRs (30d)
43

Description

Hi @ruvnet,

I'm using wifi-densepose with Lonely Binary ESP32-S3 nodes for a vital signs monitoring project. I've done a deep review of the codebase including ADR-079, ADR-069, and the CHANGELOG.

I have a few questions about your validated test environment:

  1. Room setup: The repo mentions 4×4m, 4×5m, and 5×4m in different docs. What room dimensions did you use when achieving your best HR/BR accuracy results?

  2. ESP32 placement: ADR-079 mentions camera FOV must cover the sensing volume. What height and positions worked best for vitals detection specifically?

  3. HR/BR validation: ADR-069 says "vitals ranges checked" but I couldn't find a published accuracy comparison against ground truth (oximeter etc.). Did you validate HR/BR against a reference device? If so what accuracy did you achieve?

  4. ADR-079 P7-P9 are marked Pending — is there a branch or fork where the camera-supervised training pipeline was completed?

Any guidance on your validated setup would help me uerstand how close I am to your best results.

Thanks for the great open source work.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with ADR-079, ADR-069, and the CHANGELOG, then trace the referenced P7-P9 status and any documented test setup. Compare the room dimensions, ESP32 placement, and HR/BR validation details requested in the issue. Done means the repository documents the validated setup, reference-device accuracy, and whether a completed training branch or fork exists.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
documentation, embedded-iot
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.