#20693: Sage crashes when computing newforms
---------------------------------+------------------------
       Reporter:  ehlen          |        Owner:
           Type:  defect         |       Status:  new
       Priority:  critical       |    Milestone:  sage-7.3
      Component:  modular forms  |   Resolution:
       Keywords:                 |    Merged in:
        Authors:                 |    Reviewers:
Report Upstream:  N/A            |  Work issues:
         Branch:                 |       Commit:
   Dependencies:                 |     Stopgaps:
---------------------------------+------------------------

Comment (by pbruin):

 Replying to [comment:4 ehlen]:
 > I would like to add a remark: something really extremely bad happened
 with the implementation of relative Number Fields.
 > It was always slow but now, and this might be related to this crash
 here, spaces that I computed using older versions of sage (6.1 to be
 concrete and give a pointer) within minutes or up to an hour or a bit
 more, do not finish to be computed within a day now. A concrete example is
 Gamma0(19), character {{{[zeta18^2]}}}, weight 14. I had the modular
 symbols space computed with sage 6.1 and stored the cputime used to
 compute it: 3780s. And now it didn't finish within 7 hours.
 With the same branches applied as in comment:18, I tried
 {{{
 %prun Newforms(DirichletGroup(19)[2], 14, names='a')
 }}}
 and got a similar NTL crash as in comment:17 after about 1.5 hours.

--
Ticket URL: <http://trac.sagemath.org/ticket/20693#comment:19>
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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to