3 ms·
Good stuff. quick q: why do you call this a hopfield network? I see you have a fully connected 2 layer neural network (0 hidden layers): https://github.com/mat
by ilzmastr 12y ago
Good stuff.
quick q: why do you call this a hopfield network? I see you have a fully connected 2 layer neural network (0 hidden layers): https://github.com/mateogianolio/hopfield-color-recognition/blob/master/network.js#L5 https://github.com/mateogianolio/hopfield-color-recognition/...
instead of a bunch of circularly connected perceptrons: http://en.wikipedia.org/wiki/Hopfield_network#mediaviewer/File:Hopfield-net.png http://en.wikipedia.org/wiki/Hopfield_network#mediaviewer/Fi...
p.s. it looks like the library you're using has a built in Hopfield network `new Architect.Hopfield(10)` (at the bottom: [here](https://www.npmjs.com/package/synaptic) https://www.npmjs.com/package/synaptic)), why didn't you use this?
- megalodon 12y agoThanks. To answer your first question, I (perhaps naively) assumed that the synaptic library used correct naming for its network prototypes [1]. My implementation contains a few modifications to the one defined as 'Architect.Hopfield' [2], which is why I decided to put it in a separate file. It also helps a visitor to know how the network is defined without needing to browse the source of the synaptic library. [1]: https://github.com/cazala/synaptic/blob/master/README.md#hopfield https://github.com/cazala/synaptic/blob/master/README.md#hop... [2]: https://github.com/cazala/synaptic/blob/master/src/architect.js https://github.com/cazala/synaptic/blob/master/src/architect...