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: 13
|
![]() |
Author |
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi all,
----------------------------------------Please take a look at this link I dunno why this WU was inconclusive, so I have 2 questions :- a. Why this must have happened and what can I do for it to not happen again? (First time it has happened though) b. Would I get the time/credit for it or no? [Edit 2 times, last edit by Former Member at Nov 4, 2008 10:07:27 AM] |
||
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Please see our FAQ on FAAH/DDDT Zero Redundancy. Randomly, about 1 in 10, a first result for these projects is marked inconclusive and second copy send out. After that comes back a validation takes place and credit awarded according the Quorum 2 rules.
----------------------------------------Added: Can't' see anyone's result details, need copy/paste of detail, but looking at Quorum 2 / Init distro 3, it seems the first 2 were not in agreement or 1 of the first 2 had another condition preventing validation. cheers
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Nov 4, 2008 11:00:56 AM] |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I dunno if this is what you are looking at or not
|
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Or this
<core_client_version>6.2.12</core_client_version> <![CDATA[ <stderr_txt> INFO:[12:27:51] Start AutoGrid... autogrid: autogrid4: Successful Completion. INFO:[12:31:09] End AutoGrid... Beginning AutoDock... autodock4: *** WARNING! Non-integral total charge (-1.5 e) on ligand! *** 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: -8.06 Finished Docking number 1 Finished Docking number 2 Finished Docking number 3 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 Restoring grahics. bestEnergy: -9.994520 maxGenSeen: 10328 AG Check: Found receptor.A.map Beginning AutoDock... Restoring grahics. bestEnergy: -9.994520 maxGenSeen: 10328 AG Check: Found receptor.A.map Beginning AutoDock... autodock4: *** WARNING! Non-integral total charge (-1.5 e) on ligand! *** INFO: Setting num_generations: 10000 About to enter main loop...(dockings already completed: 11) 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 Finished Docking number 26 Finished Docking number 27 Finished Docking number 28 Restoring grahics. bestEnergy: -9.994520 maxGenSeen: 10328 AG Check: Found receptor.A.map Beginning AutoDock... autodock4: *** WARNING! Non-integral total charge (-1.5 e) on ligand! *** INFO: Setting num_generations: 10000 About to enter main loop...(dockings already completed: 29) Finished Docking number 29 Restoring grahics. bestEnergy: -9.994520 maxGenSeen: 10328 AG Check: Found receptor.A.map Beginning AutoDock... autodock4: *** WARNING! Non-integral total charge (-1.5 e) on ligand! *** INFO: Setting num_generations: 10000 About to enter main loop...(dockings already completed: 30) Restoring grahics. bestEnergy: -9.994520 maxGenSeen: 10328 AG Check: Found receptor.A.map Beginning AutoDock... autodock4: *** WARNING! Non-integral total charge (-1.5 e) on ligand! *** INFO: Setting num_generations: 10000 About to enter main loop...(dockings already completed: 30) Finished Docking number 30 Restoring grahics. bestEnergy: -9.994520 maxGenSeen: 10328 AG Check: Found receptor.A.map Beginning AutoDock... autodock4: *** WARNING! Non-integral total charge (-1.5 e) on ligand! *** INFO: Setting num_generations: 10000 About to enter main loop...(dockings already completed: 31) Finished Docking number 31 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 ________________________________________________________________________________ autodock4: Successful Completion on "World Community Grid device" ________________________________________________________________________________ INFO:[06:06:19] Start AutoGrid... autogrid: autogrid4: Successful Completion. INFO:[06:08:04] End AutoGrid... Beginning AutoDock... INFO: Setting num_generations: 27000 About to enter main loop...(dockings already completed: 41) Finished Docking number 0 ________________________________________________________________________________ autodock4: Successful Completion on "World Community Grid device" ________________________________________________________________________________ called boinc_finish </stderr_txt> ]]> |
||
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Okay, so this task was issued to a device that has not reached the "reliable" status (See FAQs) and thus not one but two copies were initially sent out. Since there was no agreement, they were rated "inconclusive", so the 3rd will have to determine which is OK.
----------------------------------------If you click on the "Inconclusive" link on the Result status page you can see if there is something odd. Note that there are a number of "benign" messages that read as e.g. "warning". Yes, another FAQ lists the most common ones you can ignore. See http://www.worldcommunitygrid.org/forums/wcg/viewthread?thread=21501 for the FAQ index. cheers
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
One of the links I got
----------------------------------------http://www.worldcommunitygrid.org/forums/wcg/viewthread?thread=6105#120888 Can't find the second one, the one which you said about benign warnings and such :( [Edit 1 times, last edit by Former Member at Nov 4, 2008 2:25:47 PM] |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi shirish,
Look under 4. BOINC Messages and Problem Resolution in the The Start Here Forum Frequently Asked Questions Index at http://www.worldcommunitygrid.org/forums/wcg/viewthread?thread=21501 This post ( BOINC: "Failed to get VersionInfo size: 1812" and other Innocent Result log entries at http://www.worldcommunitygrid.org/forums/wcg/viewthread?thread=15646 ) has a number of 'benign' messages. Lawrence |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The third one agreed with the other guy and hence the WU was invalid. can somebody point out why the WU was invalid? Some line or something which tells me what was wrong in that WU?
Also is this a random thing, or does it mean my PC or my BOINC client has issues? Although one of the things is that my client and machine just got a HPF2 valid thing (and it has a much larger quorum) So it would be nicer to know as well. |
||
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
shirish,
----------------------------------------See nothing in your Log of alarming nature, to me, but do note you're running a beta client, early beta 6.2.12. We ran through 6.2 point releases pretty quick. WCG's version will be at least release 6.2.26 if not higher. You don't tell which of the 2 "inconclusive" is yours. If you post the final quorum detail, could speculate. Possible the job had a wrong bit, which is enough to render a result invalid in a "bit for bit" comparison and given it was deemed "inconclusive" means that in principle it ran OK, possible interrupted during the run? Very occasionally I have one post a power out, so unless you have more results going bad, it's going to stay a secret, understanding that you got 50% credit from the whatever was given to the other 2 in recognition of the effort in vain. sorry [Edit: The "Finished Docking number 0" near the end suggest something did get lost... was the task once or twice restarted ? Normally should not harm though! ]
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Nov 5, 2008 1:10:38 PM] |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
shirish, See nothing in your Log of alarming nature, to me, but do note you're running a beta client, early beta 6.2.12. We ran through 6.2 point releases pretty quick. WCG's version will be at least release 6.2.26 if not higher.] Thank you for sharing that, then would make sure that in the next cycle i.e. jaunty we have atleast 6.2.26 (or if there is something more specific you may know about, lemme know so atleast can ask to the debian/ubuntu packaging people) . I do know its a moving target. You don't tell which of the 2 "inconclusive" is yours. If you post the final quorum detail, could speculate. Possible the job had a wrong bit, which is enough to render a result invalid in a "bit for bit" comparison and given it was deemed "inconclusive" means that in principle it ran OK, possible interrupted during the run? Mine was the third/last one. Will put up the stats after this post. Don't want to muddle everything in one post. Very occasionally I have one post a power out, so unless you have more results going bad, it's going to stay a secret, understanding that you got 50% credit from the whatever was given to the other 2 in recognition of the effort in vain. sorry [Edit: The "Finished Docking number 0" near the end suggest something did get lost... was the task once or twice restarted ? Normally should not harm though! ] Yes, I do have power cuts, something like once a day, but I do also have an APC UPS which thankfully does a graceful system shutdown couple of minutes before its batteries run out. Also please correct me if I'm wrong. In case, one shutdowns the system and restarts the system, boinc will start working from last checkpoint, wouldn't it, then where should it fail. I'm not bothered much by the credit (as in points given) but its interesting to learn and know what went and could go wrong and if any steps I could take to prevent the same. Its also an off-chance that it might be a random experience but still give my best shot to understanding the same. |
||
|
|
![]() |