-
Notifications
You must be signed in to change notification settings - Fork 464
Weighted pearson #3134
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
base: master
Are you sure you want to change the base?
Weighted pearson #3134
Conversation
@matsumotosan how is it going here? 🦩 |
@Borda Going to move over the test cases from the previous PR. Now that the weighted and unweighted metrics are separate, tests should be easier to write. |
sounds cool :) |
it would be great to ave this landed and then we can do another feature release :) |
for more information, see https://pre-commit.ci
@matsumotosan do you have a time estimate for finishing this one? |
@Borda Working on it right now, I think I might need a week. |
@matsumotosan please check Nicki comments :) |
…s. test with 4 samples instead of 2.
elif check_batch and not metric.dist_sync_on_step: | ||
batch_kwargs_update = { | ||
k: v.cpu() if isinstance(v, Tensor) else v | ||
k: v[i].cpu() if isinstance(v, Tensor) else v |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change is breaking class tests for metrics like precision, recall, MAP, MRR, fallout.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cc @SkafteNicki
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.
What does this PR do?
Fixes part of #1235
New PR for #1759
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃