Skip to content

The enhancement in the arguments of HyperparameterSearchSpaceUpdates #125

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

Closed
nabenabe0928 opened this issue Mar 5, 2021 · 0 comments
Closed
Assignees
Labels
enhancement New feature or request refactoring Improvement of readability and abstract codes

Comments

@nabenabe0928
Copy link
Collaborator

Currently, when we create configuration space, we often take var_name=((lower_bound, upper_bound), default_value) as an argument. However, since var_name is already used as a value of the variable, this is not Tuple[Tuple[type, type], type].
For example, while we use lr as a float in some functions, we take lr as a tuple in the function to create configuration space.
Meta-programming is not intuitive and not easy to understand. We should unite the name for consistency.

@nabenabe0928 nabenabe0928 added enhancement New feature or request refactoring Improvement of readability and abstract codes labels Mar 5, 2021
@ravinkohli ravinkohli self-assigned this Mar 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request refactoring Improvement of readability and abstract codes
Projects
None yet
Development

No branches or pull requests

2 participants