ruidy/ai_advent_code_2024
1
0
Fork 0
mirror of https://github.com/rjNemo/ai_advent_code_2024 synced 2026-06-06 02:26:44 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

docs: Update Day 2 README with clearer Part 2 challenge description

Browse source
This commit is contained in:
Ruidy (aider) 2024-12-02 08:21:59 +01:00 committed by Ruidy
parent 9cf6061dcd
commit bc2091cb79
No known key found for this signature in database
GPG key ID: E00F51288CB857CC
1 changed files with 18 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

32
lib/advent_code2024/solutions/day02/README.md
View file

@ -24,7 +24,7 @@ A report is considered safe if it meets both of these criteria:
1 3 6 7 9 # Safe (all increasing by 1-3) 1 3 6 7 9 # Safe (all increasing by 1-3)
``` ```
### Part 1 Challenge ## Part 1 Challenge
Count how many reports in the input data are safe according to the rules above. Count how many reports in the input data are safe according to the rules above.
@ -36,21 +36,25 @@ Each line contains space-separated integers representing the levels in a report.
In the example above, 2 reports are safe. In the example above, 2 reports are safe.
--- Part Two --- ## Part 2 Challenge
The engineers are surprised by the low number of safe reports until they realize they forgot to tell you about the Problem Dampener.
The Problem Dampener is a reactor-mounted module that lets the reactor safety systems tolerate a single bad level in what would otherwise be a safe report. It's like the bad level never happened! The engineers discovered they forgot to tell you about the Problem Dampener - a reactor
module that can tolerate a single bad level in a report. If removing any single level
from an unsafe report would make it safe according to the original rules, that report
should now be considered safe.
Now, the same rules apply as before, except if removing a single level from an unsafe report would make it safe, the report instead counts as safe. For example, in the same reports from Part 1:
More of the above example's reports are now safe: ```csv
7 6 4 2 1 # Safe (already safe, no removal needed)
1 2 7 8 9 # Still unsafe (no single removal helps)
9 7 6 2 1 # Still unsafe (no single removal helps)
1 3 2 4 5 # Now safe (removing 3 makes it safe)
8 6 4 4 1 # Now safe (removing one 4 makes it safe)
1 3 6 7 9 # Safe (already safe, no removal needed)
```
7 6 4 2 1: Safe without removing any level. With the Problem Dampener active, 4 reports are now considered safe instead of
1 2 7 8 9: Unsafe regardless of which level is removed. just 2.
9 7 6 2 1: Unsafe regardless of which level is removed.
1 3 2 4 5: Safe by removing the second level, 3.
8 6 4 4 1: Safe by removing the third level, 4.
1 3 6 7 9: Safe without removing any level.
Thanks to the Problem Dampener, 4 reports are actually safe!
Update your analysis by handling situations where the Problem Dampener can remove a single level from unsafe reports. How many reports are now safe? Count how many reports become safe when the Problem Dampener is active.