hi,
here is a sieve-file for R192
n= 50k to 100k
sieved to 6T

hi,
here is a sieve-file for R166
n= 25k to 100k
sieved to 7T

hi,
here is a sieve-file for R15
n= 200k to 400k
sieved to 29T

hi,
reserving R6 n=5M to 6M to sieve for BOINC

Lalera-
Look into sieving 5M-10M instead, or an even-larger region. It's pretty inefficient to sieve a small range compared to a large one ("small" measured as either number of expected primes in the candidate pool, or multiple of starting exponent).

If you would have sieved 5-6M to, say, 100T, that same sieve depth might take 60% more time for 5-8M, but you end up with a file that won't need all that much more effort to be ready to test 6-8M. That extra time may not be worth it to you, but you should be aware of how little it is.

[QUOTE=VBCurtis;443007]Lalera-
Look into sieving 5M-10M instead, or an even-larger region. It's pretty inefficient to sieve a small range compared to a large one ("small" measured as either number of expected primes in the candidate pool, or multiple of starting exponent).

If you would have sieved 5-6M to, say, 100T, that same sieve depth might take 60% more time for 5-8M, but you end up with a file that won't need all that much more effort to be ready to test 6-8M. That extra time may not be worth it to you, but you should be aware of how little it is.[/QUOTE]

hi,
i do not like to take a bigger range for R6 because it would take too long for me
and maybe there is a prime in that range

[QUOTE=lalera;443000]hi,
reserving R6 n=5M to 6M to sieve for BOINC[/QUOTE]

You do as you please but in my opinion, sieving only n=5M-6M is a waste of long-term resources. There is very little chance of a prime in that range. Sieving anything where nmax/nmin < 2 is inefficient as implied by Curtis. Consider sieving n=5M-10M or getting help with sieving or not sieving it at all.

[QUOTE=gd_barnes;443042]You do as you please but in my opinion, sieving only n=5M-6M is a waste of long-term resources. There is very little chance of a prime in that range. Sieving anything where nmax/nmin < 2 is inefficient as implied by Curtis. Consider sieving n=5M-10M or getting help with sieving or not sieving it at all.[/QUOTE]

hi,
for the range R6, n=5M-6M
i estimate that after sieving there are about 5000 candidates left for prp-testing
on a sbe3930k one cand. would take 24h-36h - that is about 6250 days on one core
i think that you are both right that it is more efficient to take a bigger range
of exponents - but it would take too long for me to sieve - several months
(and i think on R72)

so please do cancel my reservation for R6

[QUOTE=lalera;443043]hi,
for the range R6, n=5M-6M
i estimate that after sieving there are about 5000 candidates left for prp-testing
on a sbe3930k one cand. would take 24h-36h - that is about 6250 days on one core
i think that you are both right that it is more efficient to take a bigger range
of exponents - but it would take too long for me to sieve - several months
(and i think on R72)

so please do cancel my reservation for R6[/QUOTE]

If you would like to sieve a small base with one k remaining that is at a high search depth, may I suggest sieving S9 for n=2M-5M? Size-wise, it would be more manageable for you and testing it would bring it up to where R6 is currently.

[QUOTE=gd_barnes;443075]If you would like to sieve a small base with one k remaining that is at a high search depth, may I suggest sieving S9 for n=2M-5M? Size-wise, it would be more manageable for you and testing it would bring it up to where R6 is currently.[/QUOTE]

hi,
i want to do only riesel bases

hi,
here is a sieve-file for R171
n= 25k to 100k
sieved to 7T

[QUOTE=lalera;443086]hi,
i want to do only riesel bases[/QUOTE]

The Sierpinski bases will start to feel lonely and sad. They will begin to cry.

[QUOTE=gd_barnes;443206]The Sierpinski bases will start to feel lonely and sad. They will begin to cry.[/QUOTE]

hi,
at this time i have much to do - but maybe next year

hi,
reserving R798, n=100k to 200k to sieve for BOINC

hi,
reserving R565, n=100k to 200k to sieve for BOINC
reserving R703, n=100k to 200k to sieve for BOINC

hi,
the following range is done
R7, k=110M to 200M, n= 25k to 100k
sieved to 400G
results emailed
continuing with k=200M to 500M

hi,
here is a sieve-file for R798
n= 100k to 200k
sieved to 19T

hi,
to mr. barnes:
i sieved R798 to 19T (not 17T)

hi,
the following range is done
R7, k=200M to 300M, n= 25k to 100k
sieved to 400G
results emailed
continuing with k=300M to 500M

hi,
here is a sieve-file for R703
n= 100k to 200k
sieved to 20T

hi,
the following range is done
R106, n= 25k to 100k
sieved to 6T
results emailed

hi,
the following range is done
R7, k=300M to 400M, n= 25k to 100k
sieved to 400G
results emailed
continuing with k=400M to 500M

hi,
the following range is done
R7, k=400M to 500M, n= 25k to 100k
sieved to 400G
results emailed

Hi.
My PC is not at 100 CPU usage, I have enough free space to run some sievs.

I´d like to reserve and run some Bases where is only one k left.

R532 to n=500K
R533 to n=400K
R548 to n=400K
R549 to n=400K

[QUOTE=MisterBitcoin;446940]Hi.
My PC is not at 100 CPU usage, I have enough free space to run some sievs.

I´d like to reserve and run some Bases where is only one k left.

R532 to n=500K
R533 to n=400K
R548 to n=400K
R549 to n=400K[/QUOTE]

DAMN, I was talking about R523, not R532. My mistake. :/

R523 is @7T. 15,5K n-values left, sieving goal is 20T.

Dear other sievers,

I decided to to some pre-sieves with srsieve. I´ll focus on Sierpinski for the first months.
I´ll sieve to p=50B, the output file will be uploaded to dropbox (I´ve tested GitHub, but you cant download an selected file...)
I´ll post the links to the files to the forum. Or give me your Mail, that I can give you access to the files, without posting links.

Progress:
[CODE]
S798 with k-value 33 (N=200K to 1M) sieved to P=50B
S836 (k=2)(n=200K to1M) sieved to 10B (maybe I´ll go to 50B in a few days.)
S17 (k=244; n=2M to 5M) Running to P=50B (This can take a while...)
[/CODE]
[URL="https://www.dropbox.com/s/ahfyxic1pzhxirw/S798_n%3D1M_P%3D50G.npg?dl=0"]S798[/URL]
[URL="https://www.dropbox.com/s/6cg8y9ei3prmef1/S836_n%3D200K_1M_P10G.npg?dl=0"]S836[/URL]

@lalera Tell me which bases you will run, I can pre-sieve some files for you. :)
@gd_barnes Don´t worry, I´ll write very often here in the future. Sofar I saw "only" two persons are sieving. We should get this under control. :smile:

[QUOTE=MisterBitcoin;447019]Dear other sievers,

I decided to to some pre-sieves with srsieve. I´ll focus on Sierpinski for the first months.
I´ll sieve to p=50B, the output file will be uploaded to dropbox (I´ve tested GitHub, but you cant download an selected file...)
I´ll post the links to the files to the forum. Or give me your Mail, that I can give you access to the files, without posting links.

Progress:
[CODE]
S798 with k-value 33 (N=200K to 1M) sieved to P=50B
S836 (k=2)(n=200K to1M) sieved to 10B (maybe I´ll go to 50B in a few days.)
S17 (k=244; n=2M to 5M) Running to P=50B (This can take a while...)
[/CODE]
[URL="https://www.dropbox.com/s/ahfyxic1pzhxirw/S798_n%3D1M_P%3D50G.npg?dl=0"]S798[/URL]
[URL="https://www.dropbox.com/s/6cg8y9ei3prmef1/S836_n%3D200K_1M_P10G.npg?dl=0"]S836[/URL]

@lalera Tell me which bases you will run, I can pre-sieve some files for you. :)
@gd_barnes Don´t worry, I´ll write very often here in the future. Sofar I saw "only" two persons are sieving. We should get this under control. :smile:[/QUOTE]

hi,
i do plan to do some bases in the R7xx range in the year 2017
... just take the free ranges ...

MisterBitcoin,

See the PM that I sent you. If you are sieving any range for n>100K, please consider a sieve depth of at least P=5T (5000G) in order for us to show your reservation in the first post here and for me to post the files on the project reservation pages.

Note that for the bases you are talking about, the optimum sieve depth will be far greater than P=5T but that is a good minimum point to get the sieving of the files started.


Gary

I started the the following bases (only 1 k left)

[CODE]
R702
R727
R730
R731
R736[/CODE]
All sieved to P=50G, now running them to 5T.
I sieved to n=500K in the hope the prime will be found :smile:

I tested R709 (9k´s left), but I got an error with sr2sieve. [ERROR Line 1: Malformed line in input file]
Line 1:
[CODE]
ABCD 170*709^$a-1 [100002] // Sieved to 419078549 with srsieve[/CODE]

If you have a single k then you should not use sr2sieve, that is for many k's and it is slower. Someone correct me if I am wrong here, but I think sr1sieve is the fastest here. Even for 2,3, k's you can do separate sr1sieve runs in the same time

[QUOTE=MisterBitcoin;447069]I tested R709 (9k´s left), but I got an error with sr2sieve. [ERROR Line 1: Malformed line in input file]
Line 1:
[CODE]
ABCD 170*709^$a-1 [100002] // Sieved to 419078549 with srsieve[/CODE][/QUOTE]

That is the correct header for an sr2sieve file. I do not know why you got the error. The following command should be issued at the DOS command prompt:

sr2sieve -P 5e12 -i sieve-R709-100K-500K.txt

Just replace the file name with whatever your file is.

Is that the command that you gave sr2sieve?

[QUOTE=LaurV;447080]If you have a single k then you should not use sr2sieve, that is for many k's and it is slower. Someone correct me if I am wrong here, but I think sr1sieve is the fastest here. Even for 2,3, k's you can do separate sr1sieve runs in the same time[/QUOTE]

His example is sieving R709 with 9 k's remaining. Sr2sieve is correct to use.

[QUOTE=MisterBitcoin;446940]Hi.
My PC is not at 100 CPU usage, I have enough free space to run some sievs.

I´d like to reserve and run some Bases where is only one k left.

R532 to n=500K
R533 to n=400K
R548 to n=400K
R549 to n=400K[/QUOTE]

[QUOTE=MisterBitcoin;446949]DAMN, I was talking about R523, not R532. My mistake. :/

R523 is @7T. 15,5K n-values left, sieving goal is 20T.[/QUOTE]

[QUOTE=MisterBitcoin;447019]Dear other sievers,

I decided to to some pre-sieves with srsieve. I´ll focus on Sierpinski for the first months.
I´ll sieve to p=50B, the output file will be uploaded to dropbox (I´ve tested GitHub, but you cant download an selected file...)
I´ll post the links to the files to the forum. Or give me your Mail, that I can give you access to the files, without posting links.

Progress:
[CODE]
S798 with k-value 33 (N=200K to 1M) sieved to P=50B
S836 (k=2)(n=200K to1M) sieved to 10B (maybe I´ll go to 50B in a few days.)
S17 (k=244; n=2M to 5M) Running to P=50B (This can take a while...)
[/CODE][URL="https://www.dropbox.com/s/ahfyxic1pzhxirw/S798_n%3D1M_P%3D50G.npg?dl=0"]S798[/URL]
[URL="https://www.dropbox.com/s/6cg8y9ei3prmef1/S836_n%3D200K_1M_P10G.npg?dl=0"]S836[/URL]

@lalera Tell me which bases you will run, I can pre-sieve some files for you. :)
@gd_barnes Don´t worry, I´ll write very often here in the future. Sofar I saw "only" two persons are sieving. We should get this under control. :smile:[/QUOTE]

[QUOTE=MisterBitcoin;447069]I started the the following bases (only 1 k left)

[CODE]
R702
R727
R730
R731
R736[/CODE]All sieved to P=50G, now running them to 5T.
I sieved to n=500K in the hope the prime will be found :smile:

I tested R709 (9k´s left), but I got an error with sr2sieve. [ERROR Line 1: Malformed line in input file]
Line 1:
[CODE]
ABCD 170*709^$a-1 [100002] // Sieved to 419078549 with srsieve[/CODE][/QUOTE]

MisterBitcoin,

You are attempting to reserve too many bases at once and just kind of going all over the place, which makes it difficult to administer. With all of this I cannot tell what it is that you are doing.

It looks like you are trying to sieve 11 bases at once. For now, please reduce your reservations to 3-4 bases. After you are done, you can reserve some more. We do not need to know how far you have sieved so far. Just let us know how far you plan on sieving each base.

For people new to the project, it is important that they know how long any effort is going to take because most people well underestimate the personal and CPU effort involved. Please give us a time frame on how long you think it will take for you to sieve the 3-4 bases to at least P=5T.


Thanks,
Gary

R958
 

Sieving R958 from n=200k to 500k.

Will do a PRP test at n=400,000 to see roughly what amount of sieving is reasonable. The initial srsieve sweep to 1e10 has left <4000 candidates or so.

Sorry that I could reply earlier. I was really busy to setup my new dedicated server (Debian Jessie). I´ve got some problems setting up the gnome environment...what ever, it was an short night. ;)

After 5 hrs sleep and 8 hrs work I tryed to start sieving on 7 threads. And, surprise! Nothing works, again.
I tested everything...(I tryed to start sr1sieve via bash, (allready maked the file executable via the filemanager) but just got "commando "file-name" not found". [I hoped setting up is as easy as it is on windows...] (EDIT: Solved, I was in the wrong folder...:/)
I searched in atleast 4 forums for an sollution, well no sucess...sofar. If someone could help me or got an idea how to solve it, please pm me. (German would be easier...last linux use is 1,5 years ago, notice I´m just an user not an admin...additional I god headache. I love Mondays...^^)

EDIT: I got an: Syntax error "(" unexpected. After I maked the sr2sieve with "chmod +x" executable I tryed the following command:
[CODE]
sh sr2sieve_x86_linux -i input.abcd -pmax 5e12
[/CODE]
If I try "./" or "bash" I´ll get some other errors. Like "file not found" or "file not executable. (I´m in the right directory, now). I´m out of motivation...allways I have these problems...Never give up, live is to short to let an Error win.

@gd_barnes Well, I hoped sieving is much faster then it is. Well, I should get another dedicated server in 3 days, with 12 more threads (CPU´s). It will be used to finish R602 and sieving my reserved work. ETA´s are coming when server is running. The first 4 tasks had an ETA on my main computer, estimate an 4 day ETA.

The solution is here...finaly
 

To late to edit it...
I got it solved!
Using "chmod +x" and then start Dash (not the bash) using the following command:
[CODE]
./sr2sieve_x86_linux -i input.abcd -pmax 5e12
[/CODE]
Don´t know why it doesn´t work with the bash...

MisterBitcoin,

Per your PM, I now have you reserved for only R523, R533, R548, R549, and S17. Please complete those to at least P=5T and post the files here before reserving any more work. Thanks.


Gary

[QUOTE=MisterBitcoin;447209]To late to edit it...
I got it solved!
Using "chmod +x" and then start Dash (not the bash) using the following command:
[CODE]
./sr2sieve_x86_linux -i input.abcd -pmax 5e12
[/CODE]
Don´t know why it doesn´t work with the bash...[/QUOTE]
hi,
you could try to use the -t switch (works only with linux)
an example to use 4 cpu cores:
./sr2sieve-x86_64-linux -f factors.txt -i xxx.abcd -P 5e12 -t4

[QUOTE=lalera;447241]hi,
you could try to use the -t switch (works only with linux)
an example to use 4 cpu cores:
./sr2sieve-x86_64-linux -f factors.txt -i xxx.abcd -P 5e12 -t4[/QUOTE]

If you use -t4 is sieve four time faster or it is below that factor?

[QUOTE=pepi37;447247]If you use -t4 is sieve four time faster or it is below that factor?[/QUOTE]

hi,
the speed is below 4 times but it scales good

hi,
here is a sieve-file for R565
n= 100k to 200k
sieved to 44T

[QUOTE=pepi37;447247]If you use -t4 is sieve four time faster or it is below that factor?[/QUOTE]

It's really close; -t 2 is within 5% of two single-threaded sieves, and -t 8 is <12% slower than 8 single-threaded sieves (that is, faster than 7 single-threaded instances). The code I have is limited to 8 or fewer threads.

Hi,

R548 is sieved to p=5T. (n=200K to 400K)


Thanks to Lalera and Curtis for "-t". Running one program with all CPU´s seems to be faster than running six (in my case) different threads and bases.

[QUOTE=MisterBitcoin;447303]Hi,

R548 is sieved to p=5T. (n=200K to 400K)


Thanks to Lalera and Curtis for "-t". Running one program with all CPU´s seems to be faster than running six (in my case) different threads and bases.[/QUOTE]

Thanks. I previously gave P=5T as a good starting point if you have limited resources. Someone can use the file but will need to do much additional sieving before beginning testing. In the future if you have the resources when sieving n=200K-400K or higher it is better that the files be sieved to at least P=25T.

As a general guideline on this project, n=25K-100K can be sieved to P=5T, 100K-200K to P=15T, and 200K-400K to P=25T. You can see some of the sieve depths that lalera sieved to in the first post of this thread.

That shouldn´t be the biggest problem, my second server will be, hopefully, online in 24 hrs. (ty strato support...very slow atm).
It will take some days longer. ;)
I´ll focus on sierp, starting with some 25K-100K and 100K-200K work, when the reserved work is done.
My actual server has 6 v Cores and is from an good friend. (cheap. ;)

I gonne set up an patreon account soon, more money=more servers. :))
I have planned 4 servers with 16 cores to add in 2016 (in total 200€/month), plus an Raspberry Pi Cluster.
The cluster wont start before 06/2017, a lot of planning and money is needed. My mate is very busy, not sure if we can start the project...:/

I got an idea, again. Not sure if it´s needed, but if someone needs inputs files for srsieve (>2 k´s left) try your luck on the github I created.
You simply download the file or copy the lines into a text-file. (You don´t need an account. ;))
Here is the link: [URL]https://github.com/AureliusB/CRUS_Sieve[/URL]

File is looking like:
S/R (base)_(lowest n-value)

Without reserving it I sieved R548 more deeper to p=20T.

Next one (R523) will be done in 2 days, depth 20T.

R958 has been sieved to P=30e12 for n=200k to 500k and should be ready for immediate PRP testing. It took ~8500 seconds to PRP test n=400,000, and I sieved until the seconds per factor roughly matched that.

File is attached.

R523 is finished to p=20T.

Next one (R549) will be completed in 2 days.

I'll sieve S758 from n=200k-500k.

Hi,
I am a newcomer, I want to sieve these bases to BOINC, how to sieve?

S9 2M-3M
S30 500K-1M
S46 100K-200K
S48 100K-200K
S212 all k's to n=1M
S214 200K-1M
S218 200K-1M
S228 200K-500K
S257 600K-1M
S263 350K-1M
S264 200K-400K
S294 200K-400K
S320 200K-400K
S332 k=4 to n=1M
S334 k=4 to n=1M
S426 400K-1M
S461 250K-1M
S476 200K-400K
S480 200K-400K
S497 200K-400K
S579 200K-400K
S836 200K-1M
R6 5M-10M
R30 k=659 and k=1024 to n=1M
R45 250K-400K
R55 250K-400K
R60 k=36 to n=1M
R102 200K-1M
R157 100K-200K
R159 600K-1M
R213 200K-1M
R214 500K-1M
R218 200K-1M
R221 400K-1M
R233 400K-1M
R234 400K-1M
R236 400K-1M
R253 500K-1M
R275 400K-1M
R328 900K-1M
R398 200K-1M
R425 400K-1M
R581 200K-1M
R650 200K-1M
R812 200K-1M
R968 250K-1M
R1019 400K-1M

Well. You made my day.
(I´m new, too.)

You wanted to reserve work for a few months. :)

If you´re not trolling, take a look to this thread: [URL]http://mersenneforum.org/showthread.php?t=9742[/URL]

Or just wait a few minutes and read the following replys.

Thank you, MisterBitcoin.

I am interested that why nobody reserved S30 to n=1M? It and S117 are the only two base b<=200 with <=5 k's remaining and not sieved to n=1M.

[QUOTE=sweety439;447640]Thank you, MisterBitcoin.[/QUOTE]

Before starting any work, talk with @gd_barnes about that. There are lot lot of mistakes you can make if your not 100% sure what your doing.
Reserving 1-2 bases for sieving is okay, but not that much like your trying.
Informations can be found on this thread. too.

[QUOTE=sweety439;447642]I am interested that why nobody reserved S30 to n=1M? It and S117 are the only two base b<=200 with <=5 k's remaining and not sieved to n=1M.[/QUOTE]

Since the project is so huge, frequently holes are left in efforts and are missed for several years. I somewhat attempt to mitigate that with the recommended bases thread but I don't specifically look at "sieving holes" just testing holes. Part of the problem here is that more people are interested in sieving/testing Riesel bases than Sierp bases. Feel free to begin on S30. As a starting point, I suggest sieving to at least P=25T. It will likely need to ultimately be sieved further but 25T is a good starting point. It will take a while so you might run a small test sieve first to see how long you think it will take you. After looking into it, let me know if you would like to officially reserve it.

[QUOTE=gd_barnes;447649]Sometimes holes are left in efforts and are missed for quite a while. Part of the problem here is that more people are interested in sieving/testing Riesel bases than Sierp bases. Feel free to begin on S30. As a starting point, I suggest sieving to at least P=25T. It will likely need to ultimately be sieved further but 25T is a good starting point. It will take you awhile so you might run a small test sieve first to see how long you think it will take you.[/QUOTE]

By the way, sieving depht for S17. I suggest p=90T or just the time to eliminate 1 canidate. (60% Rule.) ?
N-Value is going up to 5M.

[QUOTE=sweety439;447632]Hi,
I am a newcomer, I want to sieve these bases to BOINC, how to sieve?
[/QUOTE]

How much work (CPU time) are you interested in doing?

srsieve is used to create the file and do initial sieving. Once you reach 1e9, use sr2sieve for most bases (a base with 1-3 k's remaining may be faster with sr1sieve on each k individually rather than sr2 on all of them at once).

The flags needed for invocation of the programs can be learned via "srsieve -h" etc, or surely there's a thread detailing exact invocation here in this forum. sr2sieve can be multi-threaded with -t 4 flag (for 4 threads); this allows modern machinery to run a sieve pretty quickly. For example, I think I spent about a month on an older 4-core Intel chip to sieve R327 earlier this fall to 80T or so, sufficient for testing the first part of the file.

In general, it's not very efficient to sieve ranges smaller than a factor of two (say, 2M-3M).

[Soapbox not necessarily shared by the regulars in this forum:]
200k-500k is more efficient than 200-400k, but a too-large range (say 200k to 5M) is a waste of work because any prime found removes that k from the testing pool, "wasting" all the sieve computations for that k above the prime. I personally choose the range of exponents such that 1/3rd or less of the k's are expected to prime when testing the file; a factor of 3-5 usually fits this concept (say, 200k to 1M or 300k to 1M). It's not a big deal, but the way I see it a 10% gain in efficiency is equivalent to a free 10% overclock, and I go to great lengths to achieve those!
[/Soapbox]

[QUOTE=MisterBitcoin;447650]By the way, sieving depht for S17. I suggest p=90T or just the time to eliminate 1 canidate. (60% Rule.) ?
N-Value is going up to 5M.[/QUOTE]

If the sieve range is around a factor of two (say, 200k to 400k or 500k to 1M), the rule of thumb is to sieve until the average time per factor is equal to the time to primality-test a candidate 60% of the way into the file (from 200k to 400k, that's 320k exponent: 60% of (400-200) + 200). If you knew the entire file would be primality tested, the rule of thumb is 70%; but fewer of the candidates at the end of the file will be tested because we expect to find some primes in the lower ranges, so we shift the rule of thumb lower (60% is widely used around here).

You don't need to run a full primality test of such a candidate to get this timing; you can run a few minutes of the test for iteration timings and multiply by the number of iterations needed.

[QUOTE=sweety439;447632]Hi,
I am a newcomer, I want to sieve these bases to BOINC, how to sieve?

S9 2M-3M
S30 500K-1M
S46 100K-200K
S48 100K-200K
S212 all k's to n=1M
S214 200K-1M
S218 200K-1M
S228 200K-500K
S257 600K-1M
S263 350K-1M
S264 200K-400K
S294 200K-400K
S320 200K-400K
S332 k=4 to n=1M
S334 k=4 to n=1M
S426 400K-1M
S461 250K-1M
S476 200K-400K
S480 200K-400K
S497 200K-400K
S579 200K-400K
S836 200K-1M
R6 5M-10M
R30 k=659 and k=1024 to n=1M
R45 250K-400K
R55 250K-400K
R60 k=36 to n=1M
R102 200K-1M
R157 100K-200K
R159 600K-1M
R213 200K-1M
R214 500K-1M
R218 200K-1M
R221 400K-1M
R233 400K-1M
R234 400K-1M
R236 400K-1M
R253 500K-1M
R275 400K-1M
R328 900K-1M
R398 200K-1M
R425 400K-1M
R581 200K-1M
R650 200K-1M
R812 200K-1M
R968 250K-1M
R1019 400K-1M[/QUOTE]
hi,
in the case you are using linux x64
an example for S476, k=28, n=200k to 400k
you could start with
./srsieve-x86_64-linux --newpgen --nmin 200000 --nmax 400000 --pmax 20e9 28*476^n+1
this will take about 30 minutes
take the output file t16_b476_k28.npg
as an input file for sr1sieve
./sr1sieve-x86_64-linux -i t16_b476_k28.npg -o b476k28-1.txt -P40e12 -t4
this will take about 6 days

[QUOTE=sweety439;447632]Hi,
I am a newcomer, I want to sieve these bases to BOINC, how to sieve?

S9 2M-3M
S30 500K-1M
S46 100K-200K
S48 100K-200K
<snip lots of bases>
[/QUOTE]

I had missed the post initially Please reserve the sieving for only 4-5 bases at a time as a starting point. The effort required for each base is likely larger than what you are initially anticipating. It is difficult for the project to manage such large reservations and you may find that your initial enthusiasm wears off after doing many of them. After you've done 4-5 of them then just reserve a few more. Thanks.

Thanks.

Now, I only want to sieve 3 bases:

S30 to n=1M
S461 to n=1M
R1019 to n=1M

R549 done + reservation
 

R549 sieved to p=20T, file attached.
Next one (R533) will be completed in 24 hours.

By the way:
Reserving S1021

R533 is completed to p=20T.

[QUOTE=lalera;447274]hi,
here is a sieve-file for R565
n= 100k to 200k
sieved to 44T[/QUOTE]

to gd_barnes:
may i remind you that R565 is already done
and a question for R742:
on the website and in the sieve-file there are 78 k´s
but you wrote 79 k´s
what is right?

[QUOTE=lalera;447787]to gd_barnes:
may i remind you that R565 is already done
and a question for R742:
on the website and in the sieve-file there are 78 k´s
but you wrote 79 k´s
what is right?[/QUOTE]

Both issues fixed. Thanks for pointing them out. There are only 78 k's remaining for R742 so the sieve file is right and the pages have been corrected. When people post sieve files I do not closely inspect them so I welcome anyone to closely inspect the k's being sieved in the file. All that I generally do is take a cursory glance at the header to make sure the base and sieve depth are what the person posted.

[QUOTE=MisterBitcoin;447585]R523 is finished to p=20T.

Next one (R549) will be completed in 2 days.[/QUOTE]

Completed aswell, information isn´t updated sofar.

[QUOTE=MisterBitcoin;447797]Completed aswell, information isn´t updated sofar.[/QUOTE]

Fixed.

hi,
reserving R742, n=25k to 100k to sieve for BOINC
reserving S742, n=25k to 100k to sieve for BOINC

Thanks for sieving S30, S461 and R1019!!!

Sorry, I am a newcomer, should I sieve for BOINC myself?

[QUOTE=sweety439;447980]Sorry, I am a newcomer, should I sieve for BOINC myself?[/QUOTE]

Yes. How you can start, read the quote. (Posted by lalera)
[QUOTE]
hi,
in the case you are using linux x64
an example for S476, k=28, n=200k to 400k
you could start with
./srsieve-x86_64-linux --newpgen --nmin 200000 --nmax 400000 --pmax 20e9 28*476^n+1
this will take about 30 minutes
take the output file t16_b476_k28.npg
as an input file for sr1sieve
./sr1sieve-x86_64-linux -i t16_b476_k28.npg -o b476k28-1.txt -P40e12 -t4
this will take about 6 days [/QUOTE]

If your using Windows use CMD:

cd (to the directory where srsieve is located)
srsieve-x86_64-windows --newpgen --nmin 200000 --nmax 500000 --pmax 40e9 "28*476^n+1"
Well, its nearly the same like above. Notice: "-t(n)" only works on Linux.
You can found some informations in the README´s aswell.

[QUOTE=MisterBitcoin;447983]Notice: "-t(n)" only works on Linux.[/QUOTE]

One of those goals of mine to address, but easier said than done as it would likely require a rewrite of major portions of the code

S1021 has sieved to p=15T.

S17 will be at 90T on 08.12.
And: Reserving S1027.

Future plans:

S17 is now running on my "big" server and the other on on the smaller once. In about 1-2 day(s) I will start with S1027, allready sieved to 20M. (still 2,4 Million lines. :O)
I´ll then focus on the bigger once, like S63, S66, S7 and S15.

[QUOTE=MisterBitcoin;448040]<snip>
In about 1-2 day(s) I will start with S1027, allready sieved to 20M. (still 2,4 Million lines. :O) I´ll then focus on the bigger once, like S63, S66, S7 and S15.[/QUOTE]

It would be better to focus on more reasonably sized bases. For example:
Instead of S1027, consider S1010 or S1017 for n=100K-200K. These very large bases with many k's remaining take an extremely long time to test.
Instead of S63 and S66, consider other bases < 300 that have < 500 k's remaining for n=25K-100K.

In particular S7 and S15 have only had a small portion of their entire k-range tested. I would ignore them completely for now. Extending the currently tested k-range is inefficient in the long run. Wait until more of their k-range has been tested so that a much larger k-range can be included in a sieve.

[QUOTE=gd_barnes;448043]It would be better to focus on more reasonably sized bases. For example:
Instead of S1027, consider S1010 or S1017 for n=100K-200K. These very large bases with many k's remaining take an extremely long time to test.
Instead of S63 and S66, consider other bases < 300 that have < 500 k's remaining for n=25K-100K.

In particular S7 and S15 have only had a small portion of their entire k-range tested. I would ignore them completely for now. Extending the currently tested k-range is inefficient in the long run. Wait until more of their k-range has been tested so that a much larger k-range can be included in a sieve.[/QUOTE]

Allright, there are a lot of unsieved bases at n=100K. I´ll pick some of them. I´ll reserve in a few days.

[QUOTE=rogue;447993]One of those goals of mine to address, but easier said than done as it would likely require a rewrite of major portions of the code[/QUOTE]

I think it should now be possible to compile pthreads on windows and as such srxsieve with -t. Msieve uses pthreads currently on windows I think.

s63
 

i'm working on s63
[URL]http://mersenneforum.org/showpost.php?p=419909&postcount=1337[/URL]

[QUOTE=grueny;448074]i'm working on s63
[URL]http://mersenneforum.org/showpost.php?p=419909&postcount=1337[/URL][/QUOTE]

Well, it isnt reserved on the page. But there is a lot of work still open, no problem. ;)

S1027 will be at 50e9 in about 24 hours, >750000 factors found sofar. If this step is done I´ll bring it on one of my servers to give informations about the ETA.

BTW: Reserving S884, will be done in 3-4 days.

[QUOTE=grueny;448074]i'm working on s63
[URL]http://mersenneforum.org/showpost.php?p=419909&postcount=1337[/URL][/QUOTE]

I have corrected that.

S1027 has been sieved to 50G.
833,933 factors found. I´ll move this base to my brand new server (#3). I predict it will take 3 to 6 weeks.

I created an sr2cache with the -c command. This file is 1,2 GB huge, it has 7,7 Million lines! What the heck is in it? If I open it with n++ I see only not translabled code.
Example:
[CODE]
¤p ÿƒC 9u
[/CODE]

That is only used to resume jobs that take a while to resume, without it, you will lose up to few hours every time you resume the job, by redoing the "startup" calculations every time. If this is ok for you (assuming you do not resume more than once or twice in the life of the job, unless you really have a shitty system or bad electricity supply), you don't need that file.

hi,
reserving R709, n=100k to 200k to sieve for BOINC
reserving R710, n=100k to 200k to sieve for BOINC

Sieving progress
 

Short sieving status update:

S17: ATM@48,9T 336 sec/factor.
Goal was 90T, might sieve deeper. Will be at goal on 7.12

S844 will be finished in 7 hrs, sec/factor is already close to prp-time needed.
Goal: 20T

S1027: ATM@0,35T. This was reached in about 2 days, but sr2sieve said it will be at 1T in about 9 days.

Reserve S218 and S257 to n=1M.

[QUOTE=sweety439;448307]Reserve S218 and S257 to n=1M.[/QUOTE]

S257 is already sieved, see Sierp conjecture reservation page: [URL]http://www.noprimeleftbehind.net/crus/Sierp-conjecture-reserves.htm[/URL]

S844 has been sieved to 20T, time/factor higher then avg PRP test.
File attached.

hi,
reserving R712, n=100k to 200k to sieve for BOINC

[QUOTE=sweety439;448442]Why cannot I use my program? I gave a list of n (250K<n<=400K) such that 2*461^n+1 has no prime factors <= (the 1000th prime).

You can check whether the list is correct.[/QUOTE]

sweety439, I'm not sure if you are a troll or not. I prefer to think that you are not a troll and that you have genuine and sincere reasons to be here. Therefor, please sweety439, stop making any further reservations and reach out to me in a private message. I'm more than willing to help you understand how the various programs work and how to calculate how much effort it actually takes to complete a reservation - weather it be a sieve or primality reservation.

This projects really could use many more contributors and many more ressources, however if someone does a lot of work and does it wrong, they end up hurting this project more than they benefit this project. So please, sweety439, reach out in a private message and let's see if you and I can make you a positive contribution to the CRUS (original definition) project. Looking forward to be hearing from you :smile:

Take care!

S758 is sieved to P=30e12. I used 6 threads, so the time per factor is a little wonky, but it should be ready to go.


Edit: Reserving S320 (k=97) for sieving n=200k-500k.

[QUOTE=wombatman;448459]S758 is sieved to P=30e12. I used 6 threads, so the time per factor is a little wonky, but it should be ready to go.


Edit: Reserving S320 (k=97) for sieving n=200k-500k.[/QUOTE]

Name of your file is S958 instead S758 :smile:

[QUOTE=pepi37;448461]Name of your file is S958 instead S758 :smile:[/QUOTE]

Ouch. Apparently I needed more caffeine this morning. The base is 758. Thanks for the correction! :smile:

[QUOTE=wombatman;448484]Ouch. Apparently I needed more caffeine this morning. The base is 758. Thanks for the correction! :smile:[/QUOTE]

No problem!
Best regards :smile:

Sweety, I am asking you for the 3rd and final time. Learn how to use srsieve, sr1sieve, and sr2sieve so that you can sieve to 15 trillion or higher. KEP has offered his assistance. He is one of our most helpful and patient searchers and is happy to help.

I am currently ignoring your files and reservations because they are useless as Curtis pointed out.

If you continue to fill up our threads with useless files that are only sieved for the first 1000, 3000, or 10000 primes I will begin to delete the posts and ask the supermods about a temporary ban.

[QUOTE=gd_barnes;448501]KEP has offered his assistance. He is one of our most helpful and patient searchers and is happy to help.[/QUOTE]

Thank you friend for those kind and warming words :smile:

Hello again.
I got some news. I decided to do some initial sieving from S66. I have splitted it into 4 parts, following below:
[CODE]
k: <5M: P=5,7M (stoped because PC crash)
k: >5M-10M (P=50M)
k: >10M-15M (P=50M)
k:>15M-21,3M (P=50M)
[/CODE]These files are about 50 MB huge. I´ll start working on it in the beginning 2017. If someone want to reserve it, let me know.
I can create an extra account on one of mine servers. ;)

And one more thing:

Reserving S117

[QUOTE=sweety439;448611]To MisterBitcoin and KEP:

Since I cannot sieve to P=15000000000000, I cannot make a data that you can use.

Can you sieve S30 to 1M and S461 to 400K? Thanks.[/QUOTE]

I'm going to send you a PM, everyone with free resources can do what you ask of us to do, within few days, maybe faster. All you need is guidance on how to create usefull data and all it requires in this case is 3 sieve programs, know as srsieve, sr1sieve and sr2sieve and a data file creator known as srfile. Srfile and srsive is found in the same zip folder. But as stated, I'm going to send you a PM and with a little bit writing back and forward I'm sure that we can get you up and running, so you can make realistic reservations and start producing productive and useful data files. Looking forward to be working with you :smile:

Take care.