-
Notifications
You must be signed in to change notification settings - Fork 186
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
Predictions are inverted (sometimes) #50
Comments
I've come up with a temporary workaround: swapping the order that the two classes are defined in the ARFF file. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I've noticed that the validation accuracy logged by dl4j is almost an exact inversion of the test set accuray reported by weka for some binary classification datasets I've been using.
To Reproduce
Steps to reproduce the behavior:
Note that this does not happen with all binary classification datasets I have used.
Expected behavior
Accuracy reported by dl4j should be similar to what is reported by weka.
The text was updated successfully, but these errors were encountered: