I'll take care of 21570-21575.
Will post more ranges soon.
I'll take care of 21570-21575.
Will post more ranges soon.
Here are the new ranges:
Please note that some of the ranges are a bit larger this time. Please feel free to grab only a portion the larger ranges if you wish to do so.
Original range: 22200-22260
User: louie
Expected: 54 factors
Actual: 33 factors
I checked 22200-22210, and found three new factors (22201416757283 | 4847*2^7759791+1, 22205950519559 | 4847*2^6479727+1, and 22209953234849 | 4847*2^10016031+1).
22210-22260 is available for resieve if anyone is interested. Just drop a note below.
Original range: 22710-22800
User: cmprince
Expected: 79 factors
Actual: 41 factors
I checked 22710-22720, and found one new factor (22715994543887 | 4847*2^12717591+1).
22720-22800 is available for resieve if anyone is interested. Just drop a note below.
Original range: 27315-27500
User: ceselb
Expected: 135 factors
Actual: 100 factors
I checked 27315-27325, and found two new factors (27317815344109 | 19249*2^18965822+1, and 27322606154009 | 19249*2^18862142+1).
27325-27500 is available for resieve if anyone is interested. Just drop a note below.
Original range: 39400-39450
User: mklasson
Expected: 25 factors
Actual: 14 factors
I checked 39400-39410, and found one new factor (39407497507957 | 10223*2^6688229+1).
39410-39450 is available for resieve if anyone is interested. Just drop a note below.
Original range: 42650-42700
User: mklasson
Expected: 23 factors
Actual: 14 factors
I checked 42650-42660, and found one new factor (42659666582497 | 10223*2^10445801+1).
42660-42700 is available for resieve if anyone is interested. Just drop a note below.
Original range: 42900-42950
User: netbrian
Expected: 23 factors
Actual: 13 factors
I checked 42940-42950, and found one new factor (42942861181373 | 10223*2^5759801+1).
42900-42940 is available for resieve if anyone is interested. Just drop a note below. EDIT: Taken by Keroberts1.
As always: Although it's highly likely that there will be some new factors, there is no 100% guarantee that there will be more missing factors in any of the ranges.
PS: With this batch, there is only one batch left, with three ranges. After those three are finished, only other ranges left will be that of Joe's.
Last edited by Nuri; 05-09-2004 at 07:42 AM.
21520-21550 completed with 6 new factors
I'll whack these two before I head home.
22210-22260 royanee
22720-22800 royanee
Last edited by royanee; 05-10-2004 at 12:46 PM.
I'll take 42900-42940 Keroberts1 [complete] 5 found
42660-42700 now for this one
Last edited by Keroberts1; 05-10-2004 at 07:48 AM.
17150-17240 priwo [complete]
15 new
Statistics:
pmin : 16258261219860
pmax : 16260000000000
# Tested p : 57160596
# Tested k : 628766556
# Whacked k : 511332429
# Whacked p : 17468673
Total time: 13697898 ms.
126kp/s.
Statistics:
pmin : 21550000000000
pmax : 21570000000000
# Tested p : 651430312
# Tested k : 7165733432
# Whacked k : 5828673007
# Whacked p : 199267873
Total time: 119002646 ms.
168kp/s.
42660-42700 complete 4 factors found
has anyone determined which siever it was taht was missing some of the factors or what caused this to happen? If it was sobsieve then does this mean there is a good chance that there are many more missed factors?
22210-22260 royanee [complete] 4 new factors
22720-22800 royanee [complete] 12 new factors
This means that the following ranges:
27325-27500
39410-39450
are available for resieve if anyone is interested. Just drop a note below.
I guess it was one of the proth sieve versions that we noticed the problem soon and mikael released a new one. Probably some of the users continued using it for a while.Originally posted by Keroberts1
has anyone determined which siever it was taht was missing some of the factors or what caused this to happen? If it was sobsieve then does this mean there is a good chance that there are many more missed factors?
As far as any more missed factors, there really is not much left. The very early ranges (~up to 10T) were controlled very carefully by both Mike and me, and the ones in this thread are almost all of the ones above 10T.
I'm planning to post a graph to help visualize, when we're finished with these ranges.
Joe O said he used sobsieve 1.28 on noe of his ranges didn't he? Has anyone wiht the older versions tried seeing if these factors are missed by certain versions?
I guess his problem might also be the faulty PC.Joe O said he used sobsieve 1.28 on noe of his ranges didn't he? Has anyone wiht the older versions tried seeing if these factors are missed by certain versions?
From his post:
No, it was an AMD K6-III/400 that was running at stock. It ran hot from day one, even with an extra case fan. I had to turn it off on hot summer afternoons, or the thermal warning would throttle it down anyway. It has been retired.
It seems everything is reserved now.
IIRC, there were three more ranges left. I'll check into them in the following days and let you know if there's anything worth resieve.
Here's how the factor densities looked like for 1,500G to 100,000G as of 27 April 2004.
And here's how it looks like for 1,000G to 100,000G as of today.
PS: There's been no change in 1,000G to 1,500G. The first graph lacks that poart simply because I did not keep the data for it.
27325-27500 Death complete
27.484T 10223 1346249 27.484 Mon 31-May-2004
27.478T 10223 2108729 27.478 Mon 31-May-2004
27.477T 4847 2841087 27.477 Mon 31-May-2004
27.473T 10223 16589081 27.473 Mon 31-May-2004
27.473T 19249 12829406 27.473 Mon 31-May-2004
27.471T 19249 10407218 27.471 Mon 31-May-2004
27.466T 4847 9930831 27.466 Fri 28-May-2004
27.464T 4847 14831991 27.464 Thu 27-May-2004
27.463T 10223 19333001 27.463 Thu 27-May-2004
27.456T 10223 7122665 27.456 Tue 25-May-2004
27.455T 4847 19045527 27.455 Tue 25-May-2004
27.454T 10223 17018285 27.454 Tue 25-May-2004
27.448T 4847 1031847 27.448 Sun 30-May-2004
27.428T 4847 10092591 27.428 Fri 28-May-2004
27.426T 4847 7299087 27.426 Fri 28-May-2004
27.414T 10223 37229 27.414 Fri 28-May-2004
27.410T 10223 16394345 27.410 Thu 27-May-2004
27.409T 10223 8501705 27.409 Thu 27-May-2004
27.402T 21181 104780 27.402 Thu 27-May-2004
27.393T 10223 12479309 27.393 Wed 26-May-2004
27.380T 4847 18884607 27.380 Tue 25-May-2004
27.373T 24737 181783 27.373 Tue 25-May-2004
27.347T 19249 8603042 27.347 Sat 22-May-2004
27.340T 10223 5358665 27.340 Sat 22-May-2004
27.336T 10223 19504505 27.336 Fri 21-May-2004
SobSieve 1.35 was released on 6/25/2003. It was also released as 1.34 on 6/23/2003. Both of these executables are flawed. Actually they are the same code, the only difference is that one reports itself as version 1.34 and the other as 1.35, so I will refer to them both as version 1.35.
The true version 1.34 was released on 5/24/2003. This one works correctly as far as I can tell.
This is the results from my test of 1.35:
I would suggest that anyone running 1.35 change to the 1.34 version dated 5/24/2003 or to Proth sieve.Code:Found Missed Total K=4847 16949 28989 45938 K=10223 10499 41920 52419 K=19249 1809 16971 18780 K=21181 45476 0 45476 K=22699 25466 189 25655 K=24737 47700 0 47700 K=27653 26882 0 26882 K=28433 25645 0 25645 K=33661 45138 0 45138 K=55459 69603 161 69764 K=67607 16028 0 16028 Overall 331195 88230 419425
If anyone is running older versions of SoBSieve, I can test them on the same data. But I will do this only if you really, really, are running that version and cannot change.
As far as resieving ranges run with the flawed versions, Nuri's analyses posted earlier in this thread caught the ranges done before mid May. If anyone used version 1.35 after mid May, please post and let us know the range and if you intend to resieve it yourself or wish someone else to do it.
Joe O
Since the siever only missed factors from thesre K values we should eliminate the rest from the double checking phase. 4847 10223 19249 22699 55459. perhaps only the first 3 should be resieved for the ranges in question since most of the missing factors were for those ones. This way we could finish them rather quickly and still have almost the same amount of factors per time dedicated.