69.5M-70M to 2^62

[tom11784]

Not sure how long this will take, but I'm gonna let my computer go at it once it finishes its current job.

[tom11784]

taking up space, watch the dancing bananas:

[hbock]

Let the range run for 60 bit at first (FactorOverride=60). Up to 62 bit (independent from the CPU you are using) the time spent for factoring is doubling for each bit so you can estimate the end date and choose your final limit.
Of course you can do what you want, but first you can this way obtain much more factors in the same time at the beginning and secondly a completed range is better to handle for us than an incompleted.

[tom11784]

On my P4 2.4 it says it should take roughly 5 weeks to do the range to 2^62, which compared to that being how long it took to run an LL on a 33M doesn't seem as long. If you prefer, I can break the reports into sections at say 2 week intervals (should be like 69.5M-69.7M, 69.7M-69.9M, 69.9M to 70M). Also, the 3 factors found thus far are all greater than 2^60. I don't mean to sound rude, but I feel confident my computer can handle the range in a relatively short amount of time.

[garo]

You may wanna check this thread out which talks about the unsuitability of P4s for factoring upto 62 bits.
http://www.mersenneforum.org/viewtopic.php?t=725

But while that is suboptimal for the project it's your computer and you may do whatever you want with it and I'm sure GIMPS appreciates every contribution you make.

[tom11784]

current status: (all times are in EDT)

desktop (P4 2.4GHz) - 69.5000-69.5259M completed - 59 to 62 bit ~ 13 min - last report 9/5/3 0920

work (P3 866MHz) - 69.8000-69.8005M completed - 60 to 62 bit ~ 15 min - last report 9/5/3 1455

laptop (P4M 1.8GHz) - 69.9000-69.9057M completed - 59 to 62 bit ~ 25 min - last report 9/5/3 0920

times are for when nothing else is running

[tom11784]

update as of 9/9/3, 13:00 EDT (17:00 UTC)

desktop - worktodo (69.50-69.779)
submitted 69.50-69.53852M to 62 bits (listed in today's nofactor.cmp)
working around 69.54 right now

work - worktodo (69.779-69.90)
completed (not submitted) 69.80-69.81655M to 62 bits
also taking 69.779-69.8 at front of range from desktop's worktodo

laptop - worktodo (69.90-70.00)
completed (not submitted) 69.90 to around 69.914M to 62 bits

Hoping to be done with this range somewhere in early to middle October, and will give updates probably weekly

[tom11784]

holy cow where did the month go? - update time
the nofactor.zip mentioned is the 10/9 one


desktop (69.50-69.725)
69.50-69.6433 factored to 62 (in nofactor.zip)
69.6433-69.6673 factored to 62 (submitted)
69.6673-69.725 at 59 bits

work (69.725-69.90)
69.725-69.74 at 59 bits
69.74-69.779 factored to 62 bits (submitted)
69.779-69.8634 factored to 62 (in nofactor.zip)
69.8634-69.90 factored to 62 bits (submitted)

laptop (69.90-70.00)
69.90-69.95545 factored to 62 (in nofactor.zip)
69.95545-69.9827 factored to 62 bits (submitted)
69.9827-69.99 at 59 bits
69.99-70.00 at 60 bits

[tom11784]

as of 11/9 nofactor file (all numbers first three digits of 69.XXX)

desktop (000-199, 500-699)
000-003 - 61 bits (in nofactor)
004-070 - 61 bits (not submitted)
071-199 - 60 bits
500-699 - 62 bits (in nofactor)

work (200-499, 725-899)
200-499 - 60 bits
725-739 - 62 bits (not submitted)
740-899 - 62 bits (in nofactor)

laptop (700-724, 900-999)
700-704 - 62 bits (in nofactor)
705-708 - 62 bits (not submitted)
709-724 - 59 bits
900-999 - 62 bits (in nofactor)