-
Notifications
You must be signed in to change notification settings - Fork 209
[ENH] Refactor range-based metrics to restore original behavior #2781
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
Conversation
… metrics and integrate them into the AD test harness
Thank you for contributing to
|
aeon/benchmarking/metrics/anomaly_detection/_range_ts_metrics.py
Outdated
Show resolved
Hide resolved
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
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
Reference Issues/PRs
Fixes #2780
This deprecates / closes #2767
What does this implement/fix? Explain your changes.
range_f_score
,range_precision
, andrange_recall
and removes their deprecation (uses the implementation ofts_precision
,ts_recall
, andts_fscore
)ts_precision
,ts_recall
, andts_fscore
y_true
andy_pred
(which was confusing before)range_metrics.py
-module private (similar to all other modules in this folder) by renaming to_range_ts_metrics.py
. The methods are still accessible via their original name from the parent module (__init__.py
)Does your contribution introduce a new dependency? If yes, which one?
no