-
Notifications
You must be signed in to change notification settings - Fork 31
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
thumos14_gt.json #41
Comments
@lurchycc good issue! In experiments, we directly took the THUMOS GT file from GTAD codes (https://github.com/frostinassiky/gtad/blob/master/evaluation/thumos_gt.json). To compare to GTAD, we did not change the json file. You can update the thumos14_gt.json and check the new results. |
Okay, thanks for your reply. |
the question that I asked: Hello, do you remove the background data provided by the thumos 14 dataset during training and testing? |
@menghuaa, I think you means that we remove the 'Ambiguous' class label. These data label is useless to training and testing for action detection task. GTAD is an action proposal task which predicts the foreground proposal and do not need the class label, so they can use the data sample with 'Ambiguous' class. In detection evaluation, GTAD also removes the 'Ambiguous' class data label according to their thumos_gt.json. |
thanks for your reply,for action proposal task,can I also remove the the data sample with 'Ambiguous' class in traning and testing? |
@menghuaa you can observe the gt file for ambiguous class to action proposal task. If ambiguous proposals are included in gt file, you should not remove them in training and testing. |
ok,thanks for you reply. As an additional question, have you ever seen the features of thumos14 fine tuned on the thumos14 dataset? |
@menghuaa no, I have never seen it. |
I noticed that the number of videos in the thumos14_gt. json file is 410, it seems that there are 3 videos missing in the test part, now I check that 'video_test_0000270' is not in the thumos14_gt. json, does this affect the evaluation result?
The text was updated successfully, but these errors were encountered: