PosteriorStandardDeviation docstring correction and upgrades to other documentation
#2071
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
facebook-github-bot
added
the
CLA Signed
|
@esantorella has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
Codecov Report
@@ Coverage Diff @@
## main #2071 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 179 179
Lines 15859 15859
=========================================
Hits 15859 15859
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
|
@esantorella merged this pull request in 84245d5. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
PosteriorMeanwas used instead ofPosteriorStandardDeviationSingleTaskGPand "Getting Started" documentation use single-precision data and non-standardized outcome data, which is not recommended usage and raises warnings. I changed the documentation to use an outcome transform and double-precision data.Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
N/A
Related PRs
#2060