C197 poly
 

[code]
R0: -198163287610408008474299544600510487866
R1: 713588604854929381
A0: 464860712074244018011487871108388695701300147178095
A1: 883598583001102527733435593339761342580914
A2: -2028992567682389466010511292053996
A3: -2093021702063113798100666
A4: 831165963415509
A5: 68400
skew 1743820123.59, size 2.088e-019, alpha -8.380, combined = 6.415e-015 rroots = 5
[/code]

no luck here
 

[QUOTE=swellman;484885][code]
R0: -198163287610408008474299544600510487866
R1: 713588604854929381
A0: 464860712074244018011487871108388695701300147178095
A1: 883598583001102527733435593339761342580914
A2: -2028992567682389466010511292053996
A3: -2093021702063113798100666
A4: 831165963415509
A5: 68400
skew 1743820123.59, size 2.088e-019, alpha -8.380, combined = 6.415e-015 rroots = 5
[/code][/QUOTE]
I tried to improve this poly --> no luck, sorry.

C197 polys
 

I guess there is no need to post polys with the E below 7.5e-15, right? We have three so far that are above 7.5e-15.
Who is test-sieving for C197? Approximately when?
If you suddenly want to test-sieve more than three polys, please let us know. I have some 7.1s-7.4s that are not posted here.
Also, I can try spinning anything better than 6.7 into shape.

Sorry, I had posted my highest score to date - a rather anemic 6.415. It was for pride’s sake. Won’t publish anything < 7.00 going forward.

Approaching 250k for c5. Slow going but better speed than I was getting previously. But to cover my reserved range up to 500k will take several more weeks. Planning to plow through unless someone suggests otherwise. I’m willing to complete it, I just ask you delay proposing this job to NFS@Home until I finish my range.

@Sean
Save your cycles for another time. I believe we are at or near record levels for this size number.
Let's wrap this up, put a bow on it and call it a winner.

What's next on the chopping block? I thought I may be out of town so I didn't commit too much last time around, but I'm ready now.

I guess the real question is, Can we shoe horn this into a 15e siever?
That may dictate whether we have a "good enough" poly.

There's no doubt we can do this with 15e/33. I think C200 can be done with nfs@home 15e, though the matrix will likely be bigger than if done with 16e.

GNFS-200 is the spot where solving the matrix is the bigger hurdle than getting the sieving done. Aliquot-276 at C205 can be done with 15e, but the matrix will be gross (and worse than 16). I'm willing to donate a thread-year (that is, two months on 6-core i7) to a GNFS200+ matrix for the sake of pushing our tools, but that won't be enough to finish such a beast.

So, unless the owner of new shiny iron wishes to offer his services for the C205, I think we should poly-select Max's C200 next. I am more interested in the C205 from Aliq-276, but until and unless someone who matters agrees to postprocess it it's folly.

My GPU work completes tonight at 1M; I've run CADO from 500k to 750k with no poly within 10% of the 6.9 I posted a week or so ago. Assuming my last runs with CADO and msieve-GPU produce nothing worth posting to Max, I'll test-sieve the three 7.5+ polys Thursday evening.

4788c197 candidate
 

Dear Max:
Please polish. Msieve-generated.
[code]# norm 3.102524e-19 alpha -6.943160 e 7.217e-15 rroots 3
skew: 152039729.27
c0: 2931130217185327116601317015565420773934927200
c1: -918193698486396137048328916808242683510
c2: 46768211205451464797643011244055
c3: 40873832936202201931322
c4: 1577994290944152
c5: 991728
Y0: -116079600316758606974465208257186926517
Y1: 13552554441652526533[/code]

Starting on the C205 from Aliquot 276 at 1M on msieve. Stage1norm of 1e30 still has 11 pieces available!

I don't mind switching to Max's C200 if there is consensus that nobody wants to solve the C205 matrix.

[QUOTE=RichD;485102]@Sean
Save your cycles for another time. I believe we are at or near record levels for this size number.
Let's wrap this up, put a bow on it and call it a winner.
[/QUOTE]

Agreed. Characterizing 1 to N in poly searching is less important here than “good enough to sieve”. I’ll stop my search later when I get home, followed by -npr. Just in case.

As to the next poly search, C205 seems a bridge too far with 15e. So we either search the C200, which will be a new 15e record GNFS job, or we ask Greg if he’s willing to take on the C205 with 16. Either way we go it’s a BIG job.

I vote for the C200. I will reserve the range c5 < 100,000 to start regardless of which composite we tackle.

Forgetful moron here, what's the size of a GNFS-205 matrix? North or south of 32 GiB?