Skip to content

Refactor One-shot configuration #156

Description

@david-chapela

Currently, the one-shot option is implemented by running the HyperOpt stage only once, so the setup values are automatically put in the best_bps_model variable.

To improve performance, might be interesting to avoid running HyperOpt stages and directly take the setup values as the final ones. This is, directly jump to the discovery of the final_bps_model.

Activity

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

Metadata

Metadata

Assignees

Labels

improvementImprovement that don't change the behaviour for a userperformanceTemporal/memory performance of the algorithm

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions