[sage-devel] Re: prime_pi gives wrong output

This is a known bug. The additional example could be added as a comment on trac ticket #24960 . On Friday, November 12, 2021 at 12:49:24 PM UTC-7 martin@gmail.com wrote: > Hello, > > prime_pi(281474961965055) gives correct output 8731188419994. > > pr

[sage-devel] Re: prime_pi plotting preposterousness

On 7/18/12 8:57 AM, Jason Grout wrote: Gee, it'd be nice if there was a way to provide plugins for the plot command. I could see, for example, prime_pi providing a "sample" plugin that would provide a custom sampling routine, but otherwise using the standard plotting functionality. In fact, t

Re: [sage-devel] Re: prime_pi plotting preposterousness

On Wed, 18 Jul 2012 at 08:57AM -0500, Jason Grout wrote: > Gee, it'd be nice if there was a way to provide plugins for the plot > command. I could see, for example, prime_pi providing a "sample" > plugin that would provide a custom sampling routine, but otherwise > using the standard plotting func

[sage-devel] Re: prime_pi plotting preposterousness

On 7/18/12 8:47 AM, kcrisman wrote: On Wednesday, July 18, 2012 9:41:40 AM UTC-4, Dan Drake wrote: On Wed, 18 Jul 2012 at 01:00AM -0500, Jason Grout wrote: > IIRC, if A.plot exists, then plot(A, ...) will call A.plot(...). I > think plot(prime_pi, ...) *is* using the custom plot

Re: [sage-devel] Re: prime_pi plotting preposterousness

On Wednesday, July 18, 2012 9:41:40 AM UTC-4, Dan Drake wrote: > > On Wed, 18 Jul 2012 at 01:00AM -0500, Jason Grout wrote: > > IIRC, if A.plot exists, then plot(A, ...) will call A.plot(...). I > > think plot(prime_pi, ...) *is* using the custom plotting method > > always. The problem is tha

Re: [sage-devel] Re: prime_pi plotting preposterousness

On Wed, 18 Jul 2012 at 01:00AM -0500, Jason Grout wrote: > IIRC, if A.plot exists, then plot(A, ...) will call A.plot(...). I > think plot(prime_pi, ...) *is* using the custom plotting method > always. The problem is that the prime_pi.plot method is very > limited, and doesn't recognize prime_pi.p

[sage-devel] Re: prime_pi plotting preposterousness

On Wednesday, July 18, 2012 2:00:58 AM UTC-4, jason wrote: > > On 7/18/12 12:50 AM, Dan Drake wrote: > > On Tue, 17 Jul 2012 at 10:27PM -0700, R. Andrew Ohana wrote: > >> This is kind of fixed by #11475 (in that prime_pi becomes part of the > >> symbolic ring). > > > > Cool. > > > >> The b

[sage-devel] Re: prime_pi plotting preposterousness

On 7/18/12 12:50 AM, Dan Drake wrote: On Tue, 17 Jul 2012 at 10:27PM -0700, R. Andrew Ohana wrote: This is kind of fixed by #11475 (in that prime_pi becomes part of the symbolic ring). Cool. The bigger issue is that the symbolic ring does sampling for plotting, which is horribly inefficient

[sage-devel] Re: prime_pi for large parallel machines

Robert Bradshaw wrote: > Actually, the clever algorithm is very parallelizable, so you could > have the best of both worlds. > > - Robert That would be interesting. The Mathematica does have some arbitrary limit on the maximum size it will handle. I forget what it is, but it would be good

[sage-devel] Re: prime_pi for large parallel machines

On Jul 9, 2009, at 2:32 AM, Dr. David Kirkby wrote: > There was some discussion a month or two back about different > algorithms > for prime_pi. IIRC, Mathematica's was the fastest, Sage's was second > fastest and Maple's method was dumb and just counted them like a 10 > year > old could do.

[sage-devel] Re: prime_pi

On May 5, 4:40 am, Michel wrote: > I always get > > /home/sage/sage_install/sage-a/local/bin/sage-sage: line 348: 26501 > Segmentation fault      python "$@" > Connection to localhost closed. > > when trying prime_pi onwww.sagenb.org sagenb.org still runs 3.4.1 which has the bad/inefficient ve

[sage-devel] Re: prime_pi

I always get /home/sage/sage_install/sage-a/local/bin/sage-sage: line 348: 26501 Segmentation fault python "$@" Connection to localhost closed. when trying prime_pi on www.sagenb.org Regards, Michel On May 5, 4:32 am, William Stein wrote: > This is from the guy who wrote prime_pi: > > --