| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Beta Testing
Forum: Beta Test Support Forum
Thread: CMD2_0001-GPDAA.clustersOccur-PTN1.clustersOccur_26 -- Too late? |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 9
|
|
| Author |
|
|
pirogue
Veteran Cruncher USA Joined: Dec 8, 2008 Post Count: 685 Status: Offline Project Badges: 
|
I returned a result in 2 days and the others are still In Progess. How could mine be Too Late?
----------------------------------------CMD2_ 0001-GPDAA.clustersOccur-PTN1.clustersOccur_ 26_ 1-- - In Progress 4/29/09 02:27:54 5/9/09 21:04:08 0.00 0.0 / 0.0 CMD2_ 0001-GPDAA.clustersOccur-PTN1.clustersOccur_ 26_ 2-- 610 Too Late 4/29/09 02:27:52 5/1/09 19:53:03 1.40 22.0 / 0.0 CMD2_ 0001-GPDAA.clustersOccur-PTN1.clustersOccur_ 26_ 0-- - In Progress 4/29/09 02:27:35 5/9/09 21:04:08 0.00 0.0 / 0.0 |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
You had the third copy, so I'm guessing it will have had a short deadline to get it returned quickly.
I forget exactly how credit is awarded for late results, but I'm fairly sure that results returned before the work unit is validated are eligible for credit. |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
There I thought this particular beta (yes without the prefix) had an init 3, the few seconds apart strongly suggesting so too.
----------------------------------------This "too late" faulting is becoming a pain in the proverbials. knreed said credit would be given for all [beta] that come in up to 7 days late. Source: http://www.worldcommunitygrid.org/forums/wcg/printpost?post=226358
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
pirogue
Veteran Cruncher USA Joined: Dec 8, 2008 Post Count: 685 Status: Offline Project Badges:
|
You had the third copy, so I'm guessing it will have had a short deadline to get it returned quickly. So, the others also are really too late, but haven't been returned. |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
None are at this time "technically" too late. It's a flunky where distribution is in limbo. Possibly these slipped out unintentionally with standard 10 day deadline. Given the 1.40 hours run time [not one of the monsters], it's obscure that the other 2 have not come back yet.
----------------------------------------
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Something's off, the deadline is the 9th.
|
||
|
|
rilian
Veteran Cruncher Ukraine - we rule! Joined: Jun 17, 2007 Post Count: 1452 Status: Offline Project Badges: 
|
BETA_ CMD2_ 0001-PP1BA.clustersOccur-Q01105-2A.clustersOccur_ 5_ 4-- - In Progress 4/26/09 01:13:56 5/9/09 21:04:08 0.00 0.0 / 0.0
----------------------------------------BETA_ CMD2_ 0001-PP1BA.clustersOccur-Q01105-2A.clustersOccur_ 5_ 6-- - In Progress 4/26/09 01:13:00 5/9/09 21:04:08 0.00 0.0 / 0.0 BETA_ CMD2_ 0001-PP1BA.clustersOccur-Q01105-2A.clustersOccur_ 5_ 5-- 610 Aborted 4/26/09 01:12:40 4/28/09 00:51:34 47.13 364.6 / 364.6 BETA_ CMD2_ 0001-PP1BA.clustersOccur-Q01105-2A.clustersOccur_ 5_ 2-- 610 Aborted 4/25/09 00:08:19 4/26/09 02:31:14 0.00 0.0 / 0.0 BETA_ CMD2_ 0001-PP1BA.clustersOccur-Q01105-2A.clustersOccur_ 5_ 3-- 610 Valid 4/25/09 00:08:16 4/27/09 00:56:17 48.77 809.3 / 806.1 BETA_ CMD2_ 0001-PP1BA.clustersOccur-Q01105-2A.clustersOccur_ 5_ 1-- 610 Error 4/25/09 00:05:47 4/25/09 00:07:02 0.00 0.0 / 0.0 BETA_ CMD2_ 0001-PP1BA.clustersOccur-Q01105-2A.clustersOccur_ 5_ 0-- 610 Valid 4/25/09 00:05:33 4/28/09 15:11:55 55.06 802.9 / 806.1 Xeon 2Ghz CPU 170hours elapsed, 120 remaining, 45% done  is that ok ? dont want to abort it because i get 0 pts then  |
||
|
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges: 
|
We have canceled all of the outstanding workunits. We are not going to be able to effectively predict the workunit lengths.
We are awarding credit to the results aborted or marked too late. I will keep doing that for the next couple of days. Since we cannot predict length, we are going with plan B. This will mean that we will put an upper bound on execution time for each workunit. If that limit is reached, we will examine how far the workunit got and then create child workunits to finish off the remain work. The quanta of work for this project is a 'position'. So if a workunit is intended to compute 2000 positions, but only 150 are computed. Then we will create child workunits to compute positions 151 - 250, 251-350, etc. This will allow us to get the work done without these massive workunits. |
||
|
|
rilian
Veteran Cruncher Ukraine - we rule! Joined: Jun 17, 2007 Post Count: 1452 Status: Offline Project Badges:
|
thanks
----------------------------------------i will abort it |
||
|
|
|