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.

Sign up for GitHub

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

Jump to bottom

Incorrect Accuracy #64

Open
Berkmann18 opened this issue May 2, 2019 · 0 comments
Open

Incorrect Accuracy #64

Berkmann18 opened this issue May 2, 2019 · 0 comments

Comments

@Berkmann18
Copy link
Contributor

Berkmann18 commented May 2, 2019 •
edited

After doing some checks on my limbdu wrapper, and seeing that the Accuracy fields don't return what one would except knowing TP, TN and count's values (for both microAverage and macroAverage).
I was wondering, why is the TRUE field used for calculating Accuracy when it's not equal to TP which means it's not using the standard (TP + TN) / count formula which applies to both 2-class and multi-class classifications?
@Berkmann18 Berkmann18 changed the title TRUE != TP Incorrect Accuracy May 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Berkmann18