Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 24
Posts: 24   Pages: 3   [ Previous Page | 1 2 3 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 4781 times and has 23 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Inconclusive

Interesting discussion.

Strangely, 1 of my 2 machines (a 32-bit Core DUO) (having crunched WCG for over a year) had its 1st HFCC WU validate, then the next 3 (all reported at the same time) return Status Inconclusive. I nottice that for whatever reason, 1 of the 3 WUs took a REALLY long time (~12 CPUhours) to complete, versus 3~4 hours for the others. Maybe that's why the validator is taking a cautious approach.

My other machine (a 64-bit Core2DUO running the HFCC 32-bit app under the 64-bit BOINC client) has reported 6 WUs, all with similar runtimes, and all validated.

73,
J. Whalen, N6KTC
[Mar 14, 2009 11:19:37 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Bearcat
Master Cruncher
USA
Joined: Jan 6, 2007
Post Count: 2803
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Inconclusive

All my wu's from my octo mac show inconclusive. Have to wait for the others to clear hoping they are valid
----------------------------------------
Crunching for humanity since 2007!

[Mar 15, 2009 1:28:23 AM]   Link   Report threatening or abusive post: please login first  Go to top 
rkar22
Cruncher
Joined: Nov 17, 2004
Post Count: 48
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Inconclusive

My first result for this project returned an error sad :

HFCC_ 00000652_ TrkB_ 0000_ 2-- In Progress 3/15/09 07:48:12 3/16/09 15:29:00 0.00 0.0 / 0.0
HFCC_ 00000652_ TrkB_ 0000_ 1-- Error 3/13/09 16:29:08 3/15/09 07:40:40 19.66 82.9 / 0.0
HFCC_ 00000652_ TrkB_ 0000_ 0-- Inconclusive 3/13/09 16:16:47 3/14/09 10:35:55 3.05 59.3 / 0.0

but the result log:

<core_client_version>6.2.28</core_client_version>
<![CDATA[
<stderr_txt>
Failed to get VersionInfo size: 1812
INFO:[21:13:09] Start AutoGrid...

autogrid: autogrid4: Successful Completion.
INFO:[21:15:13] End AutoGrid...
Beginning AutoDock...
INFO: Setting num_generations: 10000
About to enter main loop...(dockings already completed: 0)
_maxGenSeenSoFar changed: 2500
_maxGenSeenSoFar changed: 2626
_maxGenSeenSoFar changed: 2758
_maxGenSeenSoFar changed: 2896
_maxGenSeenSoFar changed: 3041
_maxGenSeenSoFar changed: 3194
_maxGenSeenSoFar changed: 3354
_maxGenSeenSoFar changed: 3522
_maxGenSeenSoFar changed: 3699
_maxGenSeenSoFar changed: 3885
_maxGenSeenSoFar changed: 4080
_maxGenSeenSoFar changed: 4285
_maxGenSeenSoFar changed: 4500
_maxGenSeenSoFar changed: 4726
_maxGenSeenSoFar changed: 4963
_maxGenSeenSoFar changed: 5212
_maxGenSeenSoFar changed: 5473
_maxGenSeenSoFar changed: 5747
_maxGenSeenSoFar changed: 6035
_maxGenSeenSoFar changed: 6337
_maxGenSeenSoFar changed: 6654
_maxGenSeenSoFar changed: 6987
_maxGenSeenSoFar changed: 7337
_maxGenSeenSoFar changed: 7704
_maxGenSeenSoFar changed: 8090
_maxGenSeenSoFar changed: 8495
_maxGenSeenSoFar changed: 8920
_maxGenSeenSoFar changed: 9367
_maxGenSeenSoFar changed: 9836
_maxGenSeenSoFar changed: 10328
Updating Best Energy for WU: 0.00
Finished Docking number 0
Updating Best Energy for WU: -5.65
Finished Docking number 1
Finished Docking number 2
Finished Docking number 3
Updating Best Energy for WU: -5.69
Finished Docking number 4
Finished Docking number 5
Finished Docking number 6
Finished Docking number 7
Finished Docking number 8
Finished Docking number 9
Finished Docking number 10
Finished Docking number 11
Finished Docking number 12
Finished Docking number 13
Finished Docking number 14
Finished Docking number 15
Finished Docking number 16
Finished Docking number 17
Finished Docking number 18
Finished Docking number 19
Finished Docking number 20
Finished Docking number 21
Finished Docking number 22
Failed to get VersionInfo size: 1812
Restoring grahics. bestEnergy: -5.696200 maxGenSeen: 10328
AG Check: Found receptor.A.map
Beginning AutoDock...
INFO: Setting num_generations: 10000
About to enter main loop...(dockings already completed: 23)
Finished Docking number 23
Finished Docking number 24
Finished Docking number 25
Updating Best Energy for WU: -5.70
Finished Docking number 26
Finished Docking number 27
Finished Docking number 28
Finished Docking number 29
Finished Docking number 30
Finished Docking number 31
Updating Best Energy for WU: -5.70
Finished Docking number 32
Finished Docking number 33
Finished Docking number 34
Finished Docking number 35
Finished Docking number 36
Finished Docking number 37
Finished Docking number 38
Finished Docking number 39
Finished Docking number 40
Finished Docking number 41
Finished Docking number 42
Finished Docking number 43

________________________________________________________________________________

autodock4: Successful Completion on "World Community Grid device"

________________________________________________________________________________

INFO:[03:40:45] Start AutoGrid...

autogrid: autogrid4: Successful Completion.
INFO:[03:45:55] End AutoGrid...
Beginning AutoDock...
INFO: Setting num_generations: 27000
About to enter main loop...(dockings already completed: 44)
Finished Docking number 0

________________________________________________________________________________

autodock4: Successful Completion on "World Community Grid device"

________________________________________________________________________________

called boinc_finish

</stderr_txt>
]]>

looks very similar to my wingman's:

<core_client_version>6.4.7</core_client_version>
<![CDATA[
<stderr_txt>
Failed to get VersionInfo size: 1812
INFO:[14:36:43] Start AutoGrid...

autogrid: autogrid4: Successful Completion.
INFO:[14:37:03] End AutoGrid...
Beginning AutoDock...
INFO: Setting num_generations: 10000
About to enter main loop...(dockings already completed: 0)
_maxGenSeenSoFar changed: 2500
_maxGenSeenSoFar changed: 2626
_maxGenSeenSoFar changed: 2758
_maxGenSeenSoFar changed: 2896
_maxGenSeenSoFar changed: 3041
_maxGenSeenSoFar changed: 3194
_maxGenSeenSoFar changed: 3354
_maxGenSeenSoFar changed: 3522
_maxGenSeenSoFar changed: 3699
_maxGenSeenSoFar changed: 3885
_maxGenSeenSoFar changed: 4080
_maxGenSeenSoFar changed: 4285
_maxGenSeenSoFar changed: 4500
_maxGenSeenSoFar changed: 4726
_maxGenSeenSoFar changed: 4963
_maxGenSeenSoFar changed: 5212
_maxGenSeenSoFar changed: 5473
_maxGenSeenSoFar changed: 5747
_maxGenSeenSoFar changed: 6035
_maxGenSeenSoFar changed: 6337
_maxGenSeenSoFar changed: 6654
_maxGenSeenSoFar changed: 6987
_maxGenSeenSoFar changed: 7337
_maxGenSeenSoFar changed: 7704
_maxGenSeenSoFar changed: 8090
_maxGenSeenSoFar changed: 8495
_maxGenSeenSoFar changed: 8920
_maxGenSeenSoFar changed: 9367
_maxGenSeenSoFar changed: 9836
_maxGenSeenSoFar changed: 10328
Updating Best Energy for WU: 0.00
Finished Docking number 0
Updating Best Energy for WU: -5.65
Finished Docking number 1
Finished Docking number 2
Finished Docking number 3
Updating Best Energy for WU: -5.69
Finished Docking number 4
Finished Docking number 5
Finished Docking number 6
Finished Docking number 7
Finished Docking number 8
Finished Docking number 9
Finished Docking number 10
Finished Docking number 11
Finished Docking number 12
Finished Docking number 13
Finished Docking number 14
Finished Docking number 15
Finished Docking number 16
Finished Docking number 17
Finished Docking number 18
Finished Docking number 19
Finished Docking number 20
Finished Docking number 21
Finished Docking number 22
Finished Docking number 23
Finished Docking number 24
Finished Docking number 25
Updating Best Energy for WU: -5.70
Finished Docking number 26
Finished Docking number 27
Finished Docking number 28
Finished Docking number 29
Finished Docking number 30
Finished Docking number 31
Updating Best Energy for WU: -5.70
Finished Docking number 32
Finished Docking number 33
Finished Docking number 34
Finished Docking number 35
Finished Docking number 36
Finished Docking number 37
Finished Docking number 38
Finished Docking number 39
Finished Docking number 40
Finished Docking number 41
Finished Docking number 42
Finished Docking number 43

________________________________________________________________________________

autodock4: Successful Completion on "World Community Grid device"

________________________________________________________________________________

INFO:[17:41:06] Start AutoGrid...

autogrid: autogrid4: Successful Completion.
INFO:[17:41:43] End AutoGrid...
Beginning AutoDock...
INFO: Setting num_generations: 27000
About to enter main loop...(dockings already completed: 44)
Finished Docking number 0

________________________________________________________________________________

autodock4: Successful Completion on "World Community Grid device"

________________________________________________________________________________

called boinc_finish

</stderr_txt>
]]>

whose result is marked as Inconclusive. The only significant (?) difference I can see is the client version.

BTW, it's a useful feature to have access to the results logs of one's co-crunchers.
[Mar 15, 2009 9:01:13 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Inconclusive

The first of my inconclusives had its wingman workunit come in and validated. I'm in my way back to being reliable again. biggrin


Right. My most of my inconclusives have validated by now, and I've had some workunits get validated directy, so I'm reliable again. Woohoo biggrin
[Mar 15, 2009 9:09:46 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Inconclusive

I have finished crunching 8 HFCC and ALL have a Q of 2. My results are coming in as PV not Inconclusive, does that mean I have been randomly selected to be a "validator"?
[Mar 15, 2009 11:15:23 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
Re: Inconclusive

"Pending Validation" generally means the "Init distribution" was 2 or more.
"Inconclusive" generally indicates the initial result(s) could not be validated and additional copies are submitted. The suffix of a work unit and the distribution times also tell what the order was of distribution.

You need to understand that if someone's device was chosen to be re-checked, there's a wingman needed, usually a reliable device; yes it could be yours too. The information you can glean as per para 1 above is indicative.
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
----------------------------------------
[Edit 2 times, last edit by Sekerob at Mar 15, 2009 11:24:51 AM]
[Mar 15, 2009 11:19:42 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Inconclusive

I apologize for not reading the "zero redundancy" formula carefully before posting. blushing
This is a new PC so there it has no reliability factor yet , thus it is I who am forcing a "wingman" to be created and when my results are returned, because apparently the reliability factor has not "fallen below the required level" it is marked as "PV" rather than "Inconlusive"
[Mar 15, 2009 11:42:34 AM]   Link   Report threatening or abusive post: please login first  Go to top 
boulmontjj
Senior Cruncher
France
Joined: Nov 17, 2004
Post Count: 317
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Inconclusive

Un petit résumé de ce fil en français pour ceux que ça intéresse.
Si j'ai tout bien compris, si vous avez une unité qui est retournée "non concluant", pas de panique, le WU va alors être soumis à un autre cruncher pour vérifier le résultat.
Le 0 point n'est donc pas définitif et vous devez attendre que le ou les autres crunchers aient retourné le résultat du calcul.

Many french speeking people does not understand very well english.
I tried to shortly translate what have been told about inconclusive results in this thread. wink
Doing this, it can help to provent french speeking people to ask the same questions a couple of time and make you spend hours to answer.
----------------------------------------

Rejoignez nous et visitez le site de l'équipe France ici http://www.grid-france.fr
----------------------------------------
[Edit 3 times, last edit by boulmontjj at Mar 15, 2009 6:54:10 PM]
[Mar 15, 2009 12:40:40 PM]   Link   Report threatening or abusive post: please login first  Go to top 
jamie.kotlewski
Cruncher
Joined: Feb 7, 2007
Post Count: 32
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Inconclusive

I'm getting an abnormal amount of errors from one of my hosts. However, some will come back Valid. Is this normal? Should i post an error message to see what you guys think? They are massive so I will see what I should do first. It is my fastest machine that is losing the WU's so I would hate to be wasting time on it if there is a problem I can fix. I don't know if a moderator or tech can look at my stats and see the WU's that are going bad?

Thanks,

Jamie
[Mar 16, 2009 11:22:50 PM]   Link   Report threatening or abusive post: please login first  Go to top 
JmBoullier
Former Community Advisor
Normandy - France
Joined: Jan 26, 2007
Post Count: 3716
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Inconclusive

As far as I remember, for the time being the only errors which have been reported are described in this thread Autodock 4 Error
If your errors are of the same nature (jobs aborting straight at the beginning with messages like
autodock4: ERROR: autodock4: ERROR: 260 runs requested, but only dimensioned for 256.
Change "MAX_RUNS" in "constants.h".
in the Result log then simply ignore them.

Otherwise please give us more details so we have a chance to tell you if it is the WUs or this device which have problems.

Edit: As a test you can provide a link to one of your Result logs. Maybe we can see them now that we can look at the Result logs of our peers in a quorum.

Cheers. Jean.
----------------------------------------
Team--> Decrypthon -->Statistics/Join -->Thread
----------------------------------------
[Edit 1 times, last edit by JmBoullier at Mar 17, 2009 3:46:56 AM]
[Mar 17, 2009 3:42:53 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 24   Pages: 3   [ Previous Page | 1 2 3 | Next Page ]
[ Jump to Last Post ]
Post new Thread