Ticket #3347 (closed defect: fixed)
[with patches, positive review] lots of changes to the tutorial
| Reported by: | jhpalmieri | Owned by: | jhpalmieri |
|---|---|---|---|
| Priority: | major | Milestone: | sage-3.0.4 |
| Component: | documentation | Keywords: | tutorial, editor_mhansen |
| Cc: | Work issues: | ||
| Report Upstream: | Reviewers: | ||
| Authors: | Merged in: | ||
| Dependencies: | Stopgaps: |
Description
I've been working on rewriting the tutorial, moving sections around, deleting things, adding things, etc. I'm done with a first draft of the "guided tour" (chapter 2). I'll try to get to the rest eventually.
Please let me know if I've deleted your very favorite section or something like that...
Attachments
Change History
Changed 5 years ago by jhpalmieri
-
attachment
3347-1.patch
added
comment:1 Changed 5 years ago by jhpalmieri
Two additional comments: first, the file macros-new.tex is very similar to macros.tex, but I didn't want to break anything in the other parts of the documentation, so tut.tex now calls macros-new.tex while macros.tex is still intact. The main difference here is that macros-new.tex contains the line \usepackage{html}, which allows for the use of commands which are parsed one way when the file is run through latex (or pdflatex), and another way when run through latex2html. It also defines a few commands which rely on this.
Second, when I was editing the tutorial and running 'make tut' and 'make paper-letter/tut.pdf', for some reason the .aux file wasn't being regenerated, so it kept building with the old .aux file. This screwed up all of the cross-references. I don't know if this has to do with my set-up, but if not, be warned that you might get errors unless you do something like (1) manually set TEXINPUTS to be the right thing, and then (2) going to doc/tut/ and running 'pdflatex tut' a few times to update the .aux file. (You might also want to run 'makeindex tut' while you're there, just for kicks.)
comment:2 Changed 5 years ago by TimothyClemans
- Summary changed from [with patches, needs review] lots of changes to the tutorial to [with patches, negative review] lots of changes to the tutorial
Hi,
Could you explain why you removed the section on Distributed Computing, section 2.13? Right now I don't agree with the removal of that section. I helped with reviewing it several months back and found it very accessible.
The Table of Contents needs to be updated, for example:
2.1 Arithmetical binary operator precedence 2.2 Assignment, Equality, Functions, Indentation, and Counting 2.3 Basic, and not-so-basic, Rings ... etc
to
2.1 Assignment, Equality, and Arithmetic 2.2 Getting Help 2.3 Functions, Indentation, and Counting ... etc
comment:3 Changed 5 years ago by TimothyClemans
- Summary changed from [with patches, negative review] lots of changes to the tutorial to [with patches, mostly positive review] lots of changes to the tutorial
Hi,
I made a mistake with the summary. My review is mostly positive.
Sorry about the mistake.
comment:4 Changed 5 years ago by jhpalmieri
Thanks for the comments.
Regarding the table of contents, that may be related to the .aux file problem that I mentioned. In any case, the table of contents should be regenerated automatically from the tex file.
Regarding the distributed computing stuff, I don't mind putting it back, but I think it doesn't belong in the guided tour (chapter 2). Maybe it belongs in its own chapter, between the current chapters 5 (programming) and 6 (afterword). I was also thinking that maybe it didn't belong in a tutorial: a tutorial is not supposed to be a complete reference guide, and I was wondering if this material was perhaps too specialized.
I also found that section choppy: several very short subsections, with titles like "Introduction", "Overview", and "Quick start". These should probably be combined into one subsection, or maybe two. I was also a little nervous about whether this whole section was actually complete, because there were some lines commented out like
% \subsection{Deploying dsage} % (fold)
% To be written...
% % section deploying_workers (end)
%
% \subsection{Upgrading workers} % (fold)
%
% % subsection upgrading_workers (end)
If you think it's okay with these parts missing, and if you think that this material belongs in the tutorial (not just in the reference guide or somewhere else), I'm fine putting it back (but later in the tutorial). At some point, I think it needs some tightening and rewriting. Let me know, and I'll make a new patch reinstating it.
comment:5 Changed 5 years ago by TimothyClemans
I certainly think the DSage guide should be in the tutorial somewhere. The section is far more general than say number theory or elliptic curves. I wouldn't worry about finishing the section, but please put it back into the tutorial.
comment:6 Changed 5 years ago by jhpalmieri
Okay, here's a new version of the patch. This replaces the old one; the difference is that the dsage stuff has been reinstated (with minor rewordings and re-organization: I combined several sections).
comment:7 Changed 5 years ago by TimothyClemans
- Summary changed from [with patches, mostly positive review] lots of changes to the tutorial to [with patches, needs review] lots of changes to the tutorial
comment:9 Changed 5 years ago by jhpalmieri
In case it makes things easier for anyone, I've posted a pdf version of the tutorial here:
http://www.math.washington.edu/~palmieri/Sage/tut/tut.pdf
(I produced this on my linux box, which results in a first page which says "-1 = -1". I don't know why. When I do it on my mac, this doesn't happen.)
The html version is also there, in case you want to look at that (although latex2html always seems to be a bit flaky when I use it):
http://www.math.washington.edu/~palmieri/Sage/tut/index.html
comment:10 Changed 5 years ago by wdj
I printed the tutorial and read it over. It seems to flow better but I have a few minor comments.
- It would be great if you could get rid of *all* the cases where the text runs into the margins even a tiny bit. The reason why is that for the amazon version of the book (uploaded via createspace.com, as opposed to lulu.com) *any* margin overruns result in the *entire* book being rejected automatically. I fould overruns on pages 8, 16 and 68, but may have missed some.
- At some point, "SAGE Constructions will go away and be replaced by "SAGE Cookbook". It would not hurt to simply remove the references to the "Constructions" document now.
- The Examples on page 49 and 52 (which actually started on p 51) have a SAGE banner stating that SAGE is licensed under the GPLv2. Since this has changed to GPLv2+, my feeling is that the examples should be updated to prevent misleading information from leaking out.
- On page 82, one reads
sage: w # random 0x number <generator object at 0xb0853d6c>
I wonder if
sage: w # vvvvvvvvvv random 0x number <generator object at 0xb0853d6c>
might be clearer?
comment:11 Changed 5 years ago by jhpalmieri
For item 1, margin overruns, I can easily fix some of them, but some of them are verbatim output from sage, and I don't know what I can do about these. For example, on page 56, the output from hitting '?' at the ipdb> prompt runs into the right margin. Should I delete this output altogether? There is a similar situation on p. 86, output from 'prun', and also on p. 29 (hard to see): the second line of output from I.primary_decomposition(). Is the issue running off of the page, or just running into the margin?
At the moment, I've cheated: I've altered the output for these commands, adding in artificial line breaks for readability. I've only had to do this a few times, so I'm not too worried about it.
For point 2, I disagree that "it wouldn't hurt" to remove references to Sage Constructions: I think it's important to have pointers for where to look for more information. So my opinion is, whenever Sage Constructions gets replaced by something else, whoever is responsible for that change should also make the corresponding change to the tutorial. If we delete all references to Sage Constructions now, the tutorial will be less informative, hence not as good.
For point 3, that's easy enough to fix. [Actually, taking a look, that banner is quite old, and the GPL stuff isn't mentioned at all in the banner any more. I've replaced it with a newer banner.]
For point 4, I haven't even gotten that far in my changes, but I'll add something relevant there.
I'll post a patch which adds these changes. When I get a chance, I'll update the pdf and html versions on my web page.
Changed 5 years ago by jhpalmieri
-
attachment
3347-3.patch
added
margin overruns, Sage banner, etc. Use this patch in addition to the earlier one.
comment:12 Changed 5 years ago by jhpalmieri
The latest version of the file '3347-2-with-dsage.patch' just fixes a few typos that I'd made in earlier versions.
Changed 5 years ago by jhpalmieri
-
attachment
3347-2-with-dsage.patch
added
changes to tutorial (large!) -- this includes the DSAGE section, and replaces the previous patch (if people like it better)
comment:13 Changed 5 years ago by craigcitro
- Keywords tutorial, editor_mhansen added; tutorial removed
comment:14 Changed 5 years ago by mhansen
I tried applying 3347-1.patch and then 3347-2-with-dsage.patch errors applying the patch. Could you clarify which patches are supposed to be applied in which order?
comment:15 Changed 5 years ago by jhpalmieri
I tried applying 3347-1.patch and then 3347-2-with-dsage.patch errors applying the patch. Could you clarify which patches are supposed to be applied in which order?
Sorry. Apply 3347-1.patch and 3347-2-with-dsage.patch first (these two are independent of each other), then apply 3347-3.patch.
Changed 5 years ago by jhpalmieri
-
attachment
3347-new.patch
added
use 3347-1.patch and this patch (against tutorial from sage 3.0.3)
comment:16 Changed 5 years ago by jhpalmieri
Ignore my previous post. I've created a new patch, 3347-new.patch, which combines the other patches to tut.tex. Use this and 3347-1.patch; the order shouldn't matter, since they're patching different files.
I think the issue before was that my patch was built against the tutorial in sage 3.0.2 and was breaking on the one in 3.0.3.
comment:17 Changed 5 years ago by mhansen
The final 3347.patch is the _only_ one that should be applied, and it applies cleanly against 3.0.3.
comment:18 follow-up: ↓ 19 Changed 5 years ago by mhansen
- Summary changed from [with patches, needs review] lots of changes to the tutorial to [with patches, positive review] lots of changes to the tutorial
comment:19 in reply to: ↑ 18 Changed 5 years ago by mabshoff
- Status changed from new to closed
- Resolution set to fixed
- Milestone changed from sage-3.1.1 to sage-3.0.4
Merged 3347.patch only in Sage 3.0.4.alpha0

new file macros-new.tex (this is a new version of macros.tex)