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'm working on HyperSpectralImages, so I have many 3D arrays. And, for calculations, I need to get vector of values of some pixel.
For example:
imageView.GetSubView(Index3.Zero, new Index3(1, 1, imageView.Depth))
So, I assume, that extent with this size will return me the view like Z column, over values in [0,0,0],[0,0,1],[0,0,2] and etc. But, I getting the values in X row, not Z, like [0,0,0], [1,0,0], [2,0,0];
I assuming this as bug, rather than undocumented feature.
If it should work like this, @m4rs-mt can you provide some workaround for my case?
(because I'm using this for my diploma and it's critical for me)
The text was updated successfully, but these errors were encountered:
@Luminisc This is definitely an interesting application.
In fact, this is the intended behavior, since the concept of an ILGPU view is a raw view of the underlying memory. In your particular case, you want to access a non-contiguous memory region via a subview, which is (unfortunately) not possible with raw views. Instead, you must manually iterate over the affected elements.
We might want to integrate an additional concept of iterators to support convenient accesses in future versions :)
I'm working on HyperSpectralImages, so I have many 3D arrays. And, for calculations, I need to get vector of values of some pixel.
For example:
imageView.GetSubView(Index3.Zero, new Index3(1, 1, imageView.Depth))
So, I assume, that extent with this size will return me the view like Z column, over values in [0,0,0],[0,0,1],[0,0,2] and etc. But, I getting the values in X row, not Z, like [0,0,0], [1,0,0], [2,0,0];
I assuming this as bug, rather than undocumented feature.
If it should work like this, @m4rs-mt can you provide some workaround for my case?
(because I'm using this for my diploma and it's critical for me)
The text was updated successfully, but these errors were encountered: