-
Notifications
You must be signed in to change notification settings - Fork 411
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
SMAP regression error #375
SMAP regression error #375
Conversation
Hello @hugoperrin! Thanks for updating this PR. There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻 Comment last updated at 2021-07-16 13:25:56 UTC |
for more information, see https://pre-commit.ci
Codecov Report
@@ Coverage Diff @@
## master #375 +/- ##
==========================================
+ Coverage 96.42% 96.46% +0.03%
==========================================
Files 112 114 +2
Lines 3665 3705 +40
==========================================
+ Hits 3534 3574 +40
Misses 131 131
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
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.
Looks great. Two things:
- Remember to add an note in the
Changelog
file - The function that is compared against takes a
multioutput
argument but the functional/modular implementation of SMAPE does not. Why is that?
torchmetrics/functional/regression/symmetric_mean_absolute_percentage_error.py
Show resolved
Hide resolved
torchmetrics/functional/regression/symmetric_mean_absolute_percentage_error.py
Outdated
Show resolved
Hide resolved
Co-authored-by: Nicki Skafte <[email protected]>
for more information, see https://pre-commit.ci
…perrin/metrics into feat/smape_regression_error
@hugoperrin mind check last comments from @SkafteNicki, mainly related to references |
@Borda I updated the needed docs, I think this should be good, I'll wait on the CI to finish and fix things if things are needed to be fixed then :) Thank you for your quick feedback :) PS: should I squash the commits by the way? |
no need, well do it with all PR by default: squash + merge @hugoperrin seems it is your first PR so GH requires to allow running CI by a maintainer, so pls when you see it is hanging, pls ping me in slack so we can speed it up :] |
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.
LGTM
Before submitting
What does this PR do?
This PR adds SMAPE regression metric: #372.
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 🙃