ex-Jane Street (pre-SBF)
ex-Google (pre-Sundar)
occasional shitpoaster
I guess there were clues. Solving it the right way is NP-hard, but I thought a bin packing heuristic was worth trying -- which did work, just was a billion times slower.
I guess there were clues. Solving it the right way is NP-hard, but I thought a bin packing heuristic was worth trying -- which did work, just was a billion times slower.
My vibe of AOC is that it shouldn't take these big guns to solve the problems but hey maybe they shouldn't take 5 minutes of naive CPU brute forcing either :P
My vibe of AOC is that it shouldn't take these big guns to solve the problems but hey maybe they shouldn't take 5 minutes of naive CPU brute forcing either :P
tried switching to BFS for part 2 and that solved some problems but not all. some have way too huge a search space
this has the shape of a linear algebra problem but I can't quite make the conceptual leap 🤔
tried switching to BFS for part 2 and that solved some problems but not all. some have way too huge a search space
this has the shape of a linear algebra problem but I can't quite make the conceptual leap 🤔
for each candidate rect from p1, walk the perimeter formed by the coordinates given in the input file. reject the rectangle if we step inside of it. it takes 54s of cpu (😱) but it works!
for each candidate rect from p1, walk the perimeter formed by the coordinates given in the input file. reject the rectangle if we step inside of it. it takes 54s of cpu (😱) but it works!
99% of the time is now spent sorting 1000² pairs by distance and that seems fine
99% of the time is now spent sorting 1000² pairs by distance and that seems fine