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

evaluation.py VGGish is not being fitted #8

Open
rola93 opened this issue Jul 8, 2019 · 0 comments
Open

evaluation.py VGGish is not being fitted #8

rola93 opened this issue Jul 8, 2019 · 0 comments

Comments

@rola93
Copy link

rola93 commented Jul 8, 2019

Hello

I've been reading your evaluation.py example, and I can't understand why weights aren't loaded when the VGGish model is made, nor it's fit after the model is made.

As I see it, those lines:

sound_model = VGGish(include_top=False, load_weights=False)

should be:

sound_model = VGGish(include_top=False, load_weights=True)

or after that, it should be fitted before used (which currently isn't).

With the current implementation (i.e. load_weights=False), I run it on a subset of Speech Commands dataset, and I get the following results:

Report for testing
              precision    recall  f1-score   support

          no       0.90      0.90      0.90       386
         yes       0.90      0.90      0.90       397

    accuracy                           0.90       783
   macro avg       0.90      0.90      0.90       783
weighted avg       0.90      0.90      0.90       783

however, only switching load_weights=True, I get those:

Report for testing
              precision    recall  f1-score   support

          no       0.92      0.98      0.95       386
         yes       0.98      0.92      0.95       397

    accuracy                           0.95       783
   macro avg       0.95      0.95      0.95       783
weighted avg       0.95      0.95      0.95       783

As I see it, if the networks are not initialized with given weights, nor fitted, then its weights are just random initializations and therefore, the features computed by the model are just random computations on the input and therefore they don add too much value to the model itself.

I would love to hear your thoughts on this

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

1 participant