You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if this is intentional, but it seems like a bug to me. When fixing all features in optimize_acqf, the returned acquisition value changes from a float to a 1-D tensor. Haven't checked what happens for the other optimize_* functions.
Of course, this is a degenerate case since calling the optimization routing with zero degrees of freedom is sort of meaningless, but it can still be useful when invoking BoTorch procedurally from wrappers as in my case.
Please provide a minimal, reproducible example of the unexpected behavior.
Here a minimal example adjusted from the landing page code:
What happened?
Not sure if this is intentional, but it seems like a bug to me. When fixing all features in
optimize_acqf
, the returned acquisition value changes from a float to a 1-D tensor. Haven't checked what happens for the otheroptimize_*
functions.Of course, this is a degenerate case since calling the optimization routing with zero degrees of freedom is sort of meaningless, but it can still be useful when invoking BoTorch procedurally from wrappers as in my case.
Please provide a minimal, reproducible example of the unexpected behavior.
Here a minimal example adjusted from the landing page code:
Please paste any relevant traceback/logs produced by the example provided.
BoTorch Version
0.13.0
Python Version
3.10
Operating System
macOS
Code of Conduct
The text was updated successfully, but these errors were encountered: