Team sieve #7: c146 from 4788:2411
 

[COLOR=black]This is the team GNFS thread for the c146.[/COLOR]

Postprocessing will be done by [B]jrk[/B]

[B]Use siever 14e.[/B]

[B]Poly:[/B]
[code]n: 26189038648693542347544128379203981085928807133100545352808625328304272178273019151767946445367950374936152823381598061806704210499765820991870233
c0: 854935704823969678446428150388307472
c1: 2628352529802281674541428166656
c2: -2269870450124465525853056
c3: -7665339912013281796
c4: 2647460484669
c5: 544320
Y0: -8638748650791516848363247201
Y1: 45290154778406353
skew: 1232509.71
rlim: 22500000
alim: 22500000
lpbr: 29
lpba: 29
mfbr: 58
mfba: 58
rlambda: 2.5
alambda: 2.5[/code][B]Reservations:[/B]
[code] [B]Who[/B] [B]Range[/B]
* jrk 8.0-9.0M (done, 3266215 rels)

* Mini-Geek 10.0-10.5M (done, 1646379 rels)
* jrk 10.5-11.0M (done, 1663945 rels)

* bsquared 12.0-22.0M (done, 33228433 rels)
* Andi47 22.0-23.0M (partially done, 2737335 rels)
* schickel 23.0-25.0M (done, 4803871 rels)
* Mini-Geek 25.0-25.2M (done, 630501 rels)
* fivemack 26.0-30.0M (partially done, 4241365 rels)[/code][B][COLOR=#0000ff]As always, please check downthread for reservations not transferred up here.[/COLOR][/B]

[B]Estimated rels needed: 50M (first filtering run: 43M)[/B]
[B]Total rels received: 52218044[/B][B] (120.4% of 43M, 104.4% of 50M)


[COLOR=Red]No more reservations needed. Please upload what is finished.[/COLOR]
[/B]

Well, just in case, I've got a flaky system that's not good for anything else, so here's a possible poly for a team job:[code]name: a4788
n: 26189038648693542347544128379203981085928807133100545352808625328304272178273019151767946445367950374936152823381598061806704210499765820991870233
skew: 455561.83
# norm 1.50e+020
c5: 699120
c4: 2623176925074
c3: -392626068983461239
c2: -45916984284943238780014
c1: -36317788167584580159315012948
c0: -4063458674883465798222978634153835
# alpha -5.61
Y1: 57526241764323101
Y0: -8216962111655199976191265626
# Murphy_E 8.06e-012
# M 23883647179055675178405248141975475617370696819412699780867508996517067125838251419116094320704530358065037152442760348269226398833743271756959811
type: gnfs[/code]

[quote=schickel;177036]Well, just in case, I've got a flaky system that's not good for anything else, so here's a possible poly for a team job:[code]name: a4788
n: 26189038648693542347544128379203981085928807133100545352808625328304272178273019151767946445367950374936152823381598061806704210499765820991870233
skew: 455561.83
# norm 1.50e+020
c5: 699120
c4: 2623176925074
c3: -392626068983461239
c2: -45916984284943238780014
c1: -36317788167584580159315012948
c0: -4063458674883465798222978634153835
# alpha -5.61
Y1: 57526241764323101
Y0: -8216962111655199976191265626
# Murphy_E 8.06e-012
# M 23883647179055675178405248141975475617370696819412699780867508996517067125838251419116094320704530358065037152442760348269226398833743271756959811
type: gnfs[/code][/quote]

Shall we turn this into a poly search thread? (Remember the poly search details don't really belong in the sieve thread.)

Here's another poly, found with msieve 1.42.
[code]n: 26189038648693542347544128379203981085928807133100545352808625328304272178273019151767946445367950374936152823381598061806704210499765820991870233
# norm 3.088359e-14 alpha -4.726567 e 8.244e-12
skew: 224520.44
c0: -330054480572167115879510887000400
c1: 1704252146819274174812063226
c2: 41778842653281650261625
c3: -160170359887451338
c4: -2337770586248
c5: 929460
Y0: -7762093262195482668875676843
Y1: 38587683749133677[/code]

[QUOTE=10metreh;177058]Shall [B]we[/B] turn this into a poly search thread? [/QUOTE]We? You're always the first to create a new tread but you haven't seem to contributed a single relation to any of the previous team efforts
[QUOTE=10metreh;177058](Remember the poly search details don't really belong in the sieve thread.)[/QUOTE]Title of this tread is [I](Possible) Team GNFS for 4788:2411[/I] so poly search and sieving both fit fine.

[QUOTE=schickel;177036]# Murphy_E 8.06e-012[/QUOTE][QUOTE=jrk;177635]# norm 3.088359e-14 alpha -4.726567 e 8.244e-12[/QUOTE]That's a pretty good margin for the msieve poly. What's an approximate relation count and anticipated run time? I've got some long-term jobs lined up for my NFS rig and I want to know if I should stall them to put some effort into this.....

Here's another poly:
[code]n: 26189038648693542347544128379203981085928807133100545352808625328304272178273019151767946445367950374936152823381598061806704210499765820991870233
# norm 3.271358e-14 alpha -7.032774 e 8.217e-12
skew: 1232509.71
c0: 854935704823969678446428150388307472
c1: 2628352529802281674541428166656
c2: -2269870450124465525853056
c3: -7665339912013281796
c4: 2647460484669
c5: 544320
Y0: -8638748650791516848363247201
Y1: 45290154778406353[/code]

It has slightly lower 'e' value than the earlier poly but look at alpha! Here's some tests.

8.06e-12 poly:
total yield: 28573, q=22510043 (0.04371 sec/rel)

8.244e-12 poly:
total yield: 27966, q=22510043 (0.04395 sec/rel)

8.217e-12 poly:
total yield: 30815, q=22510043 [COLOR="Red"](0.04011 sec/rel)[/COLOR]

Tests were done with siever 14e and the params:
[code]rlim: 22500000
alim: 22500000
lpbr: 29
lpba: 29
mfbr: 58
mfba: 58
rlambda: 2.5
alambda: 2.5[/code]

[QUOTE=jrk;177731]Here's some tests.

8.06e-12 poly:
total yield: 28573, q=22510043 (0.04371 sec/rel)

8.244e-12 poly:
total yield: 27966, q=22510043 (0.04395 sec/rel)

8.217e-12 poly:
total yield: 30815, q=22510043 [COLOR="Red"](0.04011 sec/rel)[/COLOR][/QUOTE]Nice looking result! Should we call the ECM adequate, the poly good enough, and give it a whirl?

[quote=schickel;177732]Nice looking result! Should we call the ECM adequate, the poly good enough, and give it a whirl?[/quote]

:bump:

What programs/files/commands would one do to find relations for this number? Is it right to put something like:[code]n: 26189038648693542347544128379203981085928807133100545352808625328304272178273019151767946445367950374936152823381598061806704210499765820991870233
m:
c0: 854935704823969678446428150388307472
c1: 2628352529802281674541428166656
c2: -2269870450124465525853056
c3: -7665339912013281796
c4: 2647460484669
c5: 544320
Y0: -8638748650791516848363247201
Y1: 45290154778406353
skew: 1232509.71
rlim: 16800000
alim: 8399999
lpbr: 29
lpba: 29
mfbr: 58
mfba: 58
rlambda: 2.6
alambda: 2.6

q0: 10001000
qintsize: 4000
#q1: 10005000

rlim: 22500000
alim: 22500000
lpbr: 29
lpba: 29
mfbr: 58
mfba: 58
rlambda: 2.5
alambda: 2.5[/code]in a file, say it's named test.job, then run a command like this?[code]gnfs-lasieve4I14e test.job -a[/code]Or is something there wrong? It seems to run correctly, but I just want to check if I'm doing anything wrong, or if anything there is unnecessary.

Create a poly file with the following in it.[code]n: 26189038648693542347544128379203981085928807133100545352808625328304272178273019151767946445367950374936152823381598061806704210499765820991870233
c0: 854935704823969678446428150388307472
c1: 2628352529802281674541428166656
c2: -2269870450124465525853056
c3: -7665339912013281796
c4: 2647460484669
c5: 544320
Y0: -8638748650791516848363247201
Y1: 45290154778406353
skew: 1232509.71
rlim: 22500000
alim: 22500000
lpbr: 29
lpba: 29
mfbr: 58
mfba: 58
rlambda: 2.5
alambda: 2.5[/code]Run something like[CODE]gnfs-lasieve4I14e -o 25-26.out -a 4788.poly -f 25000000 -c 1000000[/CODE] where [CODE]-o Output file for relations
-a Sieving the algebraic side
-f Special Q to start sieving
-c Range to sieve[/CODE]
If you're sieving within the factor base it could be worth to break the range in several ranges since the siever automatically lowers alim to the starting value of your range.