ell_rational_field.py and the file PRIMES

2 views
Skip to first unread message

John H Palmieri

unread,
Feb 24, 2010, 11:38:01 PM2/24/10
to sage-devel
When I run doctests on the file ell_rational_field.py, I end up with a
small file called PRIMES in the current directory. This shouldn't
happen: running doctests shouldn't produce files in a non-temporary
directory. However, I can't figure out how this file gets there. In
particular, if I delete the following doctests from the rank method,
then the file is not produced:

{{{
diff -r 23241bd151e3 sage/schemes/elliptic_curves/
ell_rational_field.py
--- a/sage/schemes/elliptic_curves/ell_rational_field.py Thu
Feb 18 14:25:25 2010 -0800
+++ b/sage/schemes/elliptic_curves/ell_rational_field.py Wed
Feb 24 20:37:09 2010 -0800
@@ -1679,14 +1679,6 @@
sage: E.minimal_model().rank()
1

- A large example where mwrank doesn't determine the result
with certainty::
-
- sage: EllipticCurve([1,0,0,0,37455]).rank(proof=False)
- 0
- sage: EllipticCurve([1,0,0,0,37455]).rank(proof=True)
- Traceback (most recent call last):
- ...
- RuntimeError: Rank not provably correct.
"""
if proof is None:
from sage.structure.proof.proof import get_flag
}}}

If I run these by hand from the command line, though, I don't see the
file PRIMES anywhere. Can someone familiar with the elliptic curves
code open a ticket, chase this down, and fix it?

--
John

Pat LeSmithe

unread,
Feb 25, 2010, 1:06:25 AM2/25/10
to sage-...@googlegroups.com
On 02/24/2010 08:38 PM, John H Palmieri wrote:
> When I run doctests on the file ell_rational_field.py, I end up with a
> small file called PRIMES in the current directory. This shouldn't
> happen: running doctests shouldn't produce files in a non-temporary
> directory. However, I can't figure out how this file gets there. In
> particular, if I delete the following doctests from the rank method,
> then the file is not produced:
> [...]

> If I run these by hand from the command line, though, I don't see the
> file PRIMES anywhere. Can someone familiar with the elliptic curves
> code open a ticket, chase this down, and fix it?

There's some progress on the problem at the originating ticket

http://trac.sagemath.org/sage_trac/ticket/7575#comment:24

This is now

http://trac.sagemath.org/sage_trac/ticket/8357

John Cremona

unread,
Feb 25, 2010, 4:18:47 AM2/25/10
to sage-...@googlegroups.com
Minh and I have been trying to track this down: the file is created
by eclib, and written out when certain C++ classes have their
destructors called. The mystery is less why it appears, as why
sometimes it doesn't. But as (of course) no-one likes it, I will sort
it out by making upstream changes in eclib.

The intention, by the way, is for the user to help various
factorizations by seeding the prime base with suitable known primes.
And the relevant parts of eclib have not changed since before Sage was
born! the reason that this is arising now seems to be just that we
are using more of eclib functionality, which has to be a good thing ;)

John

> --
> To post to this group, send an email to sage-...@googlegroups.com
> To unsubscribe from this group, send an email to sage-devel+...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/sage-devel
> URL: http://www.sagemath.org
>

Reply all
Reply to author
Forward
0 new messages