| 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: The Help Cure Muscular Dystrophy Crunching Chart |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 603
|
|
| Author |
|
|
Mysteron347
Senior Cruncher Australia Joined: Apr 28, 2007 Post Count: 179 Status: Offline Project Badges: 
|
Not quite how it works, Speedy.
At 6hrs CPU-time, if a task has not reached 60% then it is stopped,. If it has reached 60%, then it is allowed to continue but if it reaches 12hr CPU-time point it is then stopped regardless. If a task is stopped rather than completes, the results-so-far are returned and the remainder of the task is assigned as back to the queue as one or more descendant tasks. |
||
|
|
Speedy51
Veteran Cruncher New Zealand Joined: Nov 4, 2005 Post Count: 1265 Status: Offline Project Badges: 
|
Not quite how it works, Speedy. At 6hrs CPU-time, if a task has not reached 60% then it is stopped,. If it has reached 60%, then it is allowed to continue but if it reaches 12hr CPU-time point it is then stopped regardless. If a task is stopped rather than completes, the results-so-far are returned and the remainder of the task is assigned as back to the queue as one or more descendant tasks. I understand what you are saying. I will re word my question. If tasks hit the 6 hour wall & the progress bar reaches 100% how do we know how far through the task really is? I thought if a task hits either 6 or 12 hour wall a descendant task is made?  |
||
|
|
armstrdj
Former World Community Grid Tech Joined: Oct 21, 2004 Post Count: 695 Status: Offline Project Badges: 
|
The output file returned is used to determine how much work was done. No need to worry about the jump to 100% at the end.
Thanks, armstrdj |
||
|
|
dango
Senior Cruncher Joined: Jul 27, 2009 Post Count: 307 Status: Offline Project Badges: 
|
Statistics updated on 2011 April 15th : 68.35%
|
||
|
|
Speedy51
Veteran Cruncher New Zealand Joined: Nov 4, 2005 Post Count: 1265 Status: Offline Project Badges:
|
If tasks hit the 6 hour wall & the progress bar reaches 100% how do we know how far through the task really is? The output file returned is used to determine how much work was done. No need to worry about the jump to 100% at the end. Thanks, armstrdj Thanks armstrdj, In boinc manager all tasks run to 100%. Tasks never get to 60% hit the wall then jump straight to 100% So I gess the only way to tell if a task is going to exit at 60% is to look at Elapsed time in BM. If a task finishes between 8 hours & 6 hours 5 minutes I know the tasks have only really been 60% done. Tasks that come in over or under those times I know they are finished completely without any more tasks been created. Thanks for you answers [Edit 1 times, last edit by Speedy51 at Apr 15, 2011 10:07:51 PM] |
||
|
|
gb009761
Master Cruncher Scotland Joined: Apr 6, 2005 Post Count: 2977 Status: Offline Project Badges:
|
Speedy51, alternatively, if you see the message "Finishing early because max runtime has been exceeded.21602.472476" in your Result Log, then that's an even better way to see whether the WU in question completed fully or not.
---------------------------------------- |
||
|
|
Mysteron347
Senior Cruncher Australia Joined: Apr 28, 2007 Post Count: 179 Status: Offline Project Badges:
|
Speedy51, alternatively, if you see the message "Finishing early because max runtime has been exceeded.21602.472476" in your Result Log, then that's an even better way to see whether the WU in question completed fully or not. Perhaps . "Finishing early at xx% complete ... would be more informative, if it could be arranged |
||
|
|
Speedy51
Veteran Cruncher New Zealand Joined: Nov 4, 2005 Post Count: 1265 Status: Offline Project Badges:
|
Speedy51, alternatively, if you see the message "Finishing early because max runtime has been exceeded.21602.472476" in your Result Log, then that's an even better way to see whether the WU in question completed fully or not. I'm aware of this but you need to open each task to check weather it exceeded it's run time.Perhaps . "Finishing early at xx% complete ... would be more informative, if it could be arranged Mysteron347, I like your idea. Another way could be to add another field on your Results Status saying weather it was finished or not. If finished early display % it finished at This would save having to open each task to check. Is this idea do able? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
It is real simple, if it finished between exactly 6 hr, and about 6.2 hrs it stopped early, ie <60%, ANY thing else it finished, except in the very rare case of 12 hrs, then it did not finish but did >60%.
----------------------------------------if at the first check point after 6 hrs, you have less than 60% completed it will stop All time are CPU time, not elasped. [Edit 1 times, last edit by Former Member at Apr 19, 2011 9:29:59 PM] |
||
|
|
Speedy51
Veteran Cruncher New Zealand Joined: Nov 4, 2005 Post Count: 1265 Status: Offline Project Badges:
|
It is real simple, if it finished between exactly 6 hr, and about 6.2 hrs it stopped early, ie <60%, ANY thing else it finished, except in the very rare case of 12 hrs, then it did not finish but did >60%. if at the first check point after 6 hrs, you have less than 60% completed it will stop All time are CPU time, not elasped. Yip I agree that's the best to tell if a task is completely finished. Without adding new features to the result database. [off topic]It would be cool if we had an option to choose if we just wanted to process the shorter tasks (grandchildren)  dreams are free[/off topic]Statistics updated on 2011 April 15th : 68.35% |
|||
|
||||
|
|