20151007, 19:07  #364 
"James Heinrich"
May 2004
exNorthern Ontario
3^{3}×131 Posts 
Now with graphs.

20151007, 20:19  #365 
If I May
"Chris Halsall"
Sep 2002
Barbados
2^{2}×7×359 Posts 

20151007, 20:51  #366 
"James Heinrich"
May 2004
exNorthern Ontario
DD1_{16} Posts 
More seriously, perhaps you can break down more specifically what you'd like to see on the P1 data. Mersenne.info doesn't have any P1 data that I saw so I can't copy your good ideas from there. If you just want to know how many exponents in each range have had P1 done I should be able to extract that data reasonably easily. If you want something more than that, please explain to me before I start working on it Last fiddled with by James Heinrich on 20151007 at 20:58 
20151007, 21:14  #367  
If I May
"Chris Halsall"
Sep 2002
Barbados
2^{2}·7·359 Posts 
Quote:
The issue we are now facing is we are (as a community) seriously overpowered with P1, so tracking candidates without P1 compared to those with P1 done is important for our trending and resource management. To answer your question... Very similar to your TF'ing reports; how many candidates were TFed, how many candidates were P1'ed (at what bit level), how many candidates were DC'ed (at what bit level), how many candidates were LL'ed (at what bit level). This will help us all balance our collective resources to obtain optimization. I hope that makes sense; please let me know if it doesn't. 

20151007, 21:22  #368 
"James Heinrich"
May 2004
exNorthern Ontario
6721_{8} Posts 
Your example seems to have many dimensions. Perhaps you could help me visualize that better with a sample table of data you'd like to see? Do you want to see all that data in one table? Or is that 4 separate reports?
I'm not sure how easy it is parse my data for what bitlevel the exponent was at when it was P1'd (or LL'd), I'll have to investigate. 
20151007, 22:25  #369 
"/X\(‘‘)/X\"
Jan 2013
37·79 Posts 
As I understand it, the problem at hand is knowing how many unassigned exponents have no P1, and what TF bitlevel those exponents are at, and how fast those assignments are being consumed.
So it could be as simple as adding an option at the top to show only unassigned assignments without P1. The table and graph could show changes exactly like they currently do for TF, with and without deltas. 
20151007, 22:41  #370 
Aug 2009
Ontario, Canada
7·19 Posts 
Another way of thinking of it is a flag you can toggle to view the TF/LL reports for exponents that have been P1'd, not P1'd or the whole set.

20151008, 03:58  #371  
Serpentine Vermin Jar
Jul 2014
31·107 Posts 
Quote:
Code:
exponent TFBits 80010001 73 80012903 71 80012917 71 80012923 71 80012957 71 80013163 72 80013253 72 80013257 72 80013347 71 80013397 72 80013749 71 80013827 71 80013877 71 80013979 71 80014027 71 80014537 71 80014601 71 80014663 71 80014673 71 80014703 72 80016107 71 80016121 71 80016199 71 80016281 71 80016359 71 80016613 71 80016623 71 80016647 71 80016667 71 80017087 71 80017097 71 80017099 71 80017187 71 80017243 71 80017627 71 80017649 71 80017739 71 80017837 71 80017871 71 80018023 72 80018041 72 80018327 72 80018333 72 80018377 72 80018381 72 80018767 71 80018857 72 80018933 72 80018963 72 80019227 72 Code:
((exponent between 0 and 40e6 and no_factor_to_bits<71) OR (exponent between 40e6 and 50e6 and no_factor_to_bits<72) OR (exponent between 50e6 and 65e6 and no_factor_to_bits<73) OR (exponent between 65e6 and 80e6 and no_factor_to_bits<74) OR (exponent between 80e6 and 999e6 and no_factor_to_bits<75)) Last fiddled with by Madpoo on 20151008 at 04:01 

20151008, 04:40  #372 
"James Heinrich"
May 2004
exNorthern Ontario
3^{3}·131 Posts 
I don't have easy access to which exponents are assigned or not, so if it's important to you guys to have the P1 report based on that then I'll need to enlist Madpoo's help to generate some data for me.
It shouldn't be filtered by "suboptimal" TF, I'd want data on TF levels of all exponents, and not a list of exponents but just a count per range. Something like Code:
SELECT COUNT(*) AS `howmany`, (FLOOR(`exponent` / 10000) * 10000) AS `10k_range` FROM `table` GROUP BY `10k_range`, `tf_bits`, `pm1_is_done`, `pm1_is_available`, `pm1_is_assigned` @Aaron: how heavy a query is something like that? 
20151008, 04:52  #373  
"/X\(‘‘)/X\"
Jan 2013
37·79 Posts 
Quote:


20151008, 14:38  #374  
If I May
"Chris Halsall"
Sep 2002
Barbados
2^{2}·7·359 Posts 
Quote:
Quote:
Having the deltas allow us to make an informed decision as to how many we can take to 75, and how many we should only take to 74. My goal is to not have assigned for LL'ing anything not at at least 75 bits above 65M. GPU72 will "recapture" anything released for P1 at below 75 bits for final TF'ing, assuming a factor isn't found by the P1 run of course. 

Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
Requests?  Xyzzy  Forum Feedback  104  20170402 22:20 
Collaboration Requests  robert44444uk  Prime Gap Searches  2  20170117 07:57 
Requests for change...  WraithX  FactorDB  32  20141218 03:40 
Manual Requests  tului  GPU Computing  15  20140624 06:22 
a few simple requests for v5  ixfd64  PrimeNet  44  20100111 20:21 