OpenDriveLab / OpenDriveLab/RoboNaldo
Clarification on motion_anchor_pos_b semantics between training and real-robot deployment
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 53
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Hi, thank you for releasing the training and deployment code.
I am trying to understand how motion_anchor_pos_b is reproduced on the real robot without motion capture or global torso-position estimation. After comparing the paper, the training repository, and RoboNaldo_Deploy, I found what appears to be a significant difference in observation semantics.
Contributor guide
No contributing guide indexed for this repository
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
Compare the paper, the training repository, and RoboNaldo_Deploy, focusing on how motion_anchor_pos_b is defined and constructed in each observation pipeline. Trace the deployment observation entry point and document whether the training and real-robot semantics match, including what information is available without motion capture or global torso-position estimation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- robotics
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100