Reserving R247 to n=10K.

R247 is complete to n=10K; 1719 primes were found for n=2.5K-10K; 2566 k's remain; base released.

R133 is complete to n=550k, 0 primes found.
Base released.

S178 tested to n=300k (100-300k)

3 primes found, 11 remain

Results emailed - Base released

S123 tested to n=400k (250-400k)

1 prime found, 6 remain

Results emailed - Base released

Reserving S133 to n=300k (250-300k) for BOINC

Reserving R172 to n=300k (250-300k) for BOINC

Reserving S165 to n=300k (250-300k) for BOINC

Reserving S191 to n=300k (250-300k) for BOINC

R107 tested to n=500k (200-500k)

4 primes found, 13 remain

Results emailed - Base released

Progress update
 

K4 S155 at 1.3M

S133 tested to n=300k (250-300k)

nothing found, 3 remain

Results emailed - Base released

S165 tested to n=300k (250-300k)

nothing found, 3 remain

Results emailed - Base released

Reserving R187 to n=300k (250-300k) for BOINC

S191 tested to n=300k (250-300k)

nothing found, 3 remain

Results emailed - Base released

R109 tested to n=1M (600k-1M)

nothing found, 1 remain

Results emailed - Base released

R172 tested to n=300k (250-300k)

nothing found, 3 remain

Results emailed - Base released

R187 tested to n=300k (250-300k)

nothing found, 4 remain

Results emailed - Base released

Reserving S204 to n=1M (600k-1M) for BOINC

Reserving S111 to n=400k (250-400k) for BOINC

R173 tested to n=1M (600k-1M)

nothing found, 1 remain

Results emailed - Base released

Reserving S138 to n=500k (400-500k) for BOINC

Reserving S135 to n=400k (250-400k) for BOINC

Progress update
 

K4 S155 at 1.32M

S111 tested to n=400k (250-400k)

1 prime found, 16 remain

Results emailed - Base released

S135 tested to n=400k (250-400k)

nothing found, 4 remain

Results emailed - Base released

Reserving S243 to n=400k (170.2-400k) for BOINC
Reserving S248 to n=500k (400-500k) for BOINC
Reserving S249 to n=500k (400-500k) for BOINC

S204 tested to n=1M (600k-1M)

nothing found, 1 remain

Results emailed - Base released

S138 tested to n=500k (400-500k)

1 prime found, 9 remain

Results emailed - Base released

Progress update
 

K4 S155 at 1.35M

S248 tested to n=500k (400-500k)

nothing found, 4 remain

Results emailed - Base released

S249 tested to n=500k (400-500k)

nothing found, 3 remain

Results emailed - Base released

Reserving S174 from 850K to 900K

Progress update
 

K4 S155 at 1.375M

Reserving S163 to n=500k (400-500k) for BOINC

Reserving S177 to n=500k (400-500k) for BOINC

S243 tested to n=400k (170.2-400k)

28 primes found, 97 remain

Results emailed - Base released

S177 tested to n=500k (400-500k)

nothing found, 10 remain

Results emailed - Base released

K4 S155 at 1.4M
K4 S174 finished to 900K extended to 950K

S163 tested to n=500k (400-500k)

nothing found, 13 remain

Results emailed - Base released

Reserving R148 to n=300k (200-300k) for BOINC

Reserving R111 up to n=500K.

Reserving R211 to n=300k (200-300k) for BOINC
Reserving R212 to n=300k (200-300k) for BOINC

Reserving R250 up to n=10K.

R148 tested to n=300k (200-300k)

1 prime found, 4 remain

Results emailed - Base released

Reserving R210 as new base using the new-base script up to 2.5k and sieving to 10k (1G) with srsieve2

R212 tested to n=300k (200-300k)

nothing found, 4 remain

Results emailed - Base released

R210 tested to n=2.5k + sieved to 1G (2.5-10k)

239583 remain

Results emailed - Base released

R211 tested to n=300k (200-300k)

nothing found, 4 remain

Results emailed - Base released

Progress update
 

K4 S155 at 1.425M

Reserving R117 to n=300k (250-300k) for BOINC

Reserving S117.

S174 at 920K

Back at it again...

Will reserve S157. I plan to get at least to 400k on it but may go further... it depends.

R117 tested to n=300k (250-300k)

nothing found, 8 remain

Results emailed - Base released

Reserving R124 to n=10k (2.5-10k)

[QUOTE=rebirther;590274]Reserving R124 to n=10k (2.5-10k)[/QUOTE]
This has 88011 k's remaining, which makes it a very large effort. Do you have the right base? :-)

[QUOTE=gd_barnes;590357]This has 88011 k's remaining, which makes it a very large effort. Do you have the right base? :-)[/QUOTE]

yes, I will run it on 12 cores with the stoponprimek option, sieving to 10G, should be around 2M tests per core

Reserving R103 to n=600K.

Reserving R133 to n=600K.

R103 is complete to n=600K; no primes were found for n=575K-600K; 1 k still remains; base released.

Reserving R123 to n=600K.

R133 is complete to n=600K; no primes were found for n=550K-600K; 1 k still remains; base released.

Reserving R213 to n=600k (500-600k) for BOINC

R123 is complete to n=600K; no primes were found for n=555K-600K; 1 k still remains; base released.

R124 tested to n=10k (2.5-10k)

33238 found, 54773 remain

Results emailed - Base released

S117 completed to n=800000. No primes found. Residues attached. Range released.

Reserving R158 to n=500K.

[QUOTE=MisterBitcoin;585991]Reserving R250 up to n=10K.[/QUOTE]


Already finished a month ago but it reached n=10K. Found 3349 primes, releasing this base.

Reserving S190 to n=10k (2.5-10k)

Reserving R191 to n=500K.

R158 is complete to n=500K; no primes were found for n=300K-500K; 2 k's still remain; base released.

S190 tested to n=10k (2.5-10k)

5942 primes found, 4749 remain

Results emailed - Base released

Reserving R126 to n=10k (2.5-10k)

R213 tested to n=600k (500-600k)

nothing found, 1 remain

Results emailed - Base released

R126 tested to n=10k (2.5-10k)

8008 primes found, 7223 remain

Results emailed - Base released

Progress update
 

K4 S155 at 1.475M
K4 S174 at 950K - continue to 1M

Reserving R126.

R191 is complete to n=500K; no primes were found for n=300K-500K; 2 k's still remain; base released.

Reserving R130

Reserving S218 to n=600K.

S218 is complete to n=600K; no primes were found for n=500K-600K; 1k still remains; base released.

[QUOTE=rogue;594214]Reserving R126.[/QUOTE]

Completed to n=25000. Primes attached. Range released

[QUOTE=rogue;596449]Completed to n=25000. Primes attached. Range released[/QUOTE]
I get a bunch of gibberish when I try to open this file.

[QUOTE=gd_barnes;596469]I get a bunch of gibberish when I try to open this file.[/QUOTE]I had the same problem when I tried to open it with the old M$ plain-text editor Notepad. It looked like a bunch of Chinese characters or something. It was especially weird because the M$ file preview had displayed it OK.

So I opened the file in WordPad, and it looked OK. I then saved the WordPad file window to the original file name, thereby replacing the original file. The replacement opened OK in Notepad.

I also downloaded the file to a Mac. It opened OK in TextEdit as a plain text file.

[b]EDIT:[/b] It is not immediately obvious to me why the numbers are entered in the order that they are. What determines that?

There is no "order by" in the SELECT that generated this output.

Yes, this was created on a Mac, so the linefeeds are probably not what you expect. If you open in NotePad++ on Windows, it looks good.

[QUOTE=Dr Sardonicus;596472][B]EDIT:[/B] It is not immediately obvious to me why the numbers are entered in the order that they are. What determines that?[/QUOTE]
They are ordered by k-value. If you do your searching by k-value that is how they will be saved.

[QUOTE=rogue;596484]Yes, this was created on a Mac, so the line feeds are probably not what you expect. If you open in NotePad++ on Windows, it looks good.[/QUOTE]
Please post in standard NotePad format in the future. I have not had this problem before. Yes it appears to display a bunch of Asian-language characters in NotePad. I'm not sure why the line-feeds would be different amongst different operating systems. I also don't know why simply having different line-feeds would mess up the entire display of the file. It's like the ASCII characters are completely different regardless of the different line-feeds. I was able to open it in WordPad.

[QUOTE=gd_barnes;596489]They are ordered by k-value. If you do your searching by k-value that is how they will be saved.

Please post in standard NotePad format in the future. I have not had this problem before. Yes it appears to display a bunch of Asian-language characters in NotePad. I'm not sure why the line-feeds would be different amongst different operating systems. I also don't know why simply having different line-feeds would mess up the entire display of the file. It's like the ASCII characters are completely different regardless of the different line-feeds. I was able to open it in WordPad.[/QUOTE]

I see that the file I posted looks like garbage in NotePad, but looks perfectly fine in NotePad++. I produced this file in the same way I produce most of the files that I generate on my Mac that I have posted here that you haven't had any issues with. The difference this time is that I did not compress the .txt file into .7z format so I suspect that the tool you are using to decompress the .7z files is converting the linefeeds.

I strongly suggest you switch to NotePad++. It is completely free (unlike TextPad which gives regular reminders to pay for it) and you won't regret it. It handles large files much better than NotePad and you can have multiple files open concurrently in the same window. It also supports syntax highlighting so if you are looking at source code for many supported languages, it helps a great deal. And of course it handles the various EOL characters.

[QUOTE=gd_barnes;596469]I get a bunch of gibberish when I try to open this file.[/QUOTE]


Notepad++ is working and the best and fastest program ever, the rest is windows junk :/

[QUOTE=gd_barnes;596489]They are ordered by k-value. If you do your searching by k-value that is how they will be saved.
<snip>[/quote]D'oh! I should have seen that! :blush:[quote]I'm not sure why the line-feeds would be different amongst different operating systems. I also don't know why simply having different line-feeds would mess up the entire display of the file. It's like the ASCII characters are completely different regardless of the different line-feeds. I was able to open it in WordPad.[/QUOTE]If memory serves, old M$ OS's use CR-LF while Unix(alike) OS's just use LF. I also don't see how that would mess up the other chars. I thought it might have had to do with the encoding. NotePad might assume ANSI, which might cause trouble for UTF text files. I have noticed that when I copy-paste text into a NotePad window, and want to save the file, NotePad recognizes UTF encoding, but will save the file as ANSI unless I cancel the Save, start over, and choose UTF from a little options box before saving.

Notepad sometimes detects the enconding of files with lots of digits wrongly. This is not a problem of the file, it is a bug in notepad.exe, unfortunately. This will also happen if the file is saved normally with Notepad and then opened with the exact same version of Notepad.

A workaround might be using UTF-16.

[QUOTE=kruoli;596563]Notepad sometimes detects the enconding of files with lots of digits wrongly. This is not a problem of the file, it is a bug in notepad.exe, unfortunately. This will also happen if the file is saved normally with Notepad and then opened with the exact same version of Notepad.

A workaround might be using UTF-16.[/QUOTE]

The best answer is to not use Notepad.exe - it's just not really suitable for anything of significance. I immediately reassign .txt to be opened with something else (usually Notepad++) when I'm working on a Windows machine.

[QUOTE=rogue;596513]I see that the file I posted looks like garbage in NotePad, but looks perfectly fine in NotePad++. I produced this file in the same way I produce most of the files that I generate on my Mac that I have posted here that you haven't had any issues with. The difference this time is that I did not compress the .txt file into .7z format so I suspect that the tool you are using to decompress the .7z files is converting the linefeeds.

I strongly suggest you switch to NotePad++. It is completely free (unlike TextPad which gives regular reminders to pay for it) and you won't regret it. It handles large files much better than NotePad and you can have multiple files open concurrently in the same window. It also supports syntax highlighting so if you are looking at source code for many supported languages, it helps a great deal. And of course it handles the various EOL characters.[/QUOTE]
As stated I was able to read the file with WordPad. I have NotePad++ when I've had to access large files (> 1 GB). I can use it but files in this format require me to take an extra step to pull up the specific software used instead of just double clicking on the file and having it open up.

I feel strongly that people should post files that everyone should be able to read without having to download or open special software or change default settings. I've rarely if ever encountered this problem before either in my Email or on the forum here.

[QUOTE=gd_barnes;596584]As stated I was able to read the file with WordPad. I have NotePad++ when I've had to access large files (> 1 GB). I can use it but files in this format require me to take an extra step to pull up the specific software used instead of just double clicking on the file and having it open up.

I feel strongly that people should post files that everyone should be able to read without having to download or open special software or change default settings. I've rarely if ever encountered this problem before either in my Email or on the forum here.[/QUOTE]

That is why I check "always open with" when I choose NotePad++ to open a file to make that association. I think there is a setting in NotePad++ to "always use instead of NotePad" so that you don't even need to do that.

In the end it is your choice.

Releasing R151 due to yoyo being unable to provide a sieve file for this base. No work has been done.

Reserving S102 up to n=400k.

Taking R201.

R130 completed to n=25000 and released. Primes attached.

K4 S155 at 1.5M extending to 1.75M

taken R124,with k upto 100k done to n=25k is done. Result send to gd_barnes

R201 completed to n=25000. Primes attached. Range released.