![]() |
![]() |
#2025 | |
"James Heinrich"
May 2004
ex-Northern Ontario
2×11×132 Posts |
![]()
George just found a pretty one (#16 biggest ever):
Quote:
Last fiddled with by James Heinrich on 2022-01-11 at 15:06 |
|
![]() |
![]() |
![]() |
#2026 | |
Feb 2017
Nowhere
5,791 Posts |
![]() Quote:
M80309/10572519233/367135192227544403816033004684216729776734999 and M80309/10572519233 were the same. Is there some obvious reason for this? (My wits are presently addled by symptoms of a head cold...) |
|
![]() |
![]() |
![]() |
#2027 | |
"James Heinrich"
May 2004
ex-Northern Ontario
2×11×132 Posts |
![]() Quote:
Last fiddled with by James Heinrich on 2022-01-11 at 21:56 |
|
![]() |
![]() |
![]() |
#2028 | |
Feb 2017
Nowhere
5,791 Posts |
![]() Quote:
The OP in that thread seems to say that when subsequent PRP-CF tests say C, the new PRP-CF residue replaces previous PRP-CF residues. This would certainly account for all reported PRP-CF residues being the same (assuming the remaining cofactor has tested composite). Why this would be done is beyond me, but the only alternative explanation that fits the facts seems to be that, as long as the remaining CF has tested composite, the original PRP residue is simply repeated. There may be good reasons for not publishing the sequence of actual PRP residues (mod 1616) for the composite cofactors, of which I am ignorant. [I am rejecting the idea that the residues (mod 1616) from the PRP-CF tests are all actually the same.] Of course, if the remaining CF tests as a PRP, the "all PRP residues are the same" goes out the window, and the residue is reported as PRP_PRP_PRP_PRP_ . |
|
![]() |
![]() |
![]() |
#2029 |
Jun 2003
10100111101102 Posts |
![]()
As I mentioned in that other thread, the residues produced are the same. You're assuming PRP-CF does a standard Fermat test; it does NOT.
Let N=Mp/f Instead of checking 3^(N-1)==1 (mod N) (equivalently 3^N==3 (mod N)), it computes 3^(N*f+1)=3^(Mp+1)==3^(f+1) (mod N) Note. 3^N==3 ==> 3^Nf == 3^f ==> 3^(Nf+1) == 3^(f+1) This gives rise to same residue, since we're always computing the same expression 3^(Mp+1). Advantages: 1) Each run produces same residue, hence multiple runs acts as additional checks on previous runs. 2) Since the modified computation is just a series of squarings, it is now amenable to GEC and CERT. |
![]() |
![]() |
![]() |
#2030 | |
Feb 2017
Nowhere
169F16 Posts |
![]() Quote:
I had actually thought of the possibility that subsequent tests were simply looking at 3^(M + 1) (mod N) where N is the cofactor; N divides M = Mp. Suppose 3^(M+1) = M*q + R where 0 < R < M. Then, yes, N certainly divides 3^(M+1) - R = M*q = N*f*Q, so R may be considered to be "the residue" in that sense. However, what I usually think of as the "residue of 3^(M+1) (mod N)" is r, where 3^(M+1) = N*Q + r, and 0 < r < N. Clearly r is just R reduced mod N. Generally, r will be less than R. It was not clear to me why R - r would be divisible by 264. |
|
![]() |
![]() |
![]() |
#2031 | |
Jan 2021
California
6108 Posts |
![]() Quote:
ETA: This means that if the full residue of the PRP were saved, any time a (new) factor were found, the remaining cofactor could be checked against the original residue to see if it's PRP. Last fiddled with by slandrum on 2022-01-12 at 21:48 Reason: Additional thought |
|
![]() |
![]() |
![]() |
#2032 | |
Feb 2017
Nowhere
5,791 Posts |
![]() Quote:
Now 3^(M+1) = 3^(f*N + 1) = 3^(f*(N-1) + f + 1) = (3^(N-1))f * 3^(f+1). So if 3^(N-1) == 1 (mod N) we have (3^(N-1))f == 1 (mod N), and R == 3^(f+1) (mod N). Thus, if R =/= 3^(f+1) (mod N), the cofactor N is definitely composite. Done. No standard Fermat test needed. However, if R == 3^(f+1) (mod N) it does not follow that N is a base-3 Fermat PRP, i.e. that 3^(N-1) == 1 (mod N). Only that (3^(N-1)))f == 1 (mod N). I know, gcd(f, eulerphi(N)) would have to be greater than 1 in order for 3^(N-1) not to be congruent to 1 (mod N). That seems extremely unlikely to me, and I am confident that no examples are known, but I don't know that it's impossible. |
|
![]() |
![]() |
![]() |
#2033 |
Sep 2002
24·3·17 Posts |
![]()
P-1 found a factor in stage #2, B1=766000, B2=25093000.
UID: Jwb52z/Clay, M108524239 has a factor: 952615068857130427852757781191 (P-1, B1=766000, B2=25093000) 99.588 bits. |
![]() |
![]() |
![]() |
#2034 |
"Vincent"
Apr 2010
Over the rainbow
2,843 Posts |
![]()
M8590991 has a 121.408-bit (37-digit) factor: 3527086255292055773928440628536263153 (P-1,B1=1560000,B2=627605550)
another big one. |
![]() |
![]() |
![]() |
#2035 | |
"James Heinrich"
May 2004
ex-Northern Ontario
2×11×132 Posts |
![]()
Two nice first-factor finds by anonymous:
Quote:
Last fiddled with by James Heinrich on 2022-01-17 at 22:50 |
|
![]() |
![]() |
![]() |
Thread Tools | |
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Factor found that should have been found by P-1 | tha | Data | 65 | 2020-08-05 21:11 |
F12 factor found? | johnadam74 | FermatSearch | 16 | 2016-11-03 12:10 |
TF Factor Found CPU Credit | TheMawn | GPU Computing | 3 | 2013-06-17 06:21 |
found this factor | tha | Factoring | 4 | 2007-06-18 19:56 |
After a factor is found it keeps on going | jocelynl | Software | 6 | 2004-08-07 01:31 |