-
Notifications
You must be signed in to change notification settings - Fork 43
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
probability_below_threshold does assert_scalar for threshold while threshold can also be a TensorType #883
Comments
Apologies for the very slow response! It is true that Are you trying to do constrained optimisation with multiple constraints? If so, have you seen this tutorial, which combines two |
I am indeed trying to use multiple constraints. I know the approach from the tutorial, but I recently switched to using |
I believe that's not currently supported, though I will check whether there exists any simple workaround. |
From what I tried, I believe |
We will have to extend trieste if we want to support applying different thresholds to the different submodels in a model stack. I'm still not sure what the best way of doing that is (there are a few options) but I'll change the ticket type to enhancement. |
|
Describe the bug
The class description of probability_below_threshold acquisition function says that threshold can be a float or TensorType. However, at initialization with threshold a TensorType, the tf.debugging.assert_scalar fails and errors out.
To reproduce
Steps to reproduce the behaviour:
Include a minimal reproducible code example if relevant.
Expected behaviour
A TensorType should be supported. I commented the assertion and then it gave me correct results with the TensorType. So, the assertion should be changed to check for scalars and tensortypes.
System information
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: