Moved all data scaling functions to a dedicated Scaler object. #245
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
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.
This consolidates all data scaling functions to a single location in a dedicated object.
Touches functionality in training (BaseTrainer), testing (BaseTester), dataset (BaseDataset). Uncertainty sampling is affected because it requires an unscaled value for '0'. All child data classes in datazoo are affected because BaseDataset no longer accepts a scaler dictionary.
Preserves all backward compatibility for old scaler files EXCEPT that it removes support for scaler files that are 2 generations old (these files have keys labeled "camels_attrs').