[ros-users] rosh not showing all topics

[Ken Conley]

It's probably b/c rosh is currently only tab completes published
topics.  I honestly can't recall if this was:

a) by design, so that you only tab complete to topics that you can get data from

or

b) due to the fact that in the very first prototype of rosh,
subscribers in ROS didn't declare topic type (which meant that rosh
couldn't do any initialization of subscriber-only topics).

.. though I'm leaning towards (b).

I welcome your feedback (I'll probably spend some time with rosh later
this month to incorporate the API review feedback and freeze it, so
now is the time to blast away).

In the event that the theory above is wrong (i.e. it is a published
topic), please send the output of:

python -c "import os, xmlrpclib; s =
xmlrpclib.ServerProxy(os.environ['ROS_MASTER_URI']); print
s.getPublishedTopics('/test', '/')"

and

python -c "import os, xmlrpclib; s =
xmlrpclib.ServerProxy(os.environ['ROS_MASTER_URI']); print
s.getSystemState('/test')"

cheers,
Ken

On Tue, Dec 7, 2010 at 11:10 PM, Patrick Bouffard
<bouffard at eecs.berkeley.edu> wrote:
> In rosh:
>
> In [2]: topics.pelican1. <pressed TAB>
> topics.pelican1.asctec_proc                topics.pelican1.controller_mux
> topics.pelican1.autopilot                  topics.pelican1.downlink
> topics.pelican1.control_mode_attitude      topics.pelican1.estimator
> topics.pelican1.control_mode_autosequence  topics.pelican1.joy
> topics.pelican1.control_mode_hover         topics.pelican1.teleop_flyer
> topics.pelican1.control_mode_idle          topics.pelican1.vicon_recv_direct
> topics.pelican1.controller
>
> .. quit out of rosh and in the same terminal:
>
> bouffard at lipschitz:~/kinect-devel-unstable$ rostopic list | grep pelican1
> /pelican1/asctec_adapter/land_now
> /pelican1/asctec_proc/imu
> /pelican1/asctec_proc/pressure_height
> ...
>
> back into rosh, and try another way:
>
> In [1]: topics['/pelican1/asctec_adapter/land_now']
> Out[1]:
> bool data
>
> Which is what it should say (it's of type std_msgs/Bool). Why can rosh
> 'see' that topic one way but not the other, even when rostopic list
> can see it? This is using unstable maverick debs.
>
> Thanks,
> Pat
> _______________________________________________
> ros-users mailing list
> ros-users at code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>