Fork me on GitHub
#adventofcode
<
2019-12-11
>
erwinrooijakkers02:12:03

Rough night after Ajax and a few beers

meikemertsch07:12:29

what did you write it on? πŸ˜‰

lucaspolymeris02:12:39

Those are the answers to my input too

fellshard06:12:49

More intcode fusion fun!

lucaspolymeris06:12:25

https://github.com/Average-user/adventofcode-clj-2019/blob/master/src/adventofcode_clj_2019/day11.clj Until today I just used day5 code, modify it a little and so on, but I've decided to make intcode.clj its own file ...

lucaspolymeris06:12:46

I'll do it tomorrow though

fellshard07:12:36

Yeah, especially since he calls it 'complete' now

misha07:12:51

even fewer reasons to touch that sht again kappa

misha07:12:35

just require day05 :as cpu

fellshard07:12:12

Add a couple of helper fns for extracting outputs and injecting inputs; honestly, may be worth converting fully to core.async

namenu08:12:37

yeah, it's about time to break purity of intcode functions (maybe with core.async)

lucaspolymeris03:12:52

> Yeah, especially since he calls it 'complete' now

lucaspolymeris03:12:56

how do you mean?

fellshard04:12:16

The beginning of 9-2, in highlights: > You now have a complete Intcode computer. So the relative base + mode + instruction were the last pieces. From here on out, I expect if the Intcode computer is used, it'll be composed with some other system, e.g. the amplifiers and paintbot we've already seen.

regen09:12:46

if I hear "intcode" one more time this december santa is gonna pay

roman01la09:12:20

loooool πŸ˜€

mpcjanssen09:12:42

my part 2 text makes no sense

mpcjanssen09:12:40

ah partition count error

mpcjanssen10:12:28

still a bit magical to see the asciiart appear

mpcjanssen10:12:55

cant wait to see the quill version from @fellshard

mpcjanssen10:12:18

talk about synchronisity. Currently reading the joy of clojure. Just read: > To demonstrate this, let's build a robot object that has functions for moving it around a grid based on its current position and bearing.

dmarjenburgh10:12:56

Kind of hard to keep up with AoC on vacation simple_smile . I can’t be bothered to refactor my code πŸ˜† . I’m happy my core.async intcode solution works with n inputs, m outputs is any order https://gitlab.com/dmarjenburgh/adventofcode/blob/master/src/adventofcode/year_2019.clj#L254-275

erwinrooijakkers21:12:20

Kind of hard to keep up with aoc during a work week πŸ˜‰

rjray18:12:36

Hmmm. I'm getting a "bad opcode" when I run part 1 on the real data, as it moves the PC (jumps) to a location whose value is not a valid opcode.

rjray19:12:42

Nvm. Found it, was a lurking error in my input opcode that just hadn't been triggered in a previous day.

regen20:12:02

I finally completed day 7 part 2 after finding out > All signals sent or received in this process will be between pairs of amplifiers except the very first signal and the very last signal. To start the process, a 0 signal is sent to amplifier A's input exactly once. didn't mean that the 0 signal should be sent before the phase signal πŸ˜ͺ

erwinrooijakkers22:12:47

Such awesome puzzles πŸ™‚