![]() |
|
|
#12 |
|
Sep 2009
1000000111102 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 |
|
|
|
|
|
#13 |
|
Sep 2009
81E16 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 |
|
|
|
|
|
#14 | |
|
Just call me Henry
"David"
Sep 2007
Cambridge (GMT/BST)
23·3·5·72 Posts |
Quote:
|
|
|
|
|
|
|
#15 |
|
Sep 2009
207810 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) |
|
|
|
|
|
#16 |
|
Sep 2009
81E16 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 |
|
|
|
|
|
#17 | |
|
"Ed Hall"
Dec 2009
Adirondack Mtns
11·347 Posts |
Quote:
|
|
|
|
|
|
|
#18 |
|
If I May
"Chris Halsall"
Sep 2002
Barbados
37×263 Posts |
|
|
|
|
|
|
#19 |
|
Sep 2009
81E16 Posts |
|
|
|
|
|
|
#20 |
|
Bamboozled!
"𒉺𒌌𒇷𒆷ð’€"
May 2003
Down not across
10,753 Posts |
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?
|
|
|
|
|
|
#21 | |
|
"Ed Hall"
Dec 2009
Adirondack Mtns
11×347 Posts |
Quote:
I guess we'll just have to factor some of those 309 digit composites... |
|
|
|
|
|
|
#22 |
|
"Ed Hall"
Dec 2009
Adirondack Mtns
11·347 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
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 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 |
| Official "Faits erronés dans de belles-lettres" thread | ewmayer | Lounge | 39 | 2015-05-19 01:08 |
| Official "all-Greek-to-me Fiction Literature and Cinema" Thread | ewmayer | Science & Technology | 41 | 2014-04-16 11:54 |
| Official "Lasciate ogne speranza" whinge-thread | cheesehead | Soap Box | 56 | 2013-06-29 01:42 |
| Official "Ernst is a deceiving bully and George is a meanie" thread | cheesehead | Soap Box | 61 | 2013-06-11 04:30 |
| Official "String copy Statement Considered Harmful" thread | Dubslow | Programming | 19 | 2012-05-31 17:49 |