#7013: [with patch, needs work] prime_pi and nth_prime
----------------------------------------+-----------------------------------
   Reporter:  kevin.stueve              |       Owner:  kevin.stueve            
       Type:  enhancement               |      Status:  needs_work              
   Priority:  major                     |   Milestone:  sage-5.0                
  Component:  number theory             |    Keywords:  primes, sieve, table,LMO
     Author:  Kevin Stueve              |    Upstream:  N/A                     
   Reviewer:  was,robertwb,GeorgSWeber  |      Merged:                          
Work_issues:                            |  
----------------------------------------+-----------------------------------

Comment(by kevin.stueve):

 I updated our prime counting code to use denser tables from TOS, TRN, and
 Kulsha, and an updated version of TOS's prime_sieve.c from Leif.  Consider
 my Python code still a rough draft.  I haven't tested it.  It would be
 nice to see this code get finalized, polished, peer reviewed, and
 implemented in the online version of Sage and also provided as an optional
 package for the downloaded version of Sage.

 Right now the interval [1e14,1e15] has spacing 1e10.  It would be nice,
 and not too difficult to sieve this interval with prime_sieve.c on
 Sagemath with spacing 1e9.  This would be good to compare against Andrew
 Booker's new data he is going to calculate.
 
http://sage.math.washington.edu/home/kstueve/uploads/March21_2010/TableBasedPrimePi.zip

 Kevin Stueve

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/7013#comment:47>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to