![]() |
|
|
#12 | |
|
Sep 2003
2·5·7·37 Posts |
Quote:
The person was not suspected of actually cheating because they had a bunch of other machines which did find the expected number of factors. It was concluded that it must have been bad hardware. Anyone remember what I'm referring to? I could probably google it if sufficiently motivated... |
|
|
|
|
|
|
#13 | |
|
If I May
"Chris Halsall"
Sep 2002
Barbados
2·112·47 Posts |
Quote:
Might you be able to provide additional specific details? |
|
|
|
|
|
|
#14 |
|
Dec 2002
881 Posts |
First of all, I am not looking for cheaters, I only care about error rates. We know that 2-4% of all LL residues are wrong due to overheated CPU's, overtweaked memory speeds etc. etc.
I redid a lot of P-1 work in the range 12M to 13M some time ago and found quite a lot more factors that should have been found through trial factoring or previous P-1 runs than I expected beforehand. Even though of course most factors were found then because of higher B1 and B2 bounds. I personally attach a little more value to a factor found that was earlier missed than a new factor. The queries that I would like to see running against the database would sniff out user/machine combinations with the highest ratio of missed factors during trial factoring and/or P-1 runs that should have been found with the settings used, and were later found by other machines through whatever method. If we have a top ten or twenty list of suspect machines and factoring work they have done that has not been verified, I would like to redo the P-1 work or trial factoring from that list. But if others what to take portions of that list, that fine, provided the machines used are proven reliable. |
|
|
|
|
|
#15 | |
|
1976 Toyota Corona years forever!
"Wayne"
Nov 2006
Saskatchewan, Canada
3×52×71 Posts |
Quote:
I have more data that suggest I found quite a few missed factors. I was testing in the 72-77M Range. This was for work done by sannerud: http://www.mersenne.org/report_expon...exp_hi=&full=1 Last fiddled with by petrw1 on 2016-11-01 at 22:24 Reason: Last line |
|
|
|
|
|
|
#16 | |
|
If I May
"Chris Halsall"
Sep 2002
Barbados
2×112×47 Posts |
Quote:
|
|
|
|
|
|
|
#17 |
|
1976 Toyota Corona years forever!
"Wayne"
Nov 2006
Saskatchewan, Canada
3×52×71 Posts |
Sorry mis-worded. Not suggesting I am hiding anything.
I just have an old spreadsheet from that time period where I was using my GPU to re-factor a bunch of exponents from sannerud.com. I found 23 factors....not sure out of how many but I spend almost 3 days with my GTX-750 running 500 Ghz/day I thought it was Madpoo again that provided the lists of exponents to re-test but I have yet to find the forum posts. Last fiddled with by petrw1 on 2016-11-01 at 22:33 |
|
|
|
|
|
#18 | |
|
"Forget I exist"
Jul 2009
Dartmouth NS
210D16 Posts |
Quote:
meanwhile just that site without just you brings up this list of threads: Redoing factoring work done by unreliable machines OFFICIAL "SERVER PROBLEMS" THREAD Newer milestone thread fondled a factor? Turn yourself in to become inanely famous! User TJAOI More missed factors Unexpected Factor strange factors distribution?? Last fiddled with by science_man_88 on 2016-11-01 at 23:05 |
|
|
|
|
|
|
#19 |
|
"Curtis"
Feb 2005
Riverside, CA
2·2,927 Posts |
No, this addresses the question in this thread- if someone ran a bunch of TF on a known-bad computer, where known missed factors exist (as discovered by TJAOI), then an error rate can be estimated and optimal-recheck-effort can be imputed. I said nothing about cheating, and your fixation on that is your own slant, not mine.
|
|
|
|
|
|
#20 | |
|
Dec 2002
881 Posts |
Quote:
Once again, I only care about identifying unreliable machines that have added multiple results to the database that were not verified one way or the other. Last fiddled with by tha on 2016-11-01 at 23:32 |
|
|
|
|
|
|
#21 | |
|
Nov 2008
509 Posts |
Quote:
Seems like chalsall is having a bad week this week, see the completely unnecessary and over the top response here... ..the evidence was provided and no apology was forthcoming
|
|
|
|
|
|
|
#22 | |
|
Sep 2003
2×5×7×37 Posts |
Quote:
PS, In the list of exponents I posted above, some TF:63-64 factors in the 500M range were missed by some guy named "For Research", for instance 532139263 and 532268537 and others. Looks like we found a cheater! ![]() ![]() ![]()
|
|
|
|
|
![]() |
| Thread Tools | |
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Coordination thread for redoing P-1 factoring | ixfd64 | Lone Mersenne Hunters | 84 | 2021-12-21 23:36 |
| Require P-1 and other factoring work to be done on reliable machines | tha | PrimeNet | 66 | 2015-05-20 15:45 |
| Work transfer between 32 and 64 bit machines | tichy | Software | 11 | 2011-01-07 22:57 |
| Redoing work? | MooMoo2 | Riesel Prime Search | 2 | 2010-09-15 17:33 |
| 5.98M to 6.0M: redoing factoring to 62 bits | GP2 | Lone Mersenne Hunters | 0 | 2003-11-19 01:30 |