Meaning of "Trace Observations" in qMultiFidelityMaxValueEntropy Based Acquisition Functions #2867
-
Hi there, I am working with the qMultiFidelityLowerBoundMaxValueEntropy AF and was wondering what the meaning of "trace observations" is in this context. They are mentioned when talking about the expand function one can define and I thought it means "expanding" the current point of a certain fidelity level to all the other possible fidelities in order to calculate the covariance between the fidelity levels. Is it necessary to define it when using this acquisition function? Here is an excerpt of the code:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
@adrian-martens not sure what version of the code you're citing here, but he current main branch actually raises an error if you pass the The trace observation setup is mostly used for the trace-aware Knowledge Gradient acquisition functions. You can find more on the meaning of trace observations in Section 2.2 of https://arxiv.org/pdf/1903.04703 |
Beta Was this translation helpful? Give feedback.
@adrian-martens not sure what version of the code you're citing here, but he current main branch actually raises an error if you pass the
expand
argument for this acquisition function: https://github.com/pytorch/botorch/blob/4352bf3f2d94618cb2f4b80b8ba22c0753556440/botorch/acquisition/max_value_entropy_search.py#L815-L818 (this was added in #2769 since the acquisition function apparently did not handle this correctly). So it's definitely not necessary.The trace observation setup is mostly used for the trace-aware Knowledge Gradient acquisition functions. You can find more on the meaning of trace observations in Section 2.2 of https://arxiv.org/pdf/1903.04703