-
Notifications
You must be signed in to change notification settings - Fork 13
Refactor One-shot configuration #156
Copy link
Copy link
Open
Labels
improvementImprovement that don't change the behaviour for a userImprovement that don't change the behaviour for a userperformanceTemporal/memory performance of the algorithmTemporal/memory performance of the algorithm
Metadata
Metadata
Assignees
Labels
improvementImprovement that don't change the behaviour for a userImprovement that don't change the behaviour for a userperformanceTemporal/memory performance of the algorithmTemporal/memory performance of the algorithm
Type
Fields
Give feedbackNo fields configured for issues without a type.
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_modelvariable.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.