You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#368 created the concept of having AnomalyDetector type models which add an anomaly functionality to any base_estimator
Potential Feature
Implement, in some way, that this can be used inside of a Pipeline as a Transformer. So that perhaps one could use such a model in a FeatureUnion to further predict an anomaly via another type of AnomalyDetector
Probable Implementation?
One possible solution is to implement .transform method on the AnomalyDetector model, such that all training would occur there with base_estimator and then output the anomaly calculation(s) as features.
The text was updated successfully, but these errors were encountered:
milesgranger
changed the title
Potential: Allow AnomalyDetector models as transformers.
Discussion: Allow AnomalyDetector models as transformers.
Aug 7, 2019
milesgranger
changed the title
Discussion: Allow AnomalyDetector models as transformers.
RFC: Allow AnomalyDetector models as transformers.
Aug 7, 2019
milesgranger
changed the title
RFC: Allow AnomalyDetector models as transformers.
RFC: Allow AnomalyDetector models to act as transformers.
Aug 7, 2019
Topic
#368 created the concept of having
AnomalyDetector
type models which add an anomaly functionality to anybase_estimator
Potential Feature
Implement, in some way, that this can be used inside of a
Pipeline
as aTransformer
. So that perhaps one could use such a model in aFeatureUnion
to further predict an anomaly via another type ofAnomalyDetector
Probable Implementation?
One possible solution is to implement
.transform
method on theAnomalyDetector
model, such that all training would occur there withbase_estimator
and then output the anomaly calculation(s) as features.The text was updated successfully, but these errors were encountered: