Day 2, slept in :-(

This commit is contained in:
Chris Hodges 2024-12-02 06:51:53 +01:00
parent 8f879f456e
commit 79797d8ea2

97
src/aoc2024/Day02.kt Normal file
View File

@ -0,0 +1,97 @@
package aoc2024
import println
import readInput
import splitInts
/*
--- Day 2: Red-Nosed Reports ---
Fortunately, the first location The Historians want to search isn't a long walk from the Chief Historian's office.
While the Red-Nosed Reindeer nuclear fusion/fission plant appears to contain no sign of the Chief Historian, the engineers there run up to you as soon as they see you. Apparently, they still talk about the time Rudolph was saved through molecular synthesis from a single electron.
They're quick to add that - since you're already here - they'd really appreciate your help analyzing some unusual data from the Red-Nosed reactor. You turn to check if The Historians are waiting for you, but they seem to have already divided into groups that are currently searching every corner of the facility. You offer to help with the unusual data.
The unusual data (your puzzle input) consists of many reports, one report per line. Each report is a list of numbers called levels that are separated by spaces. For example:
7 6 4 2 1
1 2 7 8 9
9 7 6 2 1
1 3 2 4 5
8 6 4 4 1
1 3 6 7 9
This example data contains six reports each containing five levels.
The engineers are trying to figure out which reports are safe. The Red-Nosed reactor safety systems can only tolerate levels that are either gradually increasing or gradually decreasing. So, a report only counts as safe if both of the following are true:
The levels are either all increasing or all decreasing.
Any two adjacent levels differ by at least one and at most three.
In the example above, the reports can be found safe or unsafe by checking those rules:
7 6 4 2 1: Safe because the levels are all decreasing by 1 or 2.
1 2 7 8 9: Unsafe because 2 7 is an increase of 5.
9 7 6 2 1: Unsafe because 6 2 is a decrease of 4.
1 3 2 4 5: Unsafe because 1 3 is increasing but 3 2 is decreasing.
8 6 4 4 1: Unsafe because 4 4 is neither an increase or a decrease.
1 3 6 7 9: Safe because the levels are all increasing by 1, 2, or 3.
So, in this example, 2 reports are safe.
Analyze the unusual data from the engineers. How many reports are safe?
*/
fun main() {
val inlineTestInput = """
7 6 4 2 1
1 2 7 8 9
9 7 6 2 1
1 3 2 4 5
8 6 4 4 1
1 3 6 7 9
"""
fun checkGood(i: List<Int>): Boolean {
val dir = i[1] - i[0]
return if (dir < 0) {
!i.runningReduce { acc, elem -> if ((elem < acc) and (elem >= acc - 3)) elem else Int.MIN_VALUE }.contains(Int.MIN_VALUE)
} else if (dir > 0) {
!i.runningReduce { acc, elem -> if ((elem > acc) && (elem <= acc + 3)) elem else Int.MAX_VALUE }.contains(Int.MAX_VALUE)
} else {
false
}
}
fun part1(input: List<String>): Int {
val ilist = input.map { it.splitInts() }
var sum = 0
for (i in ilist) {
if (checkGood(i)) sum++
}
return sum
}
fun part2(input: List<String>): Int {
val ilist = input.map { it.splitInts() }
var sum = 0
for (i in ilist) {
for (dp in ilist.indices) {
if (checkGood(i.filterIndexed { index, _ -> dp != index })) {
sum++
break
}
}
}
return sum
}
// test if implementation meets criteria from the description, like:
val testInput = inlineTestInput.trim().reader().readLines()
//val testInput = readInput("aoc2024/Day02_test")
val testInputPart1Result = part1(testInput)
println("Part 1 Test: $testInputPart1Result")
val testInputPart2Result = part2(testInput)
println("Part 2 Test: $testInputPart2Result")
check(testInputPart1Result == 2)
check(testInputPart2Result == 4)
val input = readInput("aoc2024/Day02")
part1(input).println()
part2(input).println()
}