Spyke
lemmy.sdf.org

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

7
Strlcpy@1reply
lemmy.sdf.org

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

3
CameronDevreply
programming.dev

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

1
Strlcpy@1reply
lemmy.sdf.org

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.

2

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.

1
lemmy.world

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:

6

Christmas, I guess :) (I just pick a random colour each time a roll is removed)

2
lemmy.ca

Apparently this is wrong. Not sure what I'm missing here. correct, my code was borked I guess (maybe an overflow or something?).

4
CameronDevreply
programming.dev

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...

2
lemmy.ca

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.

2
hadesreply
programming.dev

Apart from day 4 not much to visualise so far this year :/

2

The graph of Day 11, created with very little effort using the dot utility of graphviz. Because of a stupid parsing error I ended up with a cyclic graph, so this visualization helped in debugging.

3

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.

3

I know I'm late, but I'd thought, I'd share some of my day 12 visualizations I wanted to see.

Here's my shapes with symmetries:

Here's some of the solutions found in a greedy manner:





The visuals are terminal based, for simple cells I used two spaces with colored background and for solutions I also used braille symbols to better delineate distinctions between cells.

2

I made a quick visualisation of my input for day 9 with matplotlib. Still haven't solved part 2 though.

2

You reached the end

Visualisations Mega Thread | Spyke