-
Notifications
You must be signed in to change notification settings - Fork 486
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
Significantly lower RTF when state logging enabled after upgrading to gazebo 8.3 #2425
Comments
Original comment by Deanna Hood (Bitbucket: d_hood). Most of my issues are specific to logging with the UR10 for ARIAC. I've confirmed that this effect occurs even without a ur10 in the environment, just from other models moving around. |
Original comment by Jordan Liviero (Bitbucket: jliviero). We have seen the same issue running the |
Original comment by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina). Pull request #2885 should solve this issue. While investigating I ran into issue #2428... Pull request #2608 created a lot of problens 😕 |
Original comment by Deanna Hood (Bitbucket: d_hood).
fixed by https://osrf-migration.github.io/gazebo-gh-pages/#!/osrf/gazebo/pull-requests/2885 thank you |
Original report (archived issue) by Deanna Hood (Bitbucket: d_hood).
State logging always lowers RTF a bit for ARIAC, but the latest releases have significantly impacted it.
Before, gazebo 8.2:
roslaunch osrf_gear sample_environment.launch
roslaunch osrf_gear sample_environment.launch state_logging:=true
After, gazebo 8.3 or gazebo 7.11:
I am aware of https://osrf-migration.github.io/gazebo-gh-pages/#!/osrf/gazebo/pull-requests/2608 that was merged during the latest release cycle, but I thought that was just targeting the
gz log --echo
tool, not logging itself. The lower RTF might be an unintended side effect of that PR, or from a different one altogether.The text was updated successfully, but these errors were encountered: