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

Poofjunior's profile - activity

2021-03-04 02:50:12 -0500 received badge  Good Question (source)
2020-06-24 02:50:18 -0500 received badge  Nice Question (source)
2015-11-16 01:31:36 -0500 marked best answer Error compiling package with custom messages

Hello, everyone,

I'm having some difficulty compiling a package that I've created with custom message.

When I run cmake . at the head of that package's directory, I get the error

 Assertion failed: file
  '/home/poofjunior/Projects/ICEX/src/external_sensor_interface/msg/data_logger_measurement.h'
 does not exist.  Message: message file not found

inside of the msg directory in my package, I have a file titled data_logger_measurement.msg but indeed, the file in question, which is the .h file, does not exist in that msg directory.

Isn't this message auto-generated?

Oddly enough, I have been able to run this package before, and I'm slightly convinced that it may be an issue with how my workspace is setup.

Many thanks in advance!

2015-04-19 22:12:36 -0500 received badge  Necromancer (source)
2015-04-19 22:12:36 -0500 received badge  Teacher (source)
2014-04-28 19:18:30 -0500 received badge  Nice Question (source)
2014-01-28 17:28:47 -0500 marked best answer cannot find custom message groovy

Hello, everyone,

I'm working to define a custom message in ROS Groovy. I've followed the tutorial and updated my CMakeLists to innclude a custom message with the following changes in my package:

  7 find_package(catkin REQUIRED COMPONENTS roscpp rospy std_msgs message_generation)

 19  add_message_files(
 20    FILES
 21    data_logger_measurement.msg
 22  )

 32  generate_messages(
 33    DEPENDENCIES
 34    std_msgs
 35  )

 44 catkin_package(
 45   INCLUDE_DIRS include
 46 #  LIBRARIES tempSensorInterface 
 47   CATKIN_DEPENDS roscpp rospy std_msgs message_generation 
 48   DEPENDS system_lib message_runtime 
 49 )

I've also created a msg directory and placed the following data_logger_measurement.msg file in that directory:

Header header
float32 pressure # [C]
float32 temperature # [kPa]

(This msg is in the same package as my executable that I'm creating.)

unfortunately, when my executable includes this message with:

#include<temp_sensor_interface/data_logger_measurement.h>

and when I call "make" in my build folder, I get a message that there's

No such file or directory

Am I missing another step that creates such a header file in groovy? Thanks for lending a hand on this problem!

2014-01-28 17:28:45 -0500 marked best answer Linker Error in simple program in Groovy

Hello, everyone,

I'm having some trouble in the linking step of my program after running rosmake.

My program has a dependency in one other package, though I'm pretty sure that this console output isn't related to something on my end.

[ rosmake ] Last 40 linesmpSensorInterface: 10.4 sec ]                                                                                       [ 1 Active 21/22 Complete ]
{-------------------------------------------------------------------------------
/opt/ros/groovy/lib/libroscpp.so: error: undefined reference to 'virtual thunk to log4cxx::AppenderSkeleton::addRef() const'
/opt/ros/groovy/lib/libroscpp.so: error: undefined reference to 'virtual thunk to log4cxx::helpers::ObjectImpl::~ObjectImpl()'
/opt/ros/groovy/lib/libroscpp.so: error: undefined reference to 'log4cxx::Level::getInfo()'
/opt/ros/groovy/lib/libroscpp.so: error: undefined reference to 'typeinfo for log4cxx::AppenderSkeleton'
/opt/ros/groovy/lib/libroscpp.so: error: undefined reference to 'log4cxx::helpers::ObjectImpl::addRef() const'
/opt/ros/groovy/lib/libroscpp.so: error: undefined reference to 'log4cxx::helpers::Pool::~Pool()'
/opt/ros/groovy/lib/libroscpp.so: error: undefined reference to 'typeinfo for log4cxx::Appender'
/opt/ros/groovy/lib/libroscpp.so: error: undefined reference to 'log4cxx::Logger::getRootLogger()'
/opt/ros/groovy/lib/libroscpp.so: error: undefined reference to 'log4cxx::Logger::getLogger(char const*)'
/opt/ros/groovy/lib/libroscpp.so: error: undefined reference to 'log4cxx::AppenderSkeleton::addRef() const'
/opt/ros/groovy/lib/libroscpp.so: error: undefined reference to 'log4cxx::Logger::getLoggerRepository() const'
/opt/ros/groovy/lib/libroscpp.so: error: undefined reference to 'typeinfo for log4cxx::helpers::ObjectImpl'
/opt/ros/groovy/lib/libroscpp.so: error: undefined reference to 'VTT for log4cxx::Appender'
/opt/ros/groovy/lib/libroscpp.so: error: undefined reference to 'log4cxx::helpers::Object::getClass() const'
/opt/ros/groovy/lib/libroscpp.so: error: undefined reference to 'log4cxx::spi::OptionHandler::getStaticClass()'
/opt/ros/groovy/lib/libroscpp.so: error: undefined reference to 'log4cxx::AppenderSkeleton::releaseRef() const'
/opt/ros/groovy/lib/libroscpp.so: error: undefined reference to 'log4cxx::spi::LocationInfo::getLineNumber() const'
/opt/ros/groovy/lib/libroscpp.so: error: undefined reference to 'log4cxx::Logger::getLogger(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
/opt/ros/groovy/lib/libroscpp.so: error: undefined reference to 'log4cxx::Level::getDebug()'
/opt/ros/groovy/lib/libroscpp.so: error: undefined reference to 'vtable for log4cxx::helpers::Object'
/opt/ros/groovy/lib/libroscpp.so: error: undefined reference to 'log4cxx::Level::getWarn()'
/opt/ros/groovy/lib/libroscpp.so: error: undefined reference to 'virtual thunk to log4cxx::helpers::ObjectImpl::addRef() const'
/opt/ros/groovy/lib/libroscpp.so: error: undefined reference to 'log4cxx::Appender::getClass() const'
/opt/ros/groovy/lib/libroscpp.so: error: undefined reference to 'log4cxx::helpers::ObjectPtrBase::~ObjectPtrBase()'
/opt/ros/groovy/lib/libroscpp.so: error: undefined reference to 'virtual thunk to log4cxx::helpers::ObjectImpl::~ObjectImpl()'
/opt/ros/groovy/lib/libroscpp.so: error: undefined reference to 'virtual thunk to log4cxx::helpers::ObjectImpl::releaseRef() const'
/opt/ros/groovy/lib/libroscpp.so: error: undefined reference to 'log4cxx::spi::LocationInfo::getMethodName() const'
/opt/ros/groovy/lib/libroscpp.so: error: undefined reference to 'log4cxx::AppenderSkeleton::doAppend(log4cxx::helpers::ObjectPtrT<log4cxx::spi::LoggingEvent> const&, log4cxx::helpers::Pool&)'
/opt/ros/groovy/lib/libroscpp.so: error: undefined reference to 'log4cxx::helpers::Object::getStaticClass()'
/opt ...
(more)
2014-01-28 17:22:29 -0500 marked best answer How to subscribe to odom properly in python

Hello, all,

I recently wrote a simple subscriber that subscribes to the topic /odom coming from the irobot_create_2_1 driver for an iCreate. However, when I simply print the odometry data and rotate the wheels myself, the data doesn't change. At the same time, though, if I re-run the Python Script, the data will have changed to the amount I previously rotated it.

Have I made a simple mistake? Or does /odom not publish the current transformation and rotation information.

(I noticed also that the time stamp doesn't change)

Thanks so much in advance for any advice!

Here's my source code:

#!/usr/bin/env python
import roslib; roslib.load_manifest('Phoebe')
import rospy
import irobot_create_2_1

from nav_msgs.msg import Odometry
from geometry_msgs.msg import *
from tf.msg import *



counter = 0

def Position(odom_data):

    global counter
    rospy.sleep(1)
    curr_time = odom_data.header.stamp
    pose = odom_data.pose.pose #  the x,y,z pose and quaternion orientation
    counter= counter+1
    print counter, curr_time
    print
    print pose


def transformation(tf_data):
    global counter
    rospy.sleep(1)
    transform = tf_data.transform
    print transform


def begin():
    while not rospy.is_shutdown():
        rospy.init_node('oodometry', anonymous=True) #make node 
        rospy.Subscriber('odom',Odometry,Position)


if __name__ == "__main__":
    begin()
    rospy.spin() # not really necessary because we have while not rospy.is_shutdown()
2014-01-28 17:22:24 -0500 marked best answer Turn a point cloud into an image with Python

Hi, everyone,

Recently, I tried to run through the pcl_ros tutorial to convert a point cloud from a Kinect to an image. My hope is to be able to do the exact same thing in Python, not C++, and then work with the image using the OpenCV Python interface.

here's the tutorial link: http://www.ros.org/wiki/pcl_ros/Tutor...

I hit a small snag, though. It seems like the tutorial is referencing a Ros Topic from openni_camera called /camera/depth/points2, but I can't seem to find this topic in list of topics published by openni_camera.

Rather, I found: /camera/depth/points, but this doesn't seem to generate an image when I make this change in the tutorial.

Will getting the image from /camera/depth/points2 be necessary to fulfill my overall goal?

Also, are there any other ways to easily convert a Point Cloud from the Kinect to an image in Python? Many Thanks in advance for everyone's words of wisdom!

2013-07-31 11:17:03 -0500 received badge  Famous Question (source)
2013-07-02 09:55:36 -0500 received badge  Famous Question (source)
2013-06-06 02:33:34 -0500 received badge  Notable Question (source)
2013-05-28 08:52:42 -0500 received badge  Taxonomist
2013-05-24 11:53:53 -0500 marked best answer Publish Kinect Depth information to a Ros Topic

Hello, all,

Recently, we've been attempting to access the kinect depth data from the published point cloud provided by the openni_node, but we've run into a couple stumbling points:

first, the ros tutorial for pcl_ros

http://www.ros.org/wiki/pcl_ros/Tutor...

references a topic published by openni called: /camera/depth/points2 but our version of openni_kinect only publishes: /camera/depth/points Are we using an outdated version?

Also, we tried working with /camera/depth/points and we believe that this information is published in binary format. When we attempted to convert the binary format of a single point to x,y,z information though, we received a list of 4 integers. Are we interpreting the information incorrectly?

We also subscribed to the /camera/depth/image, and we could access the depth information from a single point, but we're restricted to meter-by-meter resolution. Is there a better way of getting more resolution with the /camera/depth/image ?

Thanks for reading, and we appreciate any directions you can point us to accessing the depth information (of points) from the kinect.

Sincerely,

Poofjunior

2013-05-09 21:08:43 -0500 received badge  Scholar (source)
2013-05-09 21:08:35 -0500 commented answer "Are your messages built?" error from echoing that message (Groovy)

Oops! I forgot to source my setup.sh script in the devel folder. Afterwards, my ROS_PACKAGE_PATH points to the right directory and the ROSBAG that I wanted to play will now display the data from data_logger_measurement. Thanks everyone!

2013-05-09 21:05:24 -0500 received badge  Popular Question (source)
2013-05-09 08:08:10 -0500 commented question "Are your messages built?" error from echoing that message (Groovy)

Ah, this has got to be the problem. roscd won't tab-complete to that package. Under the old flavor, I could just change my package path to fix this. How do I resolve this in the Groovy?

2013-05-08 18:29:39 -0500 asked a question "Are your messages built?" error from echoing that message (Groovy)

Hello, everyone,

I've followed the steps closely defined here to create a custom message, editting my CMakeLists.txt, my package.xml, and my msg/data_logger_measurement.msg to create a new message.

I've been able to display the data with "rostopic echo /data_logger_measurement" in the past; however, now that I've rosbagged the data to revisit it a few weeks later, I cannot "rostopic echo /data_logger_measurement" when I'm playing a rosbag.

Instead, I get the error:

ERROR: Cannot load message class for [external_sensor_interface/data_logger_measurement]. Are your messages built?

The only changes that I can remember making are updating ROS when I performed a software update on Ubuntu.

Does anyone have any possible leads? (I may have made a few other changes in the past few weeks to ROS, but I cannot currently remember them.)

Thanks very much in advance!