fix fails of tests for QR/LQ factorizations #1005
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix fails of tests for QR/LQ factorizations
Hello! This PR is willing to close issue #973.
Briefly speaking, there are some problems, recently appeared after Release 3.12. Functions
GELQS/GEQRS
were made DEPRECATED and have been replaced byGELS
in tests of QR/LQ factorizations. But,GELS
calls specific factorization depending on input size:QR
form >= n
andLQ
form < n
. Test does not take into account this knowledge and wrong factorization can be called for specific parametersm
andn
.GELS
are correct, test can be also failed for matrices near overflow/underflow. I believe, that it happens, sinceGELS
calls scaling routines inside, but previous versionGELQS/GEQRS
does not. Behavior is also changed in that way.It is important to point out, that test is failed on the next iteration of parameter
K
while data is improperly changed on the first iteration. That's why fails are reproduced only on fixed input file.Thinking of solution, I suggest to call the correct factorization on each iteration of inner loop for parameter
K
. It will solve any problems, related to occasionally changed data inside the test. Maybe this solution is not fully optimal, since it does not restrict any inputs intoGELS
, but it can be discussed.