Run this notebook

Use Livebook to open this notebook and explore new ideas.

It is easy to get started, on your machine or the cloud.

Click below to open and run it in your Livebook at .

(or change your Livebook location)

# Advent of Code 2022: Day 6 ```elixir # Load the input, provided as a text file input = Path.join(__DIR__, "/06.input.txt") |> File.read!() ``` ## Tuning Trouble: Part One ([Source](https://adventofcode.com/2022/day/6)) The preparations are finally complete; you and the Elves leave camp on foot and begin to make your way toward the **star** fruit grove. As you move through the dense undergrowth, one of the Elves gives you a handheld **device**. He says that it has many fancy features, but the most important one to set up right now is the **communication system**. However, because he's heard you have [significant](https://adventofcode.com/2016/day/6) [experience](https://adventofcode.com/2016/day/25) [dealing](https://adventofcode.com/2019/day/7) [with](https://adventofcode.com/2019/day/9) [signal-based](https://adventofcode.com/2019/day/16) [systems](https://adventofcode.com/2021/day/25), he convinced the other Elves that it would be okay to give you their one malfunctioning device - surely you'll have no problem fixing it. As if inspired by comedic timing, the device emits a few colorful sparks. To be able to communicate with the Elves, the device needs to **lock on to their signal**. The signal is a series of seemingly-random characters that the device receives one at a time. To fix the communication system, you need to add a subroutine to the device that detects a **start-of-packet marker** in the datastream. In the protocol being used by the Elves, the start of a packet is indicated by a sequence of **four characters that are all different**. The device will send your subroutine a datastream buffer (your puzzle input); your subroutine needs to identify the first position where the four most recently received characters were all different. Specifically, it needs to report the number of characters from the beginning of the buffer to the end of the first such four-character marker. For example, suppose you receive the following datastream buffer: ``` mjqjpqmgbljsphdztnvjfqwrcgsmlb ``` After the first three characters (mjq) have been received, there haven't been enough characters received yet to find the marker. The first time a marker could occur is after the fourth character is received, making the most recent four characters mjqj. Because j is repeated, this isn't a marker. The first time a marker appears is after the **seventh** character arrives. Once it does, the last four characters received are jpqm, which are all different. In this case, your subroutine should report the value 7, because the first start-of-packet marker is complete after 7 characters have been processed. Here are a few more examples: * `bvwbjplbgvbhsrlpgdmjqwftvncz`: first marker after character **5** * `nppdvjthqldpwncqszvftbrmjlhg`: first marker after character **6** * `nznrnfrfntjfmvfwmzdfjlvtqnbhcprsg`: first marker after character **10** * `zcfzfwzzqfrljwzlrfnpqdbhtmscgvjw`: first marker after character **11** **How many characters need to be processed before the first start-of-packet marker is detected?** ## TuningTrouble module ```elixir defmodule TuningTrouble do def first_marker(data, skip, take) when skip + take > length(data), do: {skip + take, nil} def first_marker(data, skip, take) do idx = take - 1 packet = data |> Enum.slice(skip..(skip + idx)) is_marker = packet |> Enum.uniq() |> length == take if is_marker do {skip + take, Enum.join(packet)} else first_marker(data, skip + 1, take) end end end ``` ```elixir test_data = String.codepoints("mjqjpqmgbljsphdztnvjfqwrcgsmlb") start_of_packet_size = 4 test_data |> TuningTrouble.first_marker(0, start_of_packet_size) # {7, "jpqm"} ``` ## Part One: Answer ```elixir data = String.codepoints(input) start_of_packet_size = 4 data |> TuningTrouble.first_marker(0, start_of_packet_size) # {1647, "dsjt"} ``` ## Tuning Trouble: Part Two Your device's communication system is correctly detecting packets, but still isn't working. It looks like it also needs to look for **messages**. A **start-of-message marker** is just like a start-of-packet marker, except it consists of **14 distinct characters** rather than 4. Here are the first positions of start-of-message markers for all of the above examples: * `mjqjpqmgbljsphdztnvjfqwrcgsmlb`: first marker after character 19 * `bvwbjplbgvbhsrlpgdmjqwftvncz`: first marker after character 23 * `nppdvjthqldpwncqszvftbrmjlhg`: first marker after character 23 * `nznrnfrfntjfmvfwmzdfjlvtqnbhcprsg`: first marker after character 29 * `zcfzfwzzqfrljwzlrfnpqdbhtmscgvjw`: first marker after character 26 **How many characters need to be processed before the first start-of-message marker is detected?** ```elixir test_data = String.codepoints("mjqjpqmgbljsphdztnvjfqwrcgsmlb") start_of_message_size = 14 test_data |> TuningTrouble.first_marker(0, start_of_message_size) # {19, "qmgbljsphdztnv"} ``` ## Part Two: Answer ```elixir data = String.codepoints(input) start_of_message_size = 14 data |> TuningTrouble.first_marker(0, start_of_message_size) # {2447, "lshwdrgjfbnptq"} ```
See source

Have you already installed Livebook?

If you already installed Livebook, you can configure the default Livebook location where you want to open notebooks.
Livebook up Checking status We can't reach this Livebook (but we saved your preference anyway)
Run notebook

Not yet? Install Livebook in just a minute

Livebook is open source, free, and ready to run anywhere.

Run on your machine

with Livebook Desktop

Run in the cloud

on select platforms

To run on Linux, Docker, embedded devices, or Elixir’s Mix, check our README.

PLATINUM SPONSORS
SPONSORS
Code navigation with go to definition of modules and functions Read More ×