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

anchor frame time problem #28

Closed
HeadReaper-hc opened this issue Dec 14, 2019 · 2 comments
Closed

anchor frame time problem #28

HeadReaper-hc opened this issue Dec 14, 2019 · 2 comments
Labels
question Theory or implementation question

Comments

@HeadReaper-hc
Copy link

HeadReaper-hc commented Dec 14, 2019

You said set the first measurement to be the anchor frame,but in the FUNCTION single_triangulationfeat->anchor_clone_timestamp = feat->timestamps.at(feat->anchor_cam_id).back(); you set the newest time, Am I not understanding correctly?

besides in the file of FeatureInitializerOptions.h/// **Minimum** distance to accept triangulated features double max_dist = 40;

@goldbattle goldbattle added the question Theory or implementation question label Dec 14, 2019
@goldbattle
Copy link
Member

Yes, we do this since if we initialize a feature in the oldest frame, right away we need to perform an anchor change since that old clone will be marginalized. We do loop through and find which camera has the most measurements, and use that frame to anchor the feature in.

@HeadReaper-hc
Copy link
Author

Yes, we do this since if we initialize a feature in the oldest frame, right away we need to perform an anchor change since that old clone will be marginalized. We do loop through and find which camera has the most measurements, and use that frame to anchor the feature in.
thank you for your reply

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

No branches or pull requests

2 participants