Update:
It seems as if David Marshall has found the missing link:
The footage used in the clip is not just from the Manchester Baby, but also from the Manchester Mark 1 which became operational about a year after. As noted its first (useful) program was in fact a proof for Mersenne primes, a perfect fit for the chalkboard scene.
Looks like the combined effort has revealed that this video features less than exact wording (equation vs. expression) and a mixture of pictures, not all belonging to the topic named.
First of all, the clip does not state that this problem was used, especially not used as a test for reliability.
Next a short look at the Baby's Wiki entry would have revealed that one of the first problems used - and indeed used to prove reliability - was to find the highest (all) dividers for a rather large, but still manageable number, in this case 218:
The first of three programs written for the machine found the highest proper divisor of 218 (262,144), a calculation that was known would take a long time to run—and so prove the computer's reliability—by testing every integer from 218 downwards, as division was implemented by repeated subtraction of the divisor. The program consisted of 17 instructions and ran for 52 minutes before reaching the correct answer of 131,072, after the Baby had performed 3.5 million operations (for an effective CPU speed of 1.1 kIPS).
It's all about what to test. In this case it might be not only correct workings, but more about reliability over longer durations. Doing one operation right isn't a big deal and can be tested while building. Doing it a million times under program control is.
Useful programs need to fit several criteria; some may be:
- Finish
- Finish within a reasonable time
- Fit into program space
- Use as few instructions as possible
and, most importantly
- Have a well known answer
While #1 seems obvious and #2 simple, it isn't, as it needs a problem that scales well, so its input parameter can be used to adjust (expected) runtime. A problem solved in a few seconds doesn't test the machine well; one running for days may be already way outside even the most optimistic guesses about reliability. Being a 32-bit machine, anything between 20 and 231 may have been usable - the latter one with a runtime of maybe a year :))
Similarly, #3, where again #4 is a crucial restriction, as it is less of an issue for a small program to prove its correctness as a transformation of the problem.
And yes, #5 is really obvious. In this case it was perfect as the answers were not only well known, but (back then) known to everyone and a pain in the ass - hence large volumes of books just listing divisors for numbers :))
A problem like finding all divisors or the largest divisor fits well to all of these points and even offers secondary benefits like being repetitive but with changing data.
A vignette within the short video shows a clip of someone writing the expression 2127 - 1 on a chalk board.
Well, as usual with such an out-of-context picture, multiple explanations are possible.
First 2127-1 is not a problem but a number (the largest number that can be written using 127 bits). And we can only guess what it should mean. Then there is a question mark below, so maybe that is part of the notation? As in "What's the largest divisor for 2127-1"?
Then there's a separate section in the Wiki article naming the first three programs, with the third being one for long divisions (written by Turing), so maybe the above describes exactly this program as in allowing to "dividing (anything up to) 2127-1 by some number" (*1). This would, of course, mean that the pictures taken where not from first operation but at least 3-4 weeks later (*2) when Turing wrote that program (*3). Above clip being obviously edited and merged from original reels and pictures, this might be quite possible.
Or it is, as so often when media report about something, a staged setup. Just a scientist writing something on a chalkboard to make it look good. After all, the reporter and film crew may have had - as so often - no idea what it's about and were just looking to make it work on the screen. The text "...equations like this..." might be another hint, as it's obviously not an equation - journalists often use words they believe to be fitting but not really words that describe what's shown or happening. Remember how often some stupid header files are dumped on screen when there is some reporting about programming or anything computer related? Not a new invention.
Make your pick, I would name the second one to be true - but I can't rule out the last one.
*1 - 2127-1 would be the largest number that can be packed into four 32-bit words while still leaving one bit for a sign or other markings (like NaN). Again a little hint on multi-word arithmetic as Turing obviously programmed. Of course, without more detailed information about how many words that program used (or maybe a variable number) for its 'BigNum' representation, it is just a little hint supporting this explanation.
*2 - Back then that was well within the news cycle :))
*3 - More support for this comes by the fact be that it is hard to imagine that any other, more complex problem (like proving a Mersenne prime) is described, as such would clearly go beyond the abilities of the Manchester Baby. It was only a demonstrator with 32 words of memory, usable either as program or data storage. Already the (rather simple) first program used up 25 of them (17 instructions, 8 data).
Further the machine offered only 3 ALU instructions (subtraction, negation and test for a negative number), so any higher function must be replaced by looping around these. I can see no chance to implement something as complicated as a Lucas Lehmer Test.
2^127-1is solved ... if directly by outputing the number in binary then there is no reason to test this at all as it is just127 onesbut if the output is transformed into decadic then you need to perform a lot of integer arithmetics which would test all the basic instructions of early computer... – Spektre Jun 22 '18 at 09:42hex -> decconversion on strings I am using for my bignums (asbin <--> hexconversions are trivial) – Spektre Jun 22 '18 at 10:19*0.5versus/2. – uhoh Jun 24 '18 at 05:40