Live data from Hacker News

My Python code is a neural network

blog.gabornyeki.com

71–75 of 75 posts

Re: My Python code is a neural network

#71
post #69

Earlier quoted context omitted.

None of the students who have taken the classes I TA pass w/I learning about RNNs.

Is that true also of LSTMs?

Yes. We cover Jordan and Elman RNN, LSTMs, and GRUs. Assignments only really test for LSTM knowledge, though.

Re: My Python code is a neural network

#72
post #9
post #4

This is new to me, and therefore bad and scary. It's great that you know NN well enough to fold it into regular work. But think of all us poor regular developers! Who now have to grapple with: - an unfamiliar architecture - uncertainty / effectively non-deterministic results in program flow

NN are in principle deterministic (unless you add randomness to it such as is the case with LLM top p/k temperature). Uncertainty is probably the better word of the two, but I feel like there should be a different term.

Unpredictability?

Re: My Python code is a neural network

#73
post #66

Earlier quoted context omitted.

The Taylor Series dates to 1715. Fourier Series dates to the 1820s. Both are universal function approximators and both can be learned via gradient descent. For the case where the function you want to learn actually is polynomial or periodic (respectively), these are better than neural networks.

For your interest, Taylor Series are not universal function approximators - the Taylor Series around 0 for f(x) = e^(-1/x^2) if x != 0 else 0 is identically zero (all partial derivatives are 0 at 0) but the function is clearly not identically zero. So the radius of convergence for this Taylor series is infinite but it only equals the approximated function at one point. I'm sure there are some conditions you can put o…

I'm pretty sure the UFA theorems for neural networks wouldn't apply to that function either: https://en.wikipedia.org/wiki/Universal_approximation_theore...

Generally, they assume the function to be approximated is continuous.

Re: My Python code is a neural network

#74
post #69

Earlier quoted context omitted.

Is that true also of LSTMs?

Yes. We cover Jordan and Elman RNN, LSTMs, and GRUs. Assignments only really test for LSTM knowledge, though.

Thanks. The reason I asked the question is that I've struggled to understand RNNs and other networks (compared to MLPs, CNNs, and transformers) due to the subtlety of their design and my hope was that I could simply forget about them.

I'm surprised about only testing for LSTMs- of all the sequence/memory models, they seem like the most arbitrary and hacky, but I've never been able to determine if that's simply because I don't understand those types of models (my training is in HMMs- do you teach/test those?)

Re: My Python code is a neural network

#75
post #74

Earlier quoted context omitted.

Yes. We cover Jordan and Elman RNN, LSTMs, and GRUs. Assignments only really test for LSTM knowledge, though.

Thanks. The reason I asked the question is that I've struggled to understand RNNs and other networks (compared to MLPs, CNNs, and transformers) due to the subtlety of their design and my hope was that I could simply forget about them. I'm surprised about only testing for LSTMs- of all the sequence/memory models, they seem like the most arbitrary and hacky, but I've never been able to determine if that's simply becaus…

No, we don't teach HMMs (although that would be super cool). It's strictly a neural networks class.

A lot of my research has focused on LSTMs, and so I am partial to them. I think they are super useful and have a lot of properties, but frankly speaking if you had to choose one architectures of the ones you mentioned, LSTMs/RNNs are probably the most OK to skip.

That said, if you just look at a simple RNN like the Jordan RNNs and focus on understanding that, then LSTMs just become fancy RNNs with some forgetting and remembering logic.

Post reply on HN