-
Notifications
You must be signed in to change notification settings - Fork 7
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
Tutorial for External Controller C++ Template #29
Conversation
Signed-off-by: Michael Anderson <anderson@mbari.org>
|
Signed-off-by: Michael Anderson <anderson@mbari.org>
Signed-off-by: Michael Anderson <anderson@mbari.org>
Signed-off-by: Michael Anderson <anderson@mbari.org>
Signed-off-by: Michael Anderson <anderson@mbari.org>
Signed-off-by: Michael Anderson <anderson@mbari.org>
Signed-off-by: Michael Anderson <anderson@mbari.org>
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.
Mostly stylistic comments to make things more clear.
I assume the next tutorial linked at the bottom is going to tell me how to compile and run my awesome controller, right?
Co-authored-by: Mabel Zhang <mabel@openrobotics.org>
Co-authored-by: Mabel Zhang <mabel@openrobotics.org>
Co-authored-by: Mabel Zhang <mabel@openrobotics.org>
Co-authored-by: Mabel Zhang <mabel@openrobotics.org>
Co-authored-by: Mabel Zhang <mabel@openrobotics.org>
I added some stuff at the bottom for just sanity checking the bare controller after all the mods |
Signed-off-by: Michael Anderson <anderson@mbari.org>
@mabelzhang modified per your feedback |
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.
Nice! Thanks for the non-trivial formatting effort.
Just got on the dev computer and tried out the new compile/run instructions. A few suggestions.
Signed-off-by: Michael Anderson <anderson@mbari.org>
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.
Thanks for iterating!
|
||
2. Next, set up the repository like you would any new GitHub repository choosing the owner, | ||
repository name, public/private, etc. | ||
3. Make a ROS 2 workspace |
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.
How will this package be structured wrt to the buoy simulator, when one is using it from source vs binaries? Like in the same ws while building from source and creating a new ws when using binaries (would be relevant once we release).
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.
I suppose I was thinking that for a source build of the buoy packages, there would be a separate workspace for those packages and the user would put the source ~/buoy_ws/install/setup.bash
in their .bashrc
. Then, whatever packages they wanted on top, like the external controller, would be in another workspace. I sort of hinted at that structure in the Build, Test, Run
section at the bottom, but we could be more explicit once we have some more concrete ideas of how it's all laid out. Obviously, someone familiar with ROS could put the packages in the same workspace without us explicitly telling them to.
└── src | ||
└── controller.cpp | ||
``` | ||
|
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.
Suggestion on how to build the package could be useful too
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.
I have a section at the bottom for Build, Test, Run
Oops didn't refresh before submitting the review |
No worries! If you have any suggestions, I can throw them in the PR for the python linear damper tutorial, or make another PR |
A general suggestion I had that both tutorials could use is adding package building steps as well. |
https://osrf.github.io/buoy_entrypoint/pr-preview/pr-29/Tutorials/ROS2/CPPTemplate/
part of #27