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

Infrastructure meta-ticket #26

Open
1 of 4 tasks
mabelzhang opened this issue Mar 29, 2024 · 1 comment
Open
1 of 4 tasks

Infrastructure meta-ticket #26

mabelzhang opened this issue Mar 29, 2024 · 1 comment

Comments

@mabelzhang
Copy link
Contributor

mabelzhang commented Mar 29, 2024

To create an infrastructure for this benchmarking repository so that it is portable and extendable to new test cases and new simulators, these are the necessary items to implement:

The above should first be done and documented for the boxes case.

  • When the infrastructure above is working for the boxes, new test cases can be added to include e.g. joints and contacts. One example is a tri-ball, 3 balls connected rigidly by bars.
    An accuracy metric would need to be determined for each new test.
  • Extend to other simulators. World files should be created for other simulators based on the documented world definitions. Then tests should be created for other simulators.
@yaswanth1701
Copy link
Contributor

Hi @mabelzhang, I was looking into migration and logging for the new Gazebo and had a few questions about implementation.

  1. The new link API is missing some of the functions for example GetWorldEnergy. I think these are on the roadmap for new Gazebo and will be implemented in future. However, is it a good idea to backport these functions from classic as part of the project? This might be helpful if we plan to add new worlds.
  2. Also, I was thinking of using Gazebo's logging functionality to log link states. So, by default, the poses published by pose_publisher are logged into the .log files. We could write a plugin similar to pose_publisher that publishes link states (poses, velocity, energy, and momentum) to a specific topic and add this topic to the recorder for logging. Then convert this to a CSV file for metric calculation.
    Or
    Simply publish and log only poses and velocities and then calculate energy and momentum in postprocessing scripts as other simulators might not have the functionality for getting and logging link energy and momentum directly. I think this would be a better approach for easy integration with other simulators with minimal effort. What is your opinion on this?

@yaswanth1701 yaswanth1701 mentioned this issue Aug 5, 2024
4 tasks
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