Skip to content

Tuning with filters recalculates filter values each iteration #1995

@Prometheus77

Description

@Prometheus77

Not a bug, but a recommendation to speed up execution. Currently, when using a filter to tune (e.g. tuning on fw.perc), it recalculates the filter values at each tuning iteration, which in the case of the default filter method (randomForestRFSRC) can be quite time consuming. Would be more efficient to have the tuner check whether there is a filter wrapper in the learner, and if so, to calculate the filter values at the beginning of the tuning process and then simply pass them forward into the filter at each iteration.

A prerequisite for this would be the ability to pass pre-defined filter values into a filter, which I do not believe is currently possible.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions