Distributed Climate Prediction For Linux: Pending
saintp writes "Inspired by earlier discussions about distributed computing initiatives, I emailed the good folks at Climateprediction.net to inquire about a linux client. And, the good news: There will be one. No update yet to their system requirements, but here's what they told me: 'There is certainly a Linux version planned (in fact, already existing), but
we are a small team and can only set up the infrastructure to support
distributed experiments under one O/S at a time. Running climate models is
substantially more ambitious in terms of machine requirements, data
generated, security headaches etc than any other distributed computing
project we know of, so developing a generic O/S independent client is simply
not feasible. As soon as the Windows version is safely launched, the Linux
version will be our next priority.' Hopefully, we'll see it sometime in November or December."
Weather reports are not bad though, I just pay for them by viewing annoying advertizing. The projects that really annoy me are the ones used to design drugs to fight cancer or some other like disease, because the information from these projects will be used by pharmaceutical companies to sell me drugs!
If we are going to use ditributed computing to solve problems, the solutions should really be free or discounted for the general public, because they donated their computers cycles, and shouldn't be forced to "pay" twice.
Basically it boiles down to the fact that mallicious users sending false data would completly destroy this project. In Seti, if some mallicious user sends a I have found ET packet, it can easily be checked and confermed (which I believe is automated even) same with all the other distributed systems so far, a user sending back important info is rare enough that it can be checked. While in weather predictions each user will probably be solving a piece of a puzzle so each users will be sending back significant amounts of info not just occasiall rare users. So each user can't be checked. So the checking mechanism has to be done client side, a virtual impossibility if you ask me.
I'm guessing they are not using java because distributed computing is very much about speed. A few distributed computing clients have hand written (or hand optimized) assembly code running the bulk of the computation. Java would be a serios step backwords.