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

Benchmark Output Format #85

Open
John-Bonnin opened this issue Sep 9, 2021 · 1 comment
Open

Benchmark Output Format #85

John-Bonnin opened this issue Sep 9, 2021 · 1 comment

Comments

@John-Bonnin
Copy link

From MRip: It probably makes sense for us to save the results of the benchmark into a structured format (like CSV, YAML, JSON, XML, etc.), rather than parsing the text that we arbitrarily wrote to document the benchmark results.

My vote would be to use YAML in a structure like this:

- name: planner_name
  results:
    - n_waypoints: 10
      n_samples: 10
      dof: 6
      build_time: 0.05185
      search_time: 6.2715678
    - n_waypoints: 10
      n_samples: 50
      dof: 6
      build_time: 0.06768
      search_time: 8.123486

@Levi-Armstrong any thoughts on the structure of the benchmark output, especially if we plan to use Google Benchmark in the future?

Originally posted by @marip8 in #78 (comment)

@Levi-Armstrong
Copy link
Collaborator

I am not sure the actual format it outputs but I may be able to generate one from Tesseract benchmarks.

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

No branches or pull requests

2 participants