WE don't NEED Cuda........

The project has had enough trouble keeping up with the demands for work from 'normal' rigs.......much less OCd ones like mine...

Well, maybe (bacause of project can't feed tasks to all) you will start to remove your OCing and halve your systems ?
It's nonsense, to cut processing power for such considerations. Well, lets close BOINC, why we need BOINC, we have too much processing power with BOINC. And let's close project too. No project - no demands for work from project.... Nonsense, nonsense...

Our goal to provide as much processing power as we can provide. It's the meaning of volunteer DC project. And staff members goal is to utilize this power most effectively. If you can't get work here, go to einstein@home for example - ther have something to offer to your rigs.

I agree with the post about CUDA not being ready, but I'm going to crunch them. It's useless to crunch them on Beta so if Main is where it has to be done, then that's what I have to work with and that's where my resources will go.

---

I am still waiting for Eric to respond.........

His ears must be smoking by now...............

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

I join the boycott. I have a 88GYT on the way as Xmas present form the Mrs, but i'll stick to crunching in OSX.

This was no where near ready.

Thank you Satan...

Now there's a statement you don't hear every day!

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

I join the boycott. I have a 88GYT on the way as Xmas present form the Mrs, but i'll stick to crunching in OSX.

This was no where near ready.

Thank you Satan...

Now there's a statement you don't hear every day!

But it has very correct meaning in this context BTW ;)

It's all Santa's fault you know.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Hey, leave me alone.

It would be interesting to know the actual reason for CUDA being thrown straight to main. Considering none of the known issues were fixed, no validated results from the 20 minutes Beta testing.

---

Well, I tried today to use the modified package for CUDA and I have about 35 WUs with Compute error !!!
At first I though that it was the GPU o/c to blame, but the errors keeping coming also without the o/c.

Some examples:
http://setiathome.berkeley.edu/result.php?resultid=1096809308
http://setiathome.berkeley.edu/result.php?resultid=1096809307
http://setiathome.berkeley.edu/result.php?resultid=1096800160

Using 6.4.5 with 180.48 on two SLi-Enabled 8800GTS cards.

I really don't want to think that "SetiCUDA" was given away without the correct amount of testings.
I also don't know what these Compute errors do to my seti-account. Does this marks me as a "bad-participant" ?

---

Hey, leave me alone.

It would be interesting to know the actual reason for CUDA being thrown straight to main.

The Devil made them do it...

Sorry, couldn't resist.

---

Hey, leave me alone.

It would be interesting to know the actual reason for CUDA being thrown straight to main. Considering none of the known issues were fixed, no validated results from the 20 minutes Beta testing.

My statement remains..........

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Mark, I don't think we'll ever get a true answer to your question.

---

Well, I tried today to use the modified package for CUDA and I have about 35 WUs with Compute error !!!
At first I though that it was the GPU o/c to blame, but the errors keeping coming also without the o/c.

Some examples:
http://setiathome.berkeley.edu/result.php?resultid=1096809308
http://setiathome.berkeley.edu/result.php?resultid=1096809307
http://setiathome.berkeley.edu/result.php?resultid=1096800160

Using 6.4.5 with 180.48 on two SLi-Enabled 8800GTS cards.

I really don't want to think that "SetiCUDA" was given away without the correct amount of testings.
I also don't know what these Compute errors do to my seti-account. Does this marks me as a "bad-participant" ?

1) CUDA don't like SLI
2) Sure not, why "you" bad participant if "their" app faulty. No connection.
As good participant (not good, but active participant - more correctly) you just need to report errors (or, if you have programming skills you could also try to debug this errors from open-source code BTW).

Just a couple more pennies ...

Each time there was a leap in processing capabilities there have been increases in the amount of actual investigation done. What I mean is this, my first tasks in classic took 30 some hours to process. A year or so later they doubled the amount of actual calculations done one each issued task increasing the processing time. But, by that time had faster machines and the increased processing time was coroded by the increased processing speed.

This has occurred at least 4 times since. Each time the amount of work done on each task has increased. This is likely to occur again with the increased capability to process the work at hand.

To get CUDA work you have to have the right video cards, enough VRAM, the latest version of BOINC, and no app_info file. COnditions that almost make it so that you have to go out of your way to get CUDA work.

Yes, there are issues. And, there is already differences between 6.4.5 and 6.5.0 in what is done in CUDA... There may be issues with versions of the video drivers, but, as with *ALL* game bug reports the first reply is always, did you update your drivers to the latest version???

So, we are seeing the same thing with BOINC now with CUDA... the video driver versions are important too ...

again, just my pennies ...

---

Mark, I don't think we'll ever get a true answer to your question.

Probly not.........

But I think I know the answer........

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Mark, I don't think we'll ever get a true answer to your question.

Probly not.........

But I think I know the answer........

nvidea did most of the homework on this one........it certainly was to their benefit....

And then they persuaded the Seti folks to launch it.....bad move on the admins' part.........

More vid cards for nVidea.........simple truth.

Whether or not they enhanced the offer with cash.......we may never know.

Unless someone fesses up.......

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Last one out the window loses........

The truth will out in the end......

Criminy..........we are looking for Seti in the outlaying regions.......

Do you really think you could fool us this close to home??


Whatever.........tell us true or write us off.

I AM WAITING......

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

When I say boycott - it's simply not crunching CUDA until everything is "fixed" and it's ready for primetime...
Really easy to do. Just don't crunch until an optimum is reached.

Very nice, and how we will know what needs to be corrected ?
BTW, it's relative small % of errors now. IT don't exceed gain from speed increase. And invalid results here can't harm project - each result has wingman (it will harm only for CUDA agains CUDA validation though), but on beta it has much more chances to come into master database unchecked now.

What needs to be corrected? Have a look at the boards...

---

- Luke.

When I say boycott - it's simply not crunching CUDA until everything is "fixed" and it's ready for primetime...
Really easy to do. Just don't crunch until an optimum is reached.

Very nice, and how we will know what needs to be corrected ?
BTW, it's relative small % of errors now. IT don't exceed gain from speed increase. And invalid results here can't harm project - each result has wingman (it will harm only for CUDA agains CUDA validation though), but on beta it has much more chances to come into master database unchecked now.

What needs to be corrected? Have a look at the boards...

Or ignore them.......as seems to be the case right now.......

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Today I know 4 or 5 bugs of CUDA SETI. And know workarounds for 2 of them. So net sum is 3 bugs that need to be corrected.

Now look on Windowz from M$. They have much bigger budget and their programs have much more bugs than 3.
Maybe you put your energies to boycott for Windows? ;)

Today I know 4 or 5 bugs of CUDA SETI. And know workarounds for 2 of them. So net sum is 3 bugs that need to be corrected.

Now look on Windowz from M$. They have much bigger budget and their programs have much more bugs than 3.
Maybe you put your energies to boycott for Windows? ;)

I am not boycotting...........yet.

Just venting........

Keep a stream of work for my rigs and I shall be OK..............

And I am 2 rigs short of a full load right now..........

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster