PrimeGrid
Please visit donation page to help the project cover running costs for this month

Toggle Menu

Join PrimeGrid

Returning Participants

Community

Leader Boards

Results

Other

drummers-lowrise

Advanced search

Message boards : Seventeen or Bust : Are people even sure 78557 is the smallest k?

Author Message
Profile BurProject donor
Volunteer tester
Avatar
Send message
Joined: 25 Feb 20
Posts: 515
ID: 1241833
Credit: 414,481,880
RAC: 219
321 LLR Ruby: Earned 2,000,000 credits (2,092,823)Cullen LLR Ruby: Earned 2,000,000 credits (2,315,295)ESP LLR Ruby: Earned 2,000,000 credits (2,151,088)Generalized Cullen/Woodall LLR Ruby: Earned 2,000,000 credits (2,620,968)PPS LLR Jade: Earned 10,000,000 credits (16,474,243)PSP LLR Ruby: Earned 2,000,000 credits (2,064,832)SoB LLR Ruby: Earned 2,000,000 credits (2,434,466)SR5 LLR Ruby: Earned 2,000,000 credits (2,065,004)SGS LLR Ruby: Earned 2,000,000 credits (2,042,656)TRP LLR Ruby: Earned 2,000,000 credits (2,089,856)Woodall LLR Ruby: Earned 2,000,000 credits (2,112,258)321 Sieve (suspended) Ruby: Earned 2,000,000 credits (2,107,153)PPS Sieve Turquoise: Earned 5,000,000 credits (5,096,952)AP 26/27 Turquoise: Earned 5,000,000 credits (5,797,662)GFN Jade: Earned 10,000,000 credits (11,994,022)WW (retired) Double Silver: Earned 200,000,000 credits (349,980,000)PSA Amethyst: Earned 1,000,000 credits (1,042,601)
Message 140161 - Posted: 10 May 2020 | 17:38:25 UTC
Last modified: 10 May 2020 | 17:42:03 UTC

Seeing how SoB has gone to really large n values, are mathematicians rather certain that 78557 is the smallest Sierpinski number? I know there is no proof, but it appears to me, that some conjectures are thought to be true (like Riemann zeta) because there are lots of hints they are true.

Are there some arguments pro 78557 being the smallest Sierpinski number? If so, are there some ideas about the magnitude of n for the remaining k's?

Is there a point when such a large n is reached that doubt will be cast upon 78557 actually being the smallest Sierpinski number?

Is anything known about why some k < 78557 require such large n-values before resulting in a prime while the majority doesn't?

Ravi Fernando
Project administrator
Volunteer tester
Project scientist
Send message
Joined: 21 Mar 19
Posts: 211
ID: 1108183
Credit: 13,824,824
RAC: 7,626
321 LLR Amethyst: Earned 1,000,000 credits (1,214,472)Cullen LLR Silver: Earned 100,000 credits (111,878)ESP LLR Bronze: Earned 10,000 credits (16,570)Generalized Cullen/Woodall LLR Bronze: Earned 10,000 credits (68,801)PPS LLR Ruby: Earned 2,000,000 credits (4,672,204)PSP LLR Silver: Earned 100,000 credits (166,255)SoB LLR Silver: Earned 100,000 credits (258,849)SR5 LLR Bronze: Earned 10,000 credits (76,537)SGS LLR Silver: Earned 100,000 credits (220,642)TRP LLR Silver: Earned 100,000 credits (254,161)Woodall LLR Bronze: Earned 10,000 credits (97,444)321 Sieve (suspended) Turquoise: Earned 5,000,000 credits (5,001,667)AP 26/27 Bronze: Earned 10,000 credits (72,774)GFN Amethyst: Earned 1,000,000 credits (1,574,206)WW (retired) Bronze: Earned 10,000 credits (12,000)
Message 140164 - Posted: 10 May 2020 | 21:21:25 UTC - in response to Message 140161.

Is anything known about why some k < 78557 require such large n-values before resulting in a prime while the majority doesn't?

Yes. Some k's produce lots of candidates that are divisible by small primes, and some don't. The "weight" of a k is a relative measure of how many candidates survive the sieving process (i.e. aren't divisible by any small primes). High-weight k's produce many candidates (and are expected to produce many primes), and low-weight k's produce few candidates (and are expected to produce few primes). Known Sierpinski numbers like 78557 have weight 0, because every candidate is divisible by a small prime. (Some other known Sierpinski numbers use algebraic factorizations along with small primes to rule out the existence of a prime. Really the definition of "weight" should incorporate these algebraic factorizations too. But in any case none of the SoB k's has any algebraic factorizations.)

Seeing how SoB has gone to really large n values, are mathematicians rather certain that 78557 is the smallest Sierpinski number? I know there is no proof, but it appears to me, that some conjectures are thought to be true (like Riemann zeta) because there are lots of hints they are true.

Are there some arguments pro 78557 being the smallest Sierpinski number? If so, are there some ideas about the magnitude of n for the remaining k's?

Yves Gallot has made a calculator (link) that estimates the weight of any given k. (Try k = 3, 5, 55459, 67607, 78557, etc.) Using the weights of the SoB k's, you can predict how long they should take to produce a prime. Yves made some predictions in this 2001 paper, which have been remarkably accurate so far. I think this is the strongest evidence we have in favor of the conjecture being true: the weight of a multiplier k, after adjusting for algebraic factorizations, is empirically a good predictor of how frequently that k produces primes. So every k whose weight isn't literally 0 should eventually produce a prime.

The bad news: the conjecture is not likely to be proved any time soon. Given where we are right now, there is about a 93.5% chance that proving the conjecture will require finding a prime with over a billion digits; a 54% chance of over a trillion digits, 28% over 10^15 digits, 14% over 10^18 digits, etc. (Primes become less and less common as n grows, so asymptotically we expect a given k to produce about X primes below n = 2^(X/weight). Remember that n is itself an exponent, and all of these k's have very small weights.) So it's an uphill fight, to say the least.

Is there a point when such a large n is reached that doubt will be cast upon 78557 actually being the smallest Sierpinski number?

For each of the individual SoB k's, it's pretty surprising that they haven't produced a prime so far. (Very roughly, the five k's had 98%, 80%, 98.5%, 99.6%, and 76% chances respectively of producing primes below the current leading edge.) But there are a lot of odd numbers 1 < k < 78557, so it's not surprising that five of them have been "unlucky".

Maybe a more useful way to look at your question: given what we know now, and assuming that primes of the form k*2^n + 1 work how we expect them to, for what value of n would it be shocking if we haven't finished SoB by n? Let's say "shocking" means "<1% chance". Then the answer to the question is about n = 6 * 10^29, which corresponds to primes with 200 billion billion billion digits. If we get to that point and still haven't finished SoB, then it may be worthwhile for Skynet to take a break from number crunching and look for a theoretical reason it's not finding any primes.

SellymeProject donor
Send message
Joined: 12 Apr 11
Posts: 110
ID: 94633
Credit: 99,304,302
RAC: 0
321 LLR Ruby: Earned 2,000,000 credits (2,461,672)Cullen LLR Ruby: Earned 2,000,000 credits (2,773,349)ESP LLR Ruby: Earned 2,000,000 credits (2,353,670)Generalized Cullen/Woodall LLR Ruby: Earned 2,000,000 credits (3,893,820)PPS LLR Ruby: Earned 2,000,000 credits (2,273,773)PSP LLR Ruby: Earned 2,000,000 credits (4,180,341)SoB LLR Turquoise: Earned 5,000,000 credits (5,775,657)SR5 LLR Ruby: Earned 2,000,000 credits (4,966,427)SGS LLR Ruby: Earned 2,000,000 credits (2,518,084)TRP LLR Turquoise: Earned 5,000,000 credits (5,428,073)Woodall LLR Ruby: Earned 2,000,000 credits (4,186,617)321 Sieve (suspended) Ruby: Earned 2,000,000 credits (2,289,063)PPS Sieve Sapphire: Earned 20,000,000 credits (32,922,882)Sierpinski (ESP/PSP/SoB) Sieve (suspended) Silver: Earned 100,000 credits (196,262)TRP Sieve (suspended) Silver: Earned 100,000 credits (106,116)AP 26/27 Ruby: Earned 2,000,000 credits (2,243,865)GFN Sapphire: Earned 20,000,000 credits (20,732,665)
Message 140177 - Posted: 11 May 2020 | 16:03:35 UTC - in response to Message 140164.
Last modified: 11 May 2020 | 16:04:10 UTC

Given where we are right now, there is about a 93.5% chance that proving the conjecture will require finding a prime with over a billion digits; a 54% chance of over a trillion digits, 28% over 10^15 digits, 14% over 10^18 digits, etc.


So obviously the last few numbers in that list are pretty unfathomable, but megaprimes have gone from something that made the news to something we're discovering multiple of every week in a pretty short fashion. If we (falsely?) assume that hardware improvements don't slow down, are there any really significant hurdles on the march to gigaprimes in our lifetimes? It seems to me like GIMPS will get there, but does SoB scale effectively for that to be feasible?

wolfemancs
Send message
Joined: 25 Jun 09
Posts: 84
ID: 42483
Credit: 9,923,599
RAC: 0
321 LLR Silver: Earned 100,000 credits (113,597)Cullen LLR Silver: Earned 100,000 credits (224,304)ESP LLR Silver: Earned 100,000 credits (441,787)PPS LLR Silver: Earned 100,000 credits (117,225)PSP LLR Amethyst: Earned 1,000,000 credits (1,390,544)SoB LLR Amethyst: Earned 1,000,000 credits (1,966,668)SR5 LLR Silver: Earned 100,000 credits (157,374)SGS LLR Silver: Earned 100,000 credits (117,446)TRP LLR Silver: Earned 100,000 credits (237,230)Woodall LLR Silver: Earned 100,000 credits (309,305)321 Sieve (suspended) Silver: Earned 100,000 credits (200,118)Cullen/Woodall Sieve Bronze: Earned 10,000 credits (12,820)Generalized Cullen/Woodall Sieve (suspended) Gold: Earned 500,000 credits (559,780)PPS Sieve Amethyst: Earned 1,000,000 credits (1,650,670)Sierpinski (ESP/PSP/SoB) Sieve (suspended) Amethyst: Earned 1,000,000 credits (1,000,343)TRP Sieve (suspended) Gold: Earned 500,000 credits (528,122)AP 26/27 Gold: Earned 500,000 credits (700,724)GFN Silver: Earned 100,000 credits (195,536)
Message 140178 - Posted: 11 May 2020 | 16:30:24 UTC - in response to Message 140177.
Last modified: 11 May 2020 | 16:30:44 UTC

It was kind of hinted at in one of the previous replies, but I think it's worth pointing out (and it's probably covered better than I can in one of the links). The reason we know 78557 is a Sierpinski number is that it has been shown to have a so called "Covering Set"; a set of small primes that it can be shown with modular arithmetic to evenly divide k*2^n+1 for every n. (I think there are 19 of the primes, and it can be shown that if n/18 has remainder zero, this prime divides, 78557*2^n+1, and if n/18 has remainder 1, this other prime divides 78557*2^n+1, and so on for all 19 possible remainders of n/18)

All known Sierpinski numbers have a fairly small covering set.

All the ks remaining in SoB have been proven to NOT have a covering set of any size.

So the fact that we know they don't have a covering set gives us a little bit of hope that there will eventually be a prime for each of the remaining k.

This is all from memory of reading up on this 5-10 years ago... so please anyone who knows better feel free to correct my statements.

Ravi Fernando
Project administrator
Volunteer tester
Project scientist
Send message
Joined: 21 Mar 19
Posts: 211
ID: 1108183
Credit: 13,824,824
RAC: 7,626
321 LLR Amethyst: Earned 1,000,000 credits (1,214,472)Cullen LLR Silver: Earned 100,000 credits (111,878)ESP LLR Bronze: Earned 10,000 credits (16,570)Generalized Cullen/Woodall LLR Bronze: Earned 10,000 credits (68,801)PPS LLR Ruby: Earned 2,000,000 credits (4,672,204)PSP LLR Silver: Earned 100,000 credits (166,255)SoB LLR Silver: Earned 100,000 credits (258,849)SR5 LLR Bronze: Earned 10,000 credits (76,537)SGS LLR Silver: Earned 100,000 credits (220,642)TRP LLR Silver: Earned 100,000 credits (254,161)Woodall LLR Bronze: Earned 10,000 credits (97,444)321 Sieve (suspended) Turquoise: Earned 5,000,000 credits (5,001,667)AP 26/27 Bronze: Earned 10,000 credits (72,774)GFN Amethyst: Earned 1,000,000 credits (1,574,206)WW (retired) Bronze: Earned 10,000 credits (12,000)
Message 140180 - Posted: 11 May 2020 | 17:03:00 UTC - in response to Message 140178.

Good points, wolfemancs. (The covering set for 78557 is {3, 5, 7, 13, 19, 37, 73}.) A few comments, with apologies in advance for the pedantry:

All known Sierpinski numbers have a fairly small covering set.

Not quite: some Sierpinski numbers, such as 44745755^4, rely on algebraic factorizations combined with partial covering sets. JeppeSN discusses this here. But this can only happen when k is a perfect power, and none of the SoB k's fit that description.

All the ks remaining in SoB have been proven to NOT have a covering set of any size.

I think this is *technically* false. It's known that all SoB k's produce primes in the dual Sierpinski project, i.e. primes of the form 2^n + k. Any covering set for k in SoB is also a covering set in the dual Sierpinski problem. But technically, having a covering set doesn't mean you produce no primes--it means you produce no primes except possibly for the primes in the covering set. So e.g. k=67607 is known to produce at least two primes (or maybe PRPs, not sure if they've been tested with ECPP): 2^16389 + 67607 and 2^46549 + 67607. It follows that any covering set for k=67607 would need to include both of these rather large primes. It seems very unlikely that such a covering set exists, but I don't know how to prove that it doesn't.

Profile BurProject donor
Volunteer tester
Avatar
Send message
Joined: 25 Feb 20
Posts: 515
ID: 1241833
Credit: 414,481,880
RAC: 219
321 LLR Ruby: Earned 2,000,000 credits (2,092,823)Cullen LLR Ruby: Earned 2,000,000 credits (2,315,295)ESP LLR Ruby: Earned 2,000,000 credits (2,151,088)Generalized Cullen/Woodall LLR Ruby: Earned 2,000,000 credits (2,620,968)PPS LLR Jade: Earned 10,000,000 credits (16,474,243)PSP LLR Ruby: Earned 2,000,000 credits (2,064,832)SoB LLR Ruby: Earned 2,000,000 credits (2,434,466)SR5 LLR Ruby: Earned 2,000,000 credits (2,065,004)SGS LLR Ruby: Earned 2,000,000 credits (2,042,656)TRP LLR Ruby: Earned 2,000,000 credits (2,089,856)Woodall LLR Ruby: Earned 2,000,000 credits (2,112,258)321 Sieve (suspended) Ruby: Earned 2,000,000 credits (2,107,153)PPS Sieve Turquoise: Earned 5,000,000 credits (5,096,952)AP 26/27 Turquoise: Earned 5,000,000 credits (5,797,662)GFN Jade: Earned 10,000,000 credits (11,994,022)WW (retired) Double Silver: Earned 200,000,000 credits (349,980,000)PSA Amethyst: Earned 1,000,000 credits (1,042,601)
Message 140214 - Posted: 12 May 2020 | 16:18:05 UTC

Thank you for that detailed answer, that was exactly what I was hoping for. Unfortunately, I doubt I will even get a glimpse of why things are that way - the paper you quoted for example - but I really enjoy reading explanations such as yours.

98%, 80%, 98.5%, 99.6%, and 76% chances respectively of producing primes below the current leading edge.) But there are a lot of odd numbers 1 < k < 78557, so it's not surprising that five of them have been "unlucky".
That means, there are say 100 k's with a 98% chance of generating a prime with n < 14M, so finding 2 where it's larger was to be expected?

asymptotically we expect a given k to produce about X primes below n = 2^(X/weight)
I'm not sure I got that, to calculate X for a given weight and n I would rearrange to X = log2(n) * weight? And to calculate at which n a given k probably produces a prime is done by X = 1?

All the ks remaining in SoB have been proven to NOT have a covering set of any size.
I thought exactly that was NOT proven. Because otherwise we'd already know they aren't Sierpinski numbers? Having a covering set is a necessary requirement for a Sierpinski number, I think.

Or do I get the nature of "covering set" wrong? I think it means every number produced by that k will be divisible by at least one of the members of the set. So that k cannot produce a prime because if it's divisible by a member of the set it isn't a prime.

If it is prove a k does not have a covering set of any size, that means that the k can produce numbers that aren't divisible by any number than themselves, i.e. a prime and so it's not a Sierpinski number.

Profile JeppeSNProject donor
Avatar
Send message
Joined: 5 Apr 14
Posts: 1824
ID: 306875
Credit: 50,010,396
RAC: 13,769
Found 1 prime in the 2020 Tour de Primes321 LLR Gold: Earned 500,000 credits (593,283)Cullen LLR Gold: Earned 500,000 credits (611,298)ESP LLR Silver: Earned 100,000 credits (174,818)Generalized Cullen/Woodall LLR Silver: Earned 100,000 credits (112,799)PPS LLR Jade: Earned 10,000,000 credits (19,779,692)PSP LLR Gold: Earned 500,000 credits (598,093)SoB LLR Silver: Earned 100,000 credits (466,812)SR5 LLR Silver: Earned 100,000 credits (210,142)SGS LLR Silver: Earned 100,000 credits (136,265)TRP LLR Silver: Earned 100,000 credits (476,246)Woodall LLR Silver: Earned 100,000 credits (281,400)321 Sieve (suspended) Silver: Earned 100,000 credits (175,037)Cullen/Woodall Sieve Bronze: Earned 10,000 credits (22,952)PPS Sieve Bronze: Earned 10,000 credits (10,113)AP 26/27 Bronze: Earned 10,000 credits (12,129)GFN Ruby: Earned 2,000,000 credits (4,980,148)WW (retired) Jade: Earned 10,000,000 credits (13,756,000)PSA Turquoise: Earned 5,000,000 credits (7,614,290)
Message 140216 - Posted: 12 May 2020 | 16:56:09 UTC - in response to Message 140214.

All the ks remaining in SoB have been proven to NOT have a covering set of any size.
I thought exactly that was NOT proven.


It is not proved that they do not have a covering set, but it would have to consist of (unrealistically?) many and large primes.

Because otherwise we'd already know they aren't Sierpinski numbers? Having a covering set is a necessary requirement for a Sierpinski number, I think.


Not proved.

Most numbers that we can prove Sierpiński, have a covering set. As Ravi said, some numbers k that we can prove Sierpiński, have instead a combination of algebraic factorizations and a prime set that only "covers" the remaining cases for the exponent. This happens in many cases where k is a perfect power.

But: We have no proof that some crazy k could not be Sierpiński without matching the above description of numbers that we can prove Sierpiński.

Or do I get the nature of "covering set" wrong? I think it means every number produced by that k will be divisible by at least one of the members of the set. So that k cannot produce a prime because if it's divisible by a member of the set it isn't a prime.


That is correct.

If it is prove a k does not have a covering set of any size, that means that the k can produce numbers that aren't divisible by any number than themselves, i.e. a prime and so it's not a Sierpinski number.


No, see above. We do not know that there cannot exist a k that produces no prime for other reasons than covering sets, or algebraic factorizations.

/JeppeSN

Ravi Fernando
Project administrator
Volunteer tester
Project scientist
Send message
Joined: 21 Mar 19
Posts: 211
ID: 1108183
Credit: 13,824,824
RAC: 7,626
321 LLR Amethyst: Earned 1,000,000 credits (1,214,472)Cullen LLR Silver: Earned 100,000 credits (111,878)ESP LLR Bronze: Earned 10,000 credits (16,570)Generalized Cullen/Woodall LLR Bronze: Earned 10,000 credits (68,801)PPS LLR Ruby: Earned 2,000,000 credits (4,672,204)PSP LLR Silver: Earned 100,000 credits (166,255)SoB LLR Silver: Earned 100,000 credits (258,849)SR5 LLR Bronze: Earned 10,000 credits (76,537)SGS LLR Silver: Earned 100,000 credits (220,642)TRP LLR Silver: Earned 100,000 credits (254,161)Woodall LLR Bronze: Earned 10,000 credits (97,444)321 Sieve (suspended) Turquoise: Earned 5,000,000 credits (5,001,667)AP 26/27 Bronze: Earned 10,000 credits (72,774)GFN Amethyst: Earned 1,000,000 credits (1,574,206)WW (retired) Bronze: Earned 10,000 credits (12,000)
Message 140218 - Posted: 12 May 2020 | 18:06:43 UTC - in response to Message 140214.

Or do I get the nature of "covering set" wrong? I think it means every number produced by that k will be divisible by at least one of the members of the set. So that k cannot produce a prime because if it's divisible by a member of the set it isn't a prime.

Another technical point: if k*2^n + 1 is divisible by a member of your covering set, that doesn't entirely guarantee that it's not prime. After all, every prime is divisible by itself. In fact, if you're okay with "covering sets" being infinite, the set of all primes is a covering set for every k! (Proof: for all k and all n, k*2^n + 1 is greater than 1, so it's divisible by (and possibly equal to) some prime.) But of course not all k's are Sierpinski numbers.

For this reason, it's best to consider only finite covering sets. In this case, it's believed (but I think not proved) that some Sierpinski numbers with algebraic factorizations have no (finite) covering set. JeppeSN asked recently whether it's possible to construct a k that has a covering set but nonetheless produces at least one prime k*2^n + 1 (which would necessarily be an element of the covering set). I have no idea whether it's possible, but I don't see any obvious reason it isn't.

numbermaniac
Volunteer tester
Send message
Joined: 28 Mar 14
Posts: 210
ID: 305955
Credit: 16,715,344
RAC: 35,938
321 LLR Amethyst: Earned 1,000,000 credits (1,002,294)PPS LLR Ruby: Earned 2,000,000 credits (2,136,188)PSP LLR Bronze: Earned 10,000 credits (61,731)SR5 LLR Amethyst: Earned 1,000,000 credits (1,085,075)SGS LLR Ruby: Earned 2,000,000 credits (3,515,147)TRP LLR Ruby: Earned 2,000,000 credits (2,015,699)321 Sieve (suspended) Gold: Earned 500,000 credits (512,303)Generalized Cullen/Woodall Sieve (suspended) Gold: Earned 500,000 credits (503,510)PPS Sieve Ruby: Earned 2,000,000 credits (2,002,374)Sierpinski (ESP/PSP/SoB) Sieve (suspended) Bronze: Earned 10,000 credits (34,269)TRP Sieve (suspended) Bronze: Earned 10,000 credits (32,679)AP 26/27 Gold: Earned 500,000 credits (610,493)GFN Ruby: Earned 2,000,000 credits (3,049,874)PSA Silver: Earned 100,000 credits (141,661)
Message 140240 - Posted: 14 May 2020 | 15:21:41 UTC - in response to Message 140180.
Last modified: 14 May 2020 | 15:22:14 UTC

Ravi Fernando wrote:
So e.g. k=67607 is known to produce at least two primes (or maybe PRPs, not sure if they've been tested with ECPP): 2^16389 + 67607 and 2^46549 + 67607.

It appears the first of these two numbers was proven prime just 2 months ago: http://factordb.com/index.php?id=1100000000537223829.
____________
1 PPSE (+2 DC) & 5 SGS primes

dukebg
Volunteer tester
Avatar
Send message
Joined: 21 Nov 17
Posts: 242
ID: 950482
Credit: 23,670,125
RAC: 0
Found 1 prime in the 2018 Tour de Primes321 LLR Gold: Earned 500,000 credits (506,942)Cullen LLR Gold: Earned 500,000 credits (500,523)ESP LLR Gold: Earned 500,000 credits (655,642)Generalized Cullen/Woodall LLR Gold: Earned 500,000 credits (539,100)PPS LLR Gold: Earned 500,000 credits (688,232)PSP LLR Gold: Earned 500,000 credits (561,629)SoB LLR Ruby: Earned 2,000,000 credits (3,659,676)SR5 LLR Gold: Earned 500,000 credits (505,810)SGS LLR Gold: Earned 500,000 credits (506,024)TRP LLR Gold: Earned 500,000 credits (963,625)Woodall LLR Gold: Earned 500,000 credits (506,044)321 Sieve (suspended) Gold: Earned 500,000 credits (511,694)Generalized Cullen/Woodall Sieve (suspended) Gold: Earned 500,000 credits (549,916)PPS Sieve Gold: Earned 500,000 credits (701,168)AP 26/27 Gold: Earned 500,000 credits (525,590)GFN Jade: Earned 10,000,000 credits (10,762,872)WW (retired) Gold: Earned 500,000 credits (500,000)PSA Gold: Earned 500,000 credits (525,639)
Message 140241 - Posted: 14 May 2020 | 16:26:35 UTC - in response to Message 140240.

Ravi Fernando wrote:
So e.g. k=67607 is known to produce at least two primes (or maybe PRPs, not sure if they've been tested with ECPP): 2^16389 + 67607 and 2^46549 + 67607.

It appears the first of these two numbers was proven prime just 2 months ago: http://factordb.com/index.php?id=1100000000537223829.

Oh, that was most likely a lucky happenstance. Masaki UKAI runs ECPP basically for all PRPs in FDB of that size. 4.9K dd is pretty small, just few hours on modern hardware. I don't think they ran this exact number on purpose.

dukebg
Volunteer tester
Avatar
Send message
Joined: 21 Nov 17
Posts: 242
ID: 950482
Credit: 23,670,125
RAC: 0
Found 1 prime in the 2018 Tour de Primes321 LLR Gold: Earned 500,000 credits (506,942)Cullen LLR Gold: Earned 500,000 credits (500,523)ESP LLR Gold: Earned 500,000 credits (655,642)Generalized Cullen/Woodall LLR Gold: Earned 500,000 credits (539,100)PPS LLR Gold: Earned 500,000 credits (688,232)PSP LLR Gold: Earned 500,000 credits (561,629)SoB LLR Ruby: Earned 2,000,000 credits (3,659,676)SR5 LLR Gold: Earned 500,000 credits (505,810)SGS LLR Gold: Earned 500,000 credits (506,024)TRP LLR Gold: Earned 500,000 credits (963,625)Woodall LLR Gold: Earned 500,000 credits (506,044)321 Sieve (suspended) Gold: Earned 500,000 credits (511,694)Generalized Cullen/Woodall Sieve (suspended) Gold: Earned 500,000 credits (549,916)PPS Sieve Gold: Earned 500,000 credits (701,168)AP 26/27 Gold: Earned 500,000 credits (525,590)GFN Jade: Earned 10,000,000 credits (10,762,872)WW (retired) Gold: Earned 500,000 credits (500,000)PSA Gold: Earned 500,000 credits (525,639)
Message 140243 - Posted: 14 May 2020 | 17:22:01 UTC

A more on-topic message.
I started typing a message about why would the covering set from the dual problem automatically become a covering set in the "non-dual" problem. But then I figured it out on my own. Fun math.

Profile BurProject donor
Volunteer tester
Avatar
Send message
Joined: 25 Feb 20
Posts: 515
ID: 1241833
Credit: 414,481,880
RAC: 219
321 LLR Ruby: Earned 2,000,000 credits (2,092,823)Cullen LLR Ruby: Earned 2,000,000 credits (2,315,295)ESP LLR Ruby: Earned 2,000,000 credits (2,151,088)Generalized Cullen/Woodall LLR Ruby: Earned 2,000,000 credits (2,620,968)PPS LLR Jade: Earned 10,000,000 credits (16,474,243)PSP LLR Ruby: Earned 2,000,000 credits (2,064,832)SoB LLR Ruby: Earned 2,000,000 credits (2,434,466)SR5 LLR Ruby: Earned 2,000,000 credits (2,065,004)SGS LLR Ruby: Earned 2,000,000 credits (2,042,656)TRP LLR Ruby: Earned 2,000,000 credits (2,089,856)Woodall LLR Ruby: Earned 2,000,000 credits (2,112,258)321 Sieve (suspended) Ruby: Earned 2,000,000 credits (2,107,153)PPS Sieve Turquoise: Earned 5,000,000 credits (5,096,952)AP 26/27 Turquoise: Earned 5,000,000 credits (5,797,662)GFN Jade: Earned 10,000,000 credits (11,994,022)WW (retired) Double Silver: Earned 200,000,000 credits (349,980,000)PSA Amethyst: Earned 1,000,000 credits (1,042,601)
Message 140244 - Posted: 14 May 2020 | 17:42:52 UTC

About the weight estimator, even with the help of the linked paper I couldn't figure out what N and P are.

Is N the number of results for the sequence k*2^n+1 we want to consider? But wouldn't that be identical to n? And P is the largest prime to consider?

For example if I wanted to estimate how many primes occur within the first 1M results of 5*2^n+1, what would I plug into the website? And is using X = log2(n)*weight the correct way to determine the number of primes?

Ravi Fernando
Project administrator
Volunteer tester
Project scientist
Send message
Joined: 21 Mar 19
Posts: 211
ID: 1108183
Credit: 13,824,824
RAC: 7,626
321 LLR Amethyst: Earned 1,000,000 credits (1,214,472)Cullen LLR Silver: Earned 100,000 credits (111,878)ESP LLR Bronze: Earned 10,000 credits (16,570)Generalized Cullen/Woodall LLR Bronze: Earned 10,000 credits (68,801)PPS LLR Ruby: Earned 2,000,000 credits (4,672,204)PSP LLR Silver: Earned 100,000 credits (166,255)SoB LLR Silver: Earned 100,000 credits (258,849)SR5 LLR Bronze: Earned 10,000 credits (76,537)SGS LLR Silver: Earned 100,000 credits (220,642)TRP LLR Silver: Earned 100,000 credits (254,161)Woodall LLR Bronze: Earned 10,000 credits (97,444)321 Sieve (suspended) Turquoise: Earned 5,000,000 credits (5,001,667)AP 26/27 Bronze: Earned 10,000 credits (72,774)GFN Amethyst: Earned 1,000,000 credits (1,574,206)WW (retired) Bronze: Earned 10,000 credits (12,000)
Message 140254 - Posted: 15 May 2020 | 0:57:17 UTC - in response to Message 140244.

About the weight estimator, even with the help of the linked paper I couldn't figure out what N and P are.

Yves can correct me if I have any of this wrong, but I believe the calculator estimates the weight of k by counting how many n's between 1 and N are not sieved out by primes less than P. In any case, their only effect on the calculation is that increasing P and N makes the calculation slower and more accurate. The default values are pretty good, and multiplying them by 10 or so will give a little more accuracy.
And is using X = log2(n)*weight the correct way to determine the number of primes?

That's a reasonable heuristic, at least if n is big enough. I haven't checked this against the data, but the following is probably a little more accurate in general: the number of primes with min < n < max should behave like a Poisson random variable with parameter log2((max + log2(k))/(min + log2(k))) * weight. (For a Poisson random variable, parameter = mean = variance.) The log2(k) terms are often negligible, but if k is large and you're starting at min = 1, then it's probably better to leave them in.

Message boards : Seventeen or Bust : Are people even sure 78557 is the smallest k?

[Return to PrimeGrid main page]
DNS Powered by DNSEXIT.COM
Copyright © 2005 - 2023 Rytis Slatkevičius (contact) and PrimeGrid community. Server load 1.47, 1.28, 1.29
Generated 2 Jun 2023 | 16:10:59 UTC