Bogosort

From HandWiki
Short description: Sorting algorithm
Bogosort
ClassSorting
Data structureArray
Worst-case performanceUnbounded (randomized version), [math]\displaystyle{ \Omicron(n \times n!) }[/math] (deterministic version)
Best-case performance[math]\displaystyle{ \Omega(n) }[/math][1]
Average performance[math]\displaystyle{ \Theta(n \times n!) }[/math][1]
Worst-case space complexity[math]\displaystyle{ \Omicron(1) }[/math]

In computer science, bogosort[1][2] (also known as permutation sort and stupid sort[3]) is a sorting algorithm based on the generate and test paradigm. The function successively generates permutations of its input until it finds one that is sorted. It is not considered useful for sorting, but may be used for educational purposes, to contrast it with more efficient algorithms.

Two versions of this algorithm exist: a deterministic version that enumerates all permutations until it hits a sorted one,[2][4] and a randomized version that randomly permutes its input. An analogy for the working of the latter version is to sort a deck of cards by throwing the deck into the air, picking the cards up at random, and repeating the process until the deck is sorted. In a worst-case scenario with this version, the random source is of low quality and happens to make the sorted permutation unboundedly unlikely to occur. The algorithm's name is a portmanteau of the words bogus and sort.[5]

Description of the algorithm

The following is a description of the randomized algorithm in pseudocode:

while not sorted(deck):
    shuffle(deck)

This is the code written in C.

#include<stdio.h>
#include<stdlib.h>
int main()
{
    int random=0,flag=0,temp=0,side=0;
    int input[]={68,14,78,98,67,89,45,90,87,78,65,74,-1};
    // Last with -1
    while (1==1)// Determine the size of group being sorted.
    {
        if (input[side]!=-1) side++;
        if (input[side]==-1) {side--;break;}
    }
    redo:// Shuffle data
    for (int i=0;i<side;i++)
    {
        random=rand()%(side+1);
        temp=input[random];
        input[random]=input[i];
        input[i]=temp;
    }

    for (int i=0;i<side-1;i++)
    {
        if (input[i]>input[i+1]) goto redo;
    }// Determine whether the data is sorted.
    for (int i=0;i<side;i++)
    printf("%d ",input[i]);
    printf("Bogosort works!!");
    return 0;
}

Here is the above pseudocode rewritten in Python 3:

from random import shuffle

def is_sorted(data) -> bool:
    """Determine whether the data is sorted."""
    return all(a <= b for a, b in zip(data, data[1:]))

def bogosort(data) -> list:
    """Shuffle data until sorted."""
    while not is_sorted(data):
        shuffle(data)
    return data

This code assumes that data is a simple, mutable, array-like data structure—like Python's built-in list—whose elements can be compared without issue.

Running time and termination

Experimental runtime of bogosort

If all elements to be sorted are distinct, the expected number of comparisons performed in the average case by randomized bogosort is asymptotically equivalent to (e − 1)n!, and the expected number of swaps in the average case equals (n − 1)n!.[1] The expected number of swaps grows faster than the expected number of comparisons, because if the elements are not in order, this will usually be discovered after only a few comparisons, no matter how many elements there are; but the work of shuffling the collection is proportional to its size. In the worst case, the number of comparisons and swaps are both unbounded, for the same reason that a tossed coin might turn up heads any number of times in a row.

The best case occurs if the list as given is already sorted; in this case the expected number of comparisons is n − 1, and no swaps at all are carried out.[1]

For any collection of fixed size, the expected running time of the algorithm is finite for much the same reason that the infinite monkey theorem holds: there is some probability of getting the right permutation, so given an unbounded number of tries it will almost surely eventually be chosen.

Related algorithms

Gorosort
A sorting algorithm introduced in the 2011 Google Code Jam.[6] As long as the list is not in order, a subset of all elements is randomly permuted. If this subset is optimally chosen each time this is performed, the expected value of the total number of times this operation needs to be done is equal to the number of misplaced elements.
Bogobogosort
An algorithm that recursively calls itself with smaller and smaller copies of the beginning of the list to see if they are sorted. The base case is a single element, which is always sorted. For other cases, it compares the last element to the maximum element from the previous elements in the list. If the last element is greater or equal, it checks if the order of the copy matches the previous version, and if so returns. Otherwise, it reshuffles the current copy of the list and restarts its recursive check.[7]
Bozosort
Another sorting algorithm based on random numbers. If the list is not in order, it picks two items at random and swaps them, then checks to see if the list is sorted. The running time analysis of a bozosort is more difficult, but some estimates are found in H. Gruber's analysis of "perversely awful" randomized sorting algorithms.[1] O(n!) is found to be the expected average case.
Worstsort
A pessimal[lower-alpha 1] sorting algorithm that is guaranteed to complete in finite time; however, its efficiency can be arbitrarily bad, depending on its configuration. The worstsort algorithm is based on a bad sorting algorithm, badsort. The badsort algorithm accepts two parameters: L, which is the list to be sorted, and k, which is a recursion depth. At recursion level k = 0, badsort merely uses a common sorting algorithm, such as bubblesort, to sort its inputs and return the sorted list. That is to say, badsort(L, 0) = bubblesort(L). Therefore, badsort's time complexity is O(n2) if k = 0. However, for any k > 0, badsort(L, k) first generates P, the list of all permutations of L. Then, badsort calculates badsort(P, k − 1), and returns the first element of the sorted P. To make worstsort truly pessimal, k may be assigned to the value of a computable increasing function such as [math]\displaystyle{ f\colon\N \to \N }[/math] (e.g. f(n) = A(n, n), where A is Ackermann's function). Therefore, to sort a list arbitrarily badly, one would execute worstsort(L, f) = badsort(L, f(length(L))), where length(L) is the number of elements in L. The resulting algorithm has complexity [math]\displaystyle{ \Omega\left(\left(n!^{(f(n))}\right)^2\right) }[/math], where [math]\displaystyle{ n!^{(m)} = (\dotso((n!)!)!\dotso)! }[/math] = factorial of n iterated m times. This algorithm can be made as inefficient as one wishes by picking a fast enough growing function f.[8]
Slowsort
A different humorous sorting algorithm that employs a misguided divide-and-conquer strategy to achieve massive complexity.
Quantum bogosort
A hypothetical sorting algorithm based on bogosort, created as an in-joke among computer scientists. The algorithm generates a random permutation of its input using a quantum source of entropy, checks if the list is sorted, and, if it is not, destroys the universe. Assuming that the many-worlds interpretation holds, the use of this algorithm will result in at least one surviving universe where the input was successfully sorted in O(n) time.[9]
Miracle sort
A sorting algorithm that checks if the array is sorted until a miracle occurs. It continually checks the array until it is sorted, never changing the order of the array.[10] Because the order is never altered, the algorithm has a hypothetical time complexity of O(), but it can still sort through events such as miracles or single-event upsets. Particular care must be taken in the implementation of this algorithm as optimizing compilers may simply transform it into a while(true) loop. However, the best case is O(n), which happens on a sorted list. Since it only makes comparisons, it is both strictly in-place and stable.

See also

Notes

  1. The opposite of "optimal"

References

  1. 1.0 1.1 1.2 1.3 1.4 1.5 Gruber, H.; Holzer, M.; Ruepp, O., "Sorting the slow way: an analysis of perversely awful randomized sorting algorithms", 4th International Conference on Fun with Algorithms, Castiglioncello, Italy, 2007, Lecture Notes in Computer Science, 4475, Springer-Verlag, pp. 183–197, doi:10.1007/978-3-540-72914-3_17, http://www.hermann-gruber.com/pdf/fun07-final.pdf .
  2. 2.0 2.1 Kiselyov, Oleg; Shan, Chung-chieh; Friedman, Daniel P.; Sabry, Amr (2005), "Backtracking, interleaving, and terminating monad transformers: (functional pearl)", Proceedings of the Tenth ACM SIGPLAN International Conference on Functional Programming (ICFP '05), SIGPLAN Notices, pp. 192–203, doi:10.1145/1086365.1086390, http://www.dicta.org.uk/programming/LogicT.pdf, retrieved 22 June 2011 
  3. E. S. Raymond. "bogo-sort". The New Hacker’s Dictionary. MIT Press, 1996.
  4. Naish, Lee (1986), "Negation and quantifiers in NU-Prolog", Proceedings of the Third International Conference on Logic Programming, Lecture Notes in Computer Science, 225, Springer-Verlag, pp. 624–634, doi:10.1007/3-540-16492-8_111 .
  5. "bogosort". https://xlinux.nist.gov/dads/HTML/bogosort.html. 
  6. Google Code Jam 2011, Qualification Rounds, Problem D
  7. Bogobogosort
  8. Lerma, Miguel A. (2014). "How inefficient can a sort algorithm be?". arXiv:1406.1077 [cs.DS].
  9. The Other Tree (23 October 2009). "Quantum Bogosort". mathNEWS 111 (3): 13. https://mathnews.uwaterloo.ca/wp-content/uploads/2014/08/v111i3-compressed.pdf#page=13. Retrieved 20 March 2022. 
  10. "Miracle Sort". The Computer Science Handbook. https://www.thecshandbook.com/Miracle_Sort. 

External links