20181026, 04:11  #1 
Oct 2018
1_{8} Posts 
Does NewPGen have a bug?
I was sieving k=173 from n=1M to n=2M, and I found this message by NewPGen:
p=2215115304221 divides n=1798220. However 2,215,115,304,221 is composite (that number is 8627 * 256765423), so that message should not have popped up. Why didn't NewPGen remove n=1798220 when it was at p=8627 or at p=256765423? In case anyone's wondering, I was using NewPGen version 2.82 on a Pentium 4 computer. The problem also appears on another Pentium 4 machine, so I'm pretty sure it's not a hardware problem. Thank Cristiano 
20181026, 04:31  #2  
Jun 2003
2×3^{2}×7×37 Posts 
Quote:


20181026, 06:28  #3 
Sep 2002
Database er0rr
6375_{8} Posts 
Isn't k=173 already sieved very deeply by PrimeGrid?

20181026, 12:01  #4 
Einyen
Dec 2003
Denmark
3·7·137 Posts 
Neither 8627 nor 256765423 is a factor of 173*2^17982201, so it must have been p=2215115304211 as axn pointed out.

20181026, 12:08  #5 
"Carlos Pinho"
Oct 2011
Milton Keynes, UK
4624_{10} Posts 

20181026, 13:26  #6 
"Mark"
Apr 2003
Between here and the
5,843 Posts 
Why are you using newpgen for this form? Use srsieve/sr1sieve. They are much, much faster than newpgen for this form.

20200311, 12:13  #7 
Random Account
Aug 2009
U.S.A.
2^{3}×3×5×11 Posts 
Does NewPGen have a bug? Possibly. I noticed for any given range of n's, NewPGen will remove more n's, and at lower values of p, than the srXsieve family.
Either NewPGen is removing n's it should not or srXsieve family is not removing n's it should. A combination of both is also possible. I have no way to determine which case it may be. 
20200311, 16:54  #8  
"Curtis"
Feb 2005
Riverside, CA
108C_{16} Posts 
Quote:


20200315, 13:46  #9  
Random Account
Aug 2009
U.S.A.
2450_{8} Posts 
Quote:
I can provide example files. It may take a couple of days. I am running a widerange sieve on my HP to 1.5trillion. I can replicate this with NewPGen on my laptop. My i7 is running a doubleinstance of LLR so I cannot use it. Edit: I will allow the srXsieve on the HP to finish, and then run the NewPGen test after it. sr1sieve estimates completion on March 17 at around 19:00 UTC. Last fiddled with by storm5510 on 20200315 at 14:04 Reason: Append 

20200315, 17:18  #10  
Dec 2011
After milion nines:)
517_{16} Posts 
Quote:
Why is needed to wait so many days: take sequence you know produce "problems" runn it on NewPgen few minutes, and run it under srxsieve few minutes ( to reach same depth) So all work can be done in 10 minutes. Or tell us what sequence have problem and I would like to comparison for you, For that you can only need seconds to write reply on my post 

20200317, 01:51  #11 
Random Account
Aug 2009
U.S.A.
2450_{8} Posts 
I scaled this test down dramatically. The parameters are:
Series: 7*2^n1 n: 350,000 N: 650,000 p: (default) P: 50e9 It took srsieve/sr1sieve about 30 minutes to run this. NewPGen, over four hours. NewPGen does not start storing factors until it p passes 2^32. So, I set the ceiling for srsieve to this value. The staring p for sr1sieve was the same. During the sieve NewPGen pulled out 5,603 factors, sr1sieve pulled out 840. Yet, the compete files for LLR were exactly the same. 7,092 elements each. Some may be familiar with fc, short for file compare. I compared both LLR files. The only difference was in the header line at the very top. All the files are stored in the attached zip file. There is also an image attachment with NewPGen set into a PowerShell window where I ran srsieve and sr1sieve. Q: How is it possible for NewPGen to flag so many more factors than sr1sieve and both results files be virtually identical? 
Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
NewPgen  Cybertronic  Factoring  0  20140322 10:07 
Does NewPGen have a bug?  MooooMoo  Riesel Prime Search  16  20081211 11:46 
NewPGen k value problem  roger  Information & Answers  0  20070404 22:38 
NewPGen reliability  Cruelty  Riesel Prime Search  3  20060215 05:15 
Problem with Newpgen  Zenmastur  Software  4  20030802 19:43 