You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi everyone, I am working on benchmarking physics engines as part of Google Summer of Code'24 with the Open Source Robotics Foundation(OSRF). We are trying to build a simulator-independent benchmarking suite. I tested running our benchmarking with the gazebo classic and the new gazebo(gz-sim). Gazebo supports both bullet and bullet Featherstone and we found the results for both bullet versions to be a bit off from other engines (eg: dart, simbody, ode). So, to investigate further I ran the same benchmarking on pybullet with maximal coordinates and reduced coordinates version(Featherstone). We found that the results for the maximal coordinates version are similar to other physics engines and are mostly likely correct. However, the Featherstone version is entirely wrong (and is not even close to what was obtained on gz - sim) and has huge errors in both position and velocity compared to the analytical solutions. A detailed description of our benchmark can be found here.
There is only gravity force acting in the z direction and no force along the x and y directions. But it seems while using reduced coordinates, velocities in the x and y directions are changing which is not the case with the maximal coordinates version.
Below is the code I am using, to switch between maximal and reduced coordinates, I am changing only the useMaximalCoordinates argument except that everything is same.
Hi everyone, I am working on benchmarking physics engines as part of Google Summer of Code'24 with the Open Source Robotics Foundation(OSRF). We are trying to build a simulator-independent benchmarking suite. I tested running our benchmarking with the gazebo classic and the new gazebo(gz-sim). Gazebo supports both bullet and bullet Featherstone and we found the results for both bullet versions to be a bit off from other engines (eg: dart, simbody, ode). So, to investigate further I ran the same benchmarking on pybullet with maximal coordinates and reduced coordinates version(Featherstone). We found that the results for the maximal coordinates version are similar to other physics engines and are mostly likely correct. However, the Featherstone version is entirely wrong (and is not even close to what was obtained on gz - sim) and has huge errors in both position and velocity compared to the analytical solutions. A detailed description of our benchmark can be found here.
There is only gravity force acting in the z direction and no force along the x and y directions. But it seems while using reduced coordinates, velocities in the x and y directions are changing which is not the case with the maximal coordinates version.
Below is the code I am using, to switch between maximal and reduced coordinates, I am changing only the
useMaximalCoordinates
argument except that everything is same.Here are all the benchmarking worlds which we using in sdf format.
BENCHMARK_boxes_dt_TEST.zip
The result for Featherstone version on gz-sim can be found here.
Results for pybullet can be found here
The text was updated successfully, but these errors were encountered: