-
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
Gazebo logs unusable in gazebo 7.11.0 #2441
Comments
Original comment by Víctor López (Bitbucket: Victor Lopez).
|
2 similar comments
Original comment by Víctor López (Bitbucket: Victor Lopez).
|
Original comment by Víctor López (Bitbucket: Victor Lopez).
|
Original comment by Ian Chen (Bitbucket: Ian Chen, GitHub: iche033). the log recording slow down issue is likely the same as issue #2425, which is fixed by pull request #2889 for gazebo7 pull request #2890 mentions fixing ghost models which sounds similar to the Log Play back spawns multiple robots problem in this issue. We can try backporting that pull request to gazebo7 and see if that fixes the problem |
Original comment by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina). Yeah I vote for backporting pull request #2890 and releasing 7.12 asap |
Original comment by Víctor López (Bitbucket: Victor Lopez). I can test those fixes applied on top of 7.11 if you point me to the appropriate branch. |
Original comment by Víctor López (Bitbucket: Victor Lopez). @iche033 @chapulina Do you have an ETA for this? |
Original comment by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina). I'll see if I manage to backport pull request #2890 today or tomorrow |
Original comment by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina). Update: backported pull request #2890 to Gazebo 7 on branch issue_2441. All new tests pass, but it seems to be causing issues with log filtering, see the test failure (that test works fine on Gazebo 8). |
Original report (archived issue) by Víctor López (Bitbucket: Victor Lopez).
The original report had attachments: AF_INET_error.txt, repeated_initialization.txt, state.log
System: Ubuntu 16.04
ROS: Kinetic
Gazebo: 7.11.0-1~xenial (installed from debians)
Trying to record logs and play them afterward I've encountered some issues, they happen when the simulation includes a robot that is moving.
I first encountered them in the simulation of PAL Robotics TIAGo and PMB2, but also ocurr with the Fetch robot.
I launch the simulations providing the
-r
flag.The issues:
Slowdown when recording
Recording massively slows the simulation, from ~1.00 RT Factor to 0.03 when the robot is moving, when stopped it goes back to max speed.
With
--record_period 0.01
and the RT factor increased to 0.25With
--record_period 0.1
and the RT factor increased to 0.77I'm writing to an SSD disk.
Log Play back spawns multiple robots
Playing back a log spawns dozens of robots on the same spot.
This increases memory consumption and collapses the system in a matter of seconds.
Furthermore, there are a lot of ROS errors when playing the log that I describe below.
Couldn't find an AF_INET address for []
This happens to me if I play the log with:
gazebo -p state.log
I've attached a txt file with the errors.
I can solve it either with
gazebo -p state.log -s libgazebo_ros_api_plugin.so
orrosrun gazebo_ros gazebo -p state.log
So this can be a non-issue, I just didn't find any documentation regarding the error and wasted some time. Posting it here in case anyone else faces it.
Repeated initilization of ROS Controllers
When playing a log file, it looks like the ROS Controllers are being initialized continuously.
Might be related to the multiple robot error I mentioned above.
I'm attaching a gazebo state.log and a text log file as well for this error.
I had similar issues with gazebo 7.0.0, hence the upgrade to 7.11.0.
Last year in the Space Robotics Challenge with gazebo 7 on indigo we were able to simulate a much more complex robot (R5 and Talos) with ROS Control, record the logs and play them without these issues.
Not only the
The text was updated successfully, but these errors were encountered: