Open rogancarr opened 5 years ago
This is a great issue and I completely agree with the suggestion, I am going to remove from Project 13 as this can be implemented without breaking change post March because we still view this as a very pertinent issue in many situations.
@shauheen Note that if we want to drop the TrainTestSplit
API as it is currently implemented from AnomalyDetection, this will be a breaking change post-March.
There are two extensions for training,
TrainTestSplit
andCrossValidation
, that are not clearly suited forAnomalyDetection
as written.TrainTestSplit
is available inAnomalyDetection
as it's in theTrainerCatalogBase
, but anomaly detection scenarios often have structured data (e.g. time series) that we don't handle. Do we disableTrainTestSplit
forAnomalyDetection
? Do we add support for some sorts of structured data different than we have now? Do we assume that all structural problems can be solved with aSamplingKeyColumn
?CrossValidation
is not supported, but could be supported, should we solve theTrainTestSplit
issue.