-
Notifications
You must be signed in to change notification settings - Fork 13
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
feat: ibis_ml.metrics #174
Comments
To add: torchmetrics.functional has a lot of metrics implemented for PyTorch tensors in functional form. The typical input is
Some metrics are implemented modularly with an Notes
|
@zilto Sorry I didn't get back to you on this! If any of these would be useful for your work, or if you're more generally interested in contributing them, more than happy to add to the module @IndexSeek created! I'd also of course love to see some use in the wild—validating that this is a real challenge a number of people are facing—before going and implementing all of the metrics. :D
Yep! @IndexSeek's initial set of implementations are all tested against their scikit-learn equivalents, and I find it quite clean. |
Explore adding a metrics module to support computing classification metrics such as accuracy, precision, recall, and f1_score, as well as regression metrics such as MSE, RMSE, MAE, and MAPE.
This was brought up in ibis-project/ibis#10501.
A challenge with this implementation, at least for classification, is that calculating these metrics individually may be less performant, as it likely requires reshaping the data first for each one. Even with this being the case, we would likely still get pretty good performance, and if the backend supports result caching, it would be even better in those instances.
The text was updated successfully, but these errors were encountered: