About ROS1 version
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 381
- Forks
- 54
- PR merge metrics
- No merged PRs in 30d
Description
Thanks for your amazing work for the community! I've stared the project, and will continue to follow the work in the furture！I have a few questions about the work:
-
Are you planning to relsease the ROS1 version of source code of the code? (ROS1 noetic)
-
We're doing some local path planning work based on the humanoid robots like unitree G1, agile robot, and kuavo robots. Does mighty support these robots based on bipedal kinematics models based, or what kind of changes should we make if we want to deploy the code on the unitree G1 humanoid robots?
Thanks for your contributions on the community！I will learn and read your code and papers more detailedly and follow your work closely!
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
The issue names no files, tests, or entry points. Start by reading the ROS 2 source code and the project papers to determine the supported interfaces and robot assumptions; a useful outcome would need a decided scope for ROS1 Noetic support or Unitree G1 and other humanoid deployments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- robotics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100