Conflicting data?

ATH · 2006-02-23, 20:00

These exponent are both in "status.txt" as being currently LL tested and in "Lucas_v.txt" as being allready doublechecked:

status.txt
11317849 65 13.5 -4.5 55.5 08-Feb-06 06:22 08-Feb-06 06:08 ronha VISAR1
lucas_v.txt
11317849,imoszarh,media,WW2,57BC2E399C5F8C6A,4175519,00000000
11317849,Team_Prime_Rib,bayanne_CAFE,WZ1,57BC2E399C5F8C6A,6658988,00000000

status.txt
11585029 65 59172 9.2 14.8 74.8 12-Feb-06 12:06 S175642 C76F5AEFF
lucas_v.txt
11585029,MSRC,MSRC-VANUATA,WV5,A01BF9B3B6A3239A,11407429,00000000
11585029,SK,,WZ2,A01BF9B3B6A3239A,6171263,00000000

Same for:
11671763
11945231
11982107
12577751
12929513
12961147
13177807
13192243
13318027
13324859
13374217
13375993
13398247
13499113
13551037
13598479
13632337
13708729
13788469
13812199
13869949
14062687
14079101
14218261
14337941
14374309
14374411
14374511
14374543
14374579
14455187
14458193
14505643
14512453
14563867
14620171
14622589
14839199
14879021
15160973
15562643
15673703
18407803
20270357
24859517
33938689

These exponent are in "hrf3.txt" as being LL tested once and in "status.txt" as being currently LL tested again instead of doublechecked:

hrf3.txt:
13503221,FH2,,WX1,00000000
13503221,mersboy,odb1_a,WY2,00000000
status.txt
13503221 66 125.5 13.3 73.3 20-Feb-06 01:18 19-Oct-05 04:47 dswanson xxxx

Same for these: LL.txt

tha · 2006-02-23, 21:55

Quote:

Originally Posted by ATH

These exponent are both in "status.txt" as being currently LL tested and in "Lucas_v.txt" as being already doublechecked:

These exponent are in "hrf3.txt" as being LL tested once and in "status.txt" as being currently LL tested again instead of doublechecked:

Due to miscommunications between the server and some of the clients some exponents get tested more times than necessary. One or another exponent got LL tested two dozen different times by the very same machine. Always with the same result and got doublechecked by a complete different machine with the same result. Basically this is not so bad, it provides more data on the reliability of each of the components. Usually it is caused by clients that have run astray.
No worries.

garo · 2006-02-24, 17:17

the first set of exponents usually appear when someone who had been assigned the exponent a long time ago let it expire and it was later finished by someone else. After the exponent was cleared and removed from cleared.txt by a database synchronization, the original assignee contacts Primenet server and since the exponent has now left the Primenet server records, Primenet goes into its default mode when confronted by an unknown exponent and assigns it as a first time test. While I clear such exponents out on a monthly basis by sending the list of George, it is an unending task.

The second class is exponents that need a triplecheck and are detected by dswanson who contacts the server by himself without having been handed the exponent in order to perform a quick triple-check. This class is not to be worried about.

ATH · 2006-02-24, 18:14

Quote:

Due to miscommunications between the server and some of the clients some exponents get tested more times than necessary. One or another exponent got LL tested two dozen different times by the very same machine. Always with the same result and got doublechecked by a complete different machine with the same result. Basically this is not so bad, it provides more data on the reliability of each of the components. Usually it is caused by clients that have run astray.

The 2nd list is over 2,400 exponents its just a lot of "lost" work.

garo · 2006-02-27, 13:53

The second list is not lost work. It is just work that has the wrong status on the server.

And there isn't much you can do about computers that work very slowly, let an exponent expire which is then reassigned and completed by someone else, but the original computer keeps working on the exponent. v5 promises to fix these issues but for the moment, my monthly cleanup is the best solution we have.

2006-02-23, 20:00	#1
ATH Einyen Dec 2003 Denmark 19·181 Posts	Conflicting data? These exponent are both in "status.txt" as being currently LL tested and in "Lucas_v.txt" as being allready doublechecked: status.txt 11317849 65 13.5 -4.5 55.5 08-Feb-06 06:22 08-Feb-06 06:08 ronha VISAR1 lucas_v.txt 11317849,imoszarh,media,WW2,57BC2E399C5F8C6A,4175519,00000000 11317849,Team_Prime_Rib,bayanne_CAFE,WZ1,57BC2E399C5F8C6A,6658988,00000000 status.txt 11585029 65 59172 9.2 14.8 74.8 12-Feb-06 12:06 S175642 C76F5AEFF lucas_v.txt 11585029,MSRC,MSRC-VANUATA,WV5,A01BF9B3B6A3239A,11407429,00000000 11585029,SK,,WZ2,A01BF9B3B6A3239A,6171263,00000000 Same for: 11671763 11945231 11982107 12577751 12929513 12961147 13177807 13192243 13318027 13324859 13374217 13375993 13398247 13499113 13551037 13598479 13632337 13708729 13788469 13812199 13869949 14062687 14079101 14218261 14337941 14374309 14374411 14374511 14374543 14374579 14455187 14458193 14505643 14512453 14563867 14620171 14622589 14839199 14879021 15160973 15562643 15673703 18407803 20270357 24859517 33938689 These exponent are in "hrf3.txt" as being LL tested once and in "status.txt" as being currently LL tested again instead of doublechecked: hrf3.txt: 13503221,FH2,,WX1,00000000 13503221,mersboy,odb1_a,WY2,00000000 status.txt 13503221 66 125.5 13.3 73.3 20-Feb-06 01:18 19-Oct-05 04:47 dswanson xxxx Same for these: LL.txt

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
NFS filtering in the era of big data	jasonp	Msieve	36	2018-05-07 19:55
I got an TF assigned, but it has conflicting history	swl551	PrimeNet	9	2013-12-19 14:39
Corrupted data?	Oops!	Information & Answers	2	2013-10-22 03:48
GPU TF vs DC/LL data	bcp19	GPU to 72	0	2011-12-02 16:41
Data available?	Prime95	LMH > 100M	10	2007-06-22 23:55

2006-02-24, 17:17	#3
garo Aug 2002 Termonfeckin, IE 2⁴·173 Posts	the first set of exponents usually appear when someone who had been assigned the exponent a long time ago let it expire and it was later finished by someone else. After the exponent was cleared and removed from cleared.txt by a database synchronization, the original assignee contacts Primenet server and since the exponent has now left the Primenet server records, Primenet goes into its default mode when confronted by an unknown exponent and assigns it as a first time test. While I clear such exponents out on a monthly basis by sending the list of George, it is an unending task. The second class is exponents that need a triplecheck and are detected by dswanson who contacts the server by himself without having been handed the exponent in order to perform a quick triple-check. This class is not to be worried about.

2006-02-27, 13:53	#5
garo Aug 2002 Termonfeckin, IE 2⁴×173 Posts	The second list is not lost work. It is just work that has the wrong status on the server. And there isn't much you can do about computers that work very slowly, let an exponent expire which is then reassigned and completed by someone else, but the original computer keeps working on the exponent. v5 promises to fix these issues but for the moment, my monthly cleanup is the best solution we have.