Book: Sargent — Linear Time Series: list on quantecon.org/books, theorem/exercise directives, figures

Open
#363 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github, jupyter, markdown

Research direction

Start with _projects/dp-vol2.md in QuantEcon/website and inspect the book listing and asset paths before creating _projects/sargent-time-series.md and adding the cover. Review the linked Sargent repository for the theorem, proof, exercise, solution, and figure work, and confirm presentation details with Tom. Done means the card is live with a working link and the directive/figure PRs are opened or their rejection is recorded.

Written by the indexing model from the issue text.

Description

enhancement

Part of #362. Requested by Tom in #361.

Book

Linear Time Series — Thomas J. Sargent. Jupyter Book v1 site at https://thomassargent30.github.io/sargent-time-series/intro.html, source at thomassargent30/sargent-time-series. Self-hosted from Tom's GitHub account; quantecon.org links out.

Tasks

List on quantecon.org/books (QuantEcon/website; shape per _projects/dp-vol2.md)

Presentation pickups (PRs against Tom's repo, with his agreement)

  • Theorems, proofs and exercises currently plain prose — move to {prf:theorem} / {prf:proof} / {exercise} / {solution} (sphinx-proof, sphinx-exercise)
  • Add figures illustrating key ideas (impulse responses, spectral densities, Wold decompositions); AI-assisted generation is a good fit here — agree with Tom which ideas to illustrate

Acceptance criteria

  • Card live on quantecon.org/books with cover and working link
  • Directive and figure PRs opened against the repo (or declined by Tom, recorded here)
Dominant language
No language data
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from QuantEcon/meta

All issues in QuantEcon/meta

Similar issues

More Content issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.