#18916: Use Kedlaya algorithm to count points on hyperelliptic curves
-------------------------------------+-------------------------------------
       Reporter:  jpflori            |        Owner:
           Type:  enhancement        |       Status:  new
       Priority:  major              |    Milestone:  sage-6.8
      Component:  number fields      |   Resolution:
       Keywords:  hyperelliptic      |    Merged in:
  curves, matrix of Frobenius        |    Reviewers:
        Authors:  Kiran Kedlaya      |  Work issues:
Report Upstream:  Fixed upstream,    |       Commit:
  but not in a stable release.       |  6ca4b8c808ba9a53a17ce061a96ecbabea58d595
         Branch:                     |     Stopgaps:
  u/kedlaya/use_kedlaya_algorithm_to_count_points_on_hyperelliptic_curves|
   Dependencies:  #20219             |
-------------------------------------+-------------------------------------

Comment (by kedlaya):

 Replying to [comment:28 jpflori]:
 > @Kiran: is it in state of review or do you plan further changes?

 Even after rebasing to 7.2.rc1, there is still one failing doctest:
 {{{
 File
 "src/sage/schemes/hyperelliptic_curves/hyperelliptic_finite_field.py",
 line 1348, in
 
sage.schemes.hyperelliptic_curves.hyperelliptic_finite_field.HyperellipticCurve_finite_field.zeta_funct
 ion
 Failed example:
     H.zeta_function()
 Exception raised:
     Traceback (most recent call last):
       File
 "/projects/b8cc019c-1204-44b1-bea9-eb81c119388e/sage/local/lib/python2.7
 /site-packages/sage/doctest/forker.py", line 496, in _run
         self.compile_and_execute(example, compiler, test.globs)
       File
 "/projects/b8cc019c-1204-44b1-bea9-eb81c119388e/sage/local/lib/python2.7
 /site-packages/sage/doctest/forker.py", line 858, in compile_and_execute
         exec(compiled, globs)
       File "<doctest
 
sage.schemes.hyperelliptic_curves.hyperelliptic_finite_field.HyperellipticCurve_finite_field.zeta_function[8]>",
 line 1, in <module>
         H.zeta_function()
       File
 "/projects/b8cc019c-1204-44b1-bea9-eb81c119388e/sage/local/lib/python2.7
 /site-
 packages/sage/schemes/hyperelliptic_curves/hyperelliptic_finite_field.py",
 line 1364, in zeta_function
         P = self.frobenius_polynomial()
       File "sage/misc/cachefunc.pyx", line 2235, in
 sage.misc.cachefunc.CachedMethodCallerNoArgs.__call__
 
(/projects/b8cc019c-1204-44b1-bea9-eb81c119388e/sage/src/build/cythonized/sage/misc/cac
 hefunc.c:12462)
         self.cache = f(self._instance)
       File
 "/projects/b8cc019c-1204-44b1-bea9-eb81c119388e/sage/local/lib/python2.7
 /site-
 packages/sage/schemes/hyperelliptic_curves/hyperelliptic_finite_field.py",
 line 551, in frobenius_polyno
 mial
         return self.frobenius_polynomial_pari()
       File
 "/projects/b8cc019c-1204-44b1-bea9-eb81c119388e/sage/local/lib/python2.7
 /site-
 packages/sage/schemes/hyperelliptic_curves/hyperelliptic_finite_field.py",
 line 473, in frobenius_polyno
 mial_pari
         return ZZ['x'](pari([f, h]).hyperellcharpoly())
       File "sage/libs/pari/auto_gen.pxi", line 8650, in
 sage.libs.pari.gen.gen_auto.hyperellcharpoly
 
(/projects/b8cc019c-1204-44b1-bea9-eb81c119388e/sage/src/build/cythonized/sage/libs/pari/gen
 .c:47546)
         sig_on()
       File "src/cysignals/signals.pyx", line 108, in
 cysignals.signals.sig_raise_exception (build/src/cysignals/signals.c:1448)
     SignalError: Segmentation fault
 }}}
 As noted above, this is due to a bug in PARI which has been fixed
 upstream. To resolve this, we need to pull from upstream, which is
 probably worth a separate ticket.

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