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
Good point, I have it already for a longer time on my bucket list, from the botorch side, this is already prepared: https://github.com/pytorch/botorch/blob/68fbb68d4a78efd2b803071d883081b2c45a70ae/botorch/models/transforms/input.py#L878
The question is how to set it up in BoFire. I would vote for setting up the domain still in the original non-transformed space and just tell the surrogate which input to transform, as it is currently also done for the input scalers fors continuous inputs. This needs to be made more flexible.
What do you think?
cc: @bertiqwerty: maybe we can discuss this also tmr in our meeting
Furthermore, the question would be if the log transformed inputs should then also undergo normalization/standardization and how to set this up in a flexible way.
We frequently encounter variables that are better modeled in the logarithmic space. It would be a cool feature to have bofire to model this directly.
@niklaswulkow please add/correct ;)
The text was updated successfully, but these errors were encountered: