Bases 33-100 reservations/statuses/primes

[gd_barnes]

S67 is complete to n=100K; 8 primes were found for n=50K-100K shown below; 45 k's remain; base released.

Primes:

17118*67^51873+1
10864*67^58118+1
13152*67^68120+1
14026*67^75164+1
6702*67^78120+1
8368*67^80797+1
13038*67^92949+1
4062*67^94111+1

This now completes the following to n=100K:
All bases <=100 with <= 60 k's remaining at n=50K.
All bases <=256 with <= 25 k's remaining at n=25K.

[gd_barnes]

Kenneth reported that S58 is at n>=107K; 2 primes were found since the last status shown below; continuing on.

Primes:
41781*58^89452+1
35976*58^112155+1

[paleseptember]

Taking R55 (nine k-values remaining at n=100K) out for a run.

[firejuggler]

R51 is at 20k, 987 k's tested, 240 removed, will continue to 25k



(one of the last line has 2 k value in it, just so you know)

[gd_barnes]

Originally Posted by firejuggler

R51 is at 20k, 987 k's tested, 240 removed, will continue to 25k



(one of the last line has 2 k value in it, just so you know)

I changed "bases" to "k's". You are only testing one base, Riesel 51.

Even though the file contains 250 primes, I confirmed that 240 unique k's were found with primes. I mention this because it would be faster if you use the stop-on-prime option of either LLR or PFGW.


Gary

[rogue]

R79 update.

1651 primes (so far). They have been attached.

Unfortunately I had installed an OS update that caused pfgw to sometimes not write to pfgw.log. I was able to capture many that weren't written (fortunately still on the terminal output), but don't know if I missed any. Lucky me gets to resieve because I was using number_primes in pfgw and everytime I had to shut down pfgw, I had to edit the ABC file and remove rows with found PRPs. I had completed up to n=16,500. This will cost me a few weeks.

On the bright side, it has prompted me to work on a mod for pfgw. With this mod, pfgw will be able to read pfgw.log and pfgw-prime.log upon startup to find values that can be skipped in the ABC file. This means that stopping and restarting pfgw will not require any editing of the ABC file when using the number_primes option.

[gd_barnes]

Originally Posted by rogue

R79 update.

1651 primes (so far). They have been attached.

Unfortunately I had installed an OS update that caused pfgw to sometimes not write to pfgw.log. I was able to capture many that weren't written (fortunately still on the terminal output), but don't know if I missed any.

I cannot accept something if you don't know if it missed some primes. The nature of this project requires virtually 100% accuracy. My suggestion is to redo the range.

The mod that you suggest is an excellent one that I'm sure we'd all like to see.

[rogue]

Originally Posted by gd_barnes

I cannot accept something if you don't know if it missed some primes. The nature of this project requires virtually 100% accuracy. My suggestion is to redo the range.

That's exactly what I intend to do.

BTW, I didn't expect you to mark the range complete to n=16500, but you can at least capture the primes.

[gd_barnes]

Originally Posted by rogue

That's exactly what I intend to do.

BTW, I didn't expect you to mark the range complete to n=16500, but you can at least capture the primes.

OK thanks. I'll do that.

It's odd that an OS update would cause a program to not write to a specific file like that.

[paleseptember]

It may not be related, but I've noticed some odd behaviour with pfgw as well.
For R55, I'm running

pfgw.exe -f0 -l sr55p1.pfgw

and it's grinding through normally. However, it's not writing to pfgw.out periodically, only when I hit ctrl+C.

Windows XP, PFGW 3.3.6

Everything so far is composite according to the screen output.

[rogue]

Originally Posted by gd_barnes

OK thanks. I'll do that.

It's odd that an OS update would cause a program to not write to a specific file like that.

There were issues with the 10.7.2 update for OS X Lion. They only affected some people. Apparently I was one of them. It manifested itself in various ways, such as hanging the Finder. I found a fix on-line, but it didn't fix all of the problems I had. I reverted back to 10.6 (a clean install). I'll re-install Lion in January.