An unofficial home for the advent of code community on programming.dev! Other challenges are also welcome!
Advent of Code is an annual Advent calendar of small programming puzzles for a variety of skill sets and skill levels that can be solved in any programming language you like.
Everybody Codes is another collection of programming puzzles with seasonal events.
Solution Threads
| M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | 6 | 7 |
| 8 | 9 | 10 | 11 | 12 |
Icon base by Lorc under CC BY 3.0 with modifications to add a gradient
console.log('Hello World')
In 16-bit real mode assembly, as a hybrid DOS .COM program and BIOS-bootable disk image. With bonus palette animations! I had the hybrid thing going on before (see the repo), but this is the first time getting something animated.
Repo | day07.com (12 KB) | full video
That's awesome, is it just random paths?
Well it uses the input of course but I found that if you make it truly random, the lines mostly go down in a straight line, all bunching up in the middle, which isn't very pleasing. So now the beams have a "current direction" which has a 25% of flipping at every splitter
I used a u8, one bit per level to do mine, but because not all bits correspond to a splitter, it ends up duplicating a lot of the paths. Which is why I made the lowest bit at the top, so it flip-flops a lot, giving the appearance of multiple different paths :D
If I understand correctly, your visualization shows up to to 256 unique paths then?
In this one, every time the beam passes a splitter, the other side is put on a queue, so eventually all possible paths are traced, breadth first. Initially I worked through the options recursively, but that depth-first filling out was boring to look at.
Yeah, max of 256 paths, and if there were no holes in the splitter layout, it would be the full 256. Also why i had to limit the depth to 16 layers, more than that and the brute forcing gets a bit silly.
If took more code to animate this than it did to solve the problem...
Looks very nice for the test data:
And...okay...for the live data:
I like the coloring, really cool!
Thanks, 'Tis the season.
Its very festive :)
That certainly doesn't reflect my mood today.
Thats cool! What are the colours meant to signify?
Christmas, I guess :) (I just pick a random colour each time a roll is removed)
Day 7 - Colourised, single image.
That's day 7, right?
Its all a blur...
Video of each path (for the short example, dont think i can do the long one) https://youtube.com/shorts/jLpiUOSIiNw
Colorised video: https://youtube.com/shorts/H_Fmf1rupGg
Colorised, but filling in from least photons to most: https://youtube.com/shorts/McM1yIn5UCw
Showing the of it filling in a bit clearer (or less clearer, i dunno): https://youtube.com/shorts/dBYAdRyhCLU
Apart from day 4 not much to visualise so far this year :/
Yeah, Im hoping it picks up. No mazes yet :(
Day 7 (zoom to full screen): https://lgbt.earth/i/web/post/903381501524320591
I can probably improve this a lot, but I was afraid I'll be too lazy after getting this far, so posting as is. Still, lmk if you have any suggestions :)
Day 8: https://youtu.be/QiezRG4jiUM
Getting pretty close to having written my own game renderer, only slower and worse :D
Squeezing all spaces out of the grid (and plotting at right-angles to the other visualisation here) gives this evil shape, which will doubtless haunt my dreams tonight.
Apparently this is ~~wrong. Not sure what I'm missing here.~~ correct, my code was borked I guess (maybe an overflow or something?).
First time I've seen a visualisation before solve :D
I took one look at pt2 and noped out, its a later problem I think...
Correction, turns out doing it entirely in Excel was the answer for me. The points I found were correct, but the area calculation in my code was wrong.
I had to visualize it before I could even attempt to solve it. Still did it mostly intuitively based on the visualization.
Ha, love an excel solution, please do share it in the solutions thread!