The number of Proth tests completed has gone up from around 500 per day for the last weeks to over 1400 for today while the overal throughput only rises slowly.
Anything broken in the stats?
Yes, it's strange.
Also, n Lower bound for 55459 dropped from 540046 to 1018, and min n for the current test window for it is just 169858. As you know, 55459 is the k with highest density of candidates per given range.
What comes to my mind is "may be" Louie wanted to run quick double check tests on low ranges of that k.
PS: I'm just guessing by putting the pieces together. This might be totally wrong.
Nuri is exactly right. I didn't go to much trouble to hide it. I just wanted to see how long it would take smh to notice the test number going up.
anyway, technically, the lower ranges of 12 remaining k values have never been checked by SB. We took it on faith that the previous searchers organized by Keller did them right. Most of them used proth.exe or old versions of prp that didn't produce residues... so there is really no way to verify their work without doing it again. However, these tests take very little time compared to current tests. It's kinda fun to watch my machine do a test a minute.
Right now, it's just me doing the low tests and I've only added the tests for k=55459. In the past day, I've done n=1000-181000. SB started testing at n=540000. So there are still a bunch of tiny tests left.
If you want to do some, change your username to 'secret'. It will automatically assign you one of the tiny tests.
In the rare chance that a prime is found this way, I'll dive into the database and track you down by IP address to make sure you get credit.
-Louie
Louie
Thanks
Payam
Louie, thats a very good idea make a quick run on those ranges previously not tested by SoB.Originally posted by jjjjL
If you want to do some, change your username to 'secret'. It will automatically assign you one of the tiny tests.
-Louie
Just a little note for those who might try that 'secret' username. Copying the client to another folder in the machine you are already using for SoB and changing the user name to secret does not solve the problem of preserving your current test. So, it looks like a good idea to finish current prp test before making the change in user name.
PS: I accidentally lost my 21181*2^2337020+1 test while making that changeover. I was slowly prping that for the last two months since sieving started, and only 6 blocks were left. Well, its no big deal anyway (unless it turns out to be a prime, which would be bad luck of me personally)
Its easy to get that test back, as long as you still have the save file. Just put the old values back into the registrie and continue crunching. Such a wast to not comple two months of work.PS: I accidentally lost my 21181*2^2337020+1 test while making that changeover. I was slowly prping that for the last two months since sieving started, and only 6 blocks were left. Well, its no big deal anyway (unless it turns out to be a prime, which would be bad luck of me personally )
I'll do it for you if you don't want to do it your self. I just need the save file.
Louie: Is it possible, to make the expiration times for these particualr test much smaller (on day, or even 1 hour)?
I'm running some tests (less then 5 minutes on my P4, but don't want to hold up the status when i quit.
Oh, thx smh. I saw the z2337020 file.
It's for sure that I'd be happy to get it back.
Now, I just have to figure out how to put the old values back into the registry.
EDIT: Well, I figured it and got the test back. Thx again smh.
Last edited by Nuri; 03-08-2003 at 10:00 AM.
I installed the SB client on my portable since I had it connected to the internet at that time. But I realised that the next time it'll be connected will be 3 months from now (in the best case scenario, I don't use it often).
I'll just paste sb.log file here (I ran and completed two 'secret' tests), like that the work (not that it takes that much time) won't be lost.
[Sat Mar 08 16:04:31 2003] cache cleared
[Sat Mar 08 16:04:36 2003] connecting to server
[Sat Mar 08 16:04:53 2003] logging into server
[Sat Mar 08 16:04:54 2003] requesting a block
[Sat Mar 08 16:04:58 2003] got proth test from server (k=55459, n=223654)
[Sat Mar 08 16:40:59 2003] residue: CA361EE7BB25218C
[Sat Mar 08 16:40:59 2003] completed proth test(k=55459, n=223654): result 3
[Sat Mar 08 16:40:59 2003] connecting to server
[Sat Mar 08 16:41:00 2003] logging into server
[Sat Mar 08 16:41:01 2003] requesting a block
[Sat Mar 08 16:41:05 2003] got proth test from server (k=55459, n=226498)
[Sat Mar 08 16:42:48 2003] block processing paused
[Sat Mar 08 16:45:13 2003] got k and n from cache
[Sat Mar 08 16:45:17 2003] restarting proth test from cache (k=55459, n=226498) [5.2%]
[Sat Mar 08 17:12:27 2003] residue: 2198833FD6500529
[Sat Mar 08 17:12:27 2003] completed proth test(k=55459, n=226498): result 3
[Sat Mar 08 17:12:27 2003] connecting to server
[Sat Mar 08 17:12:28 2003] couldn't report to server [can't connect], retry in 1200 secs [error: 0]
chvo: I think that is the error (error 3) that results from trying to return a proth test that has expired or already been submitted by someone else.
Don't quote me on that, but it might require a clearing of the cache to get a different proth test (though don't do this until someone else verifies the error).
Lord I hope result/error 3 is not an expired test.. if so i've been turning those in for last 2 months!Originally posted by MAD-ness
chvo: I think that is the error (error 3) that results from trying to return a proth test that has expired or already been submitted by someone else.
You mean "result: 3"? I surely hope that's not an error since that's all I've been getting since I started this project...Originally posted by MAD-ness
chvo: I think that is the error (error 3) that results from trying to return a proth test that has expired or already been submitted by someone else.]
Sorry, I just had to.Don't quote me]
I think you're misreading his post altogether. It looks to me as if he completed two different small "secret" tests. The first result was uploaded correctly to the server while the other was not, due to his connection being down.it might require a clearing of the cache to get a different proth test (though don't do this until someone else verifies the error).
Posting Permissions
Reply With Quote