### You're not signed in!

Sign in to save your progress and sync your settings across devices.

# Greedy Algorithms with Sorting

Author: Darren Yao

Solving greedy problems by sorting the input.

Resources | |||
---|---|---|---|

IUSACO | Module is based off this. | ||

CPH | Scheduling, Tasks & Deadlines, Huffman Coding | ||

PAPS | DAGs, Scheduling | ||

CPC | slides from Intro to Algorithms |

Usually, when using a greedy algorithm, there is a **value function** that determines which choice is considered most optimal. For example, we often want to maximize or minimize a certain quantity, so we take the largest or smallest possible value in the next step.

Here, we'll focus on problems where some sorting step is involved.

## Example: Studying Algorithms

Steph wants to improve her knowledge of algorithms over winter break. She has a total of $X$ ($1 \leq X \leq 10^4$) minutes to dedicate to learning algorithms. There are $N$ ($1 \leq N \leq 100$) algorithms, and each one of them requires $a_i$ ($1 \leq a_i \leq 100$) minutes to learn. Find the maximum number of algorithms she can learn.

### Solution

Solution

## Example: The Scheduling Problem

Focus Problem â€“ read through this problem before continuing!

There are $N$ events, each described by their starting and ending times. You can only attend one event at a time, and if you choose to attend an event, you must attend the entire event. Traveling between events is instantaneous. What's the maximum number of events you can attend?

### Bad Greedy: Earliest Starting Next Event

One possible ordering for a greedy algorithm would always select the next possible event that begins as soon as possible. Let's look at the following example, where the selected events are highlighted in red:

In this example, the greedy algorithm selects two events, which is optimal. However, this doesn't always work, as shown by the following counterexample:

In this case, the greedy algorithm selects to attend only one event. However, the optimal solution would be the following:

### Correct Greedy: Earliest Ending Next Event

Instead, we can select the event that ends as early as possible. This correctly selects the three events.

In fact, this algorithm always works. A brief explanation of correctness is as follows. If we have two events $E_1$ and $E_2$, with $E_2$ ending later than $E_1$, then it is always optimal to select $E_1$. This is because selecting $E_1$ gives us more choices for future events. If we can select an event to go after $E_2$, then that event can also go after $E_1$, because $E_1$ ends first. Thus, the set of events that can go after $E_2$ is a subset of the events that can go after $E_1$, making $E_1$ the optimal choice.

For the following code, let's say we have the array `events`

of events, which each contain a start and an end point.

C++

We'll be using the C++ built in container pair to store each event. Note that since the standard sort in C++ sorts by first element, we will store each event as `pair<end, start>`

.

1// read in the input, store the events in pair<int, int>[] events.2sort(events, events + n); // sorts by first element (ending time)3int currentEventEnd = -1; // end of event currently attending4int ans = 0; // how many events were attended?5for(int i = 0; i < n; i++){ // process events in order of end time6 if(events[i].second >= currentEventEnd){ // if event can be attended7 // we know that this is the earliest ending event that we can attend8 // because of how the events are sorted9 currentEventEnd = events[i].first;10 ans++;

Java

We'll be using the following static class to store each event:

1static class Event implements Comparable<Event>{2 int start; int end;3 public Event(int s, int e){4 start = s; end = e;5 }6 public int compareTo(Event e){7 return Integer.compare(this.end, e.end);8 }9}

1// read in the input, store the events in Event[] events.2Arrays.sort(events); // sorts by comparator we defined above3int currentEventEnd = -1; // end of event currently attending4int ans = 0; // how many events were attended?5for(int i = 0; i < n; i++){ // process events in order of end time6 if(events[i].start >= currentEventEnd){ // if event can be attended7 // we know that this is the earliest ending event that we can attend8 // because of how the events are sorted9 currentEventEnd = events[i].end;10 ans++;

## When Greedy Fails

We'll provide a few common examples of when greedy fails, so that you can avoid falling into obvious traps and wasting time getting wrong answers in contest.

### Coin Change

This problem gives several coin denominations, and asks for the minimum number of coins needed to make a certain value. Greedy algorithms can be used to solve this problem only in very specific cases (it can be proven that it works for the American as well as the Euro coin systems). However, it doesn't work in the general case. For example, let the coin denominations be $\{1, 3, 4\}$, and say the value we want is 6. The optimal solution is $\{3, 3\}$, which requires only two coins, but the greedy method of taking the highest possible valued coin that fits in the remaining denomination gives the solution $\{4, 1, 1\}$, which is incorrect.

### Knapsack

The knapsack problem gives a number of items, each having a **weight** and a **value**, and we want to choose a subset of these items. We are limited to a certain weight, and we want to maximize the value of the items that we take.

Let's take the following example, where we have a maximum capacity of 4:

Item | Weight | Value | Value Per Weight |
---|---|---|---|

A | 3 | 18 | 6 |

B | 2 | 10 | 5 |

C | 2 | 10 | 5 |

If we use greedy based on highest value first, we choose item A and then we are done, as we don't have remaining weight to fit either of the other two. Using greedy based on value per weight again selects item A and then quits. However, the optimal solution is to select items B and C, as they combined have a higher value than item A alone. In fact, there is no working greedy solution. The solution to this problem uses **dynamic programming**, which is covered in gold.

## Problems

### CSES

Status | Source | Problem Name | Difficulty | Tags | Solution |
---|---|---|---|---|---|

CSES | Easy | Show Sketch | |||

Silver | Easy | ## Show TagsSorting | |||

CSES | Easy | Show Sketch | |||

CSES | Easy | Show Sketch | |||

CSES | Easy | ## Show Tagsmultiset, greedy | View Solution | ||

CSES | Easy | CPH 6.3 | |||

CSES | Normal | ## Show Tagssets | |||

CSES | Normal | External Sol |

### Other

Status | Source | Problem Name | Difficulty | Tags | Solution |
---|---|---|---|---|---|

Silver | Easy | ## Show TagsSorting | External Sol | ||

Silver | Easy | ||||

Gold | Normal | External Sol | |||

Silver | Normal | External Sol | |||

Silver | Normal | ## Show TagsSorting | External Sol | ||

CSA | Normal | Check CSA |