-
Notifications
You must be signed in to change notification settings - Fork 198
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
Modified Luanch files tutorial, added a note to the README. #1008
base: main
Are you sure you want to change the base?
Conversation
…mber funtions. Added note to Launch FIles tutorial about nodes for custom cpp files. Added note to README.md that building Moveit is not needed if only adding explinations, not exectuable code. This is mostly addressing the pain I feel of building MoveIt (3-4 hours on my laptop). Maybe I am an anomily.
As an aside, I would have liked to add more about '.planning_scene_monitor()' regarding when you need to set its parameters to be true, but I haven't found good explanations regarding common uses cases. If you can point me in the direction of where to learn more, I would be happy to add that info to the tutorial. |
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.
Thank you for getting this started!
My first response here is that the information being added is largely already available in other tutorials. I would recommend reading through some of the other pages I've linked in the comments, and seeing if there's a better way to take advantage of cross-linking doc pages, but keeping each individual page focused on a specific subset of topics.
@@ -29,6 +29,8 @@ Below are some links to help with the ports. | |||
|
|||
## MoveIt Tutorials Source Build | |||
|
|||
(This section can be skipped if you aren't adding executable code. You don't need to build MoveIt to add an explanation about something.) |
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 would remove this
``MoveItConfigsBuilder(package_name="package_name")`` will search for a package named "package_name". | ||
``MoveItConfigsBuilder("robot_name")`` will search for an explicitly given package name. |
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.
might be more readable to have this be a bulleted list
@@ -44,10 +44,44 @@ A handy way to refer to a MoveIt configuration package is to use the ``MoveItCon | |||
.to_moveit_configs() | |||
) | |||
|
|||
``MoveItConfigsBuilder`` (`defined here <https://github.com/moveit/moveit2/blob/main/moveit_configs_utils/moveit_configs_utils/moveit_configs_builder.py>`_) can take a few different types of arguments. |
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.
Note there is already another doc page that talks about this -- maybe cross-link / consider putting some of this there?
Launching a custom .cpp file | ||
---------------------------- | ||
|
||
While not part of the Getting Started tutorial, another common node to launch is one that executes a custom .cpp file: |
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.
A custom .cpp
file doesn't sound technically precise -- I think what you may want to say is "a custom executable".
Also, this in isolation may not be entirely helpful if you also don't show a CMakeLists.txt
snippet showing how to actually compile this executable.
But generally, there are other tutorials like https://moveit.picknik.ai/main/doc/tutorials/your_first_project/your_first_project.html which already cover this in full detail.
parameters=[your, | ||
parameters, | ||
here], |
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 wouldn't consider this too helpful because I always forget what the actual format of the parameters is -- it's a list of dictionaries or something? So I may consider using a real, valid input here instead of placeholder text.
Ok, I'll make those edits. Do you know if any of the tutorials discuss the parameters for |
Thanks! Maybe those could be mapped to the concepts page at https://moveit.picknik.ai/main/doc/concepts/planning_scene_monitor.html and/or https://moveit.picknik.ai/main/doc/examples/planning_scene_monitor/planning_scene_monitor_tutorial.html ? |
Yeah, I can start with those. |
If I wanted to cross link to the CMakeLists.txt file in the root moveit2_tutorials directory, how would I do that? |
I believe you can use There are other handy ones for linking to e.g. source code in the MoveIt 2 repo, etc. |
Thanks! |
I may be reading the definition wrong, but it looks like codedir can only reference stuff in the doc folder?
|
It does look that way -- maybe instead of linking to the existing repo's I assume this is just the compilation of a specific executable given source files? |
Description
Launch File tutorial
Added explanations for the member function of MoveItConfigsBuilder.
Added note about launch nodes for custom .cpp files.
Having made these suggestions, I now wonder if I am being too verbose and just cluttering up the documentation when someone wanting to learn more can do what I did and read the source code. So maybe the launch file tutorial should remain unchanged.
README
Added a note that building MoveIt can be skipped if only adding explanations, note any executable code. This is mostly addressing my own pain of building MoveIt (about a 3-4 hour process) and I could see it stopping someone from adding a few helpful comments.
Please explain the changes you made, including a reference to the related issue if applicable
Checklist