Bug 1179055
Summary: | ATLAS xerbla can't be overidden. | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Orion Poplawski <orion> | ||||
Component: | numpy | Assignee: | Nikola Forró <nforro> | ||||
Status: | CLOSED ERRATA | QA Contact: | Mirek Długosz <mzalewsk> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 7.0 | CC: | akhaitov, bnater, c.david86, charlesr.harris, dakingun, dkutalek, extras-qa, fkluknav, gwync, jspaleta, Marcin.Dulak, mzalewsk, nforro, orion, ovasik, rdieter, tomspur, ttomecek | ||||
Target Milestone: | rc | Keywords: | Patch | ||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
URL: | https://github.com/numpy/numpy/issues/5362 | ||||||
Whiteboard: | |||||||
Fixed In Version: | numpy-1.7.1-13.el7 | Doc Type: | No Doc Update | ||||
Doc Text: |
undefined
|
Story Points: | --- | ||||
Clone Of: | 1172834 | Environment: | |||||
Last Closed: | 2018-04-10 08:34:47 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | 1172834 | ||||||
Bug Blocks: | 1465906 | ||||||
Attachments: |
|
Description
Orion Poplawski
2015-01-06 03:27:15 UTC
Hi Orion, using commit [1] for the numpy/core/blasdot/python_xerbla.c and numpy/core/setup.py, I get the following: python Python 2.7.5 (default, Feb 11 2014, 07:46:25) [GCC 4.8.2 20140120 (Red Hat 4.8.2-13)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import numpy as np >>> np.linalg.lstsq([[np.nan]]*2, [1]*2) (array([ nan]), array([ nan]), 1, array([ nan])) >>> Is this expected behaviour? Your expected behaviour is to raise an error, in this case the result is "(array([ nan]), array([ nan]), 1, array([ nan]))" containing nan. Is this still OK? [1] https://github.com/numpy/numpy/commit/f0b2dd7d5151878f2b4b3ea20ff551b27243f27d Anyway, as this component is not on ACL, rhel-7.1 is in its final phase before GA and this issue is not urgent, moving this to rhel-7.2. Hi Jan, That looks like you aren't linked with ATLAS, but using the numpy fallback. Earlier versions of Numpy will not automatically find ATLAS 3.10. I would have expected: >>> np.linalg.lstsq([[np.nan]]*2, [1]*2) Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib64/python2.7/site-packages/numpy/linalg/linalg.py", line 1867, in lstsq 0, work, lwork, iwork, 0) ValueError: On entry to DLASCL parameter number 4 had an illegal value >>> Thanks Charles, how can I set numpy to find ATLAS 3.10? Orion, right, exception should be raised. @Jan Chaloupka Use site.cfg with [DEFAULT] library_dirs = /usr/lib64 include_dirs = /usr/include # Atlas # ----- # Atlas is an open source optimized implementation of the BLAS and Lapack # routines. Numpy will try to build against Atlas by default when available in # the system library dirs. To build numpy against a custom installation of # Atlas you can add an explicit section such as the following. Here we assume # that Atlas was configured with ``prefix=/opt/atlas``. # [atlas] library_dirs = /usr/lib64/atlas include_dirs = /usr/include atlas_libs = tatlas lapack_libs = tatlas Created attachment 1237233 [details]
Override LAPACK XERBLA
Marcin, what info do you need? Whether there is any progress here The problem is not in numpy not being linked with ATLAS, but there is another upstream commit [1] that needs to be backported for the fix to work. The issue is resolved with the attached patch. [1] https://github.com/numpy/numpy/commit/374e0b4d2c6f44fdccccfefe0546b607e5291e64 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0659 |