[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: