Advent of Code 2024 – C# and Python (23 Part Series)
1 Advent of Code 24
2 Advent of Code 2024 – Day 1: Historian Hysteria
… 19 more parts…
3 Advent of Code 2024 – Day 2: Red-Nosed Reports
4 Advent of Code 2024 – Day 3: Mull it Over
5 Advent of Code 2024- Day 5: Print Queue
6 Advent of Code 2024: Day 6: Guard Gallivant
7 Advent of Code 2024 – Day7: Bridge Repair
8 Advent of Code 2024 – Day8: Resonant Collinearity
9 Advent of Code ’24 – Day9: Disk Fragmenter (Python)
10 Advent of Code ’24 – Day 10: Hoof It
11 Advent of Code 2024 – Day 11: Plutonian Pebbles
12 Advent of Code ’24 – Day 13 Claw Contraption
13 Advent of Code 2024: Day 12: Garden Groups
14 Advent of Code 2024 – Day 14 : Restroom Redoubt
15 Advent of Code 2024 – Day 15: Warehouse Woes
16 Advent of Code 2024: Day 16 – Reindeer Maze
17 Advent of Code 2024 – Day 17: Chronospatial Computer
18 Advent of Code 2024 – Day 18: Ram Run
19 Advent of Code 2024 – Day 19: Linen Layout
20 Advent of Code 2024 – Day 20: Race Condition
21 Advent of Code 2024 – Day 21: Keypad Conundrum
22 Advent of Code 2024 – Day 22: Monkey Market
23 Advent of Code 2024 – Day 23: LAN Party
Day 19: Linen Layout
Today’s challenge was a refreshing change from the usual 2D puzzles and Dijkstra’s algorithms. Here’s how I approached it:
Part 1
The goal was straightforward: check if the given towel arrangements can be created using the available towels.
What NOT to do:
Initially, I tried generating all possible towel combinations with itertools.combinations. It quickly became clear this wasn’t practical or efficient.
What worked:
Using recursion combined with a dictionary (memo) to cache already processed designs. This prevents redundant computations and makes the solution much more efficient.
How it works:
For each design, try matching the beginning with one of the towel patterns.
If there’s a match, strip the matched part and recurse on the remainder.
Use memo to cache results for designs we’ve already checked, avoiding duplicate work.
The recursive approach with memoization keeps the complexity manageable, even for larger inputs, and makes the solution run efficiently.
Part 2
The second part upped the ante: count the number of ways to make each towel design using the available patterns.
Key insight:
The count_arrangements function extends the recursive logic from Part 1, but now calculates all possible ways to construct a design.
For each matching towel, recurse on the remainder of the design.
Use another dictionary (memo_count) to cache results for previously solved subproblems.
Example:
If “brgr” can be constructed in 2 ways, we simply return 2 from the cache instead of recalculating it.
Optimisation:
Thanks to Part 1, we already know which designs are possible. We only calculate arrangements for those.
<span>for</span> <span>arrangement</span> <span>in</span> <span>arrangements</span><span>:</span><span>if</span> <span>arrangement</span> <span>in</span> <span>memo</span> <span>and</span> <span>memo</span><span>[</span><span>arrangement</span><span>]:</span><span>ways</span> <span>=</span> <span>count_arrangements</span><span>(</span><span>arrangement</span><span>,</span> <span>towels</span><span>,</span> <span>memo_count</span><span>)</span><span>total_arrangements</span> <span>+=</span> <span>ways</span><span>for</span> <span>arrangement</span> <span>in</span> <span>arrangements</span><span>:</span> <span>if</span> <span>arrangement</span> <span>in</span> <span>memo</span> <span>and</span> <span>memo</span><span>[</span><span>arrangement</span><span>]:</span> <span>ways</span> <span>=</span> <span>count_arrangements</span><span>(</span><span>arrangement</span><span>,</span> <span>towels</span><span>,</span> <span>memo_count</span><span>)</span> <span>total_arrangements</span> <span>+=</span> <span>ways</span>for arrangement in arrangements: if arrangement in memo and memo[arrangement]: ways = count_arrangements(arrangement, towels, memo_count) total_arrangements += ways
Enter fullscreen mode Exit fullscreen mode
By summing up all the valid ways, we get the final answer for Part 2, simple as that.
Like I say I found today’s challenge quite fun and was a nice change. I hope this article has helped for future challenges / coding.
As always feel free to give me a follow or reach out on Twitter
Advent of Code 2024 – C# and Python (23 Part Series)
1 Advent of Code 24
2 Advent of Code 2024 – Day 1: Historian Hysteria
… 19 more parts…
3 Advent of Code 2024 – Day 2: Red-Nosed Reports
4 Advent of Code 2024 – Day 3: Mull it Over
5 Advent of Code 2024- Day 5: Print Queue
6 Advent of Code 2024: Day 6: Guard Gallivant
7 Advent of Code 2024 – Day7: Bridge Repair
8 Advent of Code 2024 – Day8: Resonant Collinearity
9 Advent of Code ’24 – Day9: Disk Fragmenter (Python)
10 Advent of Code ’24 – Day 10: Hoof It
11 Advent of Code 2024 – Day 11: Plutonian Pebbles
12 Advent of Code ’24 – Day 13 Claw Contraption
13 Advent of Code 2024: Day 12: Garden Groups
14 Advent of Code 2024 – Day 14 : Restroom Redoubt
15 Advent of Code 2024 – Day 15: Warehouse Woes
16 Advent of Code 2024: Day 16 – Reindeer Maze
17 Advent of Code 2024 – Day 17: Chronospatial Computer
18 Advent of Code 2024 – Day 18: Ram Run
19 Advent of Code 2024 – Day 19: Linen Layout
20 Advent of Code 2024 – Day 20: Race Condition
21 Advent of Code 2024 – Day 21: Keypad Conundrum
22 Advent of Code 2024 – Day 22: Monkey Market
23 Advent of Code 2024 – Day 23: LAN Party
暂无评论内容