WIP: Tutorial - #57
Open
captain-yoshi wants to merge 1 commit into
Open
Conversation
simonschmeisser
approved these changes
Apr 24, 2022
| *You can swap the legends and labels params to have planners as legends and the collision detectors as labels* | ||
|
|
||
|
|
||
| To get the full picture, it is often necessary to display several metrics as subplots. If your want to know which of the planners is the fastest in a given scenario, well it's a good idea to compare it against the solved metric, because a planner can be really quick at not solving a goal! Sadly, GNUPlot is not able to automatically resize a multiplot. However, the terminal size is configurable at runtime. You can also use the SVG terminal to somewhat bypass the resize limitation. |
Contributor
There was a problem hiding this comment.
Suggested change
| To get the full picture, it is often necessary to display several metrics as subplots. If your want to know which of the planners is the fastest in a given scenario, well it's a good idea to compare it against the solved metric, because a planner can be really quick at not solving a goal! Sadly, GNUPlot is not able to automatically resize a multiplot. However, the terminal size is configurable at runtime. You can also use the SVG terminal to somewhat bypass the resize limitation. | |
| To get the full picture, it is often necessary to display several metrics as subplots. If you want to know which of the planners is the fastest in a given scenario, well it's a good idea to compare it against the solved metric, because a planner can be really quick at not solving a goal! Sadly, GNUPlot is not able to automatically resize a multiplot. However, the terminal size is configurable at runtime. You can also use the SVG terminal to somewhat bypass the resize limitation. |
| +------------------------------------------+------------------------------------------+ | ||
|
|
||
|
|
||
| We now want to compare the collision detector FCL against Bullet with the same parameters as above. This will double the previous boxplots because we are adding another collision detector and thus plot 12 boxplots (RRTstar is still filtered**. If this is too much information you can still filter out additionnal planners. Let's use the ``legends** parameter to bring out the comparision even more. |
Contributor
There was a problem hiding this comment.
Suggested change
| We now want to compare the collision detector FCL against Bullet with the same parameters as above. This will double the previous boxplots because we are adding another collision detector and thus plot 12 boxplots (RRTstar is still filtered**. If this is too much information you can still filter out additionnal planners. Let's use the ``legends** parameter to bring out the comparision even more. | |
| We now want to compare the collision detector FCL against Bullet with the same parameters as above. This will double the previous boxplots because we are adding another collision detector and thus plot 12 boxplots (RRTstar is still filtered**. If this is too much information you can still filter out additional planners. Let's use the ``legends** parameter to bring out the comparison even more. |
|
|
||
| .. |plot1| image:: planners.svg | ||
|
|
||
| Let's try to plot this: ``Planner's vs Time``. The plot below isin't what we expected ? Given the number of combinations in the dataset, we see the RRT planner againt 3 different scenes, 2 collision detectors as well as 2 motion plan requests. That gives a total of 12 boxplots per planner! |
Contributor
There was a problem hiding this comment.
Suggested change
| Let's try to plot this: ``Planner's vs Time``. The plot below isin't what we expected ? Given the number of combinations in the dataset, we see the RRT planner againt 3 different scenes, 2 collision detectors as well as 2 motion plan requests. That gives a total of 12 boxplots per planner! | |
| Let's try to plot this: ``Planner's vs Time``. The plot below isn't what we expected ? Given the number of combinations in the dataset, we see the RRT planner against 3 different scenes, 2 collision detectors as well as 2 motion plan requests. That gives a total of 12 boxplots per planner! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add tutorial with multiple plotting outputs.