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

About the performance on JHMDB #10

Open
r09921135 opened this issue Jan 5, 2023 · 1 comment
Open

About the performance on JHMDB #10

r09921135 opened this issue Jan 5, 2023 · 1 comment

Comments

@r09921135
Copy link

r09921135 commented Jan 5, 2023

Hi,

First of all, thank you for your great work!

I am wondering does your work get improvement only on UCF and AVA datasets?
Because I've run your code on JHMDB dataset without changing anything, the best frame-mAP I got is only 67%.
Is it because the training settings are only for UCF and AVA?

Also, I found that you freeze all the 2D and 3D backbone parameters when training on JHMDB, but in the original YOWO, they still allow the last few layers of backbone to be fine-tuned. Can you explain about this?

@yjh0410
Copy link
Owner

yjh0410 commented Jan 7, 2023

@r09921135
Hi,

Thanks for for your affirmation of my work.

JHMDB is a very small-scale dataset, which means that it is easily over fitted. This dilemma requires us to carefully adjust hyperparameters. I think such a small dataset is unconvincing, and I am not good at adjusting hyperparameters, so I do not deal with JHMDB dataset. Both UCF101-24 and AVA are large-scale benchmarks, so I think that the improvement on these two benchmarks can prove the effectiveness of my job.

All the settings for JHMDB as you can see in my project are just random and not a good choice.

If you solve this problem, I wish you could share the strategy you adopted. Thanks a lot.

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

2 participants