-
Notifications
You must be signed in to change notification settings - Fork 536
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
Improvements to sort functions #1373
Conversation
This allows complex sorting based on a key, which can be the abs, real, imag etc of the value array. So the user can choose which metric they want to use.
* Sort now allows all dimensions * Sort if much faster by using batched mode. This takes up more memory though. * Enabled large tests for sort * Added tests for sorting on dim1 and dim2
This reverts commit 98e023d.
build arrayfire windows ci |
@pavanky updated sort_index code for CPU and CUDA |
build arrayfire tegrak1 ci |
build arrayfire tegrak1 ci |
build arrayfire linux-03 ci |
cuda::kernel::iota<uint>(pSeq, seqDims, tileDims); | ||
|
||
// Make pkey, pVal into a pair | ||
thrust::device_vector<IndexPair<Tk, Tv> > X(inDims.elements()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Allocate using arrayfire. This is going to be costly otherwise.
@shehzan10 Tests look fine. |
looks good 👍 |
build arrayfire ci |
1 similar comment
build arrayfire ci |
This pull request adds:
Fixes #291 #394