Fix TSNormalize to handle cases where max == min by setting output to the lower bound of the target range #943
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
- Resolved an issue where the normalization logic failed to handle cases where `max == min`. - When `max == min`, the output is now explicitly set to the target range lower bound (`range_min`). - Retained existing behavior for other scenarios and ensured compatibility with the normalization process.
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 Pull Request addresses an edge case in the
TSNormalizetransform wheremax == minin the input data, which would otherwise result in aNonereturn value during normalization.Instead of returning
None, the transform now handles this scenario gracefully by setting the output to the lower bound of the target range (range_min).