mersenneforum.org Other Factordb Problems
 User Name Remember Me? Password
 Register FAQ Search Today's Posts Mark Forums Read

2015-05-13, 16:47   #78
Batalov

"Serge"
Mar 2008
Phi(4,2^7658614+1)/2

918310 Posts

Quote:
 Originally Posted by axn ...and apparently PFGW's definition of ## is different from factordb's, so it is tagged as composite.
## in FactorDB seems to be known to be incorrect (and of course, any larger number of ##...#s, by extension)
Point in case: 4# is correctly parsed as 6, but then, why is 4## = 210 in FactorDB??

 2015-05-13, 18:49 #79 Wick   Nov 2012 23·32 Posts According to the help: # Primordial (product of all primes below n, postfix) ## Product first n primes (postfix) 4# = 6 4## = 210 (2*3*5*7) (4#)# = 30 seems correct? Last fiddled with by Wick on 2015-05-13 at 18:49
 2015-05-13, 19:23 #80 Batalov     "Serge" Mar 2008 Phi(4,2^7658614+1)/2 217378 Posts 1) That's a very "intuitive" design. If you can show how to get this helpful "help"? except as deduced by this comment that it actually exists, and if so, then it just might be at factordb.com/help ... and in fact this page [B]does[/B] exist, in its own world - not linked to any other pages. 2) nobody uses this notation 3) what is 4### then? and why? and what is 4#### -- is it (4##)## ? (((4#)#)#)# ? ((4#)#)## ? ((4##)#)# ?
2015-05-14, 03:23   #81
axn

Jun 2003

2×5×479 Posts

FWIW, I just put n## in the search box and looked at the series that factordb printed out.

Of course, the problem is that PFGW interprets ## the same way it inteprets !! (multifactorials), i.e. product of every other prime.
Quote:
 What we've got here is failure to communicate

 2015-05-14, 03:48 #82 Batalov     "Serge" Mar 2008 Phi(4,2^7658614+1)/2 100011110111112 Posts Yes, the PFGW way makes sense. Using ## for something that cannot be written (easily) in another way makes more sense. Like the motto of a certain method, “To make the impossible possible, the possible easy, and the easy elegant.” Using n## for pn# doesn't make impossible possible, or even possible much easier than it is. If 4## is simply 7# and 10## is simply 29#, then what's the economy?
2015-05-14, 04:39   #83
axn

Jun 2003

2×5×479 Posts

Quote:
 Originally Posted by Batalov Using n## for pn# doesn't make impossible possible, or even possible much easier than it is.
Not when we're looking at an individual number, no. But, it does help when looking at series. For example, I believe the two numbers I posted came out of series n##*2^n+/-1.

Anywho... whatever format it internally supports, it needs to standardise that when communicating with external tools (like PFGW).

PS:- From factordb.com home page, if you click on the ? link to the right, you'll get the help link. It has page=0 parameter. There are apparently help pages available for 1 & 2 as well

 2015-05-14, 06:32 #84 Batalov     "Serge" Mar 2008 Phi(4,2^7658614+1)/2 23DF16 Posts True! I saw a similar conceptual disconnect at UTM, but in a rare category. I submitted a partition number and all old submissions were in "p(n)" form. But for PFGW, p(n) is the prime number #n, so for a brief moment the prime was deleted (for being too small), then restored again manually by CC. So, anyway, FactorDB's 10## could be represented as p(10)# in PFGW (and could as well be the same in factorDB, if a prefix function p(n) is implemented). Let's see. PFGW has these built in: p(n), Phi(n,x), gcd(x,y), F(n), L(n), and also U(n), V(n) (primitive parts of F(n), L(n)); doesn't have numbpart(), or bernfrac(), or some other things, -- for them one can use a bridge from GP to PFGW. FactorDB has only a subset of these.
2015-05-14, 06:42   #85
Antonio

"Antonio Key"
Sep 2011
UK

32×59 Posts

Quote:
 Originally Posted by Wick According to the help: # Primordial (product of all primes below n, postfix) ## Product first n primes (postfix) 4# = 6 4## = 210 (2*3*5*7) (4#)# = 30 seems correct?
Factordb is still inconsistent even with it's own definition.
Consider it's solution to 5# =2*3*5 =30, which should be the same as 4# according to it's definition..

2015-05-14, 07:53   #86
Wick

Nov 2012

23×32 Posts

Quote:
 Originally Posted by Batalov 1) That's a very "intuitive" design. If you can show how to get this helpful "help"? except as deduced by this comment that it actually exists, and if so, then it just might be at factordb.com/help ... and in fact this page [B]does[/B] exist, in its own world - not linked to any other pages. 2) nobody uses this notation 3) what is 4### then? and why? and what is 4#### -- is it (4##)## ? (((4#)#)#)# ? ((4#)#)## ? ((4##)#)# ?
next to the factorize button on every page there is a ?. If you click it you go here: http://www.factordb.com/help.php?page=0

 2015-05-27, 15:50 #87 chris2be8     Sep 2009 194810 Posts Factordb seems unreasonably slow processing primorials. Eg the following two PRPs should be easy to prove prime by N-1 but clicking on Primality gets a LONG wait then an incomplete page as if the attempt to calculate how far factored N-1 is timed out. 26901*115637#+1 27545*115637#+1 Chris
 2015-08-03, 19:04 #88 Stargate38     "Daniel Jackson" May 2011 14285714285714285714 26816 Posts What's causing the "err" status on certain numbers? It's breaking 9 of the Aliquot sequences. Here's an example (from 270870): http://factordb.com/index.php?id=1100000000626093582

 Similar Threads Thread Thread Starter Forum Replies Last Post enzocreti FactorDB 0 2018-03-02 09:12 carpetpool FactorDB 6 2017-01-23 11:04 smh FactorDB 231 2015-07-28 02:30 firejuggler Aliquot Sequences 2 2010-06-15 14:03 Raman Factoring 15 2010-01-28 10:24

All times are UTC. The time now is 06:37.

Sat Dec 5 06:37:00 UTC 2020 up 2 days, 2:48, 0 users, load averages: 0.99, 1.37, 1.49