Team sieve #41: C165 from 3366:i2098

RichD · 2013-11-14, 05:21

Tracking Aliquot Sequence 3366 index 2098.

Code:

# sieve with ggnfs lasieve4I15e on -a side from Q=14M to 27M
# aq3366:2098
n: 325051015990535995874007588250630424661613002093251050951251894916362694976876466038809353011636859335168409712756235986441762310332466382944321915205259453868831101
# norm 5.420993e-016 alpha -6.929648 e 7.006e-013 rroots 5
skew: 9356889.28
c0: -1926024418625074017922955379536534110520
c1: 1894119714203966541640748866185150
c2: 1214709679644137937069462919
c3: -2325548176534019814
c4: -13139381174804
c5: 232560
Y0: -67465745109864492336315060899031
Y1: 266382034364015119
rlim: 42000000
alim: 42000000
lpbr: 30
lpba: 30
mfbr: 60
mfba: 87
rlambda: 2.6
alambda: 3.6

Poly generated by sashamkrt
Post-processing by: ???

Run the siever using the following command:

Code:

gnfs-lasieve4I15e -a 3366_2098.poly -o <output_file_name> -f <start_of_range> -c <length_of_range>

Add the -v switch if you want to see status updates every few seconds.
(I like to watch the progress.)

In case a restart is needed in the range, add the -R switch.
(All range numbers must be full decimal representations. i.e., 21M = 21000000)

Since ggnfs is single thread, multiple copies need to be run at the same time to utilize multiple cores. Be sure to use a different output_file_name for each range. Something like 3408_22M as signifying the starting point.

The output files can be placed at any of the file sharing services: DropBox, RapidShare, SendSpace, etc.

This is a nice poly. Expect yields greater than 4:1 in some regions.

To start things off I'll take 14-18M.

schickel · 2013-11-14, 08:25

Quote:

Originally Posted by RichD

Tracking Aliquot Sequence 3366 index 2098.

Post-processing by: ???

I can do the post-processing.

Jayder · 2013-11-14, 15:08

I'm not sure how much to take. I can do 1M in under a week. Is 2M okay?

If so, I'll take 18M-20M.

EdH · 2013-11-14, 15:38

I'll do 20M-22M.

EdH · 2013-11-15, 19:38

20M-22M are on SendSpace:

3366i2098_20M-21M.rels.zip
3366i2098_21M-22M.rels.zip

I had a lot of trouble with this task. Half of my machines segfaulted out of the sieving. I think everything is cleaned up, but you might want to test them separately.

They have been run through remdups4 and show as 4521249 and 4522756 unique, respectively. remdups4 showed a total of 90445 duplicates.

I'll run 22M-24M.

RichD · 2013-11-16, 03:00

Wow, that is fast!
I'm not even at the half way point.

Quote:

Originally Posted by schickel

I can do the post-processing.

It's yours.

EdH · 2013-11-17, 01:50

22M-24M are on SendSpace:

3366i2098_22M-23M.rels.zip
3366i2098_23M-24M.rels.zip

They have been run through remdups4 and show as 4440508 and 4432062 unique, respectively. remdups4 showed a total of 81892 duplicates.

Since I seem to be going along well, I'll run 24M-26M.

How many relations are we shooting for? I seem to work it out to about 93M relations needed for a c165. But, I only see about 58M coming from the range we're working. Am I that far off?

RichD · 2013-11-17, 03:20

Quote:

Originally Posted by EdH

How many relations are we shooting for? I seem to work it out to about 93M relations needed for a c165. But, I only see about 58M coming from the range we're working. Am I that far off?

I was thinking mid-50's for total rels. We might be able to build a matrix after Q=26M but I added an extra one for good measure. (It may not be needed.)

I'm at 72% with 4.8:1 yield.

RichD · 2013-11-17, 03:30

Quote:

Originally Posted by EdH

How many relations are we shooting for? I seem to work it out to about 93M relations needed for a c165. But, I only see about 58M coming from the range we're working. Am I that far off?

You're right EdH. Since the last few were a 29-bit problem I was thinking 29-bit. This is a 30-bit problem so we need nearly twice as many. Maybe a little over 100M to be safe. My mistake.

Edit: So we have to go to Q=40 or 42M (or more?).
Another week and a half. :)

schickel · 2013-11-17, 04:22

There's a mistake with the first link....

Quote:

Originally Posted by EdH

22M-24M are on SendSpace:

[URL="http://www.mersenneforum.org/3366i2098_23M-24M.rels.zip (232.45MB)Download Link http://www.sendspace.com/file/ypjgew"]3366i2098_22M-23M.rels.zip[/URL]
[URL="http://www.sendspace.com/file/ypjgew"]3366i2098_23M-24M.rels.zip[/URL]

I got the second one, though....

EdH · 2013-11-17, 14:59

Sorry about that!

The correct link should be:

http://www.sendspace.com/file/uep62s

I will repost all the (hopefully correct) links in my next set of rels...

2013-11-14, 05:21	#1
RichD Sep 2008 Kansas 2²×3²×7×13 Posts	Team sieve #41: C165 from 3366:i2098 Tracking Aliquot Sequence 3366 index 2098. Code: # sieve with ggnfs lasieve4I15e on -a side from Q=14M to 27M # aq3366:2098 n: 325051015990535995874007588250630424661613002093251050951251894916362694976876466038809353011636859335168409712756235986441762310332466382944321915205259453868831101 # norm 5.420993e-016 alpha -6.929648 e 7.006e-013 rroots 5 skew: 9356889.28 c0: -1926024418625074017922955379536534110520 c1: 1894119714203966541640748866185150 c2: 1214709679644137937069462919 c3: -2325548176534019814 c4: -13139381174804 c5: 232560 Y0: -67465745109864492336315060899031 Y1: 266382034364015119 rlim: 42000000 alim: 42000000 lpbr: 30 lpba: 30 mfbr: 60 mfba: 87 rlambda: 2.6 alambda: 3.6 Poly generated by sashamkrt Post-processing by: ??? Run the siever using the following command: Code: gnfs-lasieve4I15e -a 3366_2098.poly -o <output_file_name> -f <start_of_range> -c <length_of_range> Add the -v switch if you want to see status updates every few seconds. (I like to watch the progress.) In case a restart is needed in the range, add the -R switch. (All range numbers must be full decimal representations. i.e., 21M = 21000000) Since ggnfs is single thread, multiple copies need to be run at the same time to utilize multiple cores. Be sure to use a different output_file_name for each range. Something like 3408_22M as signifying the starting point. The output files can be placed at any of the file sharing services: DropBox, RapidShare, SendSpace, etc. This is a nice poly. Expect yields greater than 4:1 in some regions. To start things off I'll take 14-18M.

2013-11-14, 15:08	#3
Jayder Dec 2012 2·139 Posts	I'm not sure how much to take. I can do 1M in under a week. Is 2M okay? If so, I'll take 18M-20M. Last fiddled with by Jayder on 2013-11-14 at 15:18

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Team sieve for OPN - 70841^53-1	RichD	NFS@Home	26	2016-11-18 07:55
Team sieve #37: c165 from 4788:i5144	jrk	Aliquot Sequences	20	2013-02-19 17:18
Team Sieve for 2995125705	SlashDude	Riesel Prime Search	78	2006-05-14 16:56
Team Sieve	grobie	Riesel Prime Search	3	2005-11-16 08:46
Team Sieve of 210885	SlashDude	15k Search	21	2003-12-23 16:31

2013-11-14, 15:38	#4
EdH "Ed Hall" Dec 2009 Adirondack Mtns 5³·29 Posts	I'll do 20M-22M.

2013-11-15, 19:38	#5
EdH "Ed Hall" Dec 2009 Adirondack Mtns 5³×29 Posts	20M-22M are on SendSpace: 3366i2098_20M-21M.rels.zip 3366i2098_21M-22M.rels.zip I had a lot of trouble with this task. Half of my machines segfaulted out of the sieving. I think everything is cleaned up, but you might want to test them separately. They have been run through remdups4 and show as 4521249 and 4522756 unique, respectively. remdups4 showed a total of 90445 duplicates. I'll run 22M-24M.

2013-11-17, 01:50	#7
EdH "Ed Hall" Dec 2009 Adirondack Mtns E29₁₆ Posts	22M-24M are on SendSpace: 3366i2098_22M-23M.rels.zip 3366i2098_23M-24M.rels.zip They have been run through remdups4 and show as 4440508 and 4432062 unique, respectively. remdups4 showed a total of 81892 duplicates. Since I seem to be going along well, I'll run 24M-26M. How many relations are we shooting for? I seem to work it out to about 93M relations needed for a c165. But, I only see about 58M coming from the range we're working. Am I that far off?

2013-11-17, 14:59	#11
EdH "Ed Hall" Dec 2009 Adirondack Mtns 3625₁₀ Posts	Sorry about that! The correct link should be: http://www.sendspace.com/file/uep62s I will repost all the (hopefully correct) links in my next set of rels...