Counterexample to Euler's conjecture on sums of like powers
fermatslibrary.com
fermatslibrary.com
No reference is made to previous attempts to study Euler's conjecture or similar conjectures (there are surely a dozen other papers that ought to be cited in the introduction).
What led the authors to consider a computer search as opposed to any other approach? Does the method generalize?
It is indicated that the CDC 6600 was used. How was the programming done? How long time did the execution take? The instance is claimed to be "the smallest". In what norm? How can you be sure that the computer program did not skip any smaller examples?
The most serious problem with the paper, however, is that the only contribution is a purely computational statement which, though a counterexample to a conjecture, does not advance mathematical theory in any way.
Due to these shortcomings, my recommendation to the editor is to REJECT the submission.
You can tell by "How can you be sure that the computer program did not skip any smaller examples?"
However, in actuality it really is actually too short. For example, it would be far more interesting to us in 2016 to read this early computational result if it included "reference made to previous attempts to study Euler's conjecture or similar conjectures", also "What led the authors to consider a computer search as opposed to any other approach?" and so forth.
Also in 2016 it would be extremely interesting to know "How was the programming done? How long time did the execution take?" For purely history-of-computation reasons.
Also it would be really interesting for the authors to have listed their own views on the ramifications, i.e. in what way it advances mathematical theory (or not).
Even though the parent comment is sarcastic, as a reader in 2016, I got next to nothing out of the paper. If it had been rejected on the above (sarcastic) basis, and the authors had submitted a six-page version, it would be far more interesting to us. The same would have been true for contemporaries.
[I realize it's sarcasm but in case it's not clear to everyone, I'll speak my mind about it]
I think it's a pretty serious advancement. Confirming a conjecture is just as important as invalidating it with a counter example. It doesn't matter if that counter example fits on one line.
Why should this be even necessary? There are surveys for that. Not every mathematician needs to be a historian. Nor do most people like to read the same introduction in every paper on a certain topic.
You only need one counterexample to a theory or conjecture to prove it wrong.
I only wish they'd described the method they used to find the counterexample.
The CDC 6600 was a pretty hardcore machine; it was Seymour Cray's first design at his Chippewa Falls skunk works, according to Wikipedia. Would definitely be interesting to know how long their solution took.
- compute S0 = {n^5 | 1 < n <= 1320} (3960 multiplications)
- compute S1 = {n^5 | 1 < n <= 1000} (zero multiplications)
- compute S2 = {s+t | s,t ∈ S1} (500,500 additions)
- compute S4 = {s+t | s,t ∈ S2} (around 10^11 additions)
- compute the intersection of S0 with 4
You don't have to store S4, so 2 megabytes of memory or so should suffice. 10^11 operations likely was out of reach for the CDC600, though.
To speed up things, do the above for numbers up to 100 or so using modulo arithmetic. That gives you candidate solutions modulo your word size. That way, you don't have to compute large parts of S4.
That CDC6600 dates from a time where register access wasn't much faster (if it was faster at all. https://en.m.wikipedia.org/wiki/CDC_6600#Description: For instance, a processor might take 15 cycles to multiply two numbers, while each memory access took only one or two) than reading from memory, and integer multiplication took >1 cycle (https://en.m.wikipedia.org/wiki/CDC_6600#Description: in addition to the clock being faster, the simple processor executed instructions in fewer clock cycles; for instance, the CPU could complete a multiplication in ten cycles.)
434437^15 + 588129^15 = 588544^15
https://www.google.com/search?q=588129%5E15+%2B+434437%5E15+...
434437¹⁵ + 588129¹⁵ = 352114612798389918432959038931874707477944791745072116429171623348641601872653349744942
588544¹⁵ = 352114612798389919037509191076162751408804961099244071160111294752887772695040228327424
It’s apparently close enough to fool Google, but it’s not correct.
[0] https://www.wolframalpha.com/input/?i=588129%5E15+%2B+434437...
[1] https://www.wolframalpha.com/input/?i=(+588129%5E15+%2B+4344...
(Also a nice early-ish use of supercomputers to solve pure math problems).
Edit: I guess the answer might be "5" depending on what the paper means by "smallest" example. (smallest largest number vs smallest smallest number.)
Once you have the numbers, it's easily reproducible.
"I use BFS a lot, myself, to check mathematical conjectures. [...] You think something is true, you can imagine some graph of all possible inputs to that theorem and you'd need to check them. Typical way of doing that is BFS through that entire graph of states. Usually we're testing finite special cases of a general conjecture, but if we find a counterexample, we're done, don't have to work on it anymore. If we don't find a counterexample then we have to do the mathematics."
I'm curious if there are low or high outliers.