-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Global Coordinate Awareness in Tile
#82
Comments
Do you mean the block row & block col? For instance:
That would be fairly trivial to do, but I'm not sure how beneficial it is. Obviously the function that just got the tile A( i, j ) knows what i, j are. Or do you mean the actual row & col? For instance, for a matrix with fixed tile size mb x nb:
That would be easy for a fixed tile size, and rather hard & expensive for a variable tile size. We would basically have to iterate over the tileMb() and tileNb() functions to compute what the row & col are. Thinking more on this — we could do use an alternate representation using the first row / col of each tile, then tileMb = row[ i+1 ] - row[ i ], and tileNb = col[ i+1 ] - col[ i ]. That would have some other benefits like making |
This is essentially what TiledArray does (by introducing the concept of Expanding on this, you could also remove the need for user |
Describe the problem you are solving
For applications which manually specify the tiling of a matrix, it would be desirable for
Tile
to carry (or to be able to resolve) information pertaining to its locale relative to a global matrix. This is useful in matrix generation when the starting indices of a tile cannot be simply computed (i.e. non-uniform tiling)Describe your proposed solution
One potential solution would be to have
Tile
store it's global row/column starting indices relative to its owning matrix (and defaulting to 0)The text was updated successfully, but these errors were encountered: