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

Add benchmarks #2124

Open
felixvd opened this issue Jun 2, 2020 · 0 comments
Open

Add benchmarks #2124

felixvd opened this issue Jun 2, 2020 · 0 comments
Labels
enhancement moveit day candidate This issue can likely be resolved in less than a day

Comments

@felixvd
Copy link
Contributor

felixvd commented Jun 2, 2020

As discussed in maintainer meetings in the past, and as demonstrated in this thread, performance benchmarks would be very useful to compare the impact of changes we consider integrating into MoveIt. Good benchmarks let developers estimate how calculation speed and precision are affected in different situations. Here is an example.

Potential benchmarks could be:

  • "Simple" calls to IK
  • Motion planning through scenes of differing complexity (e.g. tight spaces, many objects) using different planners
  • Constructing a planning scene
  • Updating collision objects in the planning scene (e.g. an octomap from one or multiple sensors)
  • More realistic applications (e.g. pick-place tasks, or the MoveIt Task constructor demos)

A simple benchmark can be a good MoveIt Day project.

Related reading: 1, 2

@felixvd felixvd added enhancement moveit day candidate This issue can likely be resolved in less than a day labels Jun 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement moveit day candidate This issue can likely be resolved in less than a day
Projects
None yet
Development

No branches or pull requests

1 participant