Day 1: Trebuchet?!

My first ever Advent of Code challenge!
Completed in ~2 hours, 49 minutes.
14,553สณแตˆ worldwide.
2023-12-01

Something is wrong with global snow production, and you've been selected to take a look. The Elves have even given you a map; on it, they've used stars to mark the top fifty locations that are likely to be having problems.

You've been doing this long enough to know that to restore snow operations, you need to check all fifty stars by December 25th.

Collect stars by solving puzzles. Two puzzles will be made available on each day in the Advent calendar; the second puzzle is unlocked when you complete the first. Each puzzle grants one star. Good luck!

You try to ask why they can't just use a weather machine ("not powerful enough") and where they're even sending you ("the sky") and why your map looks mostly blank ("you sure ask a lot of questions") and hang on did you just say the sky ("of course, where do you think snow comes from") when you realize that the Elves are already loading you into a trebuchet ("please hold still, we need to strap you in").

As they're making the final adjustments, they discover that their calibration document (your puzzle input) has been amended by a very young Elf who was apparently just excited to show off her art skills. Consequently, the Elves are having trouble reading the values on the document.

The newly-improved calibration document consists of lines of text; each line originally contained a specific calibration value that the Elves now need to recover. On each line, the calibration value can be found by combining the first digit and the last digit (in that order) to form a single two-digit number.

For example:

1
2
3
4
1abc2 pqr3stu8vwx a1b2c3d4e5f treb7uchet

In this example, the calibration values of these four lines are 12, 38, 15, and 77. Adding these together produces 142.

Consider your entire calibration document.What is the sum of all of the calibration values?

  1. Remove all non-numeric characters from the line
  2. Combine the first and last numeric characters for that line and cast to an integer
  3. Add the result to a running total
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
from pathlib import Path import pytest def runner(document: list[str]) -> int: total = 0 for line in document: # Remove all non-numeric characters from the string numerics = [character for character in line if character.isnumeric()] # Combine first and last digits, add to total total += int(f"{numerics[0]}{numerics[-1]}") return total @pytest.mark.parametrize( "filename,total", [ ("example-1.txt", 142), ("example-3.txt", 54338), ], ) def test_runner(filename: str, total: int) -> None: with open(Path(__file__).with_name(filename)) as file: result = runner(file.read().splitlines()) assert result == total

Answer: 54,338

Your calculation isn't quite right. It looks like some of the digits are actually spelled out with letters:one, two, three, four, five, six, seven, eight, and nine also count as valid "digits".

Equipped with this new information, you now need to find the real first and last digit on each line. For example:

1
2
3
4
5
6
7
two1nine eightwothree abcone2threexyz xtwone3four 4nineeightseven2 zoneight234 7pqrstsixteen

In this example, the calibration values are 29, 83, 13, 24, 42, 14, and 76. Adding these together produces 281.

What is the sum of all of the calibration values?

The solution for Part 2 builds off of Part 1, but breaks a few assumptions.

  1. A "valid digit" can correspond to any number
  2. The set of "valid digits" isn't limited to characters of numbers 1-9
  3. A "valid digit" isn't limited to one character long

That's pretty much it. For an example of breaking these assumptions, let's look at the "valid digit" of three.

  1. three corresponds to a calibration score of 3
  2. three isn't in this set of characters: 1, 2, 3, 4, 5, 6, 7, 8, 9
  3. three is 5 characters long

With that in mind, we need to...

  1. Enable a mapping from "valid digits" to their calibration score
  2. Enable substring index searching/comparisons, starting from both the left and right sides of the string
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
import functools from pathlib import Path import pytest VALID_DIGIT_TO_NUM: dict[str, int] = { "1": 1, "2": 2, "3": 3, "4": 4, "5": 5, "6": 6, "7": 7, "8": 8, "9": 9, "one": 1, "two": 2, "three": 3, "four": 4, "five": 5, "six": 6, "seven": 7, "eight": 8, "nine": 9, } VALID_DIGITS = VALID_DIGIT_TO_NUM.keys() def reduce_lfind(a: str, b: str, line: str) -> str: position_a = line.find(a) position_b = line.find(b) if position_a == -1: return b if position_b == -1: return a if position_a < position_b: return a return b def reduce_rfind(a: str, b: str, line: str) -> str: position_a = line.rfind(a) position_b = line.rfind(b) if position_a == -1: return b if position_b == -1: return a if position_a > position_b: return a return b def runner(document: list[str]) -> int: total = 0 for line in document: # Find the earliest "digit" first_digit = functools.reduce( lambda a, b: reduce_lfind(a, b, line), VALID_DIGITS ) last_digit = functools.reduce( lambda a, b: reduce_rfind(a, b, line), VALID_DIGITS ) first = VALID_DIGIT_TO_NUM[first_digit] last = VALID_DIGIT_TO_NUM[last_digit] # Combine first and last digits, add to total total += int(f"{first}{last}") return total @pytest.mark.parametrize( "filename,total", [ ("example-2.txt", 281), ("example-3.txt", 53389), ], ) def test_runner(filename: str, total: int) -> None: with open(Path(__file__).with_name(filename)) as file: result = runner(file.read().splitlines()) assert result == total

Answer: 53,389

DayPart 1 TimePart 1 RankPart 2 TimePart 2 Rank
102:00:2319,25202:49:2314,553

This took a LOT longer than expected, mostly because I was setting up the project and playing around with various config tools while doing so ๐Ÿ˜….

I also spent way too much time on a silly mistake. I made the reduce_rfind function first, copied that for the reduce_lfind function, and forgot to change the line.rfind calls to line.find. So I spent a bunch of time troubleshooting that ๐Ÿ™ƒ.

But overall, super fun! I'm sure tomorrow will go much smoother ๐Ÿ˜.