-
Notifications
You must be signed in to change notification settings - Fork 26
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
release as deb package for hydro #4
Comments
Hi k-okada, has this been tested at all? I think it's missing testing on a real robot and with simulation. I'm going to go ahead and release this anyway as I don't believe anyone will be using it immediately or trying to at least. |
No I have not tested, but due to everyone is talking that EOL of groovy, I think we should release this ans ask for testing on real robot and/or simulation. |
Sure. I attempted to release this on Thursday-ish, but I ran into some permissions issues with the bloom command. Are you able to release this? The repo for pr2_navigation has been created |
ok, but could you give me a permission to pr2_navigation-release repo? or could you show me the error message of the bloom command? |
https://github.com/orgs/PR2/teams/package-release Added to package-release teams. Let me know if you need anything else to release the package. |
@k-okada At Bremen, we have so far run our navigation and localization code still under Groovy. Today, we played around with the new catkinized code out of the hydro-devel branch of this repo. Thanks for providing this! However, we ran into several problems, e.g. compilation of pr2_navigation_self_test, running stuff out of the overlay on c2, finding some of the plugins... Before we try to debug these issues in Bremen, have you already got this meta-package running and working in your lab? If yes, what setup or top-level launch-file do you use? If no, I'll keep you posted and provide pull requests as we go along. :) Just for reference, here is the relevant excerpt out of our launch-file (so that you know what we tried to run):
|
Unfortunately I haven't test these code, just to confirm it is working in catkin, I'll check this on our robot during this week with @aginika |
@airballking You may have resolved the problems already, but we tested on the real robot with rviz 2d_nav_goal and made sure that navigation seems to work in our environment. Lasers are correctly took into account and the obstacles is shown in costmaps.
Sorry for being late. |
if someone create pr2_navigagtion-release repository, I think I can help you, to run bloom to create configuration files and send PR to you.
The text was updated successfully, but these errors were encountered: