20150406, 14:59  #1 
Feb 2003
256_{8} Posts 
Extremely lucky assignments
I just checked my results and discovered that I found factors for 10 exponents in the last 24 hours (vs my usual rate of ~2/week)
http://www.gpu72.com/reports/worker/...6098b4e529221/ 
20150406, 15:06  #2  
"Kieren"
Jul 2011
In My Own Galaxy!
2·3·1,693 Posts 
Quote:


20150406, 18:03  #3 
Apr 2007
Spessart/Germany
2×3^{4} Posts 
yes that looks nice^^ and you raised above the expectet number of factors (100 vs 94.6) I myself never found more than 2 factors/day with mfaktc 
20150406, 18:28  #4  
"/X\(‘‘)/X\"
Jan 2013
3×977 Posts 
Quote:
That's very unusual. Even though I have roughly triple the throughput, and I'm working at a lower bit depth, I don't believe I've ever found ten in a day. Last fiddled with by Mark Rose on 20150406 at 18:30 

20150407, 01:54  #5 
Feb 2003
2×3×29 Posts 
I went back to look at the mfakto output logs and, even more surprisingly, I had 10 consecutive assignments with a factor found between 2^71 and 2^74 and the total time from the first reported factor [Sun Apr 5 16:55:30 2015] to the last one [Sun Apr 5 23:34:51 2015] was under 7 hours.

20150407, 03:31  #6 
Romulan Interpreter
Jun 2011
Thailand
9452_{10} Posts 
No mystery. There was a time when (due to a bug into PrimeNet intestines, i.e. the part that checks the validity of the factors was having indigestion) you could not report "factor found" lines, but only "no factor found". The disease persisted until James/George gave it some medicine. Especially when the server was busy, because the "factor" lines are reported at the end, if the communication crashed on the way, only "no factor" lines were registered. The work which resulted in factors was still registered as not being done, and reassigned to the next "lucky" guy like you
There are another 3 or 4 threads here around about these "lucky strikes" and about fixing the problem. The "unlucky" guys who could not report the factors (and did not realize) were in the group that was not using Misfit, because Misfit pops out red windows when he can't register a factor. What you can do now, if you are curious, you can check the exponent status page, for the range around the exponents you got factors in a row, and see who was the unlucky guy who missed to report the factors. There was a time when we used to hunt for these errors, like for example, look to "how deep factored" page, and if you see a 71 in the middle of 72's, then there was a mismatched report, and there is a high probability a factor is laying there, which could not be reported at some time in the past, by some unlucky cruncher. In this case, you could do the assignment by yourself and if (most probably) you find a factor, report it and be happy. I always check if my factors went through, in spite of the fact that Misfit checks it too and pops out red windozes. Just a bit of paranoia... Last fiddled with by LaurV on 20150407 at 03:37 
20150407, 04:41  #7 
Feb 2003
2×3×29 Posts 
Hmmm...
At first I thought this was unlikely because all 10 of the exponents were assigned to me for the bit levels 7175. For 7 of the exponents, I completed 1 or 2 bit levels with no factors found, indicating that the ranges weren't partially cleared. But poking around, it looks like Bill Staffen was reporting no factor ranges like "no factor from 2^71 to 2^74", so presumably an unreported found factor wouldn't clear the lower bit levels in the range. Sorry, Bill! 
Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
Fun with the Lucky Numbers of Euler  ewmayer  Probability & Probabilistic Number Theory  0  20151018 01:37 
Extremely basic questions  schwerlin  Information & Answers  6  20150120 19:26 
Lucky ECM hit  Dubslow  Factoring  3  20141019 19:10 
primo primality certificates  (un)lucky numbers  klajok  Factoring  0  20110721 08:23 
Lucky gmpecm curve...  WraithX  GMPECM  4  20090112 16:29 