Ask Your Question
0

erratic simulation does not work after ubuntu updates [closed]

asked 2013-01-15 05:18:53 -0600

otto gravatar image

I have been successfully using the erratic robot simulation in Gazebo (fuerte on ubuntu 12.04). I installed the erratic robot for simulation using:

sudo apt-get install ros-diamondback-fuerte-robot

After some updates were installed (including python-rospkg, ros-fuerte-pr2-controllers, and ros-fuerte-pr2-mechanism) using the ubuntu update manager, I have not been able to launch Gazebo with the erratic robot.

For example, the output of roslaunch erratic_navigation_apps demo_2dnav_slam.launch (from [link text]http://www.ros.org/wiki/simulator_gazebo/Tutorials/TeleopErraticSimulation)) is:

scott@scott-ub:~$ roslaunch erratic_navigation_apps demo_2dnav_slam.launch
... logging to /home/scott/.ros/log/c6d49662-5f32-11e2-aa2b-782bcbb7d7cd/roslaunch-scott-ub-14417.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

started roslaunch server http://scott-ub:42921/

SUMMARY
========

PARAMETERS
 * /base_laser_self_filter/min_sensor_dist
 * /base_laser_self_filter/self_see_default_padding
 * /base_laser_self_filter/self_see_default_scale
 * /base_laser_self_filter/self_see_links
 * /base_laser_self_filter/sensor_frame
 * /base_shadow_filter/high_fidelity
 * /base_shadow_filter/scan_filter_chain
 * /base_shadow_filter/target_frame
 * /move_base_node/NavfnROS/allow_unknown
 * /move_base_node/TrajectoryPlannerROS/acc_lim_th
 * /move_base_node/TrajectoryPlannerROS/acc_lim_x
 * /move_base_node/TrajectoryPlannerROS/acc_lim_y
 * /move_base_node/TrajectoryPlannerROS/dwa
 * /move_base_node/TrajectoryPlannerROS/escape_vel
 * /move_base_node/TrajectoryPlannerROS/goal_distance_bias
 * /move_base_node/TrajectoryPlannerROS/heading_lookahead
 * /move_base_node/TrajectoryPlannerROS/holonomic_robot
 * /move_base_node/TrajectoryPlannerROS/max_rotational_vel
 * /move_base_node/TrajectoryPlannerROS/max_vel_x
 * /move_base_node/TrajectoryPlannerROS/min_in_place_rotational_vel
 * /move_base_node/TrajectoryPlannerROS/min_vel_x
 * /move_base_node/TrajectoryPlannerROS/occdist_scale
 * /move_base_node/TrajectoryPlannerROS/oscillation_reset_dist
 * /move_base_node/TrajectoryPlannerROS/path_distance_bias
 * /move_base_node/TrajectoryPlannerROS/sim_granularity
 * /move_base_node/TrajectoryPlannerROS/sim_time
 * /move_base_node/TrajectoryPlannerROS/vtheta_samples
 * /move_base_node/TrajectoryPlannerROS/vx_samples
 * /move_base_node/TrajectoryPlannerROS/xy_goal_tolerance
 * /move_base_node/TrajectoryPlannerROS/yaw_goal_tolerance
 * /move_base_node/aggressive_clear/reset_distance
 * /move_base_node/clearing_radius
 * /move_base_node/conservative_clear/reset_distance
 * /move_base_node/controller_frequency
 * /move_base_node/controller_patience
 * /move_base_node/footprint
 * /move_base_node/footprint_padding
 * /move_base_node/global_costmap/base_scan/clearing
 * /move_base_node/global_costmap/base_scan/data_type
 * /move_base_node/global_costmap/base_scan/expected_update_rate
 * /move_base_node/global_costmap/base_scan/marking
 * /move_base_node/global_costmap/base_scan/max_obstacle_height
 * /move_base_node/global_costmap/base_scan/min_obstacle_height
 * /move_base_node/global_costmap/base_scan/observation_persistence
 * /move_base_node/global_costmap/base_scan/sensor_frame
 * /move_base_node/global_costmap/base_scan/topic
 * /move_base_node/global_costmap/base_scan_marking/clearing
 * /move_base_node/global_costmap/base_scan_marking/data_type
 * /move_base_node/global_costmap/base_scan_marking/expected_update_rate
 * /move_base_node/global_costmap/base_scan_marking/marking
 * /move_base_node/global_costmap/base_scan_marking/max_obstacle_height
 * /move_base_node/global_costmap/base_scan_marking/min_obstacle_height
 * /move_base_node/global_costmap/base_scan_marking/observation_persistence
 * /move_base_node/global_costmap/base_scan_marking/sensor_frame
 * /move_base_node/global_costmap/base_scan_marking/topic
 * /move_base_node/global_costmap/global_frame
 * /move_base_node/global_costmap/inflation_radius
 * /move_base_node/global_costmap/map_type
 * /move_base_node/global_costmap/observation_sources
 * /move_base_node/global_costmap/obstacle_range
 * /move_base_node/global_costmap/publish_frequency
 * /move_base_node/global_costmap/raytrace_range
 * /move_base_node/global_costmap/robot_base_frame
 * /move_base_node/global_costmap/rolling_window
 * /move_base_node/global_costmap/static_map
 * /move_base_node/global_costmap/transform_tolerance
 * /move_base_node/global_costmap/unknown_cost_value
 * /move_base_node/global_costmap/update_frequency
 * /move_base_node/local_costmap/base_scan/clearing
 * /move_base_node/local_costmap/base_scan/data_type
 * /move_base_node/local_costmap/base_scan/expected_update_rate
 * /move_base_node/local_costmap/base_scan/marking
 * /move_base_node/local_costmap/base_scan/max_obstacle_height
 * /move_base_node/local_costmap/base_scan/min_obstacle_height
 * /move_base_node/local_costmap/base_scan/observation_persistence
 * /move_base_node/local_costmap/base_scan/sensor_frame
 * /move_base_node/local_costmap/base_scan/topic
 * /move_base_node/local_costmap/base_scan_marking/clearing
 * /move_base_node/local_costmap/base_scan_marking/data_type
 * /move_base_node/local_costmap/base_scan_marking/expected_update_rate
 * /move_base_node/local_costmap/base_scan_marking/marking
 * /move_base_node/local_costmap/base_scan_marking/max_obstacle_height
 * /move_base_node/local_costmap/base_scan_marking/min_obstacle_height
 * /move_base_node/local_costmap/base_scan_marking/observation_persistence
 * /move_base_node/local_costmap/base_scan_marking/sensor_frame
 * /move_base_node/local_costmap/base_scan_marking/topic
 * /move_base_node/local_costmap/global_frame
 * /move_base_node/local_costmap/height
 * /move_base_node/local_costmap/inflation_radius
 * /move_base_node/local_costmap/map_type
 * /move_base_node/local_costmap/observation_sources
 * /move_base_node/local_costmap/obstacle_range
 * /move_base_node/local_costmap/origin_x
 * /move_base_node/local_costmap/origin_y
 * /move_base_node/local_costmap/publish_frequency
 * /move_base_node/local_costmap/publish_voxel_map
 * /move_base_node/local_costmap/raytrace_range
 * /move_base_node/local_costmap/resolution
 * /move_base_node/local_costmap/robot_base_frame
 * /move_base_node/local_costmap/rolling_window
 * /move_base_node/local_costmap/static_map
 * /move_base_node/local_costmap/transform_tolerance
 * /move_base_node/local_costmap/update_frequency
 * /move_base_node/local_costmap/width
 * /move_base_node/recovery_behaviors
 * /robot_description
 * /robot_state_publisher/publish_frequency
 * /robot_state_publisher/tf_prefix
 * /rosdistro
 * /rosversion
 * /slam_gmapping/angularUpdate
 * /slam_gmapping/astep
 * /slam_gmapping/base_frame
 * /slam_gmapping/delta
 * /slam_gmapping/iterations
 * /slam_gmapping/kernelSize
 * /slam_gmapping/lasamplerange
 * /slam_gmapping/lasamplestep
 * /slam_gmapping/linearUpdate
 * /slam_gmapping/llsamplerange
 * /slam_gmapping/llsamplestep
 * /slam_gmapping/lsigma
 * /slam_gmapping/lskip
 * /slam_gmapping/lstep
 * /slam_gmapping/map_update_interval
 * /slam_gmapping/maxUrange
 * /slam_gmapping/odom_frame ...
(more)
edit retag flag offensive reopen merge delete

Closed for the following reason question is off-topic or not relevant. Please see http://wiki.ros.org/Support for more details. by 130s
close date 2013-01-15 10:41:30

1 Answer

Sort by ยป oldest newest most voted
0

answered 2013-01-15 10:40:59 -0600

130s gravatar image

Starting since Sep 2012, all gazebo related questions should be asked on new gazebo specific QA community. Thank you for your cooperation!

See also this thread.

Apologies that I close as "off-topic" although it's actually very related - there isn't more suitable label.

edit flag offensive delete link more

Question Tools

Stats

Asked: 2013-01-15 05:18:53 -0600

Seen: 205 times

Last updated: Jan 15 '13