Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lots of files in sage.schemes.elliptic_curves are not included in the reference manual #4933

Closed
JohnCremona opened this issue Jan 3, 2009 · 19 comments

Comments

@JohnCremona
Copy link
Member

The following files have useful docstrings but are not included in the ref manual (judging from 3.2.3), all in sage.schemes.elliptic_curves.

  • cm.py
  • ec_database.py
  • ell_field.py
  • ell_local_data.py
  • ell_modular_symbols
  • ell_number_field
  • ell_padic_field
  • ell_point.py
  • ell_tate_curve.py
  • ell_torsion.py
  • kodaira_symbol.py
  • lseries_ell.py
  • padic_lseries.py
  • period_lattice.py
  • sha_tate.py
  • weierstrass_morphism.py

Component: documentation

Issue created by migration from https://trac.sagemath.org/ticket/4933

@sagetrac-GeorgSWeber
Copy link
Mannequin

sagetrac-GeorgSWeber mannequin commented Feb 25, 2009

comment:1

Hi,

the files

  • ell_modular_symbols.py
  • ell_tate_curve.py
  • padic_lseries.py
  • sha_tate.py

are not only enhanced in a vital way but also considerably cleaned up docstring- and comment-wise by #4667. The patch there is currently based against 3.3 and needs a rebase concerning two files (ell_rational_field.py, padocs.py) against 3.4 series, and there is still one doctest failure, but nevertheless I do consider #4667 worth of applying before working on this very ticket here!

@sagetrac-mabshoff
Copy link
Mannequin

sagetrac-mabshoff mannequin commented Mar 1, 2009

comment:2

Better luck in 3.4.1.

Cheers,

Michael

@sagetrac-mabshoff sagetrac-mabshoff mannequin modified the milestones: sage-3.4, sage-3.4.1 Mar 1, 2009
@JohnCremona
Copy link
Member Author

Attachment: trac_4933-1.patch.gz

@JohnCremona
Copy link
Member Author

comment:3

I have attached a patch trac_4933-1.patch which does this for three files:

  • ell_number_field.py
  • ell_torsion.py
  • ell_point.py
    which is a start.

The patch rewrites all the docstrings in those files and also adds them to the list of files which are processed by "sage -docbuild reference" so that they show up in the reference manual.

To review/test the patch (which was based on 3.4.1.rc2), you need to apply it and rebuild, and then (1) do "sage -t" is usual on the files affected, and (2) do "sage -docbuild reference pdf/html/whatever" to check that the documentation looks good.

@JohnCremona
Copy link
Member Author

Attachment: trac_4933-2.patch.gz

Two more; apply after previous.

@JohnCremona
Copy link
Member Author

comment:4

The second patch adds a couple more files (weierstrass_morphism and period_lattice).

@JohnCremona JohnCremona changed the title lots of files in sage.schemes.elliptic_curves are not included in the reference manual [not ready for review] lots of files in sage.schemes.elliptic_curves are not included in the reference manual Apr 16, 2009
@JohnCremona
Copy link
Member Author

Attachment: trac_4933-3.patch.gz

IGNORE all previous patches. This is based on 3.4.1.rc3

@JohnCremona
Copy link
Member Author

comment:6

The patch trac_4933-3.patch converts the following to rest/sphinx and adds them to the reference manual:

  • ell_number_field
  • ell_local_data
  • ell_torsion
  • ell_point
  • period_lattice
  • weierstrass_morphism
    as well as fixing some glitches in other files (notable ell_rational_field) and adding a few doctests.

Almost all the changes are in docstrings. To review this you'll have to build the docs (reference manual) and eyeball the output.

NB I combined more than one earlier patch into one, but failed to get "sage -hg qfold" to work, so i nthe patch there are liable to be more than one chunk for each file.

@JohnCremona JohnCremona changed the title [not ready for review] lots of files in sage.schemes.elliptic_curves are not included in the reference manual lots of files in sage.schemes.elliptic_curves are not included in the reference manual Apr 17, 2009
@jhpalmieri
Copy link
Member

comment:7

If you're patching ell_rational_field, can you fix the doc string for mwrank? It looks pretty garbled to me, and I don't know what it's supposed to say...

@JohnCremona
Copy link
Member Author

comment:8

Replying to @jhpalmieri:

If you're patching ell_rational_field, can you fix the doc string for mwrank? It looks pretty garbled to me, and I don't know what it's supposed to say...

It looks pretty clear to me, except perhaps where it explains the format of the options string. Perhaps we should just include the output of "sage -mwrank -h":

mwrank command line options (can be in any order):

-h      help            prints this info and quits
-q      quiet           turns OFF banner display
-v n    verbosity       sets verbosity to n (default=1)
-o      PARI/GP output  turns ON extra PARI/GP short output (default is OFF)
-p n    precision       sets precision to n decimals (default=15)
                        (irrelevant unless compiled with multiprecision option)
-b n    quartic bound   bound on quartic point search (default=10)
-x n    n aux           number of aux primes used for sieving (default=6)
-l      list            turns ON listing of points (default ON unless v=0)
-t      trace           turns ON trace of quartic equivalence testing (debugging only)
-s      selmer_only     if set, computes Selmer rank only (default: not set)
-d      skip_2nd_descent        if set, skips the second descent for curves with 2-torsion (default: not set)
-S n    sat_bd          upper bound on saturation primes (default=100, -1 for automatic)

@jhpalmieri
Copy link
Member

comment:9

It looks pretty clear to me, except perhaps where it explains the format of the options string.

Do you mean this part?

        -  ``options`` - string; passed when starting mwrank.
           The format is q pprecision vverbosity bhlim_q xnaux chlim_c l t o
           s d]

@JohnCremona
Copy link
Member Author

comment:10

Replying to @jhpalmieri:

It looks pretty clear to me, except perhaps where it explains the format of the options string.

Do you mean this part?

        -  ``options`` - string; passed when starting mwrank.
           The format is q pprecision vverbosity bhlim_q xnaux chlim_c l t o
           s d]

Yes!

@JohnCremona
Copy link
Member Author

Attachment: trac_4933-3-rebase.patch.gz

Replaces previous; based on 3.4.1.rc3 + #5808 patch

@JohnCremona
Copy link
Member Author

comment:11

The new patch (trac_4933-3-rebase.patch) replaces the earlier one as it applies cleanly to 3.4.1.rc3 + ref-warnings.patch from #5808. It also answers John Palmieri's request to make the docstring for mwrank() less confusing.

I think the reason that this one is smaller is that the previous one applied several patches in succession to the same files, while this one does not. At least, I hope that is the reason.

@jhpalmieri
Copy link
Member

comment:12

Code looks good, all tests pass, the reference manual looks nice. I'm attaching a referee's patch with two very small changes.

@jhpalmieri
Copy link
Member

apply on top of the other patch

@JohnCremona
Copy link
Member Author

comment:13

Attachment: 4933-ref.patch.gz

Replying to @jhpalmieri:

Code looks good, all tests pass, the reference manual looks nice. I'm attaching a referee's patch with two very small changes.

Thanks John -- I am quite happy with your adjustments.

@sagetrac-mabshoff
Copy link
Mannequin

sagetrac-mabshoff mannequin commented Apr 18, 2009

comment:14

Merged trac_4933-3-rebase.patch and 4933-ref.patch in Sage 3.4.1.rc4.

Cheers,

Michael

@sagetrac-mabshoff sagetrac-mabshoff mannequin closed this as completed Apr 18, 2009
@sagetrac-mabshoff sagetrac-mabshoff mannequin modified the milestones: sage-3.4.2, sage-3.4.1 Apr 18, 2009
@JohnCremona
Copy link
Member Author

comment:15

This is continued in #5851.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants