-
Notifications
You must be signed in to change notification settings - Fork 415
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
[Bug] Using batched_to_model_list on a model with AppendFeature input transform #1273
Comments
Hi @benmltu! Thanks for flagging the issue and the detailed repro. I haven't yet looked into the root cause, but this works if the model is in
Putting the model in train mode will effectively disable the |
Also, I am curious to hear about your use case for |
Summary: Fixes pytorch#1273 During model construction, input transforms should be in `train` mode (so that they only apply if `transform_on_train` is true). Having the input transforms in eval mode leads to buggy behavior due to `transformed_X` getting transformed when it shouldn't. Differential Revision: D37542474 fbshipit-source-id: f871ca15743030d6ccdbb251bb52ab9fe5f62333
Thanks for the fix! I was just looking at some of your recent work on risk measures and multi-objective BO and thought it would be cool to test these transformations in order to improve my own understanding. |
…h#1283) Summary: Pull Request resolved: pytorch#1283 Fixes pytorch#1273 During model construction, input transforms should be in `train` mode (so that they only apply if `transform_on_train` is true). Having the input transforms in eval mode leads to buggy behavior due to `transformed_X` getting transformed when it shouldn't. Differential Revision: D37542474 fbshipit-source-id: f4278294de5d83d967f3d21c312370e562cf372c
🐛 Bug
Hello there, I ran into an issue when trying to sample GPs which use the
AppendFeature
input transform. This issue arises from usingbatched_to_model_list
.To reproduce
Something about this particular
input_transform
appears to change after training:I have checked that this error does not occur when using
InputPerturbation
instead.The text was updated successfully, but these errors were encountered: