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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Issues with qKG.evaluate() #587
Comments
To add to this, |
Thanks for raising this.
I think rather than doing something ad-hoc in the initializer, the proper thing to do here is to add a
Good point. I think the most logical thing to do would be to somehow incorporate the projection operation as part of the Let me see what I can come up with here. |
A consistent API like this will be useful and avoid ad-hoc inferring of batch shapes. See pytorch#587 for more context.
A consistent API like this will be useful and avoid ad-hoc inferring of batch shapes. See pytorch#587 for more context.
I see that you put up #588 for the batch shape. For the
|
Yeah this seems quite reasonable to me. @danielrjiang any thoughts? |
Thanks @saitcakmak, seems pretty useful to me too. |
Cool, I鈥檒l put up a PR soon. |
A consistent API like this will be useful and avoid ad-hoc inferring of batch shapes. See pytorch#587 for more context.
A consistent API like this will be useful and avoid ad-hoc inferring of batch shapes. See pytorch#587 for more context.
Summary: A consistent API like this will be useful and avoid ad-hoc inferring of batch shapes. See pytorch#587 for more context. Pull Request resolved: pytorch#588 Differential Revision: D24622409 Pulled By: Balandat fbshipit-source-id: 471a49eb0bdbb742b24a27b3a1bdd64efb7039bb
馃悰 Bug
i) This line raises an
AttributeError
with models that do not have an_input_batch_shape
attribute. (#578 as an example)botorch/botorch/optim/initializers.py
Line 328 in 7e2a404
ii) Since it is a subclass of
qKnowledgeGradient
,qMultiFidelityKnowledgeGradient
hasevaluate
method implemented. However, the current implementation ignores theproject
operator in the inner optimization, and may produce buggy output.Expected Behavior
i) The batch shape could be inferred from
model.train_inputs
batch shape. My observation is_input_batch_shape = model.train_inputs[0].shape[:-2]
, but I am not sure if this is always true. If this is true, a simple try/except should do it.ii) It should either raise a
NotImplementedError
, or be modified to accommodate theproject
operator.The text was updated successfully, but these errors were encountered: