ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

paresh471's profile - activity

2021-09-13 10:07:30 -0500 received badge  Nice Question (source)
2015-02-20 02:43:26 -0500 received badge  Taxonomist
2014-05-12 23:17:55 -0500 received badge  Notable Question (source)
2014-05-12 23:17:55 -0500 received badge  Famous Question (source)
2014-05-12 23:17:55 -0500 received badge  Popular Question (source)
2014-03-15 07:55:38 -0500 received badge  Enthusiast
2014-03-09 06:03:46 -0500 asked a question what is the purpose of zeroconf and avahi?

Recently, I discovered a process on my ubuntu that was eating away at both processor time and memory, 18% and 10% respectively. Avahi-daemon and I got rid of it along with pulseaudio. It seems to me that there is no need for avahi-daemon which is a zeroconf derivative in itself. If this process caused issues, isn't well maintained, and eats up precious resources then why is it being utilized in ROS? All the way to Hydro, I see zeroconf. I read the discription provided by the ROS wiki, and checked Archlinux for zeroconf and avahi. I still don't see what purpose it serves because I don't see it being a dependency for anything other than ros-hydro-turtlebot-bringup.

What purpose does zeroconf and avahi serve when the amount of resources it consumes is detrimental in a resource scarce scenario such as most robot systems, e.g. 7-DOF manipulators, vision-based path planning/navigation, etc?

I am trying to understand what, why, and how of this package/stack. I feel like it should be deprecated.

2014-02-25 02:12:07 -0500 received badge  Famous Question (source)
2014-02-13 18:22:18 -0500 received badge  Autobiographer
2013-06-20 07:53:10 -0500 received badge  Good Question (source)
2013-01-25 06:42:42 -0500 received badge  Notable Question (source)
2013-01-25 06:42:42 -0500 received badge  Popular Question (source)
2013-01-20 23:28:29 -0500 received badge  Nice Question (source)
2013-01-20 23:28:21 -0500 received badge  Self-Learner (source)
2013-01-20 23:28:21 -0500 received badge  Teacher (source)
2012-09-06 03:17:17 -0500 received badge  Popular Question (source)
2012-09-06 03:17:17 -0500 received badge  Notable Question (source)
2012-09-06 03:17:17 -0500 received badge  Famous Question (source)
2012-08-30 22:04:34 -0500 received badge  Famous Question (source)
2012-08-30 22:04:34 -0500 received badge  Popular Question (source)
2012-08-30 22:04:34 -0500 received badge  Notable Question (source)
2012-07-11 05:21:16 -0500 commented answer trouble creating launch file

I am also having the same problem and running my node separately, "rosrun snd_control navigate" works just fine. The problem is when I put it into a launch file, " <node name="navigate" pkg="snd_control" type="navigate" respawn="false" /> " process[navigate-3]: started with pid [11739] terminate...

2012-07-11 01:21:03 -0500 commented answer ROS Stage in Fuerte on 12.04: Stage controller tutorial only for 3.x.x

I did exactly that to remove the first error, but the second error is the crux of the matter.

2012-07-09 23:32:28 -0500 answered a question ROS Stage in Fuerte on 12.04: Stage controller tutorial only for 3.x.x
2012-07-09 19:20:55 -0500 received badge  Student (source)
2012-07-09 03:49:11 -0500 received badge  Supporter (source)
2012-07-09 03:34:24 -0500 asked a question ROS Stage in Fuerte on 12.04: Stage controller tutorial only for 3.x.x

Is there a way to get the controller tutorial working for ROS Stage 4.x.x? I ran into the following problems when attempting to get the tutorial working though it is not meant for my version of Stage. Link to tutorial here

First Error:

paresh@paresh-9:~/ros_workspace$ rosrun stage stageros `rospack find stage_controllers`/world/roomba-wander.world

 [Loading /home/paresh/ros_workspace/stage_controllers/world/roomba-wander.world][Image "bitmaps/roomba-stage.png"]
err: Model type laser not found in model typetable (/tmp/buildd/ros-fuerte-stage-1.6.6/debian/ros-fuerte-stage/opt/ros/fuerte/stacks/stage/build/stage/libstage/world.cc CreateModel)
err: Unknown model type laser in world file. (/tmp/buildd/ros-fuerte-stage-1.6.6/debian/ros-fuerte-stage/opt/ros/fuerte/stacks/stage/build/stage/libstage/world.cc CreateModel)

Fix: roomba-wander.world: ln35 col18: laser to ranger

Second Error:

paresh@paresh-9:~/ros_workspace$ rosrun stage stageros `rospack find stage_controllers`/world/roomba-wander.world
 [Loading /home/paresh/ros_workspace/stage_controllers/world/roomba-wander.world][Image "bitmaps/roomba-stage.png"]warn: lookup of model name roomba.ranger:1: no matching name (/tmp/buildd/ros-fuerte-stage-1.6.6/debian/ros-fuerte-stage/opt/ros/fuerte/stacks/stage/build/stage/libstage/world.cc GetModel)
warn: Model roomba.ranger:1 not found (/tmp/buildd/ros-fuerte-stage-1.6.6/debian/ros-fuerte-stage/opt/ros/fuerte/stacks/stage/build/stage/libstage/model.cc GetChild)
Segmentation fault (core dumped)

I don't know how to fix the second error. Any information would help.

2012-07-09 02:11:36 -0500 received badge  Editor (source)
2012-07-09 02:03:27 -0500 asked a question ROS Stage in Fuerte on 12.04 only supports 1 ranger or 1 sonar type how to do both

I understand that there is a ROS stage limitation of support where a robot is only allowed to have "rangers with 1 sensor only." As referenced here. As well as a rename of the Laser to rangers type, as referenced here.

Then how do I create a robot model to the specifications of my physical robot which will be compatible with ROS Stage 4.1.1? See here for breakdown of S1R. I have a mix of sonar, IR, and laser rangefinder. Currently, I would have to strip it down and only have one sensor on it, and I certainly don't want to do that.

What happened to the change in Stage that allowed multiple sensors as described in here?

The following world code is what I am working with:

include "S1R.inc"
include "hokuyo.inc"

S1R
(       
  # can refer to the robot by this name
  name "r0"
  pose [ 1.20 2.00 0 150 ]

  hokuyolaser(
    color "gray"
    pose [0.04 0.00 -0.11 0]
  )

  alwayson 1
  localization "gps"
  localization_origin [ 0 0 0 0 ]
  laser_return 0
)


window
(
  size [ 800 800 ] # in pixels
  scale 150.0
     # pixels per meteri
  center [ 1.7 1.8 ]
  rotate [ 0  0 ]


  view (       
    show_data 1              
    show_laser 1
    show_laser_strikes 1
    show_ranger 0
    show_mines 1
  )
)




###########################
# OBSTACLES
###########################


define obstacle model
(
  name "unknown"
  color  "orange"
  pose [0 0 0 0]
  size [0 0 0]
  gui_nose 0
  gui_grid 0
  gui_move 1
  gui_outline 0

  # insensible to collision and range sensors
  obstacle_return 1
  laser_return 1
  ranger_return 1  
)

obstacle(name "1" pose [1.71 0.02 0 90.0] size [0.04 3.34 0.25] color "brown")
obstacle(name "2" pose [1.71 3.7 0 90.0] size [0.04 3.34 0.25] color "brown")
obstacle(name "3" pose [0.02 1.86 0 0.0] size [0.04 3.72 0.25] color "brown")
obstacle(name "4" pose [3.4 1.86 0 0.0] size [0.04 3.72 0.25] color "brown")
obstacle(name "10" pose [2.26 0.5 0 0.0] size [0.04 0.28 0.25] color "red")
#obstacle(name "11" pose [2.76 0.18 0 0.0] size [0.04 0.28 0.25] color "red")
obstacle(name "22" pose [2.9 1.46 0 0.0] size [0.04 0.28 0.25] color "red")
obstacle(name "26" pose [0.5 0.34 0 90.0] size [0.04 0.36 0.25] color "gray49")
obstacle(name "27" pose [0.18 0.66 0 90.0] size [0.04 0.32 0.25] color "gray49")
obstacle(name "28" pose [1.16 0.34 0 90.0] size [0.04 0.32 0.25] color "gray49")
obstacle(name "29" pose [1.48 0.34 0 90.0] size [0.04 0.32 0.25] color "gray49")
obstacle(name "30" pose [1.44 0.66 0 90.0] size [0.04 0.32 0.25] color "gray49")
obstacle(name "31" pose [2.1 0.66 0 90.0] size [0.04 0 ...
(more)
2012-07-09 01:57:44 -0500 asked a question Stage for Fuerte on 12.04 only allows 1 ranger or 1 sonar not both and/or multiple sensors

I understand that there is a ROS stage limitation of support where a robot is only allowed to have "rangers with 1 sensor only." As referenced here. As well as a rename of the Laser to rangers type, as referenced here.

Then how do I create a robot model to the specifications of my physical robot which will be compatible with ROS Stage 4.1.1? See here for breakdown of S1R. I have a mix of sonar, IR, and laser rangefinder. Currently, I would have to strip it down and only have one sensor on it, and I certainly don't want to do that. The following world code is what I am working with:

include "S1R.inc"
include "hokuyo.inc"

S1R
(       
  # can refer to the robot by this name
  name "r0"
  pose [ 1.20 2.00 0 150 ]

  hokuyolaser(
    color "gray"
    pose [0.04 0.00 -0.11 0]
  )

  alwayson 1
  localization "gps"
  localization_origin [ 0 0 0 0 ]
  laser_return 0
)


window
(
  size [ 800 800 ] # in pixels
  scale 150.0
     # pixels per meteri
  center [ 1.7 1.8 ]
  rotate [ 0  0 ]


  view (       
    show_data 1              
    show_laser 1
    show_laser_strikes 1
    show_ranger 0
    show_mines 1
  )
)




###########################
# OBSTACLES
###########################


define obstacle model
(
  name "unknown"
  color  "orange"
  pose [0 0 0 0]
  size [0 0 0]
  gui_nose 0
  gui_grid 0
  gui_move 1
  gui_outline 0

  # insensible to collision and range sensors
  obstacle_return 1
  laser_return 1
  ranger_return 1  
)

obstacle(name "1" pose [1.71 0.02 0 90.0] size [0.04 3.34 0.25] color "brown")
obstacle(name "2" pose [1.71 3.7 0 90.0] size [0.04 3.34 0.25] color "brown")
obstacle(name "3" pose [0.02 1.86 0 0.0] size [0.04 3.72 0.25] color "brown")
obstacle(name "4" pose [3.4 1.86 0 0.0] size [0.04 3.72 0.25] color "brown")
#obstacle(name "5" pose [0.66 0.18 0 0.0] size [0.04 0.28 0.25] color "red")
#obstacle(name "6" pose [0.66 0.5 0 0.0] size [0.04 0.28 0.25] color "red")
#obstacle(name "7" pose [1.62 0.18 0 0.0] size [0.04 0.28 0.25] color "red")
#obstacle(name "8" pose [1.62 0.5 0 0.0] size [0.04 0.28 0.25] color "red")
#obstacle(name "9" pose [2.26 0.22 0 0.0] size [0.04 0.28 0.25] color "red")
#obstacle(name "10" pose [2.26 0.5 0 0.0] size [0.04 0.28 0.25] color "red")
#obstacle(name "11" pose [2.76 0.18 0 0.0] size [0.04 0.28 0.25] color "red")
#obstacle(name "12" pose [0.82 0.66 0 90.0] size [0.04 0.28 0.25] color "red")
#obstacle(name "13" pose [1.78 0.66 0 90.0] size [0.04 0.28 0.25] color "red")
#obstacle(name "14" pose [3.24 0.66 0 90 ...
(more)