You are reading a single comment by @Greenbank and its replies.
Click here to read the full conversation.
-
22 was a bit annoying. My first instinct was to add a negative block when there's an intersection (seemingly the fastest/simplest solution) but after I couldn't get it to work I convinced myself that splitting cubes would be easier. It was a pain.
Did not solve 23 part 2 before I had to travel home for Christmas but it was getting a solution (also Dijkstra), just giving me the wrong cost. I was hoping we'd done all the hard ones for the year so that was a nasty surprise
Today looks annoying as well
frankenbike
@Greenbank
Ha. Ran out of time. Day 23p2 my Dijkstra algorithm seems to be picking up nodes with lower tentative distances for some reason, lack the time to debug it. [EDIT - Fixed that but now it doesn't find a solution, plus it still takes too long. Something bigly amiss.]
Day24 looks equally hard given the top100 times and don't have any time today so I'll guess I'll leave the remaining challenges until after Christmas.
Then, at some point, I've got to redo them all in Go...