20190719, 03:26  #45  
"Max"
Jun 2016
Toronto
701_{10} Posts 
C210 poly
Quote:
Code:
Y0: 8433824184756870697292879755887998 Y1: 6851718171937808451398387 c0: 50157313234096582642596433071178509682080150 c1: 131070603403140917396598444903577641749 c2: 771635080061282454139704797834642 c3: 390143412665212478133766565 c4: 1969397541140278648016 c5: 144541785113220 c6: 74178720 skew: 856429.18891 # lognorm 59.44, E 49.58, alpha 9.87 (proj 2.99), 2 real roots # MurphyE = 1.31319727e15 

20190722, 22:39  #46 
"Max"
Jun 2016
Toronto
701 Posts 
C210 polys
The three Gimarel's polys from posts 36 and 43 unfortunately don't spin up, sorry.
@swellman: Thank you for the PM. 
20190723, 00:52  #47  
"Max"
Jun 2016
Toronto
701 Posts 
C210 polys
Quote:
Code:
Y0: 11945075559091849769723496148553586 Y1: 20598621408885914689078117 c0: 13501574082332817040603148668654622503347773320 c1: 10156881097460087806945005627043407706466 c2: 507376313380945306542548696254673 c3: 510623497111647728073268516 c4: 199120054352596466 c5: 6623191339726 c6: 1100715 skew: 5701047.29482 # lognorm 59.44, E 49.91, alpha 9.53 (proj 1.26), 4 real roots # MurphyE = 1.39786197e15 Code:
Y0: 5969974157519860579463204168147441 Y1: 41197242817771829378156234 c0: 4948432546369891708467662655357568688304015 c1: 46198486877243578879304102264648068968 c2: 35388008013238892347531774203699 c3: 514868288492261548046580388 c4: 36267187927953793976 c5: 132273253955296 c6: 70445760 skew: 757624.78917 # lognorm 58.42, E 49.79, alpha 8.63 (proj 2.41), 4 real roots # MurphyE = 1.34461710e15 Code:
Y0: 5972537779545924884861748074276793 Y1: 20598621408885914689078117 c0: 3375393520583204260150787167163655625836943330 c1: 5078440548730043903472502813521703853233 c2: 507376313380945306542548696254673 c3: 1021246994223295456146537032 c4: 796480217410385864 c5: 52985530717808 c6: 17611440 skew: 2848696.89912 # lognorm 60.13, E 50.37, alpha 9.76 (proj 2.88), 4 real roots # MurphyE = 1.34452946e15 Last fiddled with by Max0526 on 20190723 at 01:32 

20190730, 14:32  #48 
Apr 2010
2×73 Posts 
Code:
# norm 1.547898e20 alpha 7.709420 e 1.130004e15 rroots 5 skew: 224966051.12 c0: 46523542304709920815932116270534204096078149944102 c1: 1108746025557925802550149908112273592528253 c2: 1247251566549430335138785462051674 c3: 54819856537027331130006773 c4: 55070735672396492 c5: 372372000 Y0: 16108126957193005421825842611692543447840 Y1: 161831307530189843309 
20190801, 15:11  #49 
Apr 2010
2×73 Posts 
Code:
# norm 1.528182e20 alpha 7.971412 e 1.105489e15 rroots 5 skew: 177022801.68 c0: 18141221687315584816029160568403275969140566329420 c1: 5254194658276600631654506562253982994736 c2: 9469476947909136029668922395444289 c3: 49282705511088036410465805 c4: 365507147213333748 c5: 125405280 Y0: 20025219395652712795847739261487881046851 Y1: 194209346463474127813 
20190805, 08:18  #50 
"Curtis"
Feb 2005
Riverside, CA
1000110000111_{2} Posts 
Looks like we're at 1.39 for deg 6, and 1.18 (with a couple of 1.17's and 1.16's) for deg 5.
I should have some time to begin testsieving in a week or two, at least to try to determine what degree we should focus a last burst of poly select on. 2330L may be in postprocessing before the end of August. I suspect other contributors share my interest in doing some other personal work before doing another teamCADOsieve; I'd be willing to start the next CADO team sieve around the time 2330L yields factors (2, perhaps 3 months after 2330L sieve finishes? Say, midNov?). RDS was pretty adamant that this number should be handled by NFS@home; given the schedule above, I think we wouldn't be able to finish CADO sieving before Spring begins, so I think I agree with him. Does anyone with a 48GB+ machine want to sign up for solving a ~50M matrix for 2330M? It might even fit on a 32GB machine, if that machine isn't used for "regular" work. If so, we should aim to complete poly select and testsieving in the next 46 weeks? 
20190806, 19:11  #51  
"Max"
Jun 2016
Toronto
701 Posts 
C210 polys
Quote:
Quote:


20190807, 05:10  #52  
"Seth"
Apr 2019
2·101 Posts 
Quote:


20190807, 06:52  #53  
"Curtis"
Feb 2005
Riverside, CA
7×641 Posts 
Quote:
Anyway, that C206 matrix was around 40M dimensions; data is very thin up at C210, but a matrix of 50 to 55M would take 50% to 80% longer than my C206 did. So, 3ish months on 8 cores, maybe 2 months on all 16 cores (or 6 weeks if you find MPI success). 

20190807, 22:27  #54 
(loop (#_fork))
Feb 2006
Cambridge, England
6,323 Posts 
pineapple (i9/7940X, 14 cores, 64GB memory) stands ready to assist.
It has run a 47.62M matrix at density 114 in just under four weeks. (VBITS=256 is very effective on Skylake hardware when you build with a modern gcc) 
20190808, 02:26  #55 
"Curtis"
Feb 2005
Riverside, CA
7×641 Posts 
Excellent! Perhaps someone previously in contact with frmky can ask if early Sept is acceptable to queue this number; we should be finished with poly select within a month.

Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
Poly select and testsieving for RSA232  VBCurtis  Operation Kibibit  25  20200107 01:57 
YAFU Poly Select Deadline  amphoria  YAFU  22  20160917 09:47 
msieve poly select: choosing Stage1norm  VBCurtis  Msieve  0  20160411 21:33 
Starting NFS skipping poly select  jux  YAFU  5  20160102 01:01 
big job planning  henryzz  Cunningham Tables  16  20100807 05:08 