-
Notifications
You must be signed in to change notification settings - Fork 271
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
Parallel Brick Sort #129
Comments
This page says that it was originally developed for parallel threads/processors. So, IMO, we should add its parallel implementation with odd indices being sorted on one thread and even indices on another thread. Though before, that a nice API design should be proposed which can be applicable to other parallel sorting algorithms like parallel merge sort. We can develop a uniform API for all parallel sorting algorithms. |
See our issue policy at https://github.com/codezonediitj/pydatastructs/wiki/Issue-Policy |
How to contribute |
See, https://github.com/codezonediitj/pydatastructs/wiki/Plan-of-Action-for-the-Projects |
Hi, I would like to work on this. Is anyone else already working on it? I have got an idea to go about it. @czgdp1807 can I start working on this? Any updates on this? |
@MukundVaradarajan Please start by proposing some API designs for brick sort. We need only it's parallel version implemented. IMO, the API for this can along the lines of parallel merge sort already there in the
|
Parallel implementation of this algorithm is yet to be added. |
we can try one thread for odd and one thread for even part of the array. |
Some idea is given in #129 (comment) |
I can start with a draft PR if its ok? |
Sure |
Description of the problem
I would like to propose an odd-even transposition sort or brick sort. Odd-Even Transposition Sort is based on the Bubble Sort technique. It compares two adjacent numbers and switches them if the first number is greater than the second number to get an ascending order list. The opposite case applies to a descending order series.
Please assign me this issue.
The text was updated successfully, but these errors were encountered: