Reserved for MF - Sequence 3408 - Page 8

RichD · 2013-09-19, 23:23

With your counts I believe we have surpassed the minimum needed. Of course, an ECM find now would save tons of sieving. I've switched to Seq 3366.

There are three people working on the poly in different search spaces. I'm also working on c173 for 4788:i5154 but the c162 will be the first one out the door.

EdH · 2013-09-20, 03:23

Quote:

Originally Posted by RichD

With your counts I believe we have surpassed the minimum needed. Of course, an ECM find now would save tons of sieving. I've switched to Seq 3366.

There are three people working on the poly in different search spaces. I'm also working on c173 for 4788:i5154 but the c162 will be the first one out the door.

I've got >600@2e8 now and counting. I am still getting some errors, but not too many and the scripts allow for restarts whenever I get one. Counting has to be done manually, but I have a count built into the script output for each machine that isn't too bad to use. I just have to check each machine. I'll keep these going @2e8 for now.

I see that the poly for 4788 (c173) is finished, but that's going to be a long project. I'm wondering about this c162. I may not be able to start sieving until Sunday, due to a couple of other things going on...

RichD · 2013-09-20, 04:36

Quote:

Originally Posted by EdH

I see that the poly for 4788 (c173) is finished, but that's going to be a long project. I'm wondering about this c162. I may not be able to start sieving until Sunday, due to a couple of other things going on...

I'm trying to get the optimal parameters for the c173 through trial sieving, but that is a low priority.

I have a request in to debrouxl to see if they want to perform the sieving. The post-processing would still be up for grabs.

EdH · 2013-09-20, 11:46

Quote:

Originally Posted by RichD

I'm trying to get the optimal parameters for the c173 through trial sieving, but that is a low priority.

I have a request in to debrouxl to see if they want to perform the sieving. The post-processing would still be up for grabs.

Is anyone else interested in 4788 anymore? I probably don't have the memory for it and couldn't take on anything too long within the next couple weeks.

1240@2e8 (c162 total), so far...

RichD · 2013-09-20, 16:16

A similar argument could be stated about Seq 3366.

LaurV · 2013-09-20, 17:38

Quote:

Originally Posted by RichD

A similar argument could be stated about Seq 3366.

Actually not, unless it gets a 5, it can lose the 3^2. The only problem is the size of the cofactor

4788 has a driver which is very difficult to get rid of, and at that size...
The two situations are very different.

schickel · 2013-09-20, 18:13

Quote:

Originally Posted by EdH

Is anyone else interested in 4788 anymore? I probably don't have the memory for it and couldn't take on anything too long within the next couple weeks.

If we do decide to do the c173 on 4788, I can do the post-processing.

debrouxl · 2013-09-20, 18:46

Even if I once unleashed a C172 GNFS onto RSALS clients (shortly before shutting the grid down, in order to try and match the computing power explosion from ~300 GFLOPS to 2+ TFLOPS resulting from the announcement...), a C173 is significantly outside of the 14e comfort zone.
You'd have to ask Greg for sieving with 15e on NFS@Home

EdH · 2013-09-21, 00:54

Just crossing 2100@2e8 (total)...

RichD · 2013-09-21, 05:18

In summary:
c162 (Seq 3408)
c172 (Seq 3366)
c173 (Seq 4788)

By no means do I own any of these sequences, they belong to the forum. So majority rules.

Since NFS@Home has agreed to help with c162, I think it would be best to turn it over to them. Let them sieve the entire range.

The c173 will be a long project so nobody gets burnt out sieving the c162. I see this as people may come and go, run a few million Qs, post it and come back later for more. An administrative nightmare - not really, just involved.

The c172 is weeks/months if not more away from NFS, and an ECM factor could still pop out. I would hate to have two team sieve projects going on at the same time. It would most likely be me that accumulated a bunch of rels on the wrong poly, the wrong range or the wrong number. Arg!

Comments?

EdH · 2013-09-21, 12:15

Quote:

Originally Posted by RichD

In summary:
c162 (Seq 3408)
c172 (Seq 3366)
c173 (Seq 4788)

By no means do I own any of these sequences, they belong to the forum. So majority rules.

Since NFS@Home has agreed to help with c162, I think it would be best to turn it over to them. Let them sieve the entire range.

The c173 will be a long project so nobody gets burnt out sieving the c162. I see this as people may come and go, run a few million Qs, post it and come back later for more. An administrative nightmare - not really, just involved.

The c172 is weeks/months if not more away from NFS, and an ECM factor could still pop out. I would hate to have two team sieve projects going on at the same time. It would most likely be me that accumulated a bunch of rels on the wrong poly, the wrong range or the wrong number. Arg!

Comments?

If NFS@Home has the c162, then I will turn my ecm efforts toward the c172. I'll probably run 2000@11e7 and then see what happens with continuous 2e8, unless my machines whine too much about the size. I'll see how they do...

My final count for the c162 is ~2630@2e8 (total)

2013-09-21, 00:54	#86
EdH "Ed Hall" Dec 2009 Adirondack Mtns E21₁₆ Posts	c162 Just crossing 2100@2e8 (total)...

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Reserved for MF - Sequence 3366	RichD	Aliquot Sequences	468	2021-01-27 01:16
Reserved for MF - Sequence 4788	schickel	Aliquot Sequences	2934	2021-01-07 18:52
Reserved for MF - Sequence 276	kar_bon	Aliquot Sequences	127	2020-12-17 10:05
Team Sieve #37: 3408:i1287	RichD	Aliquot Sequences	14	2013-08-02 17:02
80M to 64 bits ... but not really reserved	petrw1	Lone Mersenne Hunters	82	2010-01-11 01:57

2013-09-19, 23:23	#78
RichD Sep 2008 Kansas CCB₁₆ Posts	With your counts I believe we have surpassed the minimum needed. Of course, an ECM find now would save tons of sieving. I've switched to Seq 3366. There are three people working on the poly in different search spaces. I'm also working on c173 for 4788:i5154 but the c162 will be the first one out the door.

2013-09-20, 16:16	#82
RichD Sep 2008 Kansas 110011001011₂ Posts	A similar argument could be stated about Seq 3366.

2013-09-20, 18:46	#85
debrouxl Sep 2009 977 Posts	Even if I once unleashed a C172 GNFS onto RSALS clients (shortly before shutting the grid down, in order to try and match the computing power explosion from ~300 GFLOPS to 2+ TFLOPS resulting from the announcement...), a C173 is significantly outside of the 14e comfort zone. You'd have to ask Greg for sieving with 15e on NFS@Home

2013-09-21, 05:18	#87
RichD Sep 2008 Kansas 5²·131 Posts	In summary: c162 (Seq 3408) c172 (Seq 3366) c173 (Seq 4788) By no means do I own any of these sequences, they belong to the forum. So majority rules. Since NFS@Home has agreed to help with c162, I think it would be best to turn it over to them. Let them sieve the entire range. The c173 will be a long project so nobody gets burnt out sieving the c162. I see this as people may come and go, run a few million Qs, post it and come back later for more. An administrative nightmare - not really, just involved. The c172 is weeks/months if not more away from NFS, and an ECM factor could still pop out. I would hate to have two team sieve projects going on at the same time. It would most likely be me that accumulated a bunch of rels on the wrong poly, the wrong range or the wrong number. Arg! Comments?