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."
Forgive me if I don't know much about it, but why should it be so hard to make it platform independant? I would think most of the proccessing to be done would be just a recompile away from another platform, and sockets on *nix are virtually identical to on the PC. So what's the big thing that's making this so difficult for them?
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.
Why aren't these folks using Java? Remember write once, run everywhere? It's got an authentication mechanism, and the whole 'you can converse with the originating server' schtick seems to make it ideal.
"Draco dormiens nunquam titillandus."
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.
Demonstrant's Open Source Tools
Does anyone know if running DC to examine NEAR objects is feasible/practical/needed? This would be to assist researchers with tracking of "doomsday" asteroids that have a chance of hitting Earth. I know that there are not enough people actively watching the sky right now, and we are not currently prepared to engage an asteroid. Still, if we knew one was coming, steps maybe could be taken. Or we could argue about it.
Bottom line, would DC to track and predict paths of NEAR's be of any practical use, or not?