| 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: 4
|
|
| Author |
|
|
bieberj
Senior Cruncher United States Joined: Dec 2, 2004 Post Count: 406 Status: Offline Project Badges:
|
I noticed last night that one of my HFCC resulted in an inconclusive. Digging in a bit further, another task was submitted and was also declared inconclusive and someone else was asked to cast a tie-breaker.
When the tie-breaker came back, mine was declared valid, but the other one invalid. I looked at the wingman's data and all three of them were identical except for the core client version number and the time stamps. Is this expected behavior? |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
So,
----------------------------------------Result with suffix 0-- had an inconclusive. Result with suffix 1-- was send out and did not match 0-- Result with suffix 2-- was then send out and matched 0-- but not 1-- 1-- was declared invalid. If you post the quorum detail, we can reconstruct the order of distribution and it makes sure nothing is lost in translation, that is if the summary order above is not correct. The Result logs are basic catchers of events on the client to at all get into the verification process. Usually if there is a critical fault on the client, it will show with 'error' status as soon as received. The verification process compares bit for bit, so I have to assume that first and last agreed.
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Mar 19, 2009 3:22:25 PM] |
||
|
|
bieberj
Senior Cruncher United States Joined: Dec 2, 2004 Post Count: 406 Status: Offline Project Badges:
|
Nope. Not that way. Seems like it started out with a initial quorum of 2 and the initial two disagreed and number 2 agreed with number 1.
HFCC_ t1_ 00012286_ TrkB_ 0001_ 2-- Valid 3/18/09 17:00:52 3/19/09 02:59:09 4.08 70.8 / 69.8 HFCC_ t1_ 00012286_ TrkB_ 0001_ 1-- Valid 3/18/09 08:03:51 3/18/09 16:58:47 6.19 68.9 / 69.8 HFCC_ t1_ 00012286_ TrkB_ 0001_ 0-- Invalid 3/18/09 07:56:40 3/18/09 15:01:09 3.74 82.1 / 34.9 |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
That's perfectly correct then. An initial Quorum 2 bit for bit comparison was done and as you noted the tie-breaker was needed to determine which of the first 2 was getting the seal of approval. Effectively an HFCC task operating according the HCC standard.
----------------------------------------
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Mar 19, 2009 3:41:03 PM] |
||
|
|
|