20201011, 20:44  #34 
P90 years forever!
Aug 2002
Yeehaw, FL
7,351 Posts 
I dug into the latest batch of 11 assignments.
I thought the only way to get these was by manually adjusting the exponent range. I was wrong. The manual gpu assignments page lets you select "Lowest exponent". That's how these assignments were reserved. An easy "nonmistake" for someone to make. The manual GPU page no longer offers the "lowest exponent" option. Since these TF assignments were made in good faith, I have not unreserved them. Please let them complete in a reasonable time frame for a GPU. 
20201011, 22:25  #35  
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest
4907_{10} Posts 
Quote:
A good thing too, since that's how I keep my TF gpu fleet fed. I saw the minimum exponent set to 60M, and manually bumped it to 90M. It seems like "TF for first time LLs" ought enforce or at least default to a minimum exponent that is closely related to the recent or current milestone, but that is not what happens. (Maybe that option ought also be renamed, as part of LL/PRP migration.) Setting minimum exponent, and maximum bit depth are useful to target effort where it will be useful. Last fiddled with by kriesel on 20201011 at 23:06 

20201012, 02:24  #36 
P90 years forever!
Aug 2002
Yeehaw, FL
1CB7_{16} Posts 
Selecting lowest exponents is converted to what makes sense. What makes sense means most LL/PRP savings per unit of TF work. That translates to largest exponent for Mersennes that have been TF'ed to the same bit level.

20201012, 03:43  #37  
If I May
"Chris Halsall"
Sep 2002
Barbados
2^{2}×23×103 Posts 
Quote:
This annoyed me, so I did the trick where GPU72's scripts reserved them all, and then immediately released them. I grow tired of having to instruct my code to correct this kind of thing. It shouldn't be possible in the first place. FWTW. Edit: Oh, speak of the devil... It's happened again. No longer my problem. Last fiddled with by chalsall on 20201012 at 03:47 

20201012, 14:06  #38  
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest
7·701 Posts 
Quote:
Issuing TF assignments for higher than optimal TF bit levels does not make sense. Last fiddled with by kriesel on 20201012 at 14:43 

20201012, 17:16  #39  
If I May
"Chris Halsall"
Sep 2002
Barbados
2^{2}·23·103 Posts 
Quote:


20201012, 17:42  #40  
P90 years forever!
Aug 2002
Yeehaw, FL
7,351 Posts 
Quote:
The IP address is 77.111.246.5. Previously, when Dorko 2 was in the 53M range, he was using a TOR exit. 

20201012, 20:37  #41 
P90 years forever!
Aug 2002
Yeehaw, FL
7,351 Posts 
Loser is back to using Tor: 109.70.100.48

20201012, 20:46  #42 
Einyen
Dec 2003
Denmark
101111011100_{2} Posts 
Would it be hard to make the server deny any TF assignments in like 53M59M and 93M108M ?

20201012, 21:02  #43 
P90 years forever!
Aug 2002
Yeehaw, FL
7,351 Posts 
And back to 77.111.245.10 when Tor failed to get the latest 1000. It looks like Hern Labs in Sweden is home base for this human garbage.

20201013, 00:20  #44 
If I May
"Chris Halsall"
Sep 2002
Barbados
2^{2}·23·103 Posts 

Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
possible overlapping Fermat factor ranges  MattcAnderson  FermatSearch  3  20210105 14:34 
Trial Factoring  Factor Confirmation?  butera  GPU to 72  3  20210102 23:43 
Trial Factor Bit Depth  lavalamp  Operation Billion Digits  8  20100802 18:49 
trial division over a factor base  Peter Hackman  Factoring  7  20091026 18:27 
Shortest time to complete a 2^67 trial factor (no factor)  dsouza123  Software  12  20030821 18:38 