99 karma · joined July 6, 2016
Here is a paper where some colleagues of mine wrote a benchmark paper explicitly to check various methods against each other (with good agreement): https://journals.aps.org/prx/abstract/10.1103/PhysRevX.5.041...
Here is a study that finds a number around half of all jobs being replaced: http://www.oxfordmartin.ox.ac.uk/downloads/academic/The_Futu...
I have found this approach to multiple dispatch leads to code that's much easier to reason about and maintain. My use case is a tensor library where the tensors have a single interface but various storage backend types, which 'interact' with each other. It doesn't make sense to define these interactions through methods belonging to only one class or the other.
In the article, entanglement is a precise mathematical notion that is like an information based metric measuring the distance of a quantum state tensor (wavefunction) from the manifold of rank 1 tensors.
As long as the computer makes a decision where we can say "that was very reasonable, even if better decisions existed" then it seems ok to me.
The connection to the donut/bagel thing more familiar in topology is that topology also deals with integers: a manifold can have 0,1,2,3... holes in it, that sort of thing.
One key mathematical quantity that comes up in the works of Thouless and Haldane is the Chern number https://en.wikipedia.org/wiki/Chern_class
The reason the physics quantities jump is that the Chern numbers of certain electron bands change, and by definition a Chern number is an integer.
If you're asking why it goes in steps of 1/2 it's a group representation theory thing (guessing you probably already know about that).