View Single Post
2021-09-21, 11:33   #75
swellman

Jun 2012

3,203 Posts

Quote:
 Originally Posted by Plutie Found this one! No spin done yet apart from EdH's script, which produced no better results. Code: n: 533439167600904850230361756102700151678687933392166847323827307497363839257031077774321424872955045754669625577486179222154434651598903112919949771321416511589029559325246084363632977829645558547714072241 Y0: -5364063517160195101439064344720425686774 Y1: 38191391760434248123003 c0: -515349887751874687116560925109512114626453230780 c1: 17974344725264404895365666536735938178777 c2: -101346622782727207541871449878174 c3: -1497180969353527609911507 c4: 1395152266302128 c5: 240240 skew: 428721961.354 # lognorm 62.56, E 54.79, alpha -7.77 (proj -2.37), 3 real roots # MurphyE(Bf=1.000e+07,Bg=5.000e+06,area=1.000e+16)=3.496e-15
Plutie -

I am curious, what parameters did you use in finding this poly?

One other note, when I first saw this posted it had another skew per CADO but then you edited it to match cownoise. Do you still have the old skew value? Most folks don’t bother changing the skew from the CADO result - it seems to have little effect on sieving efficiency with these big GNFS jobs. And I believe the old skew value was < 300e6 which is the upper limit on skew per an old rule of thumb.

One could extend this argument further by saying if the skew is too high just lower it until it’s not too high…