-   FactorDB (
-   -   Other Factordb Problems (

Jayder 2014-06-18 22:31

This is exasperating. msc_ngb added [URL=""]this[/URL] 16,386 digit prime and then added [B][U]all 1900 steps[/U][/B]. About 160 are above 15,000 digits, 540 between 10-15k digits, and about 540 between 5-10k digits. There are 1354 certificates in the queue right now, and the vast majority of them are just these "steps". I feel like this is a humongous waste of resources.

Jayder 2014-06-19 15:21

[QUOTE=Jayder;376167]I feel like this is a humongous waste of resources.[/QUOTE]
It looks like this may have been rectified, at least for the moment. msc_nbg's total certificates dropped by about 30k, and the queue is now clear. Looks like they were all deleted. Thanks Syd(?)! Hope this lasts.

RichD 2014-06-21 23:25

As info
[QUOTE=Jayder;375275]Maybe not worth mentioning, but this seems to still be an issue. Examples: [URL=""][1][/URL] [URL=""][2][/URL] [URL=""][3][/URL] [URL=""][4][/URL] [URL=""][5][/URL] [URL=""][6][/URL]

The helper files seem fine and I can prove it fine myself with pfgw, but I guess the database still has a hard time with lots and lots of factors.[/QUOTE]

Even with the latest enhancements and checks-and-balances, these are still an issue.

RichD 2014-06-25 20:48

[QUOTE=wblipp;375964]I still find this argument compelling. It might be possible to convince me to support a database modification that stored the one certificate and tagged all the primes as proven by that one certificate.[/QUOTE]

I agree. If someone would request the certificate of one of the steps (primes) tagged, then the database could easily build the cert from the remaining steps.

Then again, if Syd only had the time. :smile:

RichD 2014-07-03 14:30

[QUOTE=Jayder;375275]... but this seems to still be an issue. Examples: [URL=""][1][/URL] [URL=""][2][/URL] [URL=""][3][/URL] [URL=""][4][/URL] [URL=""][5][/URL] [URL=""][6][/URL][/QUOTE]

The Proof button now works for the above six. All are proven prime via N-1.

richs 2014-07-18 14:54

This number is broken (see the last factor):


chris2be8 2014-07-18 16:09

It looks OK to me. The last divisor is a p110 raised to power 33. Which look a bit odd the first time you see it but is OK.

The next question is how long it will be until someone factors the next-to-last-factor C92.


wblipp 2014-07-18 16:12

[QUOTE=richs;378461]This number is broken (see the last factor):


Perhaps this has been fixed. As of my writing, the factordb shows the last factor as a 110 digit prime raised to the 33rd power. [URL=""]Alpertron[/URL] agrees that factorization.

richs 2014-07-18 23:37

It must have been a glitch. I was factoring the C92 at the time and I like to look at the entire number.

chris2be8 2014-08-17 16:15

The list of smallest numbers without known factors contains the following 3 entries: [code]
1100000000704879936 0 1
1100000000704879961 0 1
1100000000704879980 0 1
Clicking on the 0 shows they are all 7##-7##.

I think this needs SYD to intervene.


Batalov 2014-08-17 16:56

The ## parsing [URL=""]has been broken[/URL] in FactorDB for a while and is till broken.

All times are UTC. The time now is 08:11.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.