Please read the new rule regarding the restriction on the use of AI tools. ×

SenbonzakuraKageyoshi's blog

By SenbonzakuraKageyoshi, history, 3 years ago, In English

Hi everyone. I have been stuck on this problem for quite sometime and would like some help from the community. For those who aren't familiar with the name, let me define the problem quickly.

You are given a set of n numbers. In a single merge operation you can remove any 2 elements from the set and put their sum back inside. The cost of each merge operation is also equal to the sum. Repeat this until there is only 1 element left in the set. The total cost is the sum of cost of individual operations. We need to minimize the total cost.

Example-

Intitially : cost=0, v={1,2,3}

merge 1 & 2, cost+=3, v={3,3}

merge 3 & 3, cost+=6, v={6}

So finally,cost=9

So basically the greedy approach works here. In each iteration just merge the 2 smallest elements. I sort of get the intuition but I can't prove why this works. I can see that this can be converted to the Huffman Coding problem but the math in proofs is beyond me. I would really appreciate if someone could give me a less mathy solution...

Thank you for your time!!

| Write comment?
»
3 years ago, # |
Rev. 4   Vote: I like it 0 Vote: I do not like it

This is the same as this for fixed array though.

Idk about why greedy works but you can always try proof by AC :) Sure that there is some exchange argument lurking out there.

Solution
  • »
    »
    3 years ago, # ^ |
      Vote: I like it +7 Vote: I do not like it

    I don't think these are equivalent problems...in your question, the relative positions of the elements are fixed, however in the problem that I described, it is not.

»
3 years ago, # |
Rev. 2   Vote: I like it +42 Vote: I do not like it

wrong

  • »
    »
    3 years ago, # ^ |
      Vote: I like it +11 Vote: I do not like it

    Elegant! Thank you so much.

    I really struggle trying to prove correctness of greedy algorithms.

  • »
    »
    3 years ago, # ^ |
      Vote: I like it +14 Vote: I do not like it

    I don't understand how this idea is meant to work in the case where $$$(a_1+s_1)$$$ is not immediately merged with $$$(a_2+s_2)$$$. Suppose, for example, that $$$(a_1+s_1)$$$ is merged first with $$$x$$$ and only then with $$$(a_2+s_2)$$$. Then, you can't mean to merge $$$s_1$$$ with $$$x$$$, then $$$(s_1 + x)$$$ with $$$s_2$$$, and finally merge $$$a_1$$$ with $$$a_2$$$ and $$$(a_1 + a_2)$$$ with $$$(s_1 + x + s_2)$$$, because that has a greater cost, by $$$x - a_1$$$.

    A strategy that does work is to notice that the final cost of an optimal merging strategy is $$$\sum_{i=1}^n c_i a_i$$$, where the coefficient $$$c_i$$$ is the number of merges $$$a_i$$$ plays a role in. We can assume without loss of optimality that $$$a$$$ is sorted ascending and that $$$c$$$ is sorted descending, since we are re-arrange $$$a$$$ before merging at no cost otherwise. Now, suppose that the first merge that involves the smallest element $$$a_1$$$ is $$$a_1$$$ with $$$x$$$, and let $$$j$$$ be the any index such that $$$a_j$$$ was (directly or indirectly) merged into $$$x$$$. Then, the merges $$$a_j$$$ was involved in are a superset of those $$$a_1$$$ was involved in, so $$$c_j \geq c_1$$$. But since $$$c$$$ is assumed to be sorted descending, this means that $$$c_j = c_1$$$ and thus that $$$a_j$$$ is not involved in any merges not involving $$$a_1$$$, i.e. $$$x$$$ is not the result of a merge at all, and $$$a_1$$$ was merged directly with $$$a_j$$$ Moreover, since $$$j > 1$$$, we have that $$$c_1 \geq c_2 \geq c_j = c_1$$$, so that the coefficients $$$c_2$$$ and $$$c_j$$$ are equal. Thus, we can swap the second-smallest element $$$a_2$$$ with $$$a_j$$$ without changing the cost, and re-order the resulting direct merge between $$$a_1$$$ and $$$a_2$$$ to be at the beginning.

    • »
      »
      »
      3 years ago, # ^ |
        Vote: I like it 0 Vote: I do not like it

      By $$$s_1$$$ and $$$s_2$$$ I meant some sets of elements and not necessarily a single element.

      • »
        »
        »
        »
        3 years ago, # ^ |
          Vote: I like it +13 Vote: I do not like it

        Right, I mis-borrowed your notation. But I still don't understand how this can work.

        Let me give a concrete example, with the original multiset being $$$\{101, 102, 104, 108, 116, 132\}$$$, which has the following as one optimal merge order: $$$101 + 104 \to 205$$$, $$$205 + 116 \to 321$$$, $$$102 + 108 \to 210$$$, $$$210 + 132 \to 342$$$, and $$$321 + 342 \to 663$$$, with a total cost of $$$205+321+210+342+663 = 1741$$$. Then, $$$a_1 = 101$$$, $$$s_1 = \{a_1, 104, 116\}$$$, $$$a_2 = 102$$$, $$$s_2 = \{a_2, 108, 132\}$$$, right?

        If we merge the "something-else" parts together in the same way, we get $$$104 + 116 \to 220$$$, $$$108 + 132 \to 240$$$, and $$$220+240 \to 460$$$. Then, merging $$$(a_1 + a_2)$$$ is $$$101 + 102 \to 203$$$, and finally everything together $$$460 + 203 \to 663$$$. Is this is what you've described? But its total cost is $$$220 + 240 + 460 + 203 + 663 = 1786$$$, which is strictly greater than the original cost.

        So, either I'm misunderstanding you, or your reasoning is totally wrong.

        • »
          »
          »
          »
          »
          3 years ago, # ^ |
            Vote: I like it +13 Vote: I do not like it

          Yeah you're right, it seemed simpler than it actually is.

    • »
      »
      »
      3 years ago, # ^ |
        Vote: I like it 0 Vote: I do not like it

      Thanks a lot for sharing your approach!

»
3 years ago, # |
  Vote: I like it +47 Vote: I do not like it

There is another proof of the correctness. We create a node for every number in the set. If we merge two nodes $$$u$$$ and $$$v$$$, create a new node and make $$$u$$$ and $$$v$$$ its children. In the end we have a rooted tree whose leaves are original elements in the set. It is quite obvious that every leaf contribute to the total cost its depth times (with the root having depth 0). So for every possible rooted tree we must put the smallest 2 numbers the deepest in the tree, which means they should be merged first.

»
3 years ago, # |
  Vote: I like it +6 Vote: I do not like it

Interesting that noone mentioned this (solution of) problem is exactly Huffman encoding, did I make something wrong? https://en.wikipedia.org/wiki/Arithmetic_coding#Huffman_coding

  • »
    »
    3 years ago, # ^ |
      Vote: I like it +21 Vote: I do not like it

    Mr.Daddy mentions he knows of it in the last paragraph of the blog.

    • »
      »
      »
      3 years ago, # ^ |
        Vote: I like it +6 Vote: I do not like it

      Oh yea, sorry for being blind :(

  • »
    »
    3 years ago, # ^ |
      Vote: I like it +10 Vote: I do not like it

    I made the connection, but got scared off by a dense packing of mathematical symbols in the proofs lol.