-
Notifications
You must be signed in to change notification settings - Fork 2
ADDING SMAC3 to Sparkle #109
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
Conversation
thijssnelleman
commented
Nov 15, 2024
- Created SMAC3 class to handle configuration calls
- Created SMAC3 scenario class to wrap around smac.scenario.Scenario class
- Created TargetRunner subclass for Sparkle to make sure solver metrics are done through RunSolver and not Python.time lib or Pynisher.
- Added all scenario parameters to be able to set through Sparkle
- Added one non-scenario parameter (Initial design parameter) max_ratio
- Set smac facade to be user-configurable
- Added several unittests
- Verified configure solver for runtime example works (Improved about one order size compared to SMAC2 with same budget)
- Still lacks platform support to make use of SMAC3 MO capabilities
- SMAC3 lacks support to differentiate between Wall and CPU time
sparkle/types/__init__.py
Outdated
| """Try to resolve the objective class by (case-sensitive) name. | ||
| convention: objective_name(variable-k)?(:[min|max])? | ||
| convention: objective_name(variable-k)?(:[min|max])?(:metric)? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add to doctoring the difference between metric and objective. + convention does not align with regex in line 15
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not one hundred percent sure what is meant here, but updating docstring