Plan: add worked code, figures and exercises

Open
#143 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
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
r
Domain
documentation

Research direction

Start by reading the development plan in #139, the attached sub-issue #72, and the sibling workstream that will decide the scope of the worked analyses. The issue describes changes across whole chapters: add causal diagram figures, executed R chunks using the public dataset, exercise and solution pairs, and enable the existing checks in Morrison-Lab/gha in report mode. It says to begin after the stalled chapter pull requests land; done means those planned additions and checks are in place.

Written by the indexing model from the issue text.

Description

ai-authored

Part of the development plan in #139.

The problem

At ff6279d the notes hold 144 definitions and 143 examples, and no exercise div and no figure div.
Only chapters 6 and 7 hold R chunks.
A reader meets every estimator in prose and almost never sees one computed.

Plan

  1. Figures first. Draw each causal diagram the notes describe in prose as a figure, starting with the chapters on graphical representation, confounding and selection bias.
  2. Worked code for Part II. The book's Part II analyses one public dataset throughout; add executed chunks that reproduce each chapter's estimates from a local copy of that data, with numbers in the prose coming from inline code.
    How much to reproduce depends on the scope decision in the sibling workstream.
  3. Exercises. Add exercise and solution pairs after each definition and result, following the lab's rule that an example follows every definition.
  4. Checks. Turn on the lab's checks that already exist for this in Morrison-Lab/gha (example after definition, figures in visualization divs), in report mode first.

#72 is attached as a sub-issue.

Do this after the stalled chapter pull requests land, since each step edits whole chapters.

Posted by Claude Code (AI agent) --- not written by a human.

Dominant language
Lua
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

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 ucdavis/win

All issues in ucdavis/win

Similar issues

More Lua issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.