| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
[skip ci]
|
|
|
|
| |
[ci skip]
|
| |
|
|
|
|
| |
Mentioned here: http://stackoverflow.com/questions/37625478/why-is-ones-like-listed-as-a-ufunc
|
|
|
|
|
|
|
|
|
|
|
| |
As one can easily encounter when working with high-order signal processing
filters, converting a high-order polynomial from its roots to its polynomial
coefficients can be quite lossy, leading to inaccuracies in the filter's
properties.
This PR adds a new function, `polyrootval` - based on `polyval` - that
evaluates a polynomial given a list of its roots. The benefit of calculating it
this way can be seen at scipy/scipy:6059. Some tests are included, as well.
|
|
|
|
|
| |
Changed/corrected Time span - relative and absolute - for second, millisecond and microsecond.
There were slight differences and was noted duly in the issue. See #6711 (https://github.com/numpy/numpy/issues/6711)
|
|
|
|
|
|
|
| |
I do not think that these two function are ufuncs since they do not
have an optional [, out] argument. From the doc:
- All ufuncs can also take output arguments.
|
| |
|
|\
| |
| | |
ENH: adds np.nancumsum and np.nancumprod
|
| |
| |
| |
| |
| |
| |
| |
| | |
This PR adds an implementation of `nancumsum` and `nancumprod`.
The actual function is a two-liner adapted from `nansum`.
Its structure is adapted from PR: https://github.com/numpy/numpy/pull/5418/
|
|/
|
|
| |
Space added to resolve misrendering of monospace (``) delimiters.
|
| |
|
|
|
|
| |
[ci skip]
|
|\
| |
| | |
Generalized flip
|
| | |
|
|\ \
| | |
| | | |
DOC: add nanprod to the list of math routines
|
| | |
| | |
| | | |
This was otherwise undocumented, so the nanprod.rst page wasn't being generated.
|
| |/
|/| |
|
| |
| |
| | |
Docs looked funny at that point.
|
| | |
|
|\ \
| | |
| | | |
API: Make datetime64 timezone naive
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes GH3290
With apologies to mwiebe, this rips out most of the time zone parsing from
the datetime64 type.
I think we mostly sorted out the API design in discussions last year, but
I'll be posting this to the mailing list shortly to get feedback.
Old behavior:
# string parsing and printing defaults to your local timezone :(
>>> np.datetime64('2000-01-01T00')
numpy.datetime64('2000-01-01T00:00-0800','h')
New behavior:
# datetime64 is parsed and printed as timezone naive
>>> np.datetime64('2000-01-01T00')
numpy.datetime64('2000-01-01T00','h')
# you can still supply a timezone, but you get a deprecation warning
>>> np.datetime64('2000-01-01T00Z')
DeprecationWarning: parsing timezone aware datetimes is deprecated; this
will raise an error in the future
numpy.datetime64('2000-01-01T00','h')
|
|/ / |
|
| |
| |
| |
| | |
Fixes gh-7010
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes GH2039
This function provides a much more intuitive interface than `np.rollaxis`,
which has a confusing behavior with the position of the `start` argument:
http://stackoverflow.com/questions/29891583/reason-why-numpy-rollaxis-is-so-confusing
It was independently suggested several times over the years after discussions
on the mailing list and GitHub (GH2039), but never made it into a pull request:
https://mail.scipy.org/pipermail/numpy-discussion/2010-September/052882.html
My version adds support for a sequence of axis arguments. I find this behavior
to be very useful. It is often more intuitive than supplying a list of
arguments to `transpose` and also nicely generalizes NumPy's existing axis
manipulation routines, e.g.,
def transpose(a, order=None):
if order is None:
order = reversed(range(a.ndim))
return moveaxes(a, order, range(a.ndim))
def swapaxes(a, axis1, axis2):
return moveaxes(a, [axis1, axis2], [axis2, axis1])
def rollaxis(a, axis, start=0):
if axis < start:
start -= 1
return moveaxes(a, axis, start)
|
| |
| |
| | |
This looks more conventionnal
|
| |
| |
| |
| |
| |
| | |
* Change ".. function::" -> ".. method::"
* Remove "self" argument
* Change "self" to "obj" in __array_finalize__
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
The user guide was missing a quick tutorial --- the basics.* stuff is
somewhat too complex already.
The "building numpy" instructions also should not be "introductory
material".
|
| | |
|
| | |
|
|\ \
| | |
| | | |
DOC: Fixed a typo at line 289 at c-api.array.rst
|
| |/
| |
| |
| | |
Fixes #6521
|
|\ \
| |/
|/| |
DOC: fixed typo in arrays.classes.rst
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
| |
The check_return argument and ufunc object field was never used; ditto
for the "new" inner loop selector (which was never implemented), along
with associated typedefs. Since I was looking at this code anyway trying
to figure out which parts were actually in use, I figured I'd clear up
some of the brush to make it easier next time...
|
| |
|
| |
|
|
|
|
|
| |
It may be that you can say that it cannot happen when grow inner
is not enabled as well.
|
|
|
|
| |
The lists needed blank lines before starting.
|
|
|
|
| |
The proper reference is in routines.rst.
|
|
|
|
| |
Also correct its documented default value.
|
|
|
|
| |
List needs to be preceded by blank line.
|
| |
|
|
|
|
|
|
|
| |
Examples
:cdata: -> :c:data:
.. cfunction:: -> .. c:function::
|
|
|
|
|
|
|
| |
Update docs for boolean array indexing and nonzero order.
Add links to row-major and column-major terms where they appear.
Closes #3177
|
|
|
|
|
|
|
|
|
|
|
|
| |
Viewing an ndarray as a np.recarray now automatically converts
the dtype to np.record.
This commit also fixes assignment to MaskedArray's dtype attribute,
fixes the repr of recarrays with non-structured dtype, and removes
recarray.view so that viewing a recarray as a non-structured dtype
no longer converts to ndarray type.
Fixes #3581
|
|
|
|
|
| |
Document the matmul function and add '@' to the operator
section of the reference manual.
|
|\
| |
| | |
New typemap for in-place arrays of arbitrary number of dimensions:
|