ratneshmadaan's profile - activity

I want to use a mesh as a marker. To do that, I changed basic_controls.py to :

marker.type = Marker.MESH_RESOURCE;
marker.mesh_resource = 'package://HexagonalPrism.STL'

(And added a from visualization_msgs.msg import * at the top as well)

I get the following error

Error retrieving file [package://HexagonalPrism.STL]: Could not parse package:// format into file:// format

RViz screenshot : https://drive.google.com/file/d/0B-PF...

The same works fine if I do a simple marker:

marker = visualization_msgs.msg.Marker()
marker.type = visualization_msgs.msg.Marker.MESH_RESOURCE
marker.mesh_resource = 'package://HexagonalPrism.STL'

RViz : screenshot : https://drive.google.com/file/d/0B-PF...

I am trying to integrate leap motion sensor with youBot. I wrote a test publisher to move the joints. However, when I run the python script, I am getting this error:

youbot@youbot-desktop:~$ rosrun youbot_leap leap_armcontrol.py Traceback (most recent call last): File "/home/youbot/catkin_ws/src/youbotleap/scripts/leap_armcontrol.py", line 96, in <module> sender() File "/home/youbot/catkin_ws/src/youbotleap/scripts/leap_armcontrol.py", line 25, in sender msg.positions.joint_uri = "arm_joint_1" AttributeError: 'list' object has no attribute 'joint_uri'

While through the terminal, it runs fine on the bot: youbot@youbot-desktop:~/catkin_ws$ rostopic pub -1 /arm_1/arm_controller/position_command brics_actuator/JointPositions '{positions:[{joint_uri: arm_joint_5, unit: rad, value: 1}]}' publishing and latching message for 3.0 seconds

The message:

youbot@youbot-desktop:~$ rosmsg show brics_actuator/JointPositions brics_actuator/Poison poisonStamp string originator string description float32 qos brics_actuator/JointValue[] positions time timeStamp string joint_uri string unit float64 value

Here's the code:

import rospy
from brics_actuator.msg import JointPositions
pub_youbotleap_arm = rospy.Publisher('arm_1/arm_controller/position_command', JointPositions)
rospy.init_node('armcontrol')

rate = rospy.Rate(20)

msg = JointPositions()

msg.positions.joint_uri = "arm_joint_1"
msg.positions.unit = "rad"
msg.positions.value = 2

pub_youbotleap_arm.publish(msg)

if __name__ == '__main__':
    sender()
    rospy.spin()

?-  visualisation_canvas(_).
lights() is not available with this renderer.
true.

This has got something do to with processing, that I understand.

$ sudo apt-get install ros-hydro-cram-core Reading package lists... Done Building dependency tree
Reading state information... Done E: Unable to locate package ros-hydro-cram-core

What I tried :

$ sudo sh -c 'echo "deb packages.ros.org/ros/ubuntu precise main" > /etc/apt/sources.list.d/ros-latest.list' $ sudo apt-get install ros-hydro-knowrob

Error : E: Unable to locate package ros-hydro-knowrob

Note sudo apt-get install ros-groovy-knowrob works fine, but I got hydro.

Able to read the data via minicom. Also the lightware terminal doesn't work with Wine on Ubuntu. Did you happen to try it?

^Cterminate called after throwing an instance of 'cereal::Exception'

what(): poll failed -- error = 4: Interrupted system call (in cereal::CerealPort::readBytes)

Aborted (core dumped)

rosrun altitude_sensor altitude_sensor_node

INFO 1455503400.766892744: The serial port is opened. ERROR 1455503401.768272992: Timeout!

ERROR 1455503402.769572975: Timeout!

^Cterminate called after throwing an instance of 'cereal::Exception' what(): po

Thanks for the quick help! I ll test soon and get back to you.

Will the same for SF-40/C. Asked here http://answers.ros.org/question/22636...

Has anyone written a ROS driver for the Lightware SF-40/C laser scanner
I found one for SF-10/C altimeter here https://github.com/wavelab/ros_lightware . Not sure if this will work for SF-40/C as well.

Yeah I guess one needs to append this back again to $PYTHONPATH /opt/ros/indigo/lib/python2.7/dist-packages/. Conda seems to have removed it from the path.

More ref that might help http://answers.ros.org/question/17228... and https://github.com/proofit404/anacond...

And why should one not use pip? It seems to work here. I admit I didn't really bother with finding the exact cause - some path conflict due to Conda - and an easier fix.

The debians dependencies are already installed. I'm guessing this is happening _specifically_ due to Conda, which is changing the directory from where to find things. pip install catkin_pkg rospkg works for the two errors above. Do you recommend a better way to do the same?

I have a bag publishing left and right camera_info and image_rect_color topics. How can I use stereo_image_proc to get the point cloud?

stereo_image_proc/disparity nodelet subscribes to image_rect and gives out disparity, which can be used by the stereo_image_proc/point_cloud2 nodelet.

Do I need to modify the source code, make a custom launch file or this can be done via an easier way that I am unable to see immediately? Afai understand, I have to convert to mono image and then maybe remap or publish to the relevant topic.

ROS_NAMESPACE=stereo rosrun stereo_image_proc stereo_image_proc -> here the whole node subscribes to raw images which I don't have as a topic.

I faced this some time back after installing Conda. tl;dr: Do pip install catkin_pkg.
Chances are you also want to do pip install rospkg as you'll get ImportError: No module named 'rospkg' using launch files as well.

Maybe appending /opt/ros/indigo/lib/python2.7/dist-packages/ to $PYTHONPATH is a better solution (if that's not already there, then it's a different problem). Not tested though.

You can read about the details in the following answers.

catkin_pkg:
http://answers.ros.org/question/12647...
http://answers.ros.org/question/20402...
http://answers.ros.org/question/49143...
http://answers.ros.org/question/61027...

rospkg:
http://answers.ros.org/question/85211...
http://answers.ros.org/question/86126...

I'd like to automate(or semi-automate) this process http://wiki.ros.org/catkin/migrating_... I'm surprised as there are no scripts available for this. Has someone tried it before? I'm on the lookout for where was someone(or I might get) stuck while trying to achieve this.