20200530, 05:18  #320 
"Graham uses ISO 8601"
Mar 2014
AU, Sydney
241 Posts 
I guess that we're not connecting on this issue.
Yes I am aware that .ca processing occurs at some hours after 00:00 UTC. Yet multiple factor found results were not recorded as such at .ca until a further 24 hours, plus those lazy hours, in the mean time being recorded instead differently, but distinctly not recorded as factor found. 
20200621, 06:11  #321 
"Graham uses ISO 8601"
Mar 2014
AU, Sydney
F1_{16} Posts 
Suitable TF target indication
I was quite pleased to see the yellow background on cells (introduced many months ago) to indicate at least one marker of tour destination being achieved.
Is there warranted a second level marker, or should it be best simply imagined three more steps would be admirable, which is the way that I am inclined so far? 
20200621, 12:15  #322  
"James Heinrich"
May 2004
exNorthern Ontario
D21_{16} Posts 
Quote:
The TF Status Report has yellow highlighting on the "target" TF level, approximating the TF level to which GPU72 will assign exponents (and 4 bit levels above PrimeNet TF level). There might be small variations between these targets and what GPU72 actually assigns, but it should be pretty close. I wouldn't make any effort to TF beyond this level, the effort could probably be better spent elsewhere. The tf1G page has yellow highlighting on the bit level that will require at least 1 GHzday of effort, below that no individual record of work is retained (unless a factor is found). The target TF level is listed in the cyan column and is about 10 bit levels off the chart. 

20200626, 15:53  #323 
Jul 2003
wear a mask
3^{2}×179 Posts 
Here's a curious case. Did someone really trialfactor this exponent to 2^99?

20200626, 16:15  #324 
6809 > 6502
"""""""""""""""""""
Aug 2003
101×103 Posts
22546_{8} Posts 
I would guess that was found via P1 and just submitted

20200626, 16:23  #325 
Jul 2003
wear a mask
64B_{16} Posts 
It might makes sense that the default behavior of the server is to assume 'naked' factors were found by trial factoring. However, for bookkeeping purposes and subsequent factor searches, that report is misleading. There could be more factors below 2^99. If a factor is found by ECM, there's even a chance that the P1 bounds listed here aren't accurate.

20200626, 17:01  #326  
Jun 2003
7·709 Posts 
Quote:


20200626, 17:15  #327  
"James Heinrich"
May 2004
exNorthern Ontario
3,361 Posts 
Quote:
Thanks for reporting. 

20200626, 17:17  #328  
1976 Toyota Corona years forever!
"Wayne"
Nov 2006
Saskatchewan, Canada
4,637 Posts 
Quote:
https://www.mersenne.org/report_expo...exp_hi=&full=1 PrimeNet will know it wasn't TF'd to 99. 

20200626, 17:20  #329  
6809 > 6502
"""""""""""""""""""
Aug 2003
101×103 Posts
2·4,787 Posts 
Quote:
[edit]Correction, I will only take it to 70, which is 1 step beyond the GPU72 level. 65 was the default PrimeNet level.[/edit] Last fiddled with by Uncwilly on 20200626 at 18:35 

20200626, 18:27  #330 
"Oliver"
Sep 2017
Porta Westfalica, DE
3^{2}×5×11 Posts 
Will that only work for new factors? I looked up M3643 and it shows an actual TF limit of 2^{209} even after Ctrl+F5 and the same on a fresh browser installation on another machine.

Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
Small inconsistencies between mersenne.org and mersenne.ca factor databases  GP2  mersenne.ca  44  20160619 19:29 
mersenne.ca (ex mersennearies.sili.net)  LaurV  mersenne.ca  8  20131125 21:01 
GaussianMersenne & EisensteinMersenne primes  siegert81  Math  2  20110919 17:36 
Mersenne Wiki: Improving the mersenne primes web site by FOSS methods  optim  PrimeNet  13  20040709 13:51 