G.A. vd. Hoorn

@jrgnicho: I've transferred this issue to here (ie `stomp_ros`).

@nilsmelchert wrote: > I actually like that the location of the hardware driver. Since the Issue you mentioned is still open, I would recommend to also move the staubli_val3_driver to...

@nilsmelchert wrote: > So in order to create PRs for the staubli repository, I just fork the current master branch from the `staubli` repository and add the packages I want...

I'm really rather busy right now, so I'll see if I can find 20 mins somewhere to make it available. It won't be today though I'm afraid.

@nilsmelchert wrote: > How can I help? and :+1: :100: for offering to help here btw, really appreciated.

As `CameraInfo` does have a `Header`, it could potentially be used, but ppl typically would use [image_transport](http://wiki.ros.org/image_transport) to match frames with their corresponding `CameraInfo` messages (via a [CameraSubscriber](http://docs.ros.org/kinetic/api/image_transport/html/classimage__transport_1_1CameraSubscriber.html)). See also...

> The bunny demo and our previous real-world applications use sensors with higher framerates, so the reconstruction is composed of possibly hundreds of scans and the weights of observed voxels...

> This would require some modifications to Yak to associate camera intrinsics with each image rather than loading them from a class-member parameter variable. Ideally this change would be designed...

Yes, that would make sense to maintain current behaviour.

Thanks for the PR @schornakj. I didn't open #25 for you to fix it, but just wanted to get some input on whether something like that would fit with the...