Sieving Discussion

ltd · 2005-07-12, 18:28

I would rather suggest to finish started ranges before switching to the new dat as that gives me more time to create a dat file that does not need an update every few days.

Lars

Citrix · 2005-07-12, 18:34

Well I don't see a point in duplicating work even if people will have to update the dat every few days.

Alternatively people can work on the PRP section and help find a prime and reduce the size of the dat. We are a bit overdue for a prime.

Citrix

ltd · 2005-07-12, 18:43

I made that suggestion only for one reason. If we make a clean cut between new and old ranges there is less danger of using the wrong dat file or mixed reservations in the different sieve sections.

Buit i have no problem with doing it the way you suggested.
Let the sievers decide what they want to do.

Lars

VJS · 2005-07-12, 19:01

Either way it's pretty easy to tell which ranges are done with which dats when you do a gap analysis... especially when you consider accepting factrange.txt.

ltd · 2005-07-12, 19:04

You are right.

Lars

battlemaxx · 2005-07-12, 20:17

I can't stop a couple of the machines, they are run by someone else and out of my hands.

ltd · 2005-07-12, 20:43

Thats no problem at all. Keep those machines running!!!!!!

battlemaxx · 2005-07-12, 21:11

84600 to 84800 completed by battlemaxx

battlemaxx · 2005-07-12, 23:50

So, what's the deal with the two Sieve threads?

Citrix · 2005-07-13, 14:29

The old thread is 0-20Million dat
the new thread is 0-50 Million dat.

We are combining our sieivng efforts with SOB to make the process more efficient.

Citrix

VJS · 2005-07-13, 15:39

Not sure which thread to post this in but here are the ranges <100T we have not sieve with the 991-50M dat. Once you guys get close to these ranges and reduce the dat size I'll add it to the SoB dat and sieve these (or we can sieve these together etc..).

53000-57000
69000-76000
80000-89000
90000-95000

So please consider these reserved or on hold etc...

2005-07-12, 19:01	#4
VJS Dec 2004 13×23 Posts	Either way it's pretty easy to tell which ranges are done with which dats when you do a gap analysis... especially when you consider accepting factrange.txt. Last fiddled with by VJS on 2005-07-12 at 19:02

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
S9 and general sieving discussion	Lennart	Conjectures 'R Us	31	2014-09-14 15:14
Sieving discussion thread	jasong	Twin Prime Search	311	2010-10-22 18:41
Sieving discussion thread	philmoore	Five or Bust - The Dual Sierpinski Problem	66	2010-02-10 14:34
Combined sieving discussion	ltd	Prime Sierpinski Project	76	2008-07-25 11:44
Sieving Discussion	R.D. Silverman	Factoring	7	2005-09-30 12:57

2005-07-12, 18:28	#1
ltd Apr 2003 1404₈ Posts	I would rather suggest to finish started ranges before switching to the new dat as that gives me more time to create a dat file that does not need an update every few days. Lars

2005-07-12, 18:34	#2
Citrix Jun 2003 1,579 Posts	Well I don't see a point in duplicating work even if people will have to update the dat every few days. Alternatively people can work on the PRP section and help find a prime and reduce the size of the dat. We are a bit overdue for a prime. Citrix

2005-07-12, 18:43	#3
ltd Apr 2003 2²·193 Posts	I made that suggestion only for one reason. If we make a clean cut between new and old ranges there is less danger of using the wrong dat file or mixed reservations in the different sieve sections. Buit i have no problem with doing it the way you suggested. Let the sievers decide what they want to do. Lars

2005-07-12, 19:04	#5
ltd Apr 2003 304₁₆ Posts	You are right. Lars

2005-07-12, 20:17	#6
battlemaxx Nov 2002 43 Posts	I can't stop a couple of the machines, they are run by someone else and out of my hands.

2005-07-12, 20:43	#7
ltd Apr 2003 2²×193 Posts	Thats no problem at all. Keep those machines running!!!!!!

2005-07-12, 21:11	#8
battlemaxx Nov 2002 101011₂ Posts	84600 to 84800 completed by battlemaxx

2005-07-12, 23:50	#9
battlemaxx Nov 2002 43 Posts	So, what's the deal with the two Sieve threads?

2005-07-13, 14:29	#10
Citrix Jun 2003 1,579 Posts	The old thread is 0-20Million dat the new thread is 0-50 Million dat. We are combining our sieivng efforts with SOB to make the process more efficient. Citrix

2005-07-13, 15:39	#11
VJS Dec 2004 13×23 Posts	Not sure which thread to post this in but here are the ranges <100T we have not sieve with the 991-50M dat. Once you guys get close to these ranges and reduce the dat size I'll add it to the SoB dat and sieve these (or we can sieve these together etc..). 53000-57000 69000-76000 80000-89000 90000-95000 So please consider these reserved or on hold etc...