Andrzej Pronobis's profile - activity

I tried to use ROSCONSOLE_FORMAT as shown in Console Output Formatting on rosconsole wiki.

I configured my .bashrc as shown below:

source /opt/ros/hydro/setup.bash 
source ~/myproject/devel/setup.bash
export ROS_HOSTNAME=localhost
export ROS_MASTER_URI=<removed_link>
export ROBOT=sim
export ROSCONSOLE_FORMAT='[${severity}] [${node}@${function}:${line}]: ${message}'

For C++ I get expected outputs. However for any python program, for example

#!/usr/bin/env python
# license removed for brevity
import rospy
from std_msgs.msg import String

def talker():
    # pub = rospy.Publisher('chatter', String, queue_size=10)
    rospy.init_node('talker', anonymous=True)
    r = rospy.Rate(1)  # 10hz
    while not rospy.is_shutdown():
        # str = "hello world %s" % rospy.get_time()
        rospy.loginfo("Hello World!")
        # pub.publish(str)
        r.sleep()

if __name__ == '__main__':
    try:
        talker()
    except rospy.ROSInterruptException:
        pass

I get unformatted outputs like:

mjyc@ubuntu:~$ python test.py
[INFO] [WallTime: 1405812621.854884] Hello World!
[INFO] [WallTime: 1405812622.856649] Hello World!
[INFO] [WallTime: 1405812623.856340] Hello World!
[INFO] [WallTime: 1405812624.856789] Hello World!
[INFO] [WallTime: 1405812625.855262] Hello World!

Anybody has any clue?

I'm on Ubuntu 12.04 and using hydro.

Thanks a lot Niko for a very informative answer!

No solution so far unfortunately. This warning appears for any package using QT and MOC, including the standard ROS hydro packages.

Is that the same problem indeed? I cannot see any reference to the warning there?

For those who still have that problem (as I did after exporting my blender file to Collada), the trick is to make sure that ambient in the material in the collada file is set properly. It should look like this:

<ambient>
  <color sid="ambient">0.1 0.1 0.1 1</color>
</ambient>

Hi,

I'm trying to understand why there is such a large error in depth perception from my Asus Xtion sensor when a flat surface is being observed. When I point the sensor at a flat wall 2m away, the pointcloud visualized in RViz and viewed from the top will be a curve instead of a line (the problem is quite noticeable). Why would that be the case? What could be the solution?

Btw. calibration/rectification does not seem to make much of a difference.

Thanks!