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
Comments
One possible reason for different scores is different hardware. We observed that the performance can differ due to different GPUs or even library versions. |
Thank you for your answer. But How you get the gt_rect from gt_mask? Can you share some details? |
@alanlukezic could you write a guide doc to help us evaluate D3S on davis such vos datasets? |
@riversci how you test on davis2016, could you give some guidences? |
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.
it's not as same as the paper.
I am confused. Can you give me some advice?
The text was updated successfully, but these errors were encountered: