| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
That is, eig(), eigh(), qr(), slogdet(), and svd(). For those functions that
return non-tuples with certain keyword arguments, the return type is
unchanged. This change should be completely backwards compatible.
The namedtuple attribute names come from the array API specification (see,
e.g.,
https://data-apis.org/array-api/latest/extensions/generated/signatures.linalg.eigh.html),
with the exception of eig() which is just the same as eigh(). The name of the
namedtuple object itself is not part of the specification or the public API.
I have not used a namedtuple for the tuple output for qr(mode='raw'), which
returns (h, tau).
This updates the docstrings to use the updated namedtuple return names, and
also the examples to use those names more consistently. This also updates the
tests to check each function for the namedtuple attributes at least once.
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
CI, TST: Run Cygwin CI with Netlib reference BLAS and re-enable linalg tests
|
| | |
|
|/
|
|
|
|
|
|
|
| |
Previously, numpy.linalg.norm would return values with the same floating-point
type as input arrays for most values of the ``ord`` parameter, but not all.
This PR fixes this so that the output dtype matches the input for all (valid) values
of ``ord``.
Co-authored-by: Kenichi Maehashi <webmaster@kenichimaehashi.com>
Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
`array.reshape(-1, size)` doesn't work with 0 in the dimensions.
The fix is to use explicit shape instead of `-1`. For "non-square"
tensors the `ValueError` would come from the reshape call, while previously
`LinAlgError` appeared from the solve call. To have the same error type
I added a check for squareness before the reshape.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This test is failing due to system oom during amd64 wheel tests
with ILP64 OpenBLAS. Should not be run on account of memory
restrictions, but evidently those are not reliably reported
to the docker container running the tests.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This is happening on too many build configurations, and it's not
completely clear if it's just an OpenBLAS version or also depends
on something else. Reported as happening mostly on macOS, but
also on Fedora.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* ENH: update numpy.linalg.multi_dot to accept an `out` argument
* TST ensure value returned by numpy.linalg.multi_dot matches out
* DOC add note about initial call to numpy.linalg.multi_dot
* DOC add release note for #15715
Co-authored-by: Matti Picus <matti.picus@gmail.com>
Co-authored-by: Sebastian Berg <sebastian@sipsolutions.net>
Co-authored-by: Eric Wieser <wieser.eric@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
in documentation (#15740)
* Clarify `fro` and `nuc` usage in linalg.norm documentation
(see #15533).
* Add improved error handling when getting Frobenius norm from
a vector (see #15533).
* Fix comment in linalg norm test.
Closes gh-15533.
|
|\
| |
| | |
BUG: Fix for SVD not always sorted with hermitian=True
|
| | |
|
|/ |
|
|
|
|
|
|
|
| |
Inheriting from object was necessary for Python 2 compatibility to use
new-style classes. In Python 3, this is unnecessary as there are no
old-style classes.
Dropping the object is more idiomatic Python.
|
|
|
|
|
| |
As numpy is Python 3 only, these import statements are now unnecessary
and don't alter runtime behavior.
|
|
|
|
|
| |
LAPACK lwork call does not require much memory, and can be used as a
smoketest to whether LAPACK really uses 64-bit integers.
|
|
|
|
| |
Fix wrong multiplier for /proc/meminfo, and do style cleanups.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
ENH: Add a hermitian argument to `pinv` and `svd`, matching `matrix_rank`
|
| |
| |
| |
| | |
Related to gh-9436
|
|\ \
| |/
|/| |
TST: coverage for _commonType()
|
| |
| |
| |
| |
| |
| |
| | |
* test uncovered path in
linalg.linalg._commonType() when an
unsupported inexact scalar array is
used
|
|/
|
|
|
|
|
|
|
|
|
|
| |
(#12448)
* Review F401,F841,F842 flake8 errors (unused variables, imports)
* Review comments
* More tests in test_installed_npymath_ini
* Review comments
|
|\
| |
| | |
TST: test dims match on lstsq()
|
| | |
|
|/
|
|
|
| |
* tensorinv() was previously completely
uncovered by unit tests
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
* replace most usage of SkipTest() with
pytest.skip()
* where possible, we avoid use of the standard
library SkipTest because unittest skipping
is routed through the pytest nose compatibility
layer in that scenario, which can prevent an easy
trace back to the test line where the skip
occurred
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When code does:
```python
def test():
def check(dtype):
# code
for dtype in [types]:
check(dtype)
```
replace it with:
```python
@pytest.mark.parametrize('dtype', [types])
def test(dtype):
# code
```
|
| |
|
|\
| |
| | |
BUG: Make matrix_power again work for object arrays.
|