1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241
//! This is my solution for [Advent of Code - Day 11 - _Dumbo Octopus_](https://adventofcode.com/2021/day/11)
//!
//! Today was again using a grid of digits. This time we had to manage cascading updates as one cell overflowing
//! beyond 9 caused neighbouring cells to increase, potentially triggering more cells. If you've ever played
//! [Pandemic](https://boardgamegeek.com/boardgame/30549/pandemic), today's puzzle may give you flashbacks.
//!
//! The grid shared a lot of similarities with the grid in [`crate::day_9`], and so I reused that implementation
//! adding extra methods to meet today's needs. Whilst writing the solution I just imported the Grid directly from
//! [`crate::day_9`], but once submitted I did some cleanup refactoring and extracted it into its own module under
//! [`crate::util`], leaving the puzzle specific methods in their own impl blocks in the relevant module. Having a
//! comprehensive set of tests made this a pretty easy refactor.
//!
//! [`Grid::set`] was needed to allow incrementing the values in the cells as the octopuses powered up.
//! [`Grid::get_all_surrounds`] was needed separate to [`Grid::get_orthogonal_surrounds`] as today's
//! requirements considered diagonal cells adjacent. This caused some head scratching when I failed to notice this
//! difference, but [`Grid::print`] let me visualise the grid and work out what was wrong.
//!
//! The bulk of today's solutions is handled by [`Grid::iterate_and_flash`] which handles a single cycle of
//! incrementing the octopuses, and resolving any resulting flashes. [`Grid::count_flashes`] implements part one by
//! repeatedly calling [`Grid::iterate_and_flash`] the required number of times, summing the resulting flash counts.
//! [`Grid::run_until_sync`] also repeatedly calls [`Grid::iterate_and_flash`] until the count of flashes is equal to
//! the number of cells in the grid, indicating all octopuses flashed in sync, and returns the iteration it has reached.
use std::collections::HashSet;
use std::fs;
#[doc(inline)]
pub use crate::util::grid::Grid;
impl Grid {
/// Iterate through the four orthogonal cells, collecting the 2 - 4 values into a vector. Include the co-ordinates
/// in the returned vector so that [`Grid::get_basin`] can recursively expand the set of cells in the basin.
pub fn get_all_surrounds(&self, y: usize, x: usize) -> Vec<((usize, usize), u8)> {
[
(-1, -1),
(-1, 0),
(-1, 1),
(0, -1),
(0, 1),
(1, -1),
(1, 0),
(1, 1),
] // NW W SW N S NE E NW
.iter()
.flat_map(|&(dy, dx)| self.get_relative(y, x, dy, dx))
.collect()
}
/// This is the core logic to implement a single pass of the octopuses powering up required for both parts. It
/// first iterates through all the cells incrementing them by one. Any that started at 9 are added to a queue of
/// cells that have triggered a flash. We then take cells off the to flash list, adding them to a set of all
/// co-ordinates that have flashed this iteration (so that we can 0 them later, and also ensure no cell flashes
/// twice). If the cell was new to the flashes set, it also increments its neighbours, adding any that exceed 9
/// to the trigger queue. Once the queue has been exhausted, we iterate through the resulting set of co-ordinates
/// that flashed this iteration, set them to 0 and return the size of the set, as this is the metric needed for
/// both parts' solutions.
fn iterate_and_flash(&mut self) -> usize {
let mut flashes: HashSet<(usize, usize)> = HashSet::new();
let mut to_flash: Vec<(usize, usize)> = Vec::new();
for i in 0..self.numbers.len() {
if let Some(((y, x), val)) = self.get_with_coords(i) {
self.set(y, x, val + 1);
if val == 9 {
to_flash.push((y, x));
}
}
}
while let Some((y, x)) = to_flash.pop() {
if !flashes.insert((y, x)) {
// already flashed
continue;
}
for ((y1, x1), val) in self.get_all_surrounds(y, x) {
self.set(y1, x1, val + 1);
if val == 9 {
to_flash.push((y1, x1))
}
}
}
for &(y, x) in &flashes {
self.set(y, x, 0);
}
flashes.len()
}
/// Solution to part one. Iterate the grid <cycles> times, summing the flashes this causes.
fn count_flashes(&mut self, cycles: usize) -> usize {
let mut total: usize = 0;
for _ in 0..cycles {
total = total + self.iterate_and_flash()
}
total
}
/// Solution to part two. Iterate the grid until the set of flashes is the same size as the grid, i.e. all cells
/// triggered a flash. Return the number of iterations required to reach that point.
fn run_until_sync(&mut self) -> usize {
let target = self.numbers.len();
let mut iteration: usize = 0;
loop {
iteration = iteration + 1;
if self.iterate_and_flash() == target {
return iteration;
}
}
}
}
/// The entry point for running the solutions with the 'real' puzzle input.
///
/// - The puzzle input is expected to be at `<project_root>/res/day-11-input`
/// - It is expected this will be called by [`super::main()`] when the user elects to run day 11.
pub fn run() {
let contents = fs::read_to_string("res/day-11-input").expect("Failed to read file");
let grid = Grid::from(contents);
let flashes = grid.clone().count_flashes(100);
println!("There were {} flashes in 100 cycles", flashes);
let iterations = grid.clone().run_until_sync();
println!(
"It took {} cycles for the flashes to synchronise.",
iterations
);
}
#[cfg(test)]
mod tests {
use crate::util::grid::Grid;
use std::collections::HashSet;
#[test]
fn can_update_grid() {
let mut grid = Grid::from(
"11111
19991
19191
19991
11111"
.to_string(),
);
let expected = Grid::from(
"21111
19991
19291
19991
11111"
.to_string(),
);
grid.set(0, 0, 2);
grid.set(2, 2, 2);
assert_eq!(grid, expected);
}
#[test]
fn can_get_all_surrounds() {
let grid = Grid::from("123\n456\n789".to_string());
let surrounds: HashSet<u8> = grid
.get_all_surrounds(1, 1)
.iter()
.map(|&(_, v)| v)
.collect();
assert_eq!(surrounds.len(), 8);
assert!(!surrounds.contains(&5))
}
#[test]
fn can_iterate_and_flash() {
let mut grid = Grid::from(
"11111
19991
19191
19991
11111"
.to_string(),
);
let expected = Grid::from(
"34543
40004
50005
40004
34543"
.to_string(),
);
let flashes = grid.iterate_and_flash();
assert_eq!(flashes, 9);
assert_eq!(grid, expected);
}
#[test]
fn can_count_flashes() {
let grid = Grid::from(
"5483143223
2745854711
5264556173
6141336146
6357385478
4167524645
2176841721
6882881134
4846848554
5283751526"
.to_string(),
);
assert_eq!(grid.clone().count_flashes(10), 204);
assert_eq!(grid.clone().count_flashes(100), 1656);
}
#[test]
fn can_run_until_sync() {
let mut grid = Grid::from(
"5483143223
2745854711
5264556173
6141336146
6357385478
4167524645
2176841721
6882881134
4846848554
5283751526"
.to_string(),
);
assert_eq!(grid.run_until_sync(), 195);
}
}
