OK, well I think that the workaround then is to write a node which
subscribes to both cameras, then publishes both images with the
timestamp from one of the cameras. That would be a temporary
workaround.

On Fri, Apr 30, 2010 at 7:47 PM, Patrick Mihelich
<mihelich@willowgarage.com> wrote:
> On Fri, Apr 30, 2010 at 7:00 PM, David Feil-Seifer
> <david.feilseifer@gmail.com> wrote:
>>
>> is it possible to use cameracalibrator node in
>> such a way that TimeSynchronizer is not so strict about timestamps?
>
> Not currently, no. stereo_image_proc has the same limitation. ROS "latest"
> allows TimeSynchronizer to have "policies" that may be less strict, but
> image_pipeline packages aren't taking advantage of that yet.
>
> Patrick
>
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>
>