News for hackers. Stuff that matters.
Re:Could a Neuroscientist Understand a Microprocessor? (2017) by aavaas on Thursday April 12, 2018 @12:40AM (#16818031)
People do reverse engineer chips by photographing them. https://youtu.be/aHx-XUA6f9g (Reading Silicon: How to Reverse Engineer Integrated Circuits). But as far as I know, the same cannot be done with the brains even if we can photograph it. I guess the 3D structure of the brain compounded with high interconnection between neurons does not make it easy.
Re:Could a Neuroscientist Understand a Microprocessor? (2017) by kkylin on Thursday April 12, 2018 @02:28AM (#16818484)
Much much more to how neural circuits work than just connectivity. Good example to keep in mind is C elegans (https://en.wikipedia.org/wiki/Caenorhabditis_elegans). Despite knowing the connectivity of its 302 neurons, and the whole organism consists of just a few times that many cells, AFAIK we still don't fully understand how its nervous system works, e.g., how it makes decisions etc.

(There is a lot of work on this organism, and I haven't kept up with the literature. So maybe the comment is a bit out of date... someone more knowledgeble should chime in.)

Re:Could a Neuroscientist Understand a Microprocessor? (2017) by haZard_OS on Thursday April 12, 2018 @11:41PM (#16826987)
Well, I wouldn't say we understand C. elegans neurobiology and behavior "fully", but great advances have been made at the systems level:

https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2904967/#__ffn_... [overview of behavioral assays at systems level]

http://conferences.union.wisc.edu/ceneuro/program-info/organ... [next major conference]

And, of course, my favorite, WormWeb:

http://wormweb.org/neuralnet#c=ADA&m=1

Re:Could a Neuroscientist Understand a Microprocessor? (2017) by resiros on Thursday April 12, 2018 @04:47AM (#16819067)
The big difference is that we understand chips: We know what kind of elements does an integrated circuit need (gates, registers) and we understand how each of the low- and high-level and elements work. Reverse engineering in this case is puzzle reconstruction with very strong priors. On the other hand, we are truly clueless for brains: we do not know how "algorithms" are run in brains, if there are any simple computing units, how memory is stored ... All what we have are some guesses and statistics.
Re:Could a Neuroscientist Understand a Microprocessor? (2017) by otabdeveloper2 on Thursday April 12, 2018 @01:50AM (#16818354)
Or perhaps the brain works nothing like a CPU.

(The very idea that it does is actually laughable, akin to medieval fantasists imagining that flying machines must have huge white wings with fleshy feathers.)

Re:Could a Neuroscientist Understand a Microprocessor? (2017) by aavaas on Thursday April 12, 2018 @02:03AM (#16818395)
Yes, a brain does not work like a CPU. As noted by another user in this thread, understanding brain is a considerably harder problem. "CPUs are deliberately engineered so that their different functions are nicely decoupled and easy to reason about but brains are the result of a very messy evolutionary process" -SilasX
Re:Could a Neuroscientist Understand a Microprocessor? (2017) by makomk on Thursday April 12, 2018 @08:19AM (#16820070)
I think it's partly the regular, simple, easy to understand structure that makes the approach outlined in this paper fail so badly. Because CPUs are made up of a number of simple, regular pieces connected in a way that's generic and easy to reason about, each of which is general enough to be used across many kinds of programs, knocking out individual transistors and observing the effects on the output of complex programs doesn't tell you much. Which parts of the CPU are used for a particular "behaviour" depends on the whims of the programmer and the compiler's optimisation passes as much as anything else.
Re:Could a Neuroscientist Understand a Microprocessor? (2017) by amelius on Thursday April 12, 2018 @03:37AM (#16818758)
Engineers are also the result of a very messy evolutionary process ;)
Re:Could a Neuroscientist Understand a Microprocessor? (2017) by Sharlin on Thursday April 12, 2018 @05:45AM (#16819295)
Being the result of a messy evolutionary process doesn't give you any special insight into other messy evolutionary processes.
Re:Could a Neuroscientist Understand a Microprocessor? (2017) by adrianN on Thursday April 12, 2018 @02:15AM (#16818436)
I don't think that "maybe we could understand the brain if we had a very detailed picture" is the same as "the brain works like a CPU".
Re:Could a Neuroscientist Understand a Microprocessor? (2017) by ajuc on Thursday April 12, 2018 @03:23AM (#16818703)
Nobody is claiming it does.
Re:Could a Neuroscientist Understand a Microprocessor? (2017) by Ace17 on Thursday April 12, 2018 @01:25AM (#16818240)
So maybe we should synthesize a (probably huge) photograph of a chip, whose network would correspond to one brain ... and then hand it to hackers, as a reverse engineering challenge :-)
Re:Could a Neuroscientist Understand a Microprocessor? (2017) by aavaas on Thursday April 12, 2018 @01:58AM (#16818380)
The problem then transfers to synthesizing such a network on a chip :)
Re:Could a Neuroscientist Understand a Microprocessor? (2017) by ajuc on Thursday April 12, 2018 @08:21AM (#16820080)
We could start with something very small, like a worm.
Re:Could a Neuroscientist Understand a Microprocessor? (2017) by ItsMe000001 on Thursday April 12, 2018 @02:34AM (#16818507)
So? We know how chips work, we make them! Going from a picture is much easier, you know exactly what you are looking at. Not just the individual structures, but we also already know what kind of higher level structure to expect. There is nothing unknown about what we see on a chip, by definition (we could not have made it in the first place).
Re:Could a Neuroscientist Understand a Microprocessor? (2017) by tawayway on Thursday April 12, 2018 @09:26AM (#16820653)
Semiconductor manufacturing is very planar - it's made up of many layers on top of each other, with some interconnecting features or vias between layers. It's a best-case scenario for reverse engineering with photography.