Solve day 5 of AoC 2024
This commit is contained in:
parent
1d293b49e8
commit
74ab5de1ea
6 changed files with 1603 additions and 0 deletions
7
advent-of-code/2024/day_05/Cargo.lock
generated
Normal file
7
advent-of-code/2024/day_05/Cargo.lock
generated
Normal file
|
@ -0,0 +1,7 @@
|
|||
# This file is automatically @generated by Cargo.
|
||||
# It is not intended for manual editing.
|
||||
version = 3
|
||||
|
||||
[[package]]
|
||||
name = "day_05"
|
||||
version = "0.1.0"
|
6
advent-of-code/2024/day_05/Cargo.toml
Normal file
6
advent-of-code/2024/day_05/Cargo.toml
Normal file
|
@ -0,0 +1,6 @@
|
|||
[package]
|
||||
name = "day_05"
|
||||
version = "0.1.0"
|
||||
edition = "2021"
|
||||
|
||||
[dependencies]
|
114
advent-of-code/2024/day_05/README.md
Normal file
114
advent-of-code/2024/day_05/README.md
Normal file
|
@ -0,0 +1,114 @@
|
|||
# Day 5: Print Queue
|
||||
|
||||
Satisfied with their search on Ceres, the squadron of scholars suggests subsequently scanning the stationery stacks of sub-basement 17.
|
||||
|
||||
The North Pole printing department is busier than ever this close to Christmas, and while The Historians
|
||||
continue their search of this historically significant facility, an Elf operating a very familiar printer beckons you over.
|
||||
|
||||
The Elf must recognize you, because they waste no time explaining that the new sleigh launch safety manual updates won't print correctly.
|
||||
Failure to update the safety manuals would be dire indeed, so you offer your services.
|
||||
|
||||
Safety protocols clearly indicate that new pages for the safety manuals must be printed in a very specific order.
|
||||
The notation X|Y means that if both page number X and page number Y are to be produced as part of an update,
|
||||
page number X must be printed at some point before page number Y.
|
||||
|
||||
The Elf has for you both the page ordering rules and the pages to produce in each update (your puzzle input),
|
||||
but can't figure out whether each update has the pages in the right order.
|
||||
|
||||
For example:
|
||||
|
||||
```
|
||||
47|53
|
||||
97|13
|
||||
97|61
|
||||
97|47
|
||||
75|29
|
||||
61|13
|
||||
75|53
|
||||
29|13
|
||||
97|29
|
||||
53|29
|
||||
61|53
|
||||
97|53
|
||||
61|29
|
||||
47|13
|
||||
75|47
|
||||
97|75
|
||||
47|61
|
||||
75|61
|
||||
47|29
|
||||
75|13
|
||||
53|13
|
||||
|
||||
75,47,61,53,29
|
||||
97,61,53,29,13
|
||||
75,29,13
|
||||
75,97,47,61,53
|
||||
61,13,29
|
||||
97,13,75,29,47
|
||||
```
|
||||
|
||||
The first section specifies the page ordering rules, one per line.
|
||||
The first rule, 47|53, means that if an update includes both page number 47 and page number 53,
|
||||
then page number 47 must be printed at some point before page number 53.
|
||||
(47 doesn't necessarily need to be immediately before 53; other pages are allowed to be between them.)
|
||||
|
||||
The second section specifies the page numbers of each update. Because most safety manuals are different,
|
||||
the pages needed in the updates are different too. The first update, 75,47,61,53,29, means that the update consists of page numbers
|
||||
75, 47, 61, 53, and 29.
|
||||
|
||||
To get the printers going as soon as possible, start by identifying which updates are already in the right order.
|
||||
|
||||
In the above example, the first update (75,47,61,53,29) is in the right order:
|
||||
|
||||
- 75 is correctly first because there are rules that put each other page after it: 75|47, 75|61, 75|53, and 75|29.
|
||||
- 47 is correctly second because 75 must be before it (75|47) and every other page must be after it according to 47|61, 47|53, and 47|29.
|
||||
- 61 is correctly in the middle because 75 and 47 are before it (75|61 and 47|61) and 53 and 29 are after it (61|53 and 61|29).
|
||||
- 53 is correctly fourth because it is before page number 29 (53|29).
|
||||
- 29 is the only page left and so is correctly last.
|
||||
|
||||
Because the first update does not include some page numbers, the ordering rules involving those missing page numbers are ignored.
|
||||
|
||||
The second and third updates are also in the correct order according to the rules. Like the first update,
|
||||
they also do not include every page number, and so only some of the ordering rules apply - within each update,
|
||||
the ordering rules that involve missing page numbers are not used.
|
||||
|
||||
The fourth update, 75,97,47,61,53, is not in the correct order: it would print 75 before 97, which violates the rule 97|75.
|
||||
|
||||
The fifth update, 61,13,29, is also not in the correct order, since it breaks the rule 29|13.
|
||||
|
||||
The last update, 97,13,75,29,47, is not in the correct order due to breaking several rules.
|
||||
|
||||
For some reason, the Elves also need to know the middle page number of each update being printed.
|
||||
Because you are currently only printing the correctly-ordered updates, you will need to find the middle page number of each
|
||||
correctly-ordered update. In the above example, the correctly-ordered updates are:
|
||||
|
||||
```
|
||||
75,47,61,53,29
|
||||
97,61,53,29,13
|
||||
75,29,13
|
||||
```
|
||||
|
||||
These have middle page numbers of 61, 53, and 29 respectively. Adding these page numbers together gives 143.
|
||||
|
||||
Of course, you'll need to be careful: the actual list of page ordering rules is bigger and more complicated than the above example.
|
||||
|
||||
Determine which updates are already in the correct order. What do you get if you add up the middle page number from those
|
||||
correctly-ordered updates?
|
||||
|
||||
## Part Two
|
||||
|
||||
While the Elves get to work printing the correctly-ordered updates, you have a little time to fix the rest of them.
|
||||
|
||||
For each of the incorrectly-ordered updates, use the page ordering rules to put the page numbers in the right order.
|
||||
For the above example, here are the three incorrectly-ordered updates and their correct orderings:
|
||||
|
||||
- 75,97,47,61,53 becomes 97,75,47,61,53.
|
||||
- 61,13,29 becomes 61,29,13.
|
||||
- 97,13,75,29,47 becomes 97,75,47,29,13.
|
||||
|
||||
After taking only the incorrectly-ordered updates and ordering them correctly, their middle page numbers are 47, 29, and 47.
|
||||
Adding these together produces 123.
|
||||
|
||||
Find the updates which are not in the correct order.
|
||||
What do you get if you add up the middle page numbers after correctly ordering just those updates?
|
1359
advent-of-code/2024/day_05/input.txt
Normal file
1359
advent-of-code/2024/day_05/input.txt
Normal file
File diff suppressed because it is too large
Load diff
58
advent-of-code/2024/day_05/src/lib.rs
Normal file
58
advent-of-code/2024/day_05/src/lib.rs
Normal file
|
@ -0,0 +1,58 @@
|
|||
use std::collections::HashSet;
|
||||
|
||||
#[derive(PartialEq, Hash, Eq)]
|
||||
pub struct Rule {
|
||||
pub before: i32,
|
||||
pub after: i32,
|
||||
}
|
||||
|
||||
pub fn filter_updates(
|
||||
rules: &HashSet<Rule>,
|
||||
updates: &Vec<Vec<i32>>,
|
||||
use_correct_updates: bool,
|
||||
) -> Vec<Vec<i32>> {
|
||||
let mut res: Vec<Vec<i32>> = Vec::new();
|
||||
|
||||
for update in updates.iter() {
|
||||
if is_update_correct(&rules, update) == use_correct_updates {
|
||||
res.push(update.clone());
|
||||
}
|
||||
}
|
||||
|
||||
res
|
||||
}
|
||||
|
||||
fn is_update_correct(rules: &HashSet<Rule>, update: &Vec<i32>) -> bool {
|
||||
for i in 0..update.len() - 1 {
|
||||
for j in i + 1..update.len() {
|
||||
let bad_rule = Rule {
|
||||
before: update[j],
|
||||
after: update[i],
|
||||
};
|
||||
if rules.contains(&bad_rule) {
|
||||
return false;
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
true
|
||||
}
|
||||
|
||||
/// Bubble sort that works according to the provided rules.
|
||||
pub fn fix_update(rules: &HashSet<Rule>, update: &Vec<i32>) -> Vec<i32> {
|
||||
let mut res = update.clone();
|
||||
|
||||
for i in 0..res.len() - 1 {
|
||||
for j in i + 1..res.len() {
|
||||
let bad_rule = Rule {
|
||||
before: res[j],
|
||||
after: res[i],
|
||||
};
|
||||
if rules.contains(&bad_rule) {
|
||||
(res[i], res[j]) = (res[j], res[i])
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
res
|
||||
}
|
59
advent-of-code/2024/day_05/src/main.rs
Normal file
59
advent-of-code/2024/day_05/src/main.rs
Normal file
|
@ -0,0 +1,59 @@
|
|||
use std::collections::HashSet;
|
||||
use std::io::{BufRead, BufReader};
|
||||
|
||||
use day_05::{filter_updates, fix_update, Rule};
|
||||
|
||||
fn main() -> std::io::Result<()> {
|
||||
let file = std::fs::File::open("input.txt")?;
|
||||
let reader = BufReader::new(file);
|
||||
|
||||
let mut updates: Vec<Vec<i32>> = Vec::new();
|
||||
let mut rules: HashSet<Rule> = HashSet::new();
|
||||
let mut section = 1;
|
||||
|
||||
for line in reader.lines() {
|
||||
let content = line?;
|
||||
|
||||
if section == 2 {
|
||||
let pages: Vec<i32> = content
|
||||
.split(",")
|
||||
.map(|s| s.parse::<i32>().unwrap())
|
||||
.collect();
|
||||
updates.push(pages);
|
||||
continue;
|
||||
}
|
||||
|
||||
if content.len() == 0 {
|
||||
section = 2;
|
||||
continue;
|
||||
}
|
||||
|
||||
let pages: Vec<i32> = content
|
||||
.split("|")
|
||||
.map(|s| s.parse::<i32>().unwrap())
|
||||
.collect();
|
||||
rules.insert(Rule {
|
||||
before: pages[0],
|
||||
after: pages[1],
|
||||
});
|
||||
}
|
||||
|
||||
let correct_updates = filter_updates(&rules, &updates, true);
|
||||
let mut middle_num_sum: i32 = correct_updates
|
||||
.iter()
|
||||
.map(|pages| pages[pages.len() / 2])
|
||||
.sum();
|
||||
|
||||
println!("Part 1: {}", middle_num_sum);
|
||||
|
||||
let incorrect_updates = filter_updates(&rules, &updates, false);
|
||||
middle_num_sum = incorrect_updates
|
||||
.iter()
|
||||
.map(|update| fix_update(&rules, update))
|
||||
.map(|pages| pages[pages.len() / 2])
|
||||
.sum();
|
||||
|
||||
println!("Part 2: {}", middle_num_sum);
|
||||
|
||||
Ok(())
|
||||
}
|
Loading…
Reference in a new issue