1 / 21

CS 333 Design and Analysis of Computer Algorithms Michal Cutler Lecture 2 January 26, 2006

CS 333 Design and Analysis of Computer Algorithms Michal Cutler Lecture 2 January 26, 2006. Stable Matching Problem. Goal. Given n men and n women, find a "suitable" matching. Participants rate members of opposite sex. Each man lists women in order of preference from best to worst.

msunderland
Download Presentation

CS 333 Design and Analysis of Computer Algorithms Michal Cutler Lecture 2 January 26, 2006

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. CS 333Design and Analysis of Computer Algorithms Michal CutlerLecture 2January 26, 2006

  2. Stable Matching Problem • Goal. Given n men and n women, find a "suitable" matching. • Participants rate members of opposite sex. • Each man lists women in order of preference from best to worst. • Each woman lists men in order of preference from best to worst. favorite least favorite favorite least favorite 1st 2nd 3rd 1st 2nd 3rd Xavier Amy Bertha Clare Amy Yancey Xavier Zeus Yancey Bertha Amy Clare Bertha Xavier Yancey Zeus Zeus Amy Bertha Clare Clare Xavier Yancey Zeus Men’s Preference Profile Women’s Preference Profile

  3. Stable Matching Problem • Perfect matching: everyone is matched monogamously. • Each man gets exactly one woman. • Each woman gets exactly one man. • Stability: no incentive for some pair of participants to undermine assignment by joint action. • In matching M, an unmatched pair m-w is unstable if man m and woman w prefer each other to current partners. • Unstable pair m-w could each improve by eloping. • Stable matching: perfect matching with no unstable pairs. • Stable matching problem. Given the preference lists of n men and n women, find a stable matching if one exists.

  4. Propose-And-Reject Algorithm • Propose-and-reject algorithm. [Gale-Shapley 1962]Intuitive method that guarantees to find a stable matching. Initialize each person to be free. while (some man is free and hasn't proposed to every woman) { Choose such a man m w = 1st woman on m's list to whom m has not yet proposed if (w is free) assign m and w to be engaged elseif (w prefers m to her fiancé m') assign m and w to be engaged, and m' to be free else w rejects m }

  5. Proof of Correctness: Termination • Observation 1. Men propose to women in decreasing order of preference. • Observation 2. Once a woman is matched, she never becomes unmatched; she only "trades up." • Claim. Algorithm terminates after at most n2 iterations of while loop. • Pf.Each time through the while loop a man proposes to a new woman. There are only n2 possible proposals. ▪

  6. Proof of Correctness: Perfection • Claim. All men and women get matched. • Pf.(by contradiction) • Suppose, for sake of contradiction, that Zeus is not matched upon termination of algorithm. • Then some woman, say Amy, is not matched upon termination. • By Observation 2, Amy was never proposed to. • But, Zeus proposes to everyone, since he ends up unmatched. ▪

  7. Proof of Correctness: Stability • Claim. No unstable pairs. • Pf.(by contradiction) • Suppose A-Z is an unstable pair: each prefers each other to partner in Gale-Shapley matching S*. • Case 1: Z never proposed to A. Z prefers his GS partner to A.  A-Z is stable. • Case 2: Z proposed to A. A rejected Z (right away or later) A prefers her GS partner to Z. A-Z is stable. • In either case A-Z is stable, a contradiction. ▪ men propose in decreasingorder of preference S* Amy-Yancey Bertha-Zeus . . . women only trade up

  8. Summary • Stable matching problem. Given n men and n women, and their preferences, find a stable matching if one exists. • Gale-Shapley algorithm. Guarantees to find a stable matching for any problem instance.

  9. 1.2 Five Representative Problems

  10. b e h Interval Scheduling (Activity Selection) • Input. Set of jobs with start times and finish times. • Goal. Find maximum cardinality subset of mutually compatible jobs. jobs don't overlap Greedy method Activity Selection rule O(nlgn) solution a b c d e f g h Time 0 1 2 3 4 5 6 7 8 9 10 11

  11. Weighted Interval Scheduling • Input. Set of jobs with start times, finish times, and weights. • Goal. Find maximum weight subset of mutually compatible jobs. Dynamic programming method Optimal solution generated from optimal solution of smaller problems Save solutions! O(nlgn) solution WIS 23 12 20 26 13 20 11 16 Time 0 1 2 3 4 5 6 7 8 9 10 11

  12. Bipartite Matching • Input. Bipartite graph. • Goal. Find maximumcardinality matching. Network flow method Convert problem into a max-flow problem O(|V|3) solution and better solutions A 1 B 2 Definitions: Undirected graph Bipartite graph Cardinality of a set C 3 D 4 E 5

  13. 1 4 5 6 Independent Set • Input. Graph. • Goal. Find maximum cardinality independent set. subset of nodes such that no two joined by an edge Is there an independent subset of cardinality B? NO efficient solution! EASY to check solution! NP-Complete problem! 2 1 Note: Relation of Activity Selection and Bipartite Matching problems to Independent Set 4 5 3 7 6

  14. Competitive Facility Location • Input. Graph with weight on each each node. • Game. Two competing players alternate in selecting nodes. Not allowed to select a node if any of its neighbors have been selected. • Goal. Select a maximum weight subset of nodes. Can the second player guarantee a weight of B? No easy way to check solution PSPACE-complete 10 1 5 1 15 1 5 15 5 10 Second player can guarantee 20, but not 25.

  15. Five Representative Problems • Variations on a theme: independent set. • Interval scheduling: n log n greedy algorithm. • Weighted interval scheduling: n log n dynamic programming algorithm. • Bipartite matching: nk max-flow based algorithm. • Independent set: NP-complete. • Competitive facility location: PSPACE-complete.

  16. Computational Tractability As soon as an Analytic Engine exists, it will necessarily guide the future course of the science. Whenever any result is sought by its aid, the question will arise - By what course of calculation can these results be arrived at by the machine in the shortest time? - Charles Babbage Charles Babbage (1864) Analytic Engine (schematic)

  17. Polynomial-Time • Brute force. For many non-trivial problems, there is a natural brute force search algorithm that checks every possible solution. • Typically takes 2N time or worse for inputs of size N. • Unacceptable in practice. • Desirable scaling property. When the input size doubles, the algorithm should only slow down by some constant factor C. • Def. An algorithm is poly-time if the above scaling property holds. n! for stable matchingwith n men and n women There exists constants c > 0 and d > 0 such that on every input of size N, its running time is bounded by cNd steps. choose C =c* 2d

  18. Worst-Case Analysis • Worst case running time. Obtain bound on largest possible running time of algorithm on input of a given size N. • Generally captures efficiency in practice. • Draconian view, but hard to find effective alternative. • Average case running time. • Obtain bound on average running time of algorithm as a function of input size N. • Need to know distribution of inputs (unknown apriori) • Often make assumption all inputs equally likely

  19. Worst-Case Polynomial-Time • Def. An algorithm is efficient if its running time is polynomial. • Justification: It really works in practice! • Although 6.02  1023 N20 is technically poly-time, it would be useless in practice. • In practice, the poly-time algorithms that people develop almost always have low constants and low exponents. • Breaking through the exponential barrier of brute force typically exposes some crucial structure of the problem. • Exceptions. • Some poly-time algorithms do have high constants and/or exponents, and are useless in practice. • Some exponential-time (or worse) algorithms are widely used because the worst-case instances seem to be rare. simplex methodUnix grep

  20. Why It Matters

  21. Factorial

More Related