PDA

View Full Version : WCG wu's invalid



BlackAdder
11-24-2006, 11:59 AM
Every one of my WCG FAAH wu's in the last two weeks have been invalid, any one else having this problem or is it just me ???
Name Device Name (javascript:document.boincResultsBean.sortBy.value ='deviceId';document.boincResultsBean.submit();) Status Sent Time (javascript:document.boincResultsBean.sortBy.value ='sentTime';document.boincResultsBean.submit();) Time Due (javascript:document.boincResultsBean.sortBy.value ='dueTime';document.boincResultsBean.submit();) /
Return Time (javascript:document.boincResultsBean.sortBy.value ='returnedTime';document.boincResultsBean.submit() ;) CPU Time (hours) (javascript:document.boincResultsBean.sortBy.value ='runTime';document.boincResultsBean.submit();) Claimed/ Granted BOINC Credit faah0980_ d126n991_ x1AJX_ 01 (javascript:addHostPopup('/ms/device/viewWorkunitStatus.do?workunitId=2441784','statusP op',610,610);) main Pending Validation (javascript:addHostPopup('/ms/device/viewResultErrorLog.do?resultId=8743284','errPop',5 00,700);) 11/21/2006 05:37:17 11/23/2006 06:44:10 7.04 191 / 0 faah0980_ d126n128_ x1AJX_ 00 (javascript:addHostPopup('/ms/device/viewWorkunitStatus.do?workunitId=2441891','statusP op',610,610);) main Invalid (javascript:addHostPopup('/ms/device/viewResultErrorLog.do?resultId=8743606','errPop',5 00,700);) 11/21/2006 05:37:17 11/23/2006 20:22:50 5.60 152 / 32 faah0980_ d126n156_ x1AJX_ 00 (javascript:addHostPopup('/ms/device/viewWorkunitStatus.do?workunitId=2441893','statusP op',610,610);) main Invalid (javascript:addHostPopup('/ms/device/viewResultErrorLog.do?resultId=8743610','errPop',5 00,700);) 11/21/2006 05:37:17 11/24/2006 04:37:03 6.86 186 / 38 faah0980_ d127n373_ x1AJX_ 02 (javascript:addHostPopup('/ms/device/viewWorkunitStatus.do?workunitId=2442013','statusP op',610,610);) main Invalid (javascript:addHostPopup('/ms/device/viewResultErrorLog.do?resultId=8743975','errPop',5 00,700);) 11/21/2006 05:37:17 11/22/2006 12:13:44 4.88 133 / 22 faah0980_ d126n701_ x1AJX_ 00 (javascript:addHostPopup('/ms/device/viewWorkunitStatus.do?workunitId=2442043','statusP op',610,610);) main Invalid (javascript:addHostPopup('/ms/device/viewResultErrorLog.do?resultId=8744065','errPop',5 00,700);) 11/21/2006 05:37:17 11/22/2006 07:07:53 5.35 145 / 31 https://secure.worldcommunitygrid.org/images/spacer.gif
https://secure.worldcommunitygrid.org/images/top.gif (https://secure.worldcommunitygrid.org/ms/viewBoincResults.do#top) https://secure.worldcommunitygrid.org/images/spacer.gif https://secure.worldcommunitygrid.org/images/spacer.gif:icon_cry:

spikey_richie
11-24-2006, 04:45 PM
No problems here, I crunch WCG almost 24/7 except for the occasional Tanpaku or VTU unit.

Which client are you using? Check your device profiles.

BobCat13
11-26-2006, 12:34 AM
Are you using an optimized client? Your claimed credit is too high. Your scientific results aren't invalid, just your claimed credit. They have no way to mark the result "Valid, credit claim too high" so it is just marked "Invalid".

WCG made a change to their BOINC credit system that penalizes very high claims. On the quorum of 3, if PC1 claims 65, PC2 claims 70, and PC3 claims 170, then the claim for PC3 is thrown out and the awarded credit is averaged from PC1 & PC2. In addition, PC3 will only be given 1/2 of the awarded credit of the other PCs. I guess WCG is trying to have everyone run the standard client. You certainly want to avoid using Crunch3r's client on WCG.

Here is the link to the announcement about the change:
http://www.worldcommunitygrid.org/forums/wcg/viewthread?thread=9545

BlackAdder
11-26-2006, 01:52 AM
Hummm...so it seems....I've crunched for them over a year now and just started seeing this done.I have noticed that Boinc wu's get about double the credit as their own program grants so that is why I favor doing WCG on Boinc, besides being able to do rosetta too. I think it completely sucks....however I guess we all are forced to play by their rules. :(
BTW I was using Crunch3r's client......

spikey_richie
11-26-2006, 08:30 AM
WCGAgent has been throttled to run at 60% CPU - there was a huge uproar about 6 months ago.