mersenneforum.org Queue management for 16e queue
 Register FAQ Search Today's Posts Mark Forums Read

2020-11-19, 20:54   #23
jyb

Aug 2005
Seattle, WA

170910 Posts

Quote:
Originally Posted by swellman
Quote:
 Originally Posted by axn # 131^106+106^131, difficulty: 267.34 # 131^106+106^131, difficulty: 269.37 I don't get this part. IIUC, for getting the sextic, the number had to be multiplied by 131^2*106, whereas for the quintic, there is no such fiddling necessary. So the sextic difficulty should be 6 digits larger.
Output by Yafu. With SNFS it cranks out dozens of potential polynomials then downselects to the best three for test sieving. Perhaps B^2 can shed more light on the various steps of that Kabuki dance.
Indeed, I don't understand the values Yafu is printing. My calculations show the quintic with a difficulty of 265.32 and the sextic with a difficulty of 271.57, so there's axn's 6 digits right there.

 2020-11-23, 04:34 #24 jyb     Aug 2005 Seattle, WA 110101011012 Posts QUEUED AS 8p3_834M SNFS-251.06 (quartic) C220 HCN (8+3,834M), ECM to t60. Code: n: 4106609588424447396996222513379693412003124266674309491729863520838604405098468326525117796586140070117851619915391156765666063208322467227650127948824324948835330331474513772746013914096270530047953563697353232926629461 skew: 1.22474 c4: 4 c3: 12 c2: 18 c1: 18 c0: 9 Y1: 834385168331080533771857328695283 Y0: -411376139330301510538742295639337626245683966408394965837152256 rlim: 225000000 alim: 225000000 lpbr: 32 lpba: 32 mfbr: 94 mfba: 62 rlambda: 3.6 alambda: 2.6 Trial sieving 2K blocks. Code:  Q Yield --- ----- 50M 2816 90M 3438 130M 3539 170M 3299 210M 3673 250M 3585 290M 3703 330M 3421 Recommend sieving special Q on rational side, 50M - 310M. Last fiddled with by swellman on 2020-11-23 at 11:17
 2021-01-21, 15:27 #25 fivemack (loop (#_fork))     Feb 2006 Cambridge, England 13·491 Posts I've put L3065B (SNFS quartic, no small factor known) onto the 16fs queue. Not quite sure how much ECM has been done on it; it won't get to the front of the queue any time soon so I'll run a few thousand curves at B1=260M on my GTX1080
 2021-01-29, 08:52 #26 fivemack (loop (#_fork))     Feb 2006 Cambridge, England 13·491 Posts The few thousand curves found a factor, I've deleted the job and started running curves on L2250 Last fiddled with by fivemack on 2021-01-29 at 10:17
 2021-02-04, 15:30 #27 fivemack (loop (#_fork))     Feb 2006 Cambridge, England 13·491 Posts 6400 curves at B1=260M found no factor for L2250; I've queued up the job while post-processing a further 3840 curves. It looks rather low yield even for an SNFS-250 quartic, but 300MQ ought to get there.
 2021-04-23, 19:26 #28 swellman     Jun 2012 41·73 Posts HCN 3+2_1758L 3p2_1758L from the Homogeneous Cunningham project, ready for GNFS on 16f. Code: n: 1734147512979270320827767012217086906506556317798760101066642797284407332516993027773365157763102197607514963117947733088678302843725492651987691057475083298632139047698473602163355874115229 # norm 1.768320e-18 alpha -6.842932 e 2.201e-14 rroots 5 lss: 0 skew: 34619080.46 c0: -82717367334817895153685976600674902106038703 c1: 24230002666061859616959799270512489908 c2: 2098794365094139007789717181182 c3: -69148370343514243109752 c4: -1784626917919455 c5: 14642100 Y0: -2598343318530561190088419286201562362 Y1: 328301570246391373 rlim: 134000000 alim: 134000000 lpbr: 31 lpba: 31 mfbr: 62 mfba: 91 rlambda: 2.6 alambda: 3.4 Test sieving on the -a side with Q in blocks of 10k Code: 50M 17458 70M 19075 100M 17788 150M 15621 150M 15621 200M 15220 250M 12661 Suggesting a Q-range of 50-210M.
 2021-04-30, 05:44 #29 pinhodecarlos     "Carlos Pinho" Oct 2011 Milton Keynes, UK 23×3×5×41 Posts Sean, can you please check if the poly for 6p5_1110L is correct, people are complaining about these tasks all fail to complete. Thank you.
2021-04-30, 13:03   #30
swellman

Jun 2012

41×73 Posts

Quote:
 Originally Posted by pinhodecarlos Sean, can you please check if the poly for 6p5_1110L is correct, people are complaining about these tasks all fail to complete. Thank you.
I did find an issue - an extraneous line at the end of the .poly file. I do not have rights to edit a number in sieving, which is probably a good thing. I’ve asked Greg to intercede.

 2021-04-30, 16:06 #31 swellman     Jun 2012 41×73 Posts Greg has reset 6p5_1110L. Turns out Windows clients ignore the error but Linux clients fail, resulting in a lot of noise. Apologies to all.
2021-04-30, 16:27   #32
jyb

Aug 2005
Seattle, WA

1,709 Posts

Quote:
 Originally Posted by swellman I did find an issue - an extraneous line at the end of the .poly file. I do not have rights to edit a number in sieving, which is probably a good thing. I’ve asked Greg to intercede.
Extraneous line or no, more than 60,000 work units have been successfully returned, resulting in over 170M unique relations. Does it really make sense to kill this job entirely and start over?

At the very least, can't the existing relations be preserved and we can start the sequel job at the point where this one left off? It looks like it managed to get to special-q values of about 77M.

 2021-04-30, 18:42 #33 frmky     Jul 2003 So Cal 82816 Posts Yes, that's an option. The relations are still available and valid. You will likely have about 1/2 - 2/3 of the jobs below the leading edge done. You can start sieving at 75M or so and extend at the end if necessary.

 Similar Threads Thread Thread Starter Forum Replies Last Post VBCurtis NFS@Home 28 2021-05-05 08:04 VBCurtis NFS@Home 130 2021-05-04 16:28 Rodrigo Software 7 2018-05-25 13:26 debrouxl NFS@Home 10 2018-05-06 21:05 joblack Information & Answers 1 2009-01-06 08:45

All times are UTC. The time now is 00:57.

Sun May 9 00:57:44 UTC 2021 up 30 days, 19:38, 0 users, load averages: 2.06, 1.91, 1.83