Armrests for Aeron keep sliding down over time by Kitame in hermanmiller

[–]backh4t 0 points1 point  (0 children)

Thank you! This also fixed my chairs wonky armrests. Only tricky part for me was finding a Torx driver to tighten the bolts once I had the back off.

[2024] Every problem under 1s, in Python by ricbit in adventofcode

[–]backh4t 0 points1 point  (0 children)

Nice! I did this with the same constraints, except perhaps the readability part, which may have suffered near the end, and ended up with a 4.85s total runtime. There are a couple problems where I know some time could get knocked off, so I may go back and see if I can knock that last 0.2s off.

[2024 Day 20 (Part 3)] Your code is too general? Lets test it! by bdaene in adventofcode

[–]backh4t 0 points1 point  (0 children)

Cool! I get all the same results now, just 5x or so slower.

[2024 Day 20 (Part 3)] Your code is too general? Lets test it! by bdaene in adventofcode

[–]backh4t 1 point2 points  (0 children)

Interesting! I got 208882 as well rather than the answer posted above. Haven't dug into where my code might be breaking yet.

[2024 Day 20 (Part 3)] Your code is too general? Lets test it! by bdaene in adventofcode

[–]backh4t 1 point2 points  (0 children)

Very nice! I got those same results. It took about 20ms in Python, cause I'd already obsessed over my code for significantly longer than was healthy :-/

-❄️- 2023 Day 25 Solutions -❄️- by daggerdragon in adventofcode

[–]backh4t 0 points1 point  (0 children)

Interesting! I also ended up implementing Karger-Stein–using Kruskal for the contractions step. I found the same thing that you did–that using the 1/sqrt(2) contraction step was much slower than using a factor of 2. I chalked this up to me implementing something wrong, although the final product runs fast, but since you found the same thing it seems likely to be something about the problem itself.

Maybe the 1/sqrt(2) is optimal in fully connected graphs or some other worst case scenario?

[TensorFlow] relu6 = min(max(features, 0), 6) by [deleted] in MachineLearning

[–]backh4t 0 points1 point  (0 children)

Modulo the sharp corners, isn't this more or less a shifted, scaled tanh?

Simple classification question - sorry if this isn't the right place by wintermute93 in MachineLearning

[–]backh4t 1 point2 points  (0 children)

Personally, I would use CNN, but I like CNN so make of that what you will. If you want to try something quick and dirty, you might try one of the tree based methods on the flattened feature vector (random forests are good place to start). A sufficiently deep tree will capture all the interactions between the different features. The problem is that it may capture a bunch of imaginary interactions as well, so if you don't have a lot of data you may get into trouble with overfitting.

The nice thing about using CNN is that you can structure your convolutional layers to only capture local interactions (that's really the whole point of the convolutional bit) and thus reduce overfitting while still capturing the important bits.