Allow non-unique and non-monotonic coordinates in get_clean_interp_index and polyfit #4099
+26
−9
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.
isort -rc . && black . && mypy . && flake8whats-new.rstfor all changes andapi.rstfor new APIPull #3733 added
da.polyfitandxr.polyvaland is usingxr.core.missing.get_clean_interp_indexin order to get the fitting coordinate. However, this method is stricter than what polyfit needs: as innumpy.polyfit, non-unique and non-monotonic indexes are acceptable. This PR adds astrictkeyword argument toget_clean_interp_indexso we can skip the uniqueness and monotony tests.ds.polyfitandxr.polyvalwere modified to use that keyword. I only added tests forget_clean_interp_index, could add more forpolyfitif requested.