C157 poly
 

This is the best one I found using gpu-Msieve from 100K-2000K. Maybe Max can spin it.
[CODE]n: 1654098853492103346196376991720302913598185971995257205318506082888090635219769665780186120626612175321809381513598017302609576486754505478164972380721171343
skew: 5051266.50
# size 3.239e-15, alpha -8.487, combined = 2.250e-12 rroots = 5
Y0: -1088781481752464879679018932184
Y1: 1603175637244477
c0: 274709378060763926117863209734254003555
c1: 906390434633835309135951338630819
c2: 74689696335285598434898491
c3: -115788873860120570579
c4: -1230131772166
c5: 1081080[/CODE]

polys, polys
 

RichD,
Thank You for poly. Meanwhile I was pressing my poor Yafu, and got 'promising' e= 2.244e-012 rroots 3. I'll push some more and we'll see.
Anyway, many thanks RichD !


cubaq

Source of your number?
 

@cubaq: How did you get that [URL="http://www.factordb.com/index.php?id=1100000001431822569"]CF160[/URL]? I can't seem to find a formula for it.

Source
 

It is HP10(1455). Regards, cubaq

C189 from AS 3366:i2206
 

[CODE] 171065344393143145598685691004020457412949305674191856490470856856353467726774164074336525717740050483725614204311545373938206064857869944567319589822085897560103957504493890195049294967729
[/CODE]

It has withstood ECM up to 90% of t60, making it ready for GNFS. A poly is needed. Any search help is appreciated.

If using msieve-GPU, suggest searching in the range c5 > 25M. A sextic is unnecessary.

As a point of reference, the record e-score for a C189 is 2.078e-14.

All my machines are fully tasked now, but I will be able to contribute to this search in a few days.

I'll run a CADO search using my usual settings. Mine are different enough that someone else could use the default settings if they'd like to contribute but don't have a suitable GPU for msieve poly searching.

Should take 2-3 days.

I've been trying to contribute but so far the poly select is what I understand the least of the whole factoring ordeal. I ended up running 8 msieves, splitting the default msieve range to 8 parts and running something like [CODE]./msieve -v -s msieve0 -np polydegree=5 poly_deadline=0 min_coeff=0 max_coeff=107509504[/CODE].

Is that a good way to contribute? I thought msieve will be selecting the leading coefficient randomly from assigned range, but to be honest it seems kinda sequential to me.

Anyway, the best poly I was able to find so far is this:

[CODE]
# norm 1.207054e-18 alpha -8.735874 e 1.657e-14 rroots 5
skew: 60255863.61
c0: 31381030369826867124034704635123263015800993960
c1: 4692867254516052130833152910480426027252
c2: -264647247134491241977409863094978
c3: -2527666462360009909489429
c4: 72673440232832010
c5: 322654800
Y0: -880815154646513541646481323093299959
Y1: 133978078624087050451
[/CODE]

Thanks for any hints and/or recommended reading on how to better contribute :)

msieve -h is instructive.

I’m no master of msieve, but if you specify the search range in msieve it does work the range sequentially.

Looks as though you are using Linux, do you have a GPU?

[QUOTE=swellman;535548]msieve -h is instructive.

I’m no master of msieve, but if you specify the search range in msieve it does work the range sequentially.

Looks as though you are using Linux, do you have a GPU?[/QUOTE]

msieve -h is pretty instructive about the specific details of running it, but not really when it comes to the big picture - basically what goes into making it work effectively, and what's the best way to split work.

I do have GPUs, but unfortunately all are AMD, so no CUDA :(

C189 poly
 

I'll start at 32M with msieve-GPU.

[QUOTE=jagotu;535549]msieve -h is pretty instructive about the specific details of running it, but not really when it comes to the big picture - basically what goes into making it work effectively, and what's the best way to split work.

I do have GPUs, but unfortunately all are AMD, so no CUDA :([/QUOTE]

There’s this [url]https://www.mersenneforum.org/showthread.php?t=16933[/url]

Personally I don’t have much experience using msieve-cpu for poly searching, so I can’t be of much help. Sorry!