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

Does test_tracktor.py detect and add new boxes that are not included in the public detection? #85

Closed
igygi opened this issue May 9, 2020 · 2 comments

Comments

@igygi
Copy link

igygi commented May 9, 2020

Hi,

I'd like to clarify whether the algorithm detects new boxes (not included in the public detection set) as well during inference, aside from regressing the positions of the boxes in the public detection set.

For example, what happens if in frame t+1, a bounding box in frame t is regressed to position (x1, y1, x2, y2) but in the public detection set, there is no bounding box in frame t+1 that intersects with this regressed position?

Thank you.

@timmeinhardt
Copy link
Collaborator

Hello, thank you for your interest in our research. If applied with public detections our Tracktor framework starts any regression only with bounding box form the set of public detections. However, as you described, it is possible for the regression to produce bounding boxes in subsequent frames which do not intersect with any of the public detections in that particular frame. We had some discussions regarding the "publicness" of our method in #24 .

@igygi
Copy link
Author

igygi commented Jun 16, 2020

This is understood. Thanks so much @timmeinhardt for your help and for this wonderful work.

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