Repository navigation
Should LowRankOperator have a rank-truncation method?
#2285
drittelhacker
started this conversation in
Ideas
Replies: 2 comments 1 reply
|
Sounds fine to me, as long as the truncation does not happen upon instantiation. Due to immutability, the method would return a new operator. |
1 reply
|
Sounds good. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
The operator is constructed from the left and right VectorArrays L, R and a core NumPy array C. Consider that L, R have themselves been created as concatenations of VectorArrays and C is the block diagonal NumPy array. The result may very well have (numerical) rank-deficiency, even if the originals were fine. This situation could, e.g., happen for a linear combination of two LowRankOperators. In many situations, it would then be desirable to have a more compact representation of the LowRankOperator, that matches the (numerical) rank.
The easiest truncation procedure would
Obviously, a truncation tolerance on the SVD would then be required.
All reactions