As an update.

This is a viral marketing scheme for the movie 2012.

Similar to the marketing done by the movie Cloverfield where they claimed that ships were disappearing in Asian waters.

No its not hush hush just not taken too much notice of.

http://xfacts.com/x1.htm

I can confirm here that there does appear to be plentiful work about. Based on that I'm going to try to get a second GPU card up.

The server is utterly choking right now under the load... You will likely not be able to maintain your high levels for very much longer unless Travis does something else to lighten the load on the server...

I noticed a problem in the binaries and code I put on the code download page. I removed them to do some fixes, but they should be available tonight or at the latest tomorrow morning.

^^ From the front page..

Does this mean when you put it back up, that we Cuda users can download the app and try crunching on that? The download link you posted http://milkyway.cs.rpi.edu/milkyway/download/code_release/

Is a little confusing ..to say the least.

Yeah, I'll have a binary for OS X that you can try and crunch with.

I noticed a problem in the binaries and code I put on the code download page. I removed them to do some fixes, but they should be available tonight or at the latest tomorrow morning.

Please keep this thread to the topic of GPU discussions. Thanks

Yes I know this..its http://milkyway.cs.rpi.edu/milkyway_gpu/

My comment was about what is CURRENTLY going on.

They are building the CUDA app for MW_GPU. It's almost done, apart from checkpointing. When Travis has finished this, according to one of the other threads, he will work on getting some WUs out over at MW_GPU.

The ATi app, developed by Cluster Physik (a third party, he did it to help the science be computer faster) is being developed alongside MW - he's in constant conversation about the new app.

The ATi app was made because the source code went public and CP wanted to help. Unfortunately this is what made the server get so many requests, after a WU which did take 10-30 minutes, now only takes 30 seconds.

This action caused MW_GPU to be spawned. If it hadn't, we'd still be several months back doing CPU calculations. In essence, the MW_GPU side is being born out of necessity, and will (hopefully) make everyone happy :)

Given the MW_GPU latest update (i.e. February and 'Almost There'), and that Travis has almost finished the CUDA app, I'd give it another month or so until MW_GPU is up and running for work - maybe not fully operational at that point, but in the right direction (from own personal experience I make this estimate).

But why then is a ATI app out already, when Cuda is the one that is supported by BOINC?

The ATI app only processes CPU WUs on an ATI GPU.

Ah ic.

But why would someone create an app to do CPU work on a GPU when they know the server can't handle the requests? That doesn't make any sense to me..

Try because they did not know that the server could not scale up to the demand.

But why then is a ATI app out already, when Cuda is the one that is supported by BOINC?

The ATI app only processes CPU WUs on an ATI GPU.

So..nobody here knows when the Cuda will be released at all? ATI is out and has bugs..

The MW_GPU project is running a different application entirely. The point of MW_GPU is to run longer searches (100x longer hopefully) to get more detailed info.

So it's not as easy as just porting the MW ATi app from here to there.

This project is still declared as Alpha status, so rule of thumb is DONT EXPECT ANYTHING, and be glad when something happens :) The original CUDA status updates were back in January, and if my personal experience is anything to go by, writing a new scientific application in an almost completely new language doesn't happen overnight (or in a week, or a month).

I would be happy even with a spinning 3d model of the our galaxy..(the Milkyway) That could maybe update itself from what the project finds.

As far as I am concerned screen savers waste computer cycles that could best be used for crunching.