-
Notifications
You must be signed in to change notification settings - Fork 362
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
What is the purpose of the "lib" folder in this repository? #74
Comments
Same question here 🙌 I'm looking for evaluation code to reproduce the results presented in the paper. It seems that the 'lib' is used to generate the tracking evaluation plot shown in the paper, but I can't locate the entry function. I kindly hope the authors could clarify more about this 😊 |
@RelayZ, @LouisFinner Please use the script for your reference, this is a (very messy) script that we used to evaluate and plot the results need for paper. We also cross-verify the raw result files from other works to ensure our re-implementation is correct. Due to limited bandwidth on our side, please adapt the script for your usage on other dataset. One other good source to look in to will be the evaluation package by VastTrack.
|
@RelayZ We are reporting the VOT result on the testing split for GOT-10k and TrackingNet as both our them held their private leaderboard. Please refer to their official website and submit your result. |
Thank you for sharing this impressive work and for making it publicly available! I’ve been exploring this repository, which I understand is a SAM2-based object tracking framework. While going through the code, I came across a folder named lib located in the root directory. I was wondering if you could kindly clarify the primary purpose of the lib folder, particularly in relation to ARTrack.
Additionally, I am interested in evaluating the framework on GOT-10k, TrackingNet, NFS, OTB, etc. Would it be possible for you to provide the evaluation code or any relevant guidelines for performing evaluations on these datasets?
The text was updated successfully, but these errors were encountered: