Skip to content

CrossValidation and TrainTest for AnomalyDetection #2686

Open

Description

There are two extensions for training, TrainTestSplit and CrossValidation, that are not clearly suited for AnomalyDetection as written.

TrainTestSplit is available in AnomalyDetection as it's in the TrainerCatalogBase, but anomaly detection scenarios often have structured data (e.g. time series) that we don't handle. Do we disable TrainTestSplit for AnomalyDetection? 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 a SamplingKeyColumn?

CrossValidation is not supported, but could be supported, should we solve the TrainTestSplit issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    APIIssues pertaining the friendly APIP2Priority of the issue for triage purpose: Needs to be fixed at some point.enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions