Skip to content

Better initialization evaluation #98

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

Open
steevo87 opened this issue Sep 30, 2014 · 0 comments
Open

Better initialization evaluation #98

steevo87 opened this issue Sep 30, 2014 · 0 comments
Assignees

Comments

@steevo87
Copy link
Owner

Provide it with max number of frames or time as usual. However, in evaluation mode, it will not test randomly. Rather, it will test exhaustively and record all relevant scores. Furthermore, it will record some more information including a score which will be a generalization test. This score will be calculated by estimating the pose of all other cameras (with sufficiently shared points) in the subset, and calculating the average reprojection error. Also recorded will be the number of other cameras that were able to have their poses estimated, to help prevent skewed results.

If you can get sufficient data (e.g. run this with lots of different sequences, producing many files) then you might be able to more effectively calculate appropriate scorecard values. Later on, you can look at tasks for actually finding better features, and/or doing learning.

@steevo87 steevo87 self-assigned this Sep 30, 2014
@steevo87 steevo87 added this to the Windows - Motion Estimation milestone Sep 30, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant