Tracking the Old Assignments

petrw1 · 2007-01-02, 17:02

PREAMBLE: I report these strictly for their statistical value or for the curious. I am not in any way criticizing those that manage the assignments. I trust their handling of them.

There are 1,188 assignments from prior to 2006, the oldest is from Dec 31, 2002 (now over 4 years ago),

One is from 2002, 15 from 2003, 122 from 2004 and 1,051 from 2005.

85 are over 90% complete; 259 are over 75% complete; 487 are over 50% complete; 314 have not reported any interations yet. (DISCLAIMER: these stats may be slightly incorrect since I can tell for sure how far complete "F" assignments are)

Big players are: agc:16 assignments (+); CaptianEntropy:46 (-); hreid:14 (+); jr007j:10 (-); meresejev:28 (+); RU:92 (-); S16447:69 (+); S263903:17 (-); S404125:17 (-); SW:192 (+); Team_Prime_Rib:13 (+)

LEGEND: (+) Making Good Progress; (-) Little or, in most cases, no progress. These 5 accounts have 182 assignments that are at least a year old showing virtually no progress.

17 are less than a week away from expiring.
287 are overdue (negative number of days to go)
Exponent 35047253 reports almost 26 years to go
19 have more than 5 years to go
63 have more than a year to go
237 have more than 100 days to go
313 have more than the current limit of 60 days to go

And finally, 12 are within the current focus range (14 Million) - all double-checking and all showing progress with completion likely within the month.

Wayne

S485122 · 2007-01-02, 20:26

The very odd assigments (5 years to go for instance) have been reported more than once, I posted about it in the following thread : Strange expiry dates but there are others.

In my opinion any assignement that did not report in the last 6 months should be released. Why 6months ? The maximum holiday period one can input in prime95 is 120 days and in the rules it is stated that one must report at least every 2 months.

garo · 2007-01-03, 16:54

Unfortunately there is no automatic way of identifying such exponents. If the Primenet server worked as intended any exponent not reported in 120 days would actually expire. However, for some strange reason some of these exponents are missed by the server. If you provide us with a list of exponents that have shown no or very little progress in 2006, or have enormous expiry dates - not finish dates mind you - I can check the list and send it to George. He can manually remove those assignments from Primenet and make them available for testing again.

S485122 · 2007-01-04, 06:57

A list of exponents with HUGE expiry limits :

Code:

Prime	Type	Bits	Iteration	Run	To Go	Expires	Date Updated	Date Assigned	Account	Computer	Computed Update Date
28076593		68	254	381,6	2105	2164	2005-12-19 05:45:00	2005-12-18 15:51:00	S404125	C756893CC	
30136411	 F	67		381	2105	2164		2005-12-19 05:45:00	S404125	C756893CC	
30136567		68		381	2105	2164		2005-12-19 05:45:00	S404125	C756893CC	
30137621	 F	67		381	2105	2164		2005-12-19 05:46:00	S404125	C756893CC	
30136439		68		381	2105	2164		2005-12-19 05:45:00	S404125	C756893CC	
30137417	 F	67		381	2105	2164		2005-12-19 05:46:00	S404125	C756893CC	
30137353		68		381	2105	2164		2005-12-19 05:45:00	S404125	C756893CC	
30137347	 F	67		381	2105	2164		2005-12-19 05:45:00	S404125	C756893CC	
30136741	 F	67		381	2105	2164		2005-12-19 05:45:00	S404125	C756893CC	
30134723		68		381	2105	2164		2005-12-19 05:45:00	S404125	C756893CC	
30134981		68		381	2105	2164		2005-12-19 05:45:00	S404125	C756893CC	
30135143		68		381	2105	2164		2005-12-19 05:45:00	S404125	C756893CC	
30136573		68		381	2105	2164		2005-12-19 05:45:00	S404125	C756893CC	
30136609		68		381	2105	2164		2005-12-19 05:45:00	S404125	C756893CC	
30134729		68		381	2105	2164		2005-12-19 05:45:00	S404125	C756893CC	
30134869		68		381	2105	2164		2005-12-19 05:45:00	S404125	C756893CC	
30135013		68		381	2105	2164		2005-12-19 05:45:00	S404125	C756893CC	
17548717	D	66		176,8	1121	1180	2006-07-11 11:05:00	2006-07-11 10:26:00	S488444	C4EC3A537	
37686001	 F	62		251,1	927,9	986,9		2006-04-28 03:16:00	S442572	CC820930B	
37685899	 F	62		251,1	927,9	986,9		2006-04-28 03:16:00	S442572	CC820930B	
37685867	 F	62		251,1	927,9	986,9		2006-04-28 03:16:00	S442572	CC820930B	
18101431	D	67		8,5	723,5	782,5	2006-12-26 17:17:00	2006-12-26 17:09:00	S555244	amd-overcloc	
18087599	D	67		8,5	723,5	782,5	2006-12-26 17:17:00	2006-12-26 17:09:00	S555244	amd-overcloc	
18104441	D	67		8,5	723,5	782,5	2006-12-26 17:17:00	2006-12-26 17:09:00	S555244	amd-overcloc	
18105553	D	67		8,5	723,5	782,5	2006-12-26 17:17:00	2006-12-26 17:10:00	S555244	amd-overcloc	
18104417	D	67		8,5	723,5	782,5	2006-12-26 17:17:00	2006-12-26 17:09:00	S555244	amd-overcloc	
18083311	D	67		8,5	723,5	782,5	2006-12-26 17:17:00	2006-12-26 17:09:00	S555244	amd-overcloc	
18088303	D	67		8,5	723,5	782,5	2006-12-26 17:17:00	2006-12-26 17:09:00	S555244	amd-overcloc	
18082721	D	67		8,5	723,5	782,5	2006-12-26 17:17:00	2006-12-26 17:09:00	S555244	amd-overcloc	
17609057	D	66		8,8	723,5	782,5	2006-12-26 17:17:00	2006-12-26 12:29:00	S555244	amd-overcloc	
18081883	D	67		8,5	723,5	782,5	2006-12-26 17:17:00	2006-12-26 17:09:00	S555244	amd-overcloc	
18092401	D	67		8,5	723,5	782,5	2006-12-26 17:17:00	2006-12-26 17:09:00	S555244	amd-overcloc	
18106217	D	67		8,5	723,5	782,5	2006-12-26 17:17:00	2006-12-26 17:10:00	S555244	amd-overcloc	
18099941	D	67		8,5	723,5	782,5	2006-12-26 17:17:00	2006-12-26 17:09:00	S555244	amd-overcloc	
18099563	D	67		8,5	723,5	782,5	2006-12-26 17:17:00	2006-12-26 17:09:00	S555244	amd-overcloc	
18106897	D	67		8,5	723,5	782,5	2006-12-26 17:17:00	2006-12-26 17:10:00	S555244	amd-overcloc	
18099013	D	67		8,5	723,5	782,5	2006-12-26 17:17:00	2006-12-26 17:09:00	S555244	amd-overcloc	
18097591	D	67		8,5	723,5	782,5	2006-12-26 17:17:00	2006-12-26 17:09:00	S555244	amd-overcloc	
18106757	D	67		8,5	723,5	782,5	2006-12-26 17:17:00	2006-12-26 17:10:00	S555244	amd-overcloc	
18096941	D	67		8,5	723,5	782,5	2006-12-26 17:17:00	2006-12-26 17:09:00	S555244	amd-overcloc	
18105823	D	67		8,5	723,5	782,5	2006-12-26 17:17:00	2006-12-26 17:10:00	S555244	amd-overcloc	
26816969		67		757,1	316,9	375,9	2004-12-08 04:57:00	2004-12-08 04:49:00	S263903	C4285F3CF	
26820019		67		757,1	360,9	375,9	2004-12-08 04:57:00	2004-12-08 04:49:00	S263903	C4285F3CF	
26820007		67		757,1	316,9	375,9	2004-12-08 04:57:00	2004-12-08 04:49:00	S263903	C4285F3CF	
26819941		67		757,1	316,9	375,9	2004-12-08 04:57:00	2004-12-08 04:49:00	S263903	C4285F3CF	
26819927		67		757,1	316,9	375,9	2004-12-08 04:57:00	2004-12-08 04:49:00	S263903	C4285F3CF	
26819731		67		757,1	316,9	375,9	2004-12-08 04:57:00	2004-12-08 04:49:00	S263903	C4285F3CF	
26819677		67		757,1	316,9	375,9	2004-12-08 04:57:00	2004-12-08 04:49:00	S263903	C4285F3CF	
26819623		67		757,1	316,9	375,9	2004-12-08 04:57:00	2004-12-08 04:49:00	S263903	C4285F3CF	
26816863		67		757,1	316,9	375,9	2004-12-08 04:57:00	2004-12-08 04:49:00	S263903	C4285F3CF	
26819509		67		757,1	316,9	375,9	2004-12-08 04:57:00	2004-12-08 04:49:00	S263903	C4285F3CF	
26816761		67		757,1	316,9	375,9	2004-12-08 04:57:00	2004-12-08 04:48:00	S263903	C4285F3CF	
26816963		67		757,1	316,9	375,9	2004-12-08 04:57:00	2004-12-08 04:49:00	S263903	C4285F3CF	
26819713		67		757,1	316,9	375,9	2004-12-08 04:57:00	2004-12-08 04:49:00	S263903	C4285F3CF	
26816861		67		757,1	316,9	375,9	2004-12-08 04:57:00	2004-12-08 04:48:00	S263903	C4285F3CF	
26816789		67		757,1	316,9	375,9	2004-12-08 04:57:00	2004-12-08 04:48:00	S263903	C4285F3CF	
26816663		67		757,1	316,9	375,9	2004-12-08 04:57:00	2004-12-08 04:48:00	S263903	C4285F3CF	
26819593		67		757,1	316,9	375,9	2004-12-08 04:57:00	2004-12-08 04:49:00	S263903	C4285F3CF

The assignments of "amd-overcloc" are strange as well even if recent : how can one achieve expiry dates so far in the future (two years) ? There must be a combination of parameters that has the server go tilt.

Jacob

S485122 · 2007-01-04, 06:59

Quote:

Originally Posted by garo

Unfortunately there is no automatic way of identifying such exponents. If the Primenet server worked as intended any exponent not reported in 120 days would actually expire.

If you want a list of exponents with no progress report in 120 days I can try to provide it as well.

jinydu · 2007-01-04, 10:08

Quote:

Originally Posted by petrw1

the oldest is from Dec 31, 2002 (now over 4 years ago)

Which one is that? (I may have already asked this question somewhere else)

Andi47 · 2007-01-04, 11:39

Quote:

Originally Posted by jinydu

Which one is that? (I may have already asked this question somewhere else)

This one:

Code:

 prime      fact  current          days
exponent    bits iteration  run / to go / exp   date updated     date assigned   account ID     computer ID
-------- -- ---- ---------  -----------------  ---------------  ---------------  -------------- ------------
33386203     69   5765787    1465 387.8  73.8  04-Jan-07 06:21  31-Dec-02 03:53  GTS            GTS

Seems to make at least some progress, latest progress report: Today, Expiry date seems OK too.

tha · 2007-01-04, 13:00

Quote:

Originally Posted by Andi47

This one:

Code:

 prime      fact  current          days
exponent    bits iteration  run / to go / exp   date updated     date assigned   account ID     computer ID
-------- -- ---- ---------  -----------------  ---------------  ---------------  -------------- ------------
33386203     69   5765787    1465 387.8  73.8  04-Jan-07 06:21  31-Dec-02 03:53  GTS            GTS

Seems to make at least some progress, latest progress report: Today, Expiry date seems OK too.

That's funny. That exponent appeared on my radar as well a week ago. It claims to have spend 4 years on this assignment and needing another 20 years to finish it. In 20 years even the double checks should be well past this point. This month it will become the lowest 10M assignment without a result checked in. I weighted poaching the exponent but decided that it would be better to first try finding a factor of it using the P-1 method with B1=8M and B2=80M. If that fails (roughly 95% chance) I will run this exponent on a 2400 Core 2 machine.

Andi47 · 2007-01-04, 14:48

Quote:

Originally Posted by tha

That's funny. That exponent appeared on my radar as well a week ago. It claims to have spend 4 years on this assignment and needing another 20 years to finish it. In 20 years even the double checks should be well past this point. This month it will become the lowest 10M assignment without a result checked in. I weighted poaching the exponent but decided that it would be better to first try finding a factor of it using the P-1 method with B1=8M and B2=80M. If that fails (roughly 95% chance) I will run this exponent on a 2400 Core 2 machine.

Strange enough the line says, that it has run for 4 years, and "only" a few days more than 1 year (387 days) to go.

As of today it is approx. 17,3% done. If it continues running at the same "speed", it will take another 19 years. Maybe it has been moved to a somewhat faster machine? The next weeks will show...

garo · 2007-01-04, 14:57

While amd-overcloc is strange indeed I think it is a bit premature to expire those exponents. I would also appreciate if you give me a list of exponents that have not been updated for over 150 days - just to be safe - and I will combine the two lists and send them to George.

tha · 2007-01-04, 16:04

Quote:

Originally Posted by Andi47

The next weeks will show...

In all earlier reports the assignment was updated in the same way as the last update.

2007-01-02, 17:02	#1
petrw1 1976 Toyota Corona years forever! "Wayne" Nov 2006 Saskatchewan, Canada 2²×3×17×23 Posts	Tracking the Old Assignments PREAMBLE: I report these strictly for their statistical value or for the curious. I am not in any way criticizing those that manage the assignments. I trust their handling of them. There are 1,188 assignments from prior to 2006, the oldest is from Dec 31, 2002 (now over 4 years ago), One is from 2002, 15 from 2003, 122 from 2004 and 1,051 from 2005. 85 are over 90% complete; 259 are over 75% complete; 487 are over 50% complete; 314 have not reported any interations yet. (DISCLAIMER: these stats may be slightly incorrect since I can tell for sure how far complete "F" assignments are) Big players are: agc:16 assignments (+); CaptianEntropy:46 (-); hreid:14 (+); jr007j:10 (-); meresejev:28 (+); RU:92 (-); S16447:69 (+); S263903:17 (-); S404125:17 (-); SW:192 (+); Team_Prime_Rib:13 (+) LEGEND: (+) Making Good Progress; (-) Little or, in most cases, no progress. These 5 accounts have 182 assignments that are at least a year old showing virtually no progress. 17 are less than a week away from expiring. 287 are overdue (negative number of days to go) Exponent 35047253 reports almost 26 years to go 19 have more than 5 years to go 63 have more than a year to go 237 have more than 100 days to go 313 have more than the current limit of 60 days to go And finally, 12 are within the current focus range (14 Million) - all double-checking and all showing progress with completion likely within the month. Wayne

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
about assignments	savoie	Information & Answers	3	2015-04-30 10:07
a tracking question	bcp19	PrimeNet	12	2012-04-29 07:21
Tracking GIMPS progress with scripts	jasong	jasong	21	2008-03-25 00:47
Tracking the November 2003 release of error-prone exponents	nfortino	Data	2	2005-07-25 13:46
Tracking the October 2003 release of error-prone-machine exponents	GP2	Data	10	2005-07-25 13:14

2007-01-02, 20:26	#2
S485122 Sep 2006 Brussels, Belgium 13·131 Posts	The very odd assigments (5 years to go for instance) have been reported more than once, I posted about it in the following thread : Strange expiry dates but there are others. In my opinion any assignement that did not report in the last 6 months should be released. Why 6months ? The maximum holiday period one can input in prime95 is 120 days and in the rules it is stated that one must report at least every 2 months.

2007-01-03, 16:54	#3
garo Aug 2002 Termonfeckin, IE 2²·691 Posts	Unfortunately there is no automatic way of identifying such exponents. If the Primenet server worked as intended any exponent not reported in 120 days would actually expire. However, for some strange reason some of these exponents are missed by the server. If you provide us with a list of exponents that have shown no or very little progress in 2006, or have enormous expiry dates - not finish dates mind you - I can check the list and send it to George. He can manually remove those assignments from Primenet and make them available for testing again.

2007-01-04, 14:57	#10
garo Aug 2002 Termonfeckin, IE 2²·691 Posts	While amd-overcloc is strange indeed I think it is a bit premature to expire those exponents. I would also appreciate if you give me a list of exponents that have not been updated for over 150 days - just to be safe - and I will combine the two lists and send them to George.