100-instructors.qmd

{{< include _setup.qmd >}}

# Instructor's guide {#sec-instructors}

## Introduction 

This is an instructor's guide to conducting replication projects in courses. In addition to benefiting the field in ways that have been previously discussed by some of the authors of this book [e.g., @hawkins2018; @frank2012], replication-based courses can additionally benefit students in these courses. In this guide, we will describe these benefits, explore different ways in which courses may be modified depending on student level and resources, and provide some guidelines and examples to help you set up the logistics of your course.

## Why Teach a Project-Based Course?

Over the years, we have observed many ways in which our replication-based courses benefited students above and beyond a more traditional lecture and problem set-based course. Some of these benefits include: 

* **Student interest**: Since each student will be free to replicate a study that is aligned with their research interests, this freedom facilitates a more direct application of course methods and lessons to a project that is interesting to each student.
* **Usefulness**: If this course is taught in the first year of the program (as recommended), students may use their replication project as a way to establish robustness of a phenomenon before building studies on top of it.
* **Realism**: Practice datasets that are typically provided for course exercises lack the complexity and messiness of real data. By conducting a replication project and dealing with real data, students learn to apply the tools provided in the course in a way that more closely demonstrates their usefulness beyond the course. 
* **Intuition**: Presentations of replication outcomes across the class along with a discussion of what factors seemed to predict these outcomes helps students develop a better intuition when reading the literature for how likely studies are to replicate. 
* **Perspective**: Frustrating experiences with ambiguity (whether regarding experimental methods, materials, or analyses) can motivate students to adopt best practices for their own future studies.

A project-based course may look very different depending on student level (undergraduate vs graduate/post-doc level) and availability of resources at your institution for a course like this, namely in terms of TA support and course funding (for data collection). For most of this guide, we will assume that you have a similar setup to ours (i.e., teaching at the graduate/post-doc level and have course funding and TAs to support the course), but we have also spent some time considering ways to adjust the course to fit different student levels and availability of resources (see "Scenarios for different course layouts"). 


## Logistics

### Syllabus considerations

If it is your first time teaching this course, you may want to decide ahead of time whether your course will mainly focus on content, or whether you will cover *both* content and relevant practical skills. For instance, if the course is for undergraduate students, you may decide to focus mainly on content, whereas if the course is for graduate students, they may find it more useful if the course covers both content and practical skills they can use in their research. 

Another important consideration is how long your course will be. Depending on whether your university operates on quarters or semesters, the pace of the course will differ. For Psych 251, since we are on the quarter system, we use the 10-week schedule shown below. However, we have also adapted this schedule to a 16-week course given that it better represents a majority of other institutions' academic calendars. At the end of this appendix, we give a set of sample class schedules.

### Grading

Depending on your course format and teaching philosophy, you may have preferred grading criteria. As a point of reference, in Psych 251, we wanted to encompass both the assignments (problem sets and project components) and course attendance and participation. In addition, because the replication project is a central part of the course, we weighted the project components slightly more than the problem sets: 

\clearpage
* 40%: Problem sets (four, at 10% each)
* 50%: Final project components, including presentations, data collection, analysis, and writeup
* 10%: Attendance and participation in class

### Course budget

For our course, we usually receive around US$1,000 for course funding from the Psychology Department. In addition, when students from other departments are enrolled, we have been lucky to receive additional funding from those departments as well, to further support the course. Still, making sure that the course funds cover all students' projects is one of the most challenging parts of the course. Assuming you have a budget to work with, here are some lessons we've learned along the way regarding budgeting (and if you don't have any funding, please refer to the section titled "Course Funding" under "Scenarios for different course layouts"):

* Before students pick their study to replicate, provide them with an estimate of how many participant hours they will be able to receive for their project
* As soon as students pick a study for their replication project, help each student run a power analysis to confirm that replicating the study would be within the budget (TAs can help with this)
* If a student feels strongly about a study that does not fit within the budget, consider the following ways to adjust the study: (1) Can the study be made shorter by cutting out unnecessary measures? (2) If it is a multi-trial study, can the number of trials be reduced? (3) Would their advisors be willing to provide additional funding? (4) Can the study be run on university participant pools?
* As mentioned above, if there are students from other departments who are enrolled in your course, one possibility to obtain more funding is to reach out to the heads of those departments to see whether they would be willing to help support your course.

Once all projects have been approved as within-budget, we encourage you to create a shared spreadsheet containing each student's name, so that they can fill in the details of their replication project. Ultimately, this will help ensure that students are paying fair wages to their participants and keep track of how the course funds are being divided up. 

### Course-related Institutional Review Board application

While it may be possible to apply for individual IRB approval for each student's project, we recommend applying for course-wide standard IRB approval for all replication projects that are conducted in your class. Contacting your review board early in the planning stages of the course should clarify what options you have available.

One important thing to remember when students run their individual projects is that they should have the course-wide consent form at the beginning of their studies (and TAs should check this when they review the paradigms). For reference, this is the consent form that each student is required to post at the beginning of their study:

"By answering the following questions, you are participating in a study being performed by cognitive scientists in the Stanford Department of Psychology. If you have questions about this research, please contact us at [CLASS EMAIL ADDRESS]. You must be at least 18 years old to participate. Your participation in this research is voluntary. You may decline to answer any or all of the following questions. You may decline further participation, at any time, without adverse consequences. Your anonymity is assured; the researchers who have requested your participation will not receive any personal information about you."

## Scenarios for different course layouts

Now that we have covered the standard format of the course, we want to now turn our attention to ways in which this format can be tweaked in order to fit different needs and resources. We have organized this section into two main categories: student level and course resources (such as TAs and course funding). 

### Student level

While Psych 251 at Stanford is geared toward graduate students (and is currently a required class for entering first-year graduate students in the Psychology Department), we also accept advanced undergraduate students as well as graduate students from other departments (e.g., education, human-computer interaction, philosophy, computer science). On the first day of our course, we tell students that they should be comfortable with two of the three following topics:

1. Some knowledge of psychology experimentation subject matter
2. Statistical programming: things like functions and variables
3. Basic statistics like ANOVA and $t$-test

If students are only comfortable with one of the three topics above, we warn them ahead of time that the course may demand more time from them than the average student.

Now, if you are planning on catering this course for undergraduate students, chances are that they have had less exposure to these topics overall, so there are multiple ways to calibrate the course accordingly:

**Prerequisites**: Require students to have completed courses that cover at least two of the three topics mentioned above (i.e., a psychology class, a class that covers statistical programming, a class that covers basic statistics, any two of the three).

**Pace**: Unlike Psych 251, where the entire course only lasts 10 weeks, a class for undergraduates may benefit from a slower pace, allowing more time to cover the foundational principles before diving into the project. For instance, the course could be held over multiple academic semesters/quarters, with the project goal of Course #1 being choosing and planning the replication study, and the project goal of Course #2 being the execution and interpretation of the replication. 

**Pair-based or group-based projects**: In our course, each student is required to conduct their own replication project. However, this structure may be overwhelming for undergraduate students who may have less confidence taking on an entire replication project by themselves. One option that may alleviate this pressure is to have students conduct these projects as pairs or as small teams, so that they can collectively draw on each others' strengths. When assigning these pairs or teams, it may be especially helpful to try to ensure a relatively even balance of students who are confident in each of the three areas outlined above (psychology, statistical programming, basic statistics).

### Course resources

We think there are two main ways in which your course may have different resources from our model: in terms of course assistance (i.e., teaching assistants), and in terms of course funding for student projects. We'll explore ways to work around each of these in this section.

**Teaching assistants**. As a point of comparison, in general, two to three teaching assistants are allocated to Psych 251 (which enrolls about 25-35 students); this typically comes out to about 10-12 students per TA. We are very lucky to have this level of TA support. Since a project based course requires individual attention and feedback, having fewer than this number of TAs entails a lot of work for the instructor. What if you have *no* TAs? With some adjustments, there are still ways you can make the course work sans-TA; we outline a few ideas below:

1. **Peer grading**. As an instructor with no TAs, the area that will require the biggest lift in terms of time and attention is grading. One way to overcome this is to introduce a peer-grading system, in which students grade each others' work. If you choose this route, two things that may encourage fair grading among your students is to (1) distribute a clear and specific rubric that reduces the amount of subjectivity in the grading process as much as possible, and (2) anonymize the assignments so that students do not know whose assignment they are grading. If possible, it may again be beneficial to assign grading pairs that consist of students that are relatively knowledgeable in different areas, so that they can provide feedback that address weak points in each others' work. 

2. **Collective troubleshooting**. The second most time intensive area you will have to make up for is the amount of troubleshooting you may have to do for students who run into issues implement their projects, anywhere from getting GitHub and R Markdown up and running on their devices, to trouble with data collection on  Amazon Mechanical Turk. One way to encourage communal support among your students is to set up a central discussion board for the course (e.g., Piazza or a course channel on Slack) where students can publicly (but anonymously, if desired) post issues they are running into. Then, you can offer extra credit to students who help troubleshoot these issues, in order to further incentivize collective troubleshooting. There will likely still be issues that cannot be addressed by the students, but this system at least frees up your time to focus your attention on those that only *you* can address.

3. **Single class-wide project**. Finally, if the collective grading and troubleshooting methods outlined above do not cut down on enough time, you could consider walking through a single replication project as a class.^[This approach does cancel out some of the benefits of a project-based course we mentioned at the start---namely, the project will likely no longer fit each student's specific research interest, so there may be less benefit in terms of specific student interest and usefulness for their program of research, but the other two benefits of realism and intuition (especially if the project is discussed in the context of other replication findings) still stand.] To make a single-project course work, you could have students nominate studies they would like to replicate as a class, and then have them vote on the final choice. Once the target study has been selected, every student can individually carry out all the steps of the project, including preregistering and writing up the analysis script. Then, setting up and running the data collection phase can happen during class, and once data has been collected, you can distribute it to the students for them to run it through their analysis script and interpret the result. Whether you choose to have students grade each others' work or whether you grade their work yourself, the fact that the project is standardized should cut down on a lot of the time you would otherwise spend learning about the details of every individual project.

**Course funding**. In addition to availability of TAs, another way in which your course may be different from ours is in terms of course funding. If you have little or not funding for your course (even after reaching out to relevant members of your department or institution), we suggest the following adjustments:

1. **Pair-group-based projects**. Similarly to suggestion 3 for addressing different student levels, one option for limited course budgets is to have students conduct the replication projects as pairs or teams to reduce the cost of data collection. This structure may have the added benefit of encouraging students to problem-solve together. Alternatively, each student in the pairs or teams could complete each step of the replication individually (e.g., writing up the report, analyzing the data, interpreting the result), which would ensure that each student takes full responsibility for every step of the project. This structure may also provide opportunities for interesting discussions at the end of the course around analytic reproducibility, especially if students in the same teams (with the same dataset) differed in the conclusions they drew about the replication outcome. 

2. **Funding from advisors**. In some cases, students come to us with target studies that require more funding than we are able to allocate, but that they feel particularly invested in (e.g., because of how relevant the study is to their line of research). Once we rule out other ways of making the study fit our budget (e.g., dropping extra control conditions, running a subset of the study), we often ask students whether their advisor would be willing to fund the study. We have found that advisors are often willing to do this, especially if the replication could serve an important role in the development of the student's research program. Similarly, one way to reduce the burden on a limited course budget would be to encourage all students to first ask their advisors about whether they would be willing to fund part or all of the data collection for the replication. While chances are that some advisors will be unwilling or unable to do this, there should still be a meaningful reduction in the number of projects the course will need to fund. 

3. **Reproduce a replication**. The suggestions above apply if you at least have *some* amount of course funding, but what if you have *no* funding at all? While there are obvious limitations to this solution, one suggestion is to have students reproduce past public replications. For instance, our [course GitHub page](https://github.com/psych251) contains public repositories of all past replication projects that have been conducted in our course. Since the data for each replication project is available in these repositories, you could provide each of your students with a dataset and the original paper associated with it, and assign them to reproduce the results of the replication. Students should then be able to follow each step of the replication project described below (e.g., writing the report, identifying the key analysis, running the analysis). This format will only work if students do not view the original final replication reports that are posted publicly for their project, so it may be necessary to be clear about this at the beginning of the course. 

For those of you who are working with a different course format (whether in terms of student level or course resources), we hope these suggestions were useful. If you try out a new idea in your course that you found helpful, we would be thrilled if you shared them with us!

## Sample course schedules

The sample syllabi laid out below are categorized along the following decisions: (1) material: whether the course focuses on just content or both content and skills, and (2) duration: whether the course is 10 weeks long or 16 weeks long.

For undergraduate instructors, we have labeled advanced topics in purple. We expect that these topics are best suited for advanced undergraduate students. As for content around statistics (e.g., estimation, inference), instructors should decide how much of this content to teach, depending on students' prior preparation. 

```{r}
adv_color <- "#ebe8fc"
syllabus_table <- function(syllabus_file) {
  
  syllabi <- readr::read_csv(syllabus_file, na = character(),
                             col_types = "cccccc")
  adv_rows <- which(syllabi$Difficulty == "adv")

  syllabus <- syllabi |> dplyr::select(-Difficulty)
  
  if (knitr::is_latex_output()) {
    syllabus |>
      knitr::kable(#format = "latex",
        booktabs = TRUE,
        longtable = TRUE,
                   linesep = c("", "", "\\hline")) |>
      kableExtra::row_spec(adv_rows, background = adv_color)
  } else if (knitr::is_html_output()) {
    syllabus |>
      knitr::kable(table.attr = 'data-quarto-disable-processing="true"') |>
      kableExtra::kable_styling(bootstrap_options = c("condensed")) |>
      kableExtra::row_spec(adv_rows, background = adv_color)
  }
}
```

\clearpage

::: {.panel-tabset}

### 10 weeks

\footnotesize

A sample 10-week syllabus with both skills and content materials:

```{r}
#| cache: false

syllabus_table("data/instructor_guide/Content_Skills_10wk.csv")
```

\clearpage

### 10 weeks, content only

A sample 10-week syllabus with only content materials:

```{r}
#| cache: false

syllabus_table("data/instructor_guide/Content_10wk.csv")
```

\clearpage

### 16 weeks 

A sample 16-week syllabus with both skills and content materials:

```{r}
#| cache: false

syllabus_table("data/instructor_guide/Content_Skills_16wk.csv")
```

\clearpage

### 16 weeks, content only 

A sample 16-week syllabus with only content materials:

```{r}
#| cache: false

syllabus_table("data/instructor_guide/Content_16wk.csv")
```

\normalsize

:::