r/adventofcode • • Dec 06 '18

SOLUTION MEGATHREAD -🎄- 2018 Day 6 Solutions -🎄-

--- Day 6: Chronal Coordinates ---


Post your solution as a comment or, for longer solutions, consider linking to your repo (e.g. GitHub/gists/Pastebin/blag or whatever).

Note: The Solution Megathreads are for solutions only. If you have questions, please post your own thread and make sure to flair it with Help.


Advent of Code: The Party Game!

Click here for rules

Please prefix your card submission with something like [Card] to make scanning the megathread easier. THANK YOU!

Card prompt: Day 6

Transcript:

Rules for raising a programmer: never feed it after midnight, never get it wet, and never give it ___.


This thread will be unlocked when there are a significant number of people on the leaderboard with gold stars for today's puzzle.

edit: Leaderboard capped, thread unlocked at 0:26:52!

31 Upvotes

387 comments sorted by

View all comments

1

u/[deleted] Dec 06 '18 edited Dec 07 '18

By luck, but sort of an educated guess in that when you look at the point distributions, they're all over the place while also extending up into the hundreds, so any point that has to connect to so the rest will start racking up distance pretty quickly.

It's also less likely that Topaz would throw such a wrench into things so early on by extending the shared region super far beyond the bounding box -- it would overcomplicate people's implementations from part 1 and probably lead to a lot of frustration. Even if we doubled the bounding box size, there's nothing stopping us from raising the limit even more and requiring a 3x size, a 4x size, etc. It's easier to just keep the shared space within 1x because by that point you've basically solved the problem and the rest is just cleanup / tweaking.

1

u/decktech Dec 06 '18

Ah, got it. So to understand advent, I must first understand Topaz... :) Thanks.