-
Notifications
You must be signed in to change notification settings - Fork 413
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
Remove UnstandardizeMCMultiOutputObjective #2362
Conversation
This pull request was exported from Phabricator. Differential Revision: D58164130 |
Summary: There is no reason to use this instead of the `Standardize` outcome transform. We could add a deprecation warning and remove it at a later release, but it is hidden deep in the code base that I think it's ok to remove it outright. I couldn't find any usage anywhere. Reviewed By: Balandat Differential Revision: D58164130
866c9d8
to
0430181
Compare
This pull request was exported from Phabricator. Differential Revision: D58164130 |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2362 +/- ##
==========================================
- Coverage 99.98% 99.98% -0.01%
==========================================
Files 189 189
Lines 16548 16516 -32
==========================================
- Hits 16545 16513 -32
Misses 3 3 ☔ View full report in Codecov by Sentry. |
…Transform (pytorch#2362) Summary: There is no reason to use these instead of the `Standardize` outcome transform. We could add a deprecation warning and remove it at a later release, but it is hidden deep in the code base that I think it's ok to remove it outright. I couldn't find any usage anywhere. Reviewed By: Balandat Differential Revision: D58164130
0430181
to
71dcc7d
Compare
This pull request was exported from Phabricator. Differential Revision: D58164130 |
…Transform (pytorch#2362) Summary: There is no reason to use these instead of the `Standardize` outcome transform. We could add a deprecation warning and remove it at a later release, but it is hidden deep in the code base that I think it's ok to remove it outright. I couldn't find any usage anywhere. Reviewed By: Balandat Differential Revision: D58164130
71dcc7d
to
cc9d770
Compare
This pull request was exported from Phabricator. Differential Revision: D58164130 |
This pull request has been merged in 91b45b7. |
Summary: There is no reason to use this instead of the
Standardize
outcome transform. We could add a deprecation warning and remove it at a later release, but it is hidden deep in the code base that I think it's ok to remove it outright. I couldn't find any usage anywhere.Reviewed By: Balandat
Differential Revision: D58164130