| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ \
| | |
| | | |
ENH: Phase unwrapping generalized to arbitrary interval size
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | | |
Cleanup whitespace
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | | |
Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
|
| | |
| | |
| | |
| | | |
Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
|
| | |
| | |
| | | |
Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
|
| | |
| | |
| | |
| | | |
Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
|
| | |
| | |
| | |
| | | |
Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
|
| | | |
|
| | |
| | |
| | | |
Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
|
| | | |
|
| | |
| | |
| | | |
Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
|
| | |
| | |
| | |
| | | |
compatibility without boundary
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
unwrap function signature compatible
Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
|
| | |
| | |
| | | |
Phase unwrapping generalized to arbitrary interval size, such as 360 for phase in degree instead of radian. Also integer unwrapping is supported, but the return values are floats.
|
| | |
| | |
| | | |
Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
|
| | |
| | |
| | |
| | |
| | | |
Reject NaN as a percentile/quantile value. Previously NaNs could pass the range check `0 <= q <= 1`.
closes #18830
|
|\ \ \
| | | |
| | | | |
MAINT: Improve error message when common type not found.
|
| | | | |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
DOC: Update some plotting code to current Matplotlib idioms
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- 3D Axes are created via add_subplot(projection='3d')
- There is now a `stairs()` function that's specifically designed for
showing histogram curves
- Labels should be passed as keyword arguments to the plot functions
instead of to `legend()`, which reduces the risk of mixing them up.
- ensure equal axis scaling in the meshgrid example
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The array creation functions have the most to gain:
1. np.asarray is 4 times faster and commonly used.
2. Other functions are wrapped using __array_function__ in Python
making it more difficult
This commit (unfortunatly) has to do a few things:
* Modify __array_function__ C-side dispatching to accomodate
the fastcall argument convention.
* Move asarray, etc. to C after removing all "fast paths" from
np.array (simplifying the code)
* Fixup imports, since asarray was imported directly in a few places
* Replace some places where `np.array` was probably used for speed
instead of np.asarray or similar. (or by accident in 1 or 2 places)
|
| | |
| | |
| | |
| | |
| | |
| | | |
Subclass input of piecewise was already respected, so it seems more
logical to ensure the output is the same subclass (possibly just an
oversight that it was not done before).
|
| | |
| | |
| | |
| | | |
being returned
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
... or when the input isn't/cannot be a set. I left a few usages, e.g.
in random sampling, where "set" is reasonable as informal description of
an array as the order doesn't matter; however, for e.g. np.gradient the
order of the returned list is clearly important, so "set" is wrong.
Also some other minor doc edits noticed during the grepping: using
`shape` instead of `form` in `cov` is consistent with most other places;
the wording in `Polynomial.trim` now matches other methods on the same
class.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Adds a keyword-only dtype parameter to correlate and coerrcoef to allow
user to specify the dtype of the output.
Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
|
| | |
| | |
| | | |
* DOC: Fix typos in versionchanged.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This relies on the fact that `cos` is exactly symmetric around zero, but not around the floating-point approximation of `pi`.
Closes gh-17169.
|
| | | |
|
| | |
| | |
| | |
| | | |
Fix spacing that produced incorrect rendering
|
|\ \ \
| | | |
| | | | |
MAINT: Revert boolean casting back to elementwise comparisons in `trim_zeros`
|
| | | | |
|
| | | | |
|
| | | | |
|
|/ / /
| | |
| | |
| | | |
* BUG, API: Raise error on complex input to np.i0
|