3 ms·
You can create much tougher classical competition by writing highly optimized code that accounts for the sparse connectivity structure of the current D-Wave chi
by dmlorenzetti 13y ago
You can create much tougher classical competition by writing highly optimized code that accounts for the sparse connectivity structure of the current D-Wave chip.
Why should optimized code "account for the sparse connectivity of the D-Wave chip"? If the contest is to solve an optimization problem, then the "classical competition" doesn't need to know anything about the D-Wave. The only reason a competing code would need to model the D-Wave itself would be if it's simulating how the D-Wave solves an optimization problem-- in which case comparing the times taken to do the optimization is hardly meaningful.
- pilom 13y agoThe problem is that the "non-optimized" solutions assume that every quibit can talk to every other one. So they are modelling what the quibits should do in a perfect case and modelling the perfect case is much slower than modelling what we actually have. So the fastest ones are the ones that say, oh, the best answer that the D-Wave is going to give will be X so I don't need to be any more accurate than that. I'll just model the bare minimum necessary to have the same accuracy as the D-wave. Its like lossy compression vs lossless compression. If you are willing to have lossy compression you can do much better and faster. The D-wave is lossy (because it has a "sparse connectivity structure") and thus the other solutions which are also lossy are better comparisons on a speed benchmark.