| 2019-03-02 14:01:00 -0500 | received badge | ● Famous Question
(source)
|
| 2019-03-02 14:01:00 -0500 | received badge | ● Notable Question
(source)
|
| 2019-03-02 14:01:00 -0500 | received badge | ● Popular Question
(source)
|
| 2017-11-29 05:19:37 -0500 | received badge | ● Famous Question
(source)
|
| 2017-04-17 03:02:54 -0500 | received badge | ● Notable Question
(source)
|
| 2017-04-17 03:02:54 -0500 | received badge | ● Popular Question
(source)
|
| 2017-03-19 13:51:43 -0500 | received badge | ● Favorite Question
(source)
|
| 2017-02-14 18:36:48 -0500 | asked a question | Compress images into custom message I want to build a frame filter to synchronize the image streams from an RGBD camera into one message. I am using a ApproximateTime Synchronizer to listen to the sensor_msgs/Image and sensor_msgs/CameraInfo streams and want to publish them in a single message (see blow). How do I compress/decompress the images to put them into the message? Is it possible to build the messages manually by compressing/decompressing the images with OpenCV? Can I utilize image_transport for that to avoid high memory consumption across several nodes?
Frame.msg Header header
sensor_msgs/CompressedImage rgb_image
sensor_msgs/CompressedImage depth_image
sensor_msgs/CameraInfo rgb_cam
sensor_msgs/CameraInfo depth_cam
|
| 2017-01-19 16:06:26 -0500 | received badge | ● Famous Question
(source)
|
| 2016-12-23 02:33:43 -0500 | received badge | ● Notable Question
(source)
|
| 2016-12-15 01:03:05 -0500 | received badge | ● Popular Question
(source)
|
| 2016-11-29 19:23:26 -0500 | received badge | ● Enthusiast
|
| 2016-11-27 10:41:48 -0500 | asked a question | OpenNI camera launch - Failed to load nodelet, process has died I am trying to start up the Astra rgbd camera on a RPi with ros using the astra_launch package and I get the following errors: $ roslaunch astra_launch astra.launch
[...] process[camera/camera_nodelet_manager-2]: started with pid [1758]
process[camera/driver-3]: started with pid [1764]
process[camera/rgb_rectify_color-4]: started with pid [1765]
process[camera/depth_rectify_depth-5]: started with pid [1771]
[ INFO] [1480263571.437579437]: Initializing nodelet with 4 worker threads.
process[camera/depth_metric_rect-6]: started with pid [1789]
process[camera/depth_metric-7]: started with pid [1816]
process[camera/depth_points-8]: started with pid [1835]
process[camera/register_depth_rgb-9]: started with pid [1848]
[ INFO] [1480263571.833863631]: Device "2bc5/0402@1/4" found.
process[camera/points_xyzrgb_sw_registered-10]: started with pid [1864]
Warning: USB events thread - failed to set priority. This might cause loss of data...
process[camera/depth_registered_sw_metric_rect-11]: started with pid [1891]
process[camera_base_link-12]: started with pid [1902]
process[camera_base_link1-13]: started with pid [1918]
process[camera_base_link2-14]: started with pid [1939]
process[camera_base_link3-15]: started with pid [1960]
[FATAL] [1480263575.723996791]: Failed to load nodelet '/camera/depth_registered_sw_metric_rect` of type `depth_image_proc/convert_metric` to manager `camera_nodelet_manager'
[FATAL] [1480263575.724330379]: Failed to load nodelet '/camera/register_depth_rgb` of type `depth_image_proc/register` to manager `camera_nodelet_manager'
[FATAL] [1480263575.724582249]: Failed to load nodelet '/camera/points_xyzrgb_sw_registered` of type `depth_image_proc/point_cloud_xyzrgb` to manager `camera_nodelet_manager'
[FATAL] [1480263575.725682543]: Failed to load nodelet '/camera/depth_metric_rect` of type `depth_image_proc/convert_metric` to manager `camera_nodelet_manager'
[FATAL] [1480263575.726006600]: Failed to load nodelet '/camera/depth_metric` of type `depth_image_proc/convert_metric` to manager `camera_nodelet_manager'
[FATAL] [1480263575.726215815]: Failed to load nodelet '/camera/depth_points` of type `depth_image_proc/point_cloud_xyz` to manager `camera_nodelet_manager'
[FATAL] [1480263575.726566225]: Failed to load nodelet '/camera/rgb_rectify_color` of type `image_proc/rectify` to manager `camera_nodelet_manager'
[FATAL] [1480263575.726667317]: Failed to load nodelet '/camera/depth_rectify_depth` of type `image_proc/rectify` to manager `camera_nodelet_manager'
[camera/camera_nodelet_manager-2] process has died [pid 1758, exit code -11, cmd /opt/ros/kinetic/lib/nodelet/nodelet manager __name:=camera_nodelet_manager __log:=/home/pi/.ros/log/45647dd8-b4bd-11e6-a4ec-b827eb2510df/camera-camera_nodelet_manager-2.log].
log file: /home/pi/.ros/log/45647dd8-b4bd-11e6-a4ec-b827eb2510df/camera-camera_nodelet_manager-2*.log
[camera/rgb_rectify_color-4] process has died [pid 1765, exit code 255, cmd /opt/ros/kinetic/lib/nodelet/nodelet load image_proc/rectify camera_nodelet_manager --no-bond image_mono:=rgb/image_raw image_rect:=rgb/image_rect_color __name:=rgb_rectify_color __log:=/home/pi/.ros/log/45647dd8-b4bd-11e6-a4ec-b827eb2510df/camera-rgb_rectify_color-4.log].
log file: /home/pi/.ros/log/45647dd8-b4bd-11e6-a4ec-b827eb2510df/camera-rgb_rectify_color-4*.log
[camera/depth_rectify_depth-5] process has died [pid 1771, exit code 255, cmd /opt/ros/kinetic/lib/nodelet/nodelet load image_proc/rectify camera_nodelet_manager --no-bond image_mono:=depth/image_raw image_rect:=depth/image_rect_raw __name:=depth_rectify_depth __log:=/home/pi/.ros/log/45647dd8-b4bd-11e6-a4ec-b827eb2510df/camera-depth_rectify_depth-5.log].
log file: /home/pi/.ros/log/45647dd8-b4bd-11e6-a4ec-b827eb2510df/camera-depth_rectify_depth-5*.log
[camera/depth_metric_rect-6] process has died [pid 1789, exit code 255, cmd /opt/ros/kinetic/lib/nodelet/nodelet load depth_image_proc/convert_metric camera_nodelet_manager --no-bond image_raw:=depth/image_rect_raw image:=depth/image_rect __name:=depth_metric_rect __log:=/home/pi/.ros/log/45647dd8-b4bd-11e6-a4ec-b827eb2510df/camera-depth_metric_rect-6.log].
log file: /home/pi/.ros/log/45647dd8-b4bd-11e6-a4ec-b827eb2510df/camera-depth_metric_rect-6*.log
[camera/depth_metric-7] process has died [pid 1816, exit code 255, cmd /opt/ros/kinetic/lib/nodelet/nodelet load depth_image_proc/convert_metric camera_nodelet_manager --no-bond image_raw:=depth/image_raw image:=depth/image __name:=depth_metric __log:=/home/pi/.ros/log/45647dd8-b4bd-11e6-a4ec-b827eb2510df/camera-depth_metric-7.log].
log ...
(more) |
| 2016-11-26 02:11:57 -0500 | asked a question | Segmentation fault on ros.spin() I installed ROS from source (ros_comm) on a Raspberry Pi 3 and I cannot launch the majority of modules. When using $ roslaunch ... ... on existing launch files I get constant process has died into restarting process errors.
The following code throws me straight to a Segmentation fault. Applying subscribers before spinning doesn't really do anything. #include <ros/ros.h>
int main(int argc, char **argv)
{
ros::init(argc, argv, "my_node");
ros::spin();
}
I tried reinstalling ros, but the issue remains. The installation goes, from what I can see in the logs, without any errors. What could be the problem here? |
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.