Poly select and planning for 2,2210M
 

ECM of 2,2210M to t65 is 98% complete. Should be fully finished by 1 Sep.

With that in mind, I am reserving c6 < 1M using msieveGPU.

Where does one go to find the size of, well, actually the number itself?

[QUOTE=RichD;524444]Where does one go to find the size of, well, actually the number itself?[/QUOTE]

DukeBG posted a list [url=https://www.mersenneforum.org/showpost.php?p=513436&postcount=42]here[/url] over in the Contributing to the Cunningham Project.

It also in factordb, search on 2^2210+1.

[CODE]1035494967981608996094968430385789545942273148368197179174157979458916926996249361835599034841457568721713517315035171458834084281747156675749209765447133072804654265940216339728917289743563475602882258734938561
[/CODE]

Eta: [url]http://homes.cerias.purdue.edu/~ssw/cun/[/url] for the original source.

C211
 

Starting on this C211 at 8M using msieve-GPU.

Eta: sextic poly

The CADO team sieve will wrap up in a few days; I'll take a shot at CADO poly select at that time, likely Thursday or Friday. I think degree 6 is a CADO strength, so I'll search deg 6 first; if I'm right and the scores are way better than msieve deg 6, we should move our GPU resources to deg 5.

We should have good data by next Sunday on both msieve and CADO for deg 6.

[QUOTE=VBCurtis;524457]The CADO team sieve will wrap up in a few days; I'll take a shot at CADO poly select at that time, likely Thursday or Friday. I think degree 6 is a CADO strength, so I'll search deg 6 first; if I'm right and the scores are way better than msieve deg 6, we should move our GPU resources to deg 5.

We should have good data by next Sunday on both msieve and CADO for deg 6.[/QUOTE]

Agreed, at least with my old hardware. I couldn’t get a stable run going with deg=6 using msieveGPU.

Crying uncle and moving poly search to deg=5 for c5 < 1M.

[QUOTE=swellman;524459]Agreed, at least with my old hardware. I couldn’t get a stable run going with deg=6 using msieveGPU.

Crying uncle and moving poly search to deg=5 for c5 < 1M.[/QUOTE]

Will the forum do the sieving?

[QUOTE=RichD;524450]Starting on this C211 at 8M using msieve-GPU.

Eta: sextic poly[/QUOTE]

I ran a small test region last night (8-8.01M). Everything appeared normal. Except when I ran -nps (as a separate invocation) the following appeared many times in the screen output.
[CODE]line minimize failed[/CODE]
Additionally, the -nps phase took an extraordinarily long time to perform.

Giving the above, I will switch to a quintic search beginning at 8M.

[QUOTE=R.D. Silverman;524461]Will the forum do the sieving?[/QUOTE]

??

Or will NFS@Home do it? Greg has not listed any numbers as queued beyond
2,1076+ [currently sieving].

Why are you so demanding about a decision that (1) hasn't been made yet, and (2) is a few months away? By the time we have a poly, some of the 2330L sievers may have a sense of whether they'd like to do another team project, or wait until 2020.
Please, relax.

[QUOTE=VBCurtis;524723]Why are you so demanding about a decision that (1) hasn't been made yet, and (2) is a few months away? By the time we have a poly, some of the 2330L sievers may have a sense of whether they'd like to do another team project, or wait until 2020.
Please, relax.[/QUOTE]

Demanding??? I asked an innocuous question! Why are you so accusatory?

You say that it is a few months away, yet 2,2330L will finish sieving in a couple of days.

Greg is going to do 2,2330M, so the obvious conclusion is that the forum does
not plan to do any sieving for a 'few months'.

Degree-5
 

Early baseline for deg-5:
[CODE]N: 1035494967981608996094968430385789545942273148368197179174157979458916926996249361835599034841457568721713517315035171458834084281747156675749209765447133072804654265940216339728917289743563475602882258734938561
R0: -41819261283625699438470122761789489631579
R1: 167570775295552894171
A0: -12066997670859555604494928929174421318825319839538448
A1: 17688142541021209819902982567060035886962676
A2: 182074772809406608085014952527024304
A3: -9924817789205732407937439
A4: -140854355230416738
A5: 8095920
skew 1226175733.65, size 6.974e-21, alpha -8.014, combined = 7.517e-16 rroots = 5[/CODE]

[QUOTE=R.D. Silverman;524733]Demanding??? I asked an innocuous question! Why are you so accusatory?[/QUOTE]

I consider quoting yourself to re-ask the same question demanding. Nobody answered you the first time because nobody has an answer yet; when you quote yourself to ask it again I feel like someone has to respond to keep you from doing it over and over.

You're welcome to take on some poly select or test-sieving to reduce the load on some of the other volunteers around here. If you're in a hurry, feel free to add your labor. CADO does cpu-based poly select as effectively as msieve-gpu, and test-sieving is an area your expertise surely would be useful in.

[QUOTE=VBCurtis;524764]I consider quoting yourself to re-ask the same question demanding.
[/QUOTE]

And I consider making personal comments in a purely technical discussion to be obnoxious. I'd make a personal comment now, but I refuse to lower myself to your level.

(1) I am already running ECM on 2^(4k) + 1. This is how I contribute.

(2) I am not allowed to install outside software on machines at work without a
long and involved process to get special permission. I would need to justify it by
giving a business reason for doing it. We are behind a very strict/tight firewall.
I don't participate in NFS@Home for the same reason(s). Remote work
assignment software can't get messages through our firewall. I can't use other
people's desktop computers. I have a grand total of two machines available at work:
one in a public conference room along with my personal laptop; 10 total cores.

(3) Does CADO even run under Windows? The only Unix machines available here are all reserved for project work only.

C211 poly
 

[QUOTE=RichD;524760]Early baseline for deg-5:
[CODE]N: 1035494967981608996094968430385789545942273148368197179174157979458916926996249361835599034841457568721713517315035171458834084281747156675749209765447133072804654265940216339728917289743563475602882258734938561
R0: -41819261283625699438470122761789489631579
R1: 167570775295552894171
A0: -12066997670859555604494928929174421318825319839538448
A1: 17688142541021209819902982567060035886962676
A2: 182074772809406608085014952527024304
A3: -9924817789205732407937439
A4: -140854355230416738
A5: 8095920
skew 1226175733.65, size 6.974e-21, alpha -8.014, combined = 7.517e-16 rroots = 5[/CODE][/QUOTE]
Spins up:[code]Y0: -41819261283625099862863001160529818450055
Y1: 335141550591105788342
c0: -1500172275302201453063446822237312999031758856151588
c1: 4747669662815572167225051109909427651786537
c2: 90978711285948827879048497611864274
c3: -11939713639659710229728127
c4: -281419034881028676
c5: 32383680
skew: 613495208.36540
# size 6.994e-21, alpha -8.015, combined = 7.570e-16 rroots = 5[/code]
Also, I'll try to CADO both today to get better results.

Can the CADO server be used for poly stage? If not anyone can guide me how to manually run CADO poly search or is it better to use msieve. TIA.

[QUOTE=pinhodecarlos;524928]Can the CADO server be used for poly stage? If not anyone can guide me how to manually run CADO poly search or is it better to use msieve. TIA.[/QUOTE]

Once the filtering is complete on 2330L and the server isn't hammering swap, I can set and run a job for poly select. When I get it set up, I'll post the port number on this thread.

Good idea, sir!

[QUOTE=pinhodecarlos;524928]Can the CADO server be used for poly stage? If not anyone can guide me how to manually run CADO poly search or is it better to use msieve. TIA.[/QUOTE]
To use CADO for poly search only, you can add the switch "tasks.sieve.run=false" to your command line.

This will break out of the python script. The poly file will be in the temporary directory that CADO used. If you plan to use the poly elsewhere, you may need to edit it into the "elsewhere" format.

I actually have a hybrid script that uses CADO for poly search and sieving, but uses msieve for the Linear Algebra and later. I use "tasks.filter.run=false" to stop it after sieving.


Edit: Missed Curtis' post...

2 more polys
 

[CODE]
# norm 8.135856e-21 alpha -8.064852 e 7.456e-16 rroots 5
skew: 16271269829.01
c0: 4986454635504416157062616374417746965486523246723877600
c1: 2545022977013689450868163763307895285382555828
c2: -436790752796429147543014010580044718
c3: -83949784571166440787562654
c4: 1870886591455177
c5: 27768
Y0: -130112996392869801826534677038649745334961
Y1: 14470613719940205641



# norm 8.219219e-21 alpha -8.375061 e 7.477e-16 rroots 5
skew: 18227704190.16
c0: -1777210165474047745053322786931419958443668248341202976
c1: 4689235616783271467571583242233994782087794914
c2: -140166693678499697547849739060353969
c3: -140803141828585815106088581
c4: 281644157242757
c5: 31080
Y0: -127213557144635062895443321984084673242321
Y1: 41407283364089225239
[/CODE]

I'm running polyselect with the similar parameters as for 2,2330L.

[QUOTE=VBCurtis;524944]Once the filtering is complete on 2330L and the server isn't hammering swap, I can set and run a job for poly select. When I get it set up, I'll post the port number on this thread.

Good idea, sir![/QUOTE]

While I await more RAM, I've started a CADO server for polyselect for this number.
Point your client to the usual address as used on the 2330L job, with port number changed to 44400. The job should take about 8M thread-seconds, so just 2-3 days.
EDIT: reserving degree 6, admin 1.05M, admax 20M. For those curious: nq=6^6, incr 4620, P=8 million.

C211 polys
 

[QUOTE=swellman;525032][CODE]
# norm 8.135856e-21 alpha -8.064852 e 7.456e-16 rroots 5
skew: 16271269829.01
c0: 4986454635504416157062616374417746965486523246723877600
c1: 2545022977013689450868163763307895285382555828
c2: -436790752796429147543014010580044718
c3: -83949784571166440787562654
c4: 1870886591455177
c5: 27768
Y0: -130112996392869801826534677038649745334961
Y1: 14470613719940205641



# norm 8.219219e-21 alpha -8.375061 e 7.477e-16 rroots 5
skew: 18227704190.16
c0: -1777210165474047745053322786931419958443668248341202976
c1: 4689235616783271467571583242233994782087794914
c2: -140166693678499697547849739060353969
c3: -140803141828585815106088581
c4: 281644157242757
c5: 31080
Y0: -127213557144635062895443321984084673242321
Y1: 41407283364089225239
[/CODE][/QUOTE]
None of them spins up, sorry.

[QUOTE=VBCurtis;525274]While I await more RAM, I've started a CADO server for polyselect for this number.
Point your client to the usual address as used on the 2330L job, with port number changed to 44400. The job should take about 8M thread-seconds, so just 2-3 days.
EDIT: reserving degree 6, admin 1.05M, admax 20M. For those curious: nq=6^6, incr 4620, P=8 million.[/QUOTE]
[code]
ERROR:root:Download failed, URL error: <urlopen error [Errno 111] Connection refused>
ERROR:root:Waiting 10.0 seconds before retrying
[/code]:sad:

Bummer! I copied the network settings from 2330L params file, so I figured it would work without issue. Maybe I did something dumb like mistype the port. If I have time Saturday I'll see if I can figure out the problem; won't have time to check before then. Then again, the job will finish late Saturday on its own.

I'll be running a deg 5 search with CADO later (unless Vebis beats me to it), so we'll have another chance.

Is the new port available from outside your local network?

There is no local network; it's assigned an IP address via DHCP from my university.

[QUOTE=EdH;525300][code]
ERROR:root:Download failed, URL error: <urlopen error [Errno 111] Connection refused>
ERROR:root:Waiting 10.0 seconds before retrying
[/code]:sad:[/QUOTE]

I found the problem; I ran CADO from home, my connecton to the campus machine died, so CADO stopped responding.
Unfortunately, I learned Friday that my office is scheduled for destruction Tuesday, so I went in last night and unplugged all the silicon. My department is as surprised by this turn of events as I am, so I and my machines are homeless for a week or two until they find some office space for me.

On the bright side, RAM arrived last night.

[CODE]# norm 8.388914e-21 alpha -9.216995 e 7.639e-16 rroots 5
skew: 20979898852.98
c0: 27649131585183391812916066541481716806536590015577581424
c1: 27330385748632515681889738973504668871302682226
c2: -2155465644405759903230110401342981943
c3: -213599886258400208384412088
c4: 4879065781035618
c5: 121716
Y0: -96818882190388663272841084874018768984485
Y1: 74413548803525738089
[/CODE]

That may be a record for highest skew on a usable poly in history. 20 billion!

Recall that GGNFS does not run with skew above Q; if you change skew to 400M or 500M, I bet the score is pretty lousy. Then again, Max might be able to spin it such that skew drops by a factor of 4 or 8 while score remains similar, so there's some hope.

Skews like this are why tiny c5s aren't usually searched for poly select above c200.

[QUOTE=VBCurtis;525752]That may be a record for highest skew on a usable poly in history. 20 billion!

Recall that GGNFS does not run with skew above Q; if you change skew to 400M or 500M, I bet the score is pretty lousy. Then again, Max might be able to spin it such that skew drops by a factor of 4 or 8 while score remains similar, so there's some hope.

Skews like this are why tiny c5s aren't usually searched for poly select above c200.[/QUOTE]

I can’t even get cownoise to spit out an answer for optimal skew! :max: Perhaps Max can spin it down. But let’s face it, the best quintic e-score is likely to have at least a 9-handle.

The search goes on.

I finally finished my deg 6 CADO run:
[code]skew: 402972.111
c0: 2118696065289163977962187507742615436240832
c1: -45195693963724945835426077433010009156
c2: -298923418394166123716233260770564
c3: 328843002406215196716601281
c4: 2641231812968768558129
c5: -1065578287083828
c6: -276312960
Y0: -8247746467927728998793444647326297
Y1: 69974668288047521820527
# MurphyE (Bf=1.718e+10,Bg=1.718e+10,area=1.288e+16) = 1.17e-08[/code]
Cownoise says skew 586407.73298 score 1.21942919e-15
Prior records for deg 6: 210 digits 1.49e-15, 212 digits 9.42e-16
This composite has first three digits 103, so the poly score should be a bit closer to 210 digits than 212. I'd like a 1.30 in deg 6 to call the search complete, or 1.10 in deg 5.
I'm running CADO on 0-1.05M in deg 6 next; by then I'll be back to 2330L matrix-solving.
Edit: this was ~7M thread-seconds of search.

[QUOTE=VBCurtis;525752]That may be a record for highest skew on a usable poly in history. 20 billion!

Recall that GGNFS does not run with skew above Q[/quote]

I think that's just not true; the yields you get are definitely lower for large skew, but it will run.

(sieving the demonstrated polynomial from 400M to 400M+100k with 16e and 33-bit large primes gives a yield of 40 relations)

[QUOTE=fivemack;525828]I think that's just not true; the yields you get are definitely lower for large skew, but it will run.

(sieving the demonstrated polynomial from 400M to 400M+100k with 16e and 33-bit large primes gives a yield of 40 relations)[/QUOTE]

Then we should start sieving as soon as possible! :grin:

[QUOTE=fivemack;525828]I think that's just not true; the yields you get are definitely lower for large skew, but it will run.

(sieving the demonstrated polynomial from 400M to 400M+100k with 16e and 33-bit large primes gives a yield of 40 relations)[/QUOTE]

My understanding is that GGNFS internally adjusts skew down to Q; I'll see if I can find the source of my [mis]understanding.

If you set skew to 410M, do you get the same 40 relations? A "no" would conclusively reject my claim.

C211 poly
 

[QUOTE=swellman;525750][CODE]# norm 8.388914e-21 alpha -9.216995 e 7.639e-16 rroots 5
skew: 20979898852.98
c0: 27649131585183391812916066541481716806536590015577581424
c1: 27330385748632515681889738973504668871302682226
c2: -2155465644405759903230110401342981943
c3: -213599886258400208384412088
c4: 4879065781035618
c5: 121716
Y0: -96818882190388663272841084874018768984485
Y1: 74413548803525738089
[/CODE][/QUOTE]
I can't spin it up, sorry. I can drop skew down to 10 mln but then the E score also drops:[code]R0: -96818882190389519247725813097586565418501
R1: 148827097607051476178
A0: 6833616701827777569778742549146341079870193298849419692
A1: 13689944665495682939372373982326074456184996569
A2: -2148090690147041132745084413722189879
A3: -427648439376739194153191792
A4: 19488261277504392
A5: 973728
skew: 10892841023.33
# size 6.258e-21, alpha -9.564, combined = 7.121e-16 rroots = 5[/code]

C211 poly
 

[QUOTE=Max0526;525848]I can drop skew down to 10 mln but then the E score also drops:[/QUOTE]
I meant 10 bln of course.

C211 polys
 

[QUOTE=VBCurtis;525807]I finally finished my deg 6 CADO run:
[code]skew: 402972.111
c0: 2118696065289163977962187507742615436240832
c1: -45195693963724945835426077433010009156
c2: -298923418394166123716233260770564
c3: 328843002406215196716601281
c4: 2641231812968768558129
c5: -1065578287083828
c6: -276312960
Y0: -8247746467927728998793444647326297
Y1: 69974668288047521820527
# MurphyE (Bf=1.718e+10,Bg=1.718e+10,area=1.288e+16) = 1.17e-08[/code]Cownoise says skew 586407.73298 score 1.21942919e-15
[/QUOTE]
Two close polys:[code]Y0: -8247744810367786591523747762682721
Y1: 139949336576095043641054
c0: -121697515694159644891681490270913604269342
c1: 3234923352759311823303330074168072691
c2: 133402768957865817059990225314786
c3: -573052357776445442366809569
c4: -5025398088308725392418
c5: 4419400381850832
c6: 2210503680
skew: 255103.69305
# lognorm 58.78, E 49.61, alpha -9.17 (proj -3.12), 6 real roots
# MurphyE = 1.17147226e-15[/code]and[code]Y0: -16495489966970231872306633493333038
Y1: 69974668288047521820527
c0: -58164215341232454269144736611727941171251680
c1: 358962284111646560756801536406561670778
c2: 1083864026708650513009029013236827
c3: -1096238294845069101359840050
c4: -2526340671503694979769
c5: 550374252942234
c6: 69078240
skew: 1115632.55307
lognorm 59.65, E 49.78, alpha -9.88 (proj -2.66), 4 real roots
MurphyE = 1.15731893e-15[/code]

[QUOTE=VBCurtis;525845]My understanding is that GGNFS internally adjusts skew down to Q; I'll see if I can find the source of my [mis]understanding.

If you set skew to 410M, do you get the same 40 relations? A "no" would conclusively reject my claim.[/QUOTE]

No, I get thirteen relations.

I think you are getting confused with the way that GGNFS 15e internally adjusts alim/rlim down to Q0 (IE if you do -a -f 20000000, it will sieve with alim=20000000 if the value in the poly file is larger than that)

[QUOTE=fivemack;525883]No, I get thirteen relations.

I think you are getting confused with the way that GGNFS 15e internally adjusts alim/rlim down to Q0 (IE if you do -a -f 20000000, it will sieve with alim=20000000 if the value in the poly file is larger than that)[/QUOTE]

Thank you for doing the footwork to confirm my misunderstanding. Your explanation is the best I have, until I get around to perusing some of the places where esoteric GGNFS discussions have taken place 'round here.

My second deg-6 run has finished:
[code]n: 1035494967981608996094968430385789545942273148368197179174157979458916926996249361835599034841457568721713517$
skew: 1483907.861
c0: -758486316282603838580261525697958736410558065
c1: 89244789800220344402617658427797448531
c2: 3372372111141991619249066738092247
c3: -1439537140116844521216509025
c4: -1528375860162091192646
c5: 125567209134150
c6: -25137000
Y0: -12078430430581541489961342383064362
Y1: 12185711440192546653435119
# MurphyE (Bf=1.718e+10,Bg=1.718e+10,area=1.288e+16) = 1.11e-08[/code]
This score is lower than the first one, so I didn't bother with cownoise.
Test-sieving on 2330M indicates that deg 5 is far superior to deg 6 on the polys we found for that project (~1.18 deg 5 vs ~1.38 deg 6 is about 20% faster for deg 5). So, I'm moving my CADO search to deg 5 next time I have some free cycles; I expect a 9e-16 deg 5 to be faster than either of my deg 6 polys here.

[QUOTE=VBCurtis;525891]My second deg-6 run has finished:
[code]n: 1035494967981608996094968430385789545942273148368197179174157979458916926996249361835599034841457568721713517$
skew: 1483907.861
c0: -758486316282603838580261525697958736410558065
c1: 89244789800220344402617658427797448531
c2: 3372372111141991619249066738092247
c3: -1439537140116844521216509025
c4: -1528375860162091192646
c5: 125567209134150
c6: -25137000
Y0: -12078430430581541489961342383064362
Y1: 12185711440192546653435119
# MurphyE (Bf=1.718e+10,Bg=1.718e+10,area=1.288e+16) = 1.11e-08[/code]
This score is lower than the first one, so I didn't bother with cownoise.
Test-sieving on 2330M indicates that deg 5 is far superior to deg 6 on the polys we found for that project (~1.18 deg 5 vs ~1.38 deg 6 is about 20% faster for deg 5). So, I'm moving my CADO search to deg 5 next time I have some free cycles; I expect a 9e-16 deg 5 to be faster than either of my deg 6 polys here.[/QUOTE]

I’m torn - I want to help with the poly search but being restricted to msieve-GPU gives little hope of ever producing anything useful for a job this big. I’ve been traveling but when I get home later today I will terminate poly searching unless I find that a fantastic result fell out.

Gimarel found quite a few good polys for 2330M using msieve (admittedly, with his secret-sauce using multiples of 120120 or 210210- I forget which- as leading coefficients).

I'd start somewhere like 50 million if I were using msieve, and if I had a functioning CUDA install I'd be using msieve in addition to CADO.

My best polys so far. I hope to get above 1e-15.

[CODE]# norm 1.191764e-20 alpha -8.739251 e 9.542823e-16 rroots 5
skew: 290147042.90
c0: -135776935562388704990549019644794533664814428164000
c1: 5937379427987227585128437919182971104650500
c2: 5804073041546668110449407917351361
c3: -333095482498862424229058609
c4: -135588904276392300
c5: 683242560
Y0: -19784296655912504351830419322570633016087
Y1: 144157419788673482041

# norm 1.142823e-20 alpha -9.668513 e 9.431845e-16 rroots 3
skew: 58035263.11
c0: -4986872452312652038145241813323771956740728170410
c1: -246617563086234831662512103167398893438877
c2: 26937900914384572962697443420308252
c3: -65711817531926823292081111
c4: -1328932861673785270
c5: 37383746400
Y0: -18093085778901249382350215393204523934312
Y1: 161147338183822935653

# norm 1.152128e-20 alpha -8.465413 e 9.360483e-16 rroots 3
skew: 262473092.38
c0: -242951724554279944917921601254250434171076371823856
c1: 208050745037498983680860166923829227243064
c2: 14449538634104684658097780043593177
c3: -75840018042149775269085489
c4: 169111997159595514
c5: 687566880
Y0: -19759347904801229668001852015718067377447
Y1: 217477571882419666331[/CODE]

Well sure enough, when I returned home from my travels msieve-GPU had not found anything useful. I’m pulling the plug on my search temporarily, but I will likely later take up the suggestion by VBCurtis to search a higher range, e.g. c5>50M. And I must play with CADO poly search - I don’t have much experience with CADO but it is very powerful.

I just fried another GPU. Mostly from years of mfaktc. I gave them the summer off during the heat wave except for poly select. It was just enough to push it over the thermal limits I guess. I will have to time-share my remaining GPU with my other projects.

Is there an ETA for when the poly select server is going online? Perhaps someone else could host it thinking there won't be a large database associated with this phase.

I don't have an office yet at work; I expect that all to be resolved next week. It's possible I could be ready to host a poly select server roughly 1 Oct.

C211 poly
 

[QUOTE=Gimarel;526182]My best polys so far. I hope to get above 1e-15.

[CODE]# norm 1.191764e-20 alpha -8.739251 e 9.542823e-16 rroots 5
skew: 290147042.90
c0: -135776935562388704990549019644794533664814428164000
c1: 5937379427987227585128437919182971104650500
c2: 5804073041546668110449407917351361
c3: -333095482498862424229058609
c4: -135588904276392300
c5: 683242560
Y0: -19784296655912504351830419322570633016087
Y1: 144157419788673482041[/CODE][/QUOTE]
CADO improves this one:[code]Y0: -19784296655915061095536529202785252214903
Y1: 144157419788673482041
c0: -89538570139368926892054378827202288469339026705664
c1: 8744292274934539098550063753936913974672508
c2: 23233172794522625773214205820840825
c3: -321327192335556636995253809
c4: -196178089265525100
c5: 683242560
skew: 324458439.70763
# lognorm 67.77, E 58.86, alpha -8.91 (proj -2.77), 5 real roots
# MurphyE = 9.70597736e-16[/code]

Getting closer to my target.
[CODE]# norm 1.249273e-20 alpha -8.131286 e 9.867108e-16 rroots 3
skew: 96765656.51
c0: -6550477416959067599467176809532399756087509534400
c1: 252085967604098579869322172871807209531115
c2: -1865154245477932682975653391422980
c3: -42991167929727768272789055
c4: 918101040566284672
c5: 2683961280
Y0: -17285675171411582397504491627973804395468
Y1: 213416879342632860047[/CODE]

Barely above 1e-15:
[CODE]# norm 1.263182e-20 alpha -8.492625 e 1.000734e-15 rroots 5
skew: 120662945.24
c0: -3512508476745188976022896771917660332755170974790
c1: 997551879795485025985410700001530170302053
c2: 5434045988116703824905078248026020
c3: -206964153300867056718667822
c4: -382944703267994740
c5: 4110506400
Y0: -16597570944776009500538980813685094232365
Y1: 43137299058249864401[/CODE]

C211 poly
 

[QUOTE=Gimarel;528044]Barely above 1e-15:
[CODE]# norm 1.263182e-20 alpha -8.492625 e 1.000734e-15 rroots 5
skew: 120662945.24
c0: -3512508476745188976022896771917660332755170974790
c1: 997551879795485025985410700001530170302053
c2: 5434045988116703824905078248026020
c3: -206964153300867056718667822
c4: -382944703267994740
c5: 4110506400
Y0: -16597570944776009500538980813685094232365
Y1: 43137299058249864401[/CODE][/QUOTE]
The first poly (e 9.867108e-16) doesn't spin up, the second one does a little bit:[code]Y0: -33195141889552001541644403492261820939589
Y1: 43137299058249864401
c0: -13241650300181670296760561121510365403225849387110
c1: 1999451640848996161765487470746063460221333
c2: 5308301912943369975557108576571957
c3: -103636228367897845788623251
c4: -94696369272722185
c5: 513813300
skew: 241509964.38
# size 1.044e-20, alpha -8.493, combined = 1.007e-15 rroots = 5[/code]

[QUOTE=Max0526;529013]The first poly (e 9.867108e-16) doesn't spin up, the second one does a little bit:[code]Y0: -33195141889552001541644403492261820939589
Y1: 43137299058249864401
c0: -13241650300181670296760561121510365403225849387110
c1: 1999451640848996161765487470746063460221333
c2: 5308301912943369975557108576571957
c3: -103636228367897845788623251
c4: -94696369272722185
c5: 513813300
skew: 241509964.38
# size 1.044e-20, alpha -8.493, combined = 1.007e-15 rroots = 5[/code][/QUOTE]

It appears that Greg will do this via SNFS

Now sieving 2,2210M at NFS@Home.