#10581: change Large Cremona database format and extend it
-------------------------------+--------------------------------------------
   Reporter:  gagansekhon      |       Owner:  cremona                          
                 
       Type:  enhancement      |      Status:  new                              
                 
   Priority:  minor            |   Milestone:  sage-5.0                         
                 
  Component:  elliptic curves  |    Keywords:  cremona, stein, watkins, 
elliptic curves, database
     Author:                   |    Upstream:  N/A                              
                 
   Reviewer:                   |      Merged:                                   
                 
Work_issues:                   |  
-------------------------------+--------------------------------------------

Comment(by cremona):

 Is there any point in including SW curves of conductor < 130000 which are
 already in my database?

 For conductor > 130000 I think it is a good idea to add the prefix sw.

 I have scripts to create all of the files in the format at
 http://www.warwick.ac.uk/staff/J.E.Cremona/ftp/data/
 from a single file containing just one curve in each isogeny class, i.e.
 from a file like
 http://www.warwick.ac.uk/staff/J.E.Cremona/ftp/data/allcurves.00000-09999
 but only containing the lines where field #3 ==1 (and called
 curves.00000-09999).

 So all that would be needed for the SW part of this would be to create
 from the SW database such a file, but sorting the curves by conductor and
 then (arbitrarily, or intelligently) sorting the isogeny classes.

 Now if someone also re-writes the existing Sage scripts (in
 sage/databases/cremona.py) to create mogodb files instead of the old style
 db files, all that would be needed would be to run those after the ones I
 have written.  On the other hand, at this point there would be no point
 (perhaps) in having all the intermediate plain text files at all:
 instead,  we could go directly from a single curves.* file to the complete
 mongodb.

 Small asides: 1. in the scripts I am writing I used Magma's HeegnerPoint
 function to get generators for (some) rank 1 curves.  2. Despite what I
 said above I have not yet written the (easy) scripts for the aplist,
 degphi and intpts data files, since I have had other duties to perform...

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10581#comment:7>
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