-
Notifications
You must be signed in to change notification settings - Fork 409
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
top_k
for multiclassf1score
is not working correctly
#1653
Labels
Milestone
Comments
eneserdo
added
bug / fix
Something isn't working
help wanted
Extra attention is needed
labels
Mar 25, 2023
Hi! thanks for your contribution!, great first issue! |
Hi I am interested in solving this issue. Can I work on it? |
@arijitde92 sorry for late reply, sure, you are welcome to take it π |
@Borda pls assign it to me |
@rittik9 Hi, are you still working on this issue? If not, I will ask to take the issue. |
yes, by next week I'll try to create a pr |
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
π Bug
top_k
argument ofMulticlassF1Score
is not working as expected. It suppose to give higher results astop_k
increases, but that is not happening sometimes.According to docs:
So, it must increase strictly always.
Also normally, when
top_k=num_classes
, it is expected to give 1 (100%), but that's not happening either.To Reproduce
Steps to reproduce the behavior...
Code sample
It returns
(tensor(0.1774), tensor(0.2740), tensor(0.3318))
AFAI understood from documentation, when I set
top_k=5
, it must give 1 because there only 5 classes anyway.More explicitly, I was expected the following two to have the same output:
But result is different
Environment
pip
):The text was updated successfully, but these errors were encountered: