mersenneforum.org  

Go Back   mersenneforum.org > Prime Search Projects > No Prime Left Behind

Reply
 
Thread Tools
Old 2010-06-07, 22:22   #265
gd_barnes
 
gd_barnes's Avatar
 
May 2007
Kansas; USA

22·2,539 Posts
Default

Quote:
Originally Posted by mdettweiler View Post
Gary currently verifies all results on all drives in periodic blocks--when he posts in the drive threads saying "all results and primes have been verified up to n=x" that means he's done it for that range.
No!! That is incorrect. In a PM exchange with what I thought to be both you and Karsten, Karsten is now verifying all server results vs. the sieve files. I was duplicating his results matchup and it took me too long anyway. I only verify primes in the various places and have found no problems in a very long time. I suspect Karsten verifies both results vs. the original sieve file and found primes in post 1 of the drive threads, on top 5000, his own rieselprime page, and his own drive page. But since he is doing the last two items solely on his own, it's best to have another person doublecheck them. That's the only reason I do any kind of verification at all.

Here is what I think we should do based on what you guys are saying:

1. Let the server continue to offload them to the results page.

2. Max, plop all manual results into the results page within 1-2 days after they are done.

3. Karsten, when LLRnet/PRPnet -AND- all manual ranges have been completed up to some set limit, then process all of the results from the results page up to that limit and verify the results against the original sieve file. Since all server and manually-done results should be there, there should be no missing pairs for any range. If some manual results are missing, then it will be up to Max to find them and load them to the page.

Does that sound like the way to go?

Max, this page you're talking about where the sieve is automatically matched up against some processed results sounds like a lot of work and would require a LOT Of testing to make sure it is correct 100% of the time. I highly recommend against it until you are able to become less busy in your personal life. What we are talking about is right now so let's stick with talking about that.


Gary

Last fiddled with by gd_barnes on 2010-06-07 at 22:26
gd_barnes is offline   Reply With Quote
Old 2010-06-07, 22:26   #266
kar_bon
 
kar_bon's Avatar
 
Mar 2006
Germany

2×32×157 Posts
Default

As input for my processing/verifying script I use the normal LLRnet result file (3 lines for one pair). I think I can easily edit this to input normal LLR-resultsfiles, too (one line forn one pair).
So I only need all resultfiles available like those from the servers!
kar_bon is offline   Reply With Quote
Old 2010-06-07, 23:29   #267
mdettweiler
A Sunny Moo
 
mdettweiler's Avatar
 
Aug 2007
USA (GMT-5)

11000011010012 Posts
Default

Quote:
Originally Posted by gd_barnes View Post
No!! That is incorrect. In a PM exchange with what I thought to be both you and Karsten, Karsten is now verifying all server results vs. the sieve files. I was duplicating his results matchup and it took me too long anyway. I only verify primes in the various places and have found no problems in a very long time. I suspect Karsten verifies both results vs. the original sieve file and found primes in post 1 of the drive threads, on top 5000, his own rieselprime page, and his own drive page. But since he is doing the last two items solely on his own, it's best to have another person doublecheck them. That's the only reason I do any kind of verification at all.
Ah, I see. I don't believe I ever got a PM to that effect, but that sounds fine. As long as somebody's doing the verification, we're OK.

Quote:
Here is what I think we should do based on what you guys are saying:

1. Let the server continue to offload them to the results page.

2. Max, plop all manual results into the results page within 1-2 days after they are done.

3. Karsten, when LLRnet/PRPnet -AND- all manual ranges have been completed up to some set limit, then process all of the results from the results page up to that limit and verify the results against the original sieve file. Since all server and manually-done results should be there, there should be no missing pairs for any range. If some manual results are missing, then it will be up to Max to find them and load them to the page.

Does that sound like the way to go?
Okay, that should work. Sounds like a plan. Most of the active drives are being done exclusively via servers at this point, so manual ranges should be far and few enough that the plan you outlined would indeed make things somewhat simpler.

Quote:
Max, this page you're talking about where the sieve is automatically matched up against some processed results sounds like a lot of work and would require a LOT Of testing to make sure it is correct 100% of the time. I highly recommend against it until you are able to become less busy in your personal life. What we are talking about is right now so let's stick with talking about that.
Yeah, I definitely wasn't thinking of doing that right away. My mention of that was just me rambling about possibly overambitious ideas for the future.
mdettweiler is offline   Reply With Quote
Old 2010-06-11, 22:08   #268
gamer007
 
Mar 2009

2·3·31 Posts
Default

519K-520K is complete. No primes.

Reserving 520K-521K.
Attached Files
File Type: zip 519K-520K.zip (60.4 KB, 49 views)

Last fiddled with by gamer007 on 2010-06-11 at 22:11 Reason: Forgot to upload results.
gamer007 is offline   Reply With Quote
Old 2010-06-21, 08:35   #269
Svenie25
 
Svenie25's Avatar
 
Aug 2008
Good old Germany

3×47 Posts
Default

516K-517K is done, no primes, rsults emailed to Gary. The lower file will be done today or until tomorrow morning.

Just in time before going to take a cure for at least 3 weeks. ;)
Svenie25 is offline   Reply With Quote
Old 2010-06-21, 11:52   #270
kar_bon
 
kar_bon's Avatar
 
Mar 2006
Germany

282610 Posts
Default

@Jonathan (gamer007)
Please check your result-file for the range n=512k-513k:
There're 5 pairs missing (from end of sieve-file), namely
Code:
3091 512999
3123 512999
3129 512999
3105 513000
3119 513000

@Max
The resultfile for range n=506k-507k contains twice the pair 3117*2^506005-1!
Please delete one of them.

@Max,Gary
By now I've not checked the manually results, because I got not all of them.
The above error was very obvious and I don't know if there're more errors!
Please check those result-files.

@all
I've updated the Mini Drive #3 page at rieselprime.de.

Karsten

Last fiddled with by kar_bon on 2010-08-22 at 11:07
kar_bon is offline   Reply With Quote
Old 2010-06-21, 16:21   #271
mdettweiler
A Sunny Moo
 
mdettweiler's Avatar
 
Aug 2007
USA (GMT-5)

11000011010012 Posts
Default

Quote:
Originally Posted by kar_bon View Post
@Max
The resultfile for range n=506k-507k contains twice the pair 3117*2^506005-1!
Please delete one of them.
Hmm...strange. I don't see that in my copy. Here's what I have for n=506005:
Code:
3019*2^506005-1 is not prime.  LLR Res64: 318C7157BE6FB2AB  Time : 426.101 sec.
3025*2^506005-1 is not prime.  LLR Res64: 14C6F5CF76B5653B  Time : 430.757 sec.
3099*2^506005-1 is not prime.  LLR Res64: A7D070F2E8ED25C1  Time : 421.261 sec.
3117*2^506005-1 is not prime.  LLR Res64: A894E68E2E5A83EA  Time : 407.875 sec.
3129*2^506005-1 is not prime.  LLR Res64: 1BF46C44FC32AC12  Time : 404.264 sec.
3139*2^506005-1 is not prime.  LLR Res64: 85AEC41B034E4C72  Time : 387.427 sec.
Thus, it would seem that somewhere along the line (Gary?) the duplicate was removed prior to my receiving the results.

Last fiddled with by mdettweiler on 2010-06-21 at 16:21 Reason: fix quote
mdettweiler is offline   Reply With Quote
Old 2010-06-21, 16:41   #272
kar_bon
 
kar_bon's Avatar
 
Mar 2006
Germany

B0A16 Posts
Default

Quote:
Originally Posted by mdettweiler View Post
Thus, it would seem that somewhere along the line (Gary?) the duplicate was removed prior to my receiving the results.
Download from post #222!
kar_bon is offline   Reply With Quote
Old 2010-06-21, 17:38   #273
mdettweiler
A Sunny Moo
 
mdettweiler's Avatar
 
Aug 2007
USA (GMT-5)

3×2,083 Posts
Default

Quote:
Originally Posted by kar_bon View Post
Download from post #222!
Yes, I tried that and verified that the duplicate is present in the file attached there. However, the file I have (which was provided to me by Gary as an aggregate 500K-510K file) does not have the duplicate, so I must assume it was removed somewhere along the line.
mdettweiler is offline   Reply With Quote
Old 2010-06-21, 20:11   #274
gamer007
 
Mar 2009

2·3·31 Posts
Default

Quote:
Originally Posted by kar_bon View Post
@Jonathan (gamer007)
Please check your result-file for the range n=312k-313k:
There're 5 pairs missing (from end of sieve-file), namely
Code:
3091 512999
3123 512999
3129 512999
3105 513000
3119 513000
Hmm.. not sure what happened there. Probably missed them while I was dividing the work between my cores. Here's the updated results.
Attached Files
File Type: zip 512K-513K.zip (59.4 KB, 45 views)
gamer007 is offline   Reply With Quote
Old 2010-06-21, 20:24   #275
kar_bon
 
kar_bon's Avatar
 
Mar 2006
Germany

2·32·157 Posts
Default

Thanks! I've updated post #222 with the correct result-file (doubled result for pair 3117*2^506005-1).
kar_bon is offline   Reply With Quote
Reply

Thread Tools


Similar Threads
Thread Thread Starter Forum Replies Last Post
Sierp base 3 - mini-drive II gd_barnes Conjectures 'R Us 46 2009-10-26 18:19
Riesel base 3 - mini-drive I gd_barnes Conjectures 'R Us 199 2009-09-30 18:44
Sierp base 3 - mini-drive Ib gd_barnes Conjectures 'R Us 43 2009-03-06 08:41
Sierp base 3 - mini-drive Ia gd_barnes Conjectures 'R Us 170 2008-11-11 05:10
mini-drive for high-n testing on Sierp base 4 gd_barnes Conjectures 'R Us 43 2008-07-16 10:12

All times are UTC. The time now is 12:56.

Mon Jul 13 12:56:31 UTC 2020 up 110 days, 10:29, 1 user, load averages: 2.40, 2.08, 2.06

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.

This forum has received and complied with 0 (zero) government requests for information.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.
A copy of the license is included in the FAQ.