![]() |
![]() |
#650 | |
"Mark"
Apr 2003
Between here and the
61·109 Posts |
![]() Quote:
|
|
![]() |
![]() |
![]() |
#651 |
"Mark"
Apr 2003
Between here and the
61·109 Posts |
![]()
In making changes to sgsieve to work like the Sophie-Germain sieve in newpgen, it appears that newpgen is missing factors for 2p+1 terms. sgsieve is outputting valid factors (per pfgw). I need to do more investigation to see if I am misunderstanding something else.
|
![]() |
![]() |
![]() |
#652 |
"Mark"
Apr 2003
Between here and the
11001111110012 Posts |
![]()
I think that I have determined what is happening.
sgsieve is sieving for k*b^n-1 and 2*k*b^n-1 I suspect that newpgen is sieving for k*b^n-1 and k*b^(n+1)-1 sgsieve is sieving for the traditional form which is p and 2p+1. This is only a problem when b != 2. I do not know if anyone is sieving for b != 2 with newpgen. I do not know if llr, pfgw, sgsieve, and newpgen are all in sync with npg file formats when b != 2. I would appreciate if someone could run some tests with llr, pfgw, and newpgen to determine if they all handle the npg file format for Sophie-Germains properly for b != 2. |
![]() |
![]() |
![]() |
#653 |
"Mark"
Apr 2003
Between here and the
61×109 Posts |
![]()
I looked again at the pfgw doc on newpgen formats. I was correct. When the base != 2, then newpgen sieves per my suspicion. I will modify sgsieve to support a switch for "true" SG sieving (what it does now) or "generalized" SG sieving (which is what newpgen does). Since nobody (as far as I know) is searching for Sophie-Germain primes for base != 2, this shouldn't be a problem.
Note this is one of the reasons I dislike newpgen file formats. ABC and ABCD formats are easier to understand. |
![]() |
![]() |
![]() |
#654 | |
Jun 2022
2 Posts |
![]() Quote:
Code invoking the build : https://github.com/twobombs/theremin...file-sieve#L12 |
|
![]() |
![]() |
![]() |
#655 | |
"Mark"
Apr 2003
Between here and the
61·109 Posts |
![]() Quote:
Does mfsieve build? It uses the same syntax. |
|
![]() |
![]() |