Register FAQ Search Today's Posts Mark Forums Read

 2016-07-16, 15:51 #12 chris2be8     Sep 2009 7B716 Posts I've started running a script to go through the numbers with status unknown in factordb and add algebraic factors if factordb doesn't know about them. I *think* I've added long enough delays between requests to stop it overloading factordb. Is one request per second reasonable? It'll probably take more than 6 months to go through all 41 million such numbers. So far I'm partly factoring about 9% of them. When it's finished I could run it against composites with no known factors. I'd need to update it to stop it trying to add too many factors that are already known though. Does anyone think they would find this useful? Chris
 2016-09-06, 16:04 #13 chris2be8     Sep 2009 111101101112 Posts I decided to stop it once I'd reached 60,000 digit numbers. The tally is: 20,817,600 numbers checked. 1,023,341 numbers at least partly factored. 1,538 ended up fully factored. There are probably some duplicates in there though. I'll now start running against composites with no known factors. Which will take a few months. But should have more numbers end up fully factored, at least to start with. Chris
2016-09-07, 09:56   #14
henryzz
Just call me Henry

"David"
Sep 2007
Cambridge (GMT/BST)

2·2,897 Posts

Quote:
 Originally Posted by chris2be8 I decided to stop it once I'd reached 60,000 digit numbers. The tally is: 20,817,600 numbers checked. 1,023,341 numbers at least partly factored. 1,538 ended up fully factored. There are probably some duplicates in there though. I'll now start running against composites with no known factors. Which will take a few months. But should have more numbers end up fully factored, at least to start with. Chris
I assume that you are checking if a number would have algebraic factors even if the number has already had small factors removed.

 2016-09-07, 16:01 #15 chris2be8     Sep 2009 52×79 Posts Correct. Eg: Code:  (6827^48+1)/29605130633466729757863645596968113368259830758158964079481474144706 (record 211, match 60) has 1 factor 6827^16+1 In postFactors url = http://factordb.com/index.php?id=1100000000585123211, factors = 6827^16+1 #### http://factordb.com/index.php?id=1100000000585123211 is fully factored #### 1 factor already known by factordb for record 211 (match 60) Chris
 2016-10-21, 20:30 #16 chris2be8     Sep 2009 52·79 Posts Another "feature" I've just found, http://factordb.com/listtype.php?t=3 says you can skip a maximum of 50000 numbers. If you ask it to skip more it only skips 50000 numbers. So if there are more than 50000 numbers with a given number of digits the rest can't be displayed. That caught my script out. There are more that 50000 309 digit numbers in factordb. And it didn't notice that when it asked to skip 50012, 50112, 50212, etc numbers it was always getting the same list of numbers. And I didn't notice for a few hours either. I've patched the script to skip to the next number of digits once it's checked the first 50100 numbers (I read 100 at a time so can get that far). Which at least lets it carry on. Chris
2016-10-21, 21:20   #17
EdH

"Ed Hall"
Dec 2009

22·883 Posts

Quote:
 Originally Posted by chris2be8 Another "feature" I've just found, http://factordb.com/listtype.php?t=3 says you can skip a maximum of 50000 numbers. If you ask it to skip more it only skips 50000 numbers. So if there are more than 50000 numbers with a given number of digits the rest can't be displayed. That caught my script out. There are more that 50000 309 digit numbers in factordb. And it didn't notice that when it asked to skip 50012, 50112, 50212, etc numbers it was always getting the same list of numbers. And I didn't notice for a few hours either. I've patched the script to skip to the next number of digits once it's checked the first 50100 numbers (I read 100 at a time so can get that far). Which at least lets it carry on. Chris
Would you be able to access 4900 more if you asked for 5000 and pulled out sections of 100 for your script?

2016-10-21, 21:33   #18
chalsall
If I May

"Chris Halsall"
Sep 2002

2×3×1,567 Posts

Quote:
 Originally Posted by EdH Would you be able to access 4900 more if you asked for 5000 and pulled out sections of 100 for your script?
Not quite sure what you are trying to say there.

Does this translate into mass or money?

2016-10-22, 17:26   #19
chris2be8

Sep 2009

7B716 Posts

Quote:
 Originally Posted by EdH Would you be able to access 4900 more if you asked for 5000 and pulled out sections of 100 for your script?
Yes, it is possible and I've updated my script to do it. But there are more than 55000 309 digit numbers in factordb so I still can't get at the rest.

Chris

2016-10-22, 17:54   #20
xilman
Bamboozled!

"𒉺𒌌𒇷𒆷𒀭"
May 2003
Down not across

28·41 Posts

Quote:
 Originally Posted by chris2be8 Yes, it is possible and I've updated my script to do it. But there are more than 55000 309 digit numbers in factordb so I still can't get at the rest. Chris
Writing from a position of profound ignorance here: is it possible to ask for all 309-digit numbers which begin with (or end with) a specific string of digits?

2016-10-22, 18:55   #21
EdH

"Ed Hall"
Dec 2009

353210 Posts

Quote:
 Originally Posted by chris2be8 Yes, it is possible and I've updated my script to do it. But there are more than 55000 309 digit numbers in factordb so I still can't get at the rest. Chris
I notice, looking at the distribution graph, that there is a spike that goes up a couple thousand above 55000 right at 309 digits. There is another larger area up a few digits that encompasses a range above 55000.

I guess we'll just have to factor some of those 309 digit composites...

 2016-10-22, 20:56 #22 EdH     "Ed Hall" Dec 2009 Adirondack Mtns DCC16 Posts Chris, Depending on how bad you want those "invisible" 309s, this might allow you to find them. It's not very professional and I'm not sure it will even work, but let me know if it's of use: bash script: Code: #!/bin/bash/ IFS=" " # index of last known** 309 digit composite index=1100000000871347918 let indexEnd=${index}+100 while [$index -lt $indexEnd ] do seek=http://factordb.com/index.php?id=$index wget $seek exec <${seek:20} while read line do case $line in *"query"*) comp1=${line};; esac done rm ${seek:20} comp2=${comp1##*=} composite=${comp2:1:${#comp2}-3} compLength=${#composite} if [$compLength -eq 309 ] then echo $index >>indices309 fi let index=${index}+1 done ** By known, I'm referring to the last visible one initially. Then it can be changed to the new last known (now 1100000000871348012) after a run. It can put a bit of a pull on the db, but here is what it returned using the values in the above example: Code: 1100000000871347918 1100000000871347925 1100000000871347943 1100000000871347973 1100000000871348009 1100000000871348011 1100000000871348012 I think, other than the first one, these are all currently unavailable to you. edit: This version works on my Fedora 22 under its bash version. There might be slight differences in the string manipulations. I hope you can catch and fix those, if necessary. edit: Also note there is a file removal line that deletes the page retrieved by the wget line. If that removal line is of concern, it can be commented or removed and no files will be deleted. Ed Last fiddled with by EdH on 2016-10-22 at 21:01 Reason: technical details about my bash

 Similar Threads Thread Thread Starter Forum Replies Last Post ewmayer Lounge 39 2015-05-19 01:08 ewmayer Science & Technology 41 2014-04-16 11:54 cheesehead Soap Box 56 2013-06-29 01:42 cheesehead Soap Box 61 2013-06-11 04:30 Dubslow Programming 19 2012-05-31 17:49

All times are UTC. The time now is 07:30.

Sun Jan 17 07:30:29 UTC 2021 up 45 days, 3:41, 0 users, load averages: 2.03, 1.98, 1.87