-
Notifications
You must be signed in to change notification settings - Fork 208
[ENH, REF]Refactored time-point based ROCKAD implementation #2804
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
# Conflicts: # aeon/testing/estimator_checking/_yield_estimator_checks.py # aeon/testing/testing_data.py
# Conflicts: # aeon/anomaly_detection/whole_series/__init__.py # docs/api_reference/anomaly_detection.rst
This reverts commit c245ccb.
Thank you for contributing to
|
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.
One open question is if we should remove _fit_predict() as it is just misleading for a semi-supervised approach, or should the user be able to use/test it even if ROCKAD is not intended to be used unsupervised?
I'm not sure it is misleading unless there is something off with the docs? it fits and predicts on the same data as intended. Sometimes there are more efficient ways to do this than calling both methods individually which is why we allow it to be overloaded.
We do more with tags and testing here #2652 |
…ction based rockad implementation
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
…refactor # Conflicts: # aeon/anomaly_detection/collection/_classification.py # aeon/anomaly_detection/collection/_outlier_detection.py # aeon/anomaly_detection/collection/base.py # aeon/anomaly_detection/series/base.py # aeon/anomaly_detection/series/distance_based/__init__.py # aeon/anomaly_detection/series/outlier_detection/__init__.py # aeon/anomaly_detection/series/outlier_detection/tests/test_one_class_svm.py # aeon/testing/estimator_checking/_yield_collection_anomaly_detection_checks.py # aeon/testing/estimator_checking/_yield_estimator_checks.py # aeon/testing/testing_data.py # aeon/utils/base/_identifier.py # aeon/utils/base/_register.py # aeon/utils/tags/_tags.py # docs/api_reference/anomaly_detection.rst
Hi, I have merged this and added some stuff to fix CI errors. If i accidentally missed some changes let me know, it was a bit messy with all the refactoring. |
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.
One open question is if we should remove _fit_predict() as it is just misleading for a semi-supervised approach, or should the user be able to use/test it even if ROCKAD is not intended to be used unsupervised?
Probably better to talk in the AD meeting coming up.
What does this implement/fix? Explain your changes.
One open question is if we should remove _fit_predict() as it is just misleading for a semi-supervised approach, or should the user be able to use/test it even if ROCKAD is not intended to be used unsupervised?