We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In original paper (on page 2, section 2.2) the authors said that they keep last 100 feature for each track to calculate the cosine distance metric :
But in their code here, they delete all feature every time a confirmed track has been update :
I don't understand why, I am interested in it because I want to use deepSORT in my own project and utilize the feature vector for some purpose.
The text was updated successfully, but these errors were encountered:
@nwojke I apologize for bothering you, but the purpose is to optimize for time and memory, isn't it?
Sorry, something went wrong.
No branches or pull requests
In original paper (on page 2, section 2.2) the authors said that they keep last 100 feature for each track to calculate the cosine distance metric :
But in their code here, they delete all feature every time a confirmed track has been update :
I don't understand why, I am interested in it because I want to use deepSORT in my own project and utilize the feature vector for some purpose.
The text was updated successfully, but these errors were encountered: