Add shape drawing modules#363
Conversation
Summary of ChangesHello @csharon0218, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly enhances the Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request is a great refactoring effort, separating concerns into dedicated modules for kinematics, inverse kinematics, and trajectory generation. The code is well-structured and the new modules are clear.
My review focuses on a few key areas:
- Correctness: I found a critical bug in the Jacobian calculation that doesn't handle prismatic joints, and a numerical instability in the
rot_logfunction. - Security: There's a potential DoS vulnerability from parsing URDF XML with the standard library.
- Maintainability: I've pointed out a few places where code can be made more robust (e.g., exception handling) and more readable by removing redundant type casts.
Overall, this is a solid contribution. Addressing these points will make the code more robust and maintainable.
sunghowoo
left a comment
There was a problem hiding this comment.
- It looks like copy light support should be added.
- A package version update may be necessary.
- There appear to be too many files; merging related files could improve maintainability.
- Explicitly including the OMX model in the naming would improve clarity.
Signed-off-by: csharon0218 <csharon0218@gmail.com>
Signed-off-by: csharon0218 <csharon0218@gmail.com>
fa070d5 to
6898379
Compare
Signed-off-by: csharon0218 <csharon0218@gmail.com>
Signed-off-by: csharon0218 <csharon0218@gmail.com>
Signed-off-by: csharon0218 <csharon0218@gmail.com>
Signed-off-by: csharon0218 <csharon0218@gmail.com>
Signed-off-by: csharon0218 <csharon0218@gmail.com>
yun-goon
left a comment
There was a problem hiding this comment.
There are unnecessary install, log folders.
Please check the EOF.
Signed-off-by: kimtaehyeong99 <kth@robotis.com>
|
This PR has been replaced by the Cyclo Control drawing demo, so I will close it. |
Overview
This PR refactors traj_pub_node.py by separating kinematics, IK, and trajectory generation logic into dedicated Python modules.