-
Notifications
You must be signed in to change notification settings - Fork 73
Update ergoCubSN002
conf files from robot fork
#740
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: devel
Are you sure you want to change the base?
Conversation
…and noise rejection. right arm skin aligned though not streaming data
…, before the fingers
…prefix and removed POS wrappers
…llm task planner structure
…nfiguration for right arm
Move the cursor back to 0 0
…ing llmGUI After recent updates of llm_task_planner
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @pattacini, 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 integrates the latest configuration updates for the ergoCubSN002
robot, focusing on comprehensive adjustments across its hardware, calibration, and software application layers. The changes aim to enhance the robot's operational capabilities, particularly in areas related to head and arm control, tactile sensing, and advanced AI/LLM integration within a multi-robot framework.
Highlights
- Configuration File Synchronization: This pull request primarily synchronizes the
ergoCubSN002
robot's configuration files with updates from a robot fork, ensuring the latest operational parameters are in place. - Head Subsystem Updates: The head's electronic board, mechanical, and motor control configurations have been significantly updated, including renaming files (e.g.,
j0_1
toj0_2
,j2_3
toj3
), adjusting calibration parameters, and introducing new detailed mechanical and motor control XMLs with updated PID settings and limits. This also affects the head's IMU and motor control remapper. - Arm and Hand Calibration Refinements: Calibration parameters for the left and right arms, including
calibration1
,calibration4
,calibration5
,startupPosition
, andCALIB_ORDER
, have been adjusted. Hand position sensor offsets and rotation parameters have also been updated, along with minor adjustments to joint position limits for the fingers. - Skin Sensor Configuration Changes: The skin GUI configurations for both left and right hands have been completely revised, replacing old sensor types with
triangle_10pad
andfingertipMID
and updating their placements. The total taxel count and ranges for the arm skin wrappers have also been adjusted. - Application and Cluster Enhancements: A new YARP application (
xbgTwoRobots001.xml
) has been added to support a multi-robot setup, integrating various modules for perception, control, and LLM interaction. Existing applications likeami-xbg.xml
have been updated with new paths, parameters, and connections for depth cameras and emotion handlers, indicating deeper integration with AI/LLM functionalities. The YARP cluster configuration has been expanded to include new nodes for LLM processing and a second robot (ergocub000
). - Sensor and System Parameter Adjustments: The Realsense camera configuration now includes
stereoMode
and support for IR cameras. Variousshutdown
levels for inertial wrappers have been standardized, and theskin.xml
's port prefix has been changed fromicub
toergocub
.
Using Gemini Code Assist
The 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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
Feature | Command | Description |
---|---|---|
Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
Help | /gemini help |
Displays a list of available commands. |
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 .gemini/
folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist is currently in preview and 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 to provide feedback.
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
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request updates various configuration files for ergoCubSN002
, likely synchronizing them from a specific robot's operational setup. The changes are extensive and cover calibration parameters, hardware definition files, application configuration files, YARP cluster configuration, skin GUI configurations, realsense camera settings and a global change in YARP port prefixing. My review focused on portability and correctness.
/remind June 25 We will get back to this PR after an important demo that will take place on June 23. |
⏰ Reminder
|
As per the title.