Talk:Colossus computer/Archive 1

Archive 1

Archive 2

1990s reconstruction

"Even in 2004, Tony Sale notes that "Colossus is so fast and parallel that a modern PC programmed to do the same code-breaking task takes as long as Colossus to achieve a result!". " That's hard to believe. Is it actually true (the fact, not the fact that he said it)? --Bubba73 22:28, 26 May 2005 (UTC)

In fact, if someone could provide me with test data and a good description of what Colossus would do and how long it would take, I might try to verify that. --Bubba73 02:16, 29 May 2005 (UTC)

I have some doubts about that statement about the speed of the Colossus compared to a modern PC.

• In "The First Computers: History and Architectures", by Rojas and Hashagen, page 363 has a section "the performance of the Colossus". It was processing characters from a paper tape at 5,000 characters per second. Each character was encoded as 5 bits across the tape. For each character it could do up to 100 boolean calculations on each of the 5 channels. This is 2.5 million boolean operations per second.
• He made the statement in 2004, when I got a 2.4 GHz P4, which was two steps down from the fastest one. It can perform a bitwise operation in 2 clock cycles, or 1.2 billion per second. Futhermore, it can do the same operation on 32 bits at once in the same amount of time. It seems likely that the Colossus was doing he same operation on 5 bits in parallel, since it was doing XOR on 5-bit characters. So even if the Pentium was used to work on 5 bits of its 43 bits at the time, that amounts to 6 billion boolean operations per second, over 1000 times as fast as the Coolossus.
• The book quoted was from 2000 and mentions the same thing about a Pentium. In 2000 I had a 300 MHz Pentium II, and it wasn't the fastest one at the time. The original Pentium came out in late 1992 or early 1993 and ran at 60 MHz. I believe it could do a boolean operation on 32 bits in 2 clock cycles, or 30 million per second. Even if only 1 bit was worked on at the time (instead of 5 or more in parallel), that is still more than 10 times faster than the Colossus, at the very minimum.
• Also, the book says that the Colossus had AND and OR gates. But the operation it was primarily doing was XOR. The Pentium has XOR built in, I believe, so it may have taken more than one operation for the Colossus to do a XOR.

Bubba73 17:44, 14 Jun 2005 (UTC)

Yes, it does look dubious. Sale writes a lot of his simulators in Javascript, which might have an effect ;-) — Matt Crypto 09:42, 4 August 2005 (UTC)

The Colossus did somewhat better than that, actually; your math is a bit off, especially for the Colossus II (although it's a bit hard to convert Colossus operation rates to instruction equivalents). For one, it had to generate the key-stream (which was were most of its tubes went, actually), which is a certain amount of work (not sure how to turn that into instruction equivalents; you'd have to simulate the rotation of 10 binary-output wheels, each of a different prime size - and then there are the two Motor wheels which make the operation of the others stutter). Then, it did 5 positions at a time (i.e. because of the 5-deep systolic array, it was effectively processing 25K characters per second). Next, it had 5 separate counters, each of which could be programmed to increment on an independent logical expression (which could be as complex as "((character EQ X) OR (character EQ Y))", i.e. 3 logical operations - and perhaps more, I'd have to study the manual to be certain what the largest logical operation was that could be configured; I suspect that if one used the plug cables instead of just the switches, you could get pretty large expressions), and it could increment all of them on each step (i.e. 5K times per second, or 25K increments per second, total).

But it's still considerably slower than contemporary computers (although it was pretty darned fast, even by, say, 1960's standards; in part because it was hardwired to do that one kind of statistical analysis). I think Matt's point about those simulations being in Java is a good one, though! :-) Noel (talk) 04:22, 6 August 2005 (UTC)

PS: I forgot to mention that there were bunch of special hacks, which also would increase the time to simulate it, e.g. things like the "not-99" feature. Finally, as to XOR, that was built into Colossus, they didn't have to emulate it with other operations (as they did for OR, which had to be built out of AND and two levels of NOT). Noel (talk) 04:26, 6 August 2005 (UTC)

"it was effectively processing 25K characters per second)" OK, I had assumed that the five channels were the 5 bits to encode a character. But if it was doing the same thing to each of 5 channels, and one character was encoded in 5 or 6 bits on each channel, a modern PC can do all of that in parallel.

"But it's still considerably slower than contemporary computers" The article says that it was a fast, which I was wondering about. If I could get the details of what it did and some sample data, and it wasn't too involved, I might like to write a program for a modern PC to compare. Bubba73 04:45, August 6, 2005 (UTC)

Well, you could take Tony Sale's Java code (available through his web site here) and look at it! :-) More seriously, the various Wikipedia articles (this, and the one for the Lorenz SZ 40/42 machine), and particularly the external links from them, will provide you all the information needed. (E.g. links from the Lorenz article will give you the full details of the 12-rotor mechanism which generated the 5-bit-wide keystream - the Colossus included an electronic simulation of that mechanism, so a Colossus simulator will have to include it too.) No, it's not in the most convenient form - but writing the program is the easy part of doing a simulation. A copy of From Fish To Colossus (it's cheap) would be a really big help. Noel (talk) 15:28, 6 August 2005 (UTC)

I've just added that book to my wish list. I haven't seen that book, but as you say, it probably would be better to go to a more direct source. First, I don't know Java, and second I want to simulate the machine, not simulate a simulator. What's the "hard part" - understanding what it does? Bubba73 16:09, August 6, 2005 (UTC)

No, there's nothing spectacularly hard about most of it. It's just that there isn't a single source (excepting perhaps Copeland's forthcoming book, which I've not seen yet as it's not out yet) which clearly and concisely explains all the technical details of what Colossus did, in enough detail to produce any sort of semi-correct simulator. You have to drudge around through all sorts of odd stuff to get the detail that's required - see my investigations above (about the differences between the Mark I and Mark II Colossi) for the kind of digging that is required. E.g. when Tony Sale build the replica, a lot of the actual details on the working of the Boolean logic network which processed the two data-streams (the key-stream and the cipher-stream) and sent outputs to the counters came from reading the Special Fish Report, which was a rather cryptic "how-to" operator's guide! I still don't know of anything which clearly describes this logic network! Noel (talk) 17:30, 6 August 2005 (UTC)

I understand. And that's exactly what I was hoping for - a clear and concise description, enough that I could program it (without spending a great deal of time digging it out.) When is the new book due? Bubba73 18:11, August 6, 2005 (UTC)

I'm planning on putting in some work on this article, and it should eventually contain a description of what Colossus actually did (although whether any of my writing would ever be clear and concise is very much debatable!). — Matt Crypto 18:19, 6 August 2005 (UTC)

I guess it also depends on whether you want to simulate the Colossus itself, or simulate the codebreaking tasks that the Colossus performed. Simulating the Colossus would be a somewhat large undertaking, because it's a relatively complex machine and is not described completely in any public documents. Simulating one of the correlation algorithms that Colossus implemented would be pretty straightforward, on the other hand. P.S. There's not a great deal of similarity between Java and JavaScript other than the name ;-) — Matt Crypto 18:19, 6 August 2005 (UTC)

I guess what I had in mind was doing what Colossus did rather than simulate Colossus itself. Although the Colossus was a remarkable accomplishment for its time, I don't think it is fair of the article to say that a Pentium-based PC can do the same thing only as fast based on the programs that have been mentioned. It was mentioned that its speed compared well to computers of the 60s, and that is likely to be true. Hoever, computers of the 60s were slow compared to todays PCs. Within the last month I took something that had taken x time to run on an IBM 360/67 (IBMs fasstest computer as of August 1966) and I wrote it up for my 2.4 GHz Pentium PC, and it was 3,900 times as fast. I don't know much about Java or JavaScript exccept that I don't thing either one is a good choice for actual encoding or decoding. Bubba73 23:55, August 6, 2005 (UTC)

I've written a program to do Lorenz encoding/decoding, to give a rough idea of how long it takes on a near-modern PC, my 2.4 GHz P4. I don't know how much more work the Colossus was doing. My program encodes/decodes at 40,000,000 characters per second if the data is already in memory and the result is kept in memory. However, the bottleneck is getting data into and out of the CPU. My hard drive reads at about 10,000,000 bytes per second, so that is the limiting factor. So 100 nanoseconds to read a character in, 25 nanoseconds to encode or decode, and 100 nanoseconds to write to disk - 225 nanaoseconds total, or 4.4 million per second. That is assuming 8 bits to the character. Since the old data uses 5 bits per character, putting 6 characters in 32 bits would result in 50% faster throughput. Bubba73 18:01, August 7, 2005 (UTC)

Scavenger Hunt 2

Colossus included the first ever use of shift registers and systolic arrays

Also hoping for a source on this one! — Matt Crypto 11:04, 10 August 2005 (UTC)

That's easy. The systolic arrays is from Cragon, pp. 83. (He also claims Colossus was the first digital system which operatied in synchronous [i.e. centrally clocked] mode, pp. 97.) As for the shift registers, I've seen that in various places (I think I seem to recall Flowers making that claim at one place); one is Randell, The Colossus, pp. 66 (section 7) - which also repeats Cragon's synchronous claim. Colossus also pioneered the use of voltage levels for logic values (instead of phase, as in the Robinsons), which allowed it to be run at very slow speeds, for checkout purposes. Noel (talk) 20:09, 10 August 2005 (UTC)

Visited Station X today

Amazing.

• Image:Colossus 2005 08 13.JPG

It's Frankencomputer! There's a whizzy frame running paper tape at high speed, there are 1940s-style strowger switches clicking madly away, flashing lights blinking--decade counters, not binary. A teletype that wouldn't have been out of place at the 1850 Great Exhibition spews data onto paper, and behind there's rack upon rack of thermionic valves! Reminded me most of all of a 1970s-era PDP-11, to be honest. ;) --Tony Sidaway^Talk 00:32, 14 August 2005 (UTC)

Colossal clanger

Sorry, this gloating is a little gratuitous and unseemly, but, quoting from an online Microsoft Encarta article ("Computer"):

It [Colossus] was used by the team headed by Alan Turing, in the largely successful attempt to crack German radio messages enciphered in the Enigma code. [1]

Now (and correct me and the Wikipedia article if I'm wrong), but I recall that 1) Alan Turing was never the head of a team attacking Tunny (although he did invent "Turingismus"/"Turingery", one type of attack on Tunny); 2) Turing's involvement in Colossus was very limited, if any (although Turing did play a large role in generating some of the ideas behind early computers); and 3) Colossus was never used to attack Enigma (it was used to help break Tunny traffic).

Of course, it's not as if Wikipedia articles are always error-free, but I couldn't resist the chance to note this clanger! — Matt Crypto 12:54, 21 Feb 2005 (UTC)

I've just noticed this comment -- my apologies for being dilatory -- and must agree as I'd seen that clanger myself (AE would probably be something like goof or screw-up, I think). But it's only one of many crypto pseudo-factoids I keep tripping over and I've run out of energy attempting to correct them or publicize them. It's because of their near ubiquity that I have tried several times to include comments in WP crypto articles about the (often un) reliability of much writing -- even ostensibly authoritative writing -- on topics cryptographic.

One has in mind in these cases such things as the invention of the brassiere by a German named Titzling, the installation of the first bathtub by (? -- can't remember which US President, but it was invented as a prank by H L Mencken early in the last century), the exceptionally poisonous qualities of the not quite a spider called here a Daddy Longlegs, ... all of which are repeated and repeated. Is it ever possible to actually exterminate these bits of 'true fact'? Perhaps we should organize all the Daddy Longlegs to go bite them to death? ww 23:41, 6 September 2005 (UTC)

The first...what?

We currently say that

Colossus was the first specialised programmable digital electronic computer

We previously have said that

Colossus was the first programmable (to a limited extent) digital electronic computer

I'm not really happy with either rendition. Personally, I don't think Colossus was programmable in the modern sense — it was just configurable. Moreover, the title of "first electrical digital computer" is claimed by the Complex Number Calculator[2], and "first electronic digital computer" is claimed by the Atanasoff–Berry Computer, both of which appear to predate the Colossi.

Jack Copeland's forthcoming anthology on Colossus is titled, "Colossus: The First Electronic Computer". Above, Noel mentions that Colossus was "the first large-scale electronic digital device".

This may be too complex a question to resolve ourselves, given that different scholars might give different answers to this question. It might be that we have to opt for describing how others have viewed Colossus within the history of computing. — Matt Crypto 16:36, 7 October 2005 (UTC)

Speed of tape

The section "The construction of Colossus" states that the paper tape moved at "40 ft/s = 12 m/s = 30 mph". These speeds are not equal, but only approximately so; even the ones in imperial units differ. Which is the correct speed? There is also no need for speeds to be given in two types of imperial unit. — Paul G 12:15, 1 November 2006 (UTC)

missing table info

Our table comparing early computers is well done, but missing at least two entries. One is the Atansoff-Berry machine and the other is the Stibitz relay machines from Bell Labs in the late 30s / early 40s. Both really should be included... ww 00:03, 8 February 2007 (UTC)

It is also rather notably missing the Manchester Small-Scale Experimental Machine, which, IMNERHO, has the strongest claim to be the first true computer. I'd add it, but i can't see how to edit the table - it's done in some remarkably freaky way, i think. -- Tom Anderson 2007-02-16 2200 +0000

Also note: the table is mis-labelled: it is a table of five apparently arbitrarily chosen early computers, not the first five. For example: the Z3 machine was predated by the Z1 and Z2 Zuse computers. If Z3 is there, surely the earlier models need including?

The Manchester Baby you refer to is unquestionably the first stored program general purpose computer in the modern sense. Computing machines of various sorts had existed for a long time previously. The table lists a selection of precursor technologies to modern computers: they're none of them really computers in the modern sense.

Post-War Colossi

I replaced "two survived for many years and were used during the cold war" with "A Colossus was kept by GCHQ — Copeland (2001) writes, "The last Colossus is believed to have stopped running in 1960. During its later years it was used for training purposes."". If anyone has a reliable source for the original, we can put it back in, but it seems very unlikely to me that any Colossus was used operationally post-WWII, given how specialised it was to the Lorenz machine. — Matt Crypto 00:08, 7 August 2005 (UTC)

I seem to recall seeing somewhere that report about two being kept, but I can't lay my hands on it! (Maybe I'm remembering reading it here?) I've checked the AHC 5/3 articles, the Metropolis and Randell books, The Secret War, Cragon, all with no luck. I'll try a few more later. As to why they might have kept some Colossi, I have a number of speculations. (Let me emphasize that these are 100% pure guesses.)

• First, I seem to recall a story about the Allies reconditioning Enigma machines and selling them on to various countries (not, of course, telling that that they'd been able to break into them), and using their knowledge of how to break into the Enigma to tap into the other countries communications. (Although given Welchman's revelations that the Enigmas, properly used, would have been almost impossible to break into, I have to wonder about this. Although perhaps they counted on other users making the same kind of mistakes as the Germans had?) So perhaps something similar happened with the SZ40's?
• Second, the Colossi were relatively general machines, outside the specialized circuity for producing the key-streams. Perhaps other countries were using similar teleprinter systems, and the Colossi were modified to break into other systems? Or perhaps they were saved in case other countries adopted similar systems? (The break-in techniques would have worked on similar code-systems.) There is the famous story of the "Russian FISH" machines the Germans handed over to the Western Allies at the end of WWII, which they used to break into a Russian teleprinter system.

In any event, The Codebreakers (Hinsley and Stipp) does have a record (pp. 185) of the scrapping of one Colossus; most of the standard parts were returned to PO stores. Noel (talk) 04:52, 8 August 2005 (UTC)

We'll have to wait until 2185 for the official declassification ;-) Personally, I could imagine that a Colossus would have been very useful as a training device, and as a prototype for improved machines, while there would be compelling reasons to upgrade to a new machine for any operational use. Counting correlations between bit-streams is a very powerful cryptanalytic idea, and I would agree that GCHQ was engaged in this sort of cryptanalysis soon after WWII, even if it wasn't the Lorenz machine itself. Supposing that's the case, as you mention you'd need to rebuild the key generator part, and (of course, I speculate without any basis) it might well have seemed better to start a new design from scratch, particularly with the benefit of a few years advance in computing technology. The NSA, at least, invested heavily in computers; I'd quite like to think that GCHQ did the same — but who knows? — Matt Crypto 11:14, 8 August 2005 (UTC)

Found it! It's in Michael Smith, Station X (TV Books, New York, 1998), pp. 226-227: "Two of the Colossus computers .. were taken to Eastcote but the rest were destroyed" .. "The Colossus computers were taken to Cheltenham when GCHQ moved there in 1952 and at least one was still working into the early 1960s." Alas, it has no source notes, so I don't know where the info came from. The book seems relatively carefully researched (and contains no errors I saw), so I'd tend to go with it. Noel (talk) 22:16, 8 August 2005 (UTC)

Well found! Yesterday I went through that book looking for Colossus info, and totally missed that part (must learn to use an index, must learn to use an index...). — Matt Crypto 08:44, 9 August 2005 (UTC)

Noel, I visited the National Archives last weekend, and found some fun stuff on Colossus. It would seem your thoughts about post-War Colossus use were correct:

At the end of the War a number of the Colossus machines including the original were dismantled, but a small number of the more recent versions were moved to Eastcote and subsequently to Cheltenham. With the end of the War the particular purpose for which the machines were designed disappeared, but the nature and reliability of the machines was such that a number of attempts, some more successful than others, were made to make the remaining machines suitable for a number of similar purposes, or, in effect, to generalise them. In the course of these successive changes, new drawings and documents were prepared and, probably to avoid confusion, most of the earlier drawings and documents were destroyed. Thus we have the paradoxical situation in which the success of the machine and the consequent attempts to adapt it to other applications contributed to the loss of much of the detailed information concerning its original form. (D C Horwood, A technical description of COLOSSUS I, August 1973, PRO HW 25/24.)

— Matt Crypto 13:51, 20 September 2005 (UTC)

The transcript for the PBS Nova program "Decoding Nazi Secrets" [3] says: "Eight of the ten Colossus machines were destroyed. The remaining two were moved to British secret service headquarters, where they may have played a significant part in the codebreaking operations of the Cold War. In fact, the Russian military had developed a code that was similar to the high command's Fish code. So the techniques invented at Bletchley Park were still to prove vital in a very different kind of conflict. In 1960, the order finally came to destroy the last two Colossus machines." According to information I have read, an eleventh Colossus was essentially finished at the end of the war, but I have found no reference as to what happened to the eleventh computer. I presume that all the computers, like the first, were built at the Post Office Research Station at Dollis Hill in NW London. On 10 July 2006, I emailed Tony Sale asking if he knows what happened to the 11-th computer, but I have not received a reply as of 19 July 2006. JonEAhlquist 05:43, 19 July 2006 (UTC)

"there would be compelling reasons to upgrade to a new machine for any operational use."

Quite the opposite. Its 1945 and computers cost huge money. You want to commission an upgrade when you dont absolutely have to? Not a chance. A company would have to have a critical need to consider getting an electronic computer of any kind. Tabby 13:51, 16 March 2007 (UTC)

At that time, "computer" meant someone with a calculator, using in large ranks, working out some abstruse calculation. Most of the illustrations are from aerospace companies and they're usually young ladies in a very large hanger type building at lots and lots of desks. As for the calculating machine to which you refer, no one knew about Colossus outside government circles and steps were taken that it remain so. And finally, there was a near complete lack of understanding of what these things could mean if they were made more reliable, more flexible, and available. In the middle 50s there were comments from captains of industry extimating the total industrial need for the things at perhaps a half dozen in the United States. There were lots of critical needs that no one saw. It took a decade plus, and several bankruptcies amongst pioneer compnaies (even with sub rosa funding from military sources) for industry to understand their use and be willing to spend money on them. There is now a general understanding of that, and we're working on getting average folks to understand that there's a lot of promising from suppliers which won't be delivered. Can't agree with you here. ww 22:06, 16 March 2007 (UTC)

speed of Colossus

About a year and a half ago, I was concerned about the article saying that the Colossus was as fast at doing its job as a modern PC. I think that was based on the JavaScript simulation. I wrote my own native program, and it was thousands of times faster than the Colossus. I tried to be as fair as possible - I simulated each wheel individually, whereas I could have made it faster. I processed only one character at the time, even though my program could have done six characters in parallel with less than six times as much computing (since it is a 32-bit CPU, using 5 bits per character).

When I read the part about JavaScript, I found a JavaScript program for factoring numbers, or something like that. I made a direct translation, and the native program ran 760 times as fast. Therefore, JavaScript slows the computer down by a factor of 760 or so.

The limiting factor in my program was the time to read the data from disk, not the CPU. Even with that limitation, the speed was a couple of thousand times faster than the Colossus. Of course, the Colossus was limited by its tape input too.

So I thought it was wrong to say that the Colossus was as fast as a modern PC, because it is in the same ballpark only if you slow the computer down by a factor of 750. But later I realized that what I was doing was original research, so I didn't include it. Now I see that the part about the Colossus being as fast as a PC has been taken out. Bubba73 (talk), 16:23, 23 December 2006 (UTC)

Thanks for posting your findings. I think there's sufficient reason to doubt the "fast as a modern PC" claim that we have to exclude it from the article. — Matt Crypto 22:14, 28 December 2006 (UTC)

The bbc (http://news.bbc.co.uk/1/hi/technology/3754887.stm) reported that Tony Sale, head of the Colossus Rebuild Project, "...argues that the original Colossus was so powerful, it would take current computers the same amount of time to break codes." It might be worth putting in something along the lines of it is claimed that... What do people think? 130.209.6.43 13:46, 11 July 2007 (UTC)

Untitled

Would need an infobox to make a higher class, imo -- role^player 01:39, 23 August 2008 (UTC)

Which is right...

Underneath the third picture it reads:-

In 1994, a team led by Tony Sale began a reconstruction of a Colossus. The machine is nearly complete, and has required over 6,000 man-days of volunteer work.

However the article states:-

In May 2003, the construction of a replica of a Colossus Mark II was completed by a team led by Tony Sale. It currently is on display in the Bletchley Park Museum in Milton Keynes, Buckinghamshire.

Does someone want to sort this out? I'd do it myself but I dont want to tread on anyones toes.

--Timmywimmy 18:46, 28 October 2005 (UTC)

Thanks for spotting that! The machine isn't complete, but I believe in May 2003 they reached a milestone where the rebuild was complete enough to perform the task of "setting the Chi wheels". IIRC, there was some grand switching-on ceremony involving Flowers and some member of the British royal family. Very recently, Sale and his team have managed to get the Psi wheels working, and they can get Colossus to do on-machine decipherment (although only one character at present!). — Matt Crypto 21:42, 28 October 2005 (UTC)

I've removed the statements about being complete as I think they are currently inaccurate; see [4]. I'll try and sort this out soon (if noone gets their first!). — Matt Crypto 00:13, 20 December 2005 (UTC)

Today we say that the Z3 of Konrad Zuse was the first computer. They fought along time because they didn't know and the Allies did not want that a German designed the first Computer. http://en.wikipedia.org/wiki/Z3_%28computer%29 --88.71.130.213 (talk) 16:32, 22 June 2010 (UTC)

ENIAC

ENIAC (1946) used 17,468 valves, but, unlike Colossus, was not a software programmable machine.

The first fully programmable digital electronic computer was the ENIAC which was completed in 1946.

Somewhat controversial. —Preceding unsigned comment added by 89.178.104.81 (talk) 17:06, 9 December 2010 (UTC)

Never turned off claim probably well founded

I attended a private demonstration of the first general purpose software programmable digital computer (the Manchester Baby) a few years ago, not long after it was put on display. The British Computer Society had run the project, and did the work in conjunction with as many of the original workers as possible.

We were told that yes indeed, the Baby were simply not switched off when being developed, except sometimes, and if it did get powered down, there was hell to pay in terms of blown valves.

Since it was Tommy Flowers in charge of building Colossus and the Manchester Baby, I'd say there's no reason to doubt the claim that they didn't switch Colossus off if at all avoidable, but that's not the same as `being on continuously from initial installation to decommissioning'. Hard to see how that could have been managed.

—The preceding unsigned comment was added by 86.140.201.40 (talk) 21:58, 3 April 2007 (UTC).

Valves encounter the greatest thermal stress immediately after turning on as the heaters heat up to operating temperature - what used to be known as warming up. Leaving the valve operating continuously - no hot/cold cycle - removes this stress allowing the valve a greatly increased life. This thermal stress may well be remembered by people who once had a valve TV or radio set. When a valve was on it's last legs the set almost always failed when the TV or radio was turned on.

BTW, Colossus was left running almost continuously IIRC, as Flowers had realised that valves almost always failed during the warming-up period and that if left running all the time their lives were increased greatly, making a complex valve-based machine such as Colossus practicable. Many had previously poo-poohed the idea of a valve-based computing machine prior to Colossus for exactly this reason of frequent valve failure.

IIARC, Colossus/the Colossi, was run 24/7 for long periods and only stopped when a valve did eventually fail. IIRC, a more frequent problem was the paper tape breaking and going everywhere due to the high speed involved. —Preceding unsigned comment added by 86.112.68.219 (talk) 16:47, 21 May 2011 (UTC)

dubious edit?

A recent edit explains that the colossus secret was maintained because copies were sold to other countries after the war. Therefore the secret had to be kept so others wouldn't learn of it.

This seems dubious to me and an echo of the Engima copies sales to other countries after WWII. As it is unsourced, I suggest it deserves to be deleted soon if a credible source is not provided. I'll try to remember to come back in a a week or so to made the correction, but if anyone doesn't want to rely on my increasingly wobbly memory, feel free to make the revision yourself. ww (talk) 02:51, 27 December 2008 (UTC)

Yet another odd edit, this one with its own section. I've moed it here pending clarification.

==Trivia==

In That Mitchell and webb look it is calimed that in the war a machine called "Colosson" was made that could make seemingly imposable Numberwang calculations and was probably a nod to Colossus.

Some discussion, even explanation of what is meant would be well. ww (talk) 03:24, 1 April 2009 (UTC)

The Enigma machine was used by a number of countries post-war, including a number in South America. The British as a result were able to read these countries diplomatic and other traffic. As a number of these were 'friendly' countries Britain not unnaturally did not disclose this fact.

At least one of the other South American countries that used the Enigma and had strong links with Germany also eventually went to war over some small islands off its mainland.

IASTR that China was also another country that bought the Enigma.

The whole revelation that the British had broken the Enigma and other codes during WW II was not revealed until a book was published around 1977(?), and although I'm not sure of the title, I do remember reading it. —Preceding unsigned comment added by 86.112.68.219 (talk) 17:14, 21 May 2011 (UTC)

Colossus had nothing to do with Cryptanalysis of the Enigma, it was concerned with cryptanalysis of the Lorenz SZ42 cipher machine. --TedColes (talk) 18:05, 21 May 2011 (UTC)

Churchill's orders

Winston Churchill specifically ordered the destruction of most of the Colossus machines into "pieces no bigger than a man's hand"

I'm looking for a source for this; the best I can find is a BBC Click Online article [5]. — Matt Crypto 08:44, 9 August 2005 (UTC)

Jeez, what is this, we're making this article into the latest Wikipedis "scavenger hunt"? :-) I seem to recall seeing the Churchill thing somewhere before (not sure about that exact quote, though); let me have a look. Noel (talk) 01:35, 10 August 2005 (UTC)

Oh, I'm just getting warmed up ;-) — Matt Crypto 11:04, 10 August 2005 (UTC)

Churchill couldn't have given any orders at the end of the war, he wasn't in power... 86.31.101.253 10:37, 8 May 2007 (UTC)

Churchill was still in power at the end of the war in Europe, and Colossus was used to attack a German cipher system. — Matt Crypto 18:52, 8 May 2007 (UTC)

The whole paragraph about the end of the war is unsatisfactory. The obvious inconsistencies about Churchill being in power and ordering the destruction of the computers (only ever mentioned in a TV show and the subsequent book and completely unsourced)

The story about the drawings being destroyed is obviously false. Two computers are known to have been taken by GCHQ to Eastcotte at the end of the war. The people who operated them would obviously need manuals and programming handbooks and the engineering support staff would need design drawings and details of how the thing worked. Plus there would have been successor machines within GCHQ.

There's a story not being told here, probably because it's still secret, but what we have here is speculation and not verified in any way, and not really Wikipedia material. — Preceding unsigned comment added by 86.25.231.164 (talk) 10:42, 5 June 2011 (UTC)

Turing complete not important

This prargraph is not convincing:

Whilst Colossus featured (limited) programmability and was the first of the electronic digital machines to do so, it was not a true general purpose computer, not being Turing-complete. It was not then realized that Turing completness was significant, and most of the pioneering modern computing machines (eg, the ABC machine, the Harvard Mark I electro-mechanical relay machine, the Stiebitz Bell Labs relay machines, Konrad Zuse's first two designs, ...) weren't either.

Being Turing complete is not a big deal. Even Conways game of life has been shown to be Turing Complete. It has been shown that the Zuse Z3 was Turing complete. This machine did not differ that much from the Analytical engine or the ABC. It is quite possible that the Colossi were Turing complete. At least theorectically. In that it could have been possible to program the machine to perform an arbitary processing task. The issue of theoretical Turing Completion is over rated. The real issue is practical Turing Completion. In that respect all these machines failed to make the grade and so did the Zuse Z3. It was not until the EDSAC that a machine became practically Turing Complete

I would tend to doubt that the Colossi were Turing-complete, actually. For one, the only test/compare capability they had was whether or not to print out counters at the end of each loop if they were greater than a certain hand-set value. For another, there was no real program, and certainly no conditional branch. They really were incredibly specialized to the job of collecting statistical information used to break a particular coding machine. Very ground-breaking technology, but not ground-breaking architecture. Noel (talk) 02:12, 16 Jan 2005 (UTC)

---

However one may judge the importance of Turing completeness in this or that early machine, the Colossus were in fact the first programmable digital electronic computers. They were anticipated in each of these dimensions by other designs (programmability by the Analytical Engine; electronic by the ABC machine and some of the analog computers; digital by the Analytical Engine and the ABC machine), but in combination, Newman and crew were first. Their programability (even if limited) made them general purpose machines in a non-trivial sense.

The point about Turing Completeness is important only by way of getting across a distinction amongst various computing designs -- one that is important theoretically if not in practice (for all machines since the EDVAC). Readers may benefit, if marginally, from inclusion of this point. At least they will have links to follow if they're curious. Thus, I judge it to be 'mostly harmless'. I would keep the paragraph. ww 16:31, 5 Apr 2004 (UTC)

The amount of programmability was really limited. About the only thing that was "programmable" (configurable, really) in any general way was which bit conditions (and combinations thereof) would cause counters to increment. The rest was all very specialized to the FISH cipher; e.g. the ability to configure what the bit patterns were on the various wheels which generated the keystream. Hardly "progamming" as it's thought of today. It is really incorrect, IMO, to compare the programmability of Babbage's Analytical engine (which was real programmability, in the modern sense) with the limited configurability (which I think is a much more appropriate word) of the Colossus. Noel (talk) 02:12, 16 Jan 2005 (UTC)

Professor Benjamin Wells of the Departments of Computer Science and Mathematics of the University of San Francisco has published an academic paper that is relevant to this.

Wells, Benjamin (18 November 2010), "Unwinding performance and power on Colossus, an unconventional computer", Natural Computing, doi:10.1007/s11047-010-9225-x, ISSN 1567-7818

In it he states that "a UTM (Universal Turing machine) could have been implemented on a clustering of the ten Colossus machines installed at Bletchley Park". So, despite it not being a general-purpose machine, Colossus could be said to be Turing complete. I agree that being Turing complete is not a big deal, but some continue to regard it as being effectively synonymous with being general purpose. --TedColes (talk) 16:14, 28 October 2011 (UTC)

Turing's Colossus participation

According to History of computing, Alan Turing was a major participant in the development of Colossus

--- He was a major participant in the code breaking efforts at Bletchley Park and contributed several mathematical insights, both to breaking the Enigma code and the Lorenz code. He also built the "bombe" there, an electromechanical code breaking device for the Enigma code. He didn't play a major role in design or construction of Colossus; that was Newman's deal.

See http://www.computer50.org/mark1/turing.html and http://www.turing.org.uk/turing/scrapbook/ww2.html --AxelBoldt

--- Okay, I'll update Alan Turing's article to include that paragraph...

--- As of September 2, 2011, the article refers no participation from Alan Turing at all. Is that true? It is certainly against everything I read ever since I first read the Turing article on the My Computer encyclopedia from Orbis Publishing in 1984. A brief history of Computing says Turing designed the Colossus. Is Wikipedia failing to state the single most important fact about Colossus, the identity of its designer? That would be quite ridiculous, don't you think? --Ignacio Agulló

All right, now I believe Turing didn't build the Colossus (by the way, I am upset about being misled for about 27 years). So, I tried to shorten my previous comment, but the change got rolled back.--Ignacio Agulló — Preceding unsigned comment added by 91.117.138.142 (talk) 16:18, 20 February 2012 (UTC)

Most authors who have studied Colossus say that, other than Turingery, Turing made little or no direct contribution to the development of the breaking the Lorenz cipher. According to his biographer, Andrew Hodges, Turing had been away from Bletchley Park in the US from November 1942 to April 1943, and whilst there, as well as sharing Bombe secrets, he had studied the scrambling of voice communications at Bell Labs. From September 1934 onwards, he spent an increasing amount of his time at HMGCC, Hanslope Park, working on voice scrambling. However, there seems little doubt that he and his ideas were well known to the developers of the techniques for breaking the Lorenz cipher, so his ideas, particularly the use of statistical techniques - as in Banburismus - probably made a significant indirect contribution to the development of Colossus. --TedColes (talk) 15:07, 3 September 2011 (UTC)

There was a documentary on BBC 2 called "Code-Breakers Bletchley Parks Lost Heroes" http://www.bbc.co.uk/programmes/p00l9j3g where it is made clear who are the key contributers to breaking the Lorenz code. Bletchly park was split into teams and Turing wasn't in that group. While Turing has been widely recognised for his accomplishments in the field of computer science, there were a great many exceptional minds gathered at Bletchly park and it would be a mistake to underrate these other individuals. The history of colossus required feats of code-breaking, mathematics and engineering and it is unlikely that Turing's expertise was needed at any of these stages and was certainly unmentioned in the documentary and would certainly be insignificant compared to Flowers' contribution to Colossus.

The abilities of the others is currently understated on wikipedia in part due to the original secreacy. i.e. John Tiltman is described as showing "considerable skill at cryptanalysis." When the the main source calls him "Bletchley Park's finest cryptanalyst on non-machine ciphers".

Tetron76 (talk) 13:18, 31 October 2011 (UTC)

never turned off claim not plausible

Having been one whose experience with electronic hardware goes far enough back to have burned fingers on hot tubes, I find this claim rational, but not very believable. It is certainly true that thermal stresses at power on and power off time reduced tube life, and so avoiding those stresses by avoiding power cycles is a rational approach. However, real equipment must be powered down to make repairs, add new attachments, fiddle around and so on. Since nearly all tube equipment uses high voltages, working on powered up tube gear is most always dangerous. I cannot believe the Colossi were turned on and stayed on till the end of the War. Unless someone can provide some evidence for this, I'll come back and revise after a decent interval. ww 15:21, 7 Jul 2004 (UTC)

Several websites (including [6]) repeat the claim. — Matt 15:49, 7 Jul 2004 (UTC)

That may be so, but the ones I can trace all seem to stem from a claim reported from an interview with Sale. I suspect an underlying exagerration for effect taken (wrongly) by a reporter. Tube equipment had regular failures -- it ran hot (induces failures, perhaps most inevitably in economically manufacturable capacitors), it used considerable current (induces failures, largely from heating effects), high voltages (induces failures), it was dangerous to work on if not switched off (heat, high current, and high voltages), and so on. My doubts are not allayed, alas (and alack too). ww 17:49, 9 Jul 2004 (UTC)

Alas for your alack, this claim is also repeated in Randall (1977):

"Flowers' belief, which turned out to be fully justified, was that given the appropriate design practises, switching circuit networks involving even a large number of valves could be made to work reliably, if the equipment could be left on permanently." (emphasis mine)

The same claim is repeated in Johnson, The Secret War:

"There was some opposition to the proposal. Valves had a reputation for unreliability, but Flowers pointed out that from Post Office and BBC experience valves that were never switched off were very reliable." (emphasis mine).

His source was an interview with Flowers himself! So I'd say that this one is pretty solid. Noel (talk) 04:31, 17 Dec 2004 (UTC)

Have just noticed Flowers comments. I still suspect some skew in the meanings here. Flowers' observation is quite correct. But note that he is not reported to have said 'and so we never turned the Colossii off'. I still think that this is engineering hyperbole with regard to the claim about perpetual power on for the machines. Great resistance to turning them off, fix and fiddle as much as possible next to really hot and high voltage stuff, and so on, but... Since Flowers has passed on (and I suppose so have all the others who would know) I think we'll have to remain in ingnorance of the exact fact. But I still doubt it. Those things get hot, and if you look at the photos (and Sales' site for more detail) this is not a machine that is laid out for absolute minimum of little tiny places that are hard to reach. It looks as though they quite sensibly used some sort of ready made rack system and took what they got for serviceablity access. Rarely turned off (and great relutance to turn off, and rules against routine turn off for any reason) seems to me to be about right. ww 19:29, 28 Feb 2005 (UTC)

Since I wrote the above, I have gotten a bunch more Colossus material, including the 3 articles (by Flowers, Coombs, and Chandler, respectively) in Annals of History of Computing, and I can now solidly back up the claim that they were in fact not turned off:

"Most of the machines [out of 10 total - JNC], having been installed and handed over, had their valve heaters on literally until the end of the war. There is little doubt that expansion and contraction of valve heaters being switched on and off caused many valve failures in computing equipment built soon after the war." (from Chandler, Installation and Maintainence of Colossus, pp. 262).

This continual uptime was no doubt in part due to the intense operational requirements, but I'm pretty sure that even without that, Flowers' views on attaining reliability would have kept them on. Station X by Michael Smith contains a direct quote from Flowers on this issue:

"I knew that if you never moved them and never switched them off they would go on forever." (pp. 193)

Given the very large number of valves in these things (2,400 in the Mark II's - by way of comparison, the Pilot ACE had only about 800) I'm sure they didn't want to have to look for dead tubes!

There is much more of great interest in these articles (e.g. Chandler's note that the tubes were operated at only 25% of their maximum power dissipation, which reduced heat output and also helped with tube life), but I haven't the energy to type it all in! BTW, I have this recollection that Flowers would not be the best source for operational details of the Colossi - he was the chief designer, but was not at BP. Noel (talk) 03:43, 1 Mar 2005 (UTC)

"Since nearly all tube equipment uses high voltages, working on powered up tube gear is most always dangerous."

Not really. With appropriate precautions the danger is extremely small. Anyhow such concerns do not generally stop engineers developing cutting edge technologies during wartime. Tabby 13:50, 16 March 2007 (UTC)

Remember that Flowers came from a telephone exchange engineering background. Telephone exchanges are never powered off - the only time they have no power is when power has failed. Individual components might have their fuses removed but as often as not components and circuits were designed to be swapped out live. Flowers would have been experienced and skilled in designing the machine to be permanently on and to have components replaced without a power down. Colossus was actually built from telephone exchange parts so the same principles hold true. 86.178.121.5 (talk) 14:59, 9 March 2012 (UTC)

How much electricity it took to run?

I'm curious to know how much electricity to run ? — Preceding unsigned comment added by Shirishag75 (talk • contribs) 19:36, 2 November 2012 (UTC)

The Colossus rebuild at The National Museum of Computing take some 8.5KW when running. The original would have been vey similar. Krmurrell (talk) 08:15, 4 November 2012 (UTC)

Not “fixed program”?

I don't think that the description of "fixed-program, single-purpose computer with variable coefficients" is appropriate for the first sentence of the lead. Colossus is widely described as "programmable" (See: “Randell, Brian (1980), "The Colossus", in Metropolis, N.; Howlett, J.; Rota, Gian-Carlo (eds.), A History of Computing in the Twentieth Century (PDF), pp. 47–92, ISBN 978-0124916500” and "The Colossus Gallery, The National Museum of Computing") or "semi-programmable" (see: "Colossus Rebuild Project, Bletchley Park National Codes Centre") There is no doubt that the logic function that implemented Tutte's "1+2 break in" was programmed and that the system was developed to perform “wheel breaking” as well as “wheel setting”. I am therefore reverting the lead to the phrase “that was at all programmable.” --TedColes (talk) 10:54, 21 February 2013 (UTC)

Just because something is in a printed source, that doesn't mean we should include it, if it's not accurate. People may describe Colossus as 'programmable', but given the common modern meaning of that term ('stored program'), its use for Colossus is likely to be misleading, and I think we should eschew it. Pretty much any change to what the machine did/counted (i.e. logical function to be performed and counted) required changing switches/jumpers. The paper tapes (the only other method of entering infomation) only ever entered data, not control information. A better word to describe Colossus is 'configurable'; 'programmable' is highly misleading to the average reader. Noel (talk) 18:39, 15 February 2014 (UTC)

This proposal is a radical departure from previous practice. Historical descriptions should be sensitive to the context at the time. Comparing Colossus with the Atanasoff–Berry Computer which was fixed function requires a description of the flexibility of what it could perform. It was deliberately designed to have a great deal of ability to do far more than the original functional specification. To limit "programmable" to stored-program systems because of subsequent developments seems to me to downgrade the achievement. Would Noel re-classify ENIAC as re-configurable, not programmable? --TedColes (talk) 19:17, 15 February 2014 (UTC)

I'd have to investigate Eniac a bit more, and ponder for a bit, before I could say. As I understand it, it was initially designed to need 're-wiring' (via pluggable wires) to do different computations. They soon discovered that this made switching from problem to problem too lengthy, so they developed a 'standard' wiring, added a decoding unit, and the 'programming' was done by setting 'portable function tables' (which I think were like ROM, but done with switches) to include both the 'program' and some read-only data. (This is hard to find out about - it happened later on in the machine's life. The best source I have is "High-Speed Computing Devices" [Engineering Research Associates, 1950].) Again, I would need to check, but I think that was the only way the machine was programmed, via the switches - programs were never read in the way data could be. So on a functionality spectrum which reaches from things like Colossus on one end, to a full stored-program computer on the other (with the ABC about where Colossus is, since both were special purpose machines that couldn't really be used for more else, although the ABC could probably handle a slightly wider range of problems than Colossus), it lies between the ABC and a SPC. It was 'configurable' in the sense I used of Colossus, but across a far broader range of problems. I'm not sure there is a single word that captures all that?

I think the problem with saying (in effect) 'we need to be sensitive to the language used at the time' is that I don't think that's viable for an encyclopaedia, because today's readers don't speak that language (by and large). We have to write it in today's language. To use the word 'programmable' in a meaning which does not match its meaning today is to run a very high risk of leaving the wrong impression in the minds of our readers - surely not a good thing. Noel (talk) 20:01, 25 February 2014 (UTC)

Wheel breaking

Oh, BTW, a quick observation about the system was developed to perform “wheel breaking” as well as “wheel setting”. The Colossus was originally designed/developed only to perform wheel setting. Some time later, one of the cryptanalysts worked out that it could also be used to do wheel breaking, and modifications to help do that (e.g. rectangling - see above for descriptions of changes made to Mark II Colossi) were made to one or more of the later Colossi. I don't have time to track down a reference right now, but if it's needed, i would be happy to do so. Noel (talk) 14:52, 1 March 2015 (UTC)