Re: 2 maple important bugs, ifactor(10000!);pi(500000000);
devore_at_math.udel.edu
Date: 01/28/05
- Next message: Richard J. Fateman: "Re: 2 maple important bugs, ifactor(10000!);pi(500000000);"
- Previous message: devore_at_math.udel.edu: "Re: Maple modules"
- In reply to: J. Papp: "Re: 2 maple important bugs, ifactor(10000!);pi(500000000);"
- Next in thread: JacquesC: "Re: 2 maple important bugs, ifactor(10000!);pi(500000000);"
- Messages sorted by: [ date ] [ thread ]
Date: 28 Jan 2005 14:35:33 -0800
"J. Papp" Jan 27, 4:20 am show options
Newsgroups: sci.math.symbolic
From: j...@gmail.com ("J. Papp") - Find messages by this author
Date: Thu, 27 Jan 2005 12:20:41 +0000 (UTC)
Local: Thurs, Jan 27 2005 4:20 am
Subject: Re: 2 maple important bugs, ifactor(10000!);pi(500000000);
Reply | Reply to Author | Forward | Print | Individual Message | Show
original | Report Abuse
J Papp wrote:
> Simon Plouffe wrote:
> > with(numtheory):pi(500000000) took 985 seconds.
>
> This is very funny! In fact try:
> > pi(100000006); #instantly
> > pi(100000007); #I can't wait, I'm on a PII
> I suspected it has something to do with Digits, but no.
> Maybe someone has an explanation.
Maple has no fancy algorithm for pi. It is a brute force approach,
with some values precomputed. Some numbers are done quickly because of
their relation to the precomputed values.
To see the relevant procedures and the precomputed values do:
kernelopts(opaquemodules= false):
interface(verboseproc= 3): # not 2.
print(numtheory:-pi_internal);
print(`ithprime/large`);
- Next message: Richard J. Fateman: "Re: 2 maple important bugs, ifactor(10000!);pi(500000000);"
- Previous message: devore_at_math.udel.edu: "Re: Maple modules"
- In reply to: J. Papp: "Re: 2 maple important bugs, ifactor(10000!);pi(500000000);"
- Next in thread: JacquesC: "Re: 2 maple important bugs, ifactor(10000!);pi(500000000);"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
