@VBCurtis
Or better still, you can pass the 32 -nps hits too. The 1.527 poly originated from a way higher initial value:
[code]
94500
-876677678258570
3248735003668689402094886
17715687891854833674272716
-34989519537547452750841045053460455
-52524702699552000601863647131972706
219268809479546783231
-18033060964990831683731419600754121
-2.06
1.141099e+25
[/code]

C177_134_73 polys
 

After a deeper CADO rootopt:
[code]
Y0: -18032640470816922518059532647913926
Y1: 219268809479546783231
c0: 4924527953923931830381349068592879715841680
c1: 1645804789835045583516186874489712573
c2: -316244963722480336858975723725
c3: -4218030226452648713822
c4: 176644176023580
c5: 567000
skew: 40557694.09448
# lognorm 56.53, E 47.83, alpha -8.71 (proj -2.82), 5 real roots
# MurphyE = 1.44106650e-13
[/code][code]
Y0: -18032640494955787216043878920248254
Y1: 219268809479546783231
c0: -14614039841358511370215859439327691667111580
c1: -1715279919023355582851415801510409139
c2: 314839062858293527144687833597
c3: 4295747125837875733982
c4: -176332076543580
c5: -567000
skew: 42119242.59061
# lognorm 56.46, E 47.77, alpha -8.69 (proj -2.82), 5 real roots
# MurphyE = 1.42713091e-13
[/code]

C177 msieve poly
 

Msieve's version of the top poly above:
[code]
Y0: -18032640539903261933637214921204482
Y1: 219268809479546783231
c0: 4374713486561757305876967762693527985439884
c1: 1843808905393213184988954160709624837
c2: -312152924934050957812565513829
c3: -4440092710809520762142
c4: 175750935563580
c5: 567000
skew: 40574289.11
# size 3.188e-017, alpha -8.706, combined = 1.441e-013 rroots = 5
[/code]

Max-
Test-sieving is pretty tedious manual labor, and if I were Sean I wouldn't bother with the hordes of polys you post; I'd test the top 3 or 4 against each other and get on with the job. Creating another 1.41 or 1.42 from polishing my 1.38 doesn't help the job, but might guilt him into testing it because we (well, you) put time into it.

That said, I'll check tomorrow to see if I didn't already erase the raw -nps hits; if not, I can post them here directly for you.

[QUOTE=Max0526;482664]@VBCurtis
Or better still, you can pass the 32 -nps hits too. The 1.527 poly originated from a way higher initial value:
[code]
1.141099e+25
[/code][/QUOTE]
Pretty sure that value is from stage 1, where the values I referred to were from stage 2 (about 1/100th the value).
Attached is the list of e22 hits from -nps.

[QUOTE=swellman;482052]Can anyone help me with a poly search for C177_134_73, a xyyx stub remaining after yoyo@Home found a factor? I’ve started on the range up to 1M.

For reference, the record e-score for a C177 is held by Max at e=1.448e-13.

[code]n: 180189746142952844436124262037686342047932954306939405380401568534712179225777244095963902399806570252212701396365362103075796904850851875771907195646912199042073818244500029371[/code]

Thanks.[/QUOTE]

I’ve just finished my last range on this composite. Nothing above 1.2X. Declaring victory and moving on. From here I’ll test sieve all polys > 1.5 and request the job for the NFS@Home queue. Again my sincere thanks to all of you for moving this one across the goal line.

Max - I didn’t save any .ms or later files. I never found anything promising enough that any amount of polishing by you was going to generate a record. I think we’ve put enough effort into this C177.

[QUOTE=VBCurtis;482650]I decided to delay a round of GPU-ECM in favor of poly select on 13*2^914-1. Reserving 0-1M.
Here's the candidate:
[code]21738648296306845572021049564329346839114956866953308223382471881448692536700443342760950147619499684163176459093243365690755842713995905470870499048667020929598436481828027622759[/code]

I'm using stage1norm=1.1e26, which is default / 9.[/QUOTE]

I’ll begin on the range 1-2M Monday night, assuming it’s available.

[QUOTE=VBCurtis;482650]I decided to delay a round of GPU-ECM in favor of poly select on 13*2^914-1. Reserving 0-1M.
Here's the candidate:
[code]21738648296306845572021049564329346839114956866953308223382471881448692536700443342760950147619499684163176459093243365690755842713995905470870499048667020929598436481828027622759[/code]

I'm using stage1norm=1.1e26, which is default / 9.[/QUOTE]

I'll start at 5-6M shortly.

C179 baseline
 

It would be nice to see a first baseline for C179 around 1.0e-13. Anyone?
I started a CADO run for it with non-standard parameters. I'll let it brew for a day and then will let you know.

Yea, my first root-opt run of hits from 0-250k gave me a 1.006e-13. Your intuitive estimate of "decent" is spot-on. I had 9.8e-14 and 9.7, so the 1.00 isn't much of an outlier.

C179
 

My early find is only 9.10e-14. Continuing to 7M.