Sparse matrix error: repro case for not using numerical pivoting #852
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Tony Xiang <tony.xiang@alliander.com>
Signed-off-by: Tony Xiang <tony.xiang@alliander.com>
Signed-off-by: Tony Xiang <tony.xiang@alliander.com>
mgovers
reviewed
Dec 6, 2024
|
@mgovers please go ahead to modify the files, merge the PR and create the issue. |
|
Issue created in #853 |
Signed-off-by: Martijn Govers <Martijn.Govers@Alliander.com>
mgovers
approved these changes
Dec 6, 2024
mgovers
changed the title
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The in-house LU Sparse solver does not do numerical pivoting for performance optimization. It assumes that the matrix is always diagonal major.
However, this assumption does not hold for certain real-world state estimation cases. This results in Sparse Matrix Error where the system is actually perfectly observable and solvable.
This PR reproduces the error using two cases.