Implementing Neural Turing Machines
arxiv.org
Implementing Neural Turing Machines
1–10 of 16 posts
Re: Implementing Neural Turing Machines
#2Does it mean that one can expect better explainability in the future from these models?
Re: Implementing Neural Turing Machines
#3Re: Implementing Neural Turing Machines
#4Re: Implementing Neural Turing Machines
#5Important and unsurprising sentence from the paper's abstract: " A number of open source implementations of NTMs exist but are unstable during training and/or fail to replicate the reported performance of NTMs "
Re: Implementing Neural Turing Machines
#6Important and unsurprising sentence from the paper's abstract: " A number of open source implementations of NTMs exist but are unstable during training and/or fail to replicate the reported performance of NTMs "
Why do you deem it unsurprising? Do you think that the opensource neural network implementations are subpar?
Re: Implementing Neural Turing Machines
#7Important and unsurprising sentence from the paper's abstract: " A number of open source implementations of NTMs exist but are unstable during training and/or fail to replicate the reported performance of NTMs "
Why do you deem it unsurprising? Do you think that the opensource neural network implementations are subpar?
Re: Implementing Neural Turing Machines
#8“how the memory contents of a NTM are initialized may be a defining factor in the success of a NTM implementation” Does it mean that one can expect better explainability in the future from these models?
Re: Implementing Neural Turing Machines
#9Re: Implementing Neural Turing Machines
#10Also compared to the open source implementation (https://github.com/snowkylin/ntm) it seems like his main novel claim is that he looked at different memory initialisation patterns.
Edit:
compare the original: https://github.com/snowkylin/ntm/blob/master/ntm/ntm_cell.py
to the derivative work: https://github.com/MarkPKCollier/NeuralTuringMachine/blob/ma...
from what I can tell the main innovation is that the derivative work uses a named tuple instead of a dictionary for state keeping and there is new memory initialisation code. The original author apparently initialised the memory randomly. I also feel like the paper should cite the implementation they are basing their work on. The paper https://arxiv.org/pdf/1807.08518.pdf merely states that other implementations exist on page one and makes no mention of the fact that their implementation is based on one of those. Combine that with the fact that they are asking people in the Readme to cite their paper feels like not a very good idea.