Revision history - ROS Answers: Open Source Q&A Forum

$ catkin_make $ roscd openpose_ros $ roslaunch openpose_ros_node

I don't see a source devel/setup.bash in your copy-pasted console text.

You need to "activate" your workspace after you've built it using catkin_make, otherwise utilities like roscd and roslaunch will not know where to find the new packages that you just built.

~~$ catkin_make $ roscd openpose_ros $ roslaunch openpose_ros_nodeopenpose_ros_node~~

I don't see a source devel/setup.bash in your copy-pasted console text.

You need to "activate" your workspace after you've built it using catkin_make, otherwise utilities like roscd and roslaunch will not know where to find the new packages that you just built.

$ catkin_make
$ roscd openpose_ros
$ roslaunch openpose_ros_node

I don't see a source devel/setup.bash in your copy-pasted console text.

You need to "activate" your workspace after you've built it using catkin_make, otherwise utilities like roscd and roslaunch will not know where to find the new packages that you just built.

Edit: I only now see this:

$ roslaunch openpose_ros_node

roslaunch takes either one or two arguments:

a direct path to a .launch file
a package name and a (package relative path to a) .launch file

Your invocation is neither: openpose_ros_node is not a package name (that would probably be openpose_ros), and it's also not a launch file name.

From the build output you show, it would appear openpose_ros_node is a ROS node (ie: an executable binary).

Those you should start with rosrun $pkg $node_name, not roslaunch.

Revision history [back]