Scale obs errors before outlier detection #5126
Merged
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.
Also scale before creating update snapshot so that scaled errors are printed to the deprecated file.
Note that the scaling of errors before outlier detection with global_std_scaling is wrong as it should be
sqrt(global_std_scaling) but this was how it was done before merging the feature branch that introduced the new storage solution.
I've tested this by running REEK locally with code before and after the merge of the storage feature branch, and see only insignificant differences.
A test should be written that tests the outlier detection but that will have to wait.
Here's an issue though: #5137
Issue
Resolves #5094
Approach
Short description of the approach
Pre review checklist
Adding labels helps the maintainers when writing release notes. This is the list of release note labels.