Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

image_proc/crop_decimate initialization problems

asked 2012-01-23 05:02:50 -0600

Yogi
411 ●12 ●15 ●21

Hi all I am having a lot of problems with crop_decimate nodelet. I am using a auto starting launch script which launches camera1394 -> debayer -> crop_decimate nodelets. It seems that 80% of the times, the crop_decimate nodelet will not launch properly, however if I launch it after a delay, the problem disappears. By not launching properly I mean that the crop_decimate nodelet exists, but it never publishes any images.

Has anybody else seen this problem? My current hacky solution of delayed launching of the crop_decimate nodelet is not very elegant, and I would rather not do it.

edit retag flag offensive close merge delete

add a comment

1 Answer

Sort by » oldest newest most voted

answered 2012-01-24 11:07:50 -0600

Patrick Mihelich
4336 ●32 ●37 ●44

What version of image_pipeline are you using? (On the command line, do rosversion image_pipeline)

Prior to 1.6.4, all of the image processing nodelets had race conditions on startup that could cause your problem. So make sure you're using image_pipeline 1.6.4.

edit flag offensive delete link

add a comment

Question Tools

Stats

Asked: 2012-01-23 05:02:50 -0600

Seen: 268 times

Last updated: Jan 24 '12

image_proc/crop_decimate initialization problems edit

1 Answer

Question Tools

Stats

Related questions

image_proc/crop_decimate initialization problems