Factoring small composites

[hansl]

I was considering trying to factor some composites from the Downloads -> "List of 1.000 randomly chosen, small composite numbers"
Is this useful to the overall purpose of factordb to fully factor these small composites?

Also is there any particular script or program I can use to only evaluate the expressions created by this, and spit them into a simple file of decimal numbers by line, so I can more easily test with various programs?

[DukeBG]

Originally Posted by hansl

I was considering trying to factor some composites from the Downloads -> "List of 1.000 randomly chosen, small composite numbers"
Is this useful to the overall purpose of factordb to fully factor these small composites?

They end up factored by someone eventually anyway, kinda.

Nobody is specifically waiting for them – and if someone is, they are wrong to do so, because factordb isn't and shouldn't be a treated as a free factoring service. Anyone is better off factoring numbers themselves than submitting them to FDB and waiting for them to be factored.

Unfortunately, it kinda gets used like that by whoever since it's so open. There's a lot of "garbage" composite numbers that people might've not even submitted consciously, but just looked up some formulae.

I've downloaded that list right now and i see it has 91 and 92-digit numbers. You can see how many total there are here.

Also is there any particular script or program I can use to only evaluate the expressions created by this, and spit them into a simple file of decimal numbers by line, so I can more easily test with various programs?

Generally you wouldn't need to – programs like yafu (which I feel is most suitable for this task) can take the expressions as input no problem.

[LaurV]

There is a "yoyo" perl script somewhere, who does a wonderful job. This script takes a random composite from the db and factors it using yafu (or other external tool) then it reports the result to the db. It is nice in sense that it is "set it and forget it", and you can also specify the desired digit and from where the random composite is taken (like "get a 120-digits composite from the smallest 100 numbers which are 120-digit composites). The "randomness" is to avoid duplication of work - it still happens sometime because people want to factor "the smallest composite available" and fdb does not have an assignment procedure, but the probability is low. Of course, you must have installed some perl, and some factoring tool, like yafu.

You can search the forum for yoyo.pl or so, and if you can't find it, I will post it soon when I get home (I do not have it here at job).

[DukeBG]

Small correction. FDB doesn't actually have an ordinality of numbers with the same digit count (by, erm, the numbers themselves). All the outputs in the same digit size are arbitrarily random. So you cannot get "smallest" 120-digits, for example. However, they are always essentially in the same order – the order they are read from the DB. So those scripts randomize that – the "page" from which the numbers are taken.

[yoyo]

Originally Posted by LaurV

There is a "yoyo" perl script somewhere, who does a wonderful job. This script takes a random composite from the db and factors it using yafu (or other external tool) then it reports the result to the db. It is nice in sense that it is "set it and forget it", and you can also specify the desired digit and from where the random composite is taken (like "get a 120-digits composite from the smallest 100 numbers which are 120-digit composites). The "randomness" is to avoid duplication of work - it still happens sometime because people want to factor "the smallest composite available" and fdb does not have an assignment procedure, but the probability is low. Of course, you must have installed some perl, and some factoring tool, like yafu.

You can search the forum for yoyo.pl or so, and if you can't find it, I will post it soon when I get home (I do not have it here at job).

-> https://www.rechenkraft.net/wiki/Ben...ctordb#yafu.pl

[chris2be8]

It's at http://mersenneforum.org/showthread.php?t=19232&page=3 post 25.

Note you must change factorization.ath.cx to factordb.com since the old DNS entry doesn't work now.

Chris

[chris2be8]

Originally Posted by unconnected

Looks like someone flooded factordb with thousands of small composites.
http://factordb.com/stat_1.php

I'm working on them. But it's like painting the Forth Bridge. And starting to get annoying.

One fool can ask more questions than a thousand wise men can answer.

Though I don't think that alone would slow down sequence processing.

Chris

[garambois]

Page updated, but only for bases 2, 3, 20, 21, 23, 162, 439, 496.
31^36 and complete base 385 are reserved for me.

Thanks to all for your help !
Please check if all your requests have been taken into account.

The other bases will be updated in the next few weeks, as it takes a lot of time for each base .

[EdH]

Note: Post was edited to remove thread irrelevant content from this copied post. Original content can be found here.

@chris2be8: I wonder if the large number of small composites on factordb was just a result of the rebuild. I did factor a few thousand, but quickly got close to the hour's limit for a couple values. They seemed to be clearing pretty fast at the time, so I left the rest alone.

[chris2be8]

I don't think the small composites are from the rebuild. I've seen quite a few numbers like:

(738468*49##+557)/35840141013305049257323
(2^295+94923)/13352559799576307

So it's general junk, not components of sequences. I've been tackling the ones that can be done by SNFS in the 80-90 digit range as well as everything from 70-79 digits. But don't hold your breath waiting for me to clear them all.

Chris

[EdH]

Originally Posted by chris2be8

I don't think the small composites are from the rebuild. I've seen quite a few numbers like:

(738468*49##+557)/35840141013305049257323
(2^295+94923)/13352559799576307

So it's general junk, not components of sequences. I've been tackling the ones that can be done by SNFS in the 80-90 digit range as well as everything from 70-79 digits. But don't hold your breath waiting for me to clear them all.

Chris

I had done about 50k, 90 dd, but noticed the count fell much more than my 50k, so I figured someone with some computing power was working there. I have since trimmed my work down considerabley and moved it to 97 dd. I'm actually factoring more than are showing up, which is reassuring, even if it is pretty low ATM compared to sometimes. If you're only working to 90 dd, maybe I'll move down to 91 when I throw some work their way.