Aliquot sequence reservations - Page 134

fivemack · 2016-09-03, 06:43

Dropping 652296 (141 digits, 2^2*5*7*C139, 4000@3e6 ECM)

EdH · 2016-09-07, 15:33

Reserving 460104, 662706, 684816

mataje · 2016-09-12, 22:48

Reserving 508284.

fivemack · 2016-09-19, 21:26

Dropping 214864 (145 digits, 2^4*3^2, ECMed C140)

Gimarel · 2016-09-24, 09:44

Dropping 27324

mataje · 2016-09-24, 10:12

Dropping 508284.

EdH · 2016-09-27, 18:07

Query 640104 status?

I inadvertently worked some on 640104 instead of 460104. When I searched to see who to apologize to, I found no reference to that number at all anywhere, including the "Current status of aliquot sequences with start term below 1 million" page or the archives. Is it an unclaimed orphan?

I suppose I could check to see if it was a number with a bad .elf, but wouldn't it have shown up in the thread(s) about them, if it was, and would that keep it from showing up in the "Current status..." page?

Is this possibly within a block of reserved numbers? If so, would that prevent it from showing up on the above referenced pages.

The last line in the db is:

Code:

Unchecked     3510     138_(show)     7867005339...98_<138> = 2 · 3 · 2347 · 5586568200...39_<134>

Dubslow · 2016-09-27, 18:54

The id for the last line, 1100000000869112634, doesn't seem to be in the current list of final lines http://www.rechenkraft.net/aliquot/AllSeq.json (doesn't *necessarily* guarantee it's improperly missing, but makes it seem pretty likely). On the other hand, the line is newly created as of today. Give it four days to let all the sequences cycle on the aliquot page before we check again for a duplicate.

When you ran it, did you do so with aliqueit? It would detect any .elf errors introduced by the FDB

EdH · 2016-09-27, 19:47

Quote:

Originally Posted by Dubslow

The id for the last line, 1100000000869112634, doesn't seem to be in the current list of final lines http://www.rechenkraft.net/aliquot/AllSeq.json (doesn't *necessarily* guarantee it's improperly missing, but makes it seem pretty likely). On the other hand, the line is newly created as of today. Give it four days to let all the sequences cycle on the aliquot page before we check again for a duplicate.

When you ran it, did you do so with aliqueit? It would detect any .elf errors introduced by the FDB

That new line is probably from me. I'm testing ali.pl (by yoyo). It doesn't check the .elf or create a log, so I don't know how many lines I did. Perhaps, if it is "invisible" I didn't intrude on someone else's work.

Thanks for checking.

yoyo · 2016-09-27, 19:51

ali.pl runs yafu and yafu writes a factor.log. There you see which composites you factored and which factors you found.

ugly2dog · 2016-09-27, 22:59

Quote:

Originally Posted by EdH

Query 640104 status?

It merges with a lower sequence
640104:I2=282216:I3
and it appears that 282216 isn't being worked on.

2016-09-27, 18:07	#1470
EdH "Ed Hall" Dec 2009 Adirondack Mtns E26₁₆ Posts	Query 640104 status? I inadvertently worked some on 640104 instead of 460104. When I searched to see who to apologize to, I found no reference to that number at all anywhere, including the "Current status of aliquot sequences with start term below 1 million" page or the archives. Is it an unclaimed orphan? I suppose I could check to see if it was a number with a bad .elf, but wouldn't it have shown up in the thread(s) about them, if it was, and would that keep it from showing up in the "Current status..." page? Is this possibly within a block of reserved numbers? If so, would that prevent it from showing up on the above referenced pages. The last line in the db is: Code: Unchecked 3510 138_(show) 7867005339...98_<138> = 2 · 3 · 2347 · 5586568200...39_<134>

2016-09-27, 18:54	#1471
Dubslow Basketry That Evening! "Bunslow the Bold" Jun 2011 40<A<43 -89<O<-88 3·29·83 Posts	The id for the last line, 1100000000869112634, doesn't seem to be in the current list of final lines http://www.rechenkraft.net/aliquot/AllSeq.json (doesn't necessarily guarantee it's improperly missing, but makes it seem pretty likely). On the other hand, the line is newly created as of today. Give it four days to let all the sequences cycle on the aliquot page before we check again for a duplicate. When you ran it, did you do so with aliqueit? It would detect any .elf errors introduced by the FDB Last fiddled with by Dubslow on 2016-09-27 at 19:03

2016-09-27, 19:51	#1473
yoyo Oct 2006 Berlin, Germany 2·3·101 Posts	ali.pl runs yafu and yafu writes a factor.log. There you see which composites you factored and which factors you found. Last fiddled with by yoyo on 2016-09-27 at 19:51

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Extending an aliquot sequence backwards	arbooker	Aliquot Sequences	5	2020-11-07 15:58
Another Aliquot Sequence site	schickel	Aliquot Sequences	67	2012-01-20 17:53
Aliquot sequence worker for factordb	yoyo	FactorDB	6	2012-01-12 20:58
YA aliquot-sequence-chasing script	fivemack	Aliquot Sequences	5	2009-09-28 16:40
Useful aliquot-sequence links	10metreh	Aliquot Sequences	2	2009-07-31 17:43

2016-09-03, 06:43	#1464
fivemack (loop (#_fork)) Feb 2006 Cambridge, England 2×3,191 Posts	Dropping 652296 (141 digits, 2^257*C139, 4000@3e6 ECM)

2016-09-07, 15:33	#1465
EdH "Ed Hall" Dec 2009 Adirondack Mtns 2×1,811 Posts	Reserving 460104, 662706, 684816

2016-09-12, 22:48	#1466
mataje Jan 2009 Bilbao, Spain 283 Posts	Reserving 508284.

2016-09-19, 21:26	#1467
fivemack (loop (#_fork)) Feb 2006 Cambridge, England 2·3,191 Posts	Dropping 214864 (145 digits, 2^4*3^2, ECMed C140)

2016-09-24, 09:44	#1468
Gimarel Apr 2010 2·79 Posts	Dropping 27324

2016-09-24, 10:12	#1469
mataje Jan 2009 Bilbao, Spain 433₈ Posts	Dropping 508284.