Expose per-glove health and data freshness in the Avatar SDK and Isaac Teleop plugin
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 35/100
- issue の種類
- 機能追加
- 明瞭さ
- 明確に書かれている
- 活発さ
- 活発
- 技術スタック
- python
- 領域
- api, backend, observability
調査の方向性
Start by locating the Avatar SDK and Isaac Teleop plugin health reporting entry points, then read how existing device health entries are represented. Define per-glove identity, connection and streaming state, freshness semantics, and reason codes, and propagate them through the plugin. Done means the acceptance scenarios distinguish startup, glove and dongle failures, timeout, and recovery without robot actuation.
索引モデルが issue の本文から書いたものです。
説明
Summary
Please expose machine-readable health information for each Avatar glove and surface it through the Isaac Teleop plugin's health reporting.
Downstream applications need to distinguish a running plugin from a glove that is connected and actively providing fresh data, without parsing console logs.
Current behavior
In our integration, the Avatar plugin appears only as:
- Device entry:
inventory:unmonitored:sharpa_avatar - Health:
unknown
During a reported incident, both gloves logged "no data for 3 s", but the dropout was not reflected in the health output.
For comparison, the Manus integration reports individual devices as manus_hand_plugin/hand/{left,right}, with status and reason. We would like equivalent visibility for Avatar gloves.
Related troubleshooting has also encountered a missing/unresponsive USB dongle and absent hand data. These are additional scenarios the health interface should help diagnose, not a confirmed explanation for the dropout above.
Requested capability
Please provide a supported SDK API and/or callbacks exposing:
- Per-glove identity and handedness, so left and right can be monitored independently.
- Connection and streaming state, distinguishing connection from receipt of fresh samples.
- Data freshness, such as the last valid sample timestamp or elapsed time since the last valid sample, with documented clock semantics.
- Machine-readable reason codes, plus a human-readable explanation where available.
- Transport/SDK status, distinguishing a shared dongle or initialization failure from a single-glove problem.
Please propagate this information into the plugin's health reporting so downstream applications can consume it alongside other device health entries.
If the SDK cannot determine the underlying cause, report a factual condition such as "no recent data" rather than assigning an unsupported diagnosis.
Acceptance criteria
- Left and right gloves have independently identifiable health entries.
- A glove with fresh valid data is distinguishable from one that is connected but not streaming.
- Missing data beyond a documented timeout changes the affected glove's health and reports an actionable reason.
- A one-glove failure does not incorrectly mark the other glove as failed.
- A missing or disconnected dongle is visible through structured health information.
- Health recovers when fresh valid data resumes—not merely when the process or transport reconnects.
- Startup/waiting, unsupported health reporting, and an actual runtime failure remain distinguishable.
Validation
Please cover the following scenarios in a bench setup without robot actuation:
- Startup without gloves.
- Normal two-glove streaming.
- Loss of one glove.
- Loss of both gloves.
- Dongle removal and reconnection.
- Recovery after a data timeout.
- 主要言語
- Python
- スター
- 412
- フォーク
- 97
- 平均マージ
- 2日 3時間
- マージ済み PR（30日）
- 141
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
NVIDIA/IsaacCapture のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
NVIDIA/IsaacCapture#910 ·
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 88/100
NVIDIA/IsaacCapture#891 ·
メンテナーはふだん 1 日以内に返信
-
Add OneRobotics A1 asset and Isaac Teleop example対応中かも @WangXuechun-woan が 3 日前に担当しました。 オープン
難易度 5/5 1週間以上 初心者へのやさしさ 35/100
NVIDIA/IsaacCapture#1291 · コメント 2 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 4/5 3〜5日 初心者へのやさしさ 25/100
NVIDIA/IsaacCapture#1217 ·
メンテナーはふだん 1 日以内に返信
-
難易度 3/5 1〜2日 初心者へのやさしさ 20/100
NVIDIA/IsaacCapture#1214 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
NVIDIA/IsaacCapture の issue をすべて見る
似ている issue
-
good first issue infrastructure
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
kuznia-rdzeni/coreblocks#1135 ·
-
good first issue server
難易度 2/5 1〜3時間 初心者へのやさしさ 85/100
メンテナーはふだん 1 日以内に返信
-
documentation priority: high
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
a-lex-s/mealie-telegram-bot#54 ·
メンテナーはふだん 1 日以内に返信
-
type/test
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
SaltedTan/virgil-language-server#218 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 83/100
btclib-org/btclib-wallet#541 ·
メンテナーはふだん 1 日以内に返信