2020 Day 02

This commit is contained in:
Akumatic 2020-12-02 12:09:46 +01:00
parent 888cdda140
commit 4ec62b1cdb
4 changed files with 1086 additions and 0 deletions

43
2020/02/README.md Normal file
View File

@ -0,0 +1,43 @@
# 2020 Day 2: Password Philosophy
Copyright (c) Eric Wastl
#### [Direct Link](https://adventofcode.com/2020/day/2)
## Part 1
Your flight departs in a few days from the coastal airport; the easiest way down to the coast from here is via [toboggan](https://en.wikipedia.org/wiki/Toboggan).
The shopkeeper at the North Pole Toboggan Rental Shop is having a bad day. "Something's wrong with our computers; we can't log in!" You ask if you can take a look.
Their password database seems to be a little corrupted: some of the passwords wouldn't have been allowed by the Official Toboggan Corporate Policy that was in effect when they were chosen.
To try to debug the problem, they have created a list (your puzzle input) of **passwords** (according to the corrupted database) and the **corporate policy when that password was set**.
For example, suppose you have the following list:
```
1-3 a: abcde
1-3 b: cdefg
2-9 c: ccccccccc
```
Each line gives the password policy and then the password. The password policy indicates the lowest and highest number of times a given letter must appear for the password to be valid. For example, `1-3 a` means that the password must contain `a` at least `1` time and at most `3` times.
In the above example, **`2`** passwords are valid. The middle password, `cdefg`, is not; it contains no instances of `b`, but needs at least `1`. The first and third passwords are valid: they contain one `a` or nine `c`, both within the limits of their respective policies.
**How many passwords are valid** according to their policies?
## Part 2
While it appears you validated the passwords correctly, they don't seem to be what the Official Toboggan Corporate Authentication System is expecting.
The shopkeeper suddenly realizes that he just accidentally explained the password policy rules from his old job at the sled rental place down the street! The Official Toboggan Corporate Policy actually works a little differently.
Each policy actually describes two **positions in the password**, where `1` means the first character, `2` means the second character, and so on. (Be careful; Toboggan Corporate Policies have no concept of "index zero"!) **Exactly one of these positions** must contain the given letter. Other occurrences of the letter are irrelevant for the purposes of policy enforcement.
Given the same example list from above:
- `1-3 a: abcde` is **valid**: position 1 contains a and position 3 does not.
- `1-3 b: cdefg` is **invalid**: neither position 1 nor position 3 contains b.
- `2-9 c: ccccccccc` is **invalid**: both position 2 and position 9 contain c.
**How many passwords are valid** according to the new interpretation of the policies?

41
2020/02/code.py Normal file
View File

@ -0,0 +1,41 @@
# SPDX-License-Identifier: MIT
# Copyright (c) 2020 Akumatic
""" https://adventofcode.com/2020/day/2 """
def readFile() -> list:
input = list()
with open(f"{__file__.rstrip('code.py')}input.txt", "r") as f:
for line in f.readlines():
txt = line.split()
nums = txt[0].split("-")
input.append((int(nums[0]), int(nums[1]), txt[1][:1], txt[2]))
return input
def part1(vals: list) -> int:
cnt = 0
for val in vals:
min, max, char, text = val # for better readability
char_cnt = text.count(char)
if char_cnt >= min and char_cnt <= max:
cnt += 1
return cnt
def part2(vals: list) -> int:
cnt = 0
for val in vals:
pos_a, pos_b, char, text = val # for better readability
if (char == text[pos_a - 1]) ^ (char == text[pos_b - 1]):
cnt += 1
return cnt
def test():
test_input = [(1, 3, "a", "abcde"),
(1, 3, "b", "cdefg"), (2, 9, "c", "ccccccccc")]
assert part1(test_input) == 2
assert part2(test_input) == 1
if __name__ == "__main__":
test()
vals = readFile()
print(f"Part 1: {part1(vals)}")
print(f"Part 2: {part2(vals)}")

1000
2020/02/input.txt Normal file

File diff suppressed because it is too large Load Diff

2
2020/02/solution.txt Normal file
View File

@ -0,0 +1,2 @@
Part 1: 600
Part 2: 245