Team sieve #9: c134 from 4788.2425
 

[B]Post-processing will be done by jrk[/B]

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

[B]28/7: reservations closed.[/B]

[B]Poly:[/B][code]n: 46334491956043710225938330967034053252570375961099723291677005874807967585788533290212203831083417490921313409294721505021600000357391
Y0: -74345499857629306588651703
Y1: 526918406537017
c0: 1476115900135771763787951266874992
c1: 626824231219973690300198460
c2: -13207605174359180727636
c3: -12643447556511725
c4: 5363656602
c5: 20400
skew: 702726.68
rlim: 10000000
alim: 10000000
lpbr: 28
lpba: 28
mfbr: 56
mfba: 56
rlambda: 2.5
alambda: 2.5[/code][B]Reservations:[/B][code][B] Range Who[/B]
* L-S 1-155 jrk (done, 451824 relations)
* 1.0- 2.0M Greebley (done, 1483682 relations)
* 2.0- 3.0M bsquared (done, 4138746 relations @14e)
* 3.0- 4.0M Greebley (done, 2600321 relations)
* 4.0- 5.0M Greebley (done, 2637895 relations)
* 5.0- 5.2M wreck (done, 565856 relations)
* 5.2- 6.0M Greebley (done, 2202023 relations)
* 6.0- 8.0M bsquared (done, 5326801 relations)
* 8.0- 8.4M jrk (done, 1132295 relations)
* 8.4- 8.8M jrk (done, 1121547 relations)
* 8.8- 9.2M Greebley (done, 1109845 relations)
* 9.2- 9.5M Mini-Geek (done, 835704 relations)
* 9.5-11.0M bsquared (done, 4128980 relations)[/code]
[B]Total relations received: 27735519 (110.9% of 25M)[/B]

[B]27/7 filtering run: 20561188 relations, 17571438 unique[/B]

I reckon we should aim for about 25M relations, but do a filtering run at 20M first to see how many duplicates we're getting.

The command line to use is:[code]gnfs-lasieve4I13e -o <outputfilename> -a c134.poly -f <start of range> -c <length of range>[/code] where <outputfilename> is the file the relations will be stored in and c134.poly is the file above containing the polynomial and parameters.

[B]Instructions for uploading:[/B][quote=mdettweiler]In other news: I am pleased to announce that we now have a working FTP server set up for relations uploads! 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.

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

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

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

[B]-ftp will now output the following:[/B]
[B]230 Login successful.[/B]
[B]ftp> [/B]

[B]-Type "cd c134-relations" and press Enter.[/B]

[B]-Type "binary" and press Enter.[/B]

[B]-Now type the following command:[/B]
[B]put relations.gz[/B]
[B]...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.[/B]

[B]-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.[/B]

[B]-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![/B]

[B]-Type "quit" and press Enter. Close the command prompt/terminal window.[/B][/quote]

We need a volunteer for the post-processing...

[quote=10metreh;182550]We need a volunteer for the post-processing...[/quote]
How much RAM are we talking?
Also, the upload instructions should say c134, not c157.

[quote=Mini-Geek;182551]How much RAM are we talking?
Also, the upload instructions should say c134, not c157.[/quote]

It should fit in 768MB (or 512MB with a bit of oversieving). It'll fit in 1GB for sure.

BTW, the "c157" will change... and it has done. :smile:

[QUOTE=10metreh;182550]We need a volunteer for the post-processing...[/QUOTE]

I'll do it.

I was thinking of trying to learn to do this and help out. From the 146 string, if I wanted to try 3-3.2M I would do:
gnfs-lasieve4I13e -o 3_3.2.out -a 4788.poly -f 3000000 -c 200000

I am guessing at the gnfs-lasieve4I13e postfix based on the other one being gnfs...14e (13 is number of digits??)

Also what does the 'algabraic' mean? I don't see algebraic mentioned so is it not algebraic and I should remove the -a?

For 4788.poly I cut and paste the poly at the top of the post with all the parameters. A general question is how one chooses the parameters jrk mentions, though I don't need to know this just to help out.

When finished I follow the instructions for ftp'ing the 3_3.2.out file - is there a naming convention to follow for the file name?

[quote=Greebley;182561]I was thinking of trying to learn to do this and help out. From the 146 string, if I wanted to try 3-3.2M I would do:
gnfs-lasieve4I13e -o 3_3.2.out -a 4788.poly -f 3000000 -c 200000

[/quote]

Yep.

[quote=Greebley;182561]
I am guessing at the gnfs-lasieve4I13e postfix based on the other one being gnfs...14e (13 is number of digits??)

[/quote]

13 refers to the size of the sieving region. In GGNFS, this means we are lattice sieving over a region of size 2^13 (actually, if I understand correctly, a parallelogram of size 2^13 x 2^12) for each special-q.

[quote=Greebley;182561]

Also what does the 'algabraic' mean? I don't see algebraic mentioned so is it not algebraic and I should remove the -a?

[/quote]

In my crude understanding, NFS works by sieving and finding smooth relations over two fields simultaneously, the 'algebraic' and the 'rational'. Sieving on the algebraic side means the special-q is applied to that side rather than the rational. You'll need to specify -a or -r, here we are using -a.

[quote=Greebley;182561]
For 4788.poly I cut and paste the poly at the top of the post with all the parameters. A general question is how one chooses the parameters jrk mentions, though I don't need to know this just to help out.

When finished I follow the instructions for ftp'ing the 3_3.2.out file - is there a naming convention to follow for the file name? [/quote]

Parameter choices are somewhat of an art form based on prior experience. To get started, the ggnfs package specifies decent values over a range of input sizes in a file called def-par.txt

I've never seen a file name convention specified or adhered to. I typically just do something like:
4788_2425-2M-3M.tgz

hope this helps.

For newbies, I'm putting in the command line.

[QUOTE=bsquared;182525][CODE]
4.814 poly
total yield: 5863, q=5001001 (0.02095 sec/rel)[/CODE][/QUOTE]

[QUOTE=bsquared;182525]5 MQ should be more than enough for this one. [/QUOTE]

You used sieve 14e for that trial? With sieve 13e, I'd expect to need closer to 10MQ sieved.

Ok, I am going to try 3 to 3.5 million.

It said:
Warning: lowering FB_bound to 2999999
Does that matter?

[quote=Greebley;182613]Ok, I am going to try 3 to 3.5 million.

It said:
Warning: lowering FB_bound to 2999999
Does that matter?[/quote]
No, that's a good thing. It's a modification to the parameters that used to have to be made manually, but now is done automatically by the siever.