Beefy Boxes and Bandwidth Generously Provided by pair Networks
XP is just a number
 
PerlMonks  

Re^3: Evolving a faster filter? (optimal solution?)

by LanX (Canon)
on Jan 04, 2013 at 21:22 UTC ( #1011721=note: print w/ replies, xml ) Need Help??


in reply to Re^2: Evolving a faster filter? (sort)
in thread Evolving a faster filter?

my @order = sort { $Costs[$a]+$Trims[$a]*$Costs[$b] <=> $Costs[$b]+$Trims[$b]*$Costs[ +$a] } 0..$#Costs;

I'm pretty sure that this is the optimal solution, but I'm too lazy to write down the complete mathematical proof.

The basic idea is that the terms represent the general cost difference of swapping the first and the second filter╣!

So by sorting you get a solution which can't be improved by a pairwise swapping and any permutation can be represented by a sequence of pairwise swaps.

Cheers Rolf

╣) see restructured formula for c in Re^2: Evolving a faster filter? (combinatorics) and you will notice that these are the first elements and the rest is fix.

UPDATE:

basic transformations lead to a simpler solution:

my @order = sort { $Costs[$a]/(1-$Trims[$a]) <=> $Costs[$b]/(1-$Trims[$b]) } 0..$#Costs;

which can be precalculated to save calculation time

my @order = sort { $weight[$a] <=> $weight[$b] } 0..$#Costs;

(the edge case of a division by zero must be handled as practically infinity)


Comment on Re^3: Evolving a faster filter? (optimal solution?)
Select or Download Code
Re^4: Evolving a faster filter? (optimal?)
by tye (Cardinal) on Jan 04, 2013 at 21:32 UTC

    That's not enough to prove it. You certainly get a solution that can't be improved by a single swapping of adjacent filters. And if your sort order using that algorithm is well-defined, then you will get an optimal solution. That is, if you never get the $a < $b < $c < $a case. Update: No, maybe not even that (unless someone can convince me that "of adjacent filters" is not needed above). Update: Ah, ruling out adjacent swaps also rules out any swaps. Update: Silly me. Ruling out swapping of elements that start out adjacent doesn't rule out swapping of elements that didn't start out adjacent (but became adjacent from swapping elements that did start out adjacent).

    I thought I had already found a case where it wasn't optimal. But the total cost was reported as identical as the first cost despite a different ordering being chosen. So it might be hard to find a case where it isn't optimal.

    I bet it makes doing anything more than that not worth the effort for Ovid's usage, at least. :)

    - tye        

      Well my argument is sufficient to show that a solution where two adjacent filters don't follow this order can't be optimal, because otherwise swapping those adjacent filters f[i] and f[i+1] would improve the result.

      So any optimal solution must follow this strict order criteria. ╣

      qed! =)

      Cheers Rolf

      PS: I'm glad I didn't start implementing the B&B algorithm :-)

      UPDATE:

      ╣) and it's easy to see that all ordered solutions (plural b/c adjacent filters can have the same weight) imply the same total cost.

        Indeed!

        And the number of choices that leaves you with is rather tiny.

        Worse (or better), from throwing cases at the code, I bet it is possible to prove that all such orderings are optimal so that the one that sort gives you is optimal.

        I think it might not be hard to prove and $a <= $b <= $c implies $a <= $c (assuming non-negative cost and selectivity between 0 and 1). And that should be enough.

        - tye        

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1011721]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others cooling their heels in the Monastery: (8)
As of 2014-09-21 18:15 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    How do you remember the number of days in each month?











    Results (173 votes), past polls