Join PrimeGrid
Returning Participants
Community
Leader Boards
Results
Other
drummers-lowrise
|
Message boards :
General discussion :
Im new here..
| Author |
Message |
|---|
|
|
|
Hi everyone, I just started running prime grid, and Im just wondering if theres a way to see what numbers that Im actually checking and stuff like that? | |
|
 RafaelVolunteer tester
Send message
Joined: 22 Oct 14
Posts: 906
ID: 370496
Credit: 479,373,797
RAC: 218,485
                   
|
Hi everyone, I just started running prime grid, and Im just wondering if theres a way to see what numbers that Im actually checking and stuff like that?
Hey James, wellcome to PrimeGrid!
As far as the site goes, you can't really see what you're testing, aside for when do make a discovery, in which case it'll show up in Your Account page. With that said, the subproject you're running will NEVER find anything, as by design, it's goal is to quickly remove numbers that are definitely not prime rather than having to test them slowly, so you'll never see anything on your page.
Outside of that, you can manually go to the app's directory and retrieve the files manually, at which poinnt you can look at what is being done. | |
|
|
|
|
Welcome, James de Haan !
____________
"Accidit in puncto, quod non contingit in anno."
Something that does not occur in a year may, perchance, happen in a moment. | |
|
Crun-chi Volunteer tester
Send message
Joined: 25 Nov 09
Posts: 3114
ID: 50683
Credit: 76,797,694
RAC: 7,338
                      
|
Hi everyone, I just started running prime grid, and Im just wondering if theres a way to see what numbers that Im actually checking and stuff like that?
And since you make sieve , there is no chance to find prime, since sieve doesnot do that.
____________
92*10^1439761-1 NEAR-REPDIGIT PRIME :) :) :)
4 * 650^498101-1 CRUS PRIME
314187728^131072+1 GENERALIZED FERMAT
Proud member of team Aggie The Pew. Go Aggie! | |
|
|
|
|
James de Haan, in case you wonder, all your tasks are sieve tasks that only find composite numbers (i.e. numbers that we will not have to process further), never primes.
If you want other kinds of tasks, go to your PrimeGrid preferences page, then click "Edit PrimeGrid preferences" (or whatever it may be called in your language if your web browser asks for another language than English), then under "Applications" and "Subproject (XX)", choose some projects that are not related to "sieve", and finally save your choice by pressing the button in the bottom of that page.
/JeppeSN | |
|
|
|
|
Welcome to PrimeGrid James de Haan. As JeffeSN has said if you want to find a prime follow his advice and change your preferences from a sieve project to one of the others. When you look under primegrid preferences under your account and select to change one, you will be able to see approximate computing times each project takes to run one task. These are estimates and vary, but they will give you an idea of how long it is taking to check one number on each of those projects on average. | |
|
AzmodesVolunteer tester
Send message
Joined: 30 Dec 16
Posts: 184
ID: 479275
Credit: 2,188,202,713
RAC: 438,992
                     
|
As far as the site goes, you can't really see what you're testing
I thought the task name contained that information?
____________
Long live the sievers.
+ Encyclopaedia Metallum: The Metal Archives + | |
|
|
|
|
Azmodes wrote: I thought the task name contained that information?
I also thought so, at first.
But the task name doesn't seem to give any clue of what is being tested.
For example, from my private log:
2018/10/23 07:41:18 genefer20_19392806_1
2018/10/23 07:41:18 1055334^1048576+1 is composite. (RES=3cf281e9f683a89a) (6315983 digits) (err = 0.0000) (time = 5:06:23) 04:41:18
2018/10/23 07:41:24 genefer20_19392806_1
2018/10/23 07:46:46 llrSGS_306610763_1
2018/10/23 07:46:46 4146253429545*2^1290000-1 is not prime. LLR Res64: 76F5CA58353A420D Time : 578.563 sec.
2018/10/23 07:46:52 llrSGS_306610763_1
____________
"Accidit in puncto, quod non contingit in anno."
Something that does not occur in a year may, perchance, happen in a moment. | |
|
JimBHonorary cruncher
Send message
Joined: 4 Aug 11
Posts: 918
ID: 107307
Credit: 977,945,376
RAC: 45
        
|
|
The digits in the workunit name are our internal database id's. Those digits have no relationship to the digits in the candidate being tested. | |
|
|
|
|
As an example, the recent prime 4151902060467*2^1290000-1 was work unit ID 585098108 (name: llrSGS_306680797) and its two tasks had IDs 942375689 (name: llrSGS_306680797_0) and 942375690 (name: llrSGS_306680797_1). /JeppeSN | |
|
robishVolunteer moderator
Volunteer tester
Send message
Joined: 7 Jan 12
Posts: 2136
ID: 126266
Credit: 6,781,433,864
RAC: 2,756,784
                  
|
The digits in the workunit name are our internal database id's. Those digits have no relationship to the digits in the candidate being tested.
I often wondered that Jim, how come llr tasks do not output the tested number to sdtout like gfn does?
____________
My lucky numbers 10590941048576+1 and 224584605939537911+81292139*23#*n for n=0..26 | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13804
ID: 53948
Credit: 345,369,032
RAC: 4,797
        
|
The digits in the workunit name are our internal database id's. Those digits have no relationship to the digits in the candidate being tested.
I often wondered that Jim, how come llr tasks do not output the tested number to sdtout like gfn does?
The idea is that, since sometimes there's a delay before we can officially report a prime, we don't want the double checker (or ever a third party) to "steal" the prime by reporting it themselves. It's never happened, and I don't consider it likely, but we do want to prevent that from happening.
So when it comes to disclosing the number being tested, and whether it's prime or composite, we feel comfortable doing one or the other, but not both.
You can tell people what the number is, but not say if it's prime. Or you can tell people if it's prime, but not tell them what the number is.
LLR is the older of the two, and it hides the number. The prime status is eventually displayed on the task page.
With Genefer, we decided to go the other way. The number is shown in the output, but it never says whether it's prime or not. At least nowhere that's visible to you.
____________
My lucky number is 75898524288+1 | |
|
robishVolunteer moderator
Volunteer tester
Send message
Joined: 7 Jan 12
Posts: 2136
ID: 126266
Credit: 6,781,433,864
RAC: 2,756,784
|
The digits in the workunit name are our internal database id's. Those digits have no relationship to the digits in the candidate being tested.
I often wondered that Jim, how come llr tasks do not output the tested number to sdtout like gfn does?
The idea is that, since sometimes there's a delay before we can officially report a prime, we don't want the double checker (or ever a third party) to "steal" the prime by reporting it themselves. It's never happened, and I don't consider it likely, but we do want to prevent that from happening.
So when it comes to disclosing the number being tested, and whether it's prime or composite, we feel comfortable doing one or the other, but not both.
You can tell people what the number is, but not say if it's prime. Or you can tell people if it's prime, but not tell them what the number is.
LLR is the older of the two, and it hides the number. The prime status is eventually displayed on the task page.
With Genefer, we decided to go the other way. The number is shown in the output, but it never says whether it's prime or not. At least nowhere that's visible to you.
Thanks Michael, makes sense.
That's my naive side. Obviously still have one. Never thought of someone stealing one before it's reported. :)
____________
My lucky numbers 10590941048576+1 and 224584605939537911+81292139*23#*n for n=0..26 | |
|
Message boards :
General discussion :
Im new here.. |
