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

d3s on davis2016 #23

Open
riversci opened this issue Oct 18, 2020 · 4 comments
Open

d3s on davis2016 #23

riversci opened this issue Oct 18, 2020 · 4 comments

Comments

@riversci
Copy link

Hi, I think d3s is an excellent work which combined both tracking and segmentation. I like it very much. However, when I tested the pretrained model on davis2016, I got results as follow.
image
it's not as same as the paper.
image
I am confused. Can you give me some advice?

@alanlukezic
Copy link
Owner

One possible reason for different scores is different hardware. We observed that the performance can differ due to different GPUs or even library versions.
The other possible reason is tracker initialization. It should be initialized as:
tracker.initialize(img, gt_rect, init_mask=gt_mask)
where gt_rect is an 8-element vector of the rectangle corners: [x0, y0, x1, y1, x2, y2, x3, y2].

@riversci
Copy link
Author

Thank you for your answer. But How you get the gt_rect from gt_mask? Can you share some details?

@laisimiao
Copy link

@alanlukezic could you write a guide doc to help us evaluate D3S on davis such vos datasets?

@laisimiao
Copy link

@riversci how you test on davis2016, could you give some guidences?

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

3 participants