#10963: More functorial constructions
-------------------------------------+-------------------------------------
       Reporter:  nthiery            |        Owner:  stumpc5
           Type:  enhancement        |       Status:  needs_review
       Priority:  major              |    Milestone:  sage-5.13
      Component:  categories         |   Resolution:
       Keywords:                     |    Merged in:
        Authors:  Nicolas M. Thiéry  |    Reviewers:  Simon King, Frédéric
Report Upstream:  N/A                |  Chapoton
         Branch:                     |  Work issues:
   Dependencies:  #11224, #8327,     |       Commit:
  #10193, #12895, #14516, #14722,    |     Stopgaps:
  #13589, #14471, #15069, #15094,    |
  #11688, #13394                     |
-------------------------------------+-------------------------------------

Comment (by SimonKing):

 The lines around the error (line 6478) are
 {{{
         sage: E = EllipticCurve([0, 0, 1, -34874, -2506691])
         sage: E.heegner_index(-8)
         Traceback (most recent call last):
         ...
         RuntimeError: ...
 }}}
 Hence, we test against a runtime error with unspecified error message. Let
 us see which, and let us test the memory consumption.

 First, with the branch from #13394:
 {{{
 sage: get_memory_usage()
 190.30078125
 sage: E = EllipticCurve([0, 0, 1, -34874, -2506691])
 sage: get_memory_usage()
 190.7265625
 sage: E.heegner_index(-8)
 Unable to compute the rank with certainty (lower bound=0).
 This could be because Sha(E/Q)[2] is nontrivial.
 Try calling something like two_descent(second_limit=13) on the
 curve then trying this command again.  You could also try rank
 with only_use_mwrank=False.
 ---------------------------------------------------------------------------
 RuntimeError                              Traceback (most recent call
 last)
 ...
 RuntimeError: Rank not provably correct.
 sage: get_memory_usage()
 193.0625
 }}}
 Now, with my local branch that I've created for the patch from here:
 {{{
 sage: get_memory_usage()
 191.50390625
 sage: E = EllipticCurve([0, 0, 1, -34874, -2506691])
 sage: get_memory_usage()
 191.6328125
 sage: E.heegner_index(-8)
 ...
 RuntimeError: Rank not provably correct.
 sage: get_memory_usage()
 194.25390625
 }}}
 So, it seems that the memory consumption has just increased by a constant
 amount. Also note that
 {{{
 ulimit -v 2300000; ./sage -t --long
 src/sage/schemes/elliptic_curves/heegner.py
 Running doctests with ID 2013-11-04-23-46-03-6fbd5fa5.
 Doctesting 1 file.
 sage -t --long src/sage/schemes/elliptic_curves/heegner.py
     [1072 tests, 104.05 s]
 ----------------------------------------------------------------------
 All tests passed!
 ----------------------------------------------------------------------
 Total time for all tests: 106.1 seconds
     cpu time: 97.4 seconds
     cumulative wall time: 104.0 seconds
 }}}
 works for me. I'll try to decrease the memory limit.

--
Ticket URL: <http://trac.sagemath.org/ticket/10963#comment:155>
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 http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to