-
Notifications
You must be signed in to change notification settings - Fork 57
Add Pick and Place Harmonic launchers and environment #633
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: humble-devel
Are you sure you want to change the base?
Add Pick and Place Harmonic launchers and environment #633
Conversation
Files added: - Launchers/pick_place_harmonic.launch.py - Gazebo Harmonic launcher - Launchers/pick_place_harmonic_rviz.launch.py - MoveIt + RViz launcher - scripts/.env - GZ_VERSION, GZ_SIM_SYSTEM_PLUGIN_PATH, GZ_SIM_RESOURCE_PATH - database/universes.sql - Universe and world entries (ID 55) - CustomRobots/pick_place_harmonic/ - Robot URDFs and models
|
hi @aleon2020 |
|
Code revised. Take a look at what I mentioned in JdeRobot/RoboticsAcademy#3389 (comment). |
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.
Please remove changes from .scripts/env. This file cannot have anything related to Gazebo Harmonic, this is defined inside the RAM.
Please remove all submodules from CustomRobots, we do not support them
Also define the entries in the database in order, for ex. 53-54-55
I understand the concern. However, after extensive debugging, I found that Gazebo Harmonic requires these environment variables to be set for correct behavior. Since the RAM repository does not currently define an environment file, I assumed it would inherit them from .scripts/env, which is why I added the entries there. At the moment, there is no alternative location in RAM to configure these variables, and without them Gazebo Harmonic fails to work correctly. From my testing, adding these environment variables does not introduce crashes or side effects. If you prefer, I can move these definitions into the RAM repository once a proper configuration file or mechanism is defined there. Until then, keeping them here ensures Gazebo Harmonic compatibility. |
…:- Launchers/pick_place_harmonic.launch.py - Gazebo Harmonic world launcher- Launchers/pick_place_harmonic_rviz.launch.py - MoveIt + RViz launcher- database/universes.sql - Universe (ID 54) and world (ID 54) entries- CustomRobots/pick_place_harmonic/
4ac631d to
8b8238f
Compare
|
We have multiple Gazebo Harmonic exercises that use those variables and there has been no issue. We define them in the RAM and also in the universe launcher. Please take a look at that, because defining it in the .env file will probably break all other universes |
…b.com/anishk85/RoboticsInfrastructure into feature/pick-place-harmonic-launchers
a27fe3c to
7acfbb0
Compare
…:- Launchers/pick_place_harmonic.launch.py - Gazebo Harmonic world launcher- Launchers/pick_place_harmonic_rviz.launch.py - MoveIt + RViz launcher- database/universes.sql - Universe (ID 54) and world (ID 54) entries- CustomRobots/pick_place_harmonic/
7acfbb0 to
46cf160
Compare
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.
There must be no changes in this file
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.
Remove submodules
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.
Remove submodules
| pkg_share_dir = get_package_share_directory("ur5_gripper_description") | ||
| robotiq_pkg_share_dir = get_package_share_directory("robotiq_description") | ||
|
|
||
| <<<<<<< HEAD |
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.
There are conflicts here from a rebase. Please fix them
|
Please fix the issues pointed in the review, it has been more than 2 weeks and they have not been adressed. If not I will close this Pull Request and you will have to open a new one |
|
Yeah I am on it i am actually very busy now a days as we have solved many problems since 2 weeks Like screen black issues and conflicts and improvements in hal api. I will be doing that just give me some time as it's a quite long project. |
1 similar comment
|
Yeah I am on it i am actually very busy now a days as we have solved many problems since 2 weeks Like screen black issues and conflicts and improvements in hal api. I will be doing that just give me some time as it's a quite long project. |
|
None of those are the issues I stated in the PR review |
|
Yeah will do that in upcoming days please don't close as I have invested a lot of time to this now which I don't want to waste |
Files added: