Already any progress in granting credits for MCTE WU's ??
Or did I miss it somewhere ?

As was reported before, it will be AT LEAST mid-March before the project team can deal with the credit granting process for this class of WU failures, and maybe longer. They did say they would grant the credit in due course, but they are focused on fixing run time errors at this time. The cause of the Max time errors has been isolated and fixed so people should not see any more of them. But the credit granting process takes time.

http://boinc.bakerlab.org/rosetta/workunit.php?wuid=9429375

using AMD Athlon(tm) 64 Processor 3700+

What gives ?

Another possible cause is when the CPDN controlling process hadsm3_* is killed, leaving the worker process hadsm3um_* running. The Science Application (a.k.a. "worker") can only be killed using task manager or by a reboot.

I'm not using graphics at all running R@H.
And the other thing doesn't ring a bell to me.

Not running the Boinc screensaver? Hmm then it seems likely that some part of Rosetta isn't being killed when switching and causing the error. I wonder if this is part of the problems Ralph is looking to find? I don't know much about Rosettas' processes/app.

sorry

tony

For these, unless you've uncovered a different problem, you can stop BOINC and restart it and the workunit will start over and should complete normally.

http://boinc.bakerlab.org/rosetta/result.php?resultid=6869420

Never had it before.
Just a computer which couldn't flush (installed R@H last week) because of ZA and I've changed that so it could flush.
Now all of the WU's are like the above.
And couldn't upload any WU's this afternoon.
Reason can be ????

Well about those 20 second WU's just cuirous how much credit do you think should be granted... most my jobs that run 5000 seconds get about 14 credits. this may be low or high for the avarage .. but anyway asuming 5000 seconds =14 credits then 1 credit is about 357 seconds (~6 min) so um.. i hate saying it but it probaly isnt worth the effort to worry about loosing a 20 second job (unless you pay for your UL/DL bandwith...

yes i love to see credits for work done and credits if an error occours beyond your control... but personaly every time i reboot one of my computers it looses back to the last benchmark (probaly miniuts or more of work + 3-6 min to reboot) so i expect to loose credits now and then

sorry for the soapbox lecture

I know/understand ......................the reasons to chose this project.
I'm glad this is cleared up.

While I _totally_ agree that clear and frequent communication is a major "good thing" in general, ................... even _if_ it can be solved, and THEN tell us either "okay, we'll do that" - or "we'd like to, but we can't, and here's why".