Abhy, IIRC, the stereo image proc node doesn't need to be pushed down into a namespace. That is only important if you are running multiple pairs of cameras. What is the output of rxgraph if you run uvc_stereo and stereo_image_proc, both with no remappings or namespaces? Does stereo image proc successfully subscribe to your cameras and output point clouds/disparity images? - Eric On Tue, Feb 8, 2011 at 12:22 PM, abhy wrote: > > Hi, > > This is the example of the output i get from different packages: > If gscam package using single camera: > > /gscam/image_raw > /gscam/..... > > If i use usb_cam package then i get (Single camera), > /usb_cam/image_raw > /usb_cam/..... > > I can use any of the above packages in image_proc > ROS_NAMESPACE=my_camera rosrun image_proc image_proc > $ rosrun image_view image_view image:=my_camera/image_rect_color > Here i replace my_camera with either /usb_cam or /gscam > > Now, > > If i use uvc_stereo package i should expected to get, > /uvc_stereo/left/image_raw > /uvc_stereo/left/...... > (same for right side camera) > > Instead, i get directly, (W/o /uvc_stereo) > /left/image_raw > /left/...... > (same for right side camera) > > This is hard to replace in the image_proc_stereo package like above case. > As per package it should expect, > /stereo/left/image_raw > /stereo/left/camera_info > /stereo/right/image_raw > /stereo/right/camera_info > $ ROS_NAMESPACE=stereo rosrun stereo_image_proc stereo_image_proc > __name:=proc > $ rosrun image_view stereo_view stereo:=/stereo image:=image_rect_color > > But, here i dont get either /stereo OR /uvc_camera to replace /stereo since > i get /left/image_raw topic and not /OR/left/image_raw > > Do you suggest any way to get such publish topics through uvc_stereo > package > so as to use it in image_proc_stereo? > I hope it is not confusing. :-) I have tried my best to explain it. Please > let me know if it is still not clear. > > - Abhy > > -- > View this message in context: > http://ros-users.122217.n3.nabble.com/uvc-camera-and-stereo-proc-tp2451433p2452772.html > Sent from the ROS-Users mailing list archive at Nabble.com. > _______________________________________________ > ros-users mailing list > ros-users@code.ros.org > https://code.ros.org/mailman/listinfo/ros-users >