This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-12-15
Channels
- # adventofcode (39)
- # aws (1)
- # beginners (39)
- # boot (1)
- # calva (79)
- # cider (8)
- # cljdoc (13)
- # cljs-dev (45)
- # clojure (89)
- # clojure-berlin (2)
- # clojure-europe (1)
- # clojure-uk (1)
- # clojurescript (7)
- # datomic (1)
- # emacs (6)
- # figwheel-main (2)
- # fulcro (29)
- # hyperfiddle (21)
- # juxt (1)
- # leiningen (1)
- # lumo (3)
- # music (1)
- # off-topic (20)
- # pedestal (23)
- # portkey (3)
- # reagent (2)
- # rum (1)
- # shadow-cljs (27)
- # vim (5)
https://github.com/taylorwood/advent-of-code/blob/master/src/advent_of_code/2018/14.clj
Day 14: https://github.com/mfikes/advent-of-code/blob/master/src/advent_2018/day_14.cljc
I havent had time to do day 14 and day 15 is coming
I just looked at Day 15. It feels like CS homework. āImplement an A* algorithm.ā Not really fun
reminds me of a http://codingame.com competition but less fun
I think itās a fun problem, but thereās really too much going on here to finish quickly. Iām 2 hours in and Iām not quite getting the move selection right. I think I need finish in the morning.
It would have been more fun if the explanation was less explicit and the actual algorithm a bit more easy. Still it's doable, so I'll will.
Just looked at the times for the first 100 to get it right, around 15 minutes for almost any day, but today over 2 hours
My brain is fried. I have a solution but it works really slow for bigger dungeons. I suspect one line of code to be the culprit for making it so slow. Does anyone have the time to check this with me?
(filter (sets/union free enemies)) This is the line of code I suspect will cause trouble for large sets āfreeā. āenemiesā is usually small.
oh. and sets is (:require [clojure.set :as sets])
I tried out tufte yesterday and it seems easy to use out of the box for profiling.
https://github.com/ptaoussanis/tufte
Wrap the code you want to profile in the p macro and you should be able to see what's hogging the most time.
thanks
wow, it's almost 10 hours after the game and then only 835 people solved it completely, compared to the thousands from yesterday š
I just got the first part, almost the second but have to go, was the first time I was one of the first thousand to solve the first
I've been doing it for about 4 hours, still bug fixing part 1. Grrr.
i finally finished day 15 and it's pretty rough and slow, but I'm definitly not eager to touch it any further... https://github.com/IamDrowsy/advent-of-cljc/blob/slow/src/aoc/y2018/d15/iamdrowsy.cljc
That problem will likely cost $1000 to solve, in terms of time. You could buy a new laptop.
meanwhile stuck on part 2 of day 13, Iāve looked at this over and over and canāt find the bugā¦ any help would be appreciated! https://gist.github.com/Solaxun/1b4b7ada84b936d43fbee04ede0062f4
Line 66, :locs should be :loc. If you have any collisions that should happen on the first tick they'll get missed.
I don't see anything else obviously wrong, so hopefully that's it.
When I'm debugging these problems, especially with a loop, I'll do a println of each loop parameter and run through the first ~5 iterations manually checking that everything looks right. Usually I'll use the small sample data set from the problem description too. Would have caught this typo.
Glad I could help you fix it!
Thanks for the help ā¦ yeah belive it or not i did do several runs with the sample input
I mean print c, cs, full? and new-cars inside your loop, to ensure you got the mechanics of the loop correct. Often mistakes will not manifest obviously in the intended output, but if you look directly at the internal implementation the problem will be more obvious.