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

Reset some turbo fields before starting new run #138

Merged
merged 2 commits into from
Feb 3, 2025
Merged

Conversation

wenatuhs
Copy link
Collaborator

@wenatuhs wenatuhs commented Feb 1, 2025

No description provided.

turbo_config = generator_params["turbo_controller"]
if type(turbo_config) is dict:
if turbo_config["name"] == "optimize":
try:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove the try except statements here and below, if resetting the turbo config fails, we need it to do so in a verbose fashion

Copy link
Collaborator Author

@wenatuhs wenatuhs Feb 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Those are for the cases where there are no such fields, such as when the user selects and configs the BO generator manually (sometimes they only config the fields they care about), in those cases the turbo_controller read from the generator param editor would be a dict but may not contain the center_x and best_value fields. We only silently pass on those cases (except KeyError)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point, but I don't think KeyError will actually be raised here if the key doesn't already exist. It would just add the field to the dict

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah right, nice catch, thanks! Will get the value first then!

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh wait, actually we can safely set the fields to None I guess as long as turbo_controller is a dict

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But would it matter if originally there are no such fields in the turbo_controller but we forcefully add in those fields and set them to None?

@wenatuhs wenatuhs merged commit 59b5b65 into main Feb 3, 2025
10 checks passed
@wenatuhs wenatuhs deleted the turbo-tmp-fix branch February 3, 2025 19:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants