-
Notifications
You must be signed in to change notification settings - Fork 10
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
Remove val_gazebo from package.xml. #17
Conversation
Matches changes to the controller on the 0.9-support branch, attempting to fix joint state publishing for the head in Gazebo.
Looking into this now. Is the val_gazebo package no longer available? Or do you want the option to run ihmc_valkyrie_ros without needing all the srcsim stuff? |
I'm assuming it would have been one of the projects listed here: https://gitlab.com/nasa-jsc-robotics (also has r2_gazebo for example). It's not currently in that list. |
@tkoolen are you logged in and added to the private repositories? I can see it. Edit: @gizatt,@manuelli, @mit.valkyrie are in the access list. It's required in the dependency list as some of the launch files launch the simulator contained therein for the srcsim (for which there are debians and instructions over on bitbucket/osrf/srcsim). |
It looks like val_gazebo is only available from one of OSRF's apt repositories. Setup instructions are here: |
Yeah, perhaps moving the Gazebo-dependent launch scripts to their own package might be a good solution; it seems a little silly to have to install the whole SRCSim stack on the onboard computers. Alternatively/additionally, I think a clear set of instructions for installing the IHMC software stack on the onboard computers should be provided. I scraped together these instructions from various sources: https://docs.google.com/document/d/1YUi9qJ8nmFPg0sZgWqOUFnBXqz4EHWJPe8aY3wy0CKs/edit?usp=sharing. |
This has been merged into develop. Looks like GitHub didn't recognize it automatically though. Guessing that's because there was also a change in one of the launch files that I had to revert (your branch was using valkyrie_A instead of valkyrie_sim). @tkoolen would you mind creating a separate issue for adding the install instructions? And then subsequently remind us to look at it several months later? 😉 |
Apparently this is an open issue with GitHub. |
Fixes the following error during the rosdep install process: