-
Notifications
You must be signed in to change notification settings - Fork 99
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
X2 laser scanner data not valid #11
Comments
Original comment by Nate Koenig (Bitbucket: Nathan Koenig). I assume you are referring to the Try moving the robot around, or place an object in front of the laser. You should see the message change. |
Original comment by Steve Peters (Bitbucket: Steven Peters). I believe the gazebo sensors are following the ROS convention from REP 117, which states that "Detections that are too close to the sensor to quantify shall be represented by -Inf". Maybe the sensor collision is blocking all the sensor rays. We may need to adjust the |
Original comment by Nate Koenig (Bitbucket: Nathan Koenig). Thanks for the clarification Steve. Negative infinity would indicate that something is too close. I ran through your example, and here is the data I see:
Can you include a screenshot of Gazebo so that we can see what your environment and robot configuration look like? |
Original comment by Nate Koenig (Bitbucket: Nathan Koenig).
|
Original comment by Nate Koenig (Bitbucket: Nathan Koenig). Issue #21 was marked as a duplicate of this issue. |
Original comment by Nate Koenig (Bitbucket: Nathan Koenig). We are unable to reproduce this issue. Make sure that you have followed the installation instructions correctly: https://osrf-migration.github.io/subt-gh-pages/#!/osrf/subt/wiki/tutorials. |
Original comment by dinesh lama (Bitbucket: roboticsai). above is the screen shot, i also put some obstacles in front of the robot, but still i only see the -inf range values. I also tried the rrbot laser scan from [this](Link URL)http://gazebosim.org/tutorials?tut=ros_gzplugins tutorial and i get the same result. is using dedicated nvidia gpu neccesary to run this simulation? cas i'm not using dedicated graphics card currentely as written in system requirment page, all other system requirment are matching. |
Original comment by Nate Koenig (Bitbucket: Nathan Koenig). You can try changing Can you also post the command you are running to launch simulation? And do have the latest code? |
Original comment by Nate Koenig (Bitbucket: Nathan Koenig). I tried this on a laptop that does not have a dedicated GPU, and see the same result as you. Do you have access to a machine that has a GPU? |
Original comment by dineshlama (Bitbucket: dineshlama). o.. ok thanks. now i got it. and as described in the system requirment page, is using gpu neccesary to run subt simulation with multiple robots with laser scanner? cas right now my system don't have dedicated gpu like described in system requirment page. |
Original comment by Nate Koenig (Bitbucket: Nathan Koenig). Yes, a machine equipped with a GPU is required for SubT. GPU equipped machines will be used during the competition as well. |
Original comment by Nate Koenig (Bitbucket: Nathan Koenig).
A GPU is required by SubT. |
Original comment by dineshlama (Bitbucket: dineshlama). What is the drawback of having no GPU? after i changed gpu_ray with ray sensor the laser scan is coming properly, and i could also run the SubT environment properly in my PCwith decent performance. Isn't it ok if i use this PC for the final event also? Because i have to buy a new laptop with required GPU if it in necessary. |
Original comment by Nate Koenig (Bitbucket: Nathan Koenig). You won't be able to use your PC for the final event. All circuit events will be run in the cloud. |
Original comment by Alfredo Bencomo (Bitbucket: bencomo).
|
Original report (archived issue) by Anonymous.
Hello,
When running through the RViz tutorial, I am unable to get the laser scanner data from X2 to visualize. Looking at the topic, it appears that the data is invalid.
Launched with:
roslaunch subt_gazebo competition.launch scenario:=tunnel_practice_1
-and-
X2_SENSOR_CONFIG_3=1 roslaunch subt_example team.launch
The text was updated successfully, but these errors were encountered: