-
Notifications
You must be signed in to change notification settings - Fork 939
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
Various Cleanup and Commenting #1180
Conversation
b455b33
to
ca9a8fd
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.
Generally I approve this. However, I don't like the renaming of Transforms::transforms_
to Transforms::transforms_map_
. That's too verbose for my taste.
I'm really into verbose variables, as they improve quick understanding of the code. This is the MoveIt! style throughout the code. The ROS style guide says:
Additionally, I found |
Why didn't you rebased on master to resolve conflicts? |
- Add additional comments - Rename ftf_ to scene_transforms_ - Split up very large processCollisionObject function
- Add some comments - Clarify a few variable names
- Rename transforms_ to transforms_map_ - Add comment
- Clarify console output - Improve comments - Cleanup function flow - Change pr2 example to panda
c183649
to
45e6e86
Compare
I used Github's web-based conflict merging tool, which turned out a mess but it took significant time so I didn't want to start over. I just started over locally and rebased properly. Now it should be Rebased and Merged as the commit history is clean |
Lots of minor, non-behavior cleanup and commenting as I debugged an issue with the planning scene transforms. Changes are cleanly separated by commits and should be Rebased and Merged but not cherry-picked backwards.