| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Retired Forums
Forum: Member-to-Member Support [Read Only]
Thread: 2 hrs 50 mins and still 0.0%?? |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 27
|
|
| Author |
|
|
seasmi
Cruncher Joined: Nov 17, 2004 Post Count: 1 Status: Offline Project Badges: 
|
Seems what i have the same problem. more then a hour of work and 0.0 percentage completed. i have athlon xp 2200+.
First unit completed in 5+ hours. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Seems what i have the same problem. more then a hour of work and 0.0 percentage completed. i have athlon xp 2200+. First unit completed in 5+ hours. Ok..problem solved, finally its showing 0.4% BUT that was after 9 hours of processing timeat 0.0% then duno for some reason the program reset the CPU time to 0 and started recouting again. WTHell..Wasted My WhOle Day Of ProcEssinG TIme! |
||
|
|
erich.rutz
Cruncher Joined: Nov 18, 2004 Post Count: 2 Status: Offline Project Badges: 
|
I have the similar problems on my machine.
That may change if the run-time (at the moment 1 hour for the curent protein) increases. But if I stop the computing (by right-click 'Exit' on the task tray icon) and restart the tool then the CPU time is reset to 0 and calculation restarts from the beginning. Is this some bug which needs to be fixed? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
^Sounds like a bug to me-
|
||
|
|
erich.rutz
Cruncher Joined: Nov 18, 2004 Post Count: 2 Status: Offline Project Badges:
|
I have the similar problems on my machine.
That may change if the run-time (at the moment 1 hour for the curent protein) increases. But if I stop the computing (by right-click 'Exit' on the task tray icon) and restart the tool then the CPU time is reset to 0 and calculation restarts from the beginning. Is this some bug which needs to be fixed? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Now... if it were me running WGC... I'd do it like this... everyone gets say 5 WU's... the same 5 WU's.... it does 2 things.... First it validates the machine is producing exactly the same information.... validates your machine... second.. it allows a rough index of capability of your machine.... so... knowing what your machine has in the way of processing power and if you tend to leave it running or not.... then I can schedule bigger or smaller WU's to you based on some likelyhood that it will complete within 24 hrs. So far.. I'm working on my 3rd WU... my first one took about 9 hrs; the second one took like 33 hrs and this one ( my 3rd) looks like it's gonna take roughly 26 hrs....
Now.. saying all this... if you can "Guest-a-mate" when your WU is gonna finish... if it finishes after the time they post the "scores / Results" then you get at least another 24 hrs before you get to see your results... but his is just one poor slob's ideas of how to use this.... you know.... give the bigger work units to the systems / complexes with the greater capacity... but we will all get what we get the next time.... and all the WU's have to be processed.... it would really be intersting to see how many WU's there are in aggrigate, and how many have been completed... of course.. it's also possible... that as some of these WU's complete and the results are returned.. they have a pgm that analizes them.. and in some cases.. a new "WU" could be created after the anaylisis.. so if they initially thought there would only be say... 100 initial WU's (Gawd.. it's just a # I pulled outa the air for purposes of discussion and example).. based on the results being returned additional WU's could be generated either liniarly or exponentially... or not at all... Like I said.. this is just one slob's ideas.. your milage may vary |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I'm not sure if it works but check out this thread http://www.worldcommunitygrid.org/forums/wcg/...read=409&lastpage=yes
And read the one from Dataman |
||
|
|
Dataman
Ace Cruncher Joined: Nov 16, 2004 Post Count: 4865 Status: Offline Project Badges: 
|
It appears that for some machines in certain configurations, abruptly terminating the application causes it to either restart the calc's or stall. This would seem to indicate that in certain conditions it fails to set a restart checkpoint when terminated. What seems to work is to pause the application (snooze) before you either shut down the application or shut down the machine (I have tested both on multiple XP machines).
----------------------------------------Hope this helps. BTW ... Thank you crystalnox ... U R 2 kind. <dataman>  |
||
|
|
Alther
Former World Community Grid Tech United States of America Joined: Sep 30, 2004 Post Count: 414 Status: Offline Project Badges: 
|
Seems what i have the same problem. more then a hour of work and 0.0 percentage completed. i have athlon xp 2200+. First unit completed in 5+ hours. Ok..problem solved, finally its showing 0.4% BUT that was after 9 hours of processing timeat 0.0% then duno for some reason the program reset the CPU time to 0 and started recouting again. WTHell..Wasted My WhOle Day Of ProcEssinG TIme! A "work unit" consists of various data including the protein sequence. The longer the sequence the "harder" it is to predict the fold. Longer sequence proteins take longer to process (sometimes much longer). Due to the nature of the work, it's impossible to predict how long any specific work unit may take. i.e. it's non-determinsitic. That's really the beauty of putting this on a grid: it's a difficult computation problem. Sometimes a work unit may not "converge" as we call it. This means it just hasn't found any way to fold this specific protein in a given amount of time and gives up. When it determines it can't converge it just stops working on it, sends it back (telling us it didn't converge) and you get a new work unit. However, it will try very, very hard before it gives up. This would explain why you saw it processing for probably 4 hours and still be at 0.0%...then suddenly you saw it go to 0.4% and the CPU time went down. Points-wise, you should still get credit for the effort though. Have some faith in that you really are helping to promote our understanding of the human proteome. If this was easy to do, we wouldn't have put it on the grid!
Rick Alther
Former World Community Grid Developer |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Seems what i have the same problem. more then a hour of work and 0.0 percentage completed. i have athlon xp 2200+. First unit completed in 5+ hours. Ok..problem solved, finally its showing 0.4% BUT that was after 9 hours of processing timeat 0.0% then duno for some reason the program reset the CPU time to 0 and started recouting again. WTHell..Wasted My WhOle Day Of ProcEssinG TIme! This would explain why you saw it processing for probably 4 hours and still be at 0.0%...then suddenly you saw it go to 0.4% and the CPU time went down. Points-wise, you should still get credit for the effort though. No..unfortunetly it did'nt give my any credit at all, no added CPU time or points..  |
||
|
|
|