Closed youtalk closed 3 years ago
Funnily enough I've just finished nearly the same work: https://github.com/OYTIS/create_autonomy (should have subscribed to this repo before doing that of course). The differences I've noticed so far:
I didn't remove the dependency to diagnostic_updater relying on slightly modified this fork: https://github.com/vaibhavbhadade/diagnostics
I've added python launch files that are almost working (somehow I have a problem with leading / in my node name resulting in topics not being exposed - running the node manually doesn't show this problem). You might have done that as well, just forgotten to commit them - at least they are mentioned in your docs.
You've also done linting and test part - I didn't touch that.
Feel free to pull whatever you find useful in my implementation, and I'll try to test yours with my Roomba soon.
Since the change is significant, I think it would be better to replace the existing ca_driver
package with the new code, rather than adding a new package alongside it.
Then we could merge it to a new ros2
branch.
@jacobperron Thank you for your advice. I've changed to replace ca_driver
instead of add ca_driver2
.
@jacobperron Any update on this? Looks like the CI failure is not related to the PR.
While looking into releasing for Melodic and ROS 2, I thought it would be better if the create_autonomy
packages were refactored so that they follow ROS naming conventions and rules (REP 144). I'd like to rename the packages as such:
Therefore, I propose deprecating this repository for Melodic onward in favor of this fork: https://github.com/jacobperron/create_robot
If community members agree with my refactoring proposal, I would direct PRs to the new fork.
Apologies for the slow progress, but this is not my main focus atm. I'll try to get to it as soon as I can.
@jacobperron Thank you for your effort to follow the naming conventions.
If community members agree with my refactoring proposal, I would direct PRs to the new fork. Apologies for the slow progress, but this is not my main focus atm. I'll try to get to it as soon as I can.
If you don't have enough time to maintain the repository, I can continue to maintain and release instead of you. I have already more progress. For example:
ament_lint
It's just my suggestion. I can also continue to contribute to your new repository.
Hi @jacobperron ,
sorry for bothering you. Was there any progress with gathering the feedback from the community? create_robot
looks great in my opinion, would be nice to have the ros2 port applied on top of it.
@OYTIS Not a bother at all!
I did get some feedback, but I can't remember if there is a public thread I can point to. In any case, we should be able to move forward with the renaming of the create_autonomy packages as I proposed above. Unfortunately, I haven't had time to work towards a Melodic release or a ROS 2 port. Pull requests are welcome at https://github.com/jacobperron/create_robot.
Once things are settled on my fork, I'd like to merge everything back to this repository (and rename the repo on GitHub). This way any existing links to the repository should be properly redirected by GitHub.
I've finally done the renaming I wanted and merged everything back upstream. In addition, a ROS 2 port was completed: https://github.com/AutonomyLab/create_robot/tree/foxy
Therefore, I'll close out this PR. Feel free to open up further PRs for any improvements to the ROS 2 implementation targeting the foxy
branch.
This PR is my first trial to migrate the
create_autonomy
package to ROS 2 Crystal environment.I created a new
ca_driver2
package instead of theca_driver
package migration, because the difference is huge. This branch can be built with https://github.com/AutonomyLab/libcreate/pull/42 branch. To build these packages, please read the updatedREADME.md
or follow the process:After merge this PR, I will continue to update:
ament_lint
,dinagnostic_updater
(there is no ROS 2 migration yet).Thank you in advance. Your
create_autonomy
andlibcreate
packages are very helpful for my daily life with robot.