Team sieve #20: c170 from 4788:2549
 

We're tackling a c170 from aliquot sequence 4788, index 2549.

Post-processing will be done by [B]em99010pepe[/B].
[B]Post-processing started 02 Nov 2010.
Estimated completion 08 Nov 2010
Completed. Factored as [URL="http://www.mersenneforum.org/showthread.php?p=236111#post236111"]p55*p115[/URL].[/B]

Poly for this job:[code]n: 31312681856591762976684825948611411853648506930718408786922952694966820760977803934965693400499529851375037912983239126649207012737394067178518887401399185420987310860499
# norm 1.089488e-16 alpha -8.144343 e 2.852e-13 rroots 5
skew: 2848875.02
c0: 3449752476991340409710593294897864121568
c1: 3679068299798050640485923392826756
c2: -55695962181000919237307903624
c3: 5626603601260154351771
c4: 6624408564633178
c5: 64149120
Y0: -217612366832903667482868415880575
Y1: 542063406908335635313
rlim: 33550000
alim: 33550000
lpbr: 30
lpba: 30
mfbr: 60
mfba: 87
rlambda: 2.6
alambda: 3.6
type: gnfs[/code]This poly allows for 3 large primes on the algebraic side, resulting in a slightly faster job.

Sieve using the 15e siever, starting from 30M on the algrebraic side with the following command line:[code]gnfs-lasieve4I15e -a 4788_2549.poly -o <output_file_name> -f <start_of_range> -c <length_of_range>[/code]Per usual, please check downthread for reservations not transferred up here yet.

[B]N.B.:[/B] the 15e siever will use up to [B]200MB[/B] of RAM per instance.

On my 2Ghz dual-cores, blocks of 10k special-q take ~3 hours.

Relations needed: [B]~97M unique[/B]

Relations received: [b]94.2M unique (~97.1%)[/b]

Reservations:[code]
15 M- 15.5M Andi47 (done, 1101038 relations)
15.5M- 16 M Andi47 (done, 1091882 relations)
16 M- 30 M schickel (done, just over 24000000 relations)
30 M- 31 M bchaffin (done, 2040094 unique relations)
31 M- 32 M smh (done, 1965787 relations)
32 M- 40 M bsquared (done, 15138914 relations)
40 M- 47.2M bsquared (done, 12742177 relations)
47.2M- 50 M bchaffin (done)
50 M- 52 M bchaffin (done)
52 M- 57 M bsquared (done, 8143236 relations)
57 M- 60 M bsquared (done, 4778150 relations)
60 M- 62 M bchaffin (done)
62 M- 64 M bchaffin (done)
64 M- 65 M em99010pepe (done)
65 M- 68 M bchaffin (done)
68 M- 70 M bsquared (done, 3004347 relations)
70 M- 72 M bchaffin (done)
72 M- 75 M bsquared (done, 4409292 relations)
75 M- 77 M bchaffin (done)
77 M- 80 M bsquared (done, 4290164 relations)
80 M- 92 M em99010pepe (done)[/code][B]Estimated completion at present speed[/B]: November, 2010 [size="1"][B][I]Much better![/I][/B] [/size]

For the relations on this job, shall we use a file-share service, or should I see if I can set up a home FTP server?

[QUOTE=schickel;232776]For the relations on this job, shall we use a file-share service, or should I see if I can set up a home FTP server?[/QUOTE]

How fast is your connection?

[url]http://www.sendspace.com/[/url] is what we usually use, but if it looks like a home FTP setup would be better, we can go with that.

[QUOTE=schickel;232773]qintsize: 10000[/QUOTE]
Take this line out of the poly file. It'll override the -c count parameter on the command line.

[QUOTE=em99010pepe;232777]How fast is your connection?[/QUOTE]It usually tests at around 1Mb down/.1Mb up. So I can collect 'em pretty fast, but I'll be piss poor sending 'em.

[QUOTE=Mini-Geek;232778][url]http://www.sendspace.com/[/url] is what we usually use, but if it looks like a home FTP setup would be better, we can go with that.[/QUOTE]I guess it would make more sense if I did all the post-processing (filtering and LA), but it might make sense to do it with an FTP server if I did the filtering and cycle-counting, then pass the relations and .cyc files to em99010pepe.

[QUOTE=jrk;232779]Take this line out of the poly file. It'll override the -c count parameter on the command line.[/QUOTE]Done. I copied the poly from my work directory. I thought that was only used by the scripts, I didn't realize that the siever used that line....

[QUOTE=schickel;232780]It usually tests at around 1Mb down/.1Mb up. So I can collect 'em pretty fast, but I'll be piss poor sending 'em.

I guess it would make more sense if I did all the post-processing (filtering and LA), but it might make sense to do it with an FTP server if I did the filtering and cycle-counting, then pass the relations and .cyc files to em99010pepe.[/QUOTE]

I just don't know one step, after downloading the relations how to merge them into msieve dat file. The rest is peaceful...I hope...

[code]msieve.exe -i xxx.ini -s xxx.dat -nf xxx.fb -nc -v -t 4

or

having msieve.fb, worktodo.ini and msieve.dat, run msieve.exe -nc -v -t 4[/code]

Post-processing will be done on a core i5 750@3.7 GHz with 8GB.

[QUOTE=em99010pepe;232783]I just don't know one step, after downloading the relations how to merge them into msieve dat file. The rest is peaceful...I hope...[/QUOTE]

You can start with a msieve.dat file with one line:
[CODE][FONT=Arial Narrow]N 31312681856591762976684825948611411853648506930718408786922952694966820760977803934965693400499529851375037912983239126649207012737394067178518887401399185420987310860499[/FONT]
[/CODE]
then [FONT=Fixedsys]gzip msieve.dat[/FONT], and then, when you get a new chunk from collaborators,
1. [FONT=Fixedsys]gzip -tv new_file.gz[/FONT] to check for errors (or if bzip2'd, then bunzip and regzip)
2. [FONT=Fixedsys]cat new_file.gz >> msieve.dat.gz[/FONT]

That will save you some disk space.

[FONT=Arial]On Jeff Gilchrist's webpage he has 4 versions of ggnfs, SVN 374 (32 bits and 64 bits) and SVN 360 (32 bits and 64 bits). Which combination is fastest for [FONT=monospace]gnfs-lasieve4I15e under windows 7 64 bits?[/FONT][/FONT]

[QUOTE=em99010pepe;232861][FONT=Arial]On Jeff Gilchrist's webpage he has 4 versions of ggnfs, SVN 374 (32 bits and 64 bits) and SVN 360 (32 bits and 64 bits). Which combination is fastest for [FONT=monospace]gnfs-lasieve4I15e under windows 7 64 bits?[/FONT][/FONT][/QUOTE]Unless things have changed, the 32-bit sievers are faster on 64-bit Windows than the 64-bit sievers.