There are more than enough entries on this topic already - why not read them instead of adding to the clutter.

I strongly disagree. No specific task for this renewed problem has yet been established. All we do is to put it under the "News" thread.

But I do agree that this was a bit rude.

The problem is LIFE keeps getting in the way of the Admin figuring it out, every time he sits down to do something about the problem something else comes up. First it was that he switched jobs so he had to move his pc's to his new apartment, then he had to move them someplace else, then someone very close to him passed away, then the people he had asked to help him had no clue how to do it. He has said repeatedly the end is in site, hopefully, and as soon as he gets there he will put in the time to get the problems fixed.

What we have is a struggling project that feels it's better to live with some problems then to be shut down and potentially lose everyone. Some people are reporting a 90% error rate on downloads, that still means 10% of the work is getting done. IMHO 10% is better than none at all!

There are more than enough entries on this topic already - why not read them instead of adding to the clutter.

Guess the BOINC estimation isn't that precise after all.

This has been a problem ever since Boinc began, it probably always will be a problem as they use formulas due to them not running an actual test unit on our pc's. This was discussed but discarded, and now the Boinc software 'learns' as we crunch more and more units. The problem is most of us don't just have rooms full of pc's doing nothing else but crunching, even checking our email, or typing in a forum, can change how much time our pc has available to crunch throwing the calculations off.

ps the reason the 'test unit' idea was discarded is that since it doesn't contribute anything to the project the projects feel we should NOT get any credits for it, but we users said 'hey I'm crunching I want some credits for my work'. So now everyone just jumps right into the pool with both feet and up to our necks. The formula IS MUCH better than it used to be, but as I said it will probably never be 100% accurate.

Here is another thread to read for you:
http://asteroidsathome.net/boinc/forum_thread.php?id=131

The nVidia GPU's are not well suited for double precision, this is one reason why there is little or no gain when using them.

It will be soon. I have partially prepared it but have to set to check it via SSH.

Pardon me, but SSE3 WUs are for CPU, while CUDE55 WUs are for GPU.
But I guess you meant that there is no difference in WU generation, right?

I mean that the same file you try to Download from the server 'for CUDA' (= to be processed by CUDA application), someone else will try to Download for CPU
So there is no difference in the WU file (if the file do not exist on the server = Download errors for everyone)

The only difference is that you will process the Downloaded file by CUDA application,
the other computer will use other application (for CPU or again for CUDA - depend what his BOINC asked for)

But aren't tasks with download errors be sent out again automatically?
If not, why not?

Click the links and see - the WU was "sent out again automatically" 10 times and failed on every attempt
(and the server gave up: 'Too many errors (may have bug)' - no more attempts will be made)
 

Both SSE3 and CUDA55 WUs are affected.

There is no difference between "SSE3 and CUDA55 WUs", so if this happens it will happen with any 'type' of WU
(e.g. the same task you receive for SSE3 app someone else will receive for CUDA or AVX or ...)
 

Some of these 'Error while downloading' is yours, the other 8 are your 'wingmates' (quorum partners) - the same WU, 9 tasks:
http://asteroidsathome.net/boinc/workunit.php?wuid=21710924

Really bad is when somebody (me in the case ;) )
Completed the task but there is no other wingmate that can confirm the result
so the final outcome is 'Completed, can't validate' (after 9 Error tasks)
http://asteroidsathome.net/boinc/workunit.php?wuid=20964261

I have removed the next_rpc_delay setting.

Does project status information exist that summarizes number of asteroids characterized, rate of characterization, ultimate goal(s), and unanticipated/unexpected beneficial results of the effort thus far?

New apps show ridiculous crunching time, around 25 hours.

It's not real time. Times should be same as before. Boinc client will adjust time estimation after some complete workunits.

Bin leider dem englischen sprachgebrauch nicht fähig,habe schon versucht ein übersetzungspogramm auf meinem rechner zu instalieren,hab bis jetzt noch nicht das richtige gefunden,würde mich freuen über eure hilfe.