LSST technical note repository, formatted as a AASTeX paper preprint.
This template generates a new paper repository based on AASTeX. This template also uses bib and author metadata from lsst-texmf. See Technotes for stand-alone technical documentation in the Developer Guide.
The organization responsible for the document.
The identifier of the technote series which will be used to name the repo Choose the series that fits the document's purpose or aligns with the organization creating the document. For now to make this simpler we assume Papers are DMTN or PSTN.
DMTN
for Data Management technical notes.PSTN
for Project Science Team technical notes.
The serial number. Use three digits padded with zeros. If you are creating a technical note manually with this template, see the Create a technote instructions for how to determine the serial number.
The GitHub organization where this technote resides. Choose a GitHub organization that matches the series:
lsst-dm
for the DMTN series.lsst-pst
for the PSTN series.
The title of the technote.
The ID of the first author.
Author IDs may be found in the https://github.com/lsst/lsst-texmf/blob/main/etc/authordb.yaml file in lsst-texmf - this YAML database contains all LSST authors.
Additional authors can be added later in the authors.yaml
file.
The file authors.tex
is generated from the list of author codes in authors.yaml
.
A short description of the technote's content and purpose. This description is used in the repository's README and the abstract in the document itself.
The year of the initial copyright claim. Cookiecutter will automatically populate the current year.
The initial copyright holder. See Copyrights for LSST DM work and the COPYRIGHT file for more information.
The testn-000 directory is an example of a LaTeX-formatted technote.
Example: .github/workflows/ci.yaml.
The GitHub Actions workflow file. You shouldn't have to modify this file unless you have a novel preprocessing build step (see below).
Tip: GitHub Actions provides a flexible Python environment. It's likely easier to run preprocessing scripts directly from the GitHub actions environment, rather than within the lsst-texmf Docker container:
- Install additional Python dependencies in the
Python install
step. - Add additional bash commands for preprocessing steps to run before the
docker run
step. - Structure your
Makefile
so that files built in advance in the GitHub actions environment are automatically used as-is by thedocker run
command.
For more information about using the CI environment, see the GitHub actions workflow documentation.
Example: .gitignore.
The gitignore file ignores the built PDF product (which is persisted on LSST the Docs), as well as intermediate LaTeX build files (including meta.tex
).
The acronyms.tex
file is not ignored so that make acronyms.tex
does not need to be run for every document build.
Example: acronyms.tex.
This file is generated and updated by the make acronyms.tex
command.
Example: authors.tex.
The file authors.tex
is generated from the list of author codes in authors.yaml
.
This file is normally generated through the regular make
command, but can also be regenerated individually by running make authors.tex
.
Example: COPYRIGHT.
Record copyright claims in this file, one line per institution. See the copyright template and Copyrights for LSST DM work and the COPYRIGHT file.
Example: LICENSE.
Generally speaking, LSST documentation is licensed under CC-BY 4.0. See Licensing LSST DM source code and content in the Developer Guide for more information.
Example: local.bib.
Add BibTeX citations to this file that aren't already available in lsst-texmf (the lsstbib/. See the Updating bibliographies documentation in lsst-texmf for how to migrate local bibliography data upstream into lsst-texmf.
Example: Makefile.
The built-in targets are:
make
: compiles the PDF document by runningxelatex
andbibtex
iteratively. This command is used by the CI environment that pushes the PDF to LSST the Docs (lsst.io). See the .github/workflows/ci.yaml file.make acronyms.tex
: regenerates the acronyms.tex file.make authors.tex
: regenerates the authors.tex file.
Add additional make targets to do preprocessing steps (such as running a Python script to generate tables or figures).
Example: Makefile.
List acronyms in this file that are not found in lsst-texmf's lsstacronyms.txt or glossary.txt, or that have multiple definitions (put the one you want in the local myacronyms.txt
file).
The format for each line of this file is:
ACRONYM:Definition
For example:
MIA:Missing In Action
Example: README.rst.
The README advertises the technote to GitHub visitors and provides instructions for authors.
You can update the abstract in the README and add author instructions as necessary.
Example: skipacronyms.txt.
This file contains a list acronyms that should be ignored by generateAcronyms.py
(the script behind make acronyms.txt
).
If your document contains acronym-like strings that aren't acronyms, you can add them to skipacronyms.txt
.
Example: TESTN-000.tex
This file contains the content of the technote itself.
Either write directly in this file, or use the \input
command to include content from other files.
For more information about writing a LaTeX document with the aastex
class file, see the AASTeX Author Guide.