Part 1 was easily solved by Dijkstras (using heapq).
Tricky part was to find the way to serialize the
queue items for the heappush and heappop to behave
as required.
Part 2 was incredible hard to figure out, and I
could not do it by myself. From the subreddit, it
is hinted that a traditional set of visited nodes
to determine algorithm exit would not work.
After some laboration and readin some hints, I
managed to find a solution where the code keeps
tracks using a defaultdict.
After working overtime to solve day 12, this brief
task was a much welcome change.
For pt 1, the code uses integer division and
modulus to update all positions. The tricky part
was to determine which quadrant got the middle
column and row (since dimensions was odd numbers,
and either left or right quandrants is +1 longer),
which was straightforward to verify by the test
cases.
For pt 2, the remains of the code used to visually
identify the tree is left under the `find_easter_egg`
toggle.
Basically, the code prints the grid with
all robots marked as a `#`, and free space as `.`.`
This wording of the puzzle is important:
> very rarely, _most of the robots_ should arrange
> themselves into a picture of a Christmas tree.
"most of the robots" means the tree will be quite
visible, which also means it is safe to asume a
significant cluster of "#" would appear over time.
By keeping track of the counter (seconds the robots
has traveled), it was evident that the cluster of `#`
occoured th first time at i=64 and every 103th
time forward.
In other words, `i % 103 == 64` will most likely
give a tree. The print statement is therefore
limited to those i's, and at `i == easter_egg_appearance`
the tree is visible.
So, to be extra clear: 64, 103 and pt2 answer is
unique to my puzzle input. If this code is used
with any other puzzle input, these numbers will
most likely vary.
For the fun, the code also contains the `display_easter_egg`
flag to actually print the tree. This is provided
to indicate how big the actual tree is: 33*36 chars.
Also, the `sints` utility function was added to
extract all signed ints from a string.
Funny that original 2023 day 5 also was a PITA
to figure out.
Pt 1 was solved using BFS to flood-fill. After
trying some different methods for pt 2, including:
- wallcrawling,
- side couting,
- corner counting
I never produced code to get past the test cases.
- Wall crawling are hard due to overlapping
regions.
- corner couting and side counting are both hard,
but will act as equally good solutions (since side
count equals corner count).
- Concave corners are hard, convex corners are
easy.
The final code is based on the posts on the
solutions megathread. Changes:
- Keep all areas in a set, defining a region.
- find all convex and concave corners in each
region.
A new helper got introduced: Di, storing all
diagonal neighbors for grid traversing.
Convex corners:
.. R. .R ..
R. .. .. .R
Concave corners:
RR .R R. RR
.R RR RR R.
Initial version of the code tried to solve pt 1
using BFS, which took way too long even for the
test data.
After some fiddling with algebra with pen and paper,
I realized this 2 formulaes (using first example):
94 * b1 + 22 * b2 == 840
34 * b1 + 67 * b2 == 540
*b1 = button A presses
*b2 = button B presses
... could be rewritten to this single expression:
(94 + 34) * b1 + (22 + 67) * b2 = 840 * 540
I failed to remember the algebra for solving x than
y though, that I had to learn from the subreddit.
In the code, this is the ratio part.
Also, this solution using fractions is SICK.
https://www.reddit.com/r/adventofcode/comments/1hd4wda/comment/m1tz3nf/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button
Loooong time overdue. First drafts of the code
kept track of every id separately in a defaultdict.
This was not sustainable since the code examples
had some recurring ids, and after managing to
support the test cases the code was eay off for
the real puzzle input.
In the end, the whole code was deleted and replaced
by a BFS solution that expands the current regions
until it finds no more areas.
Got the trick to count all perimiters in an else clause
from a leaderboard placed youtuber.
First part was solved using a list to store stones,
since I misinterpreted this paragraph:
> No matter how the stones change, their order is
> preserved, and they stay on their perfectly
> straight line.
But since the puzzle question do not require the
stones in the correct order, a list (or an OrderedDict)
is not required.
The pt 1 solution code got killed for eating all
RAM, so valuable minutes was lost trying to create
a generator instead. It failed. When searching for
clues, I ran across multiple people instead
utilizing dicts to count occourences. "but what of
the order?", I asked, and realized only the counts
was relevant.
Hard one. Comparing to earlier years, the
difficulty level seems higher than usual. I blame
the LLM hipsters.
This one I asumed, but missed when I tried to
find it:
> "If a block contains free space, skip it instead."
Lucky me.
As many have said, the puzzle text this day
was a bit challenging to parse and understand.
Especially this part of pt 2 was easy to miss:
> In fact, the three T-frequency *antennas* are all
> exactly in line with two antennas,
> so *they are all also antinodes*!
not including the antennas in pt 2 gave an slightly
too low answer.
Got thrown of big time at pt 1 since there is a
duplicate test value in my puzzle input. The code
initially asumed that all test values should be
distinct. Biased from seeing "test" in the
termology, most likely.
Earlier editions of the code also tried to create
all combinations using binary strings, but it fell
short on pt 2 when a third operation was introduced.
From some inspiration in the solutions mega
thread on Reddit, the final code is queue-based
instead. Apparently, I also learned this kind of
problem is usually well suited for DFS search, and
apparently the final code very much is _in deed_
a DFS.
Pt 1 was easy, Pt 2 was pure horror.
Earlier drafts of the code tried to be way too
smart. At one point, I just came to the conclusion
to place a new obstacle (#) on the grid and just
rerun the thing to look for loops.
2 things:
- the visited positions from pt 1 can be used as a
subset for positions to consider for the extra
"#".
- The track of loops can be optimized to look at
bounces on "#"s instead of each individual y,x pos,
given that the direction is remembered.
pt 2 is familiar, the last time a puzzle required
look detection the puzzle used lazer beams and
reflectors. Not sure what Event or day it was.
In p2, it took some tries to find a correct way
to rearrange incorrect pagesets. The code ended
up just rearranging first found incorrect order
and readding the updated pageset to queue.
Felt paranoid on this one, was expecting something
much worse for pt2.
The code that solved the puzzle was _extremely_
naive:
- It asumes puzzle input only contains mul() with
1-3 chars. The versioned code have `{1,3}` as safe
guard.
- p2 asumed initial chunk does not begin with
"n't". Would have been easy to handle though.
- p2 asumed junk strings as "don", "do", "don()t"
would not exist.
In other words, I was really lucky since I did not
look that closely on puzzle input beforehand.
Might have cut 60-90 seconds further if I had just
ran pt2 immidately instead of staring dumbly on the
test data (that changed for pt2).
Also, I got reminded that \d in regular expressions
is equal to `0-9`: it does not include commas and
punctations. The code that solved the puzzle was
paranoid and instead used `0-9`.
Managed to score ~1500th somehow despite this.
DDOS of adventofcode.com, did not get to open the
puzzle until 06:05 (five minutes local time).
Screwed up the zip() and lost valuable minutes by
trying to replace it with itertools, only to find
I have made a typo (did AB CD EF instead of AB BC
CD).
I also lost valuable minutes by tring to solve p1
with one nested loop. Stupid.
For part 2, I created the issafe() helper to be
able to remove items from reports and test, one
at the time.
Realized afterwards I got the ints() helper, so
original code before cleanup splitted the input and
mapped all words with int(). valuable seconds lost
there.
Also, collections.Counter() was used initially since
I was too tired to remember count() method in lists.
Line 8 took the longest time to figure out. A typo
took 1-3 minutes to find for part 2.
Form: Sleep deprived, felt slow.
Solved by hand by visualizing the filesystem as
a grid, and put into a simple formula.
In Sweden, this is called a "Femtonspel".
https://sv.wikipedia.org/wiki/Femtonspel
Did brute force, but earlier drafts of the code
failed to exit the while loop correcly.
By manual testing, an odd number is required in reg
a to set the first output to 0 (for my puzzle
input at least). Hence, only odd numbers are tested.
Solution cide works, but is slow. According to the
subreddit, pt 2 is meant to be an exercise in
optimization.
Turns out the assembly instructions do a factorial,
i.e 7! and 12! and adds a salt (5840).
Got that spoiled. :)
A good day to utilize lots of unit testing!
For pt 2, the code initially tried to reverse
the scramble algorithm. The final code however
got the unscrambled version by the traditional
method most password crackers would resolve to:
basic brute forcing with permutations as a list
of candidates.
The code at one time used cached responses for
in range bools, but it seems that does not improve
performance.
Some IP addresses are allowed multiple times, so
min() and set() are used to find the distinct
values.
Learned a lot about the Josephus' Problem today!
Solved part 1 by using a dict, but eventually
ended up just adding the mathematical shortcut
and rewriting both parts to use deque() for
performance.
Part 2 was tricky, since k (the elf to remove
after all presents were stolen from them) is a
index that changes over time. No tries for a
solution that was performant enough using lists
and dicts were succesfull, so by inspiration from
the subreddit the final solution code is based on
2 deque() that pops and appends between them.
There are 2 part 1 solutions.
- A correct implementation of the Josephus' Problem,
using deque(). Recursion would have worked as well,
but Python do not like recursions.
- The mathematical superior version, with a link
to the Youtube video were it is introduced.
Figured out that the center position did not matter,
as long as left hand side tile and right hand side
tile on previous row are not equal.
Also tried to find a recurring pattern to speed
p2 up a bit, but it seems it does not have a
recurring pattern in the 400 000s first rows.
Lost 60 minutes due to misinterpreting this in p2:
> *whenever* you generate a hash
The code initially only did the 2016 stretching for
the triplet hash, not the quintet hash. By doing it
to both, pt 2 is solved.
Not sure the lru cache actually speeds anything up.
Many on the subreddit used the approach to generate
the quintet first and look backwards 1000 times
for a matching quintet (since quintets are more
rare than triplets), this will most likely speed
things up.
Also, this solution do not store the found keys.
Many other solutions do, I believe this is some
presumptions.
Hard one, an infamous AoC puzzle according to
Reddit.
Apparently, this is a classic logic problem named
"Missionaries and cannibals", or "Jealous husbands".
Hard lessons:
- Always use set() for visited nodes during BFS.
- Always use collections.queue() to create to queue
traversals for BFS.
- itertools permutations(), combinations() and
pairwise() may look similar, but they are not.
- Learned to use (?:chunk of text)? in regex.
Test data was achieved without bigger hazzles, but
to optimize code required a lot of Reddit browsing
and code reading from blogs. I have mentioned the
sources in a doc string.
These are already done in Elixir, so this is
just done for the flex.
Also, coming from Day 16-18 from 2023 calendar,
it is safe to say 2015 puzzles are easier and more
manageable.
* Solve 2015:16 "Aunt Sue"
* Make 2023:08 future compatible
Code used to work with another version of python.
* Solve 2015:17 "No such Thing as Too much"
* Solve 2015:18 "Like a GIF For Your Yard"
Also solve 2015:06 just in case, was just a ref
in the end.
* Solve 2015:19 "Medicine for Rudolph"
* Solve 2015:20 "Infinite Elves and Infinite Houses"
* Solve 2023:21 "RPG Simulator 20XX"
* Solve 2015:22 "Wizard Simulator 20XX"
* Solve 2015:23 "Opening the Turing Lock"
* Solve 2015:25 "Let it Snow"
Wrote p2rc and rc2p just for academic purposes.
Puzzles could be solved anyway.
* Solve 2015:24 "Hangs in the Balance"
---------
Co-authored-by: Anders Englöf Ytterström <anders@playmaker.ai>
* Prep Advent of Code 2023
* Solve 2023:01 "Trebuchet?!"
Turns out re methods are non-overlapping. And in
true AoC manners, no provided test cases had
overlaps.
Luckily for me, some of the last lines in the input
contained the string "oneight", so I was able to
find it out quite fast.
Revisions:
1) Reverse strings to find last digit
2) Use isdigit() and skip regex.
3) Use regexp with positive look-ahead.
* Solve 2023:02 "Cube Conundrum"
Very intermediate pythonic solution,
regex would have made the code more compact.
But since 2023:01 decreased the regex courage,
This code will do.
* Solve 2023:03 "Gear Ratios"
Overslept, took about 55 mins.
* Solve 2023:04 "Scratchcards"
On a train that according to swedish tradition
was late. Not a good environment to focus.
Got stuck 2 times:
- Initial code asumed the | was always after the 5th
number, because of the example. Puzzle input had
it at pos 10. Classic AoC mistake.
- I had a hard time trying to understand the score
count, I insisted there was meant to be a +1 at
some point.
> That means card 1 is worth 8 points (1 for
> the first match, then doubled three times for
> each of the three matches after the first)
I should instead have just looked at the numbers.
* Solve 2023:05 "If You Give A Seed A Fertilizer"
Part 2 takes 66 minutes to run. There is some smart
things to realize here.
* Solve 2023:06 "Wait for it"
* Solve 2023:07 "Camel Cards"
* Solve 2023:08 "Haunted Wasteland"
Part 2 would have taken 10-15 hours with brute force.
After I figured out the puzzle input had circular
A-Z paths, it was plain as day that LCM was the
solution to the problem.
https://en.wikipedia.org/wiki/Least_common_multiple
* Solve 2023:09 "Mirage Maintenance"
* Remove parse_input helper
* Refactor 2023:05
Increasing speed from 66mins to 4mins. Caching the
location value in the code to keep things at highest
speed.
From the subreddit, the algorithm looks like this.
1. Start att location 0
2. Traverse the whole process backwards, by
reversing process steps and flipping dest/src
positions.
3. Output is not a location, instead it's a seed.
4. if seed is in any seed range, use seed to get
location as in step 1.
5. If not, increase location by 1 and repeat 2-4.
* Solve 2023:10 "Pipe Maze"
Got completely stuck on part 2. Tried some polygon
area calculations, but none provided the correct
answer, most likely due to the unorthodox polygon
points.
I also tried _shoelace method_ without any luck.
Had not heard about that one earlier, it was a good
learning experience even though I vould not use it
here.
By the subreddit, several people had had luck
using the ray method.
> Part 2 using one of my favorite facts from
> graphics engineering: lets say you have an
> enclosed shape, and you want to color every
> pixel inside of it. How do you know if a given
> pixel is inside the shape or not? Well, it
> turns out: if you shoot a ray in any direction
> from the pixel and it crosses the boundary an
> _odd number_ of times, it's _inside_. if it crosses
> an even number of times, it's outside. Works
> for all enclosed shapes, even self-intersecting
> and non-convex ones.
* Fix flake8 errors for 2023:1-10
* Solve 2023:11 "Cosmic Expansion"
* Solve 2023:12 "Hot Springs"
* Solve 2023:13 "Point of Incidence"
* Solve 2023:14 "Parabolic Reflector Dish"
* Solve 2023:15 "Lens Library"
WALLOFTEXT for part 2, took me 90 minutes to find
this important text:
> Each step begins with a sequence of letters that
> indicate the label of the lens on which the step
> operates. The result of running the HASH algorithm
> on the label indicates the correct box for that
> step.
It also clarifies how part 2 and part 1 relates.
* Solve 2023:16 "The Floor Will Be Lava"
---------
Co-authored-by: Anders Englöf Ytterström <anders@playmaker.ai>
