Skip to content

Conversation

@thijssnelleman
Copy link
Member

  • 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

"""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)?
Copy link
Collaborator

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

Copy link
Member Author

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

@thijssnelleman thijssnelleman merged commit 460c892 into development Dec 6, 2024
2 checks passed
@thijssnelleman thijssnelleman deleted the SPRK-335 branch December 6, 2024 19:24
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