Clojurians Log v2

Lotta folks don't dig the cpu simulators; they've always been my favs, and it's much more interesting to me now that he's using it to drive other systems. The integration aspect is its own set of neat challenges that he wouldn't have been able to put in a single day previously. The downside I can see is that it makes catching up very linear; skipping days isn't as simple this year as it was in prior.

Yeah, I'd agree with you on the fun-aspect of integrating the sim with other systems. I only finally today got around to extracting the intcode "machine" into its own namespace and refactored my day 11 code to use the imported machine. Figure we've got at least 6 more days that'll use the machine, maybe more.

Day 11: https://github.com/transducer/adventofcode/blob/master/src/adventofcode/2019/day11.clj

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

how do you mean?

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.

nothing wrong with cpu simulator except too convoluted and verbose description of one, spread across 3 or 4 days, and like total of 15 pages of text. Even changes in requirements are not that bad comparing to this.

any part 2 ideas?

Definitely can't brute-force it. I ran out of memory on the second test data set (and I have 16Gb of physical memory). Gonna sleep on it and see if I can think of something in the morning.

my velocities keep blowing up for part 1

Guess the name of the task itself is known problem with existing solutions

https://en.m.wikipedia.org/wiki/N-body_problem

I just read reddit for hints today :opieop:

slow though:

p1 input   "Elapsed time: 35.301894 msecs"
p2 sample1 "Elapsed time: 2.732321 msecs"
p2 sample2 "Elapsed time: 293.312654 msecs"
p2 input   "Elapsed time: 11600.599702 msecs"

spoiler inside

oh?

not for me 🙂

total cycle can be predicted from cycles of each of the axes, which are much shorter. Think frequency of a wave which is a summary of sine waves with different frequencies

ah was almost there, needed to split by axis too

now some primw factor voodoo

am stuck example 1 works with my code exampen2 and my puzzle give way too high answers

another spoiler: it is not (* x y z)

you need to check when the whole x axis and vx isnrhe same for all moons

and you need some prime factor work indeed

bingo

main observation. The equations of motion in each axis are completely independent

interesting. Changing the moons from maps to records reduces the part 2 runtime from 40 to 30 seconds

Any other performance tips?

https://github.com/mpcjanssen/aoc2019/blob/master/day12.ipynb

You don't actually have to find the prime factorizations of each axis, just their lowest common multiple

which you can use Euclid's algorithm for - LCM(a,b) = a*b / GCD(a,b)

although I don't think that's the bottleneck - my solution for part2 runs in 680ms

Thats indeed not thw borrlenexk

It was a fun exercise though

how do check if you reached the initial state?

I just use = on a seq of [p, v] tuples

looking at your notebook, it's hard to read because of all the funky indentation

I've only played around with Clojure notebooks for a while before, but the Parinfer plugin was essential for keeping some grasp on the parens: https://github.com/jelmerderonde/jupyter-lab-parinfer

your dv-ax function is simply compare

my step is slow

i am doing this on my phone so indentation is not the best

ah, that explains it

your addp is (mapv + p1 p2)

30s on a phone with Clojurescript might not be that bad after all?

count on a lazy seq is slow?

count forces the elements of the seq to be realised

if I remove the xount

and add a doall, its much faster

did you use recur or iterate?

iterate

how do you know the number of steps?

iterate generates an infinite seq, I reduce over it and break using reduced when it cycles back around

Here's some of the relevant bits

(def input
  (parse "<x=14, y=9, z=14>
<x=9, y=11, z=6>
<x=-6, y=14, z=-4>
<x=4, y=-4, z=-3>"))
;; => ((14 9 14) (9 11 6) (-6 14 -4) (4 -4 -3))

(def test-input
  (parse "<x=-1, y=0, z=2>
<x=2, y=-10, z=-7>
<x=4, y=-8, z=8>
<x=3, y=5, z=-1>"))
;; => ((-1 0 2) (2 -10 -7) (4 -8 8(3 5 -1))


;; * Part 2
(defn axis-step
  [pvs]
  (map (fn [[p v]]
         (let [nv (+ v (reduce (fn [acc [p']]
                                 (+ acc (compare p' p)))
                         0 pvs))]
           [(+ p nv) nv]))
    pvs))

(defn axis-period
  [ps]
  (let [vs (repeat 0)
        pvs (map vector ps vs)]
    (reduce (fn [cnt x]
              (if (= pvs x)
                (reduced cnt)
                (inc cnt)))
      1 (next (iterate axis-step pvs)))))

(for [ps (apply map vector test-input)]
  (axis-period ps))
;; => (18 28 44)

(util/lcm 18 28 44)
;; => 2772


(apply util/lcm
  (for [ps (apply map vector input)]
    (axis-period ps)))
;; => 282399002133976

oww addp is just +

ah and reduce for the count

my phone is quite fast I am not much slower than the really fast solutions

oh yeah, I did not think to completely split the computation from for-all-axes-in-a-single-step into 1-axis-per-step

Finally one that required some puzzling 😃. I drew a graph of one of the moon coordinates that hinted towards a solution. https://gitlab.com/dmarjenburgh/adventofcode/blob/master/src/adventofcode/year_2019.clj#L277-314

I got part 2 to run In about 3 seconds: https://github.com/Average-user/adventofcode-clj-2019/blob/master/src/adventofcode_clj_2019/day12.clj

adventofcode-clj-2019.day12> (time (part-2))
"Elapsed time: 2809.105945 msecs"
324618307124784

I am working on Day 11 part 2 and I keep getting a weird drawing. Looks like a rabbit. I already set the first panel to white as per the instructions but still no actual word.

Hmm. I'd ask if there's something wrong with your turning implementation, but Part 1 should have rooted that out.

This would be my turning function

(defn move-bot
  [[face [x y]] outputs]
  (let [[_ turn] outputs]
    (if (empty? outputs)
      (do (println "OUTPUTS EMPTY standing still")
          [face [x y]])
      (case face
        :north (if (= turn 0)
                 [:west [(dec x) y]]
                 [:east [(inc x) y]])
        :south (if (= turn 0)
                 [:east [(inc x) y]]
                 [:west [(dec x) y]])
        :west (if (= turn 0)
                [:south [x (dec y)]]
                [:north [x (inc y)]])
        :east (if (= turn 0)
                [:north [x (inc y)]]
                [:south [x (dec y)]])))))