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

Rewrite module doc of LinearCode #20232

Closed
johanrosenkilde opened this issue Mar 19, 2016 · 15 comments
Closed

Rewrite module doc of LinearCode #20232

johanrosenkilde opened this issue Mar 19, 2016 · 15 comments

Comments

@johanrosenkilde
Copy link
Contributor

The module docstring of LinearCode is vastly out of date, is too detailed yet too unspecific and loose, and also has formatting issues.

I suggest completely rewriting it. It is important for guiding new users to be sure to explain the difference between a LinearCode and a specific family subclassing AbstractLinearCode.

CC: @sagetrac-dlucas

Component: coding theory

Author: David Lucas, Johan Sebastian Rosenkilde Nielsen

Branch: 9c82dcd

Reviewer: Johan Sebastian Rosenkilde Nielsen, David Lucas

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

@sagetrac-dlucas
Copy link
Mannequin

sagetrac-dlucas mannequin commented May 24, 2016

Branch: u/dlucas/rewrite_doc_for_linear_code

@sagetrac-dlucas
Copy link
Mannequin

sagetrac-dlucas mannequin commented May 24, 2016

comment:2

Hello,

I rewrote the module docstring of linear_code.py. To be more specific, I:

  • completely removed the old docstring, which was, imho, focused on mathematical details and advanced specificities,
  • wrote a very small definition of a linear code,
  • explained the difference between AbstractLinearCode and LinearCode, and
  • gave pointers to more detailed content (thematic tutorials).

I'm setting this to needs_review.

David


New commits:

9cbca19Rewrote module documentation for linear_code.py

@sagetrac-dlucas
Copy link
Mannequin

sagetrac-dlucas mannequin commented May 24, 2016

Commit: 9cbca19

@sagetrac-dlucas sagetrac-dlucas mannequin modified the milestones: sage-7.1, sage-7.3 May 24, 2016
@johanrosenkilde
Copy link
Contributor Author

comment:3

This is a much-needed improvement to sage.coding!

@johanrosenkilde
Copy link
Contributor Author

@johanrosenkilde
Copy link
Contributor Author

comment:5

Hi,

I've gone through the documentation and it's pretty good. I've pushed some suggested modifications to the text, in particular mentioning a few more keywords as well as emphasising the difference between generic codes and families. The latter lead to a slight restructuring of your description of AbstractLinearCode and LinearCode.

Let me know what you think, and we can co-review the ticket.

I also promoted linear_code in the reference manual module index, so that it figures first in its respective category. However, that lead me to thinking that perhaps some of this text should go there (not necessarily in this ticket)? What do you think -- where do people look?

Best,
Johan


New commits:

3b0140eA few more details on what a code is along with some keywords
1efb48eMore on "families" vs generic codes, and suggestions on [Abstract]LinearCode
9c82dcdSome polishing, and promote linear_code in documentation index

@johanrosenkilde
Copy link
Contributor Author

Changed commit from 9cbca19 to 9c82dcd

@sagetrac-dlucas
Copy link
Mannequin

sagetrac-dlucas mannequin commented May 25, 2016

comment:6

Hello,

Let me know what you think, and we can co-review the ticket.

I'm fine with your changes. It's indeed better to emphasise the difference between generic codes and families, as I'm not it's standard terminology so the more specific, the better.
I also agree with the definition of encoding, dual codes, etc: these are very useful concepts which deserve to be defined here.

I also promoted linear_code in the reference manual module index, so that it figures first in its respective category. However, that lead me to thinking that perhaps some of this text should go there (not necessarily in this ticket)? What do you think -- where do people look?

I think we should left it as is: this file is supposed to be an index, as in any book, and when you're browsing an index, you usually expect quick access to the entry you're looking for - not some definitions. That's why I changed the name of the entry, from Linear codes to Generic structures for linear codes: with this new name, one knows exactly what to expect when one clicks on this entry.

Best,

David

@johanrosenkilde
Copy link
Contributor Author

comment:7

I think we should left it as is: this file is supposed to be an index, as in any book, and when you're browsing an index, you usually expect quick access to the entry you're looking for - not some definitions. That's why I changed the name of the entry, from Linear codes to Generic structures for linear codes: with this new name, one knows exactly what to expect when one clicks on this entry.

That makes sense -- let's keep it. Let's think about whether we could leverage SageDays 75 for getting some input on the documentation. Some beginners might have valuable feedback.

@johanrosenkilde
Copy link
Contributor Author

Author: David Lucas, Johan S. R. Nielsen

@johanrosenkilde
Copy link
Contributor Author

Reviewer: Johan S. R. Nielsen, David Lucas

@vbraun
Copy link
Member

vbraun commented May 26, 2016

Changed branch from u/jsrn/rewrite_doc_for_linear_code to 9c82dcd

@fchapoton
Copy link
Contributor

Changed reviewer from Johan S. R. Nielsen, David Lucas to Johan Sebastian Rosenkilde Nielsen, David Lucas

@fchapoton
Copy link
Contributor

Changed commit from 9c82dcd to none

@fchapoton
Copy link
Contributor

Changed author from David Lucas, Johan S. R. Nielsen to David Lucas, Johan Sebastian Rosenkilde Nielsen

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

3 participants