Team sieve #4: c138 from 4788:2383

[10metreh]

Poly selection was done by Lots of us

Post-processing will be done by mdettweiler

We have almost enough relations....check the end of the thread for any more sieving needed before starting any ranges!

See next message for relation upload instructions.

Poly:

n: 269461302253923115743046804544204780227535518397446478002103495733055094831911180910940594253877953143079412111134453043536380649289076203
Y0: -667075514232026401037903971
Y1:  1036651090752913
c0: -70301050564161042395853180825579264
c1:  760641393409756411433308787652
c2:  456862733931472272483861
c3: -400760058780476342
c4: -26481981572
c5:  2040
skew: 3879684.27
rlim: 9000000
alim: 9000000
lpbr: 28
lpba: 28
mfbr: 56
mfba: 56
rlambda: 2.5
alambda: 2.5

As always, please check downthread for prior reservations before starting any sieve jobs....

Reservations:

    Range       Who
* 2.0M- 3.0M   jrk (done, 1512988 rels)
* 3.0M- 3.1M   Andi47 (done, 161616 rels)
* 3.1M- 3.2M   Andi47 (done, 163806 rels)
* 3.2M- 5.0M   jrk (done, 2779746 rels)
* 5.0M- 5.1M   Andi47 (done, 174956 rels)
* 5.1M- 6.0M   jrk (done, 1608500 rels)
* 6.0M- 7.0M   smh (done, 1812201 rels)
* 7.0M- 7.5M   smh (done, 909063 rels)
* 7.5M- 7.7M   antiroach (done, 366699 rels)
* 7.7M- 9.0M   jrk (done, 2290470 rels)
* 9.0M- 9.2M   Andi47 (done, 357870 rels)
* 9.2M- 9.7M   smh (done, 886845 rels)
* 9.7M-11.2M   antiroach (done, 2574369 rels)
*11.2M-12.0M   jrk (done, 1294383 rels)
*12.0M-13.8M   schickel (done, 3873188 rels)
*13.8M-14.0M   schickel (done, 459586 rels)
*14.0M-14.6M   jrk (done, 895494 rels)
*14.6M-15.6M   antiroach (done, 1439214 rels)
*15.6M-16.2M   jrk (done, 843962 rels)
*16.2M-16.6M   antiroach (done, 561854 rels)
*16.6M-17.27M  antiroach (done, 1131562 rels)
*17.27M-17.6M  antiroach (done, 452772 rels)
*17.6M-18.1M   jrk (done, 673843 rels)    
*18.1M-18.6M   mdettweiler (done, 727736 rels)
 19.0M-20.0M   antiroach

* line sieve b=1-184 jrk (done, 363410 rels)

Total relations received: 28346983 (113.9% of 25M rels) .

[schickel]

Here are instructions on how to upload your relations:

Originally Posted by mdettweiler

Instructions as follows will show how to use it with the built-in "ftp" command line program that comes with all Windows and Linux systems; feel free to adapt them as necessary for use with other FTP programs.

---------------------------------------------------
-Open a command prompt/terminal window and type the following command:
ftp nplb-gb1.no-ip.org

-ftp will ask for a username. Type "aliquot" (capitals as shown, no quotes) and press Enter.

-ftp will ask for a password. Type "aqupload-4788" (capitals as shown, no quotes) and press Enter.

-ftp will now output the following:
230 Login successful.
ftp>

-Type "cd c138-relations" and press Enter.

-Type "binary" and press Enter.

-Now type the following command:
put relations.gz
...replacing "relations.gz" with the name (and, if necessary, pathname) of the compressed relations file you're uploading. Tip: navigate to the directory your relations file(s) are in *before* starting the FTP command, so you don't have to type long and clumsy file paths in your "put" commands for each file you upload.

-Wait until the file's finished uploading. Depending on the size of the file, it may take a while; please note that ftp doesn't show any progress or status info until the upload has completed, so it can appear to be "frozen" if you haven't used ftp before.

-Verify that your file's made it to the server by typing the command "ls" and seeing if your file shows up in the directory listing that results. If you see, it, you're all set!

-Type "quit" and press Enter. Close the command prompt/terminal window.
---------------------------------------------------

Some of you may have your own personal favorite GUI-based FTP program that you'd rather use than the command-line "ftp" application that I've used in my above instructions. In that case, simply tell your program to connect to server nplb-gb1.no-ip.org (port 21, the default) and log in as user aliquot with password aqupload-4788, and upload your relations files to the c138-relations directory.

Max

[jrk]

Was that a complete search with GGNFS?

Here's a nice one that popped out of msieve, searching around the higher than default leading coefficient (to not potentially waste effort).

It has a smaller 'e' value but sieves ~4% faster.

# norm 2.230278e-13 alpha -6.709216 e 2.485e-11
skew: 508389.51
c0: -1715096044102766131555640234382300
c1:  72526691734251272118367460690
c2: -120771683611520445554704
c3: -483822867366235288
c4:  398591914077
c5:  876240
Y0: -198414717006063417277428937
Y1:  3937215344981633

Using the params:

rlim: 9000000
alim: 9000000
lpbr: 28
lpba: 28
mfbr: 56
mfba: 56
rlambda: 2.5
alambda: 2.5

The GGNFS poly: total yield: 15570, q=10010023 (0.02606 sec/rel)

msieve poly: total yield: 17086, q=10010023 (0.02513 sec/rel)

[Andi47]

Originally Posted by jrk

Here's a nice one that popped out of msieve...

# norm 2.230278e-13 alpha -6.709216 e 2.485e-11
<snip>

I did a search from 1 to 3000.

This one might be slightly better (assuming that the "combined" value from msieve is the same as the "e" value):

R0: -667075514232026401037903971
R1:  1036651090752913
A0: -70301050564161042395853180825579264
A1:  760641393409756411433308787652
A2:  456862733931472272483861
A3: -400760058780476342
A4: -26481981572
A5:  2040
skew 3879684.27, size 2.230540e-013, alpha -7.209819, combined = 2.495775e-011

[henryzz]

has a recommended level msieve poly serch been done?
i bet that will find a better poly than anything else

[10metreh]

Originally Posted by jrk

Using the params:

rlim: 9000000
alim: 9000000
lpbr: 28
lpba: 28
mfbr: 56
mfba: 56
rlambda: 2.5
alambda: 2.5

The GGNFS poly: total yield: 15570, q=10010023 (0.02606 sec/rel)

msieve poly: total yield: 17086, q=10010023 (0.02513 sec/rel)

Which siever did you use? And shouldn't alim and rlim be higher than 9M? (They were 12M for the C136.)

[henryzz]

Originally Posted by 10metreh

Which siever did you use? And shouldn't alim and rlim be higher than 9M? (They were 12M for the C136.)

we hardly used the full 12M alim and rlim for the C136

[10metreh]

Originally Posted by henryzz

we hardly used the full 12M alim and rlim for the C136

If we use 13e, then we'll probably go further than 12M this time.

[schickel]

Originally Posted by jrk

Was that a complete search with GGNFS?

That was ~12 hours of searching. The "c5" value being searched when I stopped it was >1,500,000, so it had been a while since it had found that poly....

The GGNFS poly: total yield: 15570, q=10010023 (0.02606 sec/rel)

msieve poly: total yield: 17086, q=10010023 (0.02513 sec/rel)

So, looks like ~10% better yield with msieve's poly and slightly better speed. Might be the way to go.....

[Andi47]

Originally Posted by schickel

That was ~12 hours of searching. The "c5" value being searched when I stopped it was >1,500,000, so it had been a while since it had found that poly....So, looks like ~10% better yield with msieve's poly and slightly better speed. Might be the way to go.....

Can you please also benchmark my poly? Is it better than jrk's?

[henryzz]

Originally Posted by Andi47

I did a search from 1 to 3000.

are you doing more?
3000-4000 is in progress on my machine
edit: just noticed it says 47 hours
it is pointless spending that long more
i am stopping