problem with database

Greebley · 2009-06-20, 15:25

211788 - wrong in the database.

I was suprised to find this value was longer than 276. Looking at it, it jumps from 85 to 166 digits in one step

Is there a specific thread I should post db problems?

10metreh · 2009-06-20, 15:29

Quote:

Originally Posted by Greebley

211788 - wrong in the database.

I was suprised to find this value was longer than 276. Looking at it, it jumps from 85 to 166 digits in one step

Is there a specific thread I should post db problems?

It's the common "squared line" problem. Post db problems in the database thread! This problem is well known, although not fixed yet.

Greebley · 2009-06-20, 16:19

I don't see a sticky thread with the word database in it - whats it called?

Andi47 · 2009-06-20, 16:22

Quote:

Originally Posted by Greebley

I don't see a sticky thread with the word database in it - whats it called?

The database thread is over there in the "Factoring" subforum:

http://www.mersenneforum.org/showthread.php?t=11119

Greebley · 2009-06-20, 17:49

I noticed another issue. If you get a factor like 4967^2 in your *.elf series submitted with aliqueit -s, the database doesn't handle it. I had to factor this square manually to resolve

Is this also known?

10metreh · 2009-06-20, 18:32

Quote:

Originally Posted by Greebley

I noticed another issue. If you get a factor like 4967^2 in your *.elf series submitted with aliqueit -s, the database doesn't handle it. I had to factor this square manually to resolve

Is this also known?

It is known. The database only trial factors up to 2000 automatically.

Greebley · 2009-06-20, 20:26

This seems to be my day for finding database issues:
for sequence 125970 entry 107 is wrong - it has a different number than it should. This is what it should be:

106 . 79289831227886721316 = 2^2 * 7 * 19 * 10337827 * 14417056519
107 . 87636145410556465884 = 2^2 * 3 * 7 * 79 * 269 * 49093569496201

Note that you can tell the other value is wrong because it ends 64, but the sigma has 19+1 factor and 144..519+1 factor and so ends 00, but
...00 - ...16 means the next one should end ...84.

I tried sending the correct sequence to the DB, but it didn't update to the correct value. Also what does the CF mean? (instead of ff)

Do I need to post in the other thread mentioned to get this fixed?

kar_bon · 2009-06-20, 20:41

Quote:

Originally Posted by Greebley

I tried sending the correct sequence to the DB, but it didn't update to the correct value. Also what does the CF mean? (instead of ff)

Do I need to post in the other thread mentioned to get this fixed?

for the abrevs. see http://factorization.ath.cx/status.html

(can seen by choosing a number from database and a '?' right to the 'status' is shown:

so here:
FF Composite, fully factored
CF Composite, factors known
C Composite, no factors known
P Definitely prime
Prp Probably prime

send Syd (the Guru of the Factoring Database) a PM with this error.

one question: did you uploaded/worked on that seq?
the database-id from index 106 is at 39M, so some time ago (about a week or two i think),
the id from index 107 is very new!

Greebley · 2009-06-20, 22:29

Quote:

Originally Posted by kar_bon

for the abrevs. see http://factorization.ath.cx/status.html

(can seen by choosing a number from database and a '?' right to the 'status' is shown:

so here:
FF Composite, fully factored
CF Composite, factors known
C Composite, no factors known
P Definitely prime
Prp Probably prime

send Syd (the Guru of the Factoring Database) a PM with this error.

one question: did you uploaded/worked on that seq?
the database-id from index 106 is at 39M, so some time ago (about a week or two i think),
the id from index 107 is very new!

It is possible I updated it using the -s command, but I don't know how it would have gotten wrong. I didn't look wrong in the alq

I have noticed an issue where two lines occur on the same line in my alq_*.elf output for aliqueit, but that usually means the single index is broken and I have fixed those and had the sequence correct.

I will try to make sure I don't pass in the doubled lines just in case though.

Greebley · 2009-06-21, 21:33

Index 338 of sequence 287730 is also broken. I sent a pm to syd about this one and the previous.

Was this index added recently too? I tried to upload the sequence with -s again.

Greebley · 2009-06-22, 01:32

Going to use this thread to keep track of broken ends of the sequences.

Broken so far:
125970 - Index 107
211788 - Index 963 or 964
287730 - Index 338
444378 - Index 379
309316 - Index 466 (2^10 instead of 2^5)

Note that I was purposefully trying to get some of the shortest sequences higher (c 60 or more), so the fact that I am finding so many isn't really suprising - those sequences might have been submitted, but didn't add correctly and so were short.

2009-06-20, 15:25	#1
Greebley May 2009 Dedham Massachusetts USA 3·281 Posts	problem with database 211788 - wrong in the database. I was suprised to find this value was longer than 276. Looking at it, it jumps from 85 to 166 digits in one step Is there a specific thread I should post db problems? Last fiddled with by Greebley on 2009-06-20 at 15:27

2009-06-20, 17:49	#5
Greebley May 2009 Dedham Massachusetts USA 3×281 Posts	I noticed another issue. If you get a factor like 4967^2 in your .elf series submitted with aliqueit -s, the database doesn't handle it. I had to factor this square manually to resolve Is this also known? Last fiddled with by Greebley on 2009-06-20 at 17:50*

2009-06-21, 21:33	#10
Greebley May 2009 Dedham Massachusetts USA 3·281 Posts	Index 338 of sequence 287730 is also broken. I sent a pm to syd about this one and the previous. Was this index added recently too? I tried to upload the sequence with -s again. Last fiddled with by Greebley on 2009-06-21 at 21:36

2009-06-22, 01:32	#11
Greebley May 2009 Dedham Massachusetts USA 1101001011₂ Posts	Going to use this thread to keep track of broken ends of the sequences. Broken so far: 125970 - Index 107 211788 - Index 963 or 964 287730 - Index 338 444378 - Index 379 309316 - Index 466 (2^10 instead of 2^5) Note that I was purposefully trying to get some of the shortest sequences higher (c 60 or more), so the fact that I am finding so many isn't really suprising - those sequences might have been submitted, but didn't add correctly and so were short. Last fiddled with by Greebley on 2009-06-22 at 02:12

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Database for k-b-b's:	3.14159	Miscellaneous Math	325	2016-04-09 17:45
Database question	Xyzzy	Forum Feedback	0	2012-04-01 15:37
NPLB Database	IronBits	No Prime Left Behind	177	2009-10-10 09:00
database.zip	HiddenWarrior	Data	1	2004-03-29 03:53
Database layout	Prime95	PrimeNet	1	2003-01-18 00:49

2009-06-20, 16:19	#3
Greebley May 2009 Dedham Massachusetts USA 1101001011₂ Posts	I don't see a sticky thread with the word database in it - whats it called?

2009-06-20, 20:26	#7
Greebley May 2009 Dedham Massachusetts USA 3×281 Posts	This seems to be my day for finding database issues: for sequence 125970 entry 107 is wrong - it has a different number than it should. This is what it should be: 106 . 79289831227886721316 = 2^2 * 7 * 19 * 10337827 * 14417056519 107 . 87636145410556465884 = 2^2 * 3 * 7 * 79 * 269 * 49093569496201 Note that you can tell the other value is wrong because it ends 64, but the sigma has 19+1 factor and 144..519+1 factor and so ends 00, but ...00 - ...16 means the next one should end ...84. I tried sending the correct sequence to the DB, but it didn't update to the correct value. Also what does the CF mean? (instead of ff) Do I need to post in the other thread mentioned to get this fixed?