DOC: use np.copysign()
instead of np.sign()
#19278
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.
The basis vectors returned
scipy.linalg.null_space()
are guaranteed to be orthonormal, but whether they point in the "positive" or "negative" direction is arbitrary. To remove this source of non-determinism, the 1D documentation example recommends multiplying the basis vector by the sign of its first element.This seems like good advice, but there's a bug in the way it's implemented. The issue is that
np.sign(0) == 0
, so if the first element of the basis vector happens to be zero, then the whole vector gets erased. The solution is to usenp.copysign()
, which doesn't have this behavior (and which even handles -0 correctly).