
I, like many others, joined SETI@home when it first statrted. I was there when, for 6 weeks, they passed out the same 30 work units. After a year or so, I did find out about the previous SETI computing projects, called META and BETA. EAch of which use roughly the same equipment as the SEti@home server farm, and can prcess the data themselves, at near real time.
After that, I switched to distributed.net - left that a year or two later, after a flaw I spotted in their OGR roject went unresolved for 2 years (thats what started phase2) before finally moving to Muon1DPAD.
Not only is muon1 completely british, its also one of the very few 2nd generation projects. That means its not just crunching data its told to crunch, its determining itself, at the client level, what to do. It then evolves based on its own results, and the results of others. Basically, its evolution in action. This method allows it to deal with much larger data streams than other projects. For comparison, a seti@home work unit, and an average muon1 simulation takes about the same time to process. A lattice (or design type, a subproject in the overall design) can have 10^900 (thats a 1 with nine hundred zeros after it) different designs. The current crop of 1000 or so users, can crunch through that, and give a best result (or at least a better result than through conventional design) in about 6-9 months. By contrast, RC5-64 took distributed.net, with 100,000 users almost 3 years to do, by brute force. RC5-64 has a keyspace of around 10^15 keys, and a client on a 1Ghz system was doing maybe a million keys a second.
In the end, muon1 is a small project, run by one person as part of his job, at the RAL in Oxfordshire, and is far more cutting edge in its abilities and methods than the same tired old 'download this datablock, crunch this data block, return the results for this data block, repeat' simplistic method of work.
brute forcing small projects, very 1995...
Andrew Norton - currently building his own 15m radio telescope.