Skip to content

ignoring predictor columns #221

@topepo

Description

@topepo

This issue describes how, once the data are given to a workflow, prediction always requires it as-is.

This will be increasingly important for supervised feature selection.

Look at my initial work on colander (still in private repo), there is an api called reset_columns() that edits the workflow's data objects. That's not great since we always try to remake the model or recipe when the data changes.

Alternatively, it might be better to have some sort of ignore_predictors() api that leaves the data intact but updates what the fit() and predict() methods for workflows do.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions