Skip to content

Conversation

timruhkopf
Copy link
Contributor

when using purely ask and tell instead of optimize, then smac does not need to know about the target_function and we can just drop the requirement by setting it to None. Should the user then however decide to call optimize, this must raise an ValueError. A few type checks and raises are necessary to ensure proper flow.

…then smac does not need to know about the target_function and we can just drop the requirement. Should the user then however decide to call optimize, this must raise an ValueError
Copy link
Collaborator

@benjamc benjamc left a comment

Choose a reason for hiding this comment

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

  • update changelog
  • Add short info to facade init about this behavior
    Other than that, LGTM!

@benjamc benjamc changed the base branch from main to development February 27, 2025 10:26
@benjamc benjamc removed the request for review from dengdifan February 27, 2025 10:26
…then smac does not need to know about the target_function and we can just drop the requirement. Should the user then however decide to call optimize, this must raise an ValueError
…then smac does not need to know about the target_function and we can just drop the requirement. Should the user then however decide to call optimize, this must raise an ValueError
@timruhkopf timruhkopf merged commit 6aedb86 into development Apr 16, 2025
11 checks passed
@benjamc benjamc deleted the feature/946_optional_target_function branch August 14, 2025 12:26
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.

[Feature] Remove target_function as required when using ask and tell interface

2 participants