Can someone delete the C15, C17, C18 in the top of the list? Think is some bug. If you click on them, the server factors them in a blink of a eye, but they never disappear from the list. Even if some factors are reported for them (tried already).

[QUOTE=LaurV;271372]Can someone delete the C15, C17, C18 in the top of the list? Think is some bug. If you click on them, the server factors them in a blink of a eye, but they never disappear from the list. Even if some factors are reported for them (tried already).[/QUOTE]Actually, the problem is that they're not C15, C17, or C18. They're actualy FF (fully factored). Syd will have to look at what's up with them....looks like something to do with how the equation parser is handling the double primorial.

If you search for, say, 13##+1 instead, it shows the exact same number as 1+13##, but its status is FF.

Is there a way to get the factorization of a given number from factordb.com in plain text format to simplify parsing the result by a script?

[QUOTE=maxal;271413]Is there a way to get the factorization of a given number from factordb.com in plain text format to simplify parsing the result by a script?[/QUOTE]

I hope there's a better way, but here's at least a workaround: request the .elf version of the aliquot sequence that starts with your number, and only read the first line, after the "0 .".
e.g.
[CODE]http://factordb.com/elf.php?seq=1234578901111111&type=1[/CODE]

[QUOTE=Mini-Geek;271424]I hope there's a better way, but here's at least a workaround: request the .elf version of the aliquot sequence that starts with your number, and only read the first line, after the "0 .".
e.g.
[CODE]http://factordb.com/elf.php?seq=1234578901111111&type=1[/CODE][/QUOTE]
Unfortunately, every time you do this, you launch another sequence. Even just a few, loads up the db with a bunch of new composites to work on, up to wherever the current cutoff is.

I'm not sure if that's good or bad, but it's why I'm not checking any more larger numbers to see if there is a sequence. The act of checking creates that sequence.

[QUOTE][url]http://factordb.com/elf.php?seq=1234578901111111&type=1[/url][/QUOTE]

Hi newbie here. I see these queries throughout the thread.
Is their a list of the parameters for the queries for getrandom.php, listtype.php, elf.php, etc. Kinda hard figuring out what parameters go with what query. Thanks in advance.

I currently have my first factor run going with factmsieve.py doing a 115 digit number to see what I get out. I'm also running some Aliquot sequences. Just trying to get more familiar with the DB.

I'm also running some composite factoring using YoYo's latest script.

Try this one (need id):

[code]
http://factordb.com/getnumber.php?id=<id>

for example

http://factordb.com/getnumber.php?id=1100000000455106295
[/code]

gives

[code]
CF 16267925138884671471389229642372683112510181901711632077772292182259170276416705940820077743337653477682582589108504337120850278545261040
[/code]

Only text, no html code.

[QUOTE=EdH;271436]Unfortunately, every time you do this, you launch another sequence. Even just a few, loads up the db with a bunch of new composites to work on, up to wherever the current cutoff is.

I'm not sure if that's good or bad, but it's why I'm not checking any more larger numbers to see if there is a sequence. The act of checking creates that sequence.[/QUOTE]
True. If you're dealing with large numbers, over roughly 110 digits, I'd expect you to run into a large number that will not automatically be factored with relatively little work. But in any case, if you're dealing with many numbers, best to stay away from this.
[QUOTE=MyDogBuster;271440]Hi newbie here. I see these queries throughout the thread.
Is their a list of the parameters for the queries for getrandom.php, listtype.php, elf.php, etc. Kinda hard figuring out what parameters go with what query. Thanks in advance.

I currently have my first factor run going with factmsieve.py doing a 115 digit number to see what I get out. I'm also running some Aliquot sequences. Just trying to get more familiar with the DB.

I'm also running some composite factoring using YoYo's latest script.[/QUOTE]
I recall a request for such a list at one point, but I haven't ever seen one. It would be very useful, though. Syd, would it be hard to put such a list together?
[QUOTE=kar_bon;271442]Try this one (need id):

[code]
http://factordb.com/getnumber.php?id=<id>

for example

http://factordb.com/getnumber.php?id=1100000000455106295
[/code]

gives

[code]
CF 16267925138884671471389229642372683112510181901711632077772292182259170276416705940820077743337653477682582589108504337120850278545261040
[/code]

Only text, no html code.[/QUOTE]
But this doesn't give the factorization of the number, just the factorization status ("CF") and the number itself. For maxal's purpose, this could be used to easily find the full digits of large primes from a [URL="http://factordb.com/index.php?id=1100000000443053648&raw=1"]normal factorization page[/URL]. That is, you could parse a page like the one I just linked to find the prime factors, except for ones over 60(?) digits, which are truncated with "..." in them. For those, you could take the id from the link given and call getnumber.php.

[QUOTE=LaurV;271372]Can someone delete the C15, C17, C18 in the top of the list? Think is some bug. If you click on them, the server factors them in a blink of a eye, but they never disappear from the list. Even if some factors are reported for them (tried already).[/QUOTE]

Thanks for keeping the sound of silence ...

re-started:
be able to see the column "status" in the job list

and possibilities "column" row lock release

Does anyone know the parameters for the report.php function?

The yafu@factordb Boinc project is now handling C98. The number composites <=120 digits without known factors is now less than 230k.
yoyo