Skip to content
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

Control Legend Settings and rename curves in plots #685

Closed
Johnemad96 opened this issue Jul 13, 2024 · 1 comment · Fixed by #698
Closed

Control Legend Settings and rename curves in plots #685

Johnemad96 opened this issue Jul 13, 2024 · 1 comment · Fixed by #698

Comments

@Johnemad96
Copy link

Johnemad96 commented Jul 13, 2024

Hello,
I am not sure how do I choose the pose of the legend on the plot when using "evo_config"
also, how can I change the name of every plotted line in the trajectory. (or I can just rename the trajectory file)

thanks

@MichaelGrupp MichaelGrupp changed the title Control Legend Settings Control Legend Settings and rename curves in plots Jul 17, 2024
@MichaelGrupp
Copy link
Owner

how do I choose the pose of the legend on the plot when using "evo_config"

This is not possible in the current version. The behavior of the legend is the default matplotlib positioning "best", see the loc parameter described here:
https://matplotlib.org/stable/api/_as_gen/matplotlib.pyplot.legend.html

Should be possible to make the loc a configuration parameter in evo, I could add that.

how can I change the name of every plotted line in the trajectory. (or I can just rename the trajectory file)

The names are coming from the file names (or topics, if ROS bagfiles are used). So renaming files will change it. If you only want to change it for a plot, you could also change it in the plot window interactively.

image
image

Note: this works only if Qt5 is used as matplotlib backend, as explained here in this similar ticket: #648 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants