fond of a factor? Urn yourself to become remains

[Batalov]

M90000217 has a factor: 2333366452928036056367

k = 11 * 23 * 51237611483

[Brain]

Originally Posted by ckdo

M13828261 has a factor: 1979553586274192263311048622055057969

121 bits and prime.

k = 2^3*13*71*397*160751*262651*556559*1039067

P-1 found a factor in stage #2, B1=660000, B2=18975000.
M55556251 has a factor: 550381179251347282574411233541551 (108.8 bits)
k == 275190589625673641287205616770775 == 3 * 5 * 5 * 7 * 41 * 71 * 1747 * 2693 * 178307 * 3863683

New personal lifetime record! ;-)
2nd largest I've seen in this thread (Yes, factor is prime). Sorry for posting this in LMH. I had to tell.

[TheJudger]

M59715763 has a factor: 897894732457600805887
M59715763 has a factor: 947242006352100744497
found 2 factor(s) for M59715763 from 2^69 to 2^70 [mfaktc 0.18-pre1 barrett79_mul32]

Those two factors are not big or special. Just the first time that I've noticed that I found two factors at one bitlevel on some real work.

Oliver

[ET_]

M3321935569 has a factor: 1937278552181490609610657

At 80 bits, it's the latgest for OBD.

Luigi

[TheJudger]

Hi Luigi,

nice find, you need to update to graph on the bottom here: http://www.moregimps.it/billion/factors_stats.php.
Seems that you "forget" factors > 2^80 when you've build the stats.

Oliver

[ET_]

Originally Posted by TheJudger

Hi Luigi,

nice find, you need to update to graph on the bottom here: http://www.moregimps.it/billion/factors_stats.php.
Seems that you "forget" factors > 2^80 when you've build the stats.

Oliver

I already noticed the glitch and am working on it, thanks.
The problem seems to be the size of the array of values passed to the graphic function.
I hope to squash it down today.

Luigi

[TheJudger]

My latest P-1 factor:

M55824233 has a factor: 833043841114609831879 (69.49 Bits; k = 7461310226283 = 3 * 3 * 29 * 167 * 373 * 547 * 839)

I think this is my smallest "largest factor of k". (*damn* how do I explain this in english correctly?)

Oliver

[Christenson]

Originally Posted by TheJudger

My latest P-1 factor:

M55824233 has a factor: 833043841114609831879 (69.49 Bits; k = 7461310226283 = 3 * 3 * 29 * 167 * 373 * 547 * 839)

I think this is my smallest "largest factor of k". (*damn* how do I explain this in english correctly?)

Oliver

That's clear, except that small size of the factors is referred to as smoothness...thus:
I think this is the smoothest k I have found.
********
I have found more P-1 factors than TF factors!

[cmd]

Originally Posted by ET_

I already noticed the glitch and am working on it, thanks.
The problem seems to be the size of the array of values passed to the graphic function.
I hope to squash it down today.

Luigi

fuori_classi_fic_azione (it)

notare com'è curioso come nel primo milione dei (n)umeri per i (p)rimi
si trovi solo uno così fattorizzato da sei ...


(p.s.
adesso noi torniamo in -pausa " f e r i e " fino a 7mbre
a s'ngh'°_str_°zz'° ... avant&ndre


pps ... state facendo un buon lavoro ... ma ancora lontani ... medi_ta_te sul ... ranges

[drh]

Originally Posted by TheJudger

My latest P-1 factor:

M55824233 has a factor: 833043841114609831879 (69.49 Bits; k = 7461310226283 = 3 * 3 * 29 * 167 * 373 * 547 * 839)

I think this is my smallest "largest factor of k". (*damn* how do I explain this in english correctly?)

Oliver

I was curious if I had any factors as "smooth" as this, and a few weeks ago I found this by P-1:

M54640559 has a factor: 20597868276842499067951 (74.12 Bits)
k = 188485153280025 = 3 * 5² * 7² * 43 * 109 * 149 * 271²

Doug

[firejuggler]

M56463703 has a factor : 573344166830508042119

k= 5077103841653 (prime)
nice one i think