yes, sorry.
i wrote the post before uploading the files.
i got no response from [url]www.rieselprime.org[/url] (today too) so i uploaded now all data-files to [url]www.rieselprime.de[/url].
please refer there for now.

1443
 

At 415k so far. no new primes.

--nuggetprime

[QUOTE=kar_bon;138336]yes, sorry.
i wrote the post before uploading the files.
i got no response from [url]www.rieselprime.org[/url] (today too) so i uploaded now all data-files to [url]www.rieselprime.de[/url].
please refer there for now.[/QUOTE]

today i uploaded all changed files to [url]www.rieselprime.org[/url] without any problems so please refer to this.

i included all data for 1001<=k<=1999 and 10k<=n<=35k into the summary pages (data from henryzz and me).

data for many k's (from 20000 to 200000 and mostly n<=10k) from lavalamp will follow.

1443
 

At 500k(no new primes). pausing primesearch now a bit and try a few factorizations.

--nugget

35779 tested to 600k now... one new prime found:

346735

k=443 tested to 1040k. No primes, alas.
-Curtis

k=15431 & newbie stuff
 

Was thinking of having a go at k=15431 if it's free - can't see any signs of it having been heavily done before?

Also, I'm a bit of newbie about doing all of this by hand, and the previous howtos refer to NewPGen - is there a more recent howto that covers srsieve variants?

Thanks,

\/ato

Vato
 

Welcome to RPS!

You are right, nobody did k=15431 before. It's yours!

It's the best to start sieving using NewPGen, upto p=50 or 100bn, and then to switch to srsieve. Suppose that your NewPGen output file is called "15431.txt", then you can start srsieve on the command line as follows:
> sr1sieve -i 15431.txt -o 15431.txt -P 3E12

It will sieve to 3T but you can stop it earlier if you want.

Happy hunting!

Personally I now start sieving with srsieve, then move onto sr1sieve. This is because [url=http://www.mersenneforum.org/showthread.php?t=10529]NewPGen misses factors[/url] and is no longer being actively developed.

If you're on windows, you could put these commands in a batch file and run it to create a sieve:[code]srsieve -v -g -m 4e15 -P 1e10 -n 0 -N 101419 "15431*2^n-1"

ren "t17_b2_k15431.npg" "15431_sieve.txt"

pause[/code]That command will sieve 15431*2^n-1 for n up to 101,419 which is an Intel CPU FFT jump point. If you have an AMD CPU under the hood, you might want to change that to 102,919 for the corresponding AMD jump point. It will sieve to a depth of 10 billion, at which point I would recommend switching to sr1sieve.

The ren command simply renames the output file to something more friendly, and the pause command holds the batch file window open when it's done so that you can read any output.

If you want to know what all of the other switches in that command line do, just run srsieve -h, and likewise sr1sieve -h for sr1sieve.

Sieving and LLRing a k up to n=101,419 (or n=102,919) will take maybe 1 - 2 weeks *, depending on how fast your CPU is and how many candidates are removed while sieving.

To get those jump points I used [url=http://www.mersenneforum.org/showpost.php?p=62303&postcount=36]llrtools[/url].

* completely wild guess

New k
 

OK, I'll take over k=10544249 until 1M.

Personally, I also use srsieve, so...

-Alexander Jones

taking 20934375