Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor One-shot configuration #156

Open
david-chapela opened this issue Sep 26, 2024 · 0 comments
Open

Refactor One-shot configuration #156

david-chapela opened this issue Sep 26, 2024 · 0 comments
Assignees
Labels
improvement Improvement that don't change the behaviour for a user performance Temporal/memory performance of the algorithm

Comments

@david-chapela
Copy link
Collaborator

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.

@david-chapela david-chapela added performance Temporal/memory performance of the algorithm improvement Improvement that don't change the behaviour for a user labels Sep 26, 2024
@david-chapela david-chapela self-assigned this Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement Improvement that don't change the behaviour for a user performance Temporal/memory performance of the algorithm
Projects
None yet
Development

No branches or pull requests

1 participant