5 \chapter{Approaching Optimality}
9 Recently, Chazelle \cite{chazelle:ackermann} and Pettie \cite{pettie:ackermann}
10 have presented algorithms for the MST with worst-case time complexity
11 $\O(m\timesalpha(m,n))$ on the Pointer machine. We will devote this chapter to their results
12 and especially to another algorithm by Pettie and Ramachandran \cite{pettie:optimal},
13 which is provably optimal.
15 At the very heart of all these algorithms lies the \df{soft heap} discovered by
16 Chazelle \cite{chazelle:softheap}. It is a~meldable priority queue, roughly
17 similar to the Vuillemin's binomial heaps \cite{vuillemin:binheap} or Fredman's
18 and Tarjan's Fibonacci heaps \cite{ft:fibonacci}. The soft heaps run faster at
19 the expense of \df{corrupting} a~fraction of the inserted elements by raising
20 their values (the values are however never lowered). This allows for
21 an~trade-off between accuracy and speed controlled by a~parameter~$\varepsilon$.
22 The heap operations take $\O(\log(1/\varepsilon))$ amortized time and at every
23 moment at most~$\varepsilon n$ elements of the~$n$ elements inserted can be
26 \defnn{Soft heap operations}%
27 The soft heap contains a~set of distinct items from a~totally ordered universe and it
28 supports the following operations:
30 \:$\<Create>(\varepsilon)$ --- create an~empty soft heap with the given accuracy parameter~$\varepsilon$,
31 \:$\<Insert>(H,x)$ --- insert a~new item~$x$ to the heap~$H$,
32 \:$\<Meld>(P,Q)$ --- merge two heaps into one, more precisely move all items of a~heap~$Q$
33 to the heap~$P$, destroying~$Q$ in the process (both heaps must have the same~$\varepsilon$),
34 \:$\<DeleteMin>(H)$ --- delete the minimum item of the heap~$H$ and return its value
35 (optionally signalling that the value has been corrupted).
36 \:$\<Explode>(H)$ --- destroy the heap and return a~list of all items contained in it
37 (again optionally marking those corrupted).
40 \examplen{Linear-time selection}
41 We can use soft heaps to select the median (or generally the $k$-th smallest element)
42 of a~sequence. We insert all $n$~elements to a~soft heap with error rate $\varepsilon=1/3$.
43 Then we delete the minimum about $n/3$ times and we remember the current (possibly corrupted)
44 value~$x$ of the last element deleted. This~$x$ is greater or equal than the current
45 values of the previously deleted elements and thus also than their correct values.
46 On the other hand, the current values of the $2n/3$ elements remaining in the heap
47 are greater than~$x$ and at most $n/3$ of them are corrupted. Therefore at least $n/3$
48 elements are greater than~$x$ and at least $n/3$ ones are smaller. Depending on the value
49 of~$k$, we can always throw away one of these parts and recurse on the rest (similarly to
50 the Hoare's Quickselect algorithm \cite{hoare:qselect}). The total time complexity will
51 be $\O(n+(2/3)\cdot n+(2/3)^2\cdot n+\ldots) = \O(n)$. We have obtained a~nice alternative to the standard
52 linear-time selection algorithm by Blum \cite{blum:selection}. The same trick can be used
53 to select a~good pivot in Quicksort \cite{hoare:qsort}, leading to time complexity $\O(n\log n)$
57 The soft heap is built from \df{soft queues} (we will usually omit the adjective soft
58 in the rest of this section). Each queue has a~shape of a~binary tree.\foot{%
59 Actually, Chazelle defines the queues as binomial trees, but he transforms them in ways that are
60 somewhat counter-intuitive, albeit well-defined. We prefer describing the queues as binary
61 trees with a~special distribution of values. In fact, the original C~code in the Chazelle's
62 paper \cite{chazelle:softheap} uses this representation internally.}
63 Each vertex~$v$ of the tree remembers a~doubly-linked list of items. The
64 item list in every left son will be used only temporarily and it will be kept
65 empty between operations. Only right sons and the root have their lists
66 permanently occupied. The left sons will be called \df{white}, the right ones
67 \df{black.} (See the picture.)
69 The first value in every list is called the \df{controlling key} of the vertex,
70 denoted by $\<ckey>(v)$. If the list is empty, we keep the most recently used
71 value or we set $\<ckey>(v)=+\infty$. The \<ckey> obey the standard \df{heap order}
72 --- a~\<ckey> of a~parent is always smaller than the \<ckey>'s of its sons.
74 Each vertex is also assigned its \df{rank,} which is a~non-negative integer.
75 The ranks of leaves are always zero, the rank of every internal vertex can be
76 arbitrary, but it must be strictly greater than the ranks of its sons. We
77 define the rank of the whole queue to be equal to the rank of its root vertex and
78 similarly for its \<ckey>.
80 A~queue is called \df{complete} if every two vertices joined by an~edge have rank
81 difference exactly one. In other words, it is a~complete binary tree and the
82 ranks correspond to vertex heights.
84 \figure{softheap1.eps}{\epsfxsize}{\multicap{A~complete and a~partial soft queue tree\\
85 (black vertices contain items, numbers indicate ranks)}}
88 The complete queue of rank~$k$ contains exactly~$2^{k+1}-1$ vertices, $2^k$~of which are
89 black (by induction). Any other queue can be trivially embedded to the complete queue of the same
90 rank, which we will call the \df{master tree} of the queue. This embedding preserves vertex
91 ranks, colors and the ancestor relation.
93 The queues have a~nice recursive structure. We can construct a~queue of rank~$k$ by \df{joining}
94 two queues of rank~$k-1$ under a~new root. The root will inherit the item list of one
95 of the original roots and also its \<ckey>. To preserve the heap order, we will choose
96 the one whose \<ckey> is smaller.
98 Sometimes, we will also need to split a~queue to smaller queues. We will call this operation
99 \df{dismantling} the queue and it will happen only in cases when the item list in the root
100 is empty. It suffices to remove the leftmost (all white) path going from the root. From
101 a~queue of rank~$k$, we get queues of ranks $0,1,\ldots,k-1$, some of which may be missing
102 if the original queue was not complete.
104 \figure{softheap2.eps}{\epsfxsize}{Joining and dismantling of soft queues}
106 We will now define the real soft heap and the operations on it.
108 \defn A~\df{soft heap} consists of:
110 \:a~doubly linked list of soft queues of distinct ranks (in increasing order of ranks),
111 we will call the first queue the \df{head} of the list, the last queue will be its \df{tail};
112 \:\df{suffix minima:} each queue contains a~pointer to the queue with minimum \<ckey>
113 of those following it in the list;
114 \:a~global parameter~$r$: an~even integer to be set depending on~$\varepsilon$.
117 \>We will define the \df{rank} of a~heap as the highest of the ranks of its queues
118 (that is, the rank of the heap's tail).
120 The heap always keeps the \df{Rank invariant:} When a~root of any tree has rank~$k$,
121 its leftmost path contains at least~$k/2$ vertices.
123 \paran{Operations on soft heaps}
125 \em{Melding} of two soft heaps involves merging of their lists of queues. We disassemble
126 the heap of the smaller rank and we insert its queues to the other heap.
127 If two queues of the same rank~$k$ appear in both lists, we \em{join} them to
128 a~single queue of rank~$k+1$ as already described and we propagate the new queue as
129 a~\df{carry} to the next iteration, similarly to addition of binary numbers.
130 Finally we have to update the suffix minima by walking the new list backwards
131 from the last inserted item.
133 \em{Creation} of a~new soft heap is trivial, \em{insertion} is handled by creating
134 a~single-element heap and melding it to the destination heap.
136 \algn{Creating a~new soft heap}
138 \algin The~parameter~$\varepsilon$ (the accuracy of the heap).
139 \:Allocate memory for a~new heap structure~$H$.
140 \:Initialize the list of queues in~$H$ to an~empty list.
141 \:Set the parameter~$r$ to~$2\lceil\log(1/\varepsilon)\rceil+2$ (to be justified later).
142 \algout A~newly minted soft heap~$H$.
145 \algn{Melding of two soft heaps}
147 \algin Two soft heaps~$P$ and~$Q$.
148 \:If $\<rank>(P) < \<rank>(Q)$, exchange the item lists of~$P$ and~$Q$.
150 \brk\cmt{Whenever we run into an~end of a~list in this procedure, we assume that
151 there is an~empty queue of infinite rank there.}
152 \:While $Q$ still has some queues:
154 \::If $\<rank>(p) < \<rank>(q)$, then $p\=$ the successor of~$p$,
155 \::else if $\<rank>(p) > \<rank>(q)$, remove~$q$ from~$Q$ and insert it to~$P$ before~$p$,
156 \::otherwise (the ranks are equal, we need to propagate the carry):
158 \:::Remove~$p$ from~$P$ and set $p\=$ the original successor of~$p$.
159 \:::While $\<rank>(q)=\<rank>(\<carry>)$:
160 \::::Remove~$q$ from~$Q$.
161 \::::$\<carry>\=\<join>(q, \<carry>)$.
162 \::::$q\=\<head>(Q)$.
163 \:::Insert~\<carry> before~$q$.
164 \:Update the suffix minima: Walk with~$p$ backwards to the head of~$P$:
165 \::$p'\=\<suffix\_min>$ of the successor of~$p$.
166 \::If $\<ckey>(p) < \<ckey>(p')$, set $\<suffix\_min>(p)\=p$.
167 \::Otherwise set $\<suffix\_min>(p)\=p'$.
168 \:Destroy the heap~$Q$.
169 \algout The merged heap~$P$.
172 \algn{Insertion of an~element to a~soft heap}
174 \algin A~heap~$H$ and a~new element~$x$.
175 \:Create a~new heap~$H'$ of the same parameters as~$H$. Let~$H'$ contain a~sole queue of rank~0,
176 whose only vertex has the element~$x$ in its item list.
178 \algout An~updated heap~$H$.
182 So far, the mechanics of the soft heaps were almost identical to the binomial heaps
183 and the reader could rightfully yawn. The things are going to get interesting
184 now as we approach the parts where corruption of items takes place.
186 If all item lists contain at most one item equal to the \<ckey> of the particular
187 vertex, no information is lost and the heap order guarantees that the minimum item
188 of every queue stays in its root. We can however allow longer lists and let the items
189 stored in a~single list travel together between the vertices of the tree, still
190 represented by a~common \<ckey>. This data-structural analogue of car pooling will
191 allow the items to travel at a~faster rate, but as only a~single item can be equal
192 to the \<ckey>, all other items will be inevitably corrupted.
194 We of course have to be careful about the size of the lists, because we must avoid corrupting
195 too many items. We will control the growth according to the vertex ranks. Vertices
196 with rank at most~$r$ will always contain just a~single item. Above this level,
197 the higher is the rank, the longer list will be allowed.
200 \em{Deletion of minimum} will be based on this principle. The minimum is easy to locate
201 --- we follow the \<suffix\_min> of the head of the heap to the queue with the minimum
202 \<ckey>. There we look inside the item list of the root of the queue. We remove the \em{last}
203 item from the list (we do not want the \<ckey> to change) and we return it as the minimum.
204 (It is not necessarily the real minimum of all items, but always the minimum of their
205 possibly corrupted values.)
207 If the list becomes empty, we \em{refill} it with items from the lower levels of the
208 same queue. This process can be best described recursively: We ask the left son to refill itself
209 (remember that the left son is always white, so there are currently no items there). If the new
210 \<ckey> of the left son is smaller than of the right son, we immediately move the left
211 son's list to its parent. Otherwise, we exchange the sons and move the list from the
212 new left son to the parent. This way we obey the heap order and at the same time we keep
213 the white left son free of items.
215 Ocassionally, we repeat this process once again and we concatenate the resulting lists
216 (we append the latter list to the former, using the smaller of the two \<ckey>'s). This
217 makes the lists grow longer and we want to do that roughly on every other level of the
218 tree. The exact condition will be that either the rank of the current vertex is odd,
219 or the difference in ranks between this vertex and its right son is at least two.
221 If refilling of the left son fails because there are no more items in that subtree
222 (we report this by setting its \<ckey> to $+\infty$), the current vertex is no longer
223 needed --- the items would just pass through it unmodified. We therefore want to
224 remove it. Instead of deleting it directly, we rather make it point to its former
225 grandsons and we remove the (now orhpaned) original son. This helps us to ensure
226 that both sons always keep the same rank, which will be useful for the analysis.
228 When all refilling is done, we update the suffix minima by walking from the current
229 queue to the head of the heap exactly as we did in the \<Meld> procedure.
231 Our only remaining worry is that the Rank invariant can be broken after the
232 refilling. When the leftmost path of the tree becomes too short, we just
233 \em{dismantle} the tree as already described and we meld the new trees back to
234 the heap. This is easier to handle when the item list at the root vertex is
235 empty. We will therefore move this check before the refilling of the root list.
236 It will turn out that we have enough time to always walk the leftmost path
237 completely, so no explicit counters are needed.
239 Let us translate these ideas to real (pseudo)code:
241 \algn{Deleting the minimum item from a~soft heap}
243 \algin A~soft heap~$H$.
244 \:Use \<suffix\_min> of the head queue of~$H$ to locate the queue~$q$ with the smallest \<ckey>.
245 \:Remove the final element~$x$ of the item list in the root of~$q$.
246 \:If the item list is empty:
247 \::Count the vertices on the leftmost path of~$q$.
248 \::If there are less than $\<rank>(q)$ of them:
249 \:::Remove~$q$ from the list of queues.
250 \:::Recalculate the suffix minima as in the \<Meld> procedure.
251 \:::Dismantle~$q$ and create a~heap~$H'$ holding the resulting trees.
252 \:::Meld them back: $\<Meld>(H,H')$.
254 \:::Call \<Refill> on the root of~$q$.
255 \:::If $\<ckey>(q)=+\infty$ (no items left), remove the tree~$q$ from~$H$.
256 \:::Recalculate the suffix minima.
257 \algout The deleted minimum item~$x$ (possibly corrupted).
260 \algn{Refilling the item list of a~vertex}
262 \algin A~soft queue and its vertex~$v$ with an~empty item list.
263 \:Handle trivial cases: If~$v$ has no children or both have $\<ckey>=+\infty$,
264 set $\<ckey>(v)$ to~$+\infty$ and return.
265 \:Let \<left> and~\<right> denote the respective sons of~$v$.
266 \:Recurse: call $\<Refill>(\<left>)$.
267 \:If $\<ckey>(\<left>) > \<ckey>(\<right>)$, swap the sons.
268 \:Move the item list from \<left> to~$v$ (implying $\<ckey>(v)=\<ckey>(\<left>)$).
269 \:If $\<rank>(v) > r$ and either $\<rank>(v)$ is odd or $\<rank>(v) > \<rank>(\<right>)+1$, recurse once more:
270 \::Repeat steps 3--4.
271 \::Append the item list from \<left> to the item list at~$v$.
272 \:Clean up. If $\<ckey>(\<right>) = +\infty$:
273 \::If $\<ckey>(\<left>) = +\infty$, unlink and discard both sons.
274 \::Otherwise relink the sons of \<left> to~$v$ and discard \<left>.
275 \algout A~modified soft queue.
279 \<Explode> is trivial once we know how to recognize the corrupted items. It simply examines
280 all queues in the heap, walks the trees and the item lists of all vertices. It records
281 all items seen, the corrupted ones are those that different from their \<ckey>.
283 \paran{Analysis of accuracy}
284 The description of the operations is now complete, so let us analyse their behavior
285 and verify that we have delivered what we promised --- first the accuracy of
286 the structure, then the time complexity of operations. In the whole analysis,
287 we will denote the total number of elements inserted during the history of the
288 structure by~$n$. We will also frequently take advantage of knowing that the
289 threshold~$r$ is even.
291 We start by bounding the sizes of the item lists.
294 For every vertex~$v$ of a~soft queue, the size $\ell(v)$ of its item list
296 $$\ell(v) \le \max(1, 2^{\lceil \<rank>(v)/2 \rceil - r/2}).$$
299 Initially, all item lists contain at most one item, so the ineqality trivially
300 holds. Let us continue by induction. Melds can affect it only in the favorable
301 direction (they ocassionally move an~item list to a~vertex of a~higher rank)
302 and so do deletes (they only remove items from lists). The only potentially
303 dangerous place is the \<Refill> procedure.
305 Refilling sometimes just moves items upwards, which is safe, and sometimes it
306 joins two lists into one, which generally is not. When $\<rank>(v) \le r$,
307 no joining takes place and~$\ell(v)$ is still~1. Otherwise we join when either
308 $\<rank>(v)$ is odd or $\<rank>(w) < \<rank>(v)-1$ for any son~$w$ of~$v$ (remember
309 that both sons have the same rank). In both cases, $\lceil\<rank>(w)/2\rceil \le
310 \lceil\<rank>(v)/2\rceil - 1$. By the induction hypothesis, the size of each
311 of the two joined lists is at most $2^{\max(1,\lceil\<rank>(v)/2\rceil - 1 - r/2)}$,
312 so the new list has at most $2^{\lceil\<rank>(v)/2\rceil - r/2}$ items. (The maximum
313 has disappeared since $\<rank>(v)>r$ and therefore the desired bound is at least~2.)
316 We will now sum the sizes of the lists over all vertices containing corrupted items.
318 \lemma\id{shcorrlemma}%
319 At any given time, the heap contains at most~$n/2^{r-2}$ corrupted items.
322 We first prove an~auxiliary claim: The master trees of all queues contain at most~$n$
323 black vertices. This follows by induction: If no deletions have taken place,
324 there are exactly~$n$ black vertices, because insertion adds one black vertex and
325 melding preserves their number. A~deletion affects the master trees only when
326 dismantling takes place and then it only removes a~black vertex.
328 An~obvious upper bound on the number of corrupted items is the total size of item
329 lists in all vertices of rank greater than~$r$. We already know from the previous
330 lemma that the list sizes are limited by a~function of the ranks. A~complete tree
331 is obviously the worst case, so we will prove that this lemma holds for the master
332 tree of every queue in the heap. The actual trees can be much sparser, but the
333 above claim guarantees that the total size of the master trees is bounded by the
334 number of insertions properly.
336 So let us consider a~complete tree of~rank~$k$. It has exactly $2^{k-i}$ vertices
337 of rank~$i$ and each such vertex contains a~list of at most~$2^{\lceil i/2\rceil - r/2}$
338 items by the previous lemma. Summing over all ranks greater than~$r$, we get that
339 the total number of corrupted items in this tree is at most:
341 \sum_{i=r+1}^k 2^{k-i}\cdot 2^{\lceil i/2\rceil - r/2}
342 = 2^{k-r/2} \cdot \sum_{i=r+1}^k 2^{\lceil i/2\rceil - i}
343 \le 2^{k-r/2+1/2} \cdot \sum_{i=r+1}^k 2^{-i/2}
344 \le 2^{k-r} \cdot \sum_{i=0}^\infty 2^{-i/2}.
346 The sum of a~geometric series with quotient $2^{-1/2}$ is less than four, so the
347 last expression is less than $2^{k-r+2}$. Since the tree contains $n_k=2^k$ black vertices,
348 this makes less than $n_k/2^{r-2}$ corrupted items as we asserted.
351 \paran{Analysis of time complexity}
352 Now we will examine the amortized time complexity of the individual operations.
353 We will show that if we charge $\O(r)$ time against every element inserted, it is enough
354 to cover the cost of all other operations.
356 All heap operations use only pointer operations, so it will be easy to derive the time
357 bound in the Pointer machine model. The notable exception is however that the procedures
358 often refer to the ranks, which are integers on the order of $\log n$, so they cannot
359 fit in a~single memory cell. For the time being, we will assume that the ranks can
360 be manipulated in constant time, postponing the proof for later.
362 We take a~look at the melds first.
365 The amortized cost of a~meld is $\O(1)$, except for melds induced by dismantling
366 which take $\O(\<rank>(q))$, where $q$~is the queue to be dismantled.
369 The real cost of a~meld of heaps $P$ and~$Q$ is linear in the smaller of
370 their ranks, plus the time spent on carry propagation. The latter is easy to
371 dispose of: Every time there is a~carry, the total number of trees in all
372 heaps decreases by one. So it suffices to charge $\O(1)$ against creation of
373 a~tree. An~insert creates one tree, dismantling creates at most $\<rank>(q)$
374 trees, and all other operations alter only the internal structure of trees.
376 As for the $\O(\min(\<rank>(P),\<rank>(Q)))$ part, let us assume for a~while that
377 no dismantling ever takes place and consider the \df{meld forest.} It is a~forest
378 whose leaves correspond to the $n$~single-element heaps constructed by \<Insert>
379 and each internal vertex represents a~heap arisen from melding its sons. The left
380 son will be the one with the greater or equal rank. We therefore want to bound
381 the sum of ranks of all right sons.
383 For every right son, we will distribute the change for its rank~$k$ among all leaves
384 in its subtree. There are at least $2^k$ such leaves. No leaf ever receives the same
385 rank twice, because the ranks of right sons on every path from the root of the
386 tree to a~leaf are strictly decreasing. (This holds because melding of two heaps
387 always produces a~heap of a~strictly greater rank.) Hence at most~$n/2^k$
388 right sons have rank~$k$ and the total time charged against the leaves is bounded by:
390 \sum_{k=0}^{\rm max. rank}k\cdot {n\over 2^k} \le n\cdot\sum_{k=0}^\infty {k\over 2^k} = 2n.
393 Let us return dismantling to the game. When a~queue is dismantled, melding the parts
394 back to the heap takes $\O(\<rank>(q))$ time. We can therefore let the dismantling pay for it
395 and omit such induced melds from the meld forest. As the rank of a~heap is never increased
396 by induced melds, the above calculation is still a~proper upper bound on the cost
397 of the regular melds.
400 Before we estimate the time spent on deletions, we analyse the refills.
403 Every invokation of the \<Refill> procedure takes time $\O(1)$ amortized.
406 When \<Refill> is called from the \<DeleteMin> operation, it recurses on a~subtree of the
407 queue. This subtree can be split to the ``lossless'' lower part (rank~$r$ and below)
408 and the upper part where list concatenation and thus also corruption takes place. Whenever
409 we visit the lower part during the recursion, we spend at worst $\O(r)$ time there.
410 We will prove that the total time spent in the upper parts during the whole life of the
411 data structure is $\O(n)$. Since each upper vertex can perform at most two calls to the lower
412 part, the total time spent in the lower parts is $\O(rn)$. All this can be prepaid by the
415 Let us focus on the upper part. There are three possibilities of what can happen
416 when we visit a~vertex:
420 \:We delete it: Every vertex deleted has to have been created at some time in the past.
421 New vertices are created only during inserts and melds (when joining two trees) and
422 we have already shown that these operations have constant amortized complexity. Then the
423 same must hold for deletions.
425 \:We recurse twice and concatenate the lists: The lists are disassembled only when
426 they reach the root of the tree, otherwise they are only concatenated. We can easily
427 model the situation by a~binary tree forest similar to the meld forest. There are~$n$
428 leaves and every internal vertex has outdegree two, so the total number of concatenations
429 is at most~$n$. Each of them can be performed in constant time as the list is doubly linked.
431 \:We recurse only once: This occurs only if the rank is even and the gap between the
432 rank of this vertex and its sons is equal to~1. It therefore cannot happen twice in a~row,
433 thus it is clearly dominated by the cost of the other possibilities.
436 \>The total cost of all steps in the upper part is therefore $\O(n)$.
439 We now proceed with examining the \<DeleteMin> operation.
442 Every \<DeleteMin> takes $\O(1)$ time amortized.
445 Aside from refilling, which is $\O(1)$ by the previous lemma, the \<DeleteMin>
446 takes care of the Rank invariant. This happens by checking the length of the leftmost
447 path and dismantling the tree if the length is too far from the tree's rank~$k$.
448 When the invariant is satisfied, the leftmost path is visited by the subsequent
449 call to \<Refill>, so we can account the check on the refilling.
451 When we are dismantling, we have to pay $\O(k)$ for the operation itself and
452 another $\O(k)$ for melding the trees back to the heap. Since we have produced at most
453 $k/2$ subtrees of distinct ranks, some subtree of rank $k/2$ or more must be missing.
454 Its master tree contained at least $2^{k/2}$ vertices which are now permanently gone
455 from the data structure, so we can charge the cost against them.
456 A~single vertex can participate in the master trees of several dismantlings, but their
457 ranks are always strictly increasing. By the same argument as in the proof of
458 Lemma \ref{shmeld} (complexity of \<Meld>), each vertex pays $\O(1)$.
460 We must not forget that \<DeleteMin> also has to recalculate the suffix minima.
461 In the worst case, it requires touching $k$~trees. Because of the Rank invariant,
462 this is linear in the size of the
463 leftmost path and therefore it can be also paid for by \<Refill>. (Incidentally,
464 this was the only place where we needed the invariant.)
467 \<Explode>s are easy not only to implement, but also to analyse:
470 Every \<Explode> takes $\O(1)$ time amortized.
473 As all queues, vertices and items examined by \<Explode> are forever gone from the heap,
474 we can charge the constant time spent on each of them against the operations
475 that have created them.
478 It remains to take care of the calculation with ranks:
481 Every manipulation with ranks performed by the soft heap operations can be
482 implemented on the Pointer machine in constant amortized time.
485 We create a~``yardstick'' --- a~double linked list whose elements represent the possible
486 values of a~rank. Every vertex of a~queue will store its rank as a~pointer to
487 the corresponding ``tick'' of the yardstick. We will extend the list as necessary.
489 Comparison of two ranks for equality is then trivial, as is incrementing or decrementing
490 the rank by~1. Testing whether a~rank is odd can be handled by storing an~odd/even
491 flag in every tick. This covers all uses of ranks except for the comparisons for inequality
492 when melding. In step~1 of \<Meld>, we just mark the ticks of the two ranks and walk
493 the yardstick from the beginning until we come across a~mark. Thus we compare the ranks
494 in time proportional to the smaller of them, which is the real cost of the meld anyway.
495 The comparisons in steps 5 and~6 are trickier, but since the ranks of the elements put
496 to~$P$ are strictly increasing, we can start walking the list at the rank of the previous
497 element in~$P$. The cost is then the difference between the current and the previous rank
498 and their sum telescopes, again to the real cost of the meld.
501 Now we can put the bits together and laurel our effort with the following theorem:
503 \thmn{Performance of soft heaps, Chazelle \cite{chazelle:softheap}}\id{softheap}%
504 A~soft heap with error rate~$\varepsilon$ ($0<\varepsilon\le 1/2$) processes
505 a~sequence of operations starting with an~empty heap and containing $n$~\<Insert>s
506 in time $\O(n\log(1/\varepsilon))$ on the Pointer machine. At every moment, the
507 heap contains at most $\varepsilon n$ corrupted items.
510 We set the parameter~$r$ to~$2+2\lceil\log (1/\varepsilon)\rceil$. The rest follows
511 from the analysis above. By Lemma \ref{shcorrlemma}, there are always at most $n/2^{r-2}
512 \le \varepsilon n$ corrupted items in the heap. By Lemma \ref{shmeld}--\ref{shyards},
513 the time spent on all operations in the sequence can be paid for by charging $\O(r)$ time
514 against each \<Insert>. This yields the time bound.
518 When we set $\varepsilon = 1/2n$, the soft heap is not allowed to corrupt any
519 items, so it can be used like any usual heap. By the standard lower bound on
520 sorting it therefore requires $\Omega(\log n)$ time per operation, so the
521 time complexity is optimal for this choice of~$\varepsilon$. Chazelle \cite{chazelle:softheap}
522 proves that it is optimal for every choice of~$\varepsilon$.
524 The space consumed by the heap need not be linear in the \em{current} number
525 of items, but if a~case where this matters ever occured, we could fix it easily
526 by rebuilding the whole data structure completely after $n/2$ deletes. This
527 increases the number of potentially corrupted items, but at worst twice, so it
528 suffices to decrease~$\varepsilon$ twice.
530 %--------------------------------------------------------------------------------
532 \section{Robust contractions}
536 Having the soft heaps at hand, we would like to use them in a~conventional MST
537 algorithm in place of a~usual heap. The most efficient specimen of a~heap-based
538 algorithm we have seen so far is the Iterated Jarn\'\i{}k's algorithm (\ref{itjar}).
539 It is based on a~simple, yet powerful idea: Run the Jarn\'\i{}k's algorithm with
540 limited heap size, so that it stops when the neighborhood of the tree becomes
541 large. Grow multiple such trees, always starting in a~vertex not visited yet. All
542 these trees are contained in the MST, so by the Contraction lemma
543 (\ref{contlemma}) we can contract each of them to a~single vertex and iterate
544 the algorithm on the resulting graph.
546 We can try implanting the soft heap in this algorithm, preferably in the original
547 version without active edges (\ref{jarnik}) as the soft heap lacks the \<Decrease>
548 operation. This honest, but somewhat simple-minded attempt is however doomed to
549 fail. The reason is of course the corruption of items inside the heap, which
550 leads to increase of weights of a~subset of edges. In presence of corrupted
551 edges, most of the theory we have so carefully built breaks down. For example,
552 the Blue lemma (\ref{bluelemma}) now holds only when we consider a~cut with no
553 corrupted edges, with a~possible exception of the lightest edge of the cut.
554 Similarly, the Red lemma (\ref{redlemma}) is true only if the heaviest edge on
555 the cycle is not corrupted.
557 There is fortunately some light in this darkness. While the basic structural
558 properties of MST's no longer hold, there is a~weaker form of the Contraction
559 lemma that takes the corrupted edges into account. Before we prove this lemma,
560 we will expand our awareness of subgraphs which can be contracted.
563 A~subgraph $C\subseteq G$ is \df{contractible} iff for every pair of edges $e,f\in\delta(C)$\foot{That is,
564 edges with exactly one endpoint in~$C$.} there exists a~path in~$C$ connecting the endpoints
565 of the edges $e,f$ such that all edges on this path are lighter than either $e$ or~$f$.
567 \example\id{jarniscont}%
568 Let us see that when we stop the Jarn\'\i{}k's algorithm at some moment and
569 we take a~subgraph~$C$ induced by the constructed tree, this subgraph is contractible.
570 Indeed, when we consider any two distinct edges $uv, xy$ ($u,x\in C$ and $v,y\not\in C$),
571 they enter the algorithm's heap at some time. Without loss of generality $uv$~is the first.
572 Before the algorithm reaches the vertex~$x$, it adds the whole path $ux$ to the tree.
573 As the edge~$uv$ never leaves the heap, all edges on the path $ux$ must be lighter
576 We can now easily reformulate the Contraction lemma (\ref{contlemma}) in the language
577 of contractible subgraphs. We again assume that we are working with multigraphs
578 and that they need not be connected.
579 Furthermore, we slightly abuse the notation and we omit the explicit bijection
580 between $G-C$ and~$G/C$, so we can write $G=C \cup (G/C)$.
582 \lemman{Generalized contraction}
583 When~$C\subseteq G$ is a~contractible subgraph, then $\msf(G)=\msf(C) \cup \msf(G/C)$.
586 As both sides of the equality are forests spanning the same graph, it suffices
587 to show that $\msf(G) \subseteq \msf(C)\cup\msf(G/C)$. We know that the edges which
588 does not participate in the MSF are exactly those which are the heaviest on some cycle
589 (this is the Cycle rule \ref{cyclerule}).
591 Whenever an~edge~$g$ lies in~$C$, but not in~$\msf(C)$, then $g$~is the heaviest edge
592 on some cycle in~$C$. As this cycle is also contained in~$G$, the edge $g$~does not participate
595 Similarly for $g\in (G/C)\setminus\msf(G/C)$: when the cycle does not contain
596 the vertex~$c$ to which we contracted the subgraph~$C$, the cycle is present
597 in~$G$, too. Otherwise we consider the edges $e,f$ adjacent to~$c$ on this cycle.
598 Since $C$~is contractible, there must exist a~path~$P$ in~$C$ connecting the endpoints
599 of~$e$ and~$f$ in~$G$, such that all edges of~$P$ are lighter than either $e$ or~$f$
600 and hence also than~$g$. Expanding~$c$ in the cycle to the path~$P$ then produces
601 a~cycle in~$G$ whose heaviest edge is~$g$.
604 We are ready to bring corruption back to the game now and state a~``robust'' version
605 of this lemma. A~notation for corrupted graphs will be handy:
608 When~$G$ is a~weighted graph and~$R$ a~subset of its edges, we will use $G\crpt
609 R$ to denote an arbitrary graph obtained from~$G$ by increasing the weights of
610 some of the edges in~$R$. As usually, we will assume that all edge weights in this
611 graph are pairwise distinct. While this is technically not true for the corruption
612 caused by soft heaps, we can easily make the weights unique.
614 If~$C$ is a~subgraph of~$G$, we will refer to the edges of~$R$ whose exactly
615 one endpoint lies in~$C$ by~$R^C$ (i.e., $R^C = R\cap \delta(C)$).
617 \lemman{Robust contraction}\id{robcont}%
618 Let $G$ be a~weighted graph and $C$~its subgraph contractible in~$G\crpt R$
619 for some set of edges~$R$. Then $\msf(G) \subseteq \msf(C) \cup \msf((G/C) \setminus R^C) \cup R^C$.
622 We will modify the proof of the previous lemma. We will again consider all possible types
623 of edges which do not belong to the right-hand side and show that they are the
624 heaviest edges of certain cycles. Every edge~$g$ of~$G$ lies either in~$C$, or in $H=(G/C)\setminus R^C$,
625 or possibly in~$R^C$.
627 If $g\in C\setminus\msf(C)$, then the same argument as before applies.
629 If $g\in H\setminus\msf(H)$, we consider the cycle in~$H$ on which $e$~is the heaviest.
630 When $c$ (the vertex to which we have contracted~$C$) is outside this cycle, we are finished.
631 Otherwise we observe that the edges $e,f$ adjacent to~$c$ on this cycle cannot be corrupted
632 (they would be in~$R^C$ otherwise, which is impossible). By contractibility of~$C$ there exists
633 a~path~$P$ in~$(G\crpt R)\cup C$ such that all edges of~$P$ are lighter than $e$ or~$f$ and hence
634 also than~$g$. The weights of the edges of~$P$ in the original graph~$G$ cannot be higher than
635 in~$G\crpt R$, so the path~$P$ is lighter than~$g$ even in~$G$ and we can again perform the
636 trick with expanding the vertex~$c$ to~$P$ in the cycle~$C$. Hence $g\not\in\mst(G)$.
640 Our plan still is to mimic the Iterative Jarn\'\i{}k's algorithm. We will grow a~collection~$\C$
641 of non-overlapping contractible subgraphs and put aside the edges which got corrupted in the process.
642 We recursively compute the MSF of the subgraphs and of the contracted graph. Then we take the
643 union of these MSF's and add the corrupted edges. According to the previous lemma, this does not produce
644 the final MSF, but a~sparser graph containing it, on which we can continue.
646 We can formulate the exact partitioning algorithm as follows:
648 \algn{Partition a~graph to a~collection of contractible subgraphs}\id{partition}%
650 \algin A~graph~$G$ with an~edge comparison oracle, a~parameter~$t$ controlling the size of the subgraphs,
651 and an~accuracy parameter~$\varepsilon$.
652 \:Mark all vertices as ``live''.
653 \:$\C\=\emptyset$, $R^\C\=\emptyset$. \cmt{Start with an~empty collection and no corrupted edges.}
654 \:While there is a~live vertex~$v_0$:
655 \::$T=\{v_0\}$. \cmt{the tree we currently grow}
656 \::$K=\emptyset$. \cmt{edges known to be corrupted}
657 \::\<Create> a~soft heap with accuracy~$\varepsilon$ and \<Insert> the edges adjacent to~$v_0$ in it.
658 \::While the heap is not empty and $\vert T\vert \le t$:
659 \:::\<DeleteMin> an~edge $uv$ from the heap, assume $u\in T$.
660 \:::If $uv$ was corrupted, add it to~$K$.
661 \:::If $v\in T$, drop the edge and repeat the previous two steps.
663 \:::If $v$ is dead, break out of the current loop.
664 \:::Insert all edges incident with~$v$ to the heap.
665 \::$\C\=\C \cup \{G[T]\}$. \cmt{Record the subgraph induced by the tree.}
666 \::\<Explode> the heap and add all remaining corrupted edges to~$K$.
667 \::$R^\C\=R^\C \cup \{ K^T \}$. \cmt{Record the ``interesting'' corrupted edges.}
668 \::$G\=G\setminus K^T$. \cmt{Remove the corrupted edges from~$G$.}
669 \::Mark all vertices of~$T$ as ``dead''.
670 \algout The collection $\C$ of contractible subgraphs and the set~$R^\C$ of
671 corrupted edges in the neighborhood of these subgraphs.
674 \thmn{Partitioning to contractible subgraphs, Pettie \cite{pettie:optimal}}\id{partthm}%
675 Given a~weighted graph~$G$ and parameters $\varepsilon$ ($0<\varepsilon\le 1/2$)
676 and~$t$, the Partition algorithm \ref{partition} constructs a~collection
677 $\C=\{C_1,\ldots,C_k\}$ of subgraphs and a~set~$R^\C$ of corrupted edges such that:
680 \:All the $C_i$'s and the set~$R^\C$ are edge-disjoint.
681 \:Each $C_i$ contains at most~$t$ vertices.
682 \:Each vertex of~$G$ is contained in at least one~$C_i$.
683 \:The connected components of the union of all $C_i$'s have at least~$t$ vertices each,
684 except perhaps for those which are equal to a~connected component of~$G\setminus R^\C$.
685 \:$\vert R^\C\vert \le 2\varepsilon m$.
686 \:$\msf(G) \subseteq \bigcup_i \msf(C_i) \cup \msf\bigl((G / \bigcup_i C_i) \setminus R^\C\bigr) \cup R^\C$.
687 \:The algorithm runs in time $\O(n+m\log (1/\varepsilon))$.
691 The algorithm grows a~series of trees. A~tree is built from edges adjacent to live vertices
692 and once it is finished, all vertices of the tree die, so no edge is ever reused in another
693 tree. Edges of~$R^\C$ are immediately deleted from the graph, so they never participate
694 in any tree. The algorithm stops only if all vertices are dead, so each vertex must have
695 entered some tree. Each $C_i$ is induced by some tree and the trees have at most~$t$ vertices
696 each, which limits the size of the $C_i$'s as well. This proves claims 1--3.
698 Claim~4: We can show that each connected component has $t$~or more vertices as we already did
699 in the proof of Lemma \ref{ijsize}: How can a~new tree stop growing? Either it already
700 has~$t$ vertices, or it joins one of the existing trees (which only increases the
701 size of the component), or the heap becomes empty (which means that the tree spans
702 a~full component of the current graph and hence also of~$G\setminus R^\C$).
704 Claim~5: The set~$R^\C$ contains a~subset of edges corrupted by the soft heaps over
705 the course of the algorithm. As every edge is inserted to a~heap at most once
706 in every direction, the heaps can corrupt at worst $2\varepsilon m$ edges altogether.
708 We will prove the remaining two claims as separate lemmata.
711 \lemman{Correctness of Partition, Claim 6 of Theorem \ref{partthm}}
712 $$\msf(G) \subseteq \bigcup_i \msf(C_i) \cup \msf\biggl( \bigl(G / \bigcup_i C_i \bigr) \setminus R^\C\biggr) \cup R^\C.$$
715 By iterating the Robust contraction lemma (\ref{robcont}). Let $K_i$ be the set of edges
716 corrupted when constructing the subgraph~$C_i$ in the $i$-th phase (iteration of the outer
717 loop) of the algorithm, and similarly for the state of the other variables at that time.
718 We will use induction on~$i$ to prove that the lemma holds at the end of every phase.
720 At the beginning, the statement is obviously true, even as an~equality.
721 In the $i$-th phase, we construct the subgraph~$C_j$ by running the partial Jarn\'\i{}k's algorithm on the graph
722 $G_i = G\setminus\bigcup_{j<i} K_{\smash j}^{\C_j}$.
723 If it were not for corruption, the subgraph~$C_i$ would be contractible, as we already know from Example \ref{jarniscont}.
724 When the edges in~$K_i$ get corrupted, the subgraph is contractible in some corrupted graph
725 $G_i \crpt K_i$. (We have to be careful as the edges are becoming corrupted gradually,
726 but it is easy to check that it can only improve the situation.) Since $C_i$~is edge-disjoint
727 with the previous trees, it is also a~contractible subgraph of $(G_i / \bigcup_{j<i} C_j) \crpt K_i$.
728 Now we can use the Robust contraction lemma to show that:
730 \msf\biggl(\bigl(G / \bigcup_{i<j} \bigr) \setminus \bigcup_{i<j} K_j^{\C_j} \biggr) \subseteq
731 \msf(C_i) \cup \msf\biggl(\bigl(G / \bigcup_{i\le j} \bigr) \setminus \bigcup_{i\le j} K_j^{\C_j} \biggr) \cup K_i^{C_i},
733 which completes the induction step.
736 \lemman{Efficiency of Partition, Claim 7 of Theorem \ref{partthm}}
737 The Partition algorithm runs in time $\O(n+m\log(1/\varepsilon))$.
740 The inner loop (steps 7--13) processes the edges of the current subgraph~$C_i$ and also
741 the edges in its neighborhood $\delta(C_i)$. Steps 6 and~13 insert each such edge to the heap
742 at most once, so steps 8--12 also visit each edge at most once. For every edge, we spend
743 $\O(\log(1/\varepsilon))$ time amortized on inserting it and $\O(1)$ on the other operations
744 (by Theorem \ref{softheap} on performance of the soft heaps).
746 Each edge of~$G$ can participate in some $C_i\cup \delta(C_i)$ only twice before both its
747 ends die. The inner loop therefore processes $\O(m)$ edges total, so we spend $\O(m\log(1/\varepsilon))$
748 time there. The rest of the algorithm spends $\O(m)$ time on the other operations with subgraphs
749 and $\O(n)$ on identifying the live vertices.