-
Notifications
You must be signed in to change notification settings - Fork 55
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
Test set acc doesn't work #18
Comments
test_Y in here is not related with whether output test result or not. It just used to prevent error showing : “model has no attribution test _Y”. It may caused by wrong setting of your dataset. |
What does this line is doing then?
|
Also could you please provide "the code" to your dataset in encoding which all of the people around the world could read it. I've used many chinese character encodings but it didn't work. The pass is wrong. |
if you provide test_Y, then prediction procedure on test set will be performed after each training epoch. By set the dataset with the form of [train_X, train_Y, test _X, test_Y], you should get the right result. |
txt already fixed, password is '7mpb'. If you don't want to process the raw sound data with ‘wav’ form, you don't need to download it. |
Thank you for your quick answers.
When i remove comment from |
I was working on this and I had the same problem of @Salidor. Can you please tell the exact procedure in order to give |
Hello, if you use the data set offered by me, it indeed will not show the results, since the data set are downloaded from the internet and it dosen't provide labels. Try to use youself data set or |
Thank you, I tried with some data and all worked. But could you provide me how is it possible that, with my data, I always obtain 100% test accuracy and 50-60% train accuracy? How is this possible? It seems that it is always going on overfitting. |
That is confusing. Firstly, to improve train accuracy, you can appropriately adjust |
I am setting the line test_Y to true:
But it still doesn't show the accuracy of test set
The text was updated successfully, but these errors were encountered: