Implementation

Author

Affiliation

Your Name Here

Old Dominion University

Before You Start

In your Imagination Exercise you committed to a plan. Now carry it out: get the data, run the analysis in R, and write it up as a report for a reader who has not seen your IE.

Changes are fine, within reason. Your Implementation may differ from your IE (a different year range, a dropped control, a swapped data source), as long as you explain what changed and why. Stick to methods from the course. If you use something beyond the notes, flag it and explain it in plain language.

Never fabricate or simulate data. If data will not load, or a result looks wrong, say so in your report and troubleshoot.

How to use AI: You may (and should!) use AI tools to help you throughout, but what you submit is your responsibility, not the AI’s. Read what it gives you, check it against the course material, and change whatever you would not stand behind. Never submit something you don’t understand, and make sure that what you submit is written in your own voice.

What to submit: Submit the rendered .html file on Canvas, along with the video described at the end. Your submission will be graded with the course rubric.

This week’s tools

The notes for the method you are using: Module 2 (DiD), Module 3 (SCM), or Module 4 (IV or RDD). Be sure to consider tools from earlier modules, too.

Outline

Use these sections, in this order. Write in your own words and about your own setting.

1. The plan, and what changed

Summarize your IE, and note anything that changed and why.

2. Data

Describe your data and how you cleaned it.

3. Main estimate

Report and explain your main estimate.

4. Diagnostics

Show the checks your method calls for, and say what they tell you.

5. Interpretation

Discuss what your results do and do not show, and how they compare with your motivating paper.

6. Process Reflection

In your own words (Claude Code is not allowed to write this, and it knows that): how did you use Claude on this report, where did its first attempt fall short, and what did you change or reject, and why?

Video Presentation

Record one continuous screen recording, about ten to twelve minutes for the presentation (no shorter than five, no longer than twenty) plus the four questions below, and upload it to Canvas. Your recording must show your entire screen (including the time) and include your voice. Showing your face is optional.

Part 1: Presentation (20 points). Present your report as if you were briefing a boss or client who has not seen it. Keep your rendered report open while you talk so you can reference tables and figures, but do not read from it.

Part 2: Questions (20 points). Immediately after, open a new Claude Code session (have it open in the background so you don’t waste time opening it during the recording) and paste the prompt from https://alexcardazzi.github.io/econ708a/implement_check_prompt.txt, with your report’s file name filled in. Claude will ask you four questions about your report, as if it were a boss, client, or audience member. Claude may ask why you made a particular choice, so be ready to explain it. If a question is unclear, you may ask Claude to reword or clarify it in your own words, once per question. Answer each one out loud, then type “next question” to move on.

--- title: "Implementation" author: "Your Name Here" institute: "Old Dominion University" format: html: theme: united code-tools: true code-fold: true code-summary: "Code" code-copy: hover link-external-newwindow: true tbl-cap-location: top fig-cap-location: bottom self-contained: true editor: source --- ```{r setup, include=FALSE} # INCLUDE THIS AT THE START OF EACH ASSIGNMENT # DO NOT EDIT THIS knitr::opts_chunk$set(fig.align = 'center') knitr::opts_chunk$set(out.width = '90%') knitr::opts_chunk$set(results = 'hold') knitr::opts_chunk$set(fig.show = 'hold') knitr::opts_chunk$set(dev='svg') knitr::opts_chunk$set(error = TRUE) par(mar = c(4.1, 4.1, 1.1, 4.1)) ``` ## Before You Start In your Imagination Exercise you committed to a plan. Now carry it out: get the data, run the analysis in R, and write it up as a report for a reader who has not seen your IE. **Changes are fine, within reason.** Your Implementation may differ from your IE (a different year range, a dropped control, a swapped data source), as long as you explain what changed and why. Stick to methods from the course. If you use something beyond the notes, flag it and explain it in plain language. **Never fabricate or simulate data.** If data will not load, or a result looks wrong, say so in your report and troubleshoot. **How to use AI**: You may (and should!) use AI tools to help you throughout, but what you submit is your responsibility, not the AI's. Read what it gives you, check it against the course material, and change whatever you would not stand behind. Never submit something you don't understand, and make sure that what you submit is written in your own voice. **What to submit**: Submit the rendered `.html` file on Canvas, along with the video described at the end. Your submission will be graded with the [course rubric](https://alexcardazzi.github.io/econ708a/rubric.html). --- ### This week's tools The notes for the method you are using: Module 2 (DiD), Module 3 (SCM), or Module 4 (IV or RDD). Be sure to consider tools from earlier modules, too. ### Outline Use these sections, in this order. Write in your own words and about your own setting. #### 1. The plan, and what changed - Summarize your IE, and note anything that changed and why. #### 2. Data - Describe your data and how you cleaned it. #### 3. Main estimate - Report and explain your main estimate. #### 4. Diagnostics - Show the checks your method calls for, and say what they tell you. #### 5. Interpretation - Discuss what your results do and do not show, and how they compare with your motivating paper. #### 6. Process Reflection - In your own words (Claude Code is not allowed to write this, and it knows that): how did you use Claude on this report, where did its first attempt fall short, and what did you change or reject, and why? --- ## Video Presentation Record one continuous screen recording, about ten to twelve minutes for the presentation (no shorter than five, no longer than twenty) plus the four questions below, and upload it to Canvas. Your recording must show your entire screen (including the time) and include your voice. Showing your face is optional. **Part 1: Presentation (20 points).** Present your report as if you were briefing a boss or client who has not seen it. Keep your rendered report open while you talk so you can reference tables and figures, but do not read from it. **Part 2: Questions (20 points).** Immediately after, open a **new** Claude Code session (have it open in the background so you don't waste time opening it during the recording) and paste the prompt from [https://alexcardazzi.github.io/econ708a/implement_check_prompt.txt](https://alexcardazzi.github.io/econ708a/implement_check_prompt.txt), with your report's file name filled in. Claude will ask you four questions about your report, as if it were a boss, client, or audience member. Claude may ask why you made a particular choice, so be ready to explain it. If a question is unclear, you may ask Claude to reword or clarify it in your own words, once per question. Answer each one out loud, then type "next question" to move on.