-
Notifications
You must be signed in to change notification settings - Fork 51
Extend RobustGPSampler to handle environmental disturbance #328
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
Merged
+71
−16
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
d14c3c2
Add safety guard for const noisy
nabenabe0928 6dae507
Add const_noise_inds to samplers
nabenabe0928 69c08c3
Make it runnable
nabenabe0928 5616056
do not pass unnecessary const_noise_param_inds information to acquisi…
msakai 960e5e3
change RobustGPSampler.sample_relative to return randomly sampled val…
msakai 46f4bc8
factor out RobustGPSampler._optimize_params from RobustGPSampler.samp…
msakai 87c4759
add RobustGPSampler.get_robust_params
msakai 32e86b9
Merge branch 'main' into add-const-noisy
msakai 895b998
add docstring about const_noisy_param_names
msakai File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
This modification likely serves to prevent getting stuck in local optima. The change essentially involves setting the initial values for iterative optimization to random values without altering the acquisition function itself - the target of optimization. However, based on my personal verification, even with simple objective functions, the current GPSampler's acquisition function becomes extremely jagged and becomes ill-defined for gradient-based optimization. Therefore, rather than randomly shifting initial values, wouldn't it be better to smooth the acquisition function itself to make it more amenable to optimization?
Specifically, consider setting ConstrainedLogValueAtRisk's stabilizing_noise to a larger value than currently used (e.g., 1e-5). Note that this value requires adjustment based on the specific application.
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.
This change was made by @nabenabe0928 -san in 6dae507 .
@nabenabe0928 -san removed
best_paramsfrom CARBO for that reason (#301), but in this PR, it might be simply becauseNonewas passed asbest_paramsat every call site of_optimize_acqf.How about merging this PR as is, and re-add
best_paramsin different PR if necessary?Anyway, the fact that samples are overly concentrated in specific areas is a big issue, so I'd like to try modifying the
stabilizing_noiseparameter.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.
Sounds good! Sorry for the confusion. I misunderstood the motivation of setting
best_params=None.