Cluster Cracks Jupiter's Moons
YourHero writes: "Using the 256-cpu/500MHz Velocity I Cluster (64 Dell PowerEdge boxes installed Aug 1999) Cornell researchers have explained some of the wild moon orbits around Jupiter by running a 1-billion-year simulation. Abstract , abstract (presented at AAS/Division for Planetary Sciences), and news coverage [spaceflight now]. I saw no information on run time, but Aug 1999-present represents an upper limit somewhat short of 1 billion years."
Maybe these moons were used to protect copyrighted material.
However, they do seem to provide access to anyone with a hard problem to solve. I cant find anything further about this on their website.
Anyways, did the simulator simply match reality here? Or was there something more to this?
(from their page)
I see now
http://monkeyserver.com --- weeeeee
Cluster Cracks Jupiter's Moons
I saw no information on run time
Quote from the second paragraph: In a three-month computing marathon, the Velocity I cluster at the Cornell Theory Center was able to mimic cosmic conditions over eons that would cause physical perturbations in the moons of Jupiter.
See? It's not THAT hard to find it when you actually read the article!
You can accomplish anything you set your mind to. The impossible just takes a little longer.
I'm an undergrad at Cornell, currently assisting with some magnetohydronamics research (Parallelizing a FORTRAN program written by a bunch of russian scientists... yay...). I'll probably be using the cluster at the end of the year, and I must say I'm rather impressed with it. It's not as cool as some that Cornell has had in the past, however they are very willing to let many individuals use it, and I find it great that I get to be involved with supercomputing at an undergraduate level. (Some day I hope to be a computational physicist).
Also, slightly off topic, I've been hired to create and install/maintain a linux cluster of 6 linux boxes connected with 100 base-T Eithernet, and I have about $3500 to spend for it. Anyone have any suggestions about what to use? I'm thinking 1.3-1.4 GHZ Athelon processors, a small drive, 256-512 megs of ram...
Also, can anyone tell me why using Red Hat would be a bad idea... it'll just be running FORTRAN programs non-stop, with a bit of SSH and SCP, nothing kernel-intensive. In the Space Sciences Building where I work, we use Red Hat and Solaris, and I don't really see much point using a "better" distribution, like Debian (as I have never really used it much before).
Cheers,
Justin
Debian's greatest strength is that it's easily kept up to date, with new and debuged packages, etc. I prefer it for personal use and on servers that I need to keep up to date for security fixes.
But since what you're running is computational efforts, on a static cluster, using consistant tools, you could use anything. The kernel is still just the kernel, what makes it RedHat or Debian is the rest of the packages that you're not using anyway.
And most of all, you already have experience with RedHat.
Bob-
The Ludwig von Mises Institute. The reasoning individuals economics