Pete Florence

Thanks for making the request. We should definitely support setting intrinsics in a config-type file, and make sure all stages of the pipeline are sourcing those same intrinsics.

Hi @EthonDeep, it seems like a driver/device match problem. have you launched your sensor with anything besides NiViewer? Also have you tried launching the sensor in ROS?

Hi @ianre657, that seems pretty useful you have worked through some of these compatibility issues. Would be happy to look at a PR once you have finished!

I would check your object_data.yaml file. Which mesh are you trying to use? Is it your own mesh, or one we provided?

Thanks for adding this issue On Wed, Jan 30, 2019 at 3:08 PM Greg Izatt wrote: > During acceptance testing of #360 > @peteflorence > and I found that one...

Hey @jmcculloch2018 and @gizatt , would we like to merge this sometime soon? Looks like some very useful stuff in here, for example I just cherry-picked this commit: https://github.com/RobotLocomotion/spartan/commit/8f0bf6f368721970a6aba7730eb49179208f8660

5 - done 6 - not an issue for me 7 - done 8.1 - i fixed the writing of the robot_data.yaml the last remaining thing is that the intrinsics...

Hi there, glad it worked for you with an Xtion. Intel RealSense SR300s are also of interest to us. I think possibly @5yler has taken SR300 data through the pipeline?...

For the record on this issue, I now have a direct ROSbag --> ElasticFusion driver, although it's not merged into this git codebase or in the docker hub image. If...

Woohoo!! Cool On Fri, Mar 16, 2018 at 8:44 AM 5yler wrote: > @peteflorence @laurimi > After an unfortunately long and drawn-out > approval process my ROS-LCM converter, rgbd_ros_to_lcm >...