HNHacker News
TopNewBestAskShowJobs

da-bacon

417 karma · joined September 18, 2011

Theoretical physicist, onetime quantum pontiff, pseudo-professor turned computer scientist, turned software developer.

http://dabacon.org/

submissionscomments
da-bacon··on Quantum theorem shakes foundations
A very interesting paper (I used to work in quantum computing, so I think I understand the paper pretty well after reading it a few times. Like most foundations papers is deceptively short!)

The basic idea is fairly simple. From quantum states (the wave function) we can determine probabilities of outcomes when these states are measured in different manners. A major problem in quantum foundations is how to understand these probabilities arise, i.e. where do these probabilities come from?

For example, it could be that the probabilities arise from our ignorance of knowledge of the system (these are what people traditionally call hidden variables.) Imagine a hard disk with a bunch of information on it. If you don't know all of the bits on this hard disk, then your computer can act in ways you can't explain because you don't know all of the bits. Each time you setup your system and run a program you may get different results because that extra information on the hard drive could be different, and so because you don't know all of the information you will see probabilities of outcomes. Mystery solved. Coming up with such a theory however currently always runs into a problem with locality. But that's a story for a different comment thread...

Here is what the authors ask. They say: well it could be that all of the information that is specified in a quantum wave function is all that matters, that is for each quantum state there is a one to one correspondence with a configuration of the hidden information (they allow for extra information, but that's basically irrelevant.) That is, literally, the quantum state is written on your hard drive in all its glory detail, and each quantum state is distinguished for any other quantum state. Contrary to this it could be that the information overlaps in some way. That is for different quantum states, some of the bits, say, will be in the same configuration. The authors then go on to show that this later assumption isn't compatible with the predictions of quantum theory (and show an experiment that can be done that will verify that the later interpretation is not correct. If the experiment fails, then quantum theory is wrong, and all hell will break lose. Assuming quantum theory holds, this shows the second interpretation isn't viable.) Very neat.

There are a couple places where the argument seems a bit odd to me. For example, it is really not clear to me why the measurement device in their system has to depend on the portion of the information that is shared between different prepared wave functions. If this information is ignored by the measuring device, I don't see how their contradiction will arise. Of course it self tells us something kind of interesting because it puts a limit on how shared information is revealed to a measurement device (this seems almost Kochen-Specker theorem like.)

da-bacon··on Paul Dirac: The unsung genius
One of my favorite Dirac stories "An interview with Dirac": http://www.math.rutgers.edu/~greenfie/mill_courses/math421/i...
da-bacon··on Why Finland’s schools are great (by doing what we don’t).
What makes you think teaching to a test is easy? If the sole motivation of teaching is to increase a students score on a narrowly defined set of metrics, how motivated do you think students are going to be? I'm curious because in my experience the hardest learning I've done is when it's been aimed at achieving some hurdle for a narrow externally defined subject.
da-bacon··on Science Code Manifesto
The discussion document is interesting and spells out a lot for of what is intended: http://sciencecodemanifesto.org/discussion

One thing that is missing is whether the quality of code should be used in peer review. If you are going to make software essentially part of the publication record, then is it valid to reject a paper because it's code is spaghetti and not understandable. A paper whose derivation the reviewer cannot follow because will get rejected, should a similar standard be applied to the software?

← PreviousPage 4 of 4