| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 8
|
|
| Author |
|
|
zombie67 [MM]
Senior Cruncher USA Joined: May 26, 2006 Post Count: 228 Status: Offline Project Badges:
|
Why did this WU get labeled Invalid?
---------------------------------------- If I read the posts correctly, the 500 WUs that had the recent problem were awarded full credit against claimed. Since I received 1/3 credit, I assume this is a different problem. I am using the stock BOINC client. TIA ![]() |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello zombie67,
Just looking at the quorum, I notice that ytour result was the second returned. The third result was returned at 03:59:36. Then a fourth result was sent at 04:03:58, four and a half minutes later. When it was returned at 07:53:47, your result was declared Invalid and the other 3 were labelled Valid. Apparently your result differed from the other 3. Lawrence |
||
|
|
zombie67 [MM]
Senior Cruncher USA Joined: May 26, 2006 Post Count: 228 Status: Offline Project Badges:
|
Yep. I understand the methodology. But *why* was it declared invalid? And why did I not get awarded the points accordingly?
----------------------------------------Also, if it was really invalid, then why award any points at all? ![]() |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
It was really invalid. Give your computer a health check, and check your result history. Have you changed anything in your computing environment recently?
From time to time an otherwise healthy computer will mangle a result. It happens. But if there is a persistent problem we should try to track it down. |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Also, if it was really invalid, then why award any points at all? 50% of the median is the rule in effect since the beginning of November, same as the Extreme Outlier. Consideration was, that client side the process ran without quality failure indicators, thus 50% granted for work performed. This 50% is in deviation to most other BOiNC run projects, where an invalid gets granted zero.
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
zombie67 [MM]
Senior Cruncher USA Joined: May 26, 2006 Post Count: 228 Status: Offline Project Badges:
|
The machine is fine. No history of failures at all. No changes.
----------------------------------------As for that "50%" post, that is clearly nonsense since I was awarded 33%. I am asking for someone to do analysis on the result. Not guessing. ![]() |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Hold on, 50% of the median is the rule, not 50% of what u claim!
----------------------------------------There is no guessing.... your result deviated from the other 3, who agree. My machine is 100%, yet it produces 1 in 200 a real invalid.... the larger the model, the more chance there is it hits very high memory regions...... and memory does fail, sometimes just intermittently.... only needs 1 bit to go the wrong way once. We had 163,265 results yesterday....unless there are 'errors' logged, it becomes next to impossible to determine what went wrong and why it went wrong...... on these volumes impossible to follow up without clear pointers. PS, What i can say with probability looking at the times of the 4, the claims average and your deviated claim & time, that u had a likely restart..... have a look in the log that sits in your Result Detail pages.
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 2 times, last edit by Sekerob at Dec 13, 2006 9:00:27 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
As Sekerob says, the work unit history is totally transparent, and totally consistent. No guessing involved.
If the unit failed due to the WCG software, then it is indistinguishable from a failure due to a hardware error. Again, as Sek says, it may be worth checking whether the work unit crashed and started from zero. |
||
|
|
|