Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
World Community Grid Forums
Category: Completed Research Forum: Discovering Dengue Drugs - Together - Phase 2 Forum Thread: extremely long running DDD2 w/u |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 37
|
Author |
|
themoonscrescent
Veteran Cruncher UK Joined: Jul 1, 2006 Post Count: 1320 Status: Offline Project Badges: |
"In which case you were wise to abort! but had you persevered to your error, would you both have received some credit?"
----------------------------------------My original wingman was the person who completed (and whose was validated), in 1 hr, the person who took 20.50 hrs received their copy after I aborted mine, not before, so not sure what difference my abort would have made on him/her receiving any credit, as I aborted before they even began crunching. 1st) Me, WU Aborted. 2nd) 1 hr, Valid (original wingman). 3rd) 20.50 hrs, Error. 4th) 1 hr+, Valid. Cheers. [Edit 1 times, last edit by themoonscrescent at Feb 7, 2011 5:18:09 PM] |
||
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges: |
I just discovered I had one of these that's been running for 19 hours. 3 other wingmen reported errors in anywhere from 36-114 hours. It's been aborted
----------------------------------------
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
|
||
|
seippel
Former World Community Grid Tech Joined: Apr 16, 2009 Post Count: 392 Status: Offline Project Badges: |
I'm in the process of testing several of the work units mentioned in this thread (and the other thread) to attempt to recreate the problem of very long work units that some users have reported. Seippel We were able to recreate this error and the research team has found a way to identify these work units ahead of time. A check is being added for when type C work units are built that will filter this specific problem in the future (although it's always possible that other problems could cause work units to run long). Thank you to all that reported work units names that had this problem. Seippel |
||
|
pramo
Veteran Cruncher USA Joined: Dec 14, 2005 Post Count: 703 Status: Offline Project Badges: |
I'm in the process of testing several of the work units mentioned in this thread (and the other thread) to attempt to recreate the problem of very long work units that some users have reported. Seippel We were able to recreate this error and the research team has found a way to identify these work units ahead of time. A check is being added for when type C work units are built that will filter this specific problem in the future (although it's always possible that other problems could cause work units to run long). Thank you to all that reported work units names that had this problem. Seippel Awesome! |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
There's also the opposite, in some residual tasks. Normal clean log, wingman normal clean too:
ts02_ d143_ pqb008_ 0-- 95711 Valid 2/5/11 13:39:05 2/12/11 07:04:21 0.45 4.5 / 4.7 ts02_ c464_ pca014_ 0-- 1479931 Valid 2/3/11 14:31:23 2/12/11 00:11:53 0.48 8.7 / 7.6 |
||
|
GB033533
Senior Cruncher UK Joined: Dec 8, 2004 Post Count: 198 Status: Offline Project Badges: |
In the end, both of the long-runing wus that ended in error for me, also ended in error for all but one of the wingmen;
----------------------------------------ts02_ c283_ sr67b1_ 5-- 617 Error 2/9/11 02:21:21 2/10/11 06:03:52 20.06 201.5 / 201.5 ts02_ c283_ sr67b1_ 4-- 617 Error 2/7/11 19:09:58 2/9/11 02:03:13 13.11 203.1 / 203.1 ts02_ c283_ sr67b1_ 3-- 617 Too Late 2/3/11 19:13:16 2/4/11 10:04:02 1.04 23.5 / 23.5 ts02_ c283_ sr67b1_ 2-- 617 Error 2/3/11 18:28:57 2/8/11 11:41:02 18.18 219.5 / 219.5 ts02_ c283_ sr67b1_ 1-- 617 Error 2/1/11 13:53:51 2/3/11 18:14:30 13.13 207.8 / 207.8 ts02_ c283_ sr67b1_ 0-- - Detached 2/1/11 13:53:50 2/3/11 19:09:43 0.00 0.0 / 0.0 ts02_ c283_ sr78b0_ 4-- 617 Error 2/11/11 20:16:43 2/12/11 10:06:08 10.63 209.5 / 209.5 ts02_ c283_ sr78b0_ 3-- 617 Error 2/9/11 03:18:52 2/11/11 20:16:33 12.85 193.1 / 193.1 ts02_ c283_ sr78b0_ 2-- 617 Too Late 2/3/11 13:27:40 2/3/11 16:10:39 1.35 23.7 / 23.7 ts02_ c283_ sr78b0_ 1-- 617 Error 2/1/11 13:53:59 2/9/11 03:18:41 55.07 188.9 / 188.9 ts02_ c283_ sr78b0_ 0-- 617 Error 2/1/11 13:53:51 2/3/11 13:04:32 13.09 204.3 / 204.3 Is it strange that the status for the only successful wingman changed from 'pending validation' to 'too late'? But we all received some credit for our efforts, which was nice. All of my remaining pv have now been validated, so I just need another 9.5 days to reach silver. |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
snip: "It is strange..."
Just added a few lines on that "Too Late" conversion to the Result Status page, xyz FAQ. Essentially it's to get any Wingmen-less PV results, for which there never will be a valid wingman moving through the system and pass them through the credit-granting process. --//-- |
||
|
|