[QUOTE=lavalamp;257351]There's only 1 unfactored candidate at 82 bits, and there are at least 16 candidates at 81 bits (or higher), so the level should be 15.02.

Though when ET_ put 3321929827 back after running it further, it looks like the factored status was not restored, so the MoreGIMPS site is simultaneously showing as factored in one table, and available for reservation in another.[/QUOTE]

I was sure I'd chosen 3321929927... :smile: I didn't want to take a factored exponent to 82...

Oh, well... factor restored.

Luigi

M3321997139 has a factor: 2490820565473300681
found 1 factor(s) for M3321997139 from 2^60 to 2^72 [mfaktc 0.16-Win 75bit_mul32]
no factor for M3321931777 from 2^78 to 2^79 [mfaktc 0.16-Win barrett79_mul32]
no factor for M3321931829 from 2^78 to 2^79 [mfaktc 0.16-Win barrett79_mul32]
no factor for M3321931919 from 2^78 to 2^79 [mfaktc 0.16-Win barrett79_mul32]
no factor for M3321931931 from 2^78 to 2^79 [mfaktc 0.16-Win barrett79_mul32]
no factor for M3321931967 from 2^78 to 2^79 [mfaktc 0.16-Win barrett79_mul32]
no factor for M3321931993 from 2^78 to 2^79 [mfaktc 0.16-Win barrett79_mul32]
no factor for M3321932093 from 2^78 to 2^79 [mfaktc 0.16-Win barrett79_mul32]
no factor for M3321934909 from 2^77 to 2^78 [mfaktc 0.16-Win barrett79_mul32]
no factor for M3321934909 from 2^78 to 2^79 [mfaktc 0.16-Win barrett79_mul32]

also, is it possible to have a file with the status of 'unreleased' exponent?

[QUOTE=firejuggler;257489]also, is it possible to have a file with the status of 'unreleased' exponent?[/QUOTE][COLOR="Silver"][SIZE="2"]You may want to search my posts in the OBD forum for posts with zip file attached.[/SIZE][/COLOR]:whistle:

Uncwilly, do you maintain the unreserved exponents? I have done some work on a couple of them either. :smile:

Luigi

I have not kept up to date with any thing since they were posted. Once I turned them over to you, I let you be the central point of information.

M3321936169 no factor from 60.000 bits to 71.000 bits.

Rodrigo

P.S. Luigi, may I PM you on a different OBD matter?

no factor for M3321928307 from 2^80 to 2^81 [mfaktc 0.16p1-Win barrett92_mul32]

Factor4 has found two factors for 3321936227 in the first couple of hours. Should I report them, stop work on this exponent, and move on to the next one? Or should I keep working on 3321936227 to 71 bits as planned, and then report?

Rodrigo

[QUOTE=Rodrigo;257792]Factor4 has found two factors for 3321936227 in the first couple of hours. Should I report them, stop work on this exponent, and move on to the next one? Or should I keep working on 3321936227 to 71 bits as planned, and then report?

Rodrigo[/QUOTE]

:smile:

After you completed the bit-depth where you found your last factor, its' up to you. My personal opinion is that Factor4 is better suited for smaller bit ranges, and you will find more factors in the low end.

BTW, didn't you want to PM me about something? :razz:

Luigi

[QUOTE=ET_;257795]
After you completed the bit-depth where you found your last factor, its' up to you. My personal opinion is that Factor4 is better suited for smaller bit ranges, and you will find more factors in the low end.
[/QUOTE]
Luigi,

Thanks!

Initially I leaned toward reporting the factors and moving on to the next exponent, on the theory that one purpose of OBD is to identify candidates for billion-digit primes: once a factor is found, it can no longer be a prime, ergo...

But I wasn't sure if it was better (for housekeeping or administrative reasons) to take the exponent to the pledged 71 bits.

So, unless somebody objects, I'll report the results that I got and start on my next exponent.

I'll PM you on my other question. :smile:

Rodrigo

no factor for M3321928241 from 2^81 to 2^82 [mfaktc 0.16-Win barrett92_mul32]
( second exponent is running-third will be even later)