Possible JJsieve bug?

[Joe O]

Citrix,
It looks like another dat file problem. You had:
1
100
1000000
k=43046721
etc
You were only looking for n up to a million (10^6 or 1E6)? Did you want 10 million (10^7 or 1E7)? It looks like the srfactors file you sent me has factors up to about 2E7. The actual limit of JJsieve is 4,294,967,294 (4E9) but I don't recommend going that high. 2^27 or 134,217,728 (1E8) should be adequate for most projects.

[Citrix]

I was initially sieving to 2M, then I removed the candidates and sieved upto 1M only. If the k proves productive upto 1M, I will continue it onto 2M.

Thanks

[Joe O]

Originally Posted by Citrix

I was initially sieving to 2M, then I removed the candidates and sieved upto 1M only. If the k proves productive upto 1M, I will continue it onto 2M.

Thanks

Well you can't compare apples and oranges. If you tell one program to sieve to 2M and another to sieve to 1M, of course the results will be different. The attached file has been tested for your p range and k. Where would you like the 639KB of factors sent? Most of them do not show up in your srfactors.txt file. Maybe that's because I went to 100M.

[Citrix]

Till where did you sieve in p range? I think I have most of the factors till n=2M. As for factors larger than 2M, I do not need them.

Thanks

[Joe O]

Originally Posted by Citrix

Till where did you sieve in p range? I think I have most of the factors till n=2M. As for factors larger than 2M, I do not need them.

Thanks

pmax=4000000000
pmin=3700000000

Attached are all the factors found for this range