BUG: linalg.pinv
behaves differently on NumPy version 1.x and 2.x
#28707
Labels
8000
linalg.pinv
behaves differently on NumPy version 1.x and 2.x
#28707
Uh oh!
There was an error while loading. Please reload this page.
Describe the issue:
linalg.pinv
behaves differently on NumPy version 1.26.4 and 2.1.3.I would like to know which version results in the correct one? Or are they all wrong?
Reproduce the code example:
Error message:
Python and NumPy Versions:
1.26.4
3.12.7 | packaged by Anaconda, Inc. | (main, Oct 4 2024, 13:27:36) [GCC 11.2.0]
2.1.3
3.10.0 (default, Mar 3 2022, 09:58:08) [GCC 7.5.0]
Runtime Environment:
[{'numpy_version': '1.26.4',
'python': '3.12.7 | packaged by Anaconda, Inc. | (main, Oct 4 2024, '
'13:27:36) [GCC 11.2.0]',
'uname': uname_result(system='Linux', node='xxx', release='5.15.167.4-microsoft-standard-WSL2', version='#1 SMP Tue Nov 5 00:21:55 UTC 2024', machine='x86_64')},
{'simd_extensions': {'baseline': ['SSE', 'SSE2', 'SSE3'],
'found': ['SSSE3',
'SSE41',
'POPCNT',
'SSE42',
'AVX',
'F16C',
'FMA3',
'AVX2'],
'not_found': ['AVX512F',
'AVX512CD',
'AVX512_KNL',
'AVX512_KNM',
'AVX512_SKX',
'AVX512_CLX',
'AVX512_CNL',
'AVX512_ICL']}},
{'filepath': '/home/jacin/anaconda3/lib/libmkl_rt.so.2',
'internal_api': 'mkl',
'num_threads': 9,
'prefix': 'libmkl_rt',
'threading_layer': 'intel',
'user_api': 'blas',
'version': '2023.1-Product'},
{'filepath': '/home/jacin/anaconda3/lib/libiomp5.so',
'internal_api': 'openmp',
'num_threads': 18,
'prefix': 'libiomp',
'user_api': 'openmp',
'version': None}]
[{'numpy_version': '2.1.3',
'python': '3.10.0 (default, Mar 3 2022, 09:58:08) [GCC 7.5.0]',
'uname': uname_result(system='Linux', node='xxx', release='5.15.167.4-microsoft-standard-WSL2', version='#1 SMP Tue Nov 5 00:21:55 UTC 2024', machine='x86_64')},
{'simd_extensions': {'baseline': ['SSE', 'SSE2', 'SSE3'],
'found': ['SSSE3',
'SSE41',
'POPCNT',
'SSE42',
'AVX',
'F16C',
'FMA3',
'AVX2'],
'not_found': ['AVX512F',
'AVX512CD',
'AVX512_KNL',
'AVX512_KNM',
'AVX512_SKX',
'AVX512_CLX',
'AVX512_CNL',
'AVX512_ICL']}}]
Context for the issue:
No response
The text was updated successfully, but these errors were encountered: