MAINT: stats.epps_singleton_2samp: NaNs/Infs in input -> NaNs in output #23893
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.
Reference issue
Follow-up to gh-23881
What does this implement/fix?
Currently, NaNs in the input of
epps_singleton_2sampproduce NaNs in the output, whereas Infs result in an error. Either the way, the calculation can't produce a valid number (e.g. in the Inf case, we have sines and cosines of infinity), so let's keep the result consistent. Now that the function is vectorized, it is preferable to return normally with NaNs in the output that correspond with affected slices. This PR makes that change.Additional information
@j-bowhay also replaced
axis : Nonewithaxis : 0as appropriate in the documentation ofepps_singleton_2sampandkruskal.