| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: Help Cure Muscular Dystrophy - Phase 2 Forum
Thread: WU 170% (NOT) done? |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 14
|
|
| Author |
|
|
alged
Master Cruncher FRANCE Joined: Jun 12, 2009 Post Count: 2346 Status: Offline Project Badges: 
|
i am a newbie too and do appreciate the right questions of kismetix and the answers from the seniors (and their efforts to simplify)
---------------------------------------- |
||
|
|
Steve W
Advanced Cruncher Joined: Dec 9, 2005 Post Count: 110 Status: Offline Project Badges: 
|
I've got a similar WU issue to the topic now - currently at 179% and still running.
Looking at my WU - CMD2_ 2522-2PBN_ A.clustersOccur-3CXE_ A.clustersOccur_ 1_ 9923_ 11923_ 0 - I would expect it to be processing positions 9923 to 11923. However, looking at the results file for this it is currently plowing through position 13501. It appears to have "forgotten" when to stop. I guess it will just carry on going through the raw data until all positions are completed, which from the raw data file is position 25638. FYI: Recommended WCG BOINC client. |
||
|
|
Steve W
Advanced Cruncher Joined: Dec 9, 2005 Post Count: 110 Status: Offline Project Badges:
|
Looks like I spoke too soon. As soon as it got to 200% it stopped.
Interestingly (for some anyway) the result log shows: <core_client_version>6.10.58</core_client_version> Note the two calls to "called boinc_finish". There would normally only be one entry like this. |
||
|
|
TPCBF
Master Cruncher USA Joined: Jan 2, 2011 Post Count: 1931 Status: Offline Project Badges: 
|
This is complicated and means that percentage completed refers to the time that the program expects to run before returning a partial result. But the algorithm may decide to run shorter or longer. TPCBF thought that his work unit was taking longer than expected because it had gotten caught in an endless loop. However, SekeRob pointed out that the screenshot said that the program had reached a checkpoint in the code only seconds before TPCBF made the screenshot, so it was still running well, not looping. Well, though I do not stare at the progress of all the WUs crunching along, this was the first (and so far only time) that I ever noticed a behavior like this. And returned by now more than 4500 WU. And with all the  That is why Sekerob urged TPCBF to continue running it. And sure enough, it completed in about 2 more hours.The original size estimate is just a guess in HCMD2. Lawrence strange things that happened in the last few weeks on WCG in general, I rather thought it as odd. Ona general note, maybe it would be a good idea to add a description as you now have given for all projects in a FAQ thread. Just as the 12h cutoff at the CEP2 project threw me off, as other projects (like HFCC) are happily keep crunching for far more than that. Ralf  |
||
|
|
|