Department of Economics

Syllabus/Lecture Notes Lecture Notes by Date Problem Sets

Economics 312, Empirical Analysis III
Spring 2023; Part A, Problem Sets

Teaching Assistant Information

    • Deniz Dutz (ddutz@uchicago.edu)
      • Office Hours:
    • Sofia Shchukina (sofiashchukina@uchicago.edu)
      • Office Hours:
    • TA Sessions: Fridays, 3:30pm-4:20pm, Saieh 021
    • NOTE: Please email the TAs if you plan to attend their Office Hours so that they do not wait unnecessarily. Please email them before office hours with any specific questions so that they can prepare.

Rules for Problem Sets

There will be 5 problem sets that are due each week. They will be graded and count toward the final grade. The assignments will include analytical, free-response, and empirical questions. These questions will require the use of programming languages like Python, R, or MATLAB. Any programming language is accepted for the simulation exercises. If students have any questions on Problem Sets they should first ask the TA and only ask the professor if the TA is unable to help.

For the problem sets in Part A of the course, you may form groups of up to 3 people, maximum, with no exceptions. These study groups will be permanent for the rest of the course.

Please enter your group into this google sheet by Friday, March 24: 

link to form groups

Each week, please have (only) one of your group members upload their problem set to Canvas (no late submissions are accepted) before the deadline. Note that groups consisting of more than 3 members earn a mark of 0.

Rules for submission:
  • Include everyone’s names in the submitted document
  • Unless specified, the deadline for each assignment is by Monday at 11:59pm.
  • The documents containing the write-up (including but not limited to paragraph answers, equations, graphs, plots, diagrams, tables) must be in PDF format and you are strongly encouraged to use LaTeX to typeset your solutions. A collaborative platform like Overleaf would be useful
  • Please submit your code along with the write-up: both the source file(s) and the PDF version of the code if possible. Platforms like RMarkdown (for R), Jupyter (for Python and R) and MATLAB live scripts can be especially useful to include equations and text in Markdown cells alongside code blocks. The code should be well-formatted, with comments and well-labeled variable names as appropriate
  • Supporting information for problem sets can be found in the problem set module

Your grade for part A of the course will depend on the problem sets (50%) and the take home exam (50%). Bonus points will be awarded for participation during class.

Problem Sets

Problem Set 1

Problem Set 2

Problem Set 3

Problem Set 4

Final Exam