Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Solve Day 09 #15

Merged
merged 20 commits into from
Dec 10, 2020
Merged

Solve Day 09 #15

merged 20 commits into from
Dec 10, 2020

Conversation

manuphatak
Copy link
Owner

@manuphatak manuphatak commented Dec 9, 2020

Day 9: Encoding Error

With your neighbor happily enjoying their video game, you turn your attention to an open data port on the little screen in the seat in front of you.

Though the port is non-standard, you manage to connect it to your computer through the clever use of several paperclips. Upon connection, the port outputs a series of numbers (your puzzle input).

The data appears to be encrypted with the eXchange-Masking Addition System ( XMAS ) which, conveniently for you, is an old cypher with an important weakness.

XMAS starts by transmitting a preamble of 25 numbers. After that, each number you receive should be the sum of any two of the 25 immediately previous numbers. The two numbers will have different values, and there might be more than one such pair.

For example, suppose your preamble consists of the numbers 1 through 25 in a random order. To be valid, the next number must be the sum of two of those numbers:

  • 26 would be a valid next number, as it could be 1 plus 25 (or many other pairs, like 2 and 24 ).
  • 49 would be a valid next number, as it is the sum of 24 and 25 .
  • 100 would not be valid; no two of the previous 25 numbers sum to 100 .
  • 50 would also not be valid; although 25 appears in the previous 25 numbers, the two numbers in the pair must be different.

Suppose the 26th number is 45 , and the first number (no longer an option, as it is more than 25 numbers ago) was 20 . Now, for the next number to be valid, there needs to be some pair of numbers among 1 - 19 , 21 - 25 , or 45 that add up to it:

  • 26 would still be a valid next number, as 1 and 25 are still within the previous 25 numbers.
  • 65 would not be valid, as no two of the available numbers sum to it.
  • 64 and 66 would both be valid , as they are the result of 19+45 and 21+45 respectively.

Here is a larger example which only considers the previous 5 numbers (and has a preamble of length 5):

35
20
15
25
47
40
62
55
65
95
102
117
150
182
127
219
299
277
309
576

In this example, after the 5-number preamble, almost every number is the sum of two of the previous 5 numbers; the only number that does not follow this rule is 127 .

The first step of attacking the weakness in the XMAS data is to find the first number in the list (after the preamble) which is not the sum of two of the 25 numbers before it. What is the first number that does not have this property?

Part Two

The final step in breaking the XMAS encryption relies on the invalid number you just found: you must find a contiguous set of at least two numbers in your list which sum to the invalid number from step 1.

Again consider the above example:

35
20
15
25
47
40
62
55
65
95
102
117
150
182
127
219
299
277
309
576

In this list, adding up all of the numbers from 15 through 40 produces the invalid number from step 1, 127 . (Of course, the contiguous set of numbers in your actual list might be much longer.)

To find the encryption weakness , add together the smallest and largest number in this contiguous range; in this example, these are 15 and 47 , producing 62 .

What is the encryption weakness in your XMAS-encrypted list of numbers?

Link

https://adventofcode.com/2020/day/9

@codecov
Copy link

codecov bot commented Dec 9, 2020

Codecov Report

Merging #15 (c664aa8) into main (24ab5a9) will decrease coverage by 0.82%.
The diff coverage is 88.88%.

Impacted file tree graph

@@            Coverage Diff             @@
##             main      #15      +/-   ##
==========================================
- Coverage   95.89%   95.06%   -0.83%     
==========================================
  Files          12       14       +2     
  Lines         146      162      +16     
  Branches        9       13       +4     
==========================================
+ Hits          140      154      +14     
- Misses          3        4       +1     
- Partials        3        4       +1     
Impacted Files Coverage Δ
src/Day01/Solution.hs 100.00% <ø> (ø)
src/Day09/Solution.hs 81.81% <81.81%> (ø)
src/Advent/Utils.hs 100.00% <100.00%> (ø)
src/Day09/Utils.hs 100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 24ab5a9...c664aa8. Read the comment docs.

@manuphatak manuphatak changed the base branch from main to day_09_repo_improvements December 9, 2020 18:38
@manuphatak manuphatak self-assigned this Dec 9, 2020
Base automatically changed from day_09_repo_improvements to main December 9, 2020 19:07
* origin/main:
  Fix lint checks and type checks on CI (#16)
@manuphatak manuphatak merged commit cb38e4d into main Dec 10, 2020
@manuphatak manuphatak deleted the day_09 branch December 10, 2020 03:41
manuphatak added a commit that referenced this pull request Dec 10, 2020
* origin/main:
  Solve Day 09 (#15)
  Fix lint checks and type checks on CI (#16)
  Solve Day 08 (#13)
@manuphatak manuphatak added the solution A solution to a problem label Dec 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
solution A solution to a problem
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant