Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: build a Google Tango version #59

Open
greymfm opened this issue Jun 26, 2017 · 2 comments
Open

Feature request: build a Google Tango version #59

greymfm opened this issue Jun 26, 2017 · 2 comments

Comments

@greymfm
Copy link

greymfm commented Jun 26, 2017

Google Tango's own localization engine has a major drawback: it's a blackbox, e.g. you cannot tune it for your specific application or get localization confidence feedback (e.g. number of detected feature points etc.) and so it's useless for e.g. open robotics projects...

Idea: make VINS a Google Tango version?

Here's how to get Google Tango sensor data (IMU+fisheye camera):
https://github.com/jinjaysnow/SenseData

Actually, the interesting part is in C++:
https://github.com/jinjaysnow/SenseData/blob/master/app/src/main/cpp/SenseDataApp.cpp

Do you think it's possible to create a VINS Google Tango version? :-) (example device: Lenovo PHAB 2 Pro, I have one here for testing: http://grauonline.de/wordpress/?page_id=2109)

I can help you with Android programming if you like... Or we try to persuade 'jinjaysnow' (author of SenseData) to add VINS to his project (ijinjay/SenseData#1) - what do you think?

@PeiliangLi
Copy link
Member

Thanks for the concern.
Basically, the sensor driver parts are only included in ViewController.mm, I add some comments for better understanding it, please check the latest commit.
You can port other parts without many modifications as long as the third-party (opencv, ceres, Eigen) can be used on your platform.

@greymfm
Copy link
Author

greymfm commented Jun 28, 2017

Thanks. jinjaysnow discovered that the initialization is really slow on his iPad Pro (ijinjay/SenseData#1) - maybe it's because it is initializing velocity, gravity, visual scale, and camera-IMU extrinsic calibration on the fly? (and it's probably just the first run) I'm thinking on using a cheap device for VINS, and a Google Tango phone looks like one - I hope VINS will work fast enough on it (Snapdragon 1.8GHz octa-core, 16 MP RGB camera, depth camera, a 130 degree global shutter fish eye camera, 200 Hz IMU).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants