You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe block-wise linear algebra operations such as dot default to the implementation for AbstractArray instead of doing the operation block by block and then adding the results. This is highly inefficient since searching for the block index every single time. I would understand this behavior for mixed arrays, but I think there should be specialized implementations for operations between block-arrays. Also, this limits BlockArray to contain sub-arrays that are indexable. This is quite a heavy restriction, since there might be objects implementing the whole LinearAlgebra API without being indexable (for instance, parallel arrays).
In summary, I would like someone to explain the though process behind why these choices have been made instead of leveraging the block-wise structure of BlockArray.
Thanks,
Jordi
The text was updated successfully, but these errors were encountered:
JordiManyer
changed the title
Behaviour of block indexing
Behaviour of block linear algebra
Apr 12, 2024
Hi all,
I believe block-wise linear algebra operations such as
dot
default to the implementation forAbstractArray
instead of doing the operation block by block and then adding the results. This is highly inefficient since searching for the block index every single time. I would understand this behavior for mixed arrays, but I think there should be specialized implementations for operations between block-arrays. Also, this limitsBlockArray
to contain sub-arrays that are indexable. This is quite a heavy restriction, since there might be objects implementing the wholeLinearAlgebra
API without being indexable (for instance, parallel arrays).In summary, I would like someone to explain the though process behind why these choices have been made instead of leveraging the block-wise structure of
BlockArray
.Thanks,
Jordi
The text was updated successfully, but these errors were encountered: