Course Problem Set 2022 (complete posting March 4)
Due March 18 2022 or before
Usual Honor Code procedures:
You may use any of your own inanimate resources--no collaboration or assistance from others.
This work is done under Stanford's Honor Code.
Please ask (rag@stanford.edu) about issues of question interpretation,
and especially in regard to any materials you feel you need but don't have access to.
Any issues that come up (wording, interpretation) I will post a note here, so it would be good to check this page intermittently.
Submission of work.
Given that these problems are untimed, some care
should be taken in presentation, clarity, format.
Especially important is to give full and clear answers to questions, not
just to submit unannotated computer output, although relevant
output should be included.
PLEASE check that you have answered all the parts and subparts.
Please start each problem on a new page and keep all material for a problem contiguous.
In prior years solutions for these problems sets were submitted in hard-copy form at the final class meeting.
Default this qtr is to send your submission by email to David Fager dfager {AT} stanford {DOT} edu.
Now that we have reasonable access to campus (no mask or testing) if someone had a need to submit hard copy, contact Rogosa to arrange that
The stated deadline is March 18 6PM PDT. Grading deadline is Tuesday so no slippage in deadline is possible.
Incompletes will be difficult as I am fleeing to TN spring qtr.
Prior quarters, students used a variety of methods: posting to their Google drive (e.g. pdf files) and giving us access, or mailing rendered html or pdf files.
Most popular, posting an html file on rpubs was great for a project course, but doesn't provide adequate security for an exam file.
Of course, and I probably don't need to say this, do not send a Word binary file (you shouldn't do that to anyone).
Exam paper-- available here simple text file
Problem 3. 3/12/22
One student reported a problem with installing optmatch (standalone or as part of MatchIt).
There is currently an administrative problem at CRAN with optmatch.
The alternatives are to install via github or use the archived version.
Below is code from David Fager for installation from the archive.
# get MatchIt
> install.packages("MatchIt")
> library(MatchIt)
# get devtools
> install.packages("devtools")
> library(devtools)
# get optmatch from archive using a devtools function
> install_url("https://cran.r-project.org/src/contrib/Archive/optmatch/optmatch_0.9-17.tar.gz")
> library(optmatch)
stack overflow post from matchit maintainer Noah Greifer
https://stackoverflow.com/questions/71196159/alternative-for-optmatch-in-r