20100614, 18:51  #1 
"Vincent"
Apr 2010
Over the rainbow
2×3×457 Posts 
bugged sequence in factordb
while browsing aliquot sequence, I stumbled upon these
Code:
Start Length End Ends with 794280 830 Prime P107 794196 438 Prime P106 789090 597 Prime P101 789740 608 Prime P100 790248 1278 Prime P91 792756 703 Prime P90 790884 1193 Prime P89 794880 560 Prime P85 792864 887 Prime P85 792820 835 Prime P85 791196 1853 Prime P83 789816 1030 Prime P82 765552 103 Prime P27 Last fiddled with by firejuggler on 20100614 at 18:54 
20100615, 10:39  #2 
Nov 2008
4422_{8} Posts 
This bug is known. There used to be a "Set prime" button which was given to certain (trusted) users of the DB. It was meant to be used on very large numbers that had been proved prime. However, it obviously got given to someone with malicious intents by mistake, and that person used it to set various composite numbers prime. The "Set prime" button was removed.

20100615, 14:03  #3 
Oct 2004
Austria
9B2_{16} Posts 
I thought the false primes have been fixed when the "set prime" button was removed. (AFIK Syd has (or intended to?) set all primes to "unknown" followed by a primality check.)
I have emailed Syd about the (new?) false primes yesterday in the late evening (Central European Summer Time). 
Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
Other Factordb Problems  wblipp  FactorDB  479  20211229 14:22 
A suggestion for factordb.  enzocreti  FactorDB  19  20210811 16:49 
FactorDB PRP's  smh  FactorDB  231  20150728 02:30 
Aliquot sequence worker for factordb  yoyo  FactorDB  6  20120112 20:58 
FactorDB question  Raman  Factoring  15  20100128 10:24 