A rewrite of A Geometric Approach to Matrices (frequently abbreviated to "GAtM") by Peter Herreshoff. If you are looking for the text, go to https://gunn-gatm.github.io/ for the PDFs without all the code.
This project was first bodged together in summer of 2019. I'd estimate it took a couple hundred hours, but it's not remotely free of errors and is often inconsistent. Today is February 13, 2021, and after some encouragement by a certain Yu-Ting Chang, I (Timothy) have decided to work on it once more, correcting errors and making the build system less terrifying.
There are two main documents: the textbook, and the answer key. The textbook comprises a cover, a credits page, sixteen chapters, and a glossary. The answer key comprises a cover and sixteen chapters. For simplicity, we treat the cover and credits as pseudo-chapters sometimes, even though they are handled separately. All this is inside the book/ directory; there is one folder per chapter, with each folder containing a chapter source file, cleverly named chapter.tex, and an answer key source file, named answers.tex.
If all of the textbook were to be put into one monolithic document, it would be some thousand lines long, and even longer for the answer key. More importantly as someone working on the document, it would take ages to see if your changes worked on a particular chapter, since you'd have to recompile the whole book each time. To combat this problem, we use the subfiles package, and put each chapter into its own folder. The chapters are given their order by the number preceding their folder.
The subfiles package is relatively intuitive. When compiling the document as a whole, we include a subfile with the command \subfile{./path/to/chapter.tex}, which basically transcludes the contents of that file into the main document. More tricky is when we compile a subfile, each of which is topped with a special documentclass: \documentclass[../textbook.tex]{subfiles} or, in the case of the answer key, \documentclass[../answers.tex]{subfiles}. This causes the entire preamble of the main document to be included in the subfile, including document styling information, macros like \twomat, Asymptote definitions, et cetera.
A chapter is included in the main document if it begins with a number 0–9. All the corresponding chapter.tex files are thus included as subfiles of textbook.tex, and answers.tex files as subfiles of answer_key.tex. The cover, which has different styling than the rest of the document, is included in a special way, by first compiling it to a PDF and then including the PDF in the main document.
The book builds into the build/ folder. (Didn't expect that, huh?) The build folder has the following structure:
.
+-- gatm.pdf
+-- gatm_key.pdf
+-- chapters
+-- 1 Trigonometry Review.pdf
+-- ... rest of the chapters ...
+-- key_chapters
+-- 1 Trigonometry Review.pdf
+-- ... rest of the chapters ...
+-- log
+-- gatm.log
+-- ... various debugging files ...
+-- misc
+-- textbook_cover.pdf
+-- key_cover.pdf
Simple enough. What's not so simple is the actual building process, as we encounter some of LaTeX's most stupefying characteristics.
Building works with python build.py. We can either give it command line arguments, or if no arguments are provided, we enter an interactive mode. To build everything in build, run python build.py all, which builds the textbook and answer key and then excerpts all chapters. To build the textbook ONLY, run python build.py textbook_no_chapters, which will not update textbook_chapters/. To build the textbook and chapters, run python build.py textbook. Similarly, building the answer key is just python build.py key, and without chapters, python build.py key_no_chapters.
To build a specific chapter for testing, run python build.py textbook -c <chapter index or name>, like python build.py textbook -c 10, which will dump chapter.pdf into the folder book/10 Rotations of the Plane. In this case, the only meaningful operations are all, which test builds both the chapter and answer key; chapter; key; clean_logs. In this case, building does not build the entire textbook; it only builds the given chapter, and doesn't do any excerpting. This is mostly the same as the real deal and is optimal for testing, but has the following discrepancies:
- No cross-references (to figures or questions outside of the current chapter)
- Differing page numbers
- Incorrect chapter number
The build is fast, but slightly incorrect, and dumps the PDF into the chapter folder, not the build folder, because it's not intended for students to see. To build a chapter for production, where we put it into the folder build/chapters/, we first need to build the entire document (either gatm.pdf or gatm_key.pdf) and then excerpt the chapter from the full document. Otherwise there will be some small differences from the main document (most notably, cross-references like "see question 6 on page 3" will appear as "see question ?? on page ??").
Good question. The contents of build.py will probably elucidate some details, but the gist of it is we use the log/ directory as an intermediate file—an arena of sorts, if you will. We first compile a given file with pdflatex. If the file contains inline Asymptote vector graphics, a bunch of .asy files will be dumped into the log/ directory. We then run the asy command on those files, which compiles each into a PDF. We then run pdflatex again, which assimilates all the compiled Asymptote files into the document. We're not yet done; information about the location of figures and labels has been dumped out, but is not yet used, so things will say "Figure ??". We thus run pdflatex a final time, which includes this ref information.
The cover is a special case. For reasons I forget, it's compiled into a separate PDF first, placed in build/misc/textbook_cover.pdf (or key_cover.pdf), then included via the module pdfpages into the main document. Sorry for the confusion.
Chapters are excerpted via a rather... hacky method. If you examine the macro \inclchapter, which inserts a chapter by name into the main document, you'll see that it writes some information to the log file via the command \typeout. In particular, it writes things like "Page number of chapter start: ", which is pounced upon by a corresponding regex in the build_book function. It records the start and end pages of chapters. The page number is the absolute page, meaning it doesn't care about page numbers; it's the literal nth page of the document, indexed from 1. We then use pdfjam to grab the chapter out and write it to chapter/ or key_chapters/. Then we get drunk and party all night, knowing that another embarrassing error will crop up soon.
Building chapters is a distinct process. We run the same three commands, but inside a chapter folder itself—the log file is not involved. The subfiles package makes the build relatively consistent, save a few differences, which are detailed above. Because the main point of building a chapter is editing it and seeing the results, the program also automatically opens the chapter, which can be disabled in the terminal by adding the --dont-open flag. For example:
python build.py --chapter 1 --dont-open # Builds 1 Trigonometry Review to book/1 Trigonometry Review/chapter.pdf and doesn't open it
python build.py --key 2 # Builds chapter 2 to book/2 It's a Snap/key.pdf and opens it in the default programThis dumps a lot of random shit into the chapter folders, which is .gitignored, but can get annoying. It can be swept up with the clean option in build.py.
Asymptote Vector Graphics is a language for creating... mathematical vector graphics. Googling about it can be a bit hard because it's overshadowed by the actual mathematical concept of an asymptote, but there is a nice long PDF detailing most of the language. Its syntax is based on C++ and it's not too hard to pick up, but explaining it to you is outside my remit as a bored high school student.
Asymptote files end with the extension .asy, and are compiled with the command... asy. While often figures can be placed in their own separate asy files, I personally like the convenience of inline Asymptote, which is done in documents with \begin{asy} ... \end{asy}. Using inline Asymptote does make the building process a bit more complicated; running pdflatex looks for the compiled results of inline Asymptote files, and, seeing none, will output a bunch of intermediate .asy files into the log directory. (see above)
Note that you will need pdflatex to do this, which you can get from a source like TeXLive: http://www.tug.org/texlive/ (for macOS, it is recommended to get MacTeX). You will also need Asymptote Vector Graphics, which you can get from http://asymptote.sourceforge.net/. As of February 2021, the build system has only been tested to work on macOS, with plans to possibly expand and test on Windows and Linux later.
The production build of GAtM, currently live at https://gunn-gatm.github.io/ (with source files at https://github.com/Gunn-GAtM/gunn-gatm.github.io), is automatically updated through Github Actions after every commit in this source repo. Previously, when you made an edit (even a simple, one-line typo fix), you needed to manually rebuild everything, make sure that's committed, push to this repo, and then also the production build repo. Thankfully, this process has been simplified with automatic workflows. It's still recommended, especially for larger edits, to rebuild yourself first and check whether the changes are valid, but you no longer need to go through each step described above (and also the build/ folder is now .gitignored). We can thank our Lord Yu-Ting Chang for this development.
Inside .github/workflows/, you will see 3 workflow .yml files for Github Actions: push.yml, pull_request.yml, and autoblack.yml. On every push to this repository, the push.yml workflow is activated (wow, who would've guessed?). After installing the dependencies on a macOS virtual environment using HomeBrew (sped up through some caching), the Action rebuilds everything automatically and auto-deploys to the production site repo. On every pull request (or PR sync, reopen, etc.), the pull_request.yml workflow rebuilds the textbook with the proposed changes, adding the build/ directory as a Workflow Artifact to be downloaded/viewed
under the Checks tab for that PR (another way to ensure changes are valid). Finally, if a push includes a change to a .py file that was not formatted according to Black standards (https://github.com/psf/black), the autoblack workflow will lint and push the changes to the Python files to this repo.
Important note to future maintainers: an ssh key is what allows the push.yml Action from this repo to push to the production site repo; in case it no longer functions, just regenerate a new public/private ssh key (similar to setting up git on your computer to work with GitHub), and place the private key, with the name DEPLOY_KEY, as a new secret under Settings > Secrets > Repository Secrets in this repo, and the public key, also named DEPLOY_KEY, as an actual deploy key under Settings > Deploy Keys in the production site repo.
Enjoy!