Bounds for min-max heaps (Q1101212): Difference between revisions

From MaRDI portal
Importer (talk | contribs)
Created a new Item
 
ReferenceBot (talk | contribs)
Changed an Item
 
(6 intermediate revisions by 5 users not shown)
Property / author
 
Property / author: Alnoor Hasham / rank
Normal rank
 
Property / author
 
Property / author: Alnoor Hasham / rank
 
Normal rank
Property / Wikidata QID
 
Property / Wikidata QID: Q62037532 / rank
 
Normal rank
Property / describes a project that uses
 
Property / describes a project that uses: heapsort / rank
 
Normal rank
Property / MaRDI profile type
 
Property / MaRDI profile type: MaRDI publication profile / rank
 
Normal rank
Property / cites work
 
Property / cites work: Q4091421 / rank
 
Normal rank
Property / cites work
 
Property / cites work: Min-max heaps and generalized priority queues / rank
 
Normal rank
Property / cites work
 
Property / cites work: A Counting Approach to Lower Bounds for Selection Problems / rank
 
Normal rank
Property / cites work
 
Property / cites work: Q3945583 / rank
 
Normal rank
Property / cites work
 
Property / cites work: Q5585020 / rank
 
Normal rank
Property / cites work
 
Property / cites work: Q3026346 / rank
 
Normal rank
links / mardi / namelinks / mardi / name
 

Latest revision as of 15:53, 18 June 2024

scientific article
Language Label Description Also known as
English
Bounds for min-max heaps
scientific article

    Statements

    Bounds for min-max heaps (English)
    0 references
    0 references
    0 references
    0 references
    1987
    0 references
    Very recently a new data structure, called a min-max heap, was presented for implementing the double-ended priority queue. A min-max heap on n keys is constructed in O(n) time; the minimum and maximum keys are found in constant time, and the operations of deleting the minimum, deleting the maximum and inserting a new key into the heap are performed in O(log n) time. In addition, the data structure can be stored implicitly, i.e. in an array of n elements without using any additional pointers. In this paper, we present lower bound results on the number of comparisons required, in the worst case, for the operations i) to construct a min-max heap on a given set of keys; ii) to convert a min-max heap into a max-min heap; and iii) to merge two min-max heaps into one min-max heap. New upper bounds for the convert and merge operations are also derived. It is found that the main difference between traditional heaps and min-max heaps lies in the time needed to perform the merge operation. While traditional heaps can be merged efficiently, it is shown that min-max heaps are not sublinearly mergeable. Even the seemingly simple task of converting a min-max heap into a max-min heap cannot be performed in less than linear time.
    0 references
    double-ended priority queue
    0 references
    min-max heaps
    0 references

    Identifiers

    0 references
    0 references
    0 references
    0 references
    0 references
    0 references