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."

Comments

Re:Why?

[MindStalker]

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.

Re:Distributed computing...

[Kj0n]

...irks me a little. When I give away my CPU cycles what do I get in return?

Well, one thing you get in return is some extra heat and the certainty that you just helped change the climate by using more energy.

Business model?

[Bluedove]

How's this for a preliminary stab at a distributed computing organization business model:

Each computing unit (whatever size) is allocated a price based on demand. You can use the units at the given price, or you can generate the computing units (have other peoples jobs run on your machine) at $0.50 on the dollar. Your account is tracked/stored with the organization.

The benefits are as follows:

-Your spare computing units are automatically contracted out at a competitive price. You can (arguably) make money doing it with all those spare computers laying about.

-You can stockpile computing units to be used later in your research. (Make your computer work for you even while in the reading phase).

-If you have a project where you need units, but don't have time to contribute, you can simply buy the distributed processing time.

-You could enhance your effective computing time by contributing at peak times (when the price is highest) and processing at off peak times (when the price is lowest). You will effectively have improved your computer.