s3
 

k<300e6 at n = 120e3
70 primes

k = 300e6 - 500e6 complete to n=100e3
216 primes
continuing to n = 150e3

k = 500e6 - 1e9 complete to n = 50e3
1232 primes
continuing to n = 100e3 (currently at n = 58e3)

results here: [URL]http://primes.ctrl-x-c.de/[/URL]

s3
 

k = 500e6 - 1e9 complete to n = 100e3
689 primes
continuing to n = 150e3

results here: [URL]http://primes.ctrl-x-c.de/[/URL]

Reserving 1G-3G to n 10k

Lennart

[QUOTE=Lennart;322057]Reserving 1G-3G to n 10k

Lennart[/QUOTE]

Oh man. I'm not going to enjoy this. Base 3 page updates for huge k-ranges are the bane of my existence. :smile:

[QUOTE=gd_barnes;322096]Oh man. I'm not going to enjoy this. Base 3 page updates for huge k-ranges are the bane of my existence. :smile:[/QUOTE]


Hehe This will take some time :sorry: :smile:

What would be really cool is if we could get all of Riesel base 3 searched to n=25K. That would be k=~2G-63G! I estimate that there will be ~300,000 k's remaining, which is about the same number as R63 at n=10K.

Base 3 will ultimately be far easier to prove than many bases with far smaller conjectures.

[QUOTE=gd_barnes;322119]What would be really cool is if we could get all of Riesel base 3 searched to n=25K.[/QUOTE]

Don't dream too loudly :devil:

s3
 

k<300e6 done to n = 150e3
138 primes
k-range released.
results here: [URL]http://primes.ctrl-x-c.de/[/URL]

[QUOTE=grueny;323215]k<300e6 done to n = 150e3
138 primes
k-range released.
results here: [URL]http://primes.ctrl-x-c.de/[/URL][/QUOTE]

Tremendous work Grueny! :smile:

[QUOTE=Lennart;322057]Reserving 1G-3G to n 10k

Lennart[/QUOTE]



I will cancel this now and use my sources on R3.


Lennart

s3
 

k = 300e6 - 1e9 done to n = 150e3
301 primes

results here: [URL]http://primes.ctrl-x-c.de/[/URL]

there is also a sieve to N = 500e3, sieved to P = 1e12.

base released.

[QUOTE=grueny;336006]k = 300e6 - 1e9 done to n = 150e3
301 primes

results here: [URL]http://primes.ctrl-x-c.de/[/URL]

there is also a sieve to N = 500e3, sieved to P = 1e12.

base released.[/QUOTE]

Sorry to be so long in getting to this.

Tremendous work Grueny! :smile:

For everyone's reference, all k<1G for S3 is now complete to n=150K with sieve files available for k<1G/n=150K-500K!

Reserving S3 0M-300M to n=500k (150-500k) for BOINC

Reserving S3 300M-1G to n=500k (150-500k) for BOINC

Gary:
Both sievefiles have 1080k but 2k are left somewhere?

[QUOTE=rebirther;404646]Reserving S3 300M-1G to n=500k (150-500k) for BOINC

Gary:
Both sievefiles have 1080k but 2k are left somewhere?[/QUOTE]

It is OK. The extra 2 k's are squared k's > 1G. I did a search on all squared and cubed k's for both sides of base 3 early in the project looking for k's with algebraic factors. See the Sierp base 3 remaining page.

[QUOTE=Lennart;322057]Reserving 1G-3G to n 10k

Lennart[/QUOTE]

Was this range ever completed? If not, then I presume that no k > 1G has been tested for this conjecture.

[QUOTE=rogue;405104]Was this range ever completed? If not, then I presume that no k > 1G has been tested for this conjecture.[/QUOTE]

[URL]http://mersenneforum.org/showpost.php?p=323715&postcount=301[/URL]

S3 tested to n=500k (150-500k) (0-300M)

172 primes found, 118 remain

Results emailed - Base released

S3 tested to n=500k (150-500k) (300M-1G)

469 primes found, 321 remain (in this range)

Results emailed - Base released

I'm reserving k=1G to k=5G to n=25K.

I need this to be able to compare oranges with oranges and apples with apples. I've a feeling that running the Sierpinski side is faster than running a Riesel range with same amount of k's and n's. Now when running these 2*2G ranges I can compare the final testtime for the Riesel side with the final testing time for the Sierp side (of the same base) and calculate how much faster Sierpinski side is to test :smile:

Testing using srbsieve, will start monday or tuesday.

Sorry that I have not been focused on getting srbsieve solid for restarting in the middle of a range. I have been traveling a lot since the beginning of December. That is fortunately coming close to an and soon.

S3 1G to 5G is complete to n=25000. Results are going to be e-mailed together with R3 results. Range released.

Reserving 5G-13G to n=25K, as new, using srbsieve.

S3 5G-7G is complete (288908261 MOB) (711080440 Prime) (11299 Remain)
S3 7G-9G is complete (289474837 MOB) (710513705 Prime) (11458 Remain)
S3 9G-11G is complete (289901434 MOB) (710086743 Prime) (11823 Remain)
S3 11G-13G is complete (290241009 MOB) (709746931 Prime) (12060 Remain)

Results are e-mailed.

Reserving Range 13-15G to nmax=25K using srbsieve.

[QUOTE=MisterBitcoin;453420]Reserving Range 13-15G to nmax=25K using srbsieve.[/QUOTE]

Very strange problem with newpgen and srbsieve. Somehow newpgen uses the highest k left (14999999890 for n=23) for each n-value to compute the pmax.
srbsieve uses the max k-value from the srbsieve.ini, in that case 15G

Thats why n=23-28 don´t get removed by srbsieve. I tryed that two times with new sieve file for that n-values. Sieving deeper these files didn´t happened. (He started and stopped the sieve in the same moment)

[QUOTE=MisterBitcoin;453420]Reserving Range 13-15G to nmax=25K using srbsieve.[/QUOTE]

After a bit more than 2 months this step is done.
There were 11.788 k´s remain on that range.
Results are en route via Mail.

[QUOTE=MisterBitcoin;457406]After a bit more than 2 months this step is done.
There were 11.788 k´s remain on that range.
Results are en route via Mail.[/QUOTE]

Out of curiosity, what did you use to test this range, i.e. cores, CPU, etc?

[QUOTE=rogue;460424]Out of curiosity, what did you use to test this range, i.e. cores, CPU, etc?[/QUOTE]

CPU: Intel® Xeon® E3-1230v3 (HT active)
Cores 4x3,3 GHz

Used srbsieve plus two cllr threads in the same time.

[QUOTE=MisterBitcoin;460446]CPU: Intel® Xeon® E3-1230v3 (HT active)
Cores 4x3,3 GHz

Used srbsieve plus two cllr threads in the same time.[/QUOTE]

Taking 120G to the end.

[QUOTE=rogue;460972]Taking 120G to the end.[/QUOTE]

Completed to n=25000. k without a prime are attached. I'll send Gary a link to the other files.

FYI, this was done on a 6-core machine and the work was spread across 10 instances of srbsieve.

So, lets make a multi-year reservation. :)

Reserving k-range 15G-17G to n=25K using srbsieve. (estimated time: 2,5 months)
Reserving k-range 120G> to n=100K. (estimated time: 1> years due to 32K k´s remain)

Now I have enough time to make a longer vacation.

Please dont cut off my head, but I had to post an update on S3.

k-Range 125G reached n=50K, there are 157 k´s remain in this range.
The .res files are attached.

The other 4G are atm now tested up to n=30/35K. Updates on each range if they hit 50K.

Anyway: Do you need the cllr-results for this base?

(The primes are splitted in 6 files, for each n-range 1 file. First of all i decided to generate 1 sieve file for all 32K k´s, but stopped this idea when llr reached n=26K. The file was undersieved.)

I need to add this:

[CODE]08/04/17 23:22:14 removed candidate sequence 125050976086*3^n+1 from the sieve[/CODE]

The ck was also in the pl_remain, just saying. :smile:

[QUOTE=MisterBitcoin;466070]Please dont cut off my head, but I had to post an update on S3.

k-Range 125G reached n=50K, there are 157 k´s remain in this range.
The .res files are attached.

The other 4G are atm now tested up to n=30/35K. Updates on each range if they hit 50K.

Anyway: Do you need the cllr-results for this base?

(The primes are splitted in 6 files, for each n-range 1 file. First of all i decided to generate 1 sieve file for all 32K k´s, but stopped this idea when llr reached n=26K. The file was undersieved.)

I need to add this:

[CODE]08/04/17 23:22:14 removed candidate sequence 125050976086*3^n+1 from the sieve[/CODE]The ck was also in the pl_remain, just saying. :smile:[/QUOTE]

No you don't have to post a status on S3.

This is a mess.

There is no attached file.

Nearly the whole posting is confusing. Questions:

"125G" is not a k-range. Is the k-range for k>125G or is it k=124G-125G?

You say that the other 4G is at n=30K-35K. What is the other 4G? Is that k=120G-124G? 121G-125G? Regardless why report a status for a random n-range that is completed to somewhere between n=30K and 35K? That means nothing.

You say the .res file is attached. Then you ask if we need the cllr-results file for this base. Why attach a results file and then ask if we need a results file? That is funny. To answer the question: Yes we need a results (residues) file on all bases for n>25K only.

Reference the conjectured k in the remaining file. That should not be there. I will remove it.

Please do not report statuses at random completion ranges like this on large-conjectured bases. Wait until you are done with a specific k-range to n=100K -or- report the entire k-range complete to n=50K. Otherwise it is a large waste of admin time.

Come on. I know you can do better than this.

Edit: Reference your previous post: The greater than sign goes to to the left of the number, i.e. k>120G and estimate time > 1 year. 120G> is meaningless.

If the post says "attached", there should be an file...sigh
This are the primes for k´s above 125G; the primes for k 120G up to 125G will follow if that range will hit n=50K. (atm primes: 1,975)


(I just named the range 125G, because I cant add ">" to a file name)

[QUOTE=MisterBitcoin;466134]If the post says "attached", there should be an file...sigh
This are the primes for k´s above 125G; the primes for k 120G up to 125G will follow if that range will hit n=50K. (atm primes: 1,975)


(I just named the range 125G, because I cant add ">" to a file name)[/QUOTE]

OK just a note: There are primes only files. I will need the residues files for all n>25K.

[QUOTE=gd_barnes;466253]OK just a note: There are primes only files. I will need the residues files for all n>25K.[/QUOTE]

I´ll send them when this range (>125G) will reach n=100K via mail.

Range 15-17G reached n=25K, 12092 k´s remain.
Files will be mailed after zipping is done, ~2 hrs.

Reserving Range 17G-19G to n=25K.

[QUOTE=MisterBitcoin;466593]Range 15-17G reached n=25K, 12092 k´s remain.
Files will be mailed after zipping is done, ~2 hrs.

Reserving Range 17G-19G to n=25K.[/QUOTE]

Did you received the files?

[QUOTE=MisterBitcoin;466930]Did you received the files?[/QUOTE]

Yes. The pages will be updated in a few days.

The first S3 range reached n=100K.
>125G-end has now 72k´s remain.

[CODE]125050695626*3^97171+1 is prime! (46374 decimal digits) Time : 9.713 sec.[/CODE]
Only a few minutes after I got noticed that the sister from my granddad died (on cancer) I found this prime, the last k >125,05G.

I also attached a k-remain file, I´m releasing this k-range. I might take it after my R3 Range reached 250K.

[QUOTE=MisterBitcoin;468209]
I also attached a k-remain file, I´m releasing this k-range. I might take it after my R3 Range reached 250K.[/QUOTE]

OK... k>125G is released. I still have you reserved for k=120G-125G to n=100K. Is that your intention?

[QUOTE=gd_barnes;468243]OK... k>125G is released. I still have you reserved for k=120G-125G to n=100K. Is that your intention?[/QUOTE]

Yep, that is correct.

In about a month, my remaining cores will finish some some clean-up work for the Fermat Search project. This means that I'm on to another search.

Completing S3 to n=25000 has been on my list of projects to help. I estimate that it will take around 40 weeks to complete the range of k that haven't been started. I have 22 cores at my disposal. I will start on k=100G-120G. I have already done the newpgen sieving for 100G-110G and expect to start srbsieve on parts of that range within two weeks.

Gary, I estimate that completing 100G-120G will take thru the end of the year. Please let me know if you have any issues with me taking on such a large range.

[QUOTE=rogue;468830]In about a month, my remaining cores will finish some some clean-up work for the Fermat Search project. This means that I'm on to another search.

Completing S3 to n=25000 has been on my list of projects to help. I estimate that it will take around 40 weeks to complete the range of k that haven't been started. I have 22 cores at my disposal. I will start on k=100G-120G. I have already done the newpgen sieving for 100G-110G and expect to start srbsieve on parts of that range within two weeks.

Gary, I estimate that completing 100G-120G will take thru the end of the year. Please let me know if you have any issues with me taking on such a large range.[/QUOTE]


I´d like to jump on the train, preparing Range: 19G-27G.

@MisterBitcoin and Rogue:

Are you both using this setup in your ini file for S3?

base=3
mink=
maxk=
c=1
npgfile=1,1_.log
npgfile=2,2_.log
npgfile=3,3_.log
npgfile=4,4_.log
npgfile=5,5_.log
npgfile=6,6_.log
npgfile=7,7_.log
npgfile=8,8_.log
npgfile=9,9_.log
npgfile=10,10_.log
npgfile=11,11_.log
npgfile=12,12_.log
npgfile=13,13_.log
npgfile=14,14_.log
npgfile=15,15_.log
npgfile=16,16_.log
npgfile=17,17_.log
npgfile=18,18_.log
npgfile=19,19_.log
npgfile=20,20_.log
npgfile=21,21_.log
npgfile=22,22_.log
npgfile=23,23_.log
npgfile=24,24_.log
npgfile=25,25_.log
npgfile=26,26_.log
npgfile=27,27_.log
npgfile=28,28_.log
npgfile=29,29_.log
npgfile=30,30_.log
npgfile=31,31_.log
npgfile=32,32_.log
phase=100,33000,70000
phase=335,33000,140000
phase=674,33000,315000
phase=898,33000,552500
phase=1120,33000,425000
phase=1792,33000,977500
phase=2240,33000,595000
phase=2636,33000,1080000
phase=3512,33000,2790000
phase=4364,33000,4410000
phase=5205,33000,4950000
phase=6948,33000,10620000
phase=8624,33000,18000000
phase=10288,33000,31410000
phase=13703,20000,91800000
phase=17027,15000,154800000
phase=20310,15000,190224368
phase=25000,10000,360000000

It is (or at least for me it was) the fastest way to progress on R3 and I see no reason it should not be fastest on S3. On a sidenote, Sierpinski primes are faster proven compared to Riesel primes, so if you use the same setup in your ini file on the Riesel side aswell as on the Sierpinski side, you will for the same k-range complete your S3 range faster than your R3 range. I'm not having any ressources currently to support this effort, but wow it would be cool to see this monster fall on its tale :smile:

[QUOTE=KEP;468866]@MisterBitcoin and Rogue:

Are you both using this setup in your ini file for S3?
/snip/
[/QUOTE]

I´ll use. I believe its the same that you sended me last year. :)


Your guess on SRB was wrong, maybe try it here?

[QUOTE=MisterBitcoin;468881]I´ll use. I believe its the same that you sended me last year. :)


Your guess on SRB was wrong, maybe try it here?[/QUOTE]

It is and I had actually forgotten all about the fact that I had sent this ini-setup to you :smile:

Well I have no other guesses, so whatever Aurel is doing is not something I have any available guesses for :smile: ... If you know the correct answer, please enlighten me :wink:

[QUOTE=rogue;468830]In about a month, my remaining cores will finish some some clean-up work for the Fermat Search project. This means that I'm on to another search.

Completing S3 to n=25000 has been on my list of projects to help. I estimate that it will take around 40 weeks to complete the range of k that haven't been started. I have 22 cores at my disposal. I will start on k=100G-120G. I have already done the newpgen sieving for 100G-110G and expect to start srbsieve on parts of that range within two weeks.

Gary, I estimate that completing 100G-120G will take thru the end of the year. Please let me know if you have any issues with me taking on such a large range.[/QUOTE]

I will reserve it for you but I do not understand the need to reserve such huge pieces of work. It's easy to lose interest and want to work on other projects "temporarily" in the middle of the reservation or otherwise have resources go down when doing such long-range reservations. I've seen it happen many times. Why not reserve k=115G-120G, finish that, then reserve k=110G-115G finish that, reserve...etc.?

Regardless, please send the primes and k's remaining in k=1G pieces. Thanks.

[QUOTE=MisterBitcoin;468836]I´d like to jump on the train, preparing Range: 19G-27G.[/QUOTE]

You already have an extremely huge amount of work reserved including S3 for k=17G-19G to n=25K and k=120G-125G to n=100K among many other reservations.

Can you complete this entire range to n=25K in a reasonable amount of time?

I'll state it again: I do not understand the need to reserve such large amounts of work. Why not finish 17G-19G first and then reserve 19G-21G, 21G-23G, etc.? The ranges are not going anywhere.

[QUOTE=gd_barnes;469110]I will reserve it for you but I do not understand the need to reserve such huge pieces of work. It's easy to lose interest and want to work on other projects "temporarily" in the middle of the reservation or otherwise have resources go down when doing such long-range reservations. I've seen it happen many times. Why not reserve k=115G-120G, finish that, then reserve k=110G-115G finish that, reserve...etc.?

Regardless, please send the primes and k's remaining in k=1G pieces. Thanks.[/QUOTE]

I have 22 cores at my disposal, each core will be working on a range of either 1G or .5G. That is why I have reserved such a large range.

Trust me, if I didn't get bored with working on a double-check of !7 for 9 months, then working on 100G-120G for 3 months will not bore me. If I'm bored after that, then I will go onto something else when that range is done.

[QUOTE=gd_barnes;469112]You already have an extremely huge amount of work reserved including S3 for k=17G-19G to n=25K and k=120G-125G to n=100K among many other reservations.

Can you complete this entire range to n=25K in a reasonable amount of time?

I'll state it again: I do not understand the need to reserve such large amounts of work. Why not finish 17G-19G first and then reserve 19G-21G, 21G-23G, etc.? The ranges are not going anywhere.[/QUOTE]

17-19G is at 17K.
19G-27G will take about 3 months.
I was just saying that I´m prepairing this work (which is done), I´ll reserve it when I release the S7 Range. (n=22,1K)

OK guys. Kudos to you for sticking with it.

A couple of cores should finish their 1G range in the next 10 days. I need to get more work lined up for them. Taking 80G-100G. The downside is that I can only run newpgen on one computer. On another computer with Windows it crashes. The other computers are Macs. I have the newpgen source so I will see if I can get it to compile and run correctly with gcc. If so, then I should be able to run on my Macs. The downside is that I haven't been super motivated to work on that.

[QUOTE=rogue;469883]A couple of cores should finish their 1G range in the next 10 days. I need to get more work lined up for them. Taking 80G-100G. The downside is that I can only run newpgen on one computer. On another computer with Windows it crashes. The other computers are Macs. I have the newpgen source so I will see if I can get it to compile and run correctly with gcc. If so, then I should be able to run on my Macs. The downside is that I haven't been super motivated to work on that.[/QUOTE]

A crash on Windows? Mhm, maybe these "date exc protection" like I got on my servers?
It will instandly crash if you hit the start button...

[QUOTE=MisterBitcoin;469888]A crash on Windows? Mhm, maybe these "date exc protection" like I got on my servers?
It will instandly crash if you hit the start button...[/QUOTE]

That is what I see. I have no idea why. I cannot install Visual Studio on it to debug it.

[QUOTE=rogue;469883]A couple of cores should finish their 1G range in the next 10 days. I need to get more work lined up for them. Taking 80G-100G. The downside is that I can only run newpgen on one computer. On another computer with Windows it crashes. The other computers are Macs. I have the newpgen source so I will see if I can get it to compile and run correctly with gcc. If so, then I should be able to run on my Macs. The downside is that I haven't been super motivated to work on that.[/QUOTE]

Modifying and compiling stuff on the fly like this makes me very nervous, especially with new search efforts on huge bases. Remember what happened with modifications on the fly with sr(x)sieve for algebraic factorizations that were not properly tested? Here it appears that you're talking about re-compiling and possibly making changes followed by immediately beginning searching for primes but without extensive parallel testing.

This is a huge base. Please slow down and respect quality over quantity. No one has come close to approaching this speed of work on R3 or S3. It will still be there many months and years from now. Please use what works and has been extensively tested for actual results. In other words use your Windows setup that works. Take it slow with running it on the Macs. Before accepting the results from the Macs with the new compile, run the same range on the known working Windows machine and make sure that they match...then do it again...and again...and again...with different ranges and parameters.

I feel that it is best not to accept your 80G-100G reservation until I am convinced that this has been done. If your "couple of cores" sit idle for a while then consider working on another base or project with it...maybe do some sieving for R3 for n=25K-100K.

If I write something that can replace this functionality of newpgen, it will be tested. For now you can be content that I will only be using newpgen.

I've sent Gary links for 100G-104G.

I've sent links to Gary for everything between 96G and 112G. I will submit links for 112G to 120G by the weekend.

I'll reserve 60G to 80G. I've already sieved the range with newpgen and have some cores working on parts of it.

[QUOTE=rogue;472200]I've sent links to Gary for everything between 96G and 112G. I will submit links for 112G to 120G by the weekend.

I'll reserve 60G to 80G. I've already sieved the range with newpgen and have some cores working on parts of it.[/QUOTE]

:bow: Nice work Rogue! :banana:

17G-23G reached n=25K.

1 out of 3 file is mailed, the other 2 will be mailed very soon.
Notice: They are still 2G-ranges, future work will be in 1G ranges. :smile:

I´ve just woken up, on 3 AM, to report that 23G-27G is done.
Zipping will take some time, after then it will be mailed.

For this year I´m done with new S3 ranges. Next year I will be starting the rest of the unstarted work. :razz:

Taking 40G to 60G

My work is about half done for S3. I should finish the range to n=25K around the end of February.

[QUOTE=rogue;474454]My work is about half done for S3. I should finish the range to n=25K around the end of February.[/QUOTE]

An amazing amount of work. I'm happy to get them 4G to 8G at a time like you've been doing. It allows me to spread out the update effort. :smile:

Reserving k=27G-28G to n=25K. Let´s see how long 1G range will take.

[QUOTE=MisterBitcoin;476532]Reserving k=27G-28G to n=25K. Let´s see how long 1G range will take.[/QUOTE]

On a single i5 core it should take about 1 month. How fast on i7 depends upon the generation of that CPU.

[QUOTE=rogue;476559]On a single i5 core it should take about 1 month. How fast on i7 depends upon the generation of that CPU.[/QUOTE]

Intel® Xeon® E3-1230v3

It will be around 1 month, since 2G needs about 2 months. (a little bit less than 2 months.)
Something between 3-4 weeks.

Taking the last range of 28G to 40G. Most of my cores will finish their current range within the next 10 days, so I should be able to finish what I started. Then I can move them on to Fermat Search.

So, my last S3 range (27G-28G) is done, results en route per mail.
6101 k´s remain in that range.

I have submitted the last 4G to Gary. Due to slightly higher remaining n than expected, I will probably need to run the remaining k for some of those ranges. Nevertheless the heavy lifting has been done.

I have started a check on the remaining k to verify that I didn't miss any primes. I am past n=1000 and have only one prime to report: 34359738368*3^4+1.

Even if fbncsieve removed this prime (the current version does not), then srbsieve should have found it as the first phase of srbsieve will start sieving at n=1.

Very odd.

[QUOTE=rogue;480765]I have submitted the last 4G to Gary. Due to slightly higher remaining n than expected, I will probably need to run the remaining k for some of those ranges. Nevertheless the heavy lifting has been done.[/QUOTE]

By the way, that last 4G range had almost exactly the number of k's remaining that was expected.

[QUOTE=rogue;480978]I have started a check on the remaining k to verify that I didn't miss any primes. I am past n=1000 and have only one prime to report: 34359738368*3^4+1.

Even if fbncsieve removed this prime (the current version does not), then srbsieve should have found it as the first phase of srbsieve will start sieving at n=1.

Very odd.[/QUOTE]

No worries. That k was not remaining. You must have found a higher prime for it. I see that up to n=100 it also has primes for n=6, 32, 44, 48, and 87. It would have been really difficult for it to miss all of those primes. :-)

[QUOTE=gd_barnes;480996]No worries. That k was not remaining. You must have found a higher prime for it. I see that up to n=100 it also has primes for n=6, 32, 44, 48, and 87. It would have been really difficult for it to miss all of those primes. :-)[/QUOTE]

Hmm. I wonder how it got into the file that I was testing with.

I double-checked to n=5000 and stopped. No missing primes.

[QUOTE=rogue;481498]I double-checked to n=5000 and stopped. No missing primes.[/QUOTE]

That's good to know. Can I ask: What k-range did you double-check to n=5000?

[QUOTE=gd_barnes;481523]That's good to know. Can I ask: What k-range did you double-check to n=5000?[/QUOTE]

All remaining k.

The range 123,75G-125G reached n=50K. Results will be mailed shortly.

I´ve about 4k k´s remain in that range.

It nearly took a year to reach n=50K. I´ve asked reb if he still needs small tasks, so maybe he can take it to n=100K. If not, I´ll finish it by myself. :smile:



I do not plan to do any work between n=25K-100K in the near future.

Reserving k>=125G up to n=150K

Reserving S3 to n=100k (50-100k) (123.75G-125G) for BOINC

[QUOTE=MisterBitcoin;503849]Reserving k>=125G up to n=150K[/QUOTE]


Reached n=150K, 23 primes found. 49 now remaining.
Reserving from n=150K up to 200K. Results attached.

[QUOTE=MisterBitcoin;505090]Reached n=150K, 23 primes found. 49 now remaining.
Reserving from n=150K up to 200K. Results attached.[/QUOTE]


Reached n=200K, 9 primes found. (40 remaining)
Extending reservation up to n=250K. Results attached.

[QUOTE=MisterBitcoin;506653]Reached n=200K, 9 primes found. (40 remaining)
Extending reservation up to n=250K. Results attached.[/QUOTE]


Reached n=250K, 6 primes found. (34 remaining)
Extending reservation up to n=500K. Results attached.

S3 tested to n=100k (50-100k) (123.75-125G)

1968 primes found, 2327 remain in this range

Results emailed - Base released

I did a doublecheck using PFGW console version 3.8.3.7 Windows 64-bit for this range:

kMin=70000237018
kMax=70015808992

100 k´s in total, for n=1 to n=25000, no PRPs was found and therefor no k´s appears to have missed primes.

My range reached n=500K.

Found 6 primes between 250K-300K.
Found 3 primes between 300K-350K.
Found 6 primes between 350K-500K.


That makes 19 k´s remaining in this range. Might test this one deeper, a sieve is running.

I dont want to reserve this one now.

[QUOTE=MisterBitcoin;524483]My range reached n=500K.

Found 6 primes between 250K-300K.
Found 3 primes between 300K-350K.
Found 6 primes between 350K-500K.


That makes 19 k´s remaining in this range. Might test this one deeper, a sieve is running.

I dont want to reserve this one now.[/QUOTE]

Please post primes and results. Thanks.

[QUOTE=gd_barnes;524555]Please post primes and results. Thanks.[/QUOTE]


Dont know why it didnt got attached...

Reserving k range 123G up to 123,75G up to n=100K.

Reserving k-range >125G up to n=750K. Sieve file should be deep enough to even reach n=1M before June. Lets see.

I suspect 4 primes in that range. Fingers crossed!




Ahh, forget to add infos to the other reservation:

right now at n=73,1K with little over 3K primes found. Still gonna take some time...

[QUOTE=MisterBitcoin;537433]Reserving k-range >125G up to n=750K. Sieve file should be deep enough to even reach n=1M before June. Lets see.

I suspect 4 primes in that range. Fingers crossed!




Ahh, forget to add infos to the other reservation:

right now at n=73,1K with little over 3K primes found. Still gonna take some time...[/QUOTE]


How about you complete the other k=123G-123.75G reservation before starting on k>125G? Thanks.

The S3 range from k=123G up to 123,75G reached n=100K. Found 3502 primes, results can be found [URL="https://mega.nz/file/bXpxwDrY#LoRUzUlYwVHT5SbOoKluU3vS9XO1lwKpGJDkKlue7Ps"]here[/URL]
Releasing this range

[QUOTE=MisterBitcoin;537433]Reserving k-range >125G up to n=750K. [/QUOTE]
Said range is now at n=940K with uhm 7 primes found so far. It should reach 1M in about 2 months. Primes are:
[CODE]
125011623424*3^536110+1 is prime!
125046722746*3^542844+1 is prime!
125023497122*3^550124+1 is prime!
125033255936*3^690611+1 is prime!
125026898182*3^751689+1 is prime!
125000536756*3^774704+1 is prime!
125035448126*3^933576+1 is prime! (445441 decimal digits)
[/CODE]
Last one sadly little too small to get into TOP5000.

Res will be sent once i reach 1M^^

[QUOTE=MisterBitcoin;556178]

Res will be sent once i reach 1M^^[/QUOTE]


I reached 1M a bit quicker than i planned, but i only found one more prime.


125030472038*3^945719+1 is prime! (451234 decimal digits)



Again this one is too small to reach Top5K.
There are 11 k´s remaining in that range, i will do a sieve file for up to 2M but i think thats all i can do.

[QUOTE=MisterBitcoin;560582]I reached 1M a bit quicker than I planned, but I only found one more prime.

125030472038*3^945719+1 is prime! (451234 decimal digits)

Again this one is too small to reach Top5K.
There are 11 k´s remaining in that range, I will do a sieve file for up to 2M but I think that's all I can do.[/QUOTE]
Will you be testing n>1M? If not I will release the base.