fond of a factor? Urn yourself to become inane

[petrw1]

re: Post 1831

Originally Posted by James Heinrich

You do (manual results form was changed several months ago to detect and handle this).

Seems it doesn't:

Manual testing	28722943	F	2021-04-02 22:40	0.0	Factor: 4578986428371835478041 / TF: 71-72	15.9100
Manual testing	28723249	F	2021-04-02 22:40	0.0	Factor: 3416851867143956961289 / TF: 71-72	8.8773
Manual testing	28725779	F	2021-04-02 22:40	0.0	Factor: 3325594725067066329023 / TF: 71-72	8.2263
Manual testing	28721831	NF	2021-04-02 22:40	0.0	no factor from 2^71 to 2^72	16.6513

[James Heinrich]

Originally Posted by petrw1

Seems it doesn't

Sorry, you're right. The change I was thinking of relates to detecting whether the result claims to be full-range TF or not, and some related code that handles composite factors found by TF, but the actual PrimeNet code that calculates and applies credit is outside my zone-of-control, and does not currently have any mechanism for specifying whether a range was complete or not. The data is available to the manual results form, it just can't pass that information on to where the credit is calculated and applied. Such a change would need to be applied at the George level.

[firejuggler]

M27151489 has a 76.836-bit (24-digit) factor: 134831419346216729059463 (P-1,B1=1350000,B2=109350000)

low bit but k= 7 × 11 × 349 337 × 92 306 471 , really close to my B2 bound

[petrw1]

https://www.mersenne.org/report_expo...8190299&full=1


Factor: 4299246979573209796361 / TF: 71-72
Factor: 4001656651216207394857 / TF: 71-72

0.1 bits apart

[firejuggler]

Found a new record for me

M27155813 has a 112.563-bit (34-digit) factor: 7669084564727955238545079945517857 (P-1,B1=1350000,B2=109350000)

[Jwb52z]

P-1 found a factor in stage #2, B1=746000, B2=20430000.
UID: Jwb52z/Clay, M103478927 has a factor: 118012953390073941784591 (P-1, B1=746000, B2=20430000).

76.643 bits.