ELF> @b@8 @X1X1 0=0= 0=  H=H= H= 888$$818181 Std818181 Ptd+++QtdRtd0=0= 0= GNU6 z+a`Nt@ |CEqXlv  , F"1"Pa] ] ] B *X__gmon_start___ITM_deregisterTMCloneTable_ITM_registerTMCloneTable__cxa_finalizelibcrypto.so.1.1libpython3.6m.so.1.0libpthread.so.0libc.so.6PyObject_RichCompareBoolPyExc_RuntimeErrorPyErr_SetStringPyExc_IndexErrorPyList_SetSlicePyExc_TypeErrorPyArg_UnpackTuplePyList_Append_Py_NoneStruct__stack_chk_failPyInit__heapqPyModule_Create2PyUnicode_DecodeUTF8PyModule_AddObject_edata__bss_start_endGLIBC_2.4GLIBC_2.2.5ii ui 0= )8= )@= @= [ X+[ [ C [ a+[ [ B [ +[ [ `B [ m+[ [ @ \ +\ *\ `@ \ +(\ )8\ @@ @\ +H\  X\  @ `\ +h\ *x\ @ \ +\ D \ [ ? ? ? ? ? ?  ?  ?  p? x? ? ? ?  ?  ? ? ? ? HHq4 HtH53 %3 hhhhhhhhqhah Q%U3 D%M3 D%E3 D%=3 D%53 D%-3 D%%3 D%3 D%3 D% 3 DIND$LQ0ImD$HIGM9gL3 H5I:D$IELP0I.D$t)M;gt|L=2 H5I?PlIvD$LV0D$L2 H5I;!=L m2 H5I9"IuD$LV0D$'Hmt$1}L 2 H5l1I9`LEH1AP0NH1 H5*H8HsD$ H<$HV0H<$D$ wH-1 H5H}O1L1 H5I84ML$D$H|$LAQ0H|$D$Hmt$1 H/1 H51H8LUH1AR0HD$ MND$LAQ0ImD$uMUD$LAR0D$U M_HI;o H=0 H5H?b& H0 H5H:G MFD$LAP0HmD$t) M9otKL=s0 H5DI? LMD$HAQ0D$L;0 H5tI;  ` L0 H5LI8# M\$D$LHL$AS0HL$D$) H/ H5H:n I,$u M|$LAW0HD$4MUD$LL\$AR0L\$D$H w/ H5H9H\/ H5H:MND$ H<$LAQ0H<$D$ mL!/ H5ZI81LIL$D$I9M&L9|MoI9kIH9M#LS1LIN4I$NL\$ILLT$I.H|$tpI,$Jx\M;ou@t+IGHt$HHL#HL&H HH9|1H([]A\A]A^A_L=) H5YI?։D$IFH|$LP0I,$H|$D$tHA) H5H:LFD$HLT$AP0D$LT$ff.UHSH5WH8dH%(HD$(1LL$LD$ VHD$ HPGHxHl$HH1HHHH H+u$Hl$HEHL$(dH3 %(HusH8[]H|$ Ht/LGLL$1I(IMH|$ tHEL' H521I;HsD$ HV0D$ d2fAWHAVH51AUATUSHHdH%(HD$81LL$0LD$(THD$(HPHxHHHt$0HHH1L|$(H\$IoH{HHH|$M_E1O$IXIM,L9~GO41LILIEI.ImxAM_HI;oHO$I4I$H>HI<$H9\$~oIwHt$L.Ll$IL.NHnHU0HD$f.Ht$8dH34%(HD$HH[]A\A]A^A_MoL9I,Lc1HIO4J HL$ILHEI.EHm}=M9oPbM_NIMH+II*HLMx2H ~% H5H9HD$ L5:% H5I>HD$AWHAVH5AUATUSHHdH%(HD$81LL$0LD$(+HD$(HP\HxHHHt$0HHH1L|$(H\$IoHHHH|$M_E1O$IXIHI L)L9<O4IE1LILImI.xUM_HI;ou/HO4I4MH>LI>H9\$IjH=# H5H?Ht$L.Ll$IL.`LNHAQ0HD$fDHt$8dH34%(HD$;HH[]A\A]A^A_MMD$LAQ0I.D$uMVD$LAR0D$pM_HI;oFHI L)O$I$HM,$H9\$MoL9M$LK1LIK,I$N4LL$HEHfHmHL$I,$M9ouVM_IML#IM&HHHuH-R" H5 H} HD$L=P" H5!I?XLUD$HHL$AR0I,$HL$D$YL5" H59 I>HD$;fDAWAVAUATUSH(HFvH^HHHV1HsHLdHI$H+LUI:M"LeH|$MLHHL$E1OD-IXILKL0M9'OILLHD$Ѕ%ILLHl$Յ ILLLl$AՅIILt$LLAօIt$LAօIt$LAօIt$LAօIt$LAօIt$LAօusIt$LAօudIt$LAօuUIIhH HHH[]A\A]A^A_LHl$ՅuIH H5kH:+1L%X H5I<$1H{1HHuHHLGLOLD$(LL$L9)HHt$ ff.@H\$LL9T$M_L9LIGHH9H4$HMH\$ILO4?InILN M!L9N4I$1LIL&I,$tPI.\HIEI;]LJNLI3MH2H9,$~jIkD$ value. Pop and return the current smallest value, and add the new item. This is more efficient than heappop() followed by heappush(), and can be more appropriate when using a fixed-size heap. Note that the value returned may be larger than item! That constrains reasonable uses of this routine unless written as part of a conditional replacement: if item > heap[0]: item = heapreplace(heap, item) Pop the smallest item off the heap, maintaining the heap invariant.heappushpop(heap, item) -> value. Push item on the heap, then pop and return the smallest item from the heap. The combined action runs more efficiently than heappush() followed by a separate call to heappop().heappush(heap, item) -> None. Push item onto heap, maintaining the heap invariant.Heap queue algorithm (a.k.a. priority queue). Heaps are arrays for which a[k] <= a[2*k+1] and a[k] <= a[2*k+2] for all k, counting elements from 0. For the sake of comparison, non-existing elements are considered to be infinite. The interesting property of a heap is that a[0] is always its smallest element. Usage: heap = [] # creates an empty heap heappush(heap, item) # pushes a new item on the heap item = heappop(heap) # pops the smallest item from the heap item = heap[0] # smallest item on the heap without popping it heapify(x) # transforms list into a heap, in-place, in linear time item = heapreplace(heap, item) # pops and returns smallest item, and adds # new item; the heap size is unchanged Our API differs from textbook heap algorithms as follows: - We use 0-based indexing. This makes the relationship between the index for a node and the indexes for its children slightly less obvious, but is more suitable since Python uses 0-based indexing. - Our heappop() method returns the smallest item, not the largest. These two make it possible to view the heap as a regular Python list without surprises: heap[0] is the smallest item, and heap.sort() maintains the heap invariant! Heap queues [explanation by François Pinard] Heaps are arrays for which a[k] <= a[2*k+1] and a[k] <= a[2*k+2] for all k, counting elements from 0. For the sake of comparison, non-existing elements are considered to be infinite. The interesting property of a heap is that a[0] is always its smallest element. The strange invariant above is meant to be an efficient memory representation for a tournament. The numbers below are `k', not a[k]: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 In the tree above, each cell `k' is topping `2*k+1' and `2*k+2'. In a usual binary tournament we see in sports, each cell is the winner over the two cells it tops, and we can trace the winner down the tree to see all opponents s/he had. However, in many computer applications of such tournaments, we do not need to trace the history of a winner. To be more memory efficient, when a winner is promoted, we try to replace it by something else at a lower level, and the rule becomes that a cell and the two cells it tops contain three different items, but the top cell "wins" over the two topped cells. If this heap invariant is protected at all time, index 0 is clearly the overall winner. The simplest algorithmic way to remove it and find the "next" winner is to move some loser (let's say cell 30 in the diagram above) into the 0 position, and then percolate this new 0 down the tree, exchanging values, until the invariant is re-established. This is clearly logarithmic on the total number of items in the tree. By iterating over all items, you get an O(n ln n) sort. A nice feature of this sort is that you can efficiently insert new items while the sort is going on, provided that the inserted items are not "better" than the last 0'th element you extracted. This is especially useful in simulation contexts, where the tree holds all incoming events, and the "win" condition means the smallest scheduled time. When an event schedule other events for execution, they are scheduled into the future, so they can easily go into the heap. So, a heap is a good structure for implementing schedulers (this is what I used for my MIDI sequencer :-). Various structures for implementing schedulers have been extensively studied, and heaps are good for this, as they are reasonably speedy, the speed is almost constant, and the worst case is not much different than the average case. However, there are other representations which are more efficient overall, yet the worst cases might be terrible. Heaps are also very useful in big disk sorts. You most probably all know that a big sort implies producing "runs" (which are pre-sorted sequences, which size is usually related to the amount of CPU memory), followed by a merging passes for these runs, which merging is often very cleverly organised[1]. It is very important that the initial sort produces the longest runs possible. Tournaments are a good way to that. If, using all the memory available to hold a tournament, you replace and percolate items that happen to fit the current run, you'll produce runs which are twice the size of the memory for random input, and much better for input fuzzily ordered. Moreover, if you output the 0'th item on disk and get an input which may not fit in the current tournament (because the value "wins" over the last output value), it cannot fit in the heap, so the size of the heap decreases. The freed memory could be cleverly reused immediately for progressively building a second heap, which grows at exactly the same rate the first heap is melting. When the first heap completely vanishes, you switch heaps and start a new run. Clever and quite effective! In a word, heaps are useful memory structures to know. I use them in a few applications, and I think it is good to keep a `heap' module around. :-) -------------------- [1] The disk balancing algorithms which are current, nowadays, are more annoying than clever, and this is a consequence of the seeking capabilities of the disks. On devices which cannot seek, like big tape drives, the story was quite different, and one had to be very clever to ensure (far in advance) that each tape movement will be the most effective possible (that is, will best participate at "progressing" the merge). Some tapes were even able to read backwards, and this was also used to avoid the rewinding time. Believe me, real good tape sorts were quite spectacular to watch! From all times, sorting has always been a Great Art! :-) X+C a+B +`B m+@ +*`@ +)@@ +  @ +*@ +D [ GA$3a1@ %+_heapq.cpython-36m-x86_64-linux-gnu.so-3.6.8-79.el8_10.alma.1.x86_64.debugU(v7zXZִF!t/]?Eh=ڊ2Na t|&4$\zRV'q>aO/0:Z* ڞC,MVȭ>#4i `̿h2$a!7+J!sbQgW`zW$a;yVm~mMZm)/B Q1['E1t߭v;<2a$eG\uiZhmuM:d޷/svd[g2yE&RAP%iA tT{|E0{g:kTBo.&&N95AqtaCZv#K-NБ6*=,q2X\y0خݲ'43ɯ Fu$5vJʣU\pLp^˫ۻ(5ae_klC 9M WȮ}{S+fgBǨsA˹3PG9!5~&M[}fULCňBjj Sy SqE]6cuM|^$nAdxNOc}l Rʧ\b2 _ؿ. ̾{"gYZ.shstrtab.note.gnu.build-id.gnu.hash.dynsym.dynstr.gnu.version.gnu.version_r.rela.dyn.rela.plt.init.plt.sec.text.fini.rodata.eh_frame_hdr.eh_frame.note.gnu.property.init_array.fini_array.data.rel.ro.dynamic.got.data.bss.gnu.build.attributes.gnu_debuglink.gnu_debugdata 88$o``4( 08o``,Eo0T^BP P h@ @ c` ` n  w h}++ 2(+(+++,,|8181 0= 0=8= 8=@= @=H= H=X? X?@ @ ] ]]`]$ ,]P|] a(