Bug 623000
Summary: | Inconsistent C/Fortran API causing wrong behavior of scipy.linalg.lu_solve | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ling Li <liling> |
Component: | scipy | Assignee: | Jef Spaleta <jspaleta> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 15 | CC: | gwync, jspaleta, pav |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-08-07 19:33:10 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ling Li
2010-08-11 02:59:04 UTC
Fwiw, I can also reproduce the problem with Fedora 12. Yeah this feels like something I need to have a discussion with upstream about. In the meantime do you have a suggestion on how to provide a workaround for Fedora users? Can I force lu_solve to use the dgetrf call that is working correctly? -jef Oops, I said something wrong in this bug report (although the bug is real). dgetrf is used in lu_factor, and dgetrs is used in lu_solve (I said lu_solve calls dgetrf; that was wrong). Anyway, both lu_factor and lu_solve have this inconsistency behavior. It seems the Fortran lib (flapack) has the right behavior (matches the pydoc). I can think of two workarounds: a) (at package level) don't ship the clapack lib. thus scipy will be forced to only use the Fortran lib. OR b) (at user level) always use lu_factor and lu_solve in pairs. If one has to use only one of them, pass a copy of the numpy array with something like numpy.asarray(orig_array, order='F') a) is nicer since it doesn't have as severe a performance penalty as b), and it's transparent to the users. Thanks. This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping This also affects Fedora 14 and 15. Ling, Have you brought this to the attention of upstream scipy? I'm hesitant on specifically not shipping the clapack to paper over the problem. And I don't know enough about the details for to have a constructive discussion about what the fix needs to be in the codebase. -jef Fixed in upstream in release 0.10.0: http://projects.scipy.org/scipy/ticket/1458 This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |